Application-Layer Traffic Optimization (ALTO) Requirements
draft-ietf-alto-reqs-14

The information below is for an old version of the document
Document Type Active Internet-Draft (alto WG)
Last updated 2012-05-10 (latest revision 2012-04-19)
Replaces draft-kiesel-alto-reqs
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd Enrico Marocco
Shepherd write-up Show (last changed 2011-08-19)
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES.
Responsible AD Wesley Eddy
IESG note Enrico Marocco (enrico.marocco@telecomitalia.it) is the document shepherd.
Send notices to alto-chairs@tools.ietf.org, draft-ietf-alto-reqs@tools.ietf.org
Network Working Group                                     S. Kiesel, Ed.
Internet-Draft                                   University of Stuttgart
Intended status: Informational                                S. Previdi
Expires: October 21, 2012                            Cisco Systems, Inc.
                                                          M. Stiemerling
                                                         NEC Europe Ltd.
                                                               R. Woundy
                                                     Comcast Corporation
                                                               Y R. Yang
                                                         Yale University
                                                          April 19, 2012

       Application-Layer Traffic Optimization (ALTO) Requirements
                      draft-ietf-alto-reqs-14.txt

Abstract

   Many Internet applications are used to access resources, such as
   pieces of information or server processes, which are available in
   several equivalent replicas on different hosts.  This includes, but
   is not limited to, peer-to-peer file sharing applications.  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 capable of providing a desired resource.
   This guidance shall be based on parameters that affect performance
   and efficiency of the data transmission between the hosts, e.g., the
   topological distance.  The ultimate goal is to improve performance
   (or Quality of Experience) in the application while reducing resource
   consumption in the underlying network infrastructure.

   This document enumerates requirements for specifying, assessing, or
   comparing protocols and implementations.

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

Kiesel, et al.          Expires October 21, 2012                [Page 1]
Internet-Draft              ALTO Requirements                 April 2012

   This Internet-Draft will expire on October 21, 2012.

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 October 21, 2012                [Page 2]
Internet-Draft              ALTO Requirements                 April 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology and Architectural Framework  . . . . . . . . . . .  5
     2.1.  Requirements Notation  . . . . . . . . . . . . . . . . . .  5
     2.2.  ALTO Terminology . . . . . . . . . . . . . . . . . . . . .  5
     2.3.  Architectural Framework for ALTO . . . . . . . . . . . . .  6
   3.  ALTO Requirements  . . . . . . . . . . . . . . . . . . . . . .  7
     3.1.  ALTO Client Protocol . . . . . . . . . . . . . . . . . . .  7
       3.1.1.  General Requirements . . . . . . . . . . . . . . . . .  7
       3.1.2.  Host Group Descriptor Support  . . . . . . . . . . . .  7
       3.1.3.  Rating Criteria Support  . . . . . . . . . . . . . . .  8
       3.1.4.  Placement of Entities and Timing of Transactions . . .  9
       3.1.5.  Protocol Extensibility . . . . . . . . . . . . . . . . 11
       3.1.6.  Error Handling and Overload Protection . . . . . . . . 12
     3.2.  ALTO Server Discovery  . . . . . . . . . . . . . . . . . . 13
     3.3.  Security and Privacy . . . . . . . . . . . . . . . . . . . 14
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 17
Show full document text