rfc9703v4.txt		rfc9703.txt
	skipping to change at line 25 ¶		skipping to change at line 25 ¶
	Plane		Plane
	Abstract		Abstract
	Egress Peer Engineering (EPE) is an application of Segment Routing		Egress Peer Engineering (EPE) is an application of Segment Routing
	(SR) that solves the problem of egress peer selection. The SR-based		(SR) that solves the problem of egress peer selection. The SR-based
	BGP-EPE solution allows a centralized controller, e.g., a Software-		BGP-EPE solution allows a centralized controller, e.g., a Software-
	Defined Network (SDN) controller, to program any egress peer. The		Defined Network (SDN) controller, to program any egress peer. The
	EPE solution requires the node or the SDN controller to program 1)		EPE solution requires the node or the SDN controller to program 1)
	the PeerNode Segment Identifier (SID) describing a session between		the PeerNode Segment Identifier (SID) describing a session between
	two nodes, 2) the PeerAdj SID sub-TLV describing the link or links		two nodes, 2) the PeerAdj SID describing the link or links that are
	that are used by the sessions between peer nodes, and 3) the PeerSet		used by the sessions between peer nodes, and 3) the PeerSet SID
	SID describing any connected interface to any peer in the related		describing any connected interface to any peer in the related group.
	group. This document provides new sub-TLVs for EPE-SIDs that are		This document provides new sub-TLVs for EPE-SIDs that are used in the
	used in the Target FEC Stack TLV (Type 1) in MPLS Ping and Traceroute		Target FEC Stack TLV (Type 1) in MPLS Ping and Traceroute procedures.
	procedures.
	Status of This Memo		Status of This Memo
	This is an Internet Standards Track document.		This is an Internet Standards Track document.
	This document is a product of the Internet Engineering Task Force		This document is a product of the Internet Engineering Task Force
	(IETF). It represents the consensus of the IETF community. It has		(IETF). It represents the consensus of the IETF community. It has
	received public review and has been approved for publication by the		received public review and has been approved for publication by the
	Internet Engineering Steering Group (IESG). Further information on		Internet Engineering Steering Group (IESG). Further information on
	Internet Standards is available in Section 2 of RFC 7841.		Internet Standards is available in Section 2 of RFC 7841.
End of changes. 1 change blocks.
	6 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.48.