--- 1/draft-ietf-mpls-lsr-mib-13.txt 2006-02-05 00:41:39.000000000 +0100 +++ 2/draft-ietf-mpls-lsr-mib-14.txt 2006-02-05 00:41:39.000000000 +0100 @@ -1,26 +1,26 @@ Network Working Group Cheenu Srinivasan Internet Draft Bloomberg L.P. Expires: May 2004 Arun Viswanathan Force10 Networks, Inc. Thomas D. Nadeau Cisco Systems, Inc. - October 2003 + November 2003 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base - draft-ietf-mpls-lsr-mib-13.txt + draft-ietf-mpls-lsr-mib-14.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. @@ -63,29 +63,29 @@ 5.7. mplsXCTable ..............................................5 5.8. mplsLabelStackTable ......................................6 5.9 mplsInSegmentMapTable ....................................6 6. Use of 32-bit and 64-bit Counters ........................6 7. Example of LSP Setup .....................................6 8. Application of the Interface Group to MPLS ...............8 8.1. Support of the MPLS Layer by ifTable .....................8 9. The Use of RowPointer ....................................10 10. MPLS Label Switching Router MIB Module Definitions .......10 11. Security Considerations ..................................52 - 12. Acknowledgments ..........................................53 - 13. IANA Considerations ......................................53 + 12. Acknowledgments ..........................................54 + 13. IANA Considerations ......................................54 13.1. IANA Considerations for MPLS-LSR-STD-MIB ................54 14. References ...............................................54 14.1. Normative References ....................................54 14.2. Informative References ..................................55 - 15. Authors' Addresses .........................................55 + 15. Authors' Addresses .........................................56 16. Full Copyright Statement ...................................56 - 17. Intellectual Property Notice ...............................56 + 17. Intellectual Property Notice ...............................57 1. Introduction This memo defines an portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling a Multi-Protocol Label Switching (MPLS) [RFC3031] Label Switching Router (LSR). Comments should be made directly to the MPLS mailing list at @@ -1799,23 +1800,21 @@ ::= { mplsXCEntry 6 } mplsXCRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "For creating, modifying, and deleting this row. When a row in this table has a row in the active(1) state, no objects in this row except this object - and the mplsXCStorageType can be modified. - Modification of mplsXCStorateType MUST be done - as specified in the description of that object." + and the mplsXCStorageType can be modified. " ::= { mplsXCEntry 7 } mplsXCStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this object. The agent MUST ensure that the associated in and out segments also have the same StorageType value @@ -2233,64 +2232,55 @@ GROUP mplsLsrNotificationGroup DESCRIPTION "This group is only mandatory for those implementations which can efficiently implement the notifications contained in this group." OBJECT mplsInSegmentRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } - DESCRIPTION "Support for notInservice, createAndWait and notReady - is not required. - " - + DESCRIPTION "Support for createAndWait and notReady is + not required." OBJECT mplsOutSegmentNextHopAddrType SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } - MIN-ACCESS read-only - DESCRIPTION "Write access is not required. Only unknown(0), - ipv4(1) and ipv6(2) support is required. - " + DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support + is required." OBJECT mplsOutSegmentNextHopAddr SYNTAX InetAddress (SIZE(0|4|16)) - MIN-ACCESS read-only - DESCRIPTION "Write access is not required. An implementation is - only required to support unknown(0), ipv4(1) and - ipv6(2) sizes." + DESCRIPTION "An implementation is only required to support + unknown(0), ipv4(1) and ipv6(2) sizes." OBJECT mplsOutSegmentRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } - DESCRIPTION "Support for notInservice, createAndWait and notReady - is not required. - " + DESCRIPTION "Support for createAndWait and notReady is not + required." OBJECT mplsLabelStackRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } - DESCRIPTION "Support for notInservice, createAndWait and notReady - is not required. - " + DESCRIPTION "Support for createAndWait and notReady is not + required." OBJECT mplsXCRowStatus SYNTAX RowStatus { active(1), notInService(2) } WRITE-SYNTAX RowStatus { active(1), notInService(2), createAndGo(4), destroy(6) } - DESCRIPTION "Support for notInservice, createAndWait and notReady - is not required. - " + DESCRIPTION "Support for createAndWait and notReady is not + required." ::= { mplsLsrCompliances 1 } -- Compliance requirement for read-only implementations. mplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for MPLS-LSR-STD-MIB. Such devices can then be monitored but cannot be configured @@ -2665,26 +2655,28 @@ 12. Acknowledgments We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, Vasanthi Thirumalai, Joseph Benoit, Mike Piecuch, Joan Cucchiara. A special thanks to Bert Wijnen and Mike MacFaden for really getting the MIB module into shape. 13. IANA Considerations As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB - [TCMIB], MPLS related standards track MIB modules should be - rooted under the mplsStdMIB subtree. New assignments can only - be made via a Standards Action as specified in [RFC2434]. + [MPLSTCMIB], MPLS related standards track MIB modules should be + rooted under the mplsStdMIB subtree. There are 4 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]. 13.1. IANA Considerations for MPLS-LSR-STD-MIB - The IANA is requested to assign { mplsStdMIB 2 } to the MPLS-LSR-STD-MIB module specified in this document. 14. References 14.1. Normative References [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. @@ -2681,26 +2673,20 @@ The IANA is requested to assign { mplsStdMIB 2 } to the MPLS-LSR-STD-MIB module specified in this document. 14. References 14.1. Normative References [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. - [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing -an - IANA Considerations Section in RFCs", BCP: 26, RFC -2434, - October 1998. - [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, J., Rose, M., and S. Waldbusser, "Textual Conventions