Hi Adrian, Thank you for the review and comments.
For the point about H3, we hope that at least common H2/H3 functionalities can be covered in this I-D. FWIW, we need to be careful about the versioning and keep in mind this part from RFC9205: == ... Requiring a particular version of HTTP makes it difficult to use in these situations and harms interoperability. Therefore, it is NOT RECOMMENDED that applications using HTTP specify a minimum version of HTTP to be used. However, if an application's deployment benefits from the use of a particular version of HTTP (for example, HTTP/2's multiplexing), this ought be noted. Applications using HTTP MUST NOT specify a maximum version, to preserve the protocol's ability to evolve. == The plan we had for the draft is to request an early artart review seeking specifically advice on the HTTP version matters. Cheers, Med > -----Message d'origine----- > De : Adrian Farrel <[email protected]> > Envoyé : dimanche 12 juin 2022 02:18 > À : [email protected] > Cc : [email protected] > Objet : Re: WG adoption call for draft-schott-alto-new-transport- > 01 > > Hi, > > I've read this draft and it is clearly in scope as it targets one > of the WG's milestones. I think it is a reasonable starting point > for this work and should be adopted. (I presume that a separate > document will address the second half of the milestone, namely > HTTP/3.) > > _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
