Hi, authors: I have read the latest version of ALTO transport, here is a few clarification questions and comments: 1. What is the relationship between HTTP/2 connection and Transport queue? one to one? Will information resources share the same transport queue? 2. What is the relationship between transport queue and incremental update queue? one to one mapping? 3. Will receivers share the same incremental update queue? or each receiver can join different incremental update queue? For the former case, how does new receiver know or discover the existing incremental update queue? Information resource will provide hints for the receiver or the client?
4. How incremental push update is different from incremental update? 5. In Figure 2 should 'sq/rs' be 'tq/rs'? 6. Individual update is not present in the figure 2? would it be nice to clarify the relation between incremental update and individual update? Is incremental udpate shared by multiple receivers? 7. Should this draft need to update RFC7285 since it introduce new functionalities such as transport queue, incremental update queue, receiver set? 8. Is there any open issues section to track issue tickets? -Qin (without chair hat) 发件人: alto [mailto:[email protected]] 代表 Qin Wu 发送时间: 2022年5月31日 19:11 收件人: [email protected] 主题: [alto] WG adoption call for draft-schott-alto-new-transport-01 Hi folks, This begins a 2 week WG Adoption Call for the following draft: https://datatracker.ietf.org/doc/draft-schott-alto-new-transport/ Please indicate your support or objections by June 15th, 2022. Authors, please respond to the list indicating whether you are aware of any IPR that applies to this draft. Thanks, -Qin/Med
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
