< draft-ietf-idr-eag-distribution-02.txt		draft-ietf-idr-eag-distribution-03.txt >
	IDR Working Group Z. Wang		IDR Working Group Z. Wang
	Internet-Draft Q. Wu		Internet-Draft Q. Wu
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: December 8, 2016 J. Tantsura		Expires: June 1, 2017 J. Tantsura
	Ericsson		Individual
	June 6, 2016		November 28, 2016
	Distribution of MPLS-TE Extended admin Group Using BGP		Distribution of MPLS-TE Extended admin Group Using BGP
	draft-ietf-idr-eag-distribution-02		draft-ietf-idr-eag-distribution-03
	Abstract		Abstract
	As MPLS-TE network grows, administrative Groups advertised as a		As MPLS-TE network grows, administrative Groups advertised as a
	fixed-length 32-bit Bitmask is quite constraining. "Extended		fixed-length 32-bit Bitmask is quite constraining. "Extended
	Administrative Group" IGP TE extensions sub-TLV defined in [RFC7308]		Administrative Group" IGP TE extensions sub-TLV defined in [RFC7308]
	is introduced to provide for additional administrative groups (link		is introduced to provide for additional administrative groups (link
	colors) beyond the current limit of 32. This document describes		colors) beyond the current limit of 32. This document describes
	extensions to BGP protocol, that can be used to distribute extended		extensions to BGP protocol, that can be used to distribute extended
	administrative groups in MPLS-TE.		administrative groups in MPLS-TE.
	skipping to change at page 1, line 38 ¶		skipping to change at page 1, line 38 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	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."
	This Internet-Draft will expire on December 8, 2016.		This Internet-Draft will expire on June 1, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 3, line 6 ¶		skipping to change at page 3, line 6 ¶
	"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 RFC2119 [RFC2119].		document are to be interpreted as described in RFC2119 [RFC2119].
	3. Carrying Extended Administrative Groups in BGP		3. Carrying Extended Administrative Groups in BGP
	This document proposes one new BGP link attribute TLVs that can be		This document proposes one new BGP link attribute TLVs that can be
	announced as attribute in the BGP-LS attribute (defined in [I.D-ietf-		announced as attribute in the BGP-LS attribute (defined in [I.D-ietf-
	idr-ls-distribution]) to distribute extended administrative groups.		idr-ls-distribution]) to distribute extended administrative groups.
	The extensions in this document build on the ones provided in BGP-LS		The extensions in this document build on the ones provided in BGP-LS
	[I.D-ietf-idr-ls-distribution] and BGP-4 [RFC4271].		[RFC7752] and BGP-4 [RFC4271].
	BGP-LS attribute defined in [I.D-ietf-idr-ls-distribution] has nested		BGP-LS attribute defined in [RFC7752] has nested TLVs which allow the
	TLVs which allow the BGP-LS attribute to be readily extended. Link		BGP-LS attribute to be readily extended. Link attribute TLVs defined
	attribute TLVs defined in section 3.2.2 of [I-D.ietf-idr-ls-		in section 3.2.2 of [I-D.ietf-idr-ls- distribution]are TLVs that may
	distribution]are TLVs that may be encoded in the BGP-LS attribute		be encoded in the BGP-LS attribute with a link NLRI. Each 'Link
	with a link NLRI. Each 'Link Attribute' is a Type/Length/ Value		Attribute' is a Type/Length/ Value (TLV) triplet formatted as defined
	(TLV) triplet formatted as defined in Section 3.1 of [I-D.ietf-idr-		in Section 3.1 of [I-D.ietf-idr- ls-distribution].
	ls-distribution].
	This document proposes one new TLV as a link attribute:		This document proposes one new TLV as a link attribute:
	Type Value		Type Value
	TBD1 Extended Admin Group (EAG)		TBD1 Extended Admin Group (EAG)
	The EAG TLV is used in addition to the Administrative Groups when a		The EAG TLV is used in addition to the Administrative Groups when a
	node wants to advertise more than 32 colors for a link. The EAG TLV		node wants to advertise more than 32 colors for a link. The EAG TLV
	is optional. The format and semantics of the 'value' fields in EAG		is optional. The format and semantics of the 'value' fields in EAG
	skipping to change at page 4, line 10 ¶		skipping to change at page 4, line 10 ¶
	the EAG length may be longer for some links than for others. Similar		the EAG length may be longer for some links than for others. Similar
	to section 2.3.2 of [RFC7308], if a BGP peer wants to only use links		to section 2.3.2 of [RFC7308], if a BGP peer wants to only use links
	where the specific bits of an EAG is set to 1 but the specific bits		where the specific bits of an EAG is set to 1 but the specific bits
	of this EAG is not advertised, then the implementation SHOULD process		of this EAG is not advertised, then the implementation SHOULD process
	these desire and unadvertised EAG bits in accordance with rule		these desire and unadvertised EAG bits in accordance with rule
	defined in section 2.3.2 of [RFC7308].		defined in section 2.3.2 of [RFC7308].
	4. Security Considerations		4. Security Considerations
	This document does not introduce security issues beyond those		This document does not introduce security issues beyond those
	discussed in [I.D-ietf-idr-ls-distribution] and [RFC4271].		discussed in [RFC7752] and [RFC4271].
	5. IANA Considerations		5. IANA Considerations
	IANA maintains the registry for the TLVs. BGP Extended Admin Group		IANA maintains the registry for the TLVs. BGP Extended Admin Group
	link attribute TLV will require one new type code defined in this		link attribute TLV will require one new type code defined in this
	document.		document.
	6. Acknowledgments		6. Acknowledgments
	The authors gratefully acknowledge the review made by Eric Osborne.		The authors gratefully acknowledge the review made by Eric Osborne.
	7. Normative References		7. Normative References
	[I-D.ietf-idr-ls-distribution]
	Gredler, H., "North-Bound Distribution of Link-State and
	TE Information using BGP", ID draft-ietf-idr-ls-
	distribution-13, October 2015.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", March 1997.		Requirement Levels", March 1997.
	[RFC3630] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering		[RFC3630] Katz, D., Yeung, D., and K. Kompella, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630, September		(TE) Extensions to OSPF Version 2", RFC 3630, September
	2003.		2003.
	[RFC4271] Rekhter, Y., "A Border Gateway Protocol 4 (BGP-4)",		[RFC4271] Rekhter, Y., "A Border Gateway Protocol 4 (BGP-4)",
	RFC 4271, January 2006.		RFC 4271, January 2006.
	[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic		[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
	Engineering", RFC 5305, October 2008.		Engineering", RFC 5305, October 2008.
	[RFC7308] Osborne, E., "Extended Administrative Groups in MPLS-TE",		[RFC7308] Osborne, E., "Extended Administrative Groups in MPLS-TE",
	ID RFC7308, July 2014.		ID RFC7308, July 2014.
			[RFC7752] Gredler, H., "North-Bound Distribution of Link-State and
			TE Information using BGP", RFC 7752, March 2016.
	Authors' Addresses		Authors' Addresses
	Zitao Wang		Zitao Wang
	Huawei		Huawei
	101 Software Avenue, Yuhua District		101 Software Avenue, Yuhua District
	Nanjing, Jiangsu 210012		Nanjing, Jiangsu 210012
	China		China
	Email: wangzitao@huawei.com		Email: wangzitao@huawei.com
	Qin Wu		Qin Wu
	Huawei		Huawei
	101 Software Avenue, Yuhua District		101 Software Avenue, Yuhua District
	Nanjing, Jiangsu 210012		Nanjing, Jiangsu 210012
	China		China
	Email: bill.wu@huawei.com		Email: bill.wu@huawei.com
	Jeff Tantsura		Jeff Tantsura
	Ericsson		Individual
	300 Holger Way
	San Jose, CA 95134
	US
	Email: jeff.tantsura@ericsson.com		Email: jefftant.ietf@gmail.com
End of changes. 12 change blocks.
	24 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/