draft-ietf-ccamp-gmpls-tc-mib-10.txt   draft-ietf-ccamp-gmpls-tc-mib-11.txt 
Network Working Group Thomas D. Nadeau, Ed. Network Working Group Thomas D. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Proposed Status: Standards Track Proposed Status: Standards Track
Expires: October 2006 Adrian Farrel, Ed. Expires: March 2007 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
September 2006
Definitions of Textual Conventions for Generalized Multiprotocol Definitions of Textual Conventions for Generalized Multiprotocol
Label Switching (GMPLS) Management Label Switching (GMPLS) Management
draft-ietf-ccamp-gmpls-tc-mib-10.txt draft-ietf-ccamp-gmpls-tc-mib-11.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 45 skipping to change at page 2, line 5
Abstract Abstract
This document defines a Management Information Base (MIB) module This document defines a Management Information Base (MIB) module
which contains Textual Conventions to represent commonly used which contains Textual Conventions to represent commonly used
Generalized Multiprotocol Label Switching (GMPLS) management Generalized Multiprotocol Label Switching (GMPLS) management
information. The intent is that these TEXTUAL CONVENTIONS (TCs) will information. The intent is that these TEXTUAL CONVENTIONS (TCs) will
be imported and used in GMPLS related MIB modules that would be imported and used in GMPLS related MIB modules that would
otherwise define their own representations. otherwise define their own representations.
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
Table of Contents Table of Contents
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006
1. Introduction ...................................... 2 1. Introduction ...................................... 2
2. The Internet-Standard Management Framework ........ 2 2. The Internet-Standard Management Framework ........ 2
3. GMPLS Textual Conventions MIB Definitions ......... 3 3. GMPLS Textual Conventions MIB Definitions ......... 3
4. Security Considerations ........................... 6 4. Security Considerations ........................... 5
5. IANA Considerations ............................... 6 5. IANA Considerations ............................... 6
6. References ........................................ 6 6. References ........................................ 6
6.1. Normative References ............................ 6 6.1. Normative References ............................ 6
6.2. Informative References .......................... 7 6.2. Informative References .......................... 7
7. Acknowledgements .................................. 7 7. Acknowledgements .................................. 7
8. Contact Information ............................... 7 8. Contact Information ............................... 7
9. Intellectual Property Considerations .............. 8 9. Intellectual Property Considerations .............. 8
10. Full Copyright Statement ......................... 9 10. Full Copyright Statement ......................... 9
1. Introduction 1. Introduction
skipping to change at page 2, line 31 skipping to change at page 2, line 34
This document defines a MIB module which contains Textual Conventions This document defines a MIB module which contains Textual Conventions
for Generalized Multiprotocol Label Switching (GMPLS) networks. These for Generalized Multiprotocol Label Switching (GMPLS) networks. These
Textual Conventions should be imported by MIB modules which manage Textual Conventions should be imported by MIB modules which manage
GMPLS networks. GMPLS networks.
This MIB module supplements the MIB module in [RFC3811] that defines This MIB module supplements the MIB module in [RFC3811] that defines
Textual Conventions for Multiprotocol Label Switching (MPLS) Textual Conventions for Multiprotocol Label Switching (MPLS)
Management. [RFC3811] may continue to be used without this MIB module Management. [RFC3811] may continue to be used without this MIB module
in networks that support only MPLS. in networks that support only MPLS.
Comments should be made directly to the CCAMP mailing list at
ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119, document are to be interpreted as described in BCP 14, RFC 2119,
reference [RFC2119]. reference [RFC2119].
For an introduction to the concepts of GMPLS, see [RFC3945]. For an introduction to the concepts of GMPLS, see [RFC3945].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
3. GMPLS Textual Conventions MIB Definitions 3. GMPLS Textual Conventions MIB Definitions
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2578], [RFC2579], and [RFC3811]. [RFC2578], [RFC2579], and [RFC3811].
GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY MODULE-IDENTITY
FROM SNMPv2-SMI -- RFC2578 FROM SNMPv2-SMI -- RFC2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB -- RFC3811 FROM MPLS-TC-STD-MIB -- RFC3811
; ;
gmplsTCStdMIB MODULE-IDENTITY gmplsTCStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200604060001Z" -- 06 April 2006 00:00:01 GMT "200609060001Z" -- 06 September 2006 00:00:01 GMT
ORGANIZATION ORGANIZATION
"IETF Common Control And Measurement Plane (CCAMP) Working Group" "IETF Common Control And Measurement Plane (CCAMP) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
skipping to change at page 3, line 51 skipping to change at page 3, line 49
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2006). This version of "Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC XXX; see the RFC itself for this MIB module is part of RFC XXX; see the RFC itself for
full legal notices. full legal notices.
-- RFC Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
This MIB module defines TEXTUAL-CONVENTIONs for concepts used in This MIB module defines TEXTUAL-CONVENTIONs for concepts used in
Generalized Multiprotocol Label Switching (GMPLS) networks." Generalized Multiprotocol Label Switching (GMPLS) networks."
REVISION REVISION
"200604060001Z" -- 06 April 2006 00:00:01 GMT "200609060001Z" -- 06 September 2006 00:00:01 GMT
DESCRIPTION DESCRIPTION
-- RFC Editor: Please see the IANA Considerations Section.
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006
-- This MIB module is contained in the OID sub-tree
-- rooted at mplsStdMIB.
"Initial version published as part of RFC XXX." "Initial version published as part of RFC XXX."
::= { mplsStdMIB XXX } ::= { mplsStdMIB YYY }
-- RFC Editor. Please replace XXX above with the correct RFC number and -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note. -- remove this note.
-- RFC Editor. Please replace YYY above with the OID assigned by IANA -- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note -- and remove this note
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
GmplsFreeformLabelTC ::= TEXTUAL-CONVENTION GmplsFreeformLabelTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This Textual Convention can be used as the syntax of an object "This Textual Convention can be used as the syntax of an object
that contains any GMPLS label. Objects with this syntax can be that contains any GMPLS label. Objects with this syntax can be
used to represent labels that have label types that are not used to represent labels that have label types that are not
defined in any RFCs. The freeform GMPLS Label may also be used defined in any RFCs. The freeform GMPLS Label may also be used
by systems that do not wish to represent labels that have by systems that do not wish to represent labels that have
label types defined in RFCs using type-specific syntaxes." label types defined in RFCs using type-specific syntaxes."
skipping to change at page 5, line 5 skipping to change at page 4, line 43
label as defined in RFC 3471. label as defined in RFC 3471.
gmplsFreeformLabel(3) - The label is any form of label gmplsFreeformLabel(3) - The label is any form of label
encoded as an OCTET STRING using encoded as an OCTET STRING using
the Textual Convention the Textual Convention
GmplsFreeformLabel. GmplsFreeformLabel.
gmplsSonetLabel(4) - The label is a SONET label as gmplsSonetLabel(4) - The label is a SONET label as
defined in RFC 3946. defined in RFC 3946.
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006
gmplsSdhLabel(5) - The label is an SDH label as gmplsSdhLabel(5) - The label is an SDH label as
defined in RFC 3946. defined in RFC 3946.
gmplsWavebandLabel(6) - The label is a waveband label as gmplsWavebandLabel(6) - The label is a waveband label as
defined in RFC 3471." defined in RFC 3471."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3. Functional Description, RFC 3471, section 3.
2. Definition of Textual Conventions and for Multiprotocol Label 2. Definition of Textual Conventions and for Multiprotocol Label
Switching (MPLS) Management, RFC 3811, section 3. Switching (MPLS) Management, RFC 3811, section 3.
3. Generalized Multi-Protocol Label Switching (GMPLS) Extensions 3. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 3946, section 3." Digital Hierarchy (SDH) Control, RFC 3946, section 3."
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
SYNTAX INTEGER { SYNTAX INTEGER {
gmplsMplsLabel(1), gmplsMplsLabel(1),
gmplsPortWavelengthLabel(2), gmplsPortWavelengthLabel(2),
gmplsFreeformGeneralizedLabel(3), gmplsFreeformGeneralizedLabel(3),
gmplsSonetLabel(4), gmplsSonetLabel(4),
gmplsSdhLabel(5), gmplsSdhLabel(5),
gmplsWavebandLabel(6) gmplsWavebandLabel(6)
} }
GmplsSegmentDirectionTC ::= TEXTUAL-CONVENTION GmplsSegmentDirectionTC ::= TEXTUAL-CONVENTION
skipping to change at page 5, line 43 skipping to change at page 5, line 29
head of the LSP. head of the LSP.
Where an LSP is signaled using a conventional signaling Where an LSP is signaled using a conventional signaling
protocol, the 'head' of the LSP is the source of the signaling protocol, the 'head' of the LSP is the source of the signaling
(also known as the ingress) and the 'tail' is the destination (also known as the ingress) and the 'tail' is the destination
(also known as the egress). For unidirectional LSPs, this (also known as the egress). For unidirectional LSPs, this
usually matches the direction of flow of data. usually matches the direction of flow of data.
For manually configured unidirectional LSPs the direction of the For manually configured unidirectional LSPs the direction of the
LSP segment matches the direction of flow of data. For manually LSP segment matches the direction of flow of data. For manually
configured bidirecitonal LSPs, an arbitrary decision must be configured bidirectional LSPs, an arbitrary decision must be
made about which LER is the 'head'." made about which LER is the 'head'."
SYNTAX INTEGER { SYNTAX INTEGER {
forward(1), -- data flows from head-end of LSP toward tail-end forward(1), -- data flows from head-end of LSP toward tail-end
reverse(2) -- data flows from tail-end of LSP toward head-end reverse(2) -- data flows from tail-end of LSP toward head-end
} }
END END
4. Security Considerations 4. Security Considerations
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other GMPLS defines a set of textual conventions which may be used by other GMPLS
MIB modules to define management objects. MIB modules to define management objects.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document has modules that define management objects. Therefore, this document has
no impact on the security of the Internet. no impact on the security of the Internet.
5. IANA Considerations draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
5. IANA Considerations
IANA is requested to root MIB objects in this MIB module under the IANA is requested to root MIB objects in this MIB module under the
mplsStdMIB subtree by assigning an OID to gmplsTCStdMIB currently mplsStdMIB subtree by assigning an OID to gmplsTCStdMIB.
indicated by { mplsStdMIB YYY }.
Upon approval of this document, the IANA will make the following
assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located
at http://www.iana.org/assignments/smi-numbers
In table ...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
Decimal Name References
------- ----- ----------
TBD GMPLS-TC-STD-MIB [RFC-ccamp-gmpls-tc-mib]
-- RFC Editor. Please replace YYY in the main text with the OID assigned
-- by IANA and remove this note.
In the future, GMPLS related standards track MIB modules should be In the future, GMPLS related standards track MIB modules should be
rooted under the mplsStdMIB (sic) subtree. IANA has been requested to rooted under the mplsStdMIB (sic) subtree. IANA has been requested to
manage that namespace in the SMI Numbers registry [RFC3811]. New manage that namespace in the SMI Numbers registry [RFC3811]. New
assignments can only be made via a Standards Action as specified in assignments can only be made via a Standards Action as specified in
[RFC2434]. [RFC2434].
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance Statements J., Rose, M., and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999. for SMIv2", STD 58, RFC 2580, April 1999.
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions and for Multiprotocol Label Switching (MPLS)
Management", RFC 3811, June 2004. Management", RFC 3811, June 2004.
[RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi- [RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi-
Protocol Label Switching (GMPLS) Extensions for Protocol Label Switching (GMPLS) Extensions for
skipping to change at page 7, line 41 skipping to change at page 7, line 37
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Switching (GMPLS) Architecture", RFC 3945, October 2004. Switching (GMPLS) Architecture", RFC 3945, October 2004.
7. Acknowledgements 7. Acknowledgements
This document is a product of the CCAMP Working Group. This document is a product of the CCAMP Working Group.
Special thanks to Joan Cucchiara for her help with compilation Special thanks to Joan Cucchiara for her help with compilation
issues and her very thorough MIB Doctor review. Thanks also to issues and her very thorough MIB Doctor review. Thanks also to
Bert Wijnen, David Harrington and Harrie Hazewinkel for their review Lars Eggert, David Harrington, Harrie Hazewinkel, Dan Romascanu, and
comments. Bert Wijnen for their review comments.
8. Contact Information 8. Contact Information
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
1414 Massachusetts Ave. 1414 Massachusetts Ave.
Boxborough, MA 01719 Boxborough, MA 01719
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Phone: +44 1978 860944 Phone: +44 1978 860944
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
Cheenu Srinivasan Cheenu Srinivasan
Bloomberg L.P. Bloomberg L.P.
731 Lexington Ave. 731 Lexington Ave.
New York, NY 10022 New York, NY 10022
Phone: +1-212-617-3682 Phone: +1-212-617-3682
Email: cheenu@bloomberg.net Email: cheenu@bloomberg.net
Tim Hall Tim Hall
Data Connection Ltd. Data Connection Ltd.
skipping to change at page 9, line 5 skipping to change at page 9, line 5
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
draft-ietf-ccamp-gmpls-tc-mib-10.txt April 11, 2006 draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
10. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
 End of changes. 30 change blocks. 
35 lines changed or deleted 43 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/