datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

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

Document type: Active Internet-Draft (alto WG)
Document stream: IETF
Last updated: 2014-02-13
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

IETF State: WG Document
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

ALTO                                                 M. Stiemerling, Ed.
Internet-Draft                                           NEC Europe Ltd.
Intended status: Informational                            S. Kiesel, Ed.
Expires: August 15, 2014                         University of Stuttgart
                                                              S. Previdi
                                                                   Cisco
                                                               M. Scharf
                                                Alcatel-Lucent Bell Labs
                                                       February 11, 2014

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

Abstract

   Many Internet applications are used to access resources such as
   pieces of information or server processes that 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 that have to select one or several hosts
   from a set of candidates, which are able to provide a desired
   resource.  This memo discusses deployment related issues of ALTO.  It
   addresses different use cases of ALTO such as peer-to-peer file
   sharing and CDNs, security considerations, recommendations for
   network administrators, and also 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 August 15, 2014.

Stiemerling, et al.      Expires August 15, 2014                [Page 1]
Internet-Draft          Deployment Considerations          February 2014

Copyright Notice

   Copyright (c) 2014 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.  General Considerations  . . . . . . . . . . . . . . . . . . .   4
     2.1.  ALTO Entities . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.1.  Baseline Scenario . . . . . . . . . . . . . . . . . .   4
       2.1.2.  Placement of ALTO Entities  . . . . . . . . . . . . .   4
     2.2.  Classification of Deployment Scenarios  . . . . . . . . .   6
       2.2.1.  Deployment Degrees of Freedom . . . . . . . . . . . .   6
       2.2.2.  Information Exposure  . . . . . . . . . . . . . . . .   7
       2.2.3.  More Advanced Deployments . . . . . . . . . . . . . .   8
   3.  Deployment Considerations by ISPs . . . . . . . . . . . . . .   9
     3.1.  Objectives for the Guidance to Applications . . . . . . .   9
       3.1.1.  General Objectives for Traffic Optimization . . . . .  10
       3.1.2.  Inter-Network Traffic Localization  . . . . . . . . .  11
       3.1.3.  Intra-Network Traffic Localization  . . . . . . . . .  12
       3.1.4.  Network Off-Loading . . . . . . . . . . . . . . . . .  13
       3.1.5.  Application Tuning  . . . . . . . . . . . . . . . . .  14
     3.2.  Provisioning of ALTO Maps . . . . . . . . . . . . . . . .  14
       3.2.1.  Data Sources  . . . . . . . . . . . . . . . . . . . .  15
       3.2.2.  Privacy Requirements  . . . . . . . . . . . . . . . .  17
       3.2.3.  Map Partitioning and Grouping . . . . . . . . . . . .  18
       3.2.4.  Rating Criteria and/or Cost Calculation . . . . . . .  18
     3.3.  Known Limitations of ALTO . . . . . . . . . . . . . . . .  21
       3.3.1.  Limitations of Map-based Approaches . . . . . . . . .  21
       3.3.2.  Limitiations of Non-Map-based Approaches  . . . . . .  23

[include full document text]