ALTO Protocol
draft-ietf-alto-protocol-24
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (alto WG)
|
|
Last updated |
|
2014-01-16
(latest revision 2013-12-11)
|
|
Replaces |
|
draft-penno-alto-protocol
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Enrico Marocco
|
|
Shepherd write-up |
|
Show
(last changed 2013-12-12)
|
| IESG |
IESG state |
|
Publication Requested::Revised I-D Needed
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
Spencer Dawkins
|
|
IESG note |
|
Enrico Marocco (enrico.marocco@telecomitalia.it) is the document shepherd.
|
|
Send notices to |
|
alto-chairs@tools.ietf.org, draft-ietf-alto-protocol@tools.ietf.org
|
ALTO WG R. Alimi, Ed.
Internet-Draft Google
Intended status: Standards Track R. Penno, Ed.
Expires: June 13, 2014 Cisco Systems
Y. Yang, Ed.
Yale University
December 10, 2013
ALTO Protocol
draft-ietf-alto-protocol-24.txt
Abstract
Applications using the Internet already have access to some topology
information of Internet Service Provider (ISP) networks. For
example, views to Internet routing tables at looking glass servers
are available and can be practically downloaded to many network
application clients. What is missing is knowledge of the underlying
network topologies from the point of view of ISPs. In other words,
what an ISP prefers in terms of traffic optimization -- and a way to
distribute it.
The Application-Layer Traffic Optimization (ALTO) Service provides
network information (e.g., basic network location structure and
preferences of network paths) with the goal of modifying network
resource consumption patterns while maintaining or improving
application performance. The basic information of ALTO is based on
abstract maps of a network. These maps provide a simplified view,
yet enough information about a network for applications to
effectively utilize them. Additional services are built on top of
the maps.
This document describes a protocol implementing the ALTO Service.
Although the ALTO Service would primarily be provided by ISPs, other
entities such as content service providers could also operate an ALTO
Service. Applications that could use this service are those that
have a choice to which end points to connect. Examples of such
applications are peer-to-peer (P2P) and content delivery networks.
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
Alimi, et al. Expires June 13, 2014 [Page 1]
Internet-Draft ALTO Protocol December 2013
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 June 13, 2014.
Copyright Notice
Copyright (c) 2013 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.
Alimi, et al. Expires June 13, 2014 [Page 2]
Internet-Draft ALTO Protocol December 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1. Problem Statement . . . . . . . . . . . . . . . . . . . . 7
1.2. Design Overview . . . . . . . . . . . . . . . . . . . . . 8
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1. Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2. Endpoint Address . . . . . . . . . . . . . . . . . . . . . 8
2.3. Network Location . . . . . . . . . . . . . . . . . . . . . 9
2.4. ALTO Information . . . . . . . . . . . . . . . . . . . . . 9
2.5. ALTO Information Base . . . . . . . . . . . . . . . . . . 9
Show full document text