Third-Party ALTO Server Discovery (3pdisc)
draft-kist-alto-3pdisc-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-07-15
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ALTO                                                           S. Kiesel
Internet-Draft                                                 K. Krause
Intended status: Experimental                    University of Stuttgart
Expires: January 16, 2014                                 M. Stiemerling
                                                         NEC Europe Ltd.
                                                           July 15, 2013

               Third-Party ALTO Server Discovery (3pdisc)
                       draft-kist-alto-3pdisc-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.

   This document specifies a procedure for third-party ALTO server
   discovery, which can be used if the ALTO client is not co-located
   with the actual resource consumer, but instead embedded in a third
   party such as a peer-to-peer tracker.

   Technically, the algorithm specified in this document takes one
   IP address and a U-NAPTR Service Parameter (i.e., "ALTO:http" or
   "ALTO:https") as parameters.  It performs several DNS lookups (for
   U-NAPTR and SOA resource records) and returns one or more URI(s) of
   information resources related to that IP address.

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", "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.

Kiesel, et al.          Expires January 16, 2014                [Page 1]
Internet-Draft      Third-Party ALTO Server Discovery          July 2013

   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 January 16, 2014.

Copyright Notice

   Copyright (c) 2013 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Third-party ALTO Server             Discovery Procedure
       Specification . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Interface . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Basic Principle . . . . . . . . . . . . . . . . . . . . .   4
     2.3.  Overall Procedure . . . . . . . . . . . . . . . . . . . .   5
     2.4.  Specification of Tasks and Conditional Branches . . . . .   6
       2.4.1.  T1: Prepare Domain Name for Reverse DNS Lookup  . . .   7
       2.4.2.  T2/B1: U-NAPTR Lookup in Reverse Zone . . . . . . . .   7
       2.4.3.  B2/T3/B3: Acquire SOA Record for Reverse Zone . . . .   8
       2.4.4.  T4/B4: U-NAPTR Lookup on SOA-MNAME  . . . . . . . . .   9
   3.  Implementation, Deployment, and Operational Considerations  .   9
     3.1.  Considerations for ALTO Clients . . . . . . . . . . . . .   9
       3.1.1.  Resource Consumer Initiated Discovery . . . . . . . .   9
       3.1.2.  IPv4/v6 Dual Stack, Multihoming, NAT, and
               Host Mobility . . . . . . . . . . . . . . . . . . . .   9
     3.2.  Deployment Considerations for Network Operators . . . . .  10
       3.2.1.  NAPTR in Reverse Tree vs. SOA-based discovery . . . .  10
Show full document text