RFC 6708 on Application-Layer Traffic Optimization (ALTO) Requirements

rfc-editor@rfc-editor.org Sun, 30 September 2012 16:34 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3333F21F86DC; Sun, 30 Sep 2012 09:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.325
X-Spam-Status: No, score=-102.325 tagged_above=-999 required=5 tests=[AWL=0.275, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id tOpw7msukIXd; Sun, 30 Sep 2012 09:34:43 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id B671A21F860D; Sun, 30 Sep 2012 09:34:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 28D1C72E104; Sun, 30 Sep 2012 09:30:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6708 on Application-Layer Traffic Optimization (ALTO) Requirements
From: rfc-editor@rfc-editor.org
Message-Id: <20120930163028.28D1C72E104@rfc-editor.org>
Date: Sun, 30 Sep 2012 09:30:28 -0700
Cc: alto@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Sep 2012 16:34:44 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6708

        Title:      Application-Layer Traffic Optimization (ALTO)
        Author:     S. Kiesel, Ed.,
                    S. Previdi, M. Stiemerling,
                    R. Woundy, Y. Yang
        Status:     Informational
        Stream:     IETF
        Date:       September 2012
        Mailbox:    ietf-alto@skiesel.de, 
        Pages:      20
        Characters: 47549
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-alto-reqs-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6708.txt

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 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 the
utilization of the underlying network infrastructure.

This document enumerates requirements for specifying, assessing, or
comparing protocols and implementations.  This document is not an 
Internet Standards Track specification; it is published for 
informational purposes.

This document is a product of the Application-Layer Traffic Optimization Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC