Hi Kent, all, Thanks for raising this point.
For registries where a name is available, mirroring it in the YANG module would be the right approach. That's would also be consistent with the approach in Section 4.30.3.2. FWIW, here is an attempt to address your comments: https://author-tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/rfc8407bis/draft-ietf-netmod-rfc8407bis.txt&url_2=https://boucadair.github.io/rfc8407bis/boucadair-patch-1/draft-ietf-netmod-rfc8407bis.txt Cheers, Med De : netmod <[email protected]> De la part de Kent Watsen Envoyé : dimanche 4 février 2024 15:53 À : [email protected] Objet : [netmod] rfc8407bis IANA module identifier name Authors, WG, Following is a comment on Section 4.30.3.1. https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc8407bis-06#section-4.30.3.1 The text says: "The name of the "identity" is the lower-case of the name provided in the registry." Yet Section 4.3.1. (Identifier Naming Conventions) says: "Uppercase characters, the period character, and the underscore character MAY be used if the identifier represents a well-known value that uses these characters." In the case of IANA registries, names are not limited to lowercase. Would it not be best for IANA module identifier names to match the name provided in the registry? It seems that they meet the "well-known" criteria, e.g., as strings used in code... For instance, a name from the TLS cipher suites registry: "TLS_KRB5_WITH_RC4_128_MD5" [note that it's both uppercase and also underscore characters. That said, it is not 100% possible, because sometimes the name provided in the registry is an illegal YANG identifier. E.g., the SSH Encryption alg registry contains the name "3des-cbc", which is illegal because it begins with a number. From 7950: identifier = (ALPHA / "_") *(ALPHA / DIGIT / "_" / "-" / ".") My solution for this was/is two-fold: 1) to spell out the number, that is, "3des" --> "triple-des". - could spelling out the number be a recommendation? 2) to have the original name "3des" in the "description field. - could ensuring search ability this way be a recommendation? Thanks, Kent // contributor ____________________________________________________________________________________________________________ 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] https://www.ietf.org/mailman/listinfo/netmod
