Hi Tom,
(as doc Shepherd)
Please see inline two specific points.
Cheers,
Med
> -----Message d'origine-----
> De : tom petch <daedulus@xxxxxxxxxxxxx>
> Envoyé : lundi 25 septembre 2023 13:58
> À : last-call@xxxxxxxx
> Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@xxxxxxxxxx>; alto-
> chairs@xxxxxxxx; alto@xxxxxxxx; draft-ietf-alto-oam-yang@xxxxxxxx
> Objet : Re: Last Call: <draft-ietf-alto-oam-yang-12.txt> (YANG Data
> Models for the Application-Layer Traffic Optimization (ALTO) Protocol)
> to Proposed Standard
>
>
>
> Some stray thoughts
>
> 'source-type' I do not understand. The module defines it but it is
> not used except as a base in the vendor example.
[Med] This is actually used in example-vendor-alto-data-source:
when 'derived-from-or-self(alto:source-type,'
+ '"yang-datastore")';
Section 5.4.1 includes a pointer to that appendix. I trust the authors will update the text for better clarity.
...
>
> Appendix A
> examples should use the values reserved for documentation use
>
[Med] There is no such a thing for the prefix to be used by an example module. We may discuss the need as part of the ongoing rfc8407bis effort.
draft-ietf-alto-oam-yang already adheres to this part from RFC8407:
Example modules are non-normative and SHOULD be named with the prefix
"example-".
...but I think you are right that some better names can be used to avoid confusion. At least, the authors may consider updating the modules names/prefixes: s/vendor-/example-.
____________________________________________________________________________________________________________
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.
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
