draft-ietf-idr-rpd-00.txt		draft-ietf-idr-rpd-05.txt
	Network Working Group Z. Li		Network Working Group Z. Li
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Standards Track L. Ou		Intended status: Standards Track L. Ou
	Expires: May 4, 2020 Y. Luo		Expires: December 11, 2020 Y. Luo
	China Telcom Co., Ltd.		China Telcom Co., Ltd.
	S. Lu		S. Lu
	Tencent		Tencent
	H. Chen		H. Chen
	Futurewei		Futurewei
	S. Zhuang		S. Zhuang
	H. Wang		H. Wang
	Huawei		Huawei
	November 1, 2019		June 9, 2020
	BGP Extensions for Routing Policy Distribution (RPD)		BGP Extensions for Routing Policy Distribution (RPD)
	draft-ietf-idr-rpd-00		draft-ietf-idr-rpd-05
	Abstract		Abstract
	It is hard to adjust traffic and optimize traffic paths on a		It is hard to adjust traffic and optimize traffic paths on a
	traditional IP network from time to time through manual		traditional IP network from time to time through manual
	configurations. It is desirable to have an automatic mechanism for		configurations. It is desirable to have an automatic mechanism for
	setting up routing policies, which adjust traffic and optimize		setting up routing policies, which adjust traffic and optimize
	traffic paths automatically. This document describes BGP Extensions		traffic paths automatically. This document describes BGP Extensions
	for Routing Policy Distribution (BGP RPD) to support this.		for Routing Policy Distribution (BGP RPD) to support this.
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 May 4, 2020.		This Internet-Draft will expire on December 11, 2020.
	Copyright Notice		Copyright Notice
	Copyright (c) 2019 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 5, line 40 ¶		skipping to change at page 5, line 40 ¶
	Outbound Traffic Control case		Outbound Traffic Control case
	4. Protocol Extensions		4. Protocol Extensions
	A solution is proposed to use a new AFI and SAFI with the BGP Wide		A solution is proposed to use a new AFI and SAFI with the BGP Wide
	Community for encoding a routing policy.		Community for encoding a routing policy.
	4.1. Using a New AFI and SAFI		4.1. Using a New AFI and SAFI
	A new AFI and SAFI are defined: the Routing Policy AFI whose		A new AFI and SAFI are defined: the Routing Policy AFI whose
	codepoint TBD1 is to be assigned by IANA, and SAFI whose codepoint		codepoint 16398 has been assigned by IANA, and SAFI whose codepoint
	TBD2 is to be assigned by IANA.		75 has been assigned by IANA.
	The AFI and SAFI pair uses a new NLRI, which is defined as follows:		The AFI and SAFI pair uses a new NLRI, which is defined as follows:
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	| NLRI Length |		| NLRI Length |
	+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+
	| Policy Type |		| Policy Type |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	skipping to change at page 12, line 12 ¶		skipping to change at page 12, line 12 ¶
	Counti: 1 octet. ASi repeats Counti times.		Counti: 1 octet. ASi repeats Counti times.
	The sequence of AS numbers are added to the existing AS Path.		The sequence of AS numbers are added to the existing AS Path.
	4.3. Capability Negotiation		4.3. Capability Negotiation
	It is necessary to negotiate the capability to support BGP Extensions		It is necessary to negotiate the capability to support BGP Extensions
	for Routing Policy Distribution (RPD). The BGP RPD Capability is a		for Routing Policy Distribution (RPD). The BGP RPD Capability is a
	new BGP capability [RFC5492]. The Capability Code for this		new BGP capability [RFC5492]. The Capability Code for this
	capability is to be specified by the IANA. The Capability Length		capability is 72 assigned by the IANA. The Capability Length field
	field of this capability is variable. The Capability Value field		of this capability is variable. The Capability Value field consists
	consists of one or more of the following tuples:		of one or more of the following tuples:
	+--------------------------------------------------+		+--------------------------------------------------+
	| Address Family Identifier (2 octets) |		| Address Family Identifier (2 octets) |
	+--------------------------------------------------+		+--------------------------------------------------+
	| Subsequent Address Family Identifier (1 octet) |		| Subsequent Address Family Identifier (1 octet) |
	+--------------------------------------------------+		+--------------------------------------------------+
	| Send/Receive (1 octet) |		| Send/Receive (1 octet) |
	+--------------------------------------------------+		+--------------------------------------------------+
	BGP RPD Capability		BGP RPD Capability
	skipping to change at page 14, line 13 ¶		skipping to change at page 14, line 13 ¶
	section of [RFC5575].		section of [RFC5575].
	8. Acknowledgements		8. Acknowledgements
	The authors would like to thank Acee Lindem, Jeff Haas, Jie Dong,		The authors would like to thank Acee Lindem, Jeff Haas, Jie Dong,
	Lucy Yong, Qiandeng Liang, Zhenqiang Li for their comments to this		Lucy Yong, Qiandeng Liang, Zhenqiang Li for their comments to this
	work.		work.
	9. IANA Considerations		9. IANA Considerations
	This document requests assigning a new AFI in the registry "Address		IANA has assigned a new AFI of value 16398 from the registry "Address
	Family Numbers" as follows:		Family Numbers" for Routing Policy.
	+-----------------------+-------------------------+-------------+
	| Code Point | Description | Reference |
	+-----------------------+-------------------------+-------------+
	| TBD (36879 suggested) | Routing Policy AFI |This document|
	+-------------------------------------------------+-------------+
	This document requests assigning a new SAFI in the registry
	"Subsequent Address Family Identifiers (SAFI) Parameters" as follows:
	+-----------------------+-------------------------+-------------+		IANA has assigned a new SAFI of value 75 from the registry
	| Code Point | Description | Reference |		"Subsequent Address Family Identifiers (SAFI) Parameters" for Routing
	+-----------------------+-------------------------+-------------+		Policy.
	| TBD(179 suggested) | Routing Policy SAFI |This document|
	+-----------------------+-------------------------+-------------+
	This document defines a new registry called "Routing Policy NLRI".		This document defines a new registry called "Routing Policy Type".
	The allocation policy of this registry is "First Come First Served		The allocation policy of this registry is "First Come First Served
	(FCFS)" according to [RFC8126].		(FCFS)" according to [RFC8126].
	Following code points are defined:		Following code points are defined:
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| Code Point | Description | Reference |		| Code Point | Description | Reference |
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
			| 0 | Reserved | |
			+-------------+-----------------------------------+-------------+
	| 1 | Export Policy |This document|		| 1 | Export Policy |This document|
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 2 | Import Policy |This document|		| 2 | Import Policy |This document|
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
			| 3 - 255 | To be assigned in FCFS | |
			+-------------+-----------------------------------+-------------+
	This document requests assigning a code-point from the registry "BGP		This document requests assigning a code-point from the registry "BGP
	Community Container Atom Types" as follows:		Community Container Atom Types" as follows:
	+---------------------+------------------------------+-------------+		+---------------------+------------------------------+-------------+
	| TLV Code Point | Description | Reference |		| TLV Code Point | Description | Reference |
	+---------------------+------------------------------+-------------+		+---------------------+------------------------------+-------------+
	| TBD1 (48 suggested) | RouteAttr Atom |This document|		| TBD1 (48 suggested) | RouteAttr Atom |This document|
	+---------------------+------------------------------+-------------+		+---------------------+------------------------------+-------------+
	skipping to change at page 15, line 16 ¶		skipping to change at page 15, line 10 ¶
	TLV" under RouteAttr Atom TLV. The allocation policy of this		TLV" under RouteAttr Atom TLV. The allocation policy of this
	registry is "First Come First Served (FCFS)" according to [RFC8126].		registry is "First Come First Served (FCFS)" according to [RFC8126].
	Following Sub-TLV code points are defined:		Following Sub-TLV code points are defined:
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| Code Point | Description | Reference |		| Code Point | Description | Reference |
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 0 | Reserved | |		| 0 | Reserved | |
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 1 | IP Prefix Sub-TLV |This document|		| 1 | IPv4 Prefix Sub-TLV |This document|
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 2 | AS-Path Sub-TLV |This document|		| 2 | AS-Path Sub-TLV |This document|
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 3 | Community Sub-TLV |This document|		| 3 | Community Sub-TLV |This document|
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 4 - 255 | To be assigned in FCFS | |		| 4 | IPv6 Prefix Sub-TLV |This document|
			+-------------+-----------------------------------+-------------+
			| 5 - 255 | To be assigned in FCFS | |
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	This document defines a new registry called "Attribute Change Sub-		This document defines a new registry called "Attribute Change Sub-
	TLV" under Parameter(s) TLV. The allocation policy of this registry		TLV" under Parameter(s) TLV. The allocation policy of this registry
	is "First Come First Served (FCFS)" according to [RFC8126].		is "First Come First Served (FCFS)" according to [RFC8126].
	Following Sub-TLV code points are defined:		Following Sub-TLV code points are defined:
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| Code Point | Description | Reference |		| Code Point | Description | Reference |
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 0 | Reserved | |		| 0 | Reserved | |
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 1 | MED Change Sub-TLV |This document|		| 1 | MED Change Sub-TLV |This document|
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 2 | AS-Path Change Sub-TLV |This document|		| 2 | AS-Path Change Sub-TLV |This document|
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
	| 3 - 255 | To be assigned in FCFS | |		| 3 - 255 | To be assigned in FCFS | |
	+-------------+-----------------------------------+-------------+		+-------------+-----------------------------------+-------------+
			IANA has assigned a new Code Point of value 72 from the registry
			"Capability Codes" for Routing Policy Distribution.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[I-D.ietf-idr-wide-bgp-communities]		[I-D.ietf-idr-wide-bgp-communities]
	Raszuk, R., Haas, J., Lange, A., Decraene, B., Amante, S.,		Raszuk, R., Haas, J., Lange, A., Decraene, B., Amante, S.,
	and P. Jakma, "BGP Community Container Attribute", draft-		and P. Jakma, "BGP Community Container Attribute", draft-
	ietf-idr-wide-bgp-communities-05 (work in progress), July		ietf-idr-wide-bgp-communities-05 (work in progress), July
	2018.		2018.
	skipping to change at page 17, line 18 ¶		skipping to change at page 17, line 18 ¶
	China		China
	Email: lizhenbin@huawei.com		Email: lizhenbin@huawei.com
	Liang Ou		Liang Ou
	China Telcom Co., Ltd.		China Telcom Co., Ltd.
	109 West Zhongshan Ave,Tianhe District		109 West Zhongshan Ave,Tianhe District
	Guangzhou 510630		Guangzhou 510630
	China		China
	Email: oul@gsta.com		Email: ouliang@chinatelecom.cn
	Yujia Luo		Yujia Luo
	China Telcom Co., Ltd.		China Telcom Co., Ltd.
	109 West Zhongshan Ave,Tianhe District		109 West Zhongshan Ave,Tianhe District
	Guangzhou 510630		Guangzhou 510630
	China		China
	Email: luoyuj@gsta.com		Email: luoyuj@sdu.edu.cn
	Sujian Lu		Sujian Lu
	Tencent		Tencent
	Tengyun Building,Tower A ,No. 397 Tianlin Road		Tengyun Building,Tower A ,No. 397 Tianlin Road
	Shanghai, Xuhui District 200233		Shanghai, Xuhui District 200233
	China		China
	Email: jasonlu@tencent.com		Email: jasonlu@tencent.com
	Huaimo Chen		Huaimo Chen
End of changes. 17 change blocks.
	31 lines changed or deleted		29 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/