ALTO Deployment Considerations
draft-ietf-alto-deployments-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                                                 M. Stiemerling, Ed.
Internet-Draft                                           NEC Europe Ltd.
Intended status: Informational                            S. Kiesel, Ed.
Expires: April 25, 2013                          University of Stuttgart
                                                        October 22, 2012

                     ALTO Deployment Considerations
                     draft-ietf-alto-deployments-05

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 these applications, which have to select one or several
   hosts from a set of candidates, that are able to provide a desired
   resource.  The protocol is under specification in the ALTO working
   group.  This memo discusses deployment related issues of ALTO for
   peer-to-peer and CDNs, some preliminary security considerations, and
   also initial guidance for application designers using ALTO.

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

Stiemerling & Kiesel     Expires April 25, 2013                 [Page 1]
Internet-Draft          Deployment Considerations           October 2012

   (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 . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  General Considerations . . . . . . . . . . . . . . . . . . . .  5
     2.1.  General Placement of ALTO  . . . . . . . . . . . . . . . .  5
     2.2.  Relationship between ALTO and Applications . . . . . . . .  7
     2.3.  Provided Guidance  . . . . . . . . . . . . . . . . . . . .  7
       2.3.1.  Keeping Traffic Local in Network . . . . . . . . . . .  8
       2.3.2.  Off-Loading Traffic from Network . . . . . . . . . . .  8
       2.3.3.  Intra-Network Localization/Bottleneck Off-Loading  . .  9
     2.4.  Provisiong ALTO Maps . . . . . . . . . . . . . . . . . . . 11
   3.  Deployment Considerations by ISPs  . . . . . . . . . . . . . . 12
     3.1.  Requirement for Traffic Optimization by ISPs . . . . . . . 12
     3.2.  Considerations for ISPs  . . . . . . . . . . . . . . . . . 13
       3.2.1.  Very small ISPs with simple Network Structure  . . . . 13
       3.2.2.  Large ISPs with layered fixed Network Structure  . . . 13
       3.2.3.  ISPs with Mobile Network . . . . . . . . . . . . . . . 15
   4.  Using ALTO for P2P . . . . . . . . . . . . . . . . . . . . . . 17
     4.1.  Using ALTO for Tracker-based Peer-to-Peer Applications . . 19
     4.2.  Expectations of ALTO . . . . . . . . . . . . . . . . . . . 24
   5.  Using ALTO for CDNs  . . . . . . . . . . . . . . . . . . . . . 25
     5.1.  Request Routing using the Endpoint Cost Service  . . . . . 25
       5.1.1.  ALTO Topology Vs. Network Topology . . . . . . . . . . 26
       5.1.2.  Topology Computation and ECS Delivery  . . . . . . . . 26
       5.1.3.  Ranking Service  . . . . . . . . . . . . . . . . . . . 26
       5.1.4.  Ranking and Network Events . . . . . . . . . . . . . . 27
       5.1.5.  Caching and Lifetime . . . . . . . . . . . . . . . . . 27
       5.1.6.  Redirection  . . . . . . . . . . . . . . . . . . . . . 28
       5.1.7.  Groups and Costs . . . . . . . . . . . . . . . . . . . 28
   6.  Advanced Features  . . . . . . . . . . . . . . . . . . . . . . 29
Show full document text