ALTO Server Discovery
draft-ietf-alto-server-discovery-04

The information below is for an old version of the document
Document Type Active Internet-Draft (alto WG)
Last updated 2012-07-16
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
ALTO                                                           S. Kiesel
Internet-Draft                                   University of Stuttgart
Intended status: Standards Track                          M. Stiemerling
Expires: January 17, 2013                                NEC Europe Ltd.
                                                               N. Schwan
                                                               M. Scharf
                                                Alcatel-Lucent Bell Labs
                                                                 H. Song
                                                                  Huawei
                                                           July 16, 2012

                         ALTO Server Discovery
                  draft-ietf-alto-server-discovery-04

Abstract

   The goal of Application-Layer Traffic Optimization (ALTO) is to
   provide guidance to applications, which have to select one or several
   hosts from a set of candidates that are able to provide a desired
   resource.

   Entities seeking guidance need to discover and possibly select an
   ALTO server to ask.  This is called ALTO server discovery.  This memo
   describes an ALTO server discovery mechanism based on several
   alternative mechanisms that are applicable when the resource consumer
   is co-located with the ALTO client.

Kiesel, et al.          Expires January 17, 2013                [Page 1]
Internet-Draft            ALTO Server Discovery                July 2012

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 January 17, 2013.

Copyright Notice

   Copyright (c) 2012 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, et al.          Expires January 17, 2013                [Page 2]
Internet-Draft            ALTO Server Discovery                July 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Discovery Scenarios  . . . . . . . . . . . . . . . . . . .  5
       1.1.1.  ALTO Server Discovery by Resource Consumers  . . . . .  6
       1.1.2.  ALTO Server Discovery by a Third Party . . . . . . . .  7
     1.2.  Pre-Conditions . . . . . . . . . . . . . . . . . . . . . .  8
   2.  Protocol Overview  . . . . . . . . . . . . . . . . . . . . . . 10
   3.  Retrieving the URI by U-NAPTR  . . . . . . . . . . . . . . . . 12
     3.1.  Retrieving the Domain Name . . . . . . . . . . . . . . . . 12
       3.1.1.  Option 1: User input . . . . . . . . . . . . . . . . . 12
       3.1.2.  Option 2: DHCP . . . . . . . . . . . . . . . . . . . . 13
       3.1.3.  Option 3: PPP  . . . . . . . . . . . . . . . . . . . . 13
     3.2.  U-NAPTR Resolution . . . . . . . . . . . . . . . . . . . . 14
   4.  Applicability  . . . . . . . . . . . . . . . . . . . . . . . . 16
     4.1.  Applicability for Resource Consumer Server Discovery . . . 16
     4.2.  Applicability for Third Party Server Discovery . . . . . . 16
   5.  Deployment Considerations  . . . . . . . . . . . . . . . . . . 18
     5.1.  DHCP option for DNS Suffix . . . . . . . . . . . . . . . . 18
     5.2.  PPP option for DNS Suffix  . . . . . . . . . . . . . . . . 18
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 19
Show full document text