draft-ietf-mpls-lc-if-mib-03.txt   draft-ietf-mpls-lc-if-mib-04.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde Internet Draft Subrahmanya Hegde
Expires: February 2005 Cisco Systems, Inc. Expires: April 2005 Cisco Systems, Inc.
August 2004 October 2004
Multiprotocol Label Switching (MPLS) Label-Controlled ATM Multiprotocol Label Switching (MPLS) Label-Controlled ATM
and Frame-Relay Management Interface Definition and Frame-Relay Management Interface Definition
draft-ietf-mpls-lc-if-mib-03.txt draft-ietf-mpls-lc-if-mib-04.txt
Status of this Memo Status of this Memo
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 a "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed, or
will be disclosed, and any of which I become aware will be disclosed,
in accordance with RFC 3668.
Abstract Abstract
This memo defines two MIB modules and corresponding MIB Object This memo defines two MIB modules and corresponding MIB Object
Definitions that describe how label switching controlled Definitions that describe how label switching controlled
Frame-Relay and ATM interfaces can be managed given the Frame-Relay and ATM interfaces can be managed given the
interface stacking as defined in the MPLS-LSR-STD-MIB and interface stacking as defined in the MPLS-LSR-STD-MIB and
MPLS-TE-STD-MIB. MPLS-TE-STD-MIB.
Table of Contents Table of Contents
1. Introduction .............................................. 3 1. Introduction .............................................. 3
2. Terminology ............................................... 3 2. Terminology ............................................... 3
3. The SNMP Management Framework ............................. 3 3. The SNMP Management Framework ............................. 3
4. Interface Stacking of LC-ATM and LC-FR .................... 5 4. Interface Stacking of LC-ATM and LC-FR .................... 5
5. MPLS Label Controlled ATM MIB Definitions ................. 13 5. MPLS Label Controlled ATM MIB Definitions ................. 13
6. MPLS Label Controlled Frame Relay MIB Definitions ......... 13 6. MPLS Label Controlled Frame Relay MIB Definitions ......... 13
7. Security Considerations ................................... 51 7. Security Considerations ................................... 51
8. References ................................................ 52 8. References ................................................ 52
9.1 Normative References...................................... 52 10. Authors' Addresses ........................................ 54
9.2 Informative References.................................... 52 11. Copyright Notice........................................... 55
10. Authors' Addresses ....................................... 54 12. Full Copyright Statement................................... 55
11. Full Copyright Statement ................................. 55 13. Intellectual Property...................................... 55
12. Intellectual Property Notice ............................ 52 14. IANA Considerations........................................ 55
13. IANA Considerations ..................................... 52
14.1. IANA Considerations for MPLS-LC-ATM-STD-MIB ............... 52
14.2. IANA Considerations for MPLS-LC-FR-STD-MIB ................ 52
15 Acknowledgments............................................ 52 15 Acknowledgments............................................ 52
1. Introduction 1. Introduction
This memo defines how label switching controlled Frame-Relay This memo defines how label switching controlled Frame-Relay
[RFC3034] and ATM [RFC3035] interfaces can be realized given [RFC3034] and ATM [RFC3035] interfaces can be realized given
the interface stacking as defined in the MPLS-LSR-STD [LSRMIB] the interface stacking as defined in the MPLS-LSR-STD [LSRMIB]
and MPLS-TE-STD [TEMIB] MIBs. This document also contains a and MPLS-TE-STD [TEMIB] MIBs. This document also contains a
MIB module that sparsely augments the MPLS-LSR-STD MIB's MIB module that sparsely augments the MPLS-LSR-STD MIB's
mplsInterfaceConfTable in such a way as to identify which mplsInterfaceConfTable in such a way as to identify which
skipping to change at page 3, line 33 skipping to change at page 3, line 46
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, StorageType, TruthValue RowStatus, StorageType, TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
AtmVpIdentifier AtmVpIdentifier
FROM ATM-TC-MIB -- RFC2514 FROM ATM-TC-MIB -- RFC2514
mplsStdMIB, MplsAtmVcIdentifier mplsStdMIB, MplsAtmVcIdentifier
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- RFC3811
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB -- RFC3813
; ;
mplsLcAtmStdMIB MODULE-IDENTITY mplsLcAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200405011200Z" -- 01 May 2004 12:00:00 GMT LAST-UPDATED "200410121200Z" -- 12 October 2004 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
250 Apollo Drive 250 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Tel: +1-978-244-3051 Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Subrahmanya Hegde Subrahmanya Hegde
skipping to change at page 4, line 18 skipping to change at page 4, line 31
MPLS Label Controlled ATM interfaces as defined in MPLS Label Controlled ATM interfaces as defined in
RFC3035. RFC3035.
Copyright (C) The Internet Society (2004). This Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX -- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200405011200Z" -- 01 May 2004 12:00:00 GMT "200410121200Z" -- 12 October 2004 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC XXXX."
::= { mplsStdMIB 999 } -- To Be Assigned by IANA ::= { mplsStdMIB XXX } -- To Be Assigned by IANA
-- Top level components of this MIB. -- Top level components of this MIB.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 } mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 }
mplsLcAtmStdObjects OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 1 } mplsLcAtmStdObjects OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 1 }
mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 } mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 }
skipping to change at page 6, line 31 skipping to change at page 6, line 44
DEFVAL { false } DEFVAL { false }
::= { mplsLcAtmStdInterfaceConfEntry 5 } ::= { mplsLcAtmStdInterfaceConfEntry 5 }
mplsLcAtmVcDirectlyConnected OBJECT-TYPE mplsLcAtmVcDirectlyConnected OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value indicates whether an LC-ATM is directly "This value indicates whether an LC-ATM is directly
or indirectly (by means of a VP) connected. If set to or indirectly (by means of a VP) connected. If set to
true(0), indicates that this interface is directly true(1), indicates that this interface is directly
connected LC-ATM, otherwise it MUST be set to connected LC-ATM, otherwise it MUST be set to
false(1)." false(2)."
DEFVAL { true } DEFVAL { true }
::= { mplsLcAtmStdInterfaceConfEntry 6 } ::= { mplsLcAtmStdInterfaceConfEntry 6 }
mplsLcAtmLcAtmVPI OBJECT-TYPE mplsLcAtmLcAtmVPI OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VPI value used for indirectly "This is the VPI value used for indirectly
connected LC-ATM interfaces For indirectly connected LC-ATM interfaces. For these
connected interfaces, the VPI field is not interfaces, the VPI field is not
available to MPLS, and the label MUST be available to MPLS, and the label MUST be
encoded entirely within the VCI field. encoded entirely within the VCI field.
(see RFC 3035). If the interface is directly (see RFC 3035). If the interface is directly
connected, this value MUST be set to zero." connected, this value MUST be set to zero."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsLcAtmStdInterfaceConfEntry 7 } ::= { mplsLcAtmStdInterfaceConfEntry 7 }
mplsLcAtmStdIfConfRowStatus OBJECT-TYPE mplsLcAtmStdIfConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 8, line 50 skipping to change at page 9, line 14
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdVcMerge OBJECT mplsLcAtmStdVcMerge
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdIfConfRowStatus OBJECT mplsLcAtmStdIfConfRowStatus
MIN-ACCESS read-only SYNTAX RowStatus { active(1), notInService(2) }
DESCRIPTION WRITE-SYNTAX RowStatus { active(1), notInService(2),
"Write access is not required." createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
OBJECT mplsLcAtmVcDirectlyConnected OBJECT mplsLcAtmVcDirectlyConnected
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmLcAtmVPI OBJECT mplsLcAtmLcAtmVPI
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 10, line 5 skipping to change at page 10, line 20
MPLS-LC-FR-STD-MIB DEFINITIONS ::= BEGIN MPLS-LC-FR-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
RowStatus, StorageType RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB -- RFC3813
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB -- RFC2115 FROM FRAME-RELAY-DTE-MIB -- RFC2115
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB -- RFC3811
; ;
mplsLcFrStdMIB MODULE-IDENTITY mplsLcFrStdMIB MODULE-IDENTITY
LAST-UPDATED "200405011200Z" -- 01 May 2004 12:00:00 GMT LAST-UPDATED "200405011200Z" -- 01 May 2004 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) 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
Subrahmanya Hegde Subrahmanya Hegde
skipping to change at page 12, line 32 skipping to change at page 12, line 47
on this interface." on this interface."
::= { mplsLcFrStdInterfaceConfEntry 4 } ::= { mplsLcFrStdInterfaceConfEntry 4 }
mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is object is used to create and "This is object is used to create and
delete entries in this table. When configuring delete entries in this table. When configuring
entries in this table, the corresponding entries in this table, the corresponding ifEntry and
corresponding ifEntry and mplsInterfaceConfEntry mplsInterfaceConfEntry MUST exist before hand. If an entry
MUST exist before hand. If an entry is attempted is attempted to be created by a manager for a corresponding
to be created by a manager for a corresponding
mplsInterfaceConfEntry that does not support LC-FR, mplsInterfaceConfEntry that does not support LC-FR,
the agent MUST return an inconsistentValue error. the agent MUST return an inconsistentValue error.
If this table is implemented read-only, then the If this table is implemented read-only, then the
agent must set this object to active(1) when this agent must set this object to active(1) when this
row is made active. If this table is implemented row is made active. If this table is implemented
writable, then an agent MUST not allow modification writable, then an agent MUST not allow modification
to its objects once this value is set to active(1)." to its objects once this value is set to active(1)."
::= { mplsLcFrStdInterfaceConfEntry 5 } ::= { mplsLcFrStdInterfaceConfEntry 5 }
mplsLcFrStdInterfaceConfStoreType OBJECT-TYPE mplsLcFrStdInterfaceConfStoreType OBJECT-TYPE
skipping to change at page 14, line 23 skipping to change at page 14, line 38
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdCtrlMaxDlci OBJECT mplsLcFrStdCtrlMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdInterfaceConfRowStatus OBJECT mplsLcFrStdInterfaceConfRowStatus
MIN-ACCESS read-only SYNTAX RowStatus { active(1), notInService(2) }
DESCRIPTION WRITE-SYNTAX RowStatus { active(1), notInService(2),
"Write access is not required." createAndGo(4), destroy(6)
}
DESCRIPTION "Support for createAndWait and notReady is
not required."
OBJECT mplsLcFrStdInterfaceConfStoreType OBJECT mplsLcFrStdInterfaceConfStoreType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLcFrStdCompliances 2 } ::= { mplsLcFrStdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLcFrStdIfGroup OBJECT-GROUP mplsLcFrStdIfGroup OBJECT-GROUP
skipping to change at page 15, line 20 skipping to change at page 15, line 38
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the MplsLcAtmStdInterfaceConfTable and o the MplsLcAtmStdInterfaceConfTable and
mplsLcFrStdInterfaceConfTable collectively mplsLcFrStdInterfaceConfTable collectively
contain objects which may be used to provision MPLS LC or FR-enabled contain objects which may be used to provision MPLS LC or
interfaces. Unauthorized access to objects in these tables, FR-enabled interfaces. Unauthorized access to objects in
could result in disruption of traffic on the network. This is these tables, could result in disruption of traffic on the
especially true if traffic has been established over these network. This is especially true if traffic has been
interfaces. The use of stronger mechanisms such as SNMPv3 established over these interfaces. The use of stronger
security should be considered where possible. Specifically, mechanisms such as SNMPv3 security should be considered
SNMPv3 VACM and USM MUST be used with any v3 agent which where possible. Specifically,SNMPv3 VACM and USM MUST be
implements this MIB module. Administrators should consider used with any v3 agent which implements this MIB module.
whether read access to these objects should be allowed, Administrators should consider whether read access to
since read access may be undesirable under certain these objects should be allowed, since read access may be
circumstances. undesirable under certain circumstances.
Some of the readable objects in this MIB module "i.e., objects with a Some of the readable objects in this MIB module "i.e., objects with a
MAX-ACCESS other than not-accessible" may be considered sensitive or MAX-ACCESS other than not-accessible" may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the MplsLcAtmStdInterfaceConfTable and o the MplsLcAtmStdInterfaceConfTable and
skipping to change at page 16, line 23 skipping to change at page 16, line 41
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access instance of this MIB module, is properly configured to give access
to the objects only to those principals "users" that have legitimate to the objects only to those principals "users" that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET "change/create/delete" them.
9. References 9. References
9.1 Normative References 9.1 Normative References
[RFC2115] [RFC2115] Brown, C., Baker, F., "Management Information Base
for Frame Relay DTEs Using SMIv2", RFC2115, September
[RFC2514] 1997.
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, 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., Case, [RFC2514] Noto, M., Spiegel, E., Tesink, K., et al., "Definitions
J., Rose, M., and S. Waldbusser, "Conformance of Textual Conventions and OBJECT-IDENTITIES for ATM
Statements for SMIv2", STD 58, RFC 2580, April 1999. Management", RFC2514, February 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, [RFC3031] Rosen, E., Viswanathan, A., and R. Callon,
"Multiprotocol Label Switching Architecture", RFC "Multiprotocol Label Switching Architecture", RFC
3031, January 2001. 3031, January 2001.
[TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS [TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS
Traffic Engineering Management Information Base ", Traffic Engineering Management Information Base ",
skipping to change at page 17, line 17 skipping to change at page 17, line 22
(MPLS) Label Switch Router Management (MPLS) Label Switch Router Management
Information Base ", RFC3813, June 2004. Information Base ", RFC3813, June 2004.
[TCMIB] Nadeau, T., Cucchiara, J., Editors, [TCMIB] Nadeau, T., Cucchiara, J., Editors,
"Definition of Textual Conventions and OBJECT- "Definition of Textual Conventions and OBJECT-
IDENTITIES for Multi-Protocol Label Switching (MPLS) IDENTITIES for Multi-Protocol Label Switching (MPLS)
Management", RFC3811, June 2004. Management", RFC3811, June 2004.
9.2 Informative References 9.2 Informative References
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, 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., Case,
J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[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.
[LDPMIB] J. Cucchiara, et al., "Definitions of [LDPMIB] J. Cucchiara, et al., "Definitions of
Managed Objects for the Multiprotocol Label Managed Objects for the Multiprotocol Label
Switching, Label Distribution Protocol Switching, Label Distribution Protocol
(LDP)", <draft-ietf-mpls-ldp-mib-14.txt>, (LDP)", <draft-ietf-mpls-ldp-mib-14.txt>,
November 2003. November 2003.
10. Authors' Addresses 10. Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau Subrahmanya Hegde
Cisco Systems, Inc. Cisco Systems, Inc. Cisco Systems, Inc.
300 Beaver Brook Road
Boxboro, MA 01719
Phone: +1-978-936-1470
Email: tnadeau@cisco.com
Subrahmanya Hegde 300 Beaver Brook Road 225 East Tazman Drive
Cisco Systems, Inc. Boxboro, MA 01719 San Jose, CA
225 East Tazman Drive Phone: +1-978-936-1470 Phone: +1-408-525-6562
San Jose, CA Email: tnadeau@cisco.com Email: subrah@cisco.com
Phone: +1-408-525-6562
Email: subrah@cisco.com
11. Full Copyright Statement 11. Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished 12. Full Copyright Statement
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 Copyright (C) The Internet Society (2004). This document is subject
be revoked by the Internet Society or its successors or assigns. to the rights, licenses and restrictions contained in BCP 78 and
This document and the information contained herein is provided on except as set forth therein, the authors retain all their rights.
an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR This document and the information contained herein are provided on an
IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 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. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
12. Intellectual Property Notice 13. 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 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; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11 [RFC2028]. found in BCP 78 and BCP 79.
Copies of claims of rights made available for publication 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 implementors or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF Secretariat. specification can be obtained from the IETF on-line IPR repository at
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 practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at ietf-
Director. ipr@ietf.org.
13. IANA Considerations
14. IANA Considerations
As described in and as requested in the MPLS-TC-STD-MIB As described in and as requested in the MPLS-TC-STD-MIB
[TCMIB], MPLS related standards track MIB modules should be [TCMIB], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 2 MPLS MIB Modules rooted under the mplsStdMIB subtree. There are 2 MPLS MIB Modules
contained in this document, each of the following "IANA contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under Considerations" subsections requests IANA for a new assignment under
the mplsStdMIB subtree. New assignments can only be made via a the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434]. Standards Action as specified in [RFC2434].
14.1. IANA Considerations for MPLS-LC-ATM-STD-MIB 14.1. IANA Considerations for MPLS-LC-ATM-STD-MIB
The IANA is requested to assign { mplsStdMIB 9 } to the The IANA is requested to assign { mplsStdMIB 9 } to the
MPLS-LC-ATM-STD-MIB module specified in this document. MPLS-LC-ATM-STD-MIB module specified in this document.
14.2. IANA Considerations for MPLS-LC-FR-STD-MIB 14.2. IANA Considerations for MPLS-LC-FR-STD-MIB
The IANA is requested to assign { mplsStdMIB 10 } to the The IANA is requested to assign { mplsStdMIB 10 } to the
MPLS-LC-FR-STD-MIB module specified in this document. MPLS-LC-FR-STD-MIB module specified in this document.
15. Acknowledgments 15. Acknowledgments
We wish to thank Joan Cucchiara for her comments on We wish to thank Joan Cucchiara and Carlos Pignataro for
this document. their comments on this document.
 End of changes. 

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