Extensible Property Maps for the ALTO Protocol
draft-roome-alto-unified-props-new-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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)
ALTO WG                                                         W. Roome
Internet-Draft                                           Nokia Bell Labs
Intended status: Standards Track                                 R. Yang
Expires: September 14, 2017                              Yale University
                                                          March 13, 2017

             Extensible Property Maps for the ALTO Protocol
                 draft-roome-alto-unified-props-new-00

Abstract

   This document extends the Application-Layer Traffic Optimization
   (ALTO) Protocol [RFC7285] by generalizing the concept of "endpoint
   properties" to other entity domains, and by presenting those
   properties as maps, similar to the network and cost maps in ALTO.

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/.

   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 September 14, 2017.

Copyright Notice

   Copyright (c) 2017 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

Roome & Yang           Expires September 14, 2017               [Page 1]
Internet-Draft             Unified Properties                 March 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions and Concepts  . . . . . . . . . . . . . . . . . .   4
     2.1.  Entities  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Domains . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Entity Addresses  . . . . . . . . . . . . . . . . . . . .   4
     2.4.  Domain Names  . . . . . . . . . . . . . . . . . . . . . .   5
     2.5.  Property Names  . . . . . . . . . . . . . . . . . . . . .   5
     2.6.  Relationship to Network Maps  . . . . . . . . . . . . . .   6
   3.  Entity Domains  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Internet Address Domains  . . . . . . . . . . . . . . . .   7
       3.1.1.  IPV4 Domain . . . . . . . . . . . . . . . . . . . . .   7
       3.1.2.  IPV6 Domain . . . . . . . . . . . . . . . . . . . . .   7
       3.1.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   7
       3.1.4.  Relationship To Network Maps  . . . . . . . . . . . .   8
     3.2.  PID Domain  . . . . . . . . . . . . . . . . . . . . . . .   9
       3.2.1.  Domain Name . . . . . . . . . . . . . . . . . . . . .   9
       3.2.2.  Domain-Specific Entity Addresses  . . . . . . . . . .   9
       3.2.3.  Heirarchy And Inheritance . . . . . . . . . . . . . .   9
       3.2.4.  Relationship To Internet Addresses Domains  . . . . .   9
     3.3.  Internet Address Properties vs. PID Properties  . . . . .   9
   4.  Property Map Resource . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Media Type  . . . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  HTTP Method . . . . . . . . . . . . . . . . . . . . . . .  10
     4.3.  Accept Input Parameters . . . . . . . . . . . . . . . . .  10
     4.4.  Capabilities  . . . . . . . . . . . . . . . . . . . . . .  10
     4.5.  Uses  . . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.6.  Response  . . . . . . . . . . . . . . . . . . . . . . . .  10
   5.  Filtered Property Map Resource  . . . . . . . . . . . . . . .  12
     5.1.  Media Type  . . . . . . . . . . . . . . . . . . . . . . .  12
     5.2.  HTTP Method . . . . . . . . . . . . . . . . . . . . . . .  12
Show full document text