draft-ietf-bess-nsh-bgp-control-plane-17.txt		draft-ietf-bess-nsh-bgp-control-plane-18.txt
	skipping to change at page 1, line 16 ¶		skipping to change at page 1, line 16 ¶
	Expires: February 22, 2021 E. Rosen		Expires: February 22, 2021 E. Rosen
	Juniper Networks		Juniper Networks
	J. Uttaro		J. Uttaro
	AT&T		AT&T
	L. Jalil		L. Jalil
	Verizon		Verizon
	August 21, 2020		August 21, 2020
	BGP Control Plane for the Network Service Header in Service Function		BGP Control Plane for the Network Service Header in Service Function
	Chaining		Chaining
	draft-ietf-bess-nsh-bgp-control-plane-17		draft-ietf-bess-nsh-bgp-control-plane-18
	Abstract		Abstract
	This document describes the use of BGP as a control plane for		This document describes the use of BGP as a control plane for
	networks that support Service Function Chaining (SFC). The document		networks that support Service Function Chaining (SFC). The document
	introduces a new BGP address family called the SFC Address Family		introduces a new BGP address family called the SFC Address Family
	Identifier / Subsequent Address Family Identifier (SFC AFI/SAFI) with		Identifier / Subsequent Address Family Identifier (SFC AFI/SAFI) with
	two route types. One route type is originated by a node to advertise		two route types. One route type is originated by a node to advertise
	that it hosts a particular instance of a specified service function.		that it hosts a particular instance of a specified service function.
	This route type also provides "instructions" on how to send a packet		This route type also provides "instructions" on how to send a packet
	skipping to change at page 41, line 32 ¶		skipping to change at page 41, line 32 ¶
	------ ------ ------ ------		------ ------ ------ ------
	| SFI | | SFI | | SFI | | SFI |		| SFI | | SFI | | SFI | | SFI |
	|SFT=42| |SFT=44| |SFT=43| |SFT=44|		|SFT=42| |SFT=44| |SFT=43| |SFT=44|
	------ ------ ------ ------		------ ------ ------ ------
	Figure 11: Example Service Function Overlay Network		Figure 11: Example Service Function Overlay Network
	The SFFs advertise routes to the SFIs they support. These		The SFFs advertise routes to the SFIs they support. These
	advertisements contain Route Distinguishers that are set according to		advertisements contain Route Distinguishers that are set according to
	the network operator's configuration model. In all of these IPv4		the network operator's configuration model. In all of these IPv4
	examples we use RDs of type 2 such that the available six octets are		examples we use RDs of type 1 such that the available six octets are
	partitioned as four octets for the IPv4 address of the advertising		partitioned as four octets for the IPv4 address of the advertising
	SFF, and two octets that are a local index of the SFI. This scheme		SFF, and two octets that are a local index of the SFI. This scheme
	is chosen purely for convenience of documentation, and an operator is		is chosen purely for convenience of documentation, and an operator is
	totally free to use any other scheme so long as it conforms to the		totally free to use any other scheme so long as it conforms to the
	definitions of SFIR and SFPR in Section 3.1 and Section 3.2.		definitions of SFIR and SFPR in Section 3.1 and Section 3.2.
	Thus we see the following SFIRs advertised:		Thus we see the following SFIRs advertised:
	RD = 192.0.2.1/1, SFT = 41		RD = 192.0.2.1/1, SFT = 41
	RD = 192.0.2.1/2, SFT = 42		RD = 192.0.2.1/2, SFT = 42
	skipping to change at page 57, line 4 ¶		skipping to change at page 57, line 4 ¶
	|SFT=42| |SFT=44| |SFT=43| |SFT=44|		|SFT=42| |SFT=44| |SFT=43| |SFT=44|
	------ ------ ------ ------		------ ------ ------ ------
	Figure 15: Example Service Function Overlay Network		Figure 15: Example Service Function Overlay Network
	The SFFs advertise routes to the SFIs they support. These		The SFFs advertise routes to the SFIs they support. These
	advertisements contain Route Distinguishers that are set according to		advertisements contain Route Distinguishers that are set according to
	the network operator's configuration model. Note that in an IPv6		the network operator's configuration model. Note that in an IPv6
	network, the RD is not large enough to contain the full IPv6 address		network, the RD is not large enough to contain the full IPv6 address
	as only six octets are available so, in all of these IPv6 examples,		as only six octets are available so, in all of these IPv6 examples,
	we use RDs of type 2 such that the available six octets are		we use RDs of type 1 such that the available six octets are
	partitioned as four octets for an IPv4 address of the advertising		partitioned as four octets for an IPv4 address of the advertising
	SFF, and two octets that are a local index of the SFI. Furthermore,		SFF, and two octets that are a local index of the SFI. Furthermore,
	we have chosen an IPv6 addressing scheme so that the low order four		we have chosen an IPv6 addressing scheme so that the low order four
	octets of the IPv6 address match an IPv4 address of the advertising		octets of the IPv6 address match an IPv4 address of the advertising
	node. This scheme is chosen purely for convenience of documentation,		node. This scheme is chosen purely for convenience of documentation,
	and an operator is totally free to use any other scheme so long as it		and an operator is totally free to use any other scheme so long as it
	conforms to the definitions of SFIR and SFPR in Section 3.1 and		conforms to the definitions of SFIR and SFPR in Section 3.1 and
	Section 3.2.		Section 3.2.
	Observant readers will notice that this makes the BGP advertisements		Observant readers will notice that this makes the BGP advertisements
End of changes. 3 change blocks.
	3 lines changed or deleted		3 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/