[alto] RFC 9274 on A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol

rfc-editor@rfc-editor.org Tue, 26 July 2022 20:16 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 1C849C13193B; Tue, 26 Jul 2022 13:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMMgmEeva-L5; Tue, 26 Jul 2022 13:16:38 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DEA4DC131938; Tue, 26 Jul 2022 13:16:38 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9687F4C29F; Tue, 26 Jul 2022 13:16:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20220726201638.9687F4C29F@rfcpa.amsl.com>
Date: Tue, 26 Jul 2022 13:16:38 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/nXLDpYo6q24KIyHfezJF4uSp7F4>
Subject: [alto] =?utf-8?q?RFC_9274_on_A_Cost_Mode_Registry_for_the_Applic?= =?utf-8?q?ation-Layer_Traffic_Optimization_=28ALTO=29_Protocol?=
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 26 Jul 2022 20:16:43 -0000

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

        
        RFC 9274

        Title:      A Cost Mode Registry for the Application-Layer 
                    Traffic Optimization (ALTO) Protocol 
        Author:     M. Boucadair,
                    Q. Wu
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2022
        Mailbox:    mohamed.boucadair@orange.com,
                    bill.wu@huawei.com
        Pages:      7
        Updates:    RFC 7285

        I-D Tag:    draft-ietf-alto-cost-mode-05.txt

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

        DOI:        10.17487/RFC9274

This document creates a new IANA registry for tracking cost modes
supported by the Application-Layer Traffic Optimization (ALTO)
Protocol. Also, this document relaxes a constraint that was imposed
by the ALTO specification on allowed cost mode values.

This document updates RFC 7285.

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