draft-ietf-ccamp-gmpls-tc-mib-05.txt   draft-ietf-ccamp-gmpls-tc-mib-06.txt 
Network Working Group Thomas D. Nadeau 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: December 2004 Cheenu Srinivasan Expires: April 2005 Adrian Farrel, Ed.
Bloomberg L.P.
Adrian Farrel
Old Dog Consulting Old Dog Consulting
Tim Hall October 2004
Ed Harrison
Data Connection Ltd.
June 2004
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-05.txt draft-ietf-ccamp-gmpls-tc-mib-06.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC 2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
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.
Table of Contents Table of Contents
1. Introduction 2 1. Introduction ................................... 2
2. The SNMP Management Framework 2 2. The SNMP Management Framework .................. 2
3. GMPLS Textual Conventions MIB Definitions 3 3. GMPLS Textual Conventions MIB Definitions ...... 3
4. Security Considerations 5 4. Security Considerations ........................ 5
5. IANA Considerations 5 5. IANA Considerations ............................ 5
6. References 5 6. References ..................................... 5
6.1. Normative References 5 6.1. Normative References ......................... 5
6.2. Informational References 6 6.2. Informational References ..................... 6
7. Acknowledgments 7 7. Acknowledgments ................................ 7
8. Authors' Addresses 7 8. Authors' Addresses ............................. 7
9. Intellectual Property Notice 7 9. Intellectual Property Notice ................... 9
9.1. IPR Disclosure Acknowledgement 8 10. Full Copyright Statement ..................... 10
10. Full Copyright Statement 8
1. Introduction 1. Introduction
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. for Generalized Multiprotocol Label Switching (GMPLS) networks.
These Textual Conventions should be imported by MIB modules which These Textual Conventions should be imported by MIB modules which
manage GMPLS networks. manage GMPLS networks.
This MIB module supplements the MIB module in [TCMIB] 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. [TCMIB] 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.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Comments should be made directly to the CCAMP mailing list at Comments should be made directly to the CCAMP mailing list at
ccamp@ops.ietf.org. ccamp@ops.ietf.org.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119,
reference [RFC2119].
For an introduction to the concepts of GMPLS, see [GMPLSArch]. For an introduction to the concepts of GMPLS, see [GMPLSArch].
2. The SNMP 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,
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].
3. GMPLS Textual Conventions MIB Definitions 3. GMPLS Textual Conventions MIB Definitions
GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY MODULE-IDENTITY
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
transmission
FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC -- [RFC2579]
mplsStdMIB
FROM MPLS-TC-STD-MIB -- [RFC3811]
; ;
gmplsTCStdMIB MODULE-IDENTITY gmplsTCStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200406010900Z" -- 1 June 2004 9:00:00 GMT" "200410080001Z" -- 8 October 2004 00:00:01 GMT
ORGANIZATION "Common Control And Management Protocols (CCAMP) ORGANIZATION "Common Control And Measurement Plane (CCAMP)
Working Group" 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
Cheenu Srinivasan
Bloomberg L.P.
Email: cheenu@bloomberg.net
Adrian Farrel Adrian Farrel
Old Dog Consulting Old Dog Consulting
Email: adrian@olddog.co.uk Email: adrian@olddog.co.uk
Ed Harrison
Data Connection Ltd.
Email: ed.harrison@dataconnection.com
Tim Hall
Data Connection Ltd.
Email: tim.hall@dataconnection.com
Comments about this document should be emailed direct to the Comments about this document should be emailed direct to the
CCAMP working group mailing list at ccamp@ops.ietf.org" CCAMP working group mailing list at ccamp@ops.ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The Internet Society (2004). This version of this "Copyright (C) The Internet Society (2004). The
MIB module is part of RFCXXX; see the RFC itself for full legal initial version of this MIB module was published
notices. in RFC xxxx. For full legal notices see the RFC
itself or see:
http://www.ietf.org/copyrights/ianamib.html
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 history. -- Revision history.
REVISION REVISION
"200406010900Z" -- 1 June 2004 9:00:00 GMT" "200410080001Z" -- 8 October 2004 00:00:01 GMT
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXXX." "Initial version published as part of RFC XXXX."
-- Please see the IANA Considerations Section. -- Please see the IANA Considerations Section.
-- The requested gmplsStdMIB subId is xx, i.e. -- This MIB module is contained in the OID sub-tree
::= { gmplsStdMIB xx } -- rooted at mplsStdMIB.
gmplsStdMIB OBJECT IDENTIFIER -- The requested mplsStdMIB subId is xx, i.e.
-- This object identifier needs to be assigned by IANA. ::= { mplsStdMIB xx }
-- Since mpls has been assigned an ifType of 166 we recommend
-- that this OID be 166 as well, i.e.
::= { transmission XXX }
-- Textual Conventions (sorted alphabetically). -- Textual Conventions (sorted alphabetically).
GmplsFreeformLabel ::= TEXTUAL-CONVENTION GmplsFreeformLabel ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents a freeform generalized MPLS Label. This "This value represents a freeform generalized MPLS Label. This
can be used to represent label types which are not standard can be used to represent label types which are not standard
in the drafts. It may also be used by systems that do not in the drafts. It may also be used by systems that do not
wish to represent the labels using the specific label types." wish to represent the labels using the specific label types."
REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471."
SYNTAX OCTET STRING (SIZE (0..64)) SYNTAX OCTET STRING (SIZE (0..64))
GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Determines the interpretation that should be applied to a "Determines the interpretation that should be applied to a
label." label."
REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471."
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)
} }
GmplsSegmentDirection ::= TEXTUAL-CONVENTION GmplsSegmentDirection ::= TEXTUAL-CONVENTION
skipping to change at page 5, line 8 skipping to change at page 5, line 14
SYNTAX INTEGER { SYNTAX INTEGER {
forward(1), forward(1),
reverse(2) reverse(2)
} }
END END
4. Security Considerations 4. Security Considerations
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 MPLS
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 5. IANA Considerations
IANA is requested to make a MIB OID assignment under the transmission IANA is requested to root MIB objects in this MIB module
branch, that is, assign the gmplsStdMIB under { transmission 166 }. under the mplsStdMIB subtree by assigning an OID to
gmplsTCStdMIB.
This sub-id is requested because 166 is the ifType for mpls(166) and
is available under transmission.
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 is requested to rooted under the mplsStdMIB (sic) subtree. IANA has been requested
manage that namespace. New assignments can only be made via a to manage that namespace. New assignments can only be made via a
Standards Action as specified in [RFC2434]. Standards Action as specified in [RFC2434].
This document also requests IANA to assign { gmplsStdMIB xx } to the The IANA has assigned { mplsStdMIB 1 } to the MPLS-TC-STD-MIB.
GMPLS-TC-STD-MIB specified in this document. The value 1 is
suggested.
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
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J.,
Case, J., Rose, M. and S. Waldbusser, "Structure of Case, J., Rose, M. and S. Waldbusser, "Structure of
skipping to change at page 6, line 27 skipping to change at page 6, line 31
RSVP for LSP Tunnels", RFC 3209, December 2001. RSVP for LSP Tunnels", RFC 3209, December 2001.
[RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based [RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based
LSP Setup using LDP", RFC 3212, January 2002. LSP Setup using LDP", RFC 3212, January 2002.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network
Management Protocol (SNMP) Management Frameworks",
STD 62, RFC 3411, December 2002.
[RFC3472] Ashwood-Smith, P., Berger, L. (Editors), [RFC3472] Ashwood-Smith, P., Berger, L. (Editors),
"Generalized MPLS Signaling - CR-LDP Extensions", "Generalized MPLS Signaling - CR-LDP Extensions",
RFC 3472, January 2003. RFC 3472, January 2003.
[RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
RSVP-TE Extensions", RFC 3473 January 2003. RSVP-TE Extensions", RFC 3473 January 2003.
[RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Conventions and for Multiprotocol Label Switching
(MPLS) Management", RFC 3811, June 2004.
[GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors),
"Generalized Multi-Protocol Label Switching "Generalized Multi-Protocol Label Switching
Extensions for SONET and SDH Control", Internet Extensions for SONET and SDH Control", Internet
Draft <draft-ietf-ccamp-gmpls-sonet-sdh-08.txt>, Draft <draft-ietf-ccamp-gmpls-sonet-sdh-08.txt>,
February 2003, work in progress. February 2003, work in progress.
[GMPLSLSRMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., [GMPLSLSRMIB] Nadeau, T., Farrel, A. (Editors) "Generalized
and Harrison, E., "Generalized Multiprotocol Label Multiprotocol Label Switching (GMPLS) Label
Switching (GMPLS) Label Switching Router (LSR) Switching Router (LSR) Management Information Base",
Management Information Base", draft-ietf-ccamp- draft-ietf-ccamp-gmpls-lsr-mib-06.txt, October 2004,
gmpls-lsr-mib-05.txt, June 2004, work in progress. work in progress.
[GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T.,
and Harrison, E., "Generalized Multiprotocol Label
Switching (GMPLS) Traffic Engineering Management
Information Base", draft-ietf-ccamp-gmpls-te-mib-
05.txt, June 2004, work in progress.
[TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions [GMPLSTEMIB] Nadeau, T., Farrel, A. (Editors) "Generalized
of Textual Conventions for Multiprotocol Label Multiprotocol Label Switching (GMPLS) Traffic
Switching (MPLS) Management", Internet Draft Engineering Management Information Base",
<draft-ietf-mpls-tc-mib-14.txt>, November 2003, draft-ietf-ccamp-gmpls-te-mib-06.txt, October 2004,
work in progress. work in progress.
[GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol
Label Switching (GMPLS) Architecture", Internet Label Switching (GMPLS) Architecture", Internet
Draft <draft-many-gmpls-architecture-07.txt>, May Draft <draft-many-gmpls-architecture-07.txt>, May
2003, work in progress. 2003, work in progress.
7. Acknowledgements 7. Acknowledgements
This draft is the work of the five authors listed in the next
section.
Special thanks to Joan Cucchiara for her help with compilation Special thanks to Joan Cucchiara for her help with compilation
issues. issues.
8. Authors' Addresses 8. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
skipping to change at page 8, line 17 skipping to change at page 8, line 43
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
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 this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
9.1. IPR Disclosure Acknowledgement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
10. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2004). 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. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/