Providing Next External Hop Path Information to End Hosts
draft-jaufeerally-nexthop-path-info-00

Document Type Active Internet-Draft (individual)
Last updated 2018-12-10
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Path Aware Networking Research Group                      R. Jaufeerally
Internet-Draft                                                  AS210036
Intended status: Experimental                          December 10, 2018
Expires: June 13, 2019

       Providing Next External Hop Path Information to End Hosts
                 draft-jaufeerally-nexthop-path-info-00

Abstract

   The aim of this document is to define an interface through which an
   Autonomous System (AS) can disseminate information about forwarding
   of packets to the next hop outside the AS, to devices within its
   network.  This information can be used to make path aware routing
   decisions, either by being aware of the default route packets will
   take when traversing the AS, or by using other mechanisms to control
   the path packets which is out of the scope of this document.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [1].

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 June 13, 2019.

Copyright Notice

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

Jaufeerally               Expires June 13, 2019                 [Page 1]
Internet-Draft           panrg-nexthop-path-info           December 2018

   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
   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Detection of Path Aware Functionality . . . . . . . . . . . .   3
   3.  The Path Service  . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The current state of the internet is such that routing decisions are
   made by the network operator, and the end user has no a priori
   information about network paths.  It is possible to manually find
   information about paths a posteriori using tools such as traceroute.

   There exists unstandardized out of band mechanisms such as looking
   glasses [3] and specialized tools like NLNOG RING [4] that allow for
   customizable introspection of the network control and data plane.
   These tools provide valuable information to network engineers, and
   enthusiastic end users to ascertain information about forwarding
   routes which packets are nominally following.

   This document defines a standardized interface to provide network
   path information to end hosts, routers, and other devices within a
   network.  This path awareness can be used to optimize use of network
   resources by the end host, for example allowing programmatic
   decisions on which links to use for a given packet.

   The implementation strategy we define is a mechanism to bootstrap
   devices within an AS with the information required to obtain path
   awareness from the network control plane.  In addition, we define a
   standard format for the interchange of path information in this
   context.

Jaufeerally               Expires June 13, 2019                 [Page 2]
Internet-Draft           panrg-nexthop-path-info           December 2018

2.  Detection of Path Aware Functionality

   In order for an end host to make use of the path aware functionality
   in a network, the host needs to detect that the network supports such
Show full document text