RFC 9274: A Cost Mode Registry for the Application-Layer Traffic Optimization (ALTO) Protocol
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9274
- Published
- July 2022
- Authors
- M. Boucadair; Q. Wu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 7285
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6706Asymmetric Extended Route Optimization (AERO)Current
August 2012
- RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent
September 2020
- RFC 8481Clarifications to BGP Origin Validation Based on Resource Public Key Infrastructure (RPKI)Updated
September 2018
- RFC 7075Realm-Based Redirection In DiameterCurrent
November 2013
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 6198Requirements for the Graceful Shutdown of BGP SessionsCurrent
April 2011
- RFC 4786Operation of Anycast ServicesCurrent
December 2006
- RFC 4779ISP IPv6 Deployment Scenarios in Broadband Access NetworksCurrent
January 2007
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?