ALTO Extension: Path Vector
draft-ietf-alto-path-vector-08

Document Type Active Internet-Draft (alto WG)
Last updated 2019-07-22
Replaces draft-yang-alto-path-vector
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
ALTO WG                                                           K. Gao
Internet-Draft                                        Sichuan University
Intended status: Standards Track                                  Y. Lee
Expires: January 23, 2020                                         Huawei
                                                          S. Randriamasy
                                                         Nokia Bell Labs
                                                                 Y. Yang
                                                         Yale University
                                                                J. Zhang
                                                       Tongji University
                                                           July 22, 2019

                      ALTO Extension: Path Vector
                     draft-ietf-alto-path-vector-08

Abstract

   This document defines an ALTO extension that allows a resource to
   provide not only preferences of network paths but also correlations
   of network paths, including aggregations of network components and
   their properties on the paths between different PIDs or endpoints.
   The extended information can be used to improve the robustness and
   performance for applications in some new usage scenarios, such as
   high-speed data transfers and traffic optimization using in-network
   storage and computation.  This document introduces abstract network
   element (ANE) as an abstraction for aggregations of network
   components.  It extends the base protocol and the Unified Property
   extension to enable the capability of encoding such information in a
   "path vector", i.e., an array of ANEs that are traversed by traffic
   from a source to a destination.

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 [RFC2119].

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 http://datatracker.ietf.org/drafts/current/.

Gao, et al.             Expires January 23, 2020                [Page 1]
Internet-Draft         ALTO Extension: Path Vector             July 2019

   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 January 23, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Shared Risk Resource Group  . . . . . . . . . . . . . . .   6
     3.2.  Capacity Region . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  In-Network Caching  . . . . . . . . . . . . . . . . . . .   9
   4.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  Workflow  . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Abstract Network Element  . . . . . . . . . . . . . . . .  11
     4.3.  Protocol Extensions . . . . . . . . . . . . . . . . . . .  12
       4.3.1.  Path Vector Cost Type . . . . . . . . . . . . . . . .  12
       4.3.2.  Property Negotiation  . . . . . . . . . . . . . . . .  12
       4.3.3.  Multipart/Related Message . . . . . . . . . . . . . .  13
   5.  Basic Data Types  . . . . . . . . . . . . . . . . . . . . . .  14
     5.1.  ANE Identifier  . . . . . . . . . . . . . . . . . . . . .  15
     5.2.  Path Vector Cost Type . . . . . . . . . . . . . . . . . .  15
       5.2.1.  Cost Metric: ane-path . . . . . . . . . . . . . . . .  15
       5.2.2.  Cost Mode: array  . . . . . . . . . . . . . . . . . .  15
     5.3.  ANE Domain  . . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text