[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FlowLabel TCs
Below is an inital I-D that tries to defined a common
set of TCs for the flowlabel/flowid
Thanks,
Bert
Network Working Group B. Wijnen
Internet-Draft Lucent Technologies
Expires: August 4, 2003 February 3, 2003
Textual Conventions for IPv6 Flow Label
draft-wijnen-ipv6-flowlabel-00.txt
Status of this Memo
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 4, 2003.
Copyright Notice
Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract
This MIB module defines textual conventions to represent the commonly
used IPv6 Flow Label. The intent is that these textual conventions
(TCs) will be imported and used in MIB modules that would otherwise
define their own representations.
Wijnen Expires August 4, 2003 [Page 1]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard SNMP Management Framework . . . . . . . 4
3. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
6. Intellectual Property Notice . . . . . . . . . . . . . . . . . 9
Normative References . . . . . . . . . . . . . . . . . . . . . 10
Informative References . . . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . 12
Wijnen Expires August 4, 2003 [Page 2]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
1. Introduction
Several standards-track MIB modules have defined objects to represent
an IPv6 Flow Label (sometimes refered to as Flow ID) [RFC2460].
Unfortunately the result is a set of different definitions for the
same piece of management information. This may lead to confusion and
unneeded compelxity.
This document defines a set of textual conventions (TCs) that can and
should be (re-)used in MIB modules, so that they all represent an
IPv6 Flow Label in the same way. In fact, PIB modules can and should
also use these TCs when they need to represent an IPv6 Flow label.
Wijnen Expires August 4, 2003 [Page 3]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
2. The Internet-Standard SNMP Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard SNMP Management Framework, please refer to section
7 of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58,
RFC 2580 [RFC2580].
Wijnen Expires August 4, 2003 [Page 4]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
3. Definitions
IPV6-FLOW-LABEL-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI
TEXTUAL-CONVENTION FROM SNMPv2-TC;
ipv6FlowLableTCMIB MODULE-IDENTITY
LAST-UPDATED "200302030000Z" -- 3 Feb 2003
ORGANIZATION "IETF Operations and Management Area"
CONTACT-INFO "Bert Wijnen (Editor)
Lucent Technologies
Schagen 33
3461 GL Linschoten
Netherlands
Phone: +31 348-480-685
EMail: bwijnen@lucent.com
Send comments to <mibs@ops.ietf.org>.
"
DESCRIPTION "This MIB module provides commonly used textual
conventions for IPv6 Flow Labels.
Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC xxxx,
see the RFC itself for full legal notices.
"
-- RFC-Editor assigns xxxx above
-- Revision History
REVISION "200302030000Z" -- 3 Feb 2003
DESCRIPTION "Initial version, published as RFC xxxx."
-- RFC-Editor assigns xxxx above
::= { mib-2 nnn } -- IANA assigns nnn
IPv6FlowLabel TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION "The flow identifier or Flow Label in an IPv6
packet header that may be used to discriminate
traffic flows.
"
Wijnen Expires August 4, 2003 [Page 5]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
REFERENCE "Internet Protocol, Version 6 (IPv6) specificationR,
section 6. RFC 2460
"
SYNTAX Integer32 (0..1048575)
IPv6FlowLabelOrAny TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION "The flow identifier or Flow Label in an IPv6
packet header that may be used to discriminate
traffic flows. The value of -1 is used to
indicate a wildcard, i.e. any value.
"
SYNTAX Integer32 (-1 | 0..1048575)
END
Wijnen Expires August 4, 2003 [Page 6]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
4. Security Considerations
The MIB module contained in this memo does not define any management
objects. Instead, it defines a set of textual conventions which may
be used by other MIB modules to define management objects.
Meaningful security considerations can only be written for MIB
modules that define concrete management objects. This document has
therefore no impact on the security of the Internet.
Wijnen Expires August 4, 2003 [Page 7]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
5. Acknowledgments
This document was produced by the Operations and Management Area
"IPv6MIB" design team. The editor would like to thank Juergen
Schoenwaelder for providing various pieces of XML source text that
have shamelessly been re-used in this document.
Wijnen Expires August 4, 2003 [Page 8]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
6. Intellectual Property Notice
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Wijnen Expires August 4, 2003 [Page 9]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
Normative References
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999.
Wijnen Expires August 4, 2003 [Page 10]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for the
Internet-Standard SNMP Management Framework", RFC 3410,
December 2002.
Author's Address
Bert Wijnen
Lucent Technologies
Schagen 33
3461 GL Linschoten
Netherlands
Phone: +31-348-480-685
EMail: bwijnen@lucent.com
Wijnen Expires August 4, 2003 [Page 11]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Full Copyright Statement
Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
Wijnen Expires August 4, 2003 [Page 12]
Internet-Draft Textual Conventions for IPv6 Flow Label February 2003
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
Wijnen Expires August 4, 2003 [Page 13]