Re: [alto] Zaheduzzaman Sarker's Discuss on draft-ietf-alto-oam-yang-15: (with DISCUSS)

[Zaheduzzaman Sarker <[e-mail]>]

On Thu, Oct 26, 2023 at 3:58 PM <[e-mail]> wrote:

> Zahed,
>
>
>
> It is a matter of balance between what the WG can successfully deliver vs.
> exhaustiveness. Proceeding in steps (having first a base module + including
> provision to graft extension) is pragmatic given the limited resources of
> the WG.
>

That is understandable, and it this is conscious decision to not cover the
latest and greatest then I would expect the specification describe that. A
statement on the current scope and the potential extendibility to cover the
new ALTO transport will help here. I have seen other YANG documents do that
when they are not covering for example QUIC.


>
>
> Please note that the spec relies upon common reusable http models
> (draft-ietf-netconf-http-client-server) which do not support http/3.
>

Noted, those are still in draft I guess and we can ask question why they
support HTTP/3 while they are working on it. There might be valid reason
for doing it , and important thing is to acknowledge it.

//Zahed


>
>
> Thank you.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Zaheduzzaman Sarker <[e-mail]>
> *Envoyé :* jeudi 26 octobre 2023 15:02
> *À :* BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> *Cc :* The IESG <[e-mail]>; [e-mail];
> [e-mail]; [e-mail]
> *Objet :* Re: Zaheduzzaman Sarker's Discuss on
> draft-ietf-alto-oam-yang-15: (with DISCUSS)
>
>
>
>
>
>
>
> On Thu, Oct 26, 2023 at 1:19 PM <[e-mail]> wrote:
>
> Hi Zahed,
>
> Please see inline.
>
> Cheers,
> Med
>
> > -----Message d'origine-----
> > De : Zaheduzzaman Sarker via Datatracker <[e-mail]>
> > Envoyé : jeudi 26 octobre 2023 13:12
> > À : The IESG <[e-mail]>
> > Cc : [e-mail]; [e-mail];
> > [e-mail]; BOUCADAIR Mohamed INNOV/NET
> > <[e-mail]>; BOUCADAIR Mohamed INNOV/NET
> > <[e-mail]>
> > 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
> <https://data/>
> > 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.
>
> ____________________________________________________________________________________________________________
> 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.
>
>