draft-ietf-mpls-te-mib-13.txt		draft-ietf-mpls-te-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) Traffic Engineering		Multiprotocol Label Switching (MPLS) Traffic Engineering
	Management Information Base		Management Information Base
	draft-ietf-mpls-te-mib-13.txt		draft-ietf-mpls-te-mib-14.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 line 70		skipping to change at page 2, line 22
	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 .............................. 65		12. Security Considerations .............................. 62
	13. Acknowledgments ...................................... 67		13. Acknowledgments ...................................... 63
	14. References ........................................... 67		14. References ........................................... 64
	14.1. Normative References ............................... 67		14.1. Normative References ............................... 64
	14.2. Informative References ............................. 68		14.2. Informative References ............................. 65
	15. Authors' Addresses ................................... 69		15. Authors' Addresses ................................... 65
	16. Full Copyright Statement ............................. 70		16. Full Copyright Statement ............................. 66
	17. Intellectual Property Notice ......................... 71		17. Intellectual Property Notice ......................... 66
	18. IANA Considerations ................................ 71		18. IANA Considerations ................................ 67
	18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 71		18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 67
	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 line 996		skipping to change at page 21, line 21
	DESCRIPTION		DESCRIPTION
	"This variable points to a row in the mplsXCTable.		"This variable points to a row in the mplsXCTable.
	This table identifies the segments that compose		This table identifies the segments that compose
	this tunnel, their characteristics, and		this tunnel, their characteristics, and
	relationships to each other. A value of zeroDotZero		relationships to each other. A value of zeroDotZero
	indicates that no LSP has been associated with this		indicates that no LSP has been associated with this
	tunnel yet."		tunnel yet."
	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-14.txt>,
	June 2003."		June 2003."
	DEFVAL { zeroDotZero }		DEFVAL { zeroDotZero }
	::= { mplsTunnelEntry 11 }		::= { mplsTunnelEntry 11 }
	mplsTunnelSignallingProto OBJECT-TYPE		mplsTunnelSignallingProto OBJECT-TYPE
	SYNTAX INTEGER {		SYNTAX INTEGER {
	none(1),		none(1),
	rsvp(2),		rsvp(2),
	crldp(3),		crldp(3),
	other(4)		other(4)
	skipping to change at line 1485		skipping to change at page 31, line 11
	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
	"Tertiary index into this table identifying a		"Secondary 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
	"Secondary index into this table identifying a		"Tertiary index into this table identifying a
	particular hop."		particular hop."
	::= { mplsTunnelHopEntry 3 }		::= { mplsTunnelHopEntry 3 }
	mplsTunnelHopAddrType OBJECT-TYPE		mplsTunnelHopAddrType OBJECT-TYPE
	SYNTAX TeHopAddressType		SYNTAX TeHopAddressType
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION "The Hop Address Type of this tunnel hop.		DESCRIPTION "The Hop Address Type of this tunnel hop.
	The value of this object cannot be changed		The value of this object cannot be changed
	skipping to change at line 1770		skipping to change at page 36, line 47
	mplsTunnelResourceMaxRate OBJECT-TYPE		mplsTunnelResourceMaxRate OBJECT-TYPE
	SYNTAX MplsBitRate		SYNTAX MplsBitRate
	UNITS "kilobits 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
	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 <draft-ietf-mpls-lsr-mib-10.txt>,
	June 2003."
	::= { mplsTunnelResourceEntry 2 }		::= { mplsTunnelResourceEntry 2 }
	mplsTunnelResourceMeanRate OBJECT-TYPE		mplsTunnelResourceMeanRate OBJECT-TYPE
	SYNTAX MplsBitRate		SYNTAX MplsBitRate
	UNITS "kilobits 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
	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 <draft-ietf-mpls-lsr-mib-10.txt>,
	June 2003."
	::= { mplsTunnelResourceEntry 3 }		::= { mplsTunnelResourceEntry 3 }
	mplsTunnelResourceMaxBurstSize OBJECT-TYPE		mplsTunnelResourceMaxBurstSize OBJECT-TYPE
	SYNTAX MplsBurstSize		SYNTAX MplsBurstSize
	UNITS "bytes"		UNITS "bytes"
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The maximum burst size in bytes. This object is		"The maximum burst size in bytes."
	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 <draft-ietf-mpls-lsr-mib-10.txt>,
	June 2003."
	::= { mplsTunnelResourceEntry 4 }		::= { mplsTunnelResourceEntry 4 }
	mplsTunnelResourceMeanBurstSize OBJECT-TYPE		mplsTunnelResourceMeanBurstSize OBJECT-TYPE
	SYNTAX MplsBurstSize		SYNTAX MplsBurstSize
	UNITS "bytes"		UNITS "bytes"
	MAX-ACCESS read-create		MAX-ACCESS read-create
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"The mean burst size in bytes. The implementations		"The mean burst size in bytes. The implementations
	which do not implement this variable must return		which do not implement this variable must return
	skipping to change at line 2602		skipping to change at page 52, line 46
	GROUP mplsTeNotificationGroup		GROUP mplsTeNotificationGroup
	DESCRIPTION "This group is mandatory for those implementations		DESCRIPTION "This group is mandatory for those implementations
	which can implement the notifications		which can implement the notifications
	contained in this group."		contained in this group."
	OBJECT mplsTunnelRowStatus		OBJECT mplsTunnelRowStatus
	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 mplsTunnelHopRowStatus		OBJECT mplsTunnelHopRowStatus
	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 mplsTunnelHopStorageType
	MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."
	OBJECT mplsTunnelCRLDPResRowStatus		OBJECT mplsTunnelCRLDPResRowStatus
	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 mplsTunnelCRLDPResStorageType
	MIN-ACCESS read-only
	DESCRIPTION "Write access is not required."
	::= { mplsTeCompliances 1 }		::= { mplsTeCompliances 1 }
	-- Compliance requirement for read-only implementations.		-- Compliance requirement for read-only implementations.
	mplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE		mplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"Compliance requirement for implementations that only		"Compliance requirement for implementations that only
	provide read-only support for MPLS-TE-STD-MIB.		provide read-only support for MPLS-TE-STD-MIB.
	skipping to change at line 3226		skipping to change at page 65, line 15
	[TCMIB] Nadeau, T. and J. Cucchiara (Editors),		[TCMIB] Nadeau, T. and J. Cucchiara (Editors),
	"Definition of Textual Conventions and		"Definition of Textual Conventions and
	OBJECT-IDENTITIES for Multi-Protocol Label		OBJECT-IDENTITIES for Multi-Protocol Label
	Switching (MPLS) Management", Internet Draft		Switching (MPLS) Management", Internet Draft
	<draft-ietf-mpls-tc-mib-08.txt>, June 2003.		<draft-ietf-mpls-tc-mib-08.txt>, June 2003.
	[LSRMIB] Srinivasan, C., Viswanathan, A. and T.		[LSRMIB] Srinivasan, C., Viswanathan, A. and T.
	Nadeau, "MPLS Multiprotocol Label Switching		Nadeau, "MPLS Multiprotocol Label Switching
	(MPLS) Label Switch Router Management		(MPLS) Label Switch Router Management
	Information Base ", Internet Draft <draft-		Information Base ", Internet Draft <draft-
	ietf-mpls-lsr-mib-10.txt>, June 2003.		ietf-mpls-lsr-mib-14.txt>, November 2003.
	[CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP		[CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP
	Setup using LDP", RFC 3212, January 2002.		Setup using LDP", RFC 3212, January 2002.
	14.2. Informative References		14.2. Informative References
	[RFC2026] S. Bradner, "The Internet Standards Process		[RFC2026] S. Bradner, "The Internet Standards Process
	-- Revision 3", RFC 2026, October 1996.		-- Revision 3", RFC 2026, October 1996.
	[RFC2401] Kent, S., and R. Atkinson, "Security		[RFC2401] Kent, S., and R. Atkinson, "Security
	skipping to change at line 3325		skipping to change at page 67, line 17
	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. 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].
	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/