Dear all,
We have prepared a new revision of the new transport document (version -12) [1] based on the AD review and follow-up discussions. The major changes include - Add a paragraph to discuss why this extension should coexist with RFC 8895 - Move the server push feature to the appendix - Several clarifications and text edits (see diffs [2] for details) Please feel free to provide feedback or comments. Thanks! Best, Kai [1] https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/12/ [2] https://author-tools.ietf.org/iddiff?url1=draft-ietf-alto-new-transport-11&url2=draft-ietf-alto-new-transport-12&difftype=--html -----Original Messages----- From: internet-dra...@ietf.org Sent Time: 2023-07-24 23:17:39 (Monday) To: "Y. Yang" <y...@cs.yale.edu>, "Kai Gao" <kai...@scu.edu.cn>, "Lachlan Keller" <lachlan.kel...@yale.edu>, "Lauren Delwiche" <lauren.delwi...@yale.edu>, "Roland Schott" <roland.sch...@telekom.de>, "Yang Richard Yang" <y...@cs.yale.edu> Cc: Subject: New Version Notification for draft-ietf-alto-new-transport-12.txt A new version of I-D, draft-ietf-alto-new-transport-12.txt has been successfully submitted by Kai Gao and posted to the IETF repository. Name: draft-ietf-alto-new-transport Revision: 12 Title: The ALTO Transport Information Publication Service Document date: 2023-07-24 Group: alto Pages: 54 URL: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-12.txt Status: https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ Html: https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-12.html Htmlized: https://datatracker.ietf.org/doc/html/draft-ietf-alto-new-transport Diff: https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-12 Abstract: The 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. ALTO incremental updates using Server-Sent Events (SSE) (RFC 8895) 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, concurrently (non-blocking) request (pull) specific incremental updates using native HTTP/2 or HTTP/3, while still functioning for HTTP/1.1. The IETF Secretariat
_______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
