[alto] RFC 8896 on Application-Layer Traffic Optimization (ALTO) Cost Calendar

rfc-editor@rfc-editor.org Fri, 06 November 2020 20:16 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6951D3A0EC8; Fri, 6 Nov 2020 12:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 p5Ro8gP8lRXv; Fri, 6 Nov 2020 12:16:46 -0800 (PST)
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 E76763A0DC4; Fri, 6 Nov 2020 12:16:33 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 20B26F40729; Fri, 6 Nov 2020 12:16:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20201106201611.20B26F40729@rfc-editor.org>
Date: Fri, 6 Nov 2020 12:16:11 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/K60c7kesash4IdC8lknIb9XFYtE>
Subject: [alto] =?utf-8?q?RFC_8896_on_Application-Layer_Traffic_Optimizat?= =?utf-8?q?ion_=28ALTO=29_Cost_Calendar?=
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Nov 2020 20:16:55 -0000

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

        
        RFC 8896

        Title:      Application-Layer Traffic Optimization (ALTO) Cost 
                    Calendar 
        Author:     S. Randriamasy,
                    R. Yang,
                    Q. Wu,
                    L. Deng,
                    N. Schwan
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2020
        Mailbox:    sabine.randriamasy@nokia-bell-labs.com, 
                    yry@cs.yale.edu, 
                    sunseawq@huawei.com, 
                    denglingli@chinamobile.com, 
                    nico.schwan@thalesgroup.com
        Pages:      35
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-alto-cost-calendar-21.txt

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

        DOI:        10.17487/RFC8896

This document is an extension to the base Application-Layer Traffic
Optimization (ALTO) protocol.  It extends the ALTO cost information
service so that applications decide not only 'where' to connect but
also 'when'.  This is useful for applications that need to perform
bulk data transfer and would like to schedule these transfers during
an off-peak hour, for example.  This extension introduces the ALTO
Cost Calendar with which an ALTO Server exposes ALTO cost values in
JSON arrays where each value corresponds to a given time interval. 
The time intervals, as well as other Calendar attributes, are
specified in the Information Resources Directory and ALTO Server
responses.

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