draft-ietf-ccamp-gmpls-ted-mib-02.txt		draft-ietf-ccamp-gmpls-ted-mib-03.txt
	IETF Internet Draft Masanori Miyazawa		INTERNET-DRAFT Masanori Miyazawa
	Proposed status: Standards Track Tomohiro Otani		Intended status: Standard Truck Tomohiro Otani
	Expires: Jan. 2008 KDDI R&D Labs		Expires: August 31, 2008 Kenji Kumaki
			KDDI R&D Labs
	Thomas D. Nadeau		Thomas D. Nadeau
	Cisco Systems		Cisco Systems, Inc.
	Kenji Kumaki		February 21, 2008
	KDDI Corporation
	Traffic Engineering Database Management Information Base		Traffic Engineering Database Management Information Base
	in support of GMPLS		in support of GMPLS
	draft-ietf-ccamp-gmpls-ted-mib-02.txt
			Document: draft-ietf-ccamp-gmpls-ted-mib-03.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	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		Task Force (IETF), its areas, and its working groups. Note that other
	other groups may also distribute working documents as Internet-Drafts.		groups may also distribute working documents as Internet-Drafts.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt		http://www.ietf.org/ietf/1id-abstracts.txt
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Abstract		Abstract
	This memo defines the Management Information Base (MIB) objects in		This memo defines the Management Information Base (MIB) objects in
	order to manage traffic engineering database (TED) information with		order to manage traffic engineering database (TED) information with
	extension in support of Multi-protocol label switching (MPLS) as well		extension in support of Multi-Protocol Label Switching (MPLS) as well
	as Generalized MPLS (GMPLS) for use with network management protocols.		as Generalized MPLS (GMPLS) for use with network management protocols.
	Table of Contents		Table of Contents
	Status of this Memo................................................1		Status of this Memo................................................1
	Abstract...........................................................1		Abstract...........................................................1
	1. The Internet-Standard Management Framework......................3		1. The Internet-Standard Management Framework......................3
	2. Introduction....................................................3		2. Introduction....................................................3
	T. Otani et al. 1
	3. Overview........................................................3		3. Overview........................................................3
	3.1 Conventions used in this document..............................3		3.1 Conventions used in this document..............................3
	3.2 Terminology....................................................3		3.2 Terminology....................................................3
	3.3 Acronyms.......................................................3		3.3 Acronyms.......................................................3
	4. Motivations.....................................................4		4. Motivations.....................................................4
	5. Brief description of MIB Objects................................4		5. Brief description of MIB Objects................................4
	5.1 tedTable.......................................................4		5.1 tedTable.......................................................4
	5.2 teLocalIntIpAddrTable..........................................4		5.2 teLocalIntIpAddrTable..........................................4
	5.3 teRemoteIntIpAddrTable.........................................4		5.3 teRemoteIntIpAddrTable.........................................4
	5.4 teSwCapTable...................................................5		5.4 teSwCapTable...................................................5
	5.5 teSrlgTable....................................................5		5.5 teSrlgTable....................................................5
	6. TED MIB Definitions in support of GMPLS.........................5		6. TED MIB Definitions in support of GMPLS.........................5
	7. Security consideration.........................................21		7. Security consideration.........................................21
	8. IANA Considerations............................................21		8. IANA Considerations............................................21
	8.1 IANA Considerations for TED-MIB...............................21		8.1 IANA Considerations for TED-MIB...............................21
	9. References.....................................................21		9. References.....................................................21
	9.1 Normative References..........................................21		9.1 Normative References..........................................21
	9.2 Informative References........................................22		9.2 Informative References........................................22
	10. Acknowledgment................................................23		10. Acknowledgment................................................23
	11. Author's Address..............................................23		11. Author's Address..............................................23
	12. Intellectual Property Statement...............................23		12. Intellectual Property Statement............................... 24
	13. Copyright Statement...........................................24		Copyright statement............................................... 24
	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).
	skipping to change at page 3, line 36		skipping to change at page 3, line 36
	such MPLS/GMPLS networks effectively, routing information associated		such MPLS/GMPLS networks effectively, routing information associated
	with MPLS/GMPLS TE parameters (TED) is preferred for the network		with MPLS/GMPLS TE parameters (TED) is preferred for the network
	management, however, there is no clear definition of MPLS/GMPLS TE		management, however, there is no clear definition of MPLS/GMPLS TE
	information in existing MIBs related with OSPF/ISIS.		information in existing MIBs related with OSPF/ISIS.
	This memo defines the Management Information Base (MIB) objects for		This memo defines the Management Information Base (MIB) objects for
	managing TED in support of MPLS/GMPLS for use with network management		managing TED in support of MPLS/GMPLS for use with network management
	protocols.		protocols.
	This MIB module should be used in conjunction with OSPF/ISIS MIB as		This MIB module should be used in conjunction with OSPF/ISIS MIB as
	well as other MIBs defined in [RFC3812, RFC3813, GMPLSLSRMIB,		well as other MIBs defined in [RFC3812, RFC3813, RFC4802, RFC4803]
	GMPLSTEMIB] for the management of MPLS/GMPLS based traffic		for the management of MPLS/GMPLS based traffic engineering
	engineering information.		information.
	3. Overview		3. Overview
	3.1 Conventions used in this document		3.1 Conventions used in this document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC-2119 [RFC2119].		document are to be interpreted as described in RFC-2119 [RFC2119].
	3.2 Terminology		3.2 Terminology
	skipping to change at page 5, line 45		skipping to change at page 5, line 45
	" Tomohiro Otani		" Tomohiro Otani
	otani@kddilabs.jp		otani@kddilabs.jp
	Masanori Miyazawa		Masanori Miyazawa
	ma-miyazawa@kddilabs.jp		ma-miyazawa@kddilabs.jp
	Thomas D. Nadeau		Thomas D. Nadeau
	tnadeau@cisco.com		tnadeau@cisco.com
	Kenji Kumaki		Kenji Kumaki
	ke-kumaki@kddi.com		ke-kumaki@kddilabs.jp
	Comments and discussion to ccamp@ietf.org"		Comments and discussion to ccamp@ietf.org"
	DESCRIPTION		DESCRIPTION
	"This MIB contains managed object definitions for		"This MIB contains managed object definitions for TED in
	TED in support of MPLS/GMPLS Traffic		support of MPLS/GMPLS Traffic Engienering (TE) Database.
	Engienering (TE) Database.
	Copyright (C) The Internet Society (2007). This		Copyright (C) The Internet Society (2008). This version of
	version of this MIB module is part of RFCXXX; see		this MIB module is part of RFCXXX; see the RFC itself for
	the RFC itself for full legal notices."		full legal notices."
	-- Revision history.		-- Revision history.
	REVISION		REVISION
	"200506041200Z" -- 04 July 2005 12:00:00 GMT		"200506041200Z" -- 04 July 2005 12:00:00 GMT
	DESCRIPTION		DESCRIPTION
	"Initial version. Published as RFC xxxx."		"Initial version. Published as RFC xxxx."
	-- RFC-editor pls fill in xxx		-- RFC-editor pls fill in xxx
	::= { transmission xxx }		::= { transmission xxx }
	-- assigned by IANA, see section 7.1 for details		-- assigned by IANA, see section 7.1 for details
	-- Textual Conventions.		-- Textual Conventions.
	skipping to change at page 8, line 4		skipping to change at page 8, line 4
	}		}
	teAreaId OBJECT-TYPE		teAreaId OBJECT-TYPE
	SYNTAX Unsigned32 (1..4294967295)		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object indicates the area identifier of the IGP. If		"This object indicates the area identifier of the IGP. If
	OSPF is used to advertise LSA, this represents an ospfArea. If ISIS		OSPF is used to advertise LSA, this represents an ospfArea. If ISIS
	is used, this represents an area addres. Otherwise, this represents		is used, this represents an area address. Otherwise, this represents
	zero."		zero."
	::= { tedEntry 1 }		::= { tedEntry 1 }
	teRouterId OBJECT-TYPE		teRouterId OBJECT-TYPE
	SYNTAX Unsigned32 (1..4294967295)		SYNTAX Unsigned32 (1..4294967295)
	MAX-ACCESS read-only		MAX-ACCESS read-only
	STATUS current		STATUS current
	DESCRIPTION		DESCRIPTION
	"This object indicates the router identifier. If OSPF is		"This object indicates the router identifier. If OSPF is
	used to advertise LSA, this represents a Router ID. If ISIS is used,		used to advertise LSA, this represents a Router ID. If ISIS is used,
	skipping to change at page 22, line 53		skipping to change at page 22, line 53
	[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,		[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
	"Multiprotocol Label Switching (MPLS) Traffic		"Multiprotocol Label Switching (MPLS) Traffic
	Engineering (TE) Management Information Base (MIB)",		Engineering (TE) Management Information Base (MIB)",
	RFC 3812, June 2004.		RFC 3812, June 2004.
	[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,		[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau,
	"Multiprotocol Label Switching (MPLS) Label Switching		"Multiprotocol Label Switching (MPLS) Label Switching
	(LSR) Router Management Information Base (MIB)", RFC		(LSR) Router Management Information Base (MIB)", RFC
	3813, June 2004.		3813, June 2004.
	[GMPLSLSRMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol		[RFC4802] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol
	Label Switching (GMPLS) Label Switching Router (LSR)
	Management Information Base", draft-ietf-ccamp-gmpls-
	lsr-mib-08.txt, June 2005.
	[GMPLSTEMIB] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol
	Label Switching (GMPLS) Traffic Engineering		Label Switching (GMPLS) Traffic Engineering
	Management Information Base", draft-ietf-ccamp-gmpls-		Management Information Base", RFC4802, Feb., 2007.
	te-mib-09.txt, June 2005.
			[RFC4803] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol
			Label Switching (GMPLS) Label Switching Router (LSR)
			Management Information Base", RFC4803, Feb., 2007.
	[MPLS OAM] T. Nadeau, Allan D., et al., "OAM Requirements for		[MPLS OAM] T. Nadeau, Allan D., et al., "OAM Requirements for
	MPLS Network"		MPLS Network" draft-ietf-mpls-oam-requirements-05.txt,
	draft-ietf-mpls-oam-requirements-05.txt, June 2005.		June 2005.
	[RFC3945] E. Mannie, "Generalized Multi-Protocol Label		[RFC3945] E. Mannie, "Generalized Multi-Protocol Label
	Switching Architecture", RFC3945, October, 2004.		Switching Architecture", RFC3945, October, 2004.
	[RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in		[RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in
	Support of Generalized Multi-Protocol Label		Support of Generalized Multi-Protocol Label
	Switching", RFC4203, Oct. 2005.		Switching", RFC4203, Oct. 2005.
	[RFC3630] Katz, D., et al, "Traffic Engineering (TE) Extensions		[RFC3630] Katz, D., et al, "Traffic Engineering (TE) Extensions
	to OSPF Version 2", RFC3630, September 2003.		to OSPF Version 2", RFC3630, September 2003.
	skipping to change at page 23, line 38		skipping to change at page 23, line 37
	10. Acknowledgment		10. Acknowledgment
	The authors wish to acknowledge and thank the following individuals		The authors wish to acknowledge and thank the following individuals
	for their valuable comments to this document: Ken Nagami, Shuichi		for their valuable comments to this document: Ken Nagami, Shuichi
	Okamoto, Adrian Farrel and Diego Caviglia.		Okamoto, Adrian Farrel and Diego Caviglia.
	11. Author's Address		11. Author's Address
	Tomohiro Otani		Tomohiro Otani
	KDDI R&D Laboratories, Inc.		KDDI R&D Laboratories, Inc.
	2-1-15 Ohara Fujimino Phone: +81-49-278-7357		2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan
	Saitama, 356-8502. Japan Email: otani@kddilabs.jp		Phone: +81-49-278-7357
			Email: otani@kddilabs.jp
	Masanori Miyazawa		Masanori Miyazawa
	KDDI R&D Laboratories, Inc.		KDDI R&D Laboratories, Inc.
	2-1-15 Ohara Fujimino Phone: +81-49-278-7559		2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan.
	Saitama, 356-8502. Japan Email: ma-miyazawa@kddilabs.jp		Phone: +81-49-278-7559
			Email: ma-miyazawa@kddilabs.jp
	Thomas D. Nadeau		Thomas D. Nadeau
	Cisco Systems, Inc.		Cisco Systems, Inc.
	300 Beaver Brook Road Phone: +1-978-936-1470		300 Beaver Brook Road, Boxboro, MA 01719
	Boxboro, MA 01719 Email: tnadeau@cisco.com300		Phone: +1-978-936-1470
			Email: tnadeau@cisco.com
	Kenji Kumaki		Kenji Kumaki
	KDDI Corporation		KDDI R&D Laboratories, Inc.
	GARDEN AIR TOWER,3-10-10,Iidabshi Phone: +81-3-6678-3103		2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan
	Chiyoda-ku,Tokyo, 102-8460. Japan Email: ke-kumaki@kddi.com		Phone: +81-49-278-7863
			Email: ke-kumaki@kddilabs.jp
	12. Intellectual Property Statement		12. Intellectual Property Statement
	The IETF takes no position regarding the validity or scope of any		The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to		Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in		pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights		this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	Copies of IPR disclosures made to the IETF Secretariat and any		Copies of IPR disclosures made to the IETF Secretariat and any
	skipping to change at page 24, line 18		skipping to change at page 24, line 22
	might or might not be available; nor does it represent that it has		might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information		made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be		on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.		found in BCP 78 and BCP 79.
	Copies of IPR disclosures made to the IETF Secretariat and any		Copies of IPR disclosures made to the IETF Secretariat and any
	assurances of licenses to be made available, or the result of an		assurances of licenses to be made available, or the result of an
	attempt made to obtain a general license or permission for the use of		attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr. The IETF invites any interested party to
			bring to its attention any copyrights, patents or patent applications,
	The IETF invites any interested party to bring to its attention any		or other proprietary rights that may cover technology that may be
	copyrights, patents or patent applications, or other proprietary		required to implement this standard. Please address the information
	rights that may cover technology that may be required to implement		to the IETF at ietf-ipr@ietf.org.
	this standard. Please address the information to the IETF at ietf-
	ipr@ietf.org.
	13. Copyright Statement		Copyright statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
End of changes. 24 change blocks.
	54 lines changed or deleted		53 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/