draft-ietf-ccamp-gmpls-tc-mib-07.txt   draft-ietf-ccamp-gmpls-tc-mib-08.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: December 2005 Adrian Farrel, Ed. Expires: April 2006 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
June 2005 October 2005
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-07.txt draft-ietf-ccamp-gmpls-tc-mib-08.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 2, line 7 skipping to change at page 2, line 7
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 Internet-Standard Management Framework ........ 2
3. GMPLS Textual Conventions MIB Definitions ...... 3 3. GMPLS Textual Conventions MIB Definitions ......... 3
4. Security Considerations ........................ 5 4. Security Considerations ........................... 6
5. IANA Considerations ............................ 5 5. IANA Considerations ............................... 6
6. References ..................................... 5 6. References ........................................ 6
6.1. Normative References ......................... 5 6.1. Normative References ............................ 6
6.2. Informational References ..................... 6 6.2. Informative References .......................... 7
7. Acknowledgments ................................ 7 7. Acknowledgements .................................. 7
8. Authors' Addresses ............................. 7 8. Contact Information ............................... 7
9. Intellectual Property Notice ................... 8 9. Intellectual Property Considerations .............. 8
10. Full Copyright Statement ...................... 8 10. Full Copyright Statement ......................... 9
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
These Textual Conventions should be imported by MIB modules which Textual Conventions should be imported by MIB modules which manage
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 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", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 3, line 7 skipping to change at page 3, line 9
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
This MIB module makes references to the following documents.
[RCF2578], [RFC2579], [RFC3471], [RFC3946] 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
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
ORGANIZATION "Common Control And Measurement Plane (CCAMP) ORGANIZATION
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
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 (2005). The initial version "Copyright (C) The Internet Society (2005). This version of
of this MIB module was published in RFC xxxx. For full legal this MIB module is part of RFC XXX; see the RFC itself for
notices see the RFC itself or see: full legal notices.
http://www.ietf.org/copyrights/ianamib.html -- RFC Editor. Please replace XXX above with the correct RFC number and
-- 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 history.
REVISION REVISION
"200505200001Z" -- 20 May 2005 00:00:01 GMT "200505200001Z" -- 20 May 2005 00:00:01 GMT
DESCRIPTION DESCRIPTION
-- RFC Editor: Please see the IANA Considerations Section. -- RFC Editor: Please see the IANA Considerations Section.
-- This MIB module is contained in the OID sub-tree -- This MIB module is contained in the OID sub-tree
-- rooted at mplsStdMIB. -- rooted at mplsStdMIB.
-- The requested mplsStdMIB subId is XXX "Initial version published as part of RFC XXX."
"Initial version published as part of RFC XXXX." ::= { mib-2 YYY }
::= { mplsStdMIB XXX } ::= { mplsStdMIB YYY }
-- Textual Conventions (sorted alphabetically). -- RFC Editor. Please replace XXX above with the correct RFC number and
-- remove this note.
-- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note
GmplsFreeformLabel ::= TEXTUAL-CONVENTION GmplsFreeformLabel ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents a freeform generalized MPLS Label. This "This Textual Convention can be used as the syntax of an object
can be used to represent label types which are not standard in that contains any GMPLS label. Objects with this syntax can be
the drafts. It may also be used by systems that do not wish to used to represent labels that have label types that are not
represent the labels using the specific label types." defined in any RFCs. The freeform GMPLS Label may also be used
by systems that do not wish to represent labels that have
label types defined in RFCs using type-specific syntaxes."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471." Functional Description, RFC 3471, section 3.2."
SYNTAX OCTET STRING (SIZE (0..64)) SYNTAX OCTET STRING (SIZE (0..64))
GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION GmplsLabelType ::= 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 an
label." object that encodes a label. The possible types are:
gmplsMplsLabel(1) - The label is an MPLS packet, cell,
or frame label and is encoded as
described for the Textual
Convention MplsLabel defined in
RFC 3811.
gmplsPortWavelengthLabel(2) - The label is a port or wavelength
label as defined in RFC 3471.
gmplsFreeformLabel(3) - The label is any form of label
encoded as an OCTET STRING using
the Textual Convention
GmplsFreeformLabel.
gmplsSonetLabel(4) - The label is a SONET label as
defined in RFC 3946.
gmplsSdhLabel(5) - The label is an SDH label as
defined in RFC 3946.
gmplsWavebandLabel(6) - The label is a waveband label as
defined in RFC 3471."
REFERENCE REFERENCE
"Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471." Functional Description, RFC 3471, section 3.
2. Definition of Textual Conventions and for Multiprotocol Label
Switching (MPLS) Management, RFC 3811, section 3.
3. Generalized Multi-Protocol Label Switching (GMPLS) Extensions
for Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control, RFC 3946, section 3."
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 4, line 51 skipping to change at page 5, line 44
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 bidirecitonal 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), forward(1), -- data flows from head-end of LSP toward tail-end
reverse(2) reverse(2) -- data flows from tail-end of LSP toward head-end
} }
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 MPLS 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 5. IANA Considerations
-- (Note to RFC-Editor:)
-- We request that you assign contiguous RFC numbers to the three GMPLS
-- MIB documents.
-- The first number to draft-ietf-ccamp-gmpls-tc-mib, the second to
-- draft-ietf-ccamp-gmpls-lsr-mib, and the third to
-- draft-ietf-ccamp-gmpls-te-mib.
-- (Please remove this note prior to publication.)
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 currently
indicated by { mplsStdMIB XXX }. indicated by { mplsStdMIB YYY }.
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 rooted under the mplsStdMIB (sic) subtree. IANA has been requested to
to manage that namespace. New assignments can only be made via a manage that namespace in the SMI Numbers registry [RFC3811]. New
Standards Action as specified in [RFC2434]. assignments can only be made via a Standards Action as specified in
[RFC2434].
The IANA has assigned { mplsStdMIB 1 } to the MPLS-TC-STD-MIB. -- RFC Editor. Please replace YYY above with the OID assigned by IANA
-- and remove this note.
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. Requirements Levels", BCP 14, RFC 2119, March 1997.
[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., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Case, J., Rose, M. and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Structure of
Statements for SMIv2", STD 58, RFC 2580, April 1999. Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Label Switching (GMPLS) Signaling Functional J., Rose, M., and S. Waldbusser, "Textual Conventions
Description", RFC 3471, January 2003. for SMIv2", STD 58, RFC 2579, April 1999.
6.2. Informational References [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
Writing an IANA Considerations Section in RFCs", (GMPLS) Signaling Functional Description", RFC 3471,
BCP: 26, RFC 2434, October 1998. January 2003.
[RFC3031] Rosen, E., Viswananthan, A., and R. Callon, [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual
Multiprotocol Label Switching Architecture", Conventions and for Multiprotocol Label Switching (MPLS)
RFC 3031, January 2001. Management", RFC 3811, June 2004.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., [RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi-
Srinivasan, V., Swallow, G., "RSVP-TE: Extensions to Protocol Label Switching (GMPLS) Extensions for
RSVP for LSP Tunnels", RFC 3209, December 2001. Synchronous Optical Network (SONET) and Synchronous
Digital Hierarchy (SDH) Control", RFC 3946, October
2004.
[RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based 6.2. Informative References
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 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label
Architecture for Describing Simple Network Switching (GMPLS) Architecture", RFC 3945, October 2004.
Management Protocol (SNMP) Management Frameworks",
STD 62, RFC 3411, December 2002.
[RFC3472] Ashwood-Smith, P., Berger, L. (Editors),
"Generalized MPLS Signaling - CR-LDP Extensions",
RFC 3472, January 2003.
[RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling -
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.
[RFC3945] Mannie, E. (Editor), "Generalized Multiprotocol
Label Switching (GMPLS) Architecture", RFC 3945,
October 2004.
[GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors),
"Generalized Multi-Protocol Label Switching
Extensions for SONET and SDH Control",
draft-ietf-ccamp-gmpls-sonet-sdh, work in progress.
[GMPLSLSRMIB] Nadeau, T., Farrel, A. (Editors) "Generalized
Multiprotocol Label Switching (GMPLS) Label
Switching Router (LSR) Management Information Base",
draft-ietf-ccamp-gmpls-lsr-mib, work in progress.
[GMPLSTEMIB] Nadeau, T., Farrel, A. (Editors) "Generalized
Multiprotocol Label Switching (GMPLS) Traffic
Engineering Management Information Base",
draft-ietf-ccamp-gmpls-te-mib, work in progress.
7. Acknowledgements 7. Acknowledgements
This draft is the work of the five authors listed in the next This document is a product of the CCAMP Working Group.
section.
Special thanks to Joan Cucchiara for her help with compilation Special thanks to Joan Cucchiara for her help with compilation
issues. issues and her very thorough MIB Doctor review. Thanks also to
Bert Wijnen, David Harrington and Harrie Hazewinkel for their review
comments.
8. Authors' Addresses 8. Contact Information
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 1414 Massachusetts Ave.
Chelmsford, MA 01824 Boxborough, MA 01719
Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Adrian Farrel
Old Dog Consulting
Phone: +44 1978 860944
Email: adrian@olddog.co.uk
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
Adrian Farrel
Old Dog Consulting
Phone: +44 1978 860944
Email: adrian@olddog.co.uk
Tim Hall Tim Hall
Data Connection Ltd. Data Connection Ltd.
100 Church Street 100 Church Street
Enfield, Middlesex Enfield, Middlesex
EN2 6BQ, UK EN2 6BQ, UK
Phone: +44 20 8366 1177 Phone: +44 20 8366 1177
Email: tim.hall@dataconnection.com Email: tim.hall@dataconnection.com
Ed Harrison Ed Harrison
Data Connection Ltd. Data Connection Ltd.
 End of changes. 38 change blocks. 
125 lines changed or deleted 132 lines changed or added

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