Current Open Questions in Path Aware Networking
draft-irtf-panrg-questions-07

Document Type Active Internet-Draft (panrg RG)
Author Brian Trammell 
Last updated 2020-09-06 (latest revision 2020-08-29)
Replaces draft-trammell-panrg-questions
Stream IRTF
Intended RFC status Informational
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream IRTF state Awaiting IRSG Reviews
Consensus Boilerplate Yes
Document shepherd Spencer Dawkins
Shepherd write-up Show (last changed 2020-09-01)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Path Aware Networking RG                                     B. Trammell
Internet-Draft                                   Google Switzerland GmbH
Intended status: Informational                           August 29, 2020
Expires: March 2, 2021

            Current Open Questions in Path Aware Networking
                     draft-irtf-panrg-questions-07

Abstract

   In contrast to the present Internet architecture, a path-aware
   internetworking architecture has two important properties: it exposes
   the properties of available Internet paths to endpoints, and provides
   for endpoints and applications to use these properties to select
   paths through the Internet for their traffic.  This document poses
   questions in path-aware networking open as of 2020, that must be
   answered in the design, development, and deployment of path-aware
   internetworks.  It was originally written to frame discussions in the
   Path Aware Networking proposed Research Group (PANRG), and has been
   published to snapshot current thinking in this space.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 2, 2021.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Trammell                  Expires March 2, 2021                 [Page 1]
Internet-Draft                PAN questions                  August 2020

   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction to Path-Aware Networking . . . . . . . . . . . .   2
     1.1.  Definition  . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Questions . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  A Vocabulary of Path Properties . . . . . . . . . . . . .   4
     2.2.  Discovery, Distribution, and Trustworthiness of Path
           Properties  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Supporting Path Selection . . . . . . . . . . . . . . . .   5
     2.4.  Interfaces for Path Awareness . . . . . . . . . . . . . .   5
     2.5.  Implications of Path Awareness for the Data Plane . . . .   6
     2.6.  What is an Endpoint?  . . . . . . . . . . . . . . . . . .   6
     2.7.  Operating a Path Aware Network  . . . . . . . . . . . . .   7
     2.8.  Deploying a Path Aware Network  . . . . . . . . . . . . .   7
   3.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   8
   4.  Informative References  . . . . . . . . . . . . . . . . . . .   8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction to Path-Aware Networking

   In the current Internet architecture, the network layer provides an
   unverifiable, best-effort service: an application can assume that a
   packet with a given destination address will eventually be forwarded
   toward that destination, but little else.  A transport layer protocol
   such as TCP can provide reliability over this best-effort service,
   and a protocol above the network layer such as IPsec AH [RFC4302] or
   TLS [RFC8446] can authenticate the remote endpoint.  However, little,
   if any, explicit information about the path is available, and
   assumptions about that path often do not hold, sometimes with serious
   impacts on the application, as in the case with BGP hijacking
   attacks.

   By contrast, in a path-aware internetworking architecture, endpoints
   have the ability to select or influence the path through the network
   used by any given packet, and the network and transport layers
   explicitly expose information about the path or paths available from
   one endpoint to another, and vice versa, to those endpoints and the
   applications running on them, so that they can make this selection.

   Path selection provides transparency and control to applications and
   users of the network.  Selection may be made at either the
Show full document text