< draft-irtf-panrg-questions.txt		draft-irtf-panrg-questions.txt >
	Path Aware Networking RG B. Trammell		Path Aware Networking RG B. Trammell
	Internet-Draft Google Switzerland GmbH		Internet-Draft Google Switzerland GmbH
	Intended status: Informational 25 January 2022		Intended status: Informational 25 January 2022
	Expires: 29 July 2022		Expires: 29 July 2022
	Current Open Questions in Path Aware Networking		Current Open Questions in Path Aware Networking
	draft-irtf-panrg-questions-12		draft-irtf-panrg-questions-latest
	Abstract		Abstract
	In contrast to the present Internet architecture, a path-aware		In contrast to the present Internet architecture, a path-aware
	internetworking architecture has two important properties: it exposes		internetworking architecture has two important properties: it exposes
	the properties of available Internet paths to endpoints, and provides		the properties of available Internet paths to endpoints, and provides
	for endpoints and applications to use these properties to select		for endpoints and applications to use these properties to select
	paths through the Internet for their traffic. While this property of		paths through the Internet for their traffic. While this property of
	"path awareness" already exists in many Internet-connected networks		"path awareness" already exists in many Internet-connected networks
	within single domains and via administrative interfaces to the		within single domains and via administrative interfaces to the
	skipping to change at page 2, line 28 ¶		skipping to change at line 69 ¶
	Provisions Relating to IETF Documents (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Revised BSD License text as		extracted from this document must include Revised BSD License text as
	described in Section 4.e of the Trust Legal Provisions and are		described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Revised BSD License.		provided without warranty as described in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction to Path-Aware Networking . . . . . . . . . . . . 2		1. Introduction to Path-Aware Networking
	1.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4		1.1. Definitions
	2. Questions . . . . . . . . . . . . . . . . . . . . . . . . . . 4		2. Questions
	2.1. A Vocabulary of Path Properties . . . . . . . . . . . . . 5		2.1. A Vocabulary of Path Properties
	2.2. Discovery, Distribution, and Trustworthiness of Path		2.2. Discovery, Distribution, and Trustworthiness of Path
	Properties . . . . . . . . . . . . . . . . . . . . . . . 5		Properties
	2.3. Supporting Path Selection . . . . . . . . . . . . . . . . 6		2.3. Supporting Path Selection
	2.4. Interfaces for Path Awareness . . . . . . . . . . . . . . 6		2.4. Interfaces for Path Awareness
	2.5. Implications of Path Awareness for the Transport and		2.5. Implications of Path Awareness for the Transport and
	Application Layers . . . . . . . . . . . . . . . . . . . 7		Application Layers
	2.6. What is an Endpoint? . . . . . . . . . . . . . . . . . . 7		2.6. What is an Endpoint?
	2.7. Operating a Path Aware Network . . . . . . . . . . . . . 8		2.7. Operating a Path Aware Network
	2.8. Deploying a Path Aware Network . . . . . . . . . . . . . 8		2.8. Deploying a Path Aware Network
	3. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 9		3. Acknowledgments
	4. Informative References . . . . . . . . . . . . . . . . . . . 10		4. Informative References
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10		Author's Address
	1. Introduction to Path-Aware Networking		1. Introduction to Path-Aware Networking
	In the current Internet architecture, the network layer provides a		In the current Internet architecture, the network layer provides a
	best-effort service to the endpoints using it, without verifiability		best-effort service to the endpoints using it, without verifiability
	of the properties of the path between tne endpoints. While there are		of the properties of the path between tne endpoints. While there are
	network layer technologies that attempt better-than-best-effort		network layer technologies that attempt better-than-best-effort
	delivery, the interfaces to these are generally administrative as		delivery, the interfaces to these are generally administrative as
	opposed to endpoint-exposed (e.g. Path Computation Element (PCE)		opposed to endpoint-exposed (e.g. Path Computation Element (PCE)
	[RFC4655] and Software-Defined Wide Area Network (SD-WAN)		[RFC4655] and Software-Defined Wide Area Network (SD-WAN)
	approaches), and they are often restricted to single administrative		approaches), and they are often restricted to single administrative
	domains. In this architecture, an application can assume that a		domains. In this architecture, an application can assume that a
	packet with a given destination address will eventually be forwarded		packet with a given destination address will eventually be forwarded
	toward that destination, but little else.		toward that destination, but little else.
	A transport layer protocol such as TCP can provide reliability over		A transport layer protocol such as TCP can provide reliability over
	this best-effort service, and a protocol above the network layer,		this best-effort service, and a protocol above the network layer,
	such as Transport Layer Security (TLS) [RFC8446] can authenticate the		such as Transport Layer Security (TLS) [RFC8446] can authenticate the
	remote endpoint. However, little, if any, explicit information about		remote endpoint. However, little, if any, explicit information about
End of changes. 5 change blocks.
	16 lines changed or deleted		15 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/