draft-ietf-mpls-te-mib-12.txt   draft-ietf-mpls-te-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) Traffic Engineering Multiprotocol Label Switching (MPLS) Traffic Engineering
Management Information Base Management Information Base
draft-ietf-mpls-te-mib-12.txt draft-ietf-mpls-te-mib-13.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full This document is an Internet-Draft and is in full
conformance with all provisions of Section 10 of RFC 2026. conformance with all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF), its areas, and its working Engineering Task Force (IETF), its areas, and its working
groups. Note that other groups may also distribute working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
skipping to change at page 2, line 22 skipping to change at line 70
6.4. mplsTunnelARHopTable ................................. 6 6.4. mplsTunnelARHopTable ................................. 6
6.5. mplsTunnelCHoptable .................................. 6 6.5. mplsTunnelCHoptable .................................. 6
6.6. mplsTunnelPerfTable .................................. 6 6.6. mplsTunnelPerfTable .................................. 6
6.7. mplsTunnelCRLDPResTable .............................. 6 6.7. mplsTunnelCRLDPResTable .............................. 6
7. Use of 32-bit and 64-bit Counters ...................... 7 7. Use of 32-bit and 64-bit Counters ...................... 7
8. Application of the Interface Group to MPLS Tunnels ..... 7 8. Application of the Interface Group to MPLS Tunnels ..... 7
8.1. Support of the MPLS Tunnel Interface by ifTable ...... 8 8.1. Support of the MPLS Tunnel Interface by ifTable ...... 8
9. Example of Tunnel Setup ................................ 9 9. Example of Tunnel Setup ................................ 9
10. The Use of RowPointer ................................ 11 10. The Use of RowPointer ................................ 11
11. MPLS Traffic Engineering MIB Definitions ............. 12 11. MPLS Traffic Engineering MIB Definitions ............. 12
12. Security Considerations .............................. 63 12. Security Considerations .............................. 65
13. Acknowledgments ...................................... 64 13. Acknowledgments ...................................... 67
14. References ........................................... 64 14. References ........................................... 67
14.1. Normative References ............................... 64 14.1. Normative References ............................... 67
14.2. Informative References ............................. 66 14.2. Informative References ............................. 68
15. Authors' Addresses ................................... 66 15. Authors' Addresses ................................... 69
16. Full Copyright Statement ............................. 67 16. Full Copyright Statement ............................. 70
17. Intellectual Property Notice ......................... 67 17. Intellectual Property Notice ......................... 71
18. IANA Considerations ................................ 68 18. IANA Considerations ................................ 71
18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 68 18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 71
1. Introduction 1. Introduction
This memo defines a portion of the Management Information This memo defines a portion of the Management Information
Base (MIB) for use with network management protocols in the Base (MIB) for use with network management protocols in the
Internet community. In particular, it describes managed Internet community. In particular, it describes managed
objects for modeling a Multi-Protocol Label Switching objects for modeling a Multi-Protocol Label Switching
(MPLS) [RFC3031] based traffic engineering. This MIB module (MPLS) [RFC3031] based traffic engineering. This MIB module
should be used in conjunction with the companion document should be used in conjunction with the companion document
[LSRMIB] for MPLS based traffic engineering configuration [LSRMIB] for MPLS based traffic engineering configuration
skipping to change at page 13, line 13 skipping to change at line 591
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
IndexIntegerNextFree IndexIntegerNextFree
FROM DIFFSERV-MIB FROM DIFFSERV-MIB
InetAddressPrefixLength InetAddressPrefixLength
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
; ;
mplsTeStdMIB MODULE-IDENTITY mplsTeStdMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"200308061200Z" -- 06 August 2003 12:00:00 GMT "200310191200Z" -- 19 October 2003 12:00:00 GMT
ORGANIZATION ORGANIZATION
"Multiprotocol Label Switching (MPLS) Working Group" "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Cheenu Srinivasan " Cheenu Srinivasan
Bloomberg L.P. Bloomberg 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 13, line 50 skipping to change at line 628
al, RFC 3209, December 2001 al, RFC 3209, December 2001
2. Constraint-Based LSP Setup using LDP, Jamoussi 2. Constraint-Based LSP Setup using LDP, Jamoussi
(Editor), RFC 3212, January 2002 (Editor), RFC 3212, January 2002
3. Requirements for Traffic Engineering Over MPLS, 3. Requirements for Traffic Engineering Over MPLS,
Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M.,
and J. McManus, RFC 2702, September 1999" and J. McManus, RFC 2702, September 1999"
-- 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 draft version issued as part of RFC XXXX." "Initial draft version issued as part of RFC XXXX."
::= { mplsStdMIB 3 }
::= { mplsStdMIB XXX } -- Please see IANA considerations section
-- the requested mplsStdMIB subId is 3.
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- traps -- traps
mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeStdMIB 0 } mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeStdMIB 0 }
-- tables, scalars -- tables, scalars
mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeStdMIB 1 } mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeStdMIB 1 }
mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeStdMIB 2 } mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeStdMIB 2 }
-- conformance -- conformance
mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeStdMIB 3 } mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeStdMIB 3 }
skipping to change at page 15, line 34 skipping to change at line 710
means no throttling is applied and events may be means no throttling is applied and events may be
notified at the rate at which they occur." notified at the rate at which they occur."
DEFVAL { 0 } DEFVAL { 0 }
::= { mplsTeScalars 5 } ::= { mplsTeScalars 5 }
-- End of MPLS Tunnel scalars. -- End of MPLS Tunnel scalars.
-- MPLS tunnel table. -- MPLS tunnel table.
mplsTunnelIndexNext OBJECT-TYPE mplsTunnelIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree SYNTAX IndexIntegerNextFree (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an unused value for "This object contains an unused value for
mplsTunnelIndex, or a zero to indicate mplsTunnelIndex, or a zero to indicate
that none exist. that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsTunnelIndex.
Note that this object offers an unused value Note that this object offers an unused value
for an mplsTunnelIndex value at the ingress for an mplsTunnelIndex value at the ingress
side of a tunnel. At other LSRs the value side of a tunnel. At other LSRs the value
of mplsTunnelIndex SHOULD be taken from the of mplsTunnelIndex SHOULD be taken from the
value signaled by the MPLS signaling protocol. value signaled by the MPLS signaling protocol.
" "
::= { mplsTeObjects 1 } ::= { mplsTeObjects 1 }
mplsTunnelTable OBJECT-TYPE mplsTunnelTable OBJECT-TYPE
skipping to change at page 17, line 48 skipping to change at line 826
mplsTunnelIndex OBJECT-TYPE mplsTunnelIndex OBJECT-TYPE
SYNTAX MplsTunnelIndex SYNTAX MplsTunnelIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies a set of tunnel instances "Uniquely identifies a set of tunnel instances
between a pair of ingress and egress LSRs. between a pair of ingress and egress LSRs.
Managers should obtain new values for row Managers should obtain new values for row
creation in this table by reading creation in this table by reading
mplsTunnelIndexNextFree. When mplsTunnelIndexNext. When
the MPLS signalling protocol is rsvp(2) this value the MPLS signalling protocol is rsvp(2) this value
SHOULD be equal to the value signaled in the SHOULD be equal to the value signaled in the
Tunnel Id of the Session object. When the MPLS Tunnel Id of the Session object. When the MPLS
signalling protocol is crldp(3) this value signalling protocol is crldp(3) this value
SHOULD be equal to the value signaled in the SHOULD be equal to the value signaled in the
LSP ID. LSP ID."
"
::= { mplsTunnelEntry 1 } ::= { mplsTunnelEntry 1 }
mplsTunnelInstance OBJECT-TYPE mplsTunnelInstance OBJECT-TYPE
SYNTAX MplsTunnelInstanceIndex SYNTAX MplsTunnelInstanceIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies a particular instance of a "Uniquely identifies a particular instance of a
tunnel between a pair of ingress and egress LSRs. tunnel between a pair of ingress and egress LSRs.
It is useful to identify multiple instances of It is useful to identify multiple instances of
skipping to change at page 31, line 10 skipping to change at line 1485
DESCRIPTION DESCRIPTION
"Primary index into this table identifying a "Primary index into this table identifying a
particular explicit route object." particular explicit route object."
::= { mplsTunnelHopEntry 1 } ::= { mplsTunnelHopEntry 1 }
mplsTunnelHopPathOptionIndex OBJECT-TYPE mplsTunnelHopPathOptionIndex OBJECT-TYPE
SYNTAX MplsPathIndex SYNTAX MplsPathIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Secondary index into this table identifying a "Tertiary index into this table identifying a
particular group of hops representing a particular particular group of hops representing a particular
configured path. This is otherwise known as a path configured path. This is otherwise known as a path
option." option."
::= { mplsTunnelHopEntry 2 } ::= { mplsTunnelHopEntry 2 }
mplsTunnelHopIndex OBJECT-TYPE mplsTunnelHopIndex OBJECT-TYPE
SYNTAX MplsPathIndex SYNTAX MplsPathIndex
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 36, line 36 skipping to change at line 1762
mplsTunnelResourceIndex OBJECT-TYPE mplsTunnelResourceIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..2147483647) SYNTAX Unsigned32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Uniquely identifies this row." "Uniquely identifies this row."
::= { mplsTunnelResourceEntry 1 } ::= { mplsTunnelResourceEntry 1 }
mplsTunnelResourceMaxRate OBJECT-TYPE mplsTunnelResourceMaxRate OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX MplsBitRate
UNITS "bits per second" UNITS "kilobits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum rate in bits/second. Note that setting "The maximum rate in bits/second. Note that setting
mplsTunnelResourceMaxRate, mplsTunnelResourceMaxRate,
mplsTunnelResourceMeanRate, and mplsTunnelResourceMeanRate, and
mplsTunnelResourceMaxBurstSize to 0 indicates best- mplsTunnelResourceMaxBurstSize to 0 indicates best-
effort treatment. effort treatment.
This object is copied to an instance of This object is copied to an instance of
skipping to change at page 37, line 9 skipping to change at line 1785
mplsInSegmentTrafficParamPtr." mplsInSegmentTrafficParamPtr."
REFERENCE REFERENCE
"Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS
Label Switch Router Management Information Base, Label Switch Router Management Information Base,
Internet Draft <draft-ietf-mpls-lsr-mib-10.txt>, Internet Draft <draft-ietf-mpls-lsr-mib-10.txt>,
June 2003." June 2003."
::= { mplsTunnelResourceEntry 2 } ::= { mplsTunnelResourceEntry 2 }
mplsTunnelResourceMeanRate OBJECT-TYPE mplsTunnelResourceMeanRate OBJECT-TYPE
SYNTAX MplsBitRate SYNTAX MplsBitRate
UNITS "bits per second" UNITS "kilobits per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is copied into an instance of "This object is copied into an instance of
mplsTrafficParamMeanRate in the mplsTrafficParamMeanRate in the
mplsTrafficParamTable. The OID of this table entry mplsTrafficParamTable. The OID of this table entry
is then copied into the corresponding is then copied into the corresponding
mplsInSegmentTrafficParamPtr. mplsInSegmentTrafficParamPtr.
When resource allocation is performed as requested When resource allocation is performed as requested
skipping to change at page 68, line 15 skipping to change at line 3325
The IETF invites any interested party to bring to its The IETF invites any interested party to bring to its
attention any copyrights, patents or patent applications, attention any copyrights, patents or patent applications,
or other proprietary rights that may cover technology that or other proprietary rights that may cover technology that
may be required to practice this standard. Please address may be required to practice this standard. Please address
the information to the IETF Executive Director. the information to the IETF Executive Director.
18. IANA Considerations 18. 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 [MPLSTCMIB], 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].
18.1. IANA Considerations for MPLS-TE-STD-MIB 18.1. IANA Considerations for MPLS-TE-STD-MIB
The IANA is requested to assign { mplsStdMIB 3 } to the The IANA is requested to assign { mplsStdMIB 3 } to the
MPLS-TE-STD-MIB module specified in this document. MPLS-TE-STD-MIB module specified in this document.
 End of changes. 

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