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

The information below is for an old version of the document
Document Type Active Internet-Draft (alto WG)
Last updated 2012-10-22
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: April 25, 2013                                  NEC Europe Ltd.
                                                               N. Schwan
                                                      Stuttgart, Germany
                                                               M. Scharf
                                                Alcatel-Lucent Bell Labs
                                                                 H. Song
                                                                  Huawei
                                                        October 22, 2012

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

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 resource consumer initiated
   ALTO server discovery, which can be used if the ALTO client is
   embedded in the resource consumer.

Kiesel, et al.           Expires April 25, 2013                 [Page 1]
Internet-Draft            ALTO Server Discovery             October 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 April 25, 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 April 25, 2013                 [Page 2]
Internet-Draft            ALTO Server Discovery             October 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  ALTO Server Discovery Procedure Overview . . . . . . . . . . .  5
   3.  ALTO Server Discovery Procedure Specification  . . . . . . . .  6
     3.1.  Step 1: Retrieving the Domain Name . . . . . . . . . . . .  6
       3.1.1.  Step 1, Option 1: User input . . . . . . . . . . . . .  6
       3.1.2.  Step 1, Option 2: DHCP . . . . . . . . . . . . . . . .  6
     3.2.  Step 2: U-NAPTR Resolution . . . . . . . . . . . . . . . .  6
   4.  Deployment Considerations  . . . . . . . . . . . . . . . . . .  8
     4.1.  Issues with Home Gateways  . . . . . . . . . . . . . . . .  8
     4.2.  Issues with Multihoming, Mobility and Changing IP
           Addresses  . . . . . . . . . . . . . . . . . . . . . . . .  8
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
     6.1.  General  . . . . . . . . . . . . . . . . . . . . . . . . . 11
     6.2.  For U-NAPTR  . . . . . . . . . . . . . . . . . . . . . . . 11
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 13
Show full document text