Diff: draft-ietf-mpls-telink-mib-06.txt - draft-ietf-mpls-telink-mib-07.txt

	draft-ietf-mpls-telink-mib-06.txt	draft-ietf-mpls-telink-mib-07.txt

	Network Working Group Martin Dubuc	Network Working Group Martin Dubuc
	Internet Draft	Internet Draft
	Category: Standards Track Sudheer Dharanikota	Category: Standards Track Sudheer Dharanikota

	Expires: August 2004	Expires: November 2004
	Thomas D. Nadeau	Thomas D. Nadeau
	Cisco Systems	Cisco Systems

	Jonathan P. Lang	Jonathan P. Lang
	Rincon Networks	Rincon Networks


	February 2004	May 2004

	Traffic Engineering Link Management Information Base	Traffic Engineering Link Management Information Base


	draft-ietf-mpls-telink-mib-06.txt	draft-ietf-mpls-telink-mib-07.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 Internet Engineering	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that other	Task Force (IETF), its areas, and its working groups. Note that other
	groups may also distribute working documents as Internet-Drafts.	groups may also distribute working documents as Internet-Drafts.


	skipping to change at page 2, line 27	skipping to change at page 2, line 27
	6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5	6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5
	7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5	7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5
	8. Application of the Interfaces Group to TE Links . . . . . . . . . 9	8. Application of the Interfaces Group to TE Links . . . . . . . . . 9
	8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9	8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9
	8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11	8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11
	8.3 Applicability of ifRcvAddressTable . . . . . . . . . . . . . . . 13	8.3 Applicability of ifRcvAddressTable . . . . . . . . . . . . . . . 13
	9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13	9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13
	10. Intellectual Property Considerations . . . . . . . . . . . . . . 50	10. Intellectual Property Considerations . . . . . . . . . . . . . . 50
	11. Security Considerations . . . . . . . . . . . . . . . . . . . . 51	11. Security Considerations . . . . . . . . . . . . . . . . . . . . 51
	12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 52	12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 52

	13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 52	13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 52
	13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 53	13.1 IANA Considerations for TE-LINK-STD-MIB . . . . . . . . . . . . 52
	13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53	14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
	14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54	14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 53
	15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 54	14.2 Informative References . . . . . . . . . . . . . . . . . . . . 54
		15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54
		16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 55

	1. The Internet-Standard Management Framework	1. The Internet-Standard Management Framework

	For a detailed overview of the documents that describe the current	For a detailed overview of the documents that describe the current
	Internet-Standard Management Framework, please refer to section 7 of	Internet-Standard Management Framework, please refer to section 7 of
	RFC 3410 [RFC3410].	RFC 3410 [RFC3410].

	Managed objects are accessed via a virtual information store, termed	Managed objects are accessed via a virtual information store, termed
	the Management Information Base or MIB. MIB objects are generally	the Management Information Base or MIB. MIB objects are generally
	accessed through the Simple Network Management Protocol (SNMP).	accessed through the Simple Network Management Protocol (SNMP).
	Objects in the MIB are defined using the mechanisms defined in the	Objects in the MIB are defined using the mechanisms defined in the
	Structure of Management Information (SMI). This memo specifies a MIB	Structure of Management Information (SMI). This memo specifies a MIB
	module that is compliant to the SMIv2, which is described in STD 58,	module that is compliant to the SMIv2, which is described in STD 58,
	RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580	RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
	[RFC2580].	[RFC2580].

	2. Introduction	2. Introduction


	OSPF [OSPF], Generalized MPLS (GMPLS) [RFC3471] and the Link	OSPF [RFC3630], Generalized MPLS (GMPLS) [RFC3471] and the Link
	Management Protocol (LMP) [LMP] use the concept of traffic	Management Protocol (LMP) [LMP] use the concept of traffic
	engineering (TE) links to abstract link properties. The effect of	engineering (TE) links to abstract link properties. The effect of
	this approach is the reduction of the amount of routing information	this approach is the reduction of the amount of routing information
	exchanged in the network, which improves routing scalability. In	exchanged in the network, which improves routing scalability. In
	addition, the use of TE link allows the implementation of new	addition, the use of TE link allows the implementation of new
	capabilities such as link protection.	capabilities such as link protection.

	We present in this document a MIB module that can be used to manage	We present in this document a MIB module that can be used to manage
	TE links and their extension, the bundled link. This MIB module	TE links and their extension, the bundled link. This MIB module
	enables both the configuration and the performance monitoring of TE	enables both the configuration and the performance monitoring of TE

	skipping to change at page 13, line 32	skipping to change at page 13, line 36
	TEXTUAL-CONVENTION, RowStatus, StorageType	TEXTUAL-CONVENTION, RowStatus, StorageType
	FROM SNMPv2-TC	FROM SNMPv2-TC

	InterfaceIndexOrZero, ifIndex	InterfaceIndexOrZero, ifIndex
	FROM IF-MIB	FROM IF-MIB

	InetAddressType, InetAddress	InetAddressType, InetAddress
	FROM INET-ADDRESS-MIB;	FROM INET-ADDRESS-MIB;

	teLinkStdMIB MODULE-IDENTITY	teLinkStdMIB MODULE-IDENTITY

	LAST-UPDATED "200402011200Z" -- 1 February 2004 12:00:00 EST	LAST-UPDATED "200405141200Z" -- 14 May 2004 12:00:00 EST
	ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"	ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
	CONTACT-INFO	CONTACT-INFO
	" Martin Dubuc	" Martin Dubuc

	Email: dubuc.consulting@rogers.com	Email: mdubuc@ncf.ca

	Sudheer Dharanikota	Sudheer Dharanikota
	Email: sudheer@ieee.org	Email: sudheer@ieee.org

	Thomas D. Nadeau	Thomas D. Nadeau
	Email: tnadeau@cisco.com	Email: tnadeau@cisco.com

	Jonathan P. Lang	Jonathan P. Lang
	Email: jplang@ieee.org	Email: jplang@ieee.org


	Comments about this document should be emailed directly to	Comments about this document should be emailed directly to
	the MPLS working group mailing list at mpls@uu.net."	the MPLS working group mailing list at mpls@uu.net."

	DESCRIPTION	DESCRIPTION
	"Copyright (C) 2004 The Internet Society. This version of	"Copyright (C) 2004 The Internet Society. This version of
	this MIB module is part of RFC XXXX; see the RFC	this MIB module is part of RFC XXXX; see the RFC
	itself for full legal notices.	itself for full legal notices.

	This MIB module contains managed object definitions for	This MIB module contains managed object definitions for
	MPLS traffic engineering links as defined in	MPLS traffic engineering links as defined in

	skipping to change at page 14, line 13	skipping to change at page 14, line 18
	"Copyright (C) 2004 The Internet Society. This version of	"Copyright (C) 2004 The Internet Society. This version of
	this MIB module is part of RFC XXXX; see the RFC	this MIB module is part of RFC XXXX; see the RFC
	itself for full legal notices.	itself for full legal notices.

	This MIB module contains managed object definitions for	This MIB module contains managed object definitions for
	MPLS traffic engineering links as defined in	MPLS traffic engineering links as defined in
	'Link Bundling in MPLS Traffic Engineering'."	'Link Bundling in MPLS Traffic Engineering'."

	-- Revision history.	-- Revision history.
	REVISION	REVISION

	"200402011200Z" -- 1 February 2004 12:00:00 EST	"200405141200Z" -- 14 May 2004 12:00:00 EST
	DESCRIPTION	DESCRIPTION
	"Initial version published as RFC xxxx (to be assigned by RFC	"Initial version published as RFC xxxx (to be assigned by RFC
	Editor)"	Editor)"
	::= { transmission xxx } -- To be assigned by IANA.	::= { transmission xxx } -- To be assigned by IANA.
	-- Request to assign 200 which is	-- Request to assign 200 which is
	-- ifType value for teLink.	-- ifType value for teLink.

	-- Textual Conventions	-- Textual Conventions

	TeLinkBandwidth ::= TEXTUAL-CONVENTION	TeLinkBandwidth ::= TEXTUAL-CONVENTION
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This type is used to represent link bandwidth in bps. This	"This type is used to represent link bandwidth in bps. This
	value is represented using a 4 octet IEEE floating point	value is represented using a 4 octet IEEE floating point

	format."	format. The floating point representation is not used to
		represent fractional value but rather to allow
		specification of large numbers that cannot be expressed
		with 32-bit integers."
	REFERENCE	REFERENCE
	"IEEE Standard for Binary Floating-Point Arithmetic,	"IEEE Standard for Binary Floating-Point Arithmetic,
	Standard 754-1985"	Standard 754-1985"
	SYNTAX OCTET STRING (SIZE(4))	SYNTAX OCTET STRING (SIZE(4))

	TeLinkPriority ::= TEXTUAL-CONVENTION	TeLinkPriority ::= TEXTUAL-CONVENTION
	DISPLAY-HINT "d"	DISPLAY-HINT "d"
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This type is used to represent a priority. Each connection is	"This type is used to represent a priority. Each connection is

	skipping to change at page 19, line 44	skipping to change at page 20, line 4
	-- RFC Editor to fill in RFC number that will be assigned to	-- RFC Editor to fill in RFC number that will be assigned to
	-- [GMPLS-OSPF]	-- [GMPLS-OSPF]
	::= { teLinkEntry 7 }	::= { teLinkEntry 7 }

	teLinkResourceClass OBJECT-TYPE	teLinkResourceClass OBJECT-TYPE
	SYNTAX Unsigned32	SYNTAX Unsigned32
	MAX-ACCESS read-create	MAX-ACCESS read-create
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This attribute specifies the TE link resource class.	"This attribute specifies the TE link resource class.


	The resource class is a 32 bit bitfield. The resource class for	The resource class is a 32 bit bitfield. The resource class for
	a link bundle is derived from the resource class of its	a link bundle is derived from the resource class of its
	TE links. All TE links within a link bundle must have the	TE links. All TE links within a link bundle must have the
	same resource class. Encoding of the resource class is described	same resource class. Encoding of the resource class is described
	in the 'Traffic Engineering Extensions to OSPF Version 2'	in the 'Traffic Engineering Extensions to OSPF Version 2'
	document."	document."
	REFERENCE	REFERENCE
	"Link Bundling in MPLS Traffic Engineering, RFC xxxx and	"Link Bundling in MPLS Traffic Engineering, RFC xxxx and

	Traffic Engineering Extensions to OSPF Version 2, RFC xxxx"	Traffic Engineering (TE) Extensions to OSPF Version 2,
		RFC 3630"
	-- RFC Editor to fill in RFC number that will be assigned to	-- RFC Editor to fill in RFC number that will be assigned to

	-- [BUNDLING] and [OSPF]	-- [BUNDLING]
	::= { teLinkEntry 8 }	::= { teLinkEntry 8 }

	teLinkIncomingIfId OBJECT-TYPE	teLinkIncomingIfId OBJECT-TYPE
	SYNTAX Integer32 (0..2147483647)	SYNTAX Integer32 (0..2147483647)
	MAX-ACCESS read-create	MAX-ACCESS read-create
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"For unnumbered links, the incoming interface is set to the	"For unnumbered links, the incoming interface is set to the
	outgoing interface identifier chosen by the neighboring LSR	outgoing interface identifier chosen by the neighboring LSR
	for the reverse link corresponding to this TE link. If the	for the reverse link corresponding to this TE link. If the

	skipping to change at page 29, line 17	skipping to change at page 29, line 26
	teLinkBandwidthPriority OBJECT-TYPE	teLinkBandwidthPriority OBJECT-TYPE
	SYNTAX TeLinkPriority	SYNTAX TeLinkPriority
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This attribute specifies the priority. A value of 0 is valid	"This attribute specifies the priority. A value of 0 is valid
	as specified in the 'Traffic Engineering Extensions to OSPF	as specified in the 'Traffic Engineering Extensions to OSPF
	Version 2' document."	Version 2' document."
	REFERENCE	REFERENCE
	"OSPF Extensions in Support of Generalized MPLS, RFC xxxx and	"OSPF Extensions in Support of Generalized MPLS, RFC xxxx and

	Traffic Engineering Extensions to OSPF Version 2, RFC xxxx"	Traffic Engineering (TE) Extensions to OSPF Version 2,
		RFC 3630"
	-- RFC Editor to fill in RFC number that will be assigned to	-- RFC Editor to fill in RFC number that will be assigned to

	-- [GMPLS-OSPF] and [OSPF]	-- [GMPLS-OSPF]
	::= { teLinkBandwidthEntry 1 }	::= { teLinkBandwidthEntry 1 }

	teLinkBandwidthUnreserved OBJECT-TYPE	teLinkBandwidthUnreserved OBJECT-TYPE
	SYNTAX TeLinkBandwidth	SYNTAX TeLinkBandwidth
	UNITS "bps"	UNITS "bps"
	MAX-ACCESS read-only	MAX-ACCESS read-only
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This attribute specifies the TE link unreserved	"This attribute specifies the TE link unreserved
	bandwidth at priority p. It is the sum of the unreserved	bandwidth at priority p. It is the sum of the unreserved

	skipping to change at page 29, line 47	skipping to change at page 30, line 9
	::= { teLinkBandwidthEntry 2 }	::= { teLinkBandwidthEntry 2 }

	teLinkBandwidthRowStatus OBJECT-TYPE	teLinkBandwidthRowStatus OBJECT-TYPE
	SYNTAX RowStatus	SYNTAX RowStatus
	MAX-ACCESS read-create	MAX-ACCESS read-create
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This variable is used to create, modify, and/or	"This variable is used to create, modify, and/or
	delete a row in this table. No read-create object	delete a row in this table. No read-create object
	can be modified when teLinkBandwidthRowStatus is active(1)."	can be modified when teLinkBandwidthRowStatus is active(1)."

	::= { teLinkBandwidthEntry 4 }	::= { teLinkBandwidthEntry 3 }

	teLinkBandwidthStorageType OBJECT-TYPE	teLinkBandwidthStorageType OBJECT-TYPE
	SYNTAX StorageType	SYNTAX StorageType
	MAX-ACCESS read-create	MAX-ACCESS read-create
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"The storage type for this conceptual row in the	"The storage type for this conceptual row in the
	teLinkBandwidthTable. Conceptual rows having the value	teLinkBandwidthTable. Conceptual rows having the value
	'permanent' need not allow write-access to any	'permanent' need not allow write-access to any
	columnar object in the row."	columnar object in the row."

	::= { teLinkBandwidthEntry 5 }	::= { teLinkBandwidthEntry 4 }

	-- End of teLinkBandwidthTable	-- End of teLinkBandwidthTable

	-- Component Link Table	-- Component Link Table

	componentLinkTable OBJECT-TYPE	componentLinkTable OBJECT-TYPE
	SYNTAX SEQUENCE OF ComponentLinkEntry	SYNTAX SEQUENCE OF ComponentLinkEntry
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION

	skipping to change at page 38, line 24	skipping to change at page 38, line 33
	componentLinkBandwidthPriority OBJECT-TYPE	componentLinkBandwidthPriority OBJECT-TYPE
	SYNTAX TeLinkPriority	SYNTAX TeLinkPriority
	MAX-ACCESS not-accessible	MAX-ACCESS not-accessible
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This attribute specifies the priority. A value of 0 is valid	"This attribute specifies the priority. A value of 0 is valid
	as specified in the 'Traffic Engineering Extensions to OSPF	as specified in the 'Traffic Engineering Extensions to OSPF
	Version 2' document."	Version 2' document."
	REFERENCE	REFERENCE
	"OSPF Extensions in Support of Generalized MPLS, RFC xxxx and	"OSPF Extensions in Support of Generalized MPLS, RFC xxxx and

	Traffic Engineering Extensions to OSPF Version 2, RFC xxxx"	Traffic Engineering (TE) Extensions to OSPF Version 2,
		RFC 3630"
	-- RFC Editor to fill in RFC number that will be assigned to	-- RFC Editor to fill in RFC number that will be assigned to

	-- [GMPLS-OSPF] and [OSPF]	-- [GMPLS-OSPF]
	::= { componentLinkBandwidthEntry 1 }	::= { componentLinkBandwidthEntry 1 }

	componentLinkBandwidthUnreserved OBJECT-TYPE	componentLinkBandwidthUnreserved OBJECT-TYPE
	SYNTAX TeLinkBandwidth	SYNTAX TeLinkBandwidth
	UNITS "bps"	UNITS "bps"
	MAX-ACCESS read-only	MAX-ACCESS read-only
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This attribute specifies the component link unreserved	"This attribute specifies the component link unreserved
	bandwidth at priority p."	bandwidth at priority p."

	skipping to change at page 39, line 4	skipping to change at page 39, line 14

	componentLinkBandwidthRowStatus OBJECT-TYPE	componentLinkBandwidthRowStatus OBJECT-TYPE
	SYNTAX RowStatus	SYNTAX RowStatus
	MAX-ACCESS read-create	MAX-ACCESS read-create
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"This variable is used to create, modify, and/or	"This variable is used to create, modify, and/or
	delete a row in this table. No read-create object can	delete a row in this table. No read-create object can
	be modified when componentLinkBandwidthRowStatus is	be modified when componentLinkBandwidthRowStatus is
	active(1)."	active(1)."

	::= { componentLinkBandwidthEntry 4 }	::= { componentLinkBandwidthEntry 3 }

	componentLinkBandwidthStorageType OBJECT-TYPE	componentLinkBandwidthStorageType OBJECT-TYPE
	SYNTAX StorageType	SYNTAX StorageType
	MAX-ACCESS read-create	MAX-ACCESS read-create
	STATUS current	STATUS current
	DESCRIPTION	DESCRIPTION
	"The storage type for this conceptual row in the	"The storage type for this conceptual row in the
	componentLinkBandwidthTable. Conceptual rows	componentLinkBandwidthTable. Conceptual rows
	having the value 'permanent' need not allow write-access	having the value 'permanent' need not allow write-access
	to any columnar object in the row."	to any columnar object in the row."

	::= { componentLinkBandwidthEntry 5 }	::= { componentLinkBandwidthEntry 4 }

	-- End of componentLinkBandwidthTable	-- End of componentLinkBandwidthTable

	-- Module compliance	-- Module compliance

	teLinkCompliances	teLinkCompliances
	OBJECT IDENTIFIER ::= { teLinkConformance 1 }	OBJECT IDENTIFIER ::= { teLinkConformance 1 }

	teLinkGroups	teLinkGroups
	OBJECT IDENTIFIER ::= { teLinkConformance 2 }	OBJECT IDENTIFIER ::= { teLinkConformance 2 }

	skipping to change at page 51, line 5	skipping to change at page 51, line 7
	obtain a general license or permission for the use of such	obtain a general license or permission for the use of such
	proprietary rights by implementers or users of this specification can	proprietary rights by implementers or users of this specification can
	be obtained from the IETF Secretariat.	be obtained from the IETF Secretariat.

	The IETF invites any interested party to bring to its attention any	The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary	copyrights, patents or patent applications, or other proprietary
	rights which may cover technology that may be required to practice	rights which may cover technology that may be required to practice
	this standard. Please address the information to the IETF Executive	this standard. Please address the information to the IETF Executive
	Director.	Director.


		By submitting this Internet Draft, we certify that any applicable
		patent or other IPR claims of which we are aware have been disclosed,
		and ant of which we become aware will be disclosed, in accordance
		with RFC 3668.

	11. Security Considerations	11. Security Considerations

	There are a number of management objects defined in this MIB module	There are a number of management objects defined in this MIB module
	with a MAX-ACCESS clause of read-write and/or read-create. Such	with a MAX-ACCESS clause of read-write and/or read-create. Such
	objects may be considered sensitive or vulnerable in some network	objects may be considered sensitive or vulnerable in some network
	environments. The support for SET operations in a non-secure	environments. The support for SET operations in a non-secure
	environment without proper protection can have a negative effect on	environment without proper protection can have a negative effect on
	network operations. These are the tables and objects and their	network operations. These are the tables and objects and their
	sensitivity/vulnerability:	sensitivity/vulnerability:


	skipping to change at page 52, line 10	skipping to change at page 52, line 15
	responsibility to ensure that the SNMP entity giving access to an	responsibility to ensure that the SNMP entity giving access to an
	instance of this MIB module is properly configured to give access to	instance of this MIB module is properly configured to give access to
	the objects only to those principals (users) that have legitimate	the objects only to those principals (users) that have legitimate
	rights to indeed GET or SET (change/create/delete) them.	rights to indeed GET or SET (change/create/delete) them.

	12. Acknowledgments	12. Acknowledgments

	The authors would like to acknowledge the contribution of Dmitry	The authors would like to acknowledge the contribution of Dmitry
	Ryumkin.	Ryumkin.


	13. References	13. IANA Considerations


	13.1. Normative References	The following "IANA Considerations" subsection requests IANA for a
		new assignment. New assignments can only be made via Standards Action
		as specified in [RFC2434].

		13.1. IANA Considerations for TE-LINK-STD-MIB

		TE-LINK-STD-MIB should be rooted under the transmission subtree. The
		IANA is requested to assign { transmission TBD } to the TE-LINK-STD-
		MIB module specified in this document. The IANA is requested to use
		same number as the telink ifType.

		14. References

		14.1. Normative References

	[IEEE] IEEE, "IEEE Standard for Binary Floating-Point	[IEEE] IEEE, "IEEE Standard for Binary Floating-Point
	Arithmetic", Standard 754-1985, 1985	Arithmetic", Standard 754-1985, 1985
	(ISBN 1-5593-7653-8).	(ISBN 1-5593-7653-8).


		[RFC2026] Bradner, S., "The Internet Standards Process -
		Revision 3", RFC 2026, October 1996.

	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.	Requirement Levels", BCP 14, RFC 2119, March 1997.


		[RFC2434] Narten, T., Alverstrand, H., "Guidelines for Writing
		an IANA Considerations Section in RFCs", RFC 2434,
		October 1998.

	[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,	Management Information Version 2 (SMIv2)", STD 58,
	RFC 2578, April 1999.	RFC 2578, April 1999.

	[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,	[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
	J., Rose, M., and S. Waldbusser, "Textual Conventions	J., Rose, M., and S. Waldbusser, "Textual Conventions
	for SMIv2", STD 58, RFC 2579, April 1999.	for SMIv2", STD 58, RFC 2579, April 1999.

	[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,	[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
	J., Rose, M., and Waldbusser, S., "Conformance	J., Rose, M., and Waldbusser, S., "Conformance
	Statements for SMIv2", STD 58, RFC 2580, April 1999.	Statements for SMIv2", STD 58, RFC 2580, April 1999.

	[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces	[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
	Group MIB", RFC 2863, June 2000.	Group MIB", RFC 2863, June 2000.


		[RFC2914] Floyd, S., "Congestion Control Principles", RFC 2914,
		September 2000.

	[RFC3291] Daniele, M., Haberman, B., Routhier, S., and	[RFC3291] Daniele, M., Haberman, B., Routhier, S., and
	Shoenwaelder, J., "Textual Conventions for Internet	Shoenwaelder, J., "Textual Conventions for Internet
	Network Addresses", RFC 3291, May 2002.	Network Addresses", RFC 3291, May 2002.

	[RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L.,	[RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L.,
	Bernstein, G., Drake, J., Fan, Y., Kompella, K.,	Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
	Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,	Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
	Saha, D., Sharma, V., Swallow, G., and Tang, Z.,	Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
	"Generalized MPLS Signaling Functional Description",	"Generalized MPLS Signaling Functional Description",
	RFC 3471, January 2003.	RFC 3471, January 2003.


		[RFC3630] Katz, D., Kompella, K., and Yeung, D., "Traffic
		Engineering (TE) Extensions to OSPF Version 2",
		RFC 3630, September 2003.

		[RFC3667] Bradner, S., "IETF Rights in Contributions",
		RFC 3667, February 2004.

		[RFC3668] Bradner, S., "Intellectual Property Rights in IETF
		Technology", RFC 3668, February 2004.

	[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,	[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,
	"Link Bundling in MPLS Traffic Engineering",	"Link Bundling in MPLS Traffic Engineering",
	Internet Draft <draft-ietf-mpls-bundle-04.txt>,	Internet Draft <draft-ietf-mpls-bundle-04.txt>,
	July 2002.	July 2002.

	[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF	[GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF
	Extensions in Support of Generalized MPLS", Internet	Extensions in Support of Generalized MPLS", Internet
	Draft <draft-ietf-ccamp-ospf-gmpls-extensions-12.txt>,	Draft <draft-ietf-ccamp-ospf-gmpls-extensions-12.txt>,
	October 2003.	October 2003.


	skipping to change at page 53, line 26	skipping to change at page 54, line 17
	http://www.iana.org/assignments/ianaiftype-mib.	http://www.iana.org/assignments/ianaiftype-mib.

	[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,	[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
	Rekhter, Y., Berger, L., Saha, D.,	Rekhter, Y., Berger, L., Saha, D.,
	Basak, D., Sandick, H., Zinin, A.,	Basak, D., Sandick, H., Zinin, A.,
	Rajagopalan, B., and Ramamoorthi, S.,	Rajagopalan, B., and Ramamoorthi, S.,
	"Link Management Protocol",	"Link Management Protocol",
	Internet Draft <draft-ietf-ccamp-lmp-10.txt>,	Internet Draft <draft-ietf-ccamp-lmp-10.txt>,
	October 2003.	October 2003.


	[OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic
	Engineering Extensions to OSPF", Internet Draft
	<draft-katz-yeung-ospf-traffic-10.txt>, June 2003.

	[ROUTING] Kompella, K., Rekhter, Y., "Routing Extensions in	[ROUTING] Kompella, K., Rekhter, Y., "Routing Extensions in
	Support of Generalized MPLS", Internet Draft	Support of Generalized MPLS", Internet Draft
	<draft-ietf-ccamp-gmpls-routing-09.txt>, October 2003.	<draft-ietf-ccamp-gmpls-routing-09.txt>, October 2003.


	13.2. Informative References	14.2. Informative References

	[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,	[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
	"Introduction and Applicability Statements for	"Introduction and Applicability Statements for
	Internet-Standard Management Framework", RFC 3410,	Internet-Standard Management Framework", RFC 3410,
	December 2002.	December 2002.

	[GMPLS-ARCH] Ashwood-Smith, P., Awduche, D.,	[GMPLS-ARCH] Ashwood-Smith, P., Awduche, D.,
	Banarjee, A., Basak, D., Berger, L., Bernstein, G.,	Banarjee, A., Basak, D., Berger, L., Bernstein, G.,
	Dharanikota, S., Drake, J., Fan, Y., Fedyk, D.,	Dharanikota, S., Drake, J., Fan, Y., Fedyk, D.,
	Grammel, G., Guo, D., Kompella, K., Kullberg, A.,	Grammel, G., Guo, D., Kompella, K., Kullberg, A.,
	Lang, J., Liaw, Mannie, E., F., Nadeau, T., Ong, L.,	Lang, J., Liaw, Mannie, E., F., Nadeau, T., Ong, L.,
	Papadimitriou, D., Pendarakis, D., Rajagopalan, B.,	Papadimitriou, D., Pendarakis, D., Rajagopalan, B.,
	Rekhter, Y., Saha, D., Sandick, H., Sharma, V.,	Rekhter, Y., Saha, D., Sandick, H., Sharma, V.,
	Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J.,	Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J.,
	Zinin, A., "Generalized Multi-Protocol Label Switching	Zinin, A., "Generalized Multi-Protocol Label Switching
	(GMPLS) Architecture", Internet Draft	(GMPLS) Architecture", Internet Draft
	<draft-ietf-ccamp-gmpls-architecture-07.txt>,	<draft-ietf-ccamp-gmpls-architecture-07.txt>,
	May 2003.	May 2003.


	14. Authors' Addresses	15. Authors' Addresses

	Martin Dubuc Thomas D. Nadeau	Martin Dubuc Thomas D. Nadeau

	Email: dubuc.consulting@rogers.com Cisco Systems, Inc.	Email: mdubuc@ncf.ca Cisco Systems, Inc.
	300 Apollo Drive	300 Apollo Drive
	Chelmsford, MA 01824	Chelmsford, MA 01824
	Phone: +1-978-244-3051	Phone: +1-978-244-3051
	Email: tnadeau@cisco.com	Email: tnadeau@cisco.com

	Sudheer Dharanikota Jonathan P. Lang	Sudheer Dharanikota Jonathan P. Lang


	Email: sudheer@ieee.org Rincon Networks, Inc.	Email: sudheer@ieee.org Rincon Networks, Inc.
	110 El Paseo	110 El Paseo
	Santa Barbara, CA 93101	Santa Barbara, CA 93101
	Email: jplang@ieee.org	Email: jplang@ieee.org


	15. Full Copyright Statement	16. Full Copyright Statement


	Copyright (C) The Internet Society (2004). All Rights Reserved.	Copyright (C) The Internet Society (2004). This document is subject
		to the rights, licenses and restrictions contained in BCP 78, and
		except as set forth therein, the authors retain all their rights.

	This document and translations of it may be copied and furnished to	This document and translations of it may be copied and furnished to
	others, and derivative works that comment on or otherwise explain it	others, and derivative works that comment on or otherwise explain it
	or assist in its implementation may be prepared, copied, published	or assist in its implementation may be prepared, copied, published
	and distributed, in whole or in part, without restriction of any	and distributed, in whole or in part, without restriction of any
	kind, provided that the above copyright notice and this paragraph are	kind, provided that the above copyright notice and this paragraph are
	included on all such copies and derivative works. However, this	included on all such copies and derivative works. However, this
	document itself may not be modified in any way, such as by removing	document itself may not be modified in any way, such as by removing
	the copyright notice or references to the Internet Society or other	the copyright notice or references to the Internet Society or other
	Internet organizations, except as needed for the purpose of	Internet organizations, except as needed for the purpose of
	developing Internet standards in which case the procedures for	developing Internet standards in which case the procedures for
	copyrights defined in the Internet Standards process must be	copyrights defined in the Internet Standards process must be
	followed, or as required to translate it into languages other than	followed, or as required to translate it into languages other than
	English.	English.

	The limited permissions granted above are perpetual and will not be	The limited permissions granted above are perpetual and will not be
	revoked by the Internet Society or its successors or assigns. This	revoked by the Internet Society or its successors or assigns. This
	document and the information contained herein is provided on an "AS	document and the information contained herein is provided on an "AS

	IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK	IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR
	FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT	IS SPONSORED BY (IF ANY),THE INTERNET SOCIETY AND THE INTERNET
	LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	OR FITNESS FOR A PARTICULAR PURPOSE.	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

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