RFC 5693 on Application-Layer Traffic Optimization (ALTO) Problem Statement

rfc-editor@rfc-editor.org Thu, 22 October 2009 23:46 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26CE33A67C2; Thu, 22 Oct 2009 16:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.202
X-Spam-Level:
X-Spam-Status: No, score=-17.202 tagged_above=-999 required=5 tests=[AWL=0.397, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDV-mfnRFkBh; Thu, 22 Oct 2009 16:46:34 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 2B0C43A67B1; Thu, 22 Oct 2009 16:46:34 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 71855350151; Thu, 22 Oct 2009 16:44:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5693 on Application-Layer Traffic Optimization (ALTO) Problem Statement
From: rfc-editor@rfc-editor.org
Message-Id: <20091022234405.71855350151@bosco.isi.edu>
Date: Thu, 22 Oct 2009 16:44:05 -0700
Cc: alto@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 22 Oct 2009 23:46:35 -0000

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

        
        RFC 5693

        Title:      Application-Layer Traffic Optimization (ALTO) Problem 
                    Statement 
        Author:     J. Seedorf, E. Burger
        Status:     Informational
        Date:       October 2009
        Mailbox:    jan.seedorf@nw.neclab.eu, 
                    eburger@standardstrack.com
        Pages:      14
        Characters: 34234
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-alto-problem-statement-04.txt

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

Distributed applications -- such as file sharing, real-time
communication, and live and on-demand media streaming -- prevalent on
the Internet use a significant amount of network resources.  Such
applications often transfer large amounts of data through connections
established between nodes distributed across the Internet with little
knowledge of the underlying network topology.  Some applications are
so designed that they choose a random subset of peers from a larger
set with which to exchange data.  Absent any topology information
guiding such choices, or acting on suboptimal or local information
obtained from measurements and statistics, these applications often
make less than desirable choices.

This document discusses issues related to an information-sharing
service that enables applications to perform better-than-random peer
selection.  This memo provides information for the Internet community.

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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
USC/Information Sciences Institute