On Thu, Oct 26, 2023 at 1:19 PM <[email protected]> wrote:
> Hi Zahed, > > Please see inline. > > Cheers, > Med > > > -----Message d'origine----- > > De : Zaheduzzaman Sarker via Datatracker <[email protected]> > > Envoyé : jeudi 26 octobre 2023 13:12 > > À : The IESG <[email protected]> > > Cc : [email protected]; [email protected]; > > [email protected]; BOUCADAIR Mohamed INNOV/NET > > <[email protected]>; BOUCADAIR Mohamed INNOV/NET > > <[email protected]> > > Objet : Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: > > (with DISCUSS) > > > > Zaheduzzaman Sarker has entered the following ballot position for > > draft-ietf-alto-oam-yang-15: Discuss > > > > When responding, please keep the subject line intact and reply to all > > email addresses included in the To and CC lines. (Feel free to cut > > this introductory paragraph, however.) > > > ... > > > > > > > > ---------------------------------------------------------------------- > > DISCUSS: > > ---------------------------------------------------------------------- > > > > Thanks for working on this specification. > > > > It appears that this specification does not support the > > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdata > > tracker.ietf.org%2Fdoc%2Fdraft-ietf-alto-new- > > transport%2F&data=05%7C01%7Cmohamed.boucadair%40orange.com%7C83b1a7d82 > > bff4d001b0208dbd61454a5%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C6 > > 38339155028873290%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi > > V2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RzITu9tHi > > jJbSCyknPmpM1ZGAoA9aJtLqdno10in0NI%3D&reserved=0, as it only > > defines TCP server grouping but the new transport also compatible with > > HTTP/3 > > which would be running over QUIC. I would like to discuss why is that > > so and if > > there explicit reasoning behind excluding HTTP/3 why is that > > described? It is > > no longer the case that QUIC and HTTP/3 is work in progress. > > > > [Med] The scope of this work is to set the base model that adheres to what > is specified in the base ALTO spec (see Table 2). As discussed in Section > 4.3, the model is designed with the intent to allow future augmentations to > cover extensions and new features such as TIPS. why is it scoped like this when we are also publishing the new transport at the same time? //Zahed > > > > Also supporting Roman's discuss. It is very important that we record > > under what > > circumstances ALTO servers are configured to use HTTP instead of > > HTTPS. > > > > > > [Med] Noted: > https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues/96 > > ____________________________________________________________________________________________________________ > 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
