RFC 8189 on Multi-Cost Application-Layer Traffic Optimization (ALTO)

rfc-editor@rfc-editor.org Wed, 25 October 2017 00:16 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9656313A344; Tue, 24 Oct 2017 17:16:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 I6zbnUzKqh9i; Tue, 24 Oct 2017 17:16:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EDAF13A1FA; Tue, 24 Oct 2017 17:16:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 842F2B81561; Tue, 24 Oct 2017 17:16:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8189 on Multi-Cost Application-Layer Traffic Optimization (ALTO)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, alto@ietf.org
Message-Id: <20171025001633.842F2B81561@rfc-editor.org>
Date: Tue, 24 Oct 2017 17:16:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/SZKegxZzApJvm-8ZL-fxXVhTxBY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: <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: Wed, 25 Oct 2017 00:16:37 -0000

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

        
        RFC 8189

        Title:      Multi-Cost Application-Layer Traffic Optimization (ALTO) 
        Author:     S. Randriamasy, 
                    W. Roome,
                    N. Schwan
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2017
        Mailbox:    sabine.randriamasy@nokia-bell-labs.com, 
                    ietf@wdroome.com, 
                    nico.schwan@thalesgroup.com
        Pages:      29
        Characters: 57010
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-alto-multi-cost-10.txt

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

        DOI:        10.17487/RFC8189

The Application-Layer Traffic Optimization (ALTO) protocol, specified
in RFC 7285, defines several services that return various metrics
describing the costs between network endpoints.

This document defines a new service that allows an ALTO Client to
retrieve several cost metrics in a single request for an ALTO
filtered cost map and endpoint cost map.  In addition, it extends the
constraints to further filter those maps by allowing an ALTO Client
to specify a logical combination of tests on several cost metrics.

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/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