< draft-chunduri-lsr-isis-preferred-path-routing-05.txt		draft-chunduri-lsr-isis-preferred-path-routing-06.txt >
	LSR Working Group U. Chunduri		LSR Working Group U. Chunduri
	Internet-Draft R. Li		Internet-Draft R. Li
	Intended status: Standards Track Futurewei		Intended status: Standards Track Futurewei
	Expires: September 9, 2020 R. White		Expires: April 1, 2021 R. White
	Juniper Networks		Juniper Networks
	J. Tantsura		J. Tantsura
	Apstra Inc.		Apstra Inc.
	L. Contreras		L. Contreras
	Telefonica		Telefonica
	Y. Qu		Y. Qu
	Futurewei		Futurewei
	March 8, 2020		September 28, 2020
	Preferred Path Routing (PPR) in IS-IS		Preferred Path Routing (PPR) in IS-IS
	draft-chunduri-lsr-isis-preferred-path-routing-05		draft-chunduri-lsr-isis-preferred-path-routing-06
	Abstract		Abstract
	This document specifies Preferred Path Routing (PPR), a routing		This document specifies Preferred Path Routing (PPR), an extensible
	protocol extension to simplify the path description on the packet for		method of providing path based dynamic routing for a number of packet
	Segment Routing (SR) deployments and beyond. PPR aims to mitigate		types including IPv4, IPv6 and MPLS. PPR uses a simple encapsulation
	the MTU and data plane processing issues that may result from SR		to add the path identity to the packet. PPR can also be used to
	packet overhead; and also supports further extensions along the		mitigate the MTU and data plane processing issues that may result
	paths.		from Segment Routing (SR) packet overhead; and also supports further
			extensions along the paths.
	Requirements Language		Requirements Language
	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 RFC2119 [RFC2119],		document are to be interpreted as described in RFC2119 [RFC2119],
	RFC8174 [RFC8174] when, and only when they appear in all capitals, as		RFC8174 [RFC8174] when, and only when they appear in all capitals, as
	shown here.		shown here.
	Status of This Memo		Status of This Memo
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 6 ¶
	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 September 9, 2020.
			This Internet-Draft will expire on April 1, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 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
	skipping to change at page 20, line 46 ¶		skipping to change at page 20, line 46 ¶
	[I-D.ietf-isis-encapsulation-cap]		[I-D.ietf-isis-encapsulation-cap]
	Xu, X., Decraene, B., Raszuk, R., Chunduri, U., Contreras,		Xu, X., Decraene, B., Raszuk, R., Chunduri, U., Contreras,
	L., and L. Jalil, "Advertising Tunnelling Capability in		L., and L. Jalil, "Advertising Tunnelling Capability in
	IS-IS", draft-ietf-isis-encapsulation-cap-01 (work in		IS-IS", draft-ietf-isis-encapsulation-cap-01 (work in
	progress), April 2017.		progress), April 2017.
	[I-D.ietf-isis-mpls-elc]		[I-D.ietf-isis-mpls-elc]
	Xu, X., Kini, S., Psenak, P., Filsfils, C., Litkowski, S.,		Xu, X., Kini, S., Psenak, P., Filsfils, C., Litkowski, S.,
	and M. Bocci, "Signaling Entropy Label Capability and		and M. Bocci, "Signaling Entropy Label Capability and
	Entropy Readable Label Depth Using IS-IS", draft-ietf-		Entropy Readable Label Depth Using IS-IS", draft-ietf-
	isis-mpls-elc-10 (work in progress), October 2019.		isis-mpls-elc-13 (work in progress), May 2020.
	[I-D.ietf-isis-segment-routing-extensions]		[I-D.ietf-isis-segment-routing-extensions]
	Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,		Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
	Gredler, H., and B. Decraene, "IS-IS Extensions for		Gredler, H., and B. Decraene, "IS-IS Extensions for
	Segment Routing", draft-ietf-isis-segment-routing-		Segment Routing", draft-ietf-isis-segment-routing-
	extensions-25 (work in progress), May 2019.		extensions-25 (work in progress), May 2019.
	[I-D.ietf-mpls-sfc]		[I-D.ietf-mpls-sfc]
	Farrel, A., Bryant, S., and J. Drake, "An MPLS-Based		Farrel, A., Bryant, S., and J. Drake, "An MPLS-Based
	Forwarding Plane for Service Function Chaining", draft-		Forwarding Plane for Service Function Chaining", draft-
End of changes. 6 change blocks.
	11 lines changed or deleted		13 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/