[rfc-dist] RFC 7286 on Application-Layer Traffic Optimization (ALTO) Server Discovery

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Nov 14 15:46:15 PST 2014

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

        RFC 7286

        Title:      Application-Layer Traffic Optimization (ALTO) Server 
        Author:     S. Kiesel, M. Stiemerling,
                    N. Schwan, M. Scharf,
                    H. Song
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2014
        Mailbox:    ietf-alto at skiesel.de, 
                    mls.ietf at gmail.com, 
                    ietf at nico-schwan.de,
                    michael.scharf at alcatel-lucent.com, 
                    haibin.song at huawei.com
        Pages:      15
        Characters: 32830
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-alto-server-discovery-10.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7286.txt

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.  ALTO is realized by a client-server protocol.  Before an
ALTO client can ask for guidance, it needs to discover one or more
ALTO servers.

This document specifies a procedure for resource-consumer-initiated
ALTO server discovery, which can be used if the ALTO client is
embedded in the resource consumer.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor at 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

More information about the rfc-dist mailing list