Hi all, Agree with Mahesh.
Please see more inline. Cheers, Med De : Mahesh Jethanandani <[email protected]> Envoyé : lundi 31 mars 2025 16:24 À : Roman Danyliw <[email protected]> Cc : The IESG <[email protected]>; [email protected]; [email protected]; [email protected]; Lou Berger <[email protected]> Objet : Re: Roman Danyliw's Discuss on draft-ietf-netmod-acl-extensions-15: (with DISCUSS and COMMENT) HI Roman, I will let Med respond to your questions, but here is my understanding of some of your questions. On Mar 31, 2025, at 6:49 AM, Roman Danyliw via Datatracker <[email protected]<mailto:[email protected]>> wrote: Roman Danyliw has entered the following ballot position for draft-ietf-netmod-acl-extensions-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.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-netmod-acl-extensions/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- The XSLT of Appendix A.1, A.2 and A.3 imports “iana-yinx.xsl”: <import href="../../../xslt/iana-yinx.xsl"/> Where does this file come from? The XSLT does not compile without it. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Russ Housley for the GENART review. ** Section 6.3.1 "enum": Replicates the name from the registry with all spaces striped. How should the text in the parentheses be handled (e.g., “Information Request (Deprecated)”)? The text in the parenthesis is the current status of the type, and is not part of the name. As such, in the YANG module, the definition would come out, again taking your example, as: enum InformationRequest { value 15; status deprecated; description "Information Request (Deprecated)"; reference "- RFC 792 - RFC 6918"; } where the name of the enum does not carry what is in the parenthesis. statement “status deprecated” is derived from what is the parenthesis, and the description statement essentially copies the field from the IANA registry. [Med] We don't have usually name with parentheses in the ICMP type. We didn't call this out here as we thought this might be over-specify. Updated for completeness as the point is raised: this new text basically says: legal identifiers are stripped. Please note that we have generic guidance in RFC8407bis as a guard: - If a new registration uses an identifier that does not comply with the naming conventions listed in Section 4.3.1, IANA should check if a guidance to generate legal identifiers was supplied in the RFC that specified the initial version of the module. If no such guidance is available, IANA should check the latest revision of the IANA-maintained module for similar patterns. If failed, IANA should seek advice from relevant registry experts (e.g., designated experts for a registry with Expert Review policy (Section 4.5 of [RFC8126]) or responsible Area Director). Appendix A.2 seems to indicate that the content in the parenthesis should be stripped. Perhaps additional text could be added here that this column is formatted according to the XSLT in Appendix A.1. Stripped from the name, yes. [Med] ACK This feedback applies to Sections 6.3.2 and 6.3.3 too. ** Section 6.3.1 "status": Is included only if a registration has been deprecated or obsoleted. IANA "deprecated" maps to YANG status "deprecated", and IANA "obsolete" maps to YANG status "obsolete". ... IANA is requested to add this note to "ICMP Type Numbers" [IANA-ICMPv4]: ... [IANA-ICMPv4] "ICMP Type Numbers", n.d., <https://www.iana.org/assignments/icmp-parameters/icmp- parameters.xhtml<https://www.iana.org/assignments/icmp-parameters/icmp-%0b parameters.xhtml>>. -- This reference should be normative since it is part of the IANA guidance [Med] Done per the comment from Éric. -- Shouldn’t the link to “ICMP Type Numbers” be https://www.iana.org/assignments/icmp-parameters/icmp-parameters.xhtml#icmp-parameters-types [Med] IANA does not cite child links as far as I know. Will let this as it is. -- How does one know an entry is “obsolete” or “deprecated”? Is it by looking for those strings in the name field? There are a few that are “deprecated” but not “obsolete” The same feedback applies to Section 6.3.2 and 6.3.3? It is derived from what is in the parenthesis. The status can either be ‘deprecated’ or ‘obsolete’ but not both. Thanks. Mahesh Jethanandani [email protected]<mailto:[email protected]> ____________________________________________________________________________________________________________ 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.
_______________________________________________ netmod mailing list -- [email protected] To unsubscribe send an email to [email protected]
