draft-ietf-ccamp-gmpls-tc-mib-11.txt   rfc4801.txt 
Network Working Group Thomas D. Nadeau, Ed. Network Working Group T. Nadeau, Ed.
Internet Draft Cisco Systems, Inc. Request for Comment: 4801 Cisco Systems, Inc.
Proposed Status: Standards Track Category: Standards Track A. Farrel, Ed.
Expires: March 2007 Adrian Farrel, Ed.
Old Dog Consulting Old Dog Consulting
February 2007
September 2006 Definitions of Textual Conventions for
Generalized Multiprotocol Label Switching (GMPLS) Management
Definitions of Textual Conventions for Generalized Multiprotocol
Label Switching (GMPLS) Management
draft-ietf-ccamp-gmpls-tc-mib-11.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Status of This Memo
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 This document specifies an Internet standards track protocol for the
and may be updated, replaced, or obsoleted by other documents at any Internet community, and requests discussion and suggestions for
time. It is inappropriate to use Internet-Drafts as reference improvements. Please refer to the current edition of the "Internet
material or to cite them other than as "work in progress." Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be Copyright (C) The IETF Trust (2007).
accessed at http://www.ietf.org/shadow.html.
Abstract Abstract
This document defines a Management Information Base (MIB) module This document defines a Management Information Base (MIB) module that
which contains Textual Conventions to represent commonly used contains textual conventions (TCs) 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 will be
be imported and used in GMPLS related MIB modules that would imported and used in GMPLS-related MIB modules that would otherwise
otherwise define their own representations. define their own representations.
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
Table of Contents Table of Contents
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 ........................... 5 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
9. Intellectual Property Considerations .............. 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 that contains textual conventions
for Generalized Multiprotocol Label Switching (GMPLS) networks. These (TCs) for Generalized Multiprotocol Label Switching (GMPLS) networks.
Textual Conventions should be imported by MIB modules which manage These textual conventions should be imported by MIB modules that
GMPLS networks. manage 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
in networks that support only MPLS. module in networks that support only MPLS.
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]. [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,
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 reference to the following documents:
[RFC2578], [RFC2579], and [RFC3811]. [RFC2578], [RFC2579], [RFC3471], 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
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702280000Z" -- 28 February 2007 00:00:00 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
Comments about this document should be emailed direct to the Comments about this document should be emailed directly 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 (2006). This version of "Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC XXX; see the RFC itself for this MIB module is part of RFC 4801; see the RFC itself for
full legal notices. full legal notices.
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
"200609060001Z" -- 06 September 2006 00:00:01 GMT "200702280000Z" -- 28 February 2007 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version published as part of RFC XXX." "Initial version published as part of RFC 4801."
::= { mplsStdMIB YYY } ::= { mplsStdMIB 12 }
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."
REFERENCE REFERENCE
"1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling
Functional Description, RFC 3471, section 3.2." Functional Description, RFC 3471, section 3.2."
SYNTAX OCTET STRING (SIZE (0..64)) SYNTAX OCTET STRING (SIZE (0..64))
GmplsLabelTypeTC ::= TEXTUAL-CONVENTION GmplsLabelTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Determines the interpretation that should be applied to an "Determines the interpretation that should be applied to an
object that encodes a label. The possible types are: object that encodes a label. The possible types are:
gmplsMplsLabel(1) - The label is an MPLS packet, cell, gmplsMplsLabel(1) - The label is an MPLS Packet, Cell,
or frame label and is encoded as or Frame Label and is encoded as
described for the Textual described for the TEXTUAL-
Convention MplsLabel defined in CONVENTION MplsLabel defined in
RFC 3811. RFC 3811.
gmplsPortWavelengthLabel(2) - The label is a port or wavelength gmplsPortWavelengthLabel(2) - The label is a Port or Wavelength
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 Synchronous Optical
defined in RFC 3946. Network (SONET) Label as
defined in RFC 4606.
gmplsSdhLabel(5) - The label is an SDH label as gmplsSdhLabel(5) - The label is a Synchronous Digital
defined in RFC 3946. Hierarchy (SDH) Label as defined
in RFC 4606.
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 4606."
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
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The direction of data flow on an LSP segment with respect to the "The direction of data flow on an Label Switched Path (LSP)
head of the LSP. segment with respect to the 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
LSP segment matches the direction of flow of data. For manually the LSP segment matches the direction of flow of data. For
configured bidirectional LSPs, an arbitrary decision must be manually configured bidirectional LSPs, an arbitrary decision
made about which LER is the 'head'." must be 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
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.
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
5. IANA Considerations 5. IANA Considerations
IANA is requested to root MIB objects in this MIB module under the IANA has rooted MIB objects in this MIB module under the mplsStdMIB
mplsStdMIB subtree by assigning an OID to gmplsTCStdMIB. subtree by assigning an OID to gmplsTCStdMIB.
Upon approval of this document, the IANA will make the following IANA has made the following assignments in the "NETWORK MANAGEMENT
assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located PARAMETERS" registry located at http://www.iana.org/assignments/smi-
at http://www.iana.org/assignments/smi-numbers numbers in table:
In table ...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166) ...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
Decimal Name References Decimal Name References
------- ----- ---------- ------- ----- ----------
TBD GMPLS-TC-STD-MIB [RFC-ccamp-gmpls-tc-mib] 12 GMPLS-TC-STD-MIB [RFC4801]
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
manage that namespace in the SMI Numbers registry [RFC3811]. New to 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. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998. October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
J., Rose, M., and S. Waldbusser, "Structure of "Structure of Management Information Version 2 (SMIv2)",
Management Information Version 2 (SMIv2)", STD 58, RFC STD 58, RFC 2578, April 1999.
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, [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual
J., Rose, M., and S. Waldbusser, "Conformance Statements Conventions for SMIv2", STD 58, RFC 2579, April 1999.
for SMIv2", STD 58, RFC 2580, April 1999.
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, April
1999.
[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, "Definitions of Textual
Conventions and for Multiprotocol Label Switching (MPLS) Conventions (TCs) for Multiprotocol Label Switching (MPLS)
Management", RFC 3811, June 2004. Management", RFC 3811, June 2004.
[RFC3946] Mannie, E. and D. Papadimitriou, "Generalized Multi- [RFC4606] Mannie, E. and D. Papadimitriou, "Generalized Multi-
Protocol Label Switching (GMPLS) Extensions for Protocol Label Switching (GMPLS) Extensions for Synchronous
Synchronous Optical Network (SONET) and Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy
Digital Hierarchy (SDH) Control", RFC 3946, October (SDH) Control", RFC 4606, August 2006.
2004.
6.2. Informative References 6.2. Informative References
[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-
Internet-Standard Management Framework", RFC 3410, Standard Management Framework", RFC 3410, December 2002.
December 2002.
[RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label [RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching
Switching (GMPLS) Architecture", RFC 3945, October 2004. (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
issues and her very thorough MIB Doctor review. Thanks also to and her very thorough MIB Doctor review. Thanks also to Lars Eggert,
Lars Eggert, David Harrington, Harrie Hazewinkel, Dan Romascanu, and David Harrington, Harrie Hazewinkel, Dan Romascanu, and Bert Wijnen
Bert Wijnen for their review comments. for their review comments.
8. Contact Information 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
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.
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.
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: ed.harrison@dataconnection.com EMail: ed.harrison@dataconnection.com
9. Intellectual Property Considerations Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an 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 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 ietf- this standard. Please address the information to the IETF at
ipr@ietf.org. ietf-ipr@ietf.org.
draft-ietf-ccamp-gmpls-tc-mib-11.txt September 2006
10. Full Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject Acknowledgement
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an Funding for the RFC Editor function is currently provided by the
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS Internet Society.
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 60 change blocks. 
152 lines changed or deleted 134 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/