[alto] RFC 9275 on An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector
rfc-editor@rfc-editor.org Fri, 23 September 2022 20:39 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 5071EC1526FC; Fri, 23 Sep 2022 13:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level:
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, 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 X5ugpnJDgiju; Fri, 23 Sep 2022 13:39:21 -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 4BDA8C1526F9; Fri, 23 Sep 2022 13:39:21 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 227E516E4C7; Fri, 23 Sep 2022 13:39:21 -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: <20220923203921.227E516E4C7@rfcpa.amsl.com>
Date: Fri, 23 Sep 2022 13:39:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/epNxFZ-UnDnwE82hp8CeFcE4Cyo>
Subject: [alto] RFC 9275 on An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector
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: Fri, 23 Sep 2022 20:39:25 -0000
A new Request for Comments is now available in online RFC libraries. RFC 9275 Title: An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector Author: K. Gao, Y. Lee, S. Randriamasy, Y. Yang, J. Zhang Status: Experimental Stream: IETF Date: September 2022 Mailbox: kaigao@scu.edu.cn, younglee.tx@gmail.com, sabine.randriamasy@nokia-bell-labs.com, yry@cs.yale.edu, jingxuan.n.zhang@gmail.com Pages: 54 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-alto-path-vector-25.txt URL: https://www.rfc-editor.org/info/rfc9275 DOI: 10.17487/RFC9275 This document is an extension to the base Application-Layer Traffic Optimization (ALTO) protocol. It extends the ALTO cost map and ALTO property map services so that an application can decide to which endpoint(s) to connect based not only on numerical/ordinal cost values but also on fine-grained abstract information regarding the paths. This is useful for applications whose performance is impacted by specific components of a network on the end-to-end paths, e.g., they may infer that several paths share common links and prevent traffic bottlenecks by avoiding such paths. This extension introduces a new abstraction called the "Abstract Network Element" (ANE) to represent these components and encodes a network path as a vector of ANEs. Thus, it provides a more complete but still abstract graph representation of the underlying network(s) for informed traffic optimization among endpoints. This document is a product of the Application-Layer Traffic Optimization Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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
- [alto] RFC 9275 on An Extension for Application-L… rfc-editor
- Re: [alto] RFC 9275 on An Extension for Applicati… Qin Wu
- Re: [alto] RFC 9275 on An Extension for Applicati… Y. Richard Yang
- Re: [alto] RFC 9275 on An Extension for Applicati… Randriamasy, Sabine (Nokia - FR/Paris-Saclay)