Congratulation to authors who complete one of last two milestones.
-Qin
-----邮件原件-----
发件人: rfc-edi...@rfc-editor.org [mailto:rfc-edi...@rfc-editor.org]
发送时间: 2024年9月11日 13:32
收件人: ietf-annou...@ietf.org; rfc-d...@rfc-editor.org
抄送: rfc-edi...@rfc-editor.org; drafts-update-...@iana.org; alto@ietf.org
主题: [alto] RFC 9569 on The Application-Layer Traffic Optimization (ALTO)
Transport Information Publication Service (TIPS)
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: kai...@scu.edu.cn,
roland.sch...@telekom.de,
y...@cs.yale.edu,
lauren.delwi...@yale.edu,
lachlan.kel...@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-edi...@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 mailing list -- alto@ietf.org
To unsubscribe send an email to alto-le...@ietf.org
_______________________________________________
alto mailing list -- alto@ietf.org
To unsubscribe send an email to alto-le...@ietf.org
