Network Working Group Thomas D. Nadeau Internet Draft Subrahmanya Hegde Expires: December 2002 Cisco Systems, Inc. June 2002 Multiprotocol Label Switching (MPLS) Label-Controlled ATM and Frame-Relay Management Interface Definition draft-ietf-mpls-lc-if-mib-00.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 [RFC2026]. 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 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. Feature Checklist ......................................... 4 6. Outline ................................................... 5 6.1. Summary of LSR MIB ..................................... 6 7. Brief Description of MIB Objects .......................... 6 7.1. mplsInterfaceConfTable ................................. 7 7.2. mplsInterfacePerfTable ................................. 7 7.3. mplsInSegmentTable ..................................... 7 7.4. mplsInSegmentPerfTable ................................. 7 7.5. mplsOutSegmentTable .................................... 8 7.6. mplsOutSegmentPerfTable ................................ 8 7.7. mplsXCTable ............................................ 8 7.8. mplsLabelStackTable .................................... 8 7.9. mplsTrafficParamTable .................................. 9 Nadeau et al. Expires December 2002 [Page 1] Internet Draft LC ATM/FR MIBs June 20, 2002 8. Example of LSP Setup ...................................... 9 9. Application of the Interface Group to MPLS ................ 11 9.1. Support of the MPLS Layer by ifTable ................... 11 10. The Use of RowPointer .................................... 13 11. MPLS Label Switch Router MIB Definitions ................. 13 12. Security Considerations .................................. 51 13. Acknowledgments .......................................... 52 14. References ............................................... 52 15. Authors' Addresses ....................................... 54 16. Full Copyright Statement ................................. 55 1. Abstract 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 Nadeau et al. Expires December 2002 [Page 2] Internet Draft LC ATM/FR MIBs June 20, 2002 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 The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Nadeau et al. Expires December 2002 [Page 3] Internet Draft LC ATM/FR MIBs June 20, 2002 Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 5. Interface Stacking Relationship for MPLS The MPLS-LSR and MPLS-TE MIBs define the media-specific extensions to the Interfaces Group for managing MPLS interfaces. They also define the conceptual interface stacking as follows. +------------------------------------------------+ | MPLS tunnel interface ifType = mplsTunnel(150) | +------------------------------------------------+ | MPLS-interface ifType = mpls(166) + +------------------------------------------------+ | Underlying Layer... + +------------------------------------------------+ In the above diagram, MPLS-enabled interfaces are represented by an ifEntry with ifType set to mpls(166). This subinterface is conceptually stacked above some underlying layer. The "Underlying Layer..." refers to the ifIndex of any interface type, which has been defined for MPLS interworking. Examples include ATM, Frame Relay, Ethernet, etc. The top-most layer defines zero or more TE tunnel interfaces that are conceptually stacked above the MPLS-type interface that carries its traffic. 6. 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). Nadeau et al. Expires December 2002 [Page 4] Internet Draft LC ATM/FR MIBs June 20, 2002 7. MPLS Label Controlled ATM MIB Definitions MPLS-LC-ATM-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF RowStatus, StorageType, TruthValue FROM SNMPv2-TC mplsInterfaceConfIndex FROM MPLS-LSR-MIB AtmVpIdentifier FROM ATM-TC-MIB mplsMIB, MplsAtmVcIdentifier FROM MPLS-TC-MIB ; mplsLcAtmMIB MODULE-IDENTITY LAST-UPDATED "200205101200Z" -- 10 May 2002 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 ATM interfaces as defined in RFC3035." -- Revision history. REVISION "200012251200Z" -- 25 December 2001 12:00:00 GMT DESCRIPTION "Initial revision, published as part of RFC XXXX." ::= { mplsMIB n } -- To Be Assigned, maybe 6 Nadeau et al. Expires December 2002 [Page 5] Internet Draft LC ATM/FR MIBs June 20, 2002 -- Top level components of this MIB. -- Tables, Scalars, Notifications, Conformance mplsLcAtmNotifyPrefix OBJECT IDENTIFIER ::= { mplsLcAtmMIB 0 } mplsLcAtmObjects OBJECT IDENTIFIER ::= { mplsLcAtmMIB 1 } mplsLcAtmNotifications OBJECT IDENTIFIER ::= { mplsLcAtmMIB 2 } mplsLcAtmConformance OBJECT IDENTIFIER ::= { mplsLcAtmMIB 3 } -- 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 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 { mplsInterfaceConfIndex } ::= { mplsLcAtmIfConfTable 1 } MplsLcAtmIfConfEntry ::= SEQUENCE { mplsLcAtmCtrlVpi AtmVpIdentifier, mplsLcAtmCtrlVci MplsAtmVcIdentifier, mplsLcAtmUnlabTrafVpi AtmVpIdentifier, mplsLcAtmUnlabTrafVci MplsAtmVcIdentifier, mplsLcAtmVcMerge TruthValue, mplsLcAtmIfConfRowStatus RowStatus, mplsLcAtmIfConfStoreType StorageType } mplsLcAtmCtrlVpi OBJECT-TYPE SYNTAX AtmVpIdentifier Nadeau et al. Expires December 2002 [Page 6] Internet Draft LC ATM/FR MIBs June 20, 2002 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." ::= { 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 Nadeau et al. Expires December 2002 [Page 7] Internet Draft LC ATM/FR MIBs June 20, 2002 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." ::= { mplsLcAtmIfConfEntry 7 } -- End of mplsLcAtmIfConfTable -- Notification Configuration -- End of notifications. -- Module compliance. mplsLcAtmGroups OBJECT IDENTIFIER ::= { mplsLcAtmConformance 1 } mplsLcAtmCompliances OBJECT IDENTIFIER ::= { mplsLcAtmConformance 2 } mplsLcAtmModuleCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support MPLS LC-ATM Interfaces." MODULE -- this module Nadeau et al. Expires December 2002 [Page 8] Internet Draft LC ATM/FR MIBs June 20, 2002 -- 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 } GROUP mplsLcAtmIfGroup DESCRIPTION "This group is mandatory for those LSRs that support LC-ATM interfaces." -- 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 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." Nadeau et al. Expires December 2002 [Page 9] Internet Draft LC ATM/FR MIBs June 20, 2002 ::= { 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 8. MPLS Label Controlled Frame-Relay MIB Definitions MPLS-LC-FR-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF RowStatus, StorageType FROM SNMPv2-TC mplsInterfaceConfIndex FROM MPLS-LSR-MIB DLCI FROM FRAME-RELAY-DTE-MIB mplsMIB FROM MPLS-TC-MIB ; mplsLcFrMIB MODULE-IDENTITY LAST-UPDATED "200205101200Z" -- 10 May 2002 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 Nadeau et al. Expires December 2002 [Page 10] Internet Draft LC ATM/FR MIBs June 20, 2002 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 "200012251200Z" -- 25 December 2001 12:00:00 GMT DESCRIPTION "Initial revision, published as part of RFC XXXX." ::= { mplsMIB n } -- To Be Assigned, maybe 7 -- Top level components of this MIB. -- Tables, Scalars, Notifications, Conformance mplsLcFrNotifyPrefix OBJECT IDENTIFIER ::= { mplsLcFrMIB 0 } mplsLcFrObjects OBJECT IDENTIFIER ::= { mplsLcFrMIB 1 } mplsLcFrNotifications OBJECT IDENTIFIER ::= { mplsLcFrMIB 2 } mplsLcFrConformance OBJECT IDENTIFIER ::= { mplsLcFrMIB 3 } -- 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 MAX-ACCESS not-accessible STATUS current DESCRIPTION Nadeau et al. Expires December 2002 [Page 11] Internet Draft LC ATM/FR MIBs June 20, 2002 "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 { mplsInterfaceConfIndex } ::= { 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 on this interface." ::= { mplsLcFrIfConfEntry 3 } Nadeau et al. Expires December 2002 [Page 12] Internet Draft LC ATM/FR MIBs June 20, 2002 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 -- Notification Configuration -- End of notifications. -- Module compliance. mplsLcFrGroups OBJECT IDENTIFIER ::= { mplsLcFrConformance 1 } Nadeau et al. Expires December 2002 [Page 13] Internet Draft LC ATM/FR MIBs June 20, 2002 mplsLcFrCompliances 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 } GROUP mplsLcFrIfGroup DESCRIPTION "This group is mandatory for those LSRs that support LC-FR interfaces." -- 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 Nadeau et al. Expires December 2002 [Page 14] Internet Draft LC ATM/FR MIBs June 20, 2002 "Write access is not required." OBJECT mplsLcFrIfConfStoreType MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { mplsLcFrCompliances 1 } -- 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 12. Security Considerations This module does not define any management objects. Instead, it defines two new ifTypes which may be used by other MPLS MIB modules to define management objects. Meaningful security considerations can only be written in the MIB modules that define management objects. Therefore, this document has no impact on the security of the Internet. 13. Acknowledgments TBD. 14. References [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1700, October 1994. See also: http://www.isi.edu/in-notes/iana/assignments/smi- numbers Nadeau et al. Expires December 2002 [Page 15] Internet Draft LC ATM/FR MIBs June 20, 2002 [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 [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, Viswanathan, A. and H. Sjostrand, "Definition of Textual Conventions and OBJECT-IDENTITIES for Multi- Protocol Label Switching (MPLS) Management", Internet Draft , August 2001. [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP- based Internets", RFC 1155, May 1990. [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, May 1990. [RFC1215] M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991. [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2233] McCloghrie, K., and F. Kastenholtz, "The Interfaces Group MIB using SMIv2", RFC 2233, Nov. 1997 [RFC2401] Kent, S., and Atkinson, R., "Security Architecture for the Internet Protocol", RFC 2401, November 1998. Nadeau et al. Expires December 2002 [Page 16] Internet Draft LC ATM/FR MIBs June 20, 2002 [RFC2515] Tesink, K., "Definitions of Managed Objects for ATM Management", RFC 2515, Feb. 1999 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999. [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 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, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. McManus, "Requirements for Traffic Engineering Over MPLS", RFC 2702, September 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. [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, Nadeau et al. Expires December 2002 [Page 17] Internet Draft LC ATM/FR MIBs June 20, 2002 "Multiprotocol Label Switching Architecture", RFC 3031, January 2001. [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., Federokow, G., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, January 2001. 15. Authors' Addresses Thomas D. Nadeau Cisco Systems, Inc. 250 Apollo Drive Chelmsford, MA 01824 Phone: +1-978-244-3051 Email: tnadeau@cisco.com Subrahmanya Hegde Cisco Systems, Inc. 225 East Tazman Drive Phone: +1-408-525-6562 Email: subrah@cisco.com 16. 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 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 Nadeau et al. Expires December 2002 [Page 18] Internet Draft LC ATM/FR MIBs June 20, 2002 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Nadeau et al. Expires December 2002 [Page 19]