RFC 9569 on The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)

rfc-editor@rfc-editor.org Wed, 11 September 2024 05:31 UTC

Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28921C15106F; Tue, 10 Sep 2024 22:31:42 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 8ED823B873; Tue, 10 Sep 2024 22:31:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9569 on The Application-Layer Traffic Optimization (ALTO) Transport Information Publication Service (TIPS)
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240911053141.8ED823B873@rfcpa.rfc-editor.org>
Date: Tue, 10 Sep 2024 22:31:41 -0700
Message-ID-Hash: IRERDHDTLZGSHA6M53PBYN56P6QEID6X
X-Message-ID-Hash: IRERDHDTLZGSHA6M53PBYN56P6QEID6X
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, alto@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jnaNmcbYRvzQ_UEm_4rQQ0nLedE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>

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

        
        RFC 9569

        Title:      The Application-Layer Traffic Optimization (ALTO) 
                    Transport Information Publication Service (TIPS) 
        Author:     K. Gao,
                    R. Schott,
                    Y. R. Yang,
                    L. Delwiche,
                    L. Keller
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2024
        Mailbox:    kaigao@scu.edu.cn,
                    Roland.Schott@telekom.de,
                    yry@cs.yale.edu,
                    lauren.delwiche@yale.edu,
                    lachlan.keller@aya.yale.edu
        Pages:      40
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-alto-new-transport-22.txt

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

        DOI:        10.17487/RFC9569

"Application-Layer Traffic Optimization (ALTO) Protocol" (RFC 7285)
leverages HTTP/1.1 and is designed for the simple, sequential
request-reply use case, in which an ALTO client requests a sequence
of information resources and the server responds with the complete
content of each resource, one at a time.

RFC 8895, which describes ALTO incremental updates using Server-Sent
Events (SSE), defines a multiplexing protocol on top of HTTP/1.x, so
that an ALTO server can incrementally push resource updates to
clients whenever monitored network information resources change,
allowing the clients to monitor multiple resources at the same time.
However, HTTP/2 and later versions already support concurrent,
non-blocking transport of multiple streams in the same HTTP
connection.

To take advantage of newer HTTP features, this document introduces
the ALTO Transport Information Publication Service (TIPS). TIPS uses
an incremental RESTful design to give an ALTO client the new
capability to explicitly and concurrently (in a non-blocking manner)
request (or pull) specific incremental updates using HTTP/2 or
HTTP/3, while still functioning for HTTP/1.1.

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