draft-ietf-mpls-lsr-mib-13.txt   draft-ietf-mpls-lsr-mib-14.txt 
Network Working Group Cheenu Srinivasan Network Working Group Cheenu Srinivasan
Internet Draft Bloomberg L.P. Internet Draft Bloomberg L.P.
Expires: May 2004 Expires: May 2004
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
October 2003 November 2003
Multiprotocol Label Switching (MPLS) Label Switching Multiprotocol Label Switching (MPLS) Label Switching
Router (LSR) Management Information Base Router (LSR) Management Information Base
draft-ietf-mpls-lsr-mib-13.txt draft-ietf-mpls-lsr-mib-14.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the In ternet Engineering Internet-Drafts are working documents of the In ternet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at line 73 skipping to change at page 2, line 24
5.7. mplsXCTable ..............................................5 5.7. mplsXCTable ..............................................5
5.8. mplsLabelStackTable ......................................6 5.8. mplsLabelStackTable ......................................6
5.9 mplsInSegmentMapTable ....................................6 5.9 mplsInSegmentMapTable ....................................6
6. Use of 32-bit and 64-bit Counters ........................6 6. Use of 32-bit and 64-bit Counters ........................6
7. Example of LSP Setup .....................................6 7. Example of LSP Setup .....................................6
8. Application of the Interface Group to MPLS ...............8 8. Application of the Interface Group to MPLS ...............8
8.1. Support of the MPLS Layer by ifTable .....................8 8.1. Support of the MPLS Layer by ifTable .....................8
9. The Use of RowPointer ....................................10 9. The Use of RowPointer ....................................10
10. MPLS Label Switching Router MIB Module Definitions .......10 10. MPLS Label Switching Router MIB Module Definitions .......10
11. Security Considerations ..................................52 11. Security Considerations ..................................52
12. Acknowledgments ..........................................53 12. Acknowledgments ..........................................54
13. IANA Considerations ......................................53 13. IANA Considerations ......................................54
13.1. IANA Considerations for MPLS-LSR-STD-MIB ................54 13.1. IANA Considerations for MPLS-LSR-STD-MIB ................54
14. References ...............................................54 14. References ...............................................54
14.1. Normative References ....................................54 14.1. Normative References ....................................54
14.2. Informative References ..................................55 14.2. Informative References ..................................55
15. Authors' Addresses .........................................55 15. Authors' Addresses .........................................56
16. Full Copyright Statement ...................................56 16. Full Copyright Statement ...................................56
17. Intellectual Property Notice ...............................56 17. Intellectual Property Notice ...............................57
1. Introduction 1. Introduction
This memo defines an portion of the Management This memo defines an portion of the Management
Information Base (MIB) for use with network management protocols Information Base (MIB) for use with network management protocols
in the Internet community. In particular, it describes managed in the Internet community. In particular, it describes managed
objects for modeling a Multi-Protocol Label Switching (MPLS) objects for modeling a Multi-Protocol Label Switching (MPLS)
[RFC3031] Label Switching Router (LSR). [RFC3031] Label Switching Router (LSR).
Comments should be made directly to the MPLS mailing list at Comments should be made directly to the MPLS mailing list at
skipping to change at line 1809 skipping to change at page 37, line 16
::= { mplsXCEntry 6 } ::= { mplsXCEntry 6 }
mplsXCRowStatus OBJECT-TYPE mplsXCRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For creating, modifying, and deleting this row. "For creating, modifying, and deleting this row.
When a row in this table has a row in the active(1) When a row in this table has a row in the active(1)
state, no objects in this row except this object state, no objects in this row except this object
and the mplsXCStorageType can be modified. and the mplsXCStorageType can be modified. "
Modification of mplsXCStorateType MUST be done
as specified in the description of that object."
::= { mplsXCEntry 7 } ::= { mplsXCEntry 7 }
mplsXCStorageType OBJECT-TYPE mplsXCStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the storage type for this "This variable indicates the storage type for this
object. The agent MUST ensure that the associated in object. The agent MUST ensure that the associated in
and out segments also have the same StorageType value and out segments also have the same StorageType value
skipping to change at line 2243 skipping to change at page 45, line 51
GROUP mplsLsrNotificationGroup GROUP mplsLsrNotificationGroup
DESCRIPTION "This group is only mandatory for those implementations DESCRIPTION "This group is only mandatory for those implementations
which can efficiently implement the notifications which can efficiently implement the notifications
contained in this group." contained in this group."
OBJECT mplsInSegmentRowStatus OBJECT mplsInSegmentRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) createAndGo(4), destroy(6)
} }
DESCRIPTION "Support for notInservice, createAndWait and notReady DESCRIPTION "Support for createAndWait and notReady is
is not required. not required."
"
OBJECT mplsOutSegmentNextHopAddrType OBJECT mplsOutSegmentNextHopAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only DESCRIPTION "Only unknown(0), ipv4(1) and ipv6(2) support
DESCRIPTION "Write access is not required. Only unknown(0), is required."
ipv4(1) and ipv6(2) support is required.
"
OBJECT mplsOutSegmentNextHopAddr OBJECT mplsOutSegmentNextHopAddr
SYNTAX InetAddress (SIZE(0|4|16)) SYNTAX InetAddress (SIZE(0|4|16))
MIN-ACCESS read-only DESCRIPTION "An implementation is only required to support
DESCRIPTION "Write access is not required. An implementation is unknown(0), ipv4(1) and ipv6(2) sizes."
only required to support unknown(0), ipv4(1) and
ipv6(2) sizes."
OBJECT mplsOutSegmentRowStatus OBJECT mplsOutSegmentRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) createAndGo(4), destroy(6)
} }
DESCRIPTION "Support for notInservice, createAndWait and notReady DESCRIPTION "Support for createAndWait and notReady is not
is not required. required."
"
OBJECT mplsLabelStackRowStatus OBJECT mplsLabelStackRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) createAndGo(4), destroy(6)
} }
DESCRIPTION "Support for notInservice, createAndWait and notReady DESCRIPTION "Support for createAndWait and notReady is not
is not required. required."
"
OBJECT mplsXCRowStatus OBJECT mplsXCRowStatus
SYNTAX RowStatus { active(1), notInService(2) } SYNTAX RowStatus { active(1), notInService(2) }
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) createAndGo(4), destroy(6)
} }
DESCRIPTION "Support for notInservice, createAndWait and notReady DESCRIPTION "Support for createAndWait and notReady is not
is not required. required."
"
::= { mplsLsrCompliances 1 } ::= { mplsLsrCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE mplsLsrModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance requirement for implementations that only DESCRIPTION "Compliance requirement for implementations that only
provide read-only support for MPLS-LSR-STD-MIB. Such provide read-only support for MPLS-LSR-STD-MIB. Such
devices can then be monitored but cannot be configured devices can then be monitored but cannot be configured
skipping to change at line 2675 skipping to change at page 54, line 26
12. Acknowledgments 12. Acknowledgments
We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim
Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, Vasanthi Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, Vasanthi
Thirumalai, Joseph Benoit, Mike Piecuch, Joan Cucchiara. Thirumalai, Joseph Benoit, Mike Piecuch, Joan Cucchiara.
A special thanks to Bert Wijnen and Mike MacFaden for really A special thanks to Bert Wijnen and Mike MacFaden for really
getting the MIB module into shape. getting the MIB module into shape.
13. IANA Considerations 13. IANA Considerations
As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB
[TCMIB], MPLS related standards track MIB modules should be [MPLSTCMIB], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. New assignments can only rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules
be made via a Standards Action as specified in [RFC2434]. 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 13.1. IANA Considerations for MPLS-LSR-STD-MIB
The IANA is requested to assign { mplsStdMIB 2 } to the The IANA is requested to assign { mplsStdMIB 2 } to the
MPLS-LSR-STD-MIB module specified in this document. MPLS-LSR-STD-MIB module specified in this document.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate
Requirement Levels", RFC 2119, BCP 14, March 1997. 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 [RFC2515] Tesink, K., et al., "Definitions of Managed Objects
for ATM Management", RFC 2515, February 1999. for ATM Management", RFC 2515, February 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
 End of changes. 

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