Dear Richard and all,
Please find below the paragraph on item 2. The texts are also uploaded to the
google doc.
Best,
Kai
--------------------------------------------------
Protocol extension of the ALTO protocol over newer versions of HTTP. Existing
extensions such as path vector and incremental updates need additional
mechanisms to work around limitations of HTTP/1.x, leading to additional
development complexities and data transmission. This extension is to define the
data delivery of dependent ALTO objects, which unifies the base protocol, the
path vector (multipart) extension, and the incremental update extension when
they are transported using HTTP/2 and HTTP/3.
2020-11-17 11:01:52"'Richard Yang'" <y...@cs.yale.edu>wrote:
Thanks a lot, Kai!
I saw from the WG mailing list the proposed paragraphs on items 1 and 5. It
will be nice if the leads of 2-4 can post the initial proposals before the
meeting soon...
Richard
On Mon, Nov 16, 2020 at 8:17 AM <kai...@scu.edu.cn> wrote:
Dear all,
We will have the last meeting before the IETF 109 ALTO session at 9:00 am US
EST (3 pm CET, 10 pm Beijing Time).
The purpose is to go over and finalize the recharter items. Given that some
topics were not presented in the last meeting, I suggest we follow the order
below:
1. General extensions
2. New transport
3. Operation automation
4. First hop
5. Multi-domain
Bridge: https://yale.zoom.us/my/yryang
Best,
Kai
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto
--
--
=====================================
| Y. Richard Yang <y...@cs.yale.edu> |
| Professor of Computer Science |
| http://www.cs.yale.edu/~yry/ |
=====================================
_______________________________________________
alto mailing list
alto@ietf.org
https://www.ietf.org/mailman/listinfo/alto
