Hey all, Thank you so much for the feedback on the last draft. The diff for this draft shows a lot of changes but they are mostly structural movements and small clarifications.
The following changes were made: - Restructured the Abstract (based on Adrian's feedback) and Section 2 (based on Jordi's feedback) to be more clear on the abstractions we are proposing - Moved Requirements Language into Section 1 per RFC guidelines - Added a Section 2.3 to clarify TIPS with HTTP/1.x, because Qin noted the draft was unclear on how TIPS related to HTTP versions - Merged in the TIPS server push draft [draft-schott-alto-new-transport-push] into Section 7 (all but 3 sections of that draft were shared by this transport draft so they were copy/pasted into Section 7 - there are now 3 subsections of it) - Moved Section 8 on IRDs into Section 4.1 as an example of an IRD because Jordi noted that the definition of an IRD was unclear - Deleted the Appendix describing HTTP/3 outlook because it no longer applies since TIPS should be version independent - Updated the draft with small clarifications/grammar tweaks based on feedback from Qin, Adrian, and Jordi (including small changes to the Figures) - Cleaned up all the idnits validation errors Another draft will soon be uploaded, as Richard Yang is updating it to reflect what was talked about in the meeting earlier today regarding the new representation model for TIPS. Best, Lachlan On Tue, Feb 21, 2023 at 11:54 AM <[email protected]> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This Internet-Draft is a work item of the Application-Layer Traffic > Optimization WG of the IETF. > > Title : ALTO Transport Information Publication Service > Authors : Roland Schott > Y. Richard Yang > Kai Gao > Lauren Delwiche > Lachlan Keller > Filename : draft-ietf-alto-new-transport-06.txt > Pages : 38 > Date : 2023-02-21 > > Abstract: > The ALTO protocol (RFC 7285) leverages HTTP/1.x 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/SSE (RFC 8895) defines a multiplexing protocol on top of > HTTP/1.x, so that the server can incrementally push resource updates > to the client whenever monitored network information resources > change, allowing the client 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 > allows the naming of (i.e., assigning resource identifiers to) > individual incremental updates to multiple ALTO information > resources, and the distribution of those names. It gives an ALTO > client the capability to explicitly request (pull) a specific > incremental update. It also provides an ALTO server the capability > to push a specific incremental update. This document defines TIPS as > a service, with client pull and server push. > > > The IETF datatracker status page for this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-alto-new-transport/ > > There is also an HTML version available at: > https://www.ietf.org/archive/id/draft-ietf-alto-new-transport-06.html > > A diff from the previous version is available at: > https://author-tools.ietf.org/iddiff?url2=draft-ietf-alto-new-transport-06 > > > Internet-Drafts are also available by rsync at rsync.ietf.org: > :internet-drafts > > > _______________________________________________ > alto mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/alto >
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
