RFC 7971 on Application-Layer Traffic Optimization (ALTO) Deployment Considerations

rfc-editor@rfc-editor.org Fri, 07 October 2016 00: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 B25861294C8; Thu, 6 Oct 2016 17:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.598
X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wx3ZFbwY1u8C; Thu, 6 Oct 2016 17:34:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C810A129424; Thu, 6 Oct 2016 17:34:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C201DB811A7; Thu, 6 Oct 2016 17:34:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7971 on Application-Layer Traffic Optimization (ALTO) Deployment Considerations
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161007003421.C201DB811A7@rfc-editor.org>
Date: Thu, 06 Oct 2016 17:34:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/ahXSTLRqvxh5b26DREOsWfT4iIM>
Cc: drafts-update-ref@iana.org, alto@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 07 Oct 2016 00:34:25 -0000

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

        RFC 7971

        Title:      Application-Layer Traffic Optimization (ALTO)
                    Deployment Considerations 
        Author:     M. Stiemerling, 
                    S. Kiesel,
                    M. Scharf,
                    H. Seidel,
                    S. Previdi
        Status:     Informational
        Stream:     IETF
        Date:       October 2016
        Mailbox:    mls.ietf@gmail.com, 
        Pages:      77
        Characters: 188372
        Updates/Obsoletes/SeeAlso:   None

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

        URL:        https://www.rfc-editor.org/info/rfc7971

        DOI:        http://dx.doi.org/10.17487/RFC7971

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 memo discusses deployment-related issues of ALTO.  It addresses
different use cases of ALTO such as peer-to-peer file sharing and
Content Delivery Networks (CDNs) and presents corresponding examples.
The document also includes recommendations for network administrators
and application designers planning to deploy ALTO, such as
recommendations on how to generate ALTO map information.

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 https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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