RFC 7286 on Application-Layer Traffic Optimization (ALTO) Server Discovery
rfc-editor@rfc-editor.org Fri, 14 November 2014 23:46 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 330BC1A88B6; Fri, 14 Nov 2014 15:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.496
X-Spam-Level:
X-Spam-Status: No, score=-102.496 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9w6ZcGNNDLoq; Fri, 14 Nov 2014 15:46:54 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 7809C1A88B5; Fri, 14 Nov 2014 15:46:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B3514181C89; Fri, 14 Nov 2014 15:46:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7286 on Application-Layer Traffic Optimization (ALTO) Server Discovery
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20141114234615.B3514181C89@rfc-editor.org>
Date: Fri, 14 Nov 2014 15:46:15 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/h5oNr_y_F1Uqg0EoTtQciiJFOnA
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.15
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: <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: Fri, 14 Nov 2014 23:46:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7286
Title: Application-Layer Traffic Optimization (ALTO) Server
Discovery
Author: S. Kiesel, M. Stiemerling,
N. Schwan, M. Scharf,
H. Song
Status: Standards Track
Stream: IETF
Date: November 2014
Mailbox: ietf-alto@skiesel.de,
mls.ietf@gmail.com,
ietf@nico-schwan.de,
michael.scharf@alcatel-lucent.com,
haibin.song@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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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@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