Application Layer Traffic Optimization (ALTO) Cross-Domain Server Discovery
draft-ietf-alto-xdom-disc-04

Document Type Active Internet-Draft (alto WG)
Last updated 2018-11-14 (latest revision 2018-11-13)
Replaces draft-kiesel-alto-xdom-disc
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jan Seedorf
Shepherd write-up Show (last changed 2018-10-29)
IESG IESG state In Last Call (ends 2018-11-28)
Consensus Boilerplate Yes
Telechat date
Responsible AD Mirja K├╝hlewind
Send notices to Jan Seedorf <jan.seedorf@hft-stuttgart.de>
IANA IANA review state IANA OK - No Actions Needed
IANA action state None
ALTO                                                           S. Kiesel
Internet-Draft                                   University of Stuttgart
Intended status: Standards Track                          M. Stiemerling
Expires: May 18, 2019                                               H-DA
                                                       November 14, 2018

   Application Layer Traffic Optimization (ALTO) Cross-Domain Server
                               Discovery
                      draft-ietf-alto-xdom-disc-04

Abstract

   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications that have to select one or several
   hosts from a set of candidates capable of providing a desired
   resource.  ALTO is realized by a client-server protocol.  Before an
   ALTO client can ask for guidance it needs to discover one or more
   ALTO servers that can provide suitable guidance.

   In some deployment scenarios, in particular if the information about
   the network topology is partitioned and distributed over several ALTO
   servers, it may be needed to discover an ALTO server outside of the
   own network domain, in order to get appropriate guidance.  This
   document details applicable scenarios, itemizes requirements, and
   specifies a procedure for ALTO cross-domain server discovery.

   Technically, the procedure specified in this document takes one
   IP address or prefix and a U-NAPTR Service Parameter (typically,
   "ALTO:https") as parameters.  It performs DNS lookups (for NAPTR
   resource records in the in-addr.arpa. or ip6.arpa. tree) and returns
   one or more URI(s) of information resources related to that IP
   address or prefix.

Kiesel & Stiemerling      Expires May 18, 2019                  [Page 1]
Internet-Draft     ALTO Cross-Domain Server Discovery      November 2018

Terminology and Requirements Language

   This document makes use of the ALTO terminology defined in RFC 5693
   [RFC5693].

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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 May 18, 2019.

Copyright Notice

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

Kiesel & Stiemerling      Expires May 18, 2019                  [Page 2]
Internet-Draft     ALTO Cross-Domain Server Discovery      November 2018

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Overview on the ALTO Cross-Domain Server Discovery
       Procedure  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   3.  ALTO Cross-Domain Server Discovery Procedure Specification . .  6
     3.1.  Interface  . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.2.  Step 1: Prepare Domain Name for Reverse DNS Lookup . . . .  6
     3.3.  Step 2: Prepare Shortened Domain Names . . . . . . . . . .  7
     3.4.  Step 3: Perform DNS U-NAPTR lookups  . . . . . . . . . . .  8
     3.5.  Error Handling . . . . . . . . . . . . . . . . . . . . . .  9
   4.  Using the ALTO Protocol with Cross-Domain Server Discovery . . 10
     4.1.  Network and Cost Map Service . . . . . . . . . . . . . . . 10
     4.2.  Map-Filtering Service  . . . . . . . . . . . . . . . . . . 11
     4.3.  Endpoint Property Service  . . . . . . . . . . . . . . . . 11
     4.4.  Endpoint Cost Service  . . . . . . . . . . . . . . . . . . 11
     4.5.  Summary and Further Extensions . . . . . . . . . . . . . . 13
   5.  Implementation, Deployment, and Operational Considerations . . 14
Show full document text