Network Working Group Thomas D. Nadeau Internet Draft Subrahmanya Hegde Expires: October 2004 Cisco Systems, Inc. January 2004 Multiprotocol Label Switching (MPLS) Label-Controlled ATM and Frame-Relay Management Interface Definition draft-ietf-mpls-lc-if-mib-01.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the In ternet 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 as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Table of Contents 1. Abstract .................................................. 2 2. Introduction .............................................. 3 3. Terminology ............................................... 3 4. The SNMP Management Framework ............................. 3 5. Interface Stacking of LC-ATM and LC-FR .................... 5 6. MPLS Label Controlled ATM MIB Definitions ................. 13 7. MPLS Label Controlled Frame Relay MIB Definitions ......... 13 8. Security Considerations ................................... 51 9. References ................................................ 52 9.1 Normative References...................................... 52 9.2 Informative References.................................... 52 10. Authors' Addresses ....................................... 54 11. Full Copyright Statement ................................. 55 12. Intellectual Property Notice ............................ 52 13. IANA Considerations ..................................... 52 14.1. IANA Considerations for MPLS-LC-ATM-MIB ............... 52 14.2. IANA Considerations for MPLS-LC-FR-MIB ................ 52 1. Abstract MPLS Working Group Expires July 2004 [Page 1] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 This memo defines how label switching controlled Frame-Relay and ATM interfaces can be realized given the interface stacking as defined in the MPLS-LSR and MPLS-TE MIBs. 2. Introduction This memo defines how label switching controlled Frame-Relay [RFC3034] and ATM [RFC3035] interfaces can be realized given the interface stacking as defined in the MPLS-LSR [LSRMIB] and MPLS-TE [TEMIB] MIBs. This document also contains a MIB module that extends the MPLS-LSR MIB's mplsInterfaceConfTable in such a way as to identify which MPLS-type interfaces have LC-ATM or LC-FR capabilities. Comments should be made directly to the MPLS mailing list at mpls@uu.net. This memo does not, in its draft form, specify a standard for the Internet community. 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, reference [RFC2119]. 3. Terminology This document uses terminology from the document describing the MPLS architecture [RFC3031], as well as RFC3035 and RFC3034. Specifically, the following terms will be used in this document. LC-FR RFC3034 defines a label switching controlled Frame Relay (LC-FR) interface a Frame-Relay interface controlled by the label switching control component. Packets traversing such an interface carry labels in the DLCI field LC-ATM RFC3035 defines a label switching controlled ATM (LC-ATM) interface as an ATM interface controlled by the label switching control component. When a packet traversing such an interface is received, it is treated as a labeled packet. The packet's top label is inferred either from the contents of the VCI field or the combined contents of the VPI and VCI fields. Any two LDP peers which are connected via an LC-ATM interface will use LDP negotiations to determine which of these cases is applicable to that interface. 4. The SNMP Management Framework MPLS Working Group Expires July 2004 [Page 2] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB 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 [RFC2580]. 5. Interface Stacking of LC-ATM Since LC-ATM interfaces can carry labeled MPLS traffic, they too are considered MPLS subinterfaces with ifType = mpls(166). They differ slightly in their capability from a packet-oriented MPLS interface in that they may carry ATM or Frame-Relay encapsulated traffic. It is thus beneficial to identify them as such. To identify them as such, two tables are defined which extend the MPLS-LSR MIB's mplsInterfaceConfTable (see section 7 for LC-ATM or 8 for LC-FR). 6. MPLS Label Controlled ATM MIB Definitions MPLS-LC-ATM-MIB-DRAFT-01 DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF RowStatus, StorageType, TruthValue FROM SNMPv2-TC AtmVpIdentifier FROM ATM-TC-MIB mplsStdMIB, MplsAtmVcIdentifier FROM MPLS-TC-STD-MIB mplsInterfaceIndex FROM MPLS-LSR-STD-MIB ; mplsLcAtmMIB MODULE-IDENTITY LAST-UPDATED "200401301200Z" -- 30 January 2004 12:00:00 GMT ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Thomas D. Nadeau Postal: Cisco Systems, Inc. MPLS Working Group Expires July 2004 [Page 3] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 250 Apollo Drive Chelmsford, MA 01824 Tel: +1-978-244-3051 Email: tnadeau@cisco.com Subrahmanya Hegde Postal: Cisco Systems, Inc. 225 East Tazman Drive Tel: +1-408-525-6562 Email: subrah@cisco.com General comments should be sent to mpls@uu.net " DESCRIPTION "This MIB contains managed object definitions for MPLS Label Controlled ATM interfaces as defined in RFC3035." -- Revision history. REVISION "200401301200Z" -- 30 January 2004 12:00:00 GMT DESCRIPTION "Initial revision, published as part of RFC XXXX." ::= { mplsStdMIB XXX } -- To Be Assigned by IANA, maybe 6 -- Top level components of this MIB. -- Tables, Scalars, Notifications, Conformance mplsLcAtmNotifications OBJECT IDENTIFIER ::= { mplsLcAtmMIB 0 } mplsLcAtmObjects OBJECT IDENTIFIER ::= { mplsLcAtmMIB 1 } mplsLcAtmConformance OBJECT IDENTIFIER ::= { mplsLcAtmMIB 2 } -- MPLS LC-ATM Interface Configuration Table. mplsLcAtmIfConfTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLcAtmIfConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies per-interface MPLS LC-ATM capability and associated information. In particular, this table extends the MPLS-LSR MIB's mplsInterfaceConfTable." ::= { mplsLcAtmObjects 1 } mplsLcAtmIfConfEntry OBJECT-TYPE SYNTAX MplsLcAtmIfConfEntry MAX-ACCESS not-accessible STATUS current MPLS Working Group Expires July 2004 [Page 4] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 DESCRIPTION "An entry in this table is created by an LSR for every interface capable of supporting MPLS LC-ATM. Each entry in this table will exist only if a corresponding entry in ifTable and mplsInterfaceConfTable exist. If the associated entries in ifTable and mplsInterfaceConfTable are deleted, the corresponding entry in this table must also be deleted shortly thereafter. " INDEX { mplsInterfaceIndex } ::= { mplsLcAtmIfConfTable 1 } MplsLcAtmIfConfEntry ::= SEQUENCE { mplsLcAtmCtrlVpi AtmVpIdentifier, mplsLcAtmCtrlVci MplsAtmVcIdentifier, mplsLcAtmUnlabTrafVpi AtmVpIdentifier, mplsLcAtmUnlabTrafVci MplsAtmVcIdentifier, mplsLcAtmVcMerge TruthValue, mplsLcAtmIfConfRowStatus RowStatus, mplsLcAtmIfConfStoreType StorageType } mplsLcAtmCtrlVpi OBJECT-TYPE SYNTAX AtmVpIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION "This is the VPI value over which this LSR is willing to accept control traffic on this interface." ::= { mplsLcAtmIfConfEntry 1 } mplsLcAtmCtrlVci OBJECT-TYPE SYNTAX MplsAtmVcIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION "This is the VCI value over which this LSR is willing to accept control traffic on this interface." ::= { mplsLcAtmIfConfEntry 2 } mplsLcAtmUnlabTrafVpi OBJECT-TYPE SYNTAX AtmVpIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION "This is the max VPI value over which this LSR is willing to accept unlabeled traffic on this interface." MPLS Working Group Expires July 2004 [Page 5] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 ::= { mplsLcAtmIfConfEntry 3 } mplsLcAtmUnlabTrafVci OBJECT-TYPE SYNTAX MplsAtmVcIdentifier MAX-ACCESS read-create STATUS current DESCRIPTION "This is the VCI value over which this LSR is willing to accept unlabled traffic on this interface." ::= { mplsLcAtmIfConfEntry 4 } mplsLcAtmVcMerge OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "If set to true(0), indicates that this interface is capabile of ATM VC merge, otherwise it MUST be set to false(1)." DEFVAL { false } ::= { mplsLcAtmIfConfEntry 5 } mplsLcAtmIfConfRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This is object is used to create and delete entries in this table. When configuring entries in this table, the corresponding corresponding ifEntry and mplsInterfaceConfEntry MUST exist before hand. If an entry is attempted to be created by a manager for a corresponding mplsInterfaceConfEntry that does not support LC-ATM, the agent MUST return an inconsistentValue error. If this table is implemented read-only, then the agent must set this object to active(1) when this row is made active. If this table is implemented writable, then an agent MUST not allow modification to its objects once this value is set to active(1)." ::= { mplsLcAtmIfConfEntry 6 } mplsLcAtmIfConfStoreType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This SNMP storage type for this entry. All objects are writable for permanent objects." MPLS Working Group Expires July 2004 [Page 6] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 ::= { mplsLcAtmIfConfEntry 7 } -- End of mplsLcAtmIfConfTable -- Module compliance. mplsLcAtmCompliances OBJECT IDENTIFIER ::= { mplsLcAtmConformance 1 } mplsLcAtmGroups OBJECT IDENTIFIER ::= { mplsLcAtmConformance 2 } mplsLcAtmModuleCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support MPLS LC-ATM Interfaces." MODULE -- this module -- The mandatory groups have to be implemented -- by all LSRs. However, they may all be supported -- as read-only objects in the case where manual -- configuration is unsupported. MANDATORY-GROUPS { mplsLcAtmIfGroup } -- mplsLcAtmIfConfTable OBJECT mplsLcAtmCtrlVpi MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcAtmCtrlVci MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcAtmUnlabTrafVpi MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcAtmUnlabTrafVci MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcAtmVcMerge MIN-ACCESS read-only MPLS Working Group Expires July 2004 [Page 7] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 DESCRIPTION "Write access is not required." OBJECT mplsLcAtmIfConfRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcAtmIfConfStoreType MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { mplsLcAtmCompliances 1 } -- Units of conformance. mplsLcAtmIfGroup OBJECT-GROUP OBJECTS { mplsLcAtmCtrlVpi, mplsLcAtmCtrlVci, mplsLcAtmUnlabTrafVpi, mplsLcAtmUnlabTrafVci, mplsLcAtmVcMerge, mplsLcAtmIfConfRowStatus, mplsLcAtmIfConfStoreType } STATUS current DESCRIPTION "Collection of objects needed for MPLS LC-ATM interface configuration." ::= { mplsLcAtmGroups 1 } END 7. MPLS Label Controlled Frame-Relay MIB Definitions MPLS-LC-FR-MIB-DRAFT-01 DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF RowStatus, StorageType FROM SNMPv2-TC mplsInterfaceIndex FROM MPLS-LSR-STD-MIB DLCI FROM FRAME-RELAY-DTE-MIB mplsStdMIB FROM MPLS-TC-STD-MIB ; MPLS Working Group Expires July 2004 [Page 8] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 mplsLcFrMIB MODULE-IDENTITY LAST-UPDATED "200401301200Z" -- 30 January 2004 12:00:00 GMT ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Thomas D. Nadeau Postal: Cisco Systems, Inc. 250 Apollo Drive Chelmsford, MA 01824 Tel: +1-978-244-3051 Email: tnadeau@cisco.com Subrahmanya Hegde Postal: Cisco Systems, Inc. 225 East Tazman Drive Tel: +1-408-525-6562 Email: subrah@cisco.com General comments should be sent to mpls@uu.net " DESCRIPTION "This MIB contains managed object definitions for MPLS Label Controlled Frame-Relay interfaces as defined in RFC3034." -- Revision history. REVISION "200401301200Z" -- 30 January 2004 12:00:00 GMT DESCRIPTION "Initial draft revision." ::= { mplsStdMIB XXX } -- To Be Assigned by IANA, maybe 7 -- Top level components of this MIB. -- Tables, Scalars, Notifications, Conformance mplsLcFrNotifications OBJECT IDENTIFIER ::= { mplsLcFrMIB 0 } mplsLcFrObjects OBJECT IDENTIFIER ::= { mplsLcFrMIB 1 } mplsLcFrConformance OBJECT IDENTIFIER ::= { mplsLcFrMIB 2 } -- MPLS LC-FR Interface Configuration Table. mplsLcFrIfConfTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsLcFrIfConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table specifies per-interface MPLS LC-FR capability and associated information. In particular, this table extends the MPLS-LSR MIB's mplsInterfaceConfTable." ::= { mplsLcFrObjects 1 } mplsLcFrIfConfEntry OBJECT-TYPE SYNTAX MplsLcFrIfConfEntry MPLS Working Group Expires July 2004 [Page 9] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table is created by an LSR for every interface capable of supporting MPLS LC-FR. Each entry in this table will exist only if a corresponding entry in ifTable and mplsInterfaceConfTable exist. If the associated entries in ifTable and mplsInterfaceConfTable are deleted, the corresponding entry in this table must also be deleted shortly thereafter. " INDEX { mplsInterfaceIndex } ::= { mplsLcFrIfConfTable 1 } MplsLcFrIfConfEntry ::= SEQUENCE { mplsLcFrTrafficMinDlci DLCI, mplsLcFrTrafficMaxDlci DLCI, mplsLcFrCtrlMinDlci DLCI, mplsLcFrCtrlMaxDlci DLCI, mplsLcFrIfConfRowStatus RowStatus, mplsLcFrIfConfStoreType StorageType } mplsLcFrTrafficMinDlci OBJECT-TYPE SYNTAX DLCI MAX-ACCESS read-create STATUS current DESCRIPTION "This is the minimum DLCI value over which this LSR is willing to accept traffic on this interface." ::= { mplsLcFrIfConfEntry 1 } mplsLcFrTrafficMaxDlci OBJECT-TYPE SYNTAX DLCI MAX-ACCESS read-create STATUS current DESCRIPTION "This is the max DLCI value over which this LSR is willing to accept traffic on this interface." ::= { mplsLcFrIfConfEntry 2 } mplsLcFrCtrlMinDlci OBJECT-TYPE SYNTAX DLCI MAX-ACCESS read-create STATUS current DESCRIPTION "This is the min DLCI value over which this LSR is willing to accept control traffic MPLS Working Group Expires July 2004 [Page 10] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 on this interface." ::= { mplsLcFrIfConfEntry 3 } mplsLcFrCtrlMaxDlci OBJECT-TYPE SYNTAX DLCI MAX-ACCESS read-create STATUS current DESCRIPTION "This is the max DLCI value over which this LSR is willing to accept control traffic on this interface." ::= { mplsLcFrIfConfEntry 4 } mplsLcFrIfConfRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This is object is used to create and delete entries in this table. When configuring entries in this table, the corresponding corresponding ifEntry and mplsInterfaceConfEntry MUST exist before hand. If an entry is attempted to be created by a manager for a corresponding mplsInterfaceConfEntry that does not support LC-FR, the agent MUST return an inconsistentValue error. If this table is implemented read-only, then the agent must set this object to active(1) when this row is made active. If this table is implemented writable, then an agent MUST not allow modification to its objects once this value is set to active(1)." ::= { mplsLcFrIfConfEntry 5 } mplsLcFrIfConfStoreType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This SNMP storage type for this entry. All objects are writable for permanent entries." ::= { mplsLcFrIfConfEntry 6 } -- End of mplsLcFrIfConfTable -- Module compliance. mplsLcFrCompliances OBJECT IDENTIFIER ::= { mplsLcFrConformance 1 } mplsLcFrGroups MPLS Working Group Expires July 2004 [Page 11] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 OBJECT IDENTIFIER ::= { mplsLcFrConformance 2 } mplsLcFrModuleCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support MPLS LC-FR Interfaces." MODULE -- this module -- The mandatory groups have to be implemented -- by all LSRs. However, they may all be supported -- as read-only objects in the case where manual -- configuration is unsupported. MANDATORY-GROUPS { mplsLcFrIfGroup } -- mplsLcFrIfConfTable OBJECT mplsLcFrTrafficMinDlci MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcFrTrafficMaxDlci MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcFrCtrlMinDlci MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcFrCtrlMaxDlci MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcFrIfConfRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsLcFrIfConfStoreType MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { mplsLcFrCompliances 1 } MPLS Working Group Expires July 2004 [Page 12] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 -- Units of conformance. mplsLcFrIfGroup OBJECT-GROUP OBJECTS { mplsLcFrTrafficMinDlci, mplsLcFrTrafficMaxDlci, mplsLcFrCtrlMinDlci, mplsLcFrCtrlMaxDlci, mplsLcFrIfConfRowStatus, mplsLcFrIfConfStoreType } STATUS current DESCRIPTION "Collection of objects needed for MPLS LC-FR interface configuration." ::= { mplsLcFrGroups 1 } END 8. Security Considerations It is clear that these MIB modules are potentially useful for monitoring of MPLS LSRs supporting LC-ATM and/or LC-FR. These MIB can also be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results. 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 objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability: o the MplsLcAtmIfConfTable and mplsLcFrIfConfTable collectively contain objects which may be used to provision MPLS LC or FR-enabled interfaces. Unauthorized access to objects in these tables, could result in disruption of traffic on the network. This is especially true if traffic has been established over these interfaces. The use of stronger mechanisms such as SNMPv3 security should be considered where possible. Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent which implements this MIB module. Administrators should consider whether read access to these objects should be allowed, since read access may be undesirable under certain circumstances. Some of the readable objects in this MIB module "i.e., objects with a MPLS Working Group Expires July 2004 [Page 13] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 MAX-ACCESS other than not-accessible" may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability: o the MplsLcAtmIfConfTable and mplsLcFrIfConfTable collectively collectively show the LC-ATM and/or LC-FR interfaces, their associated configurations and their linkages to other MPLS-related configuration and/or performanc statistics. Administrators not wishing to reveal this information should consider these objects sensitive/vulnerable and take precautions so they are not revealed. SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure "for example by using IPSec", even then, there is no control as to who on the secure network is allowed to access and GET/SET "read/change/create/delete" the objects in this MIB module. It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework "see [RFC3410], section 8", including full support for the SNMPv3 cryptographic mechanisms "for authentication and privacy". Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module, is properly configured to give access to the objects only to those principals "users" that have legitimate rights to indeed GET or SET "change/create/delete" them. 9. References 9.1 Normative References [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. [RFC2515] Tesink, K., et al., "Definitions of Managed Objects for ATM Management", RFC 2515, February 1999. [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, MPLS Working Group Expires July 2004 [Page 14] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 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. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001. [RFC3291] Daniele, M., Haberman, B., Routhier., S., Schoenwaelder., J., "Textual Conventions for Internet Network Addresses", RFC3291, May 2002. [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", RFC 3411, December 2002. [TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS Traffic Engineering Management Information Base ", Internet Draft , November 2002. [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, "MPLS Multiprotocol Label Switching (MPLS) Label Switch Router Management Information Base ", Internet Draft , November 2003. [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C., Viswanathan, A., Sjostrand, H. and K. Kompella, "Definition of Textual Conventions and OBJECT- IDENTITIES for Multi-Protocol Label Switching (MPLS) Management", Internet Draft , April 2003. [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS FAMILY NUMBERS, (http://www.isi.edu/in- notes/iana/assignements/address-family-numbers), for MIB see: ftp://ftp.isi.edu/mib/iana.mib/ianaaddressfamilynum bers.mib 9.2 Informative References MPLS Working Group Expires July 2004 [Page 15] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", RFC 2026, October 1996. [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP Applications", RFC 3413, December 2002. [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002. 10. Authors' Addresses Thomas D. Nadeau Cisco Systems, Inc. 300 Beaver Brook Road Boxboro, MA 01719 Phone: +1-978-936-1470 Email: tnadeau@cisco.com Subrahmanya Hegde Cisco Systems, Inc. 225 East Tazman Drive Phone: +1-408-525-6562 Email: subrah@cisco.com 11. Full Copyright Statement Copyright (C) The Internet Society (2001). All Rights Reserved. This document and translations of it may be copied and furnished 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 be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on MPLS Working Group Expires July 2004 [Page 16] Internet Draft MPLS-LC-ATM/FR-MIB January 30, 2004 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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. 12. Intellectual Property Notice The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11 [RFC2028]. Copies of claims of rights made available for publication and any 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 such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 13. IANA Considerations As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB [MPLSTCMIB], MPLS related standards track MIB modules should be rooted under the mplsStdMIB subtree. There are 2 MPLS MIB Modules contained in this document, each of the following "IANA Considerations" subsections requests IANA for a new assignment under the mplsStdMIB subtree. New assignments can only be made via a Standards Action as specified in [RFC2434]. 14.1. IANA Considerations for MPLS-LC-ATM-MIB The IANA is requested to assign { mplsStdMIB 6 } to the MPLS-LC-ATM-MIB module specified in this document. 14.2. IANA Considerations for MPLS-LC-FR-MIB The IANA is requested to assign { mplsStdMIB 7 } to the MPLS-LC-FR-MIB module specified in this document. MPLS Working Group Expires July 2004 [Page 17]