--- 1/draft-ietf-mpls-te-mib-13.txt 2006-02-05 00:43:44.000000000 +0100 +++ 2/draft-ietf-mpls-te-mib-14.txt 2006-02-05 00:43:44.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) Traffic Engineering Management Information Base - draft-ietf-mpls-te-mib-13.txt + draft-ietf-mpls-te-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 Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. @@ -60,30 +61,30 @@ 6.4. mplsTunnelARHopTable ................................. 6 6.5. mplsTunnelCHoptable .................................. 6 6.6. mplsTunnelPerfTable .................................. 6 6.7. mplsTunnelCRLDPResTable .............................. 6 7. Use of 32-bit and 64-bit Counters ...................... 7 8. Application of the Interface Group to MPLS Tunnels ..... 7 8.1. Support of the MPLS Tunnel Interface by ifTable ...... 8 9. Example of Tunnel Setup ................................ 9 10. The Use of RowPointer ................................ 11 11. MPLS Traffic Engineering MIB Definitions ............. 12 -12. Security Considerations .............................. 65 -13. Acknowledgments ...................................... 67 -14. References ........................................... 67 -14.1. Normative References ............................... 67 -14.2. Informative References ............................. 68 -15. Authors' Addresses ................................... 69 -16. Full Copyright Statement ............................. 70 -17. Intellectual Property Notice ......................... 71 -18. IANA Considerations ................................ 71 -18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 71 +12. Security Considerations .............................. 62 +13. Acknowledgments ...................................... 63 +14. References ........................................... 64 +14.1. Normative References ............................... 64 +14.2. Informative References ............................. 65 +15. Authors' Addresses ................................... 65 +16. Full Copyright Statement ............................. 66 +17. Intellectual Property Notice ......................... 66 +18. IANA Considerations ................................ 67 +18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 67 1. Introduction This memo defines a 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] based traffic engineering. This MIB module should be used in conjunction with the companion document [LSRMIB] for MPLS based traffic engineering configuration @@ -986,21 +984,21 @@ DESCRIPTION "This variable points to a row in the mplsXCTable. This table identifies the segments that compose this tunnel, their characteristics, and relationships to each other. A value of zeroDotZero indicates that no LSP has been associated with this tunnel yet." REFERENCE "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS Label Switch Router Management Information Base, - Internet Draft , + Internet Draft , June 2003." DEFVAL { zeroDotZero } ::= { mplsTunnelEntry 11 } mplsTunnelSignallingProto OBJECT-TYPE SYNTAX INTEGER { none(1), rsvp(2), crldp(3), other(4) @@ -1475,32 +1474,32 @@ DESCRIPTION "Primary index into this table identifying a particular explicit route object." ::= { mplsTunnelHopEntry 1 } mplsTunnelHopPathOptionIndex OBJECT-TYPE SYNTAX MplsPathIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Tertiary index into this table identifying a + "Secondary index into this table identifying a particular group of hops representing a particular configured path. This is otherwise known as a path option." ::= { mplsTunnelHopEntry 2 } mplsTunnelHopIndex OBJECT-TYPE SYNTAX MplsPathIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION - "Secondary index into this table identifying a + "Tertiary index into this table identifying a particular hop." ::= { mplsTunnelHopEntry 3 } mplsTunnelHopAddrType OBJECT-TYPE SYNTAX TeHopAddressType MAX-ACCESS read-create STATUS current DESCRIPTION "The Hop Address Type of this tunnel hop. The value of this object cannot be changed @@ -1760,81 +1760,43 @@ mplsTunnelResourceMaxRate OBJECT-TYPE SYNTAX MplsBitRate UNITS "kilobits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum rate in bits/second. Note that setting mplsTunnelResourceMaxRate, mplsTunnelResourceMeanRate, and mplsTunnelResourceMaxBurstSize to 0 indicates best- - effort treatment. - - This object is copied to an instance of - mplsTrafficParamMaxRate in mplsTrafficParamTable - the OID of which is copied into the corresponding - mplsInSegmentTrafficParamPtr." - REFERENCE - "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS - Label Switch Router Management Information Base, - Internet Draft , - June 2003." + effort treatment." ::= { mplsTunnelResourceEntry 2 } mplsTunnelResourceMeanRate OBJECT-TYPE SYNTAX MplsBitRate UNITS "kilobits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "This object is copied into an instance of mplsTrafficParamMeanRate in the mplsTrafficParamTable. The OID of this table entry is then copied into the corresponding - mplsInSegmentTrafficParamPtr. - - When resource allocation is performed as requested - by this TSpec object, it is copied into an entry in - mplsTrafficParamTable [LSRMIB]: - mplsTunnelInMeanRate to mplsTrafficParamMeanRate. - The OID of this entry is copied to - mplsInSegmentTrafficParamPtr of the corresponding - in-segment entry." - REFERENCE - "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS - Label Switch Router Management Information Base, - Internet Draft , - June 2003." + mplsInSegmentTrafficParamPtr." ::= { mplsTunnelResourceEntry 3 } mplsTunnelResourceMaxBurstSize OBJECT-TYPE SYNTAX MplsBurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION - "The maximum burst size in bytes. This object is - copied to mplsInSegmentMaxBurstSize of the - corresponding in-segment. - - When resource allocation is performed as requested - by this TSpec object, it is copied into an entry in - mplsTrafficParamTable [LSRMIB]: - mplsTunnelInMaxBurstSize to - mplsTrafficParamMaxBurstSize. The OID of this entry - is copied to mplsInSegmentTrafficParamPtr of the - corresponding in-segment entry." - REFERENCE - "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS - Label Switch Router Management Information Base, - Internet Draft , - June 2003." + "The maximum burst size in bytes." ::= { mplsTunnelResourceEntry 4 } mplsTunnelResourceMeanBurstSize OBJECT-TYPE SYNTAX MplsBurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The mean burst size in bytes. The implementations which do not implement this variable must return @@ -2592,48 +2554,38 @@ GROUP mplsTeNotificationGroup DESCRIPTION "This group is mandatory for those implementations which can implement the notifications contained in this group." OBJECT mplsTunnelRowStatus 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 mplsTunnelHopRowStatus 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. - " - - OBJECT mplsTunnelHopStorageType - MIN-ACCESS read-only - DESCRIPTION "Write access is not required." + DESCRIPTION "Support for createAndWait and notReady is not + required." OBJECT mplsTunnelCRLDPResRowStatus 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. - " - OBJECT mplsTunnelCRLDPResStorageType - MIN-ACCESS read-only - DESCRIPTION "Write access is not required." + DESCRIPTION "Support for createAndWait and notReady is + not required." ::= { mplsTeCompliances 1 } -- Compliance requirement for read-only implementations. mplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance requirement for implementations that only provide read-only support for MPLS-TE-STD-MIB. @@ -3216,21 +3167,21 @@ [TCMIB] Nadeau, T. and J. Cucchiara (Editors), "Definition of Textual Conventions and OBJECT-IDENTITIES for Multi-Protocol Label Switching (MPLS) Management", Internet Draft , June 2003. [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, "MPLS Multiprotocol Label Switching (MPLS) Label Switch Router Management Information Base ", Internet Draft , June 2003. + ietf-mpls-lsr-mib-14.txt>, November 2003. [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup using LDP", RFC 3212, January 2002. 14.2. Informative References [RFC2026] S. Bradner, "The Internet Standards Process -- Revision 3", RFC 2026, October 1996. [RFC2401] Kent, S., and R. Atkinson, "Security @@ -3315,17 +3266,20 @@ 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. 18. 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. New assignments can only - be made via a Standards Action as specified in [RFC2434]. + 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]. 18.1. IANA Considerations for MPLS-TE-STD-MIB The IANA is requested to assign { mplsStdMIB 3 } to the MPLS-TE-STD-MIB module specified in this document.