draft-ietf-mpls-lsr-mib-12.txt   draft-ietf-mpls-lsr-mib-13.txt 
Network Working Group Cheenu Srinivasan Network Working Group Cheenu Srinivasan
Internet Draft Bloomberg L.P. Internet Draft Bloomberg L.P.
Expires: March 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.
August 2003 October 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-12.txt draft-ietf-mpls-lsr-mib-13.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 page 2, line 24 skipping to change at line 73
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 ..........................................54 12. Acknowledgments ..........................................53
13. IANA Considerations ......................................54 13. IANA Considerations ......................................53
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 ..................................56 14.2. Informative References ..................................55
15. Authors' Addresses .........................................56 15. Authors' Addresses .........................................55
16. Full Copyright Statement ...................................56 16. Full Copyright Statement ...................................56
17. Intellectual Property Notice ...............................57 17. Intellectual Property Notice ...............................56
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 page 11, line 17 skipping to change at line 514
mplsStdMIB, MplsLSPID, MplsLabel, MplsBitRate, mplsStdMIB, MplsLSPID, MplsLabel, MplsBitRate,
MplsOwner MplsOwner
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
AddressFamilyNumbers AddressFamilyNumbers
FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
; ;
mplsLsrStdMIB MODULE-IDENTITY mplsLsrStdMIB MODULE-IDENTITY
LAST-UPDATED "200308061200Z" -- 06 August 2003 12:00:00 GMT LAST-UPDATED "200310191200Z" -- 19 October 2003 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Cheenu Srinivasan " Cheenu Srinivasan
Blomberg L.P. Blomberg L.P.
Email: cheenu@bloomberg.net Email: cheenu@bloomberg.net
Arun Viswanathan Arun Viswanathan
Force10 Networks, Inc. Force10 Networks, Inc.
Email: arunv@force10networks.com Email: arunv@force10networks.com
skipping to change at page 11, line 49 skipping to change at line 546
defined in: Rosen, E., Viswanathan, A., and R. defined in: Rosen, E., Viswanathan, A., and R.
Callon, Multiprotocol Label Switching Architecture, Callon, Multiprotocol Label Switching Architecture,
RFC 3031, January 2001. RFC 3031, January 2001.
Copyright (C) The Internet Society (2003). This Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFCXXX; see version of this MIB module is part of RFCXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- Revision history. -- Revision history.
REVISION REVISION
"200308061200Z" -- 06 August 2003 12:00:00 GMT "200310191200Z" -- 19 October 2003 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC XXXX."
::= { mplsStdMIB 2 }
::= { mplsStdMIB XXX } -- Please see IANA considerations section
-- the requested mplsStdMIB subId is 2.
-- Textual Conventions -- Textual Conventions
MplsIndexType ::= TEXTUAL-CONVENTION MplsIndexType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is an octet string that can be used as a table "This is an octet string that can be used as a table
index in cases where a large addressable space is index in cases where a large addressable space is
required such as on an LSR where many applications required such as on an LSR where many applications
may be provisioning labels. may be provisioning labels.
skipping to change at page 19, line 43 skipping to change at line 941
The index structure of this table is specifically designed The index structure of this table is specifically designed
to handle many different MPLS implementations that manage to handle many different MPLS implementations that manage
their labels both in a distributed and centralized manner. their labels both in a distributed and centralized manner.
The table is also designed to handle existing MPLS labels The table is also designed to handle existing MPLS labels
as defined in RFC3031 as well as longer ones that may as defined in RFC3031 as well as longer ones that may
be necessary in the future. be necessary in the future.
In cases where the label cannot fit into the In cases where the label cannot fit into the
mplsInSegmentLabel object, the mplsInSegmentLabelPtr mplsInSegmentLabel object, the mplsInSegmentLabelPtr
will indicate this by being set to the first accessible will indicate this by being set to the first accessible
colum in the appropriate extension table's row. column in the appropriate extension table's row.
In this case an additional table MUST In this case an additional table MUST
be provided and MUST be indexed by at least the indexes be provided and MUST be indexed by at least the indexes
used by this table. In all other cases when the label is used by this table. In all other cases when the label is
represented within the mplsInSegmentLabel object, the represented within the mplsInSegmentLabel object, the
mplsInSegmentLabelPtr MUST be set to 0.0. Due to the mplsInSegmentLabelPtr MUST be set to 0.0. Due to the
fact that MPLS labels may not exceed 24 bits, the fact that MPLS labels may not exceed 24 bits, the
mplsInSegmentLabelPtr object is only a provision for mplsInSegmentLabelPtr object is only a provision for
future-proofing the MIB module. Thus, the definition future-proofing the MIB module. Thus, the definition
of any extension tables is beyond the scope of this of any extension tables is beyond the scope of this
MIB module." MIB module."
skipping to change at page 41, line 37 skipping to change at line 2031
SYNTAX MplsInSegmentMapEntry SYNTAX MplsInSegmentMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents one interface "An entry in this table represents one interface
and incoming label pair. and incoming label pair.
In cases where the label cannot fit into the In cases where the label cannot fit into the
mplsInSegmentLabel object, the mplsInSegmentLabelPtr mplsInSegmentLabel object, the mplsInSegmentLabelPtr
will indicate this by being set to the first accessible will indicate this by being set to the first accessible
colum in the appropriate extension table's row, column in the appropriate extension table's row,
and the mplsInSegmentLabel SHOULD be set to 0. and the mplsInSegmentLabel SHOULD be set to 0.
In all other cases when the label is In all other cases when the label is
represented within the mplsInSegmentLabel object, the represented within the mplsInSegmentLabel object, the
mplsInSegmentLabelPtr MUST be 0.0. mplsInSegmentLabelPtr MUST be 0.0.
Implementors need to be aware that if the value of Implementors need to be aware that if the value of
the mplsInSegmentMapLabelPtrIndex (an OID) has more the mplsInSegmentMapLabelPtrIndex (an OID) has more
that 111 sub-identifiers, then OIDs of column that 111 sub-identifiers, then OIDs of column
instances in this table will have more than 128 instances in this table will have more than 128
sub-identifiers and cannot be accessed using SNMPv1, sub-identifiers and cannot be accessed using SNMPv1,
skipping to change at page 54, line 34 skipping to change at line 2675
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
[MPLSTCMIB], MPLS related standards track MIB modules should be [TCMIB], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules rooted under the mplsStdMIB subtree. New assignments can only
contained in this document, each of the following "IANA be made via a Standards Action as specified in [RFC2434].
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/