Hi Alex, (focusing in the identities part of the comment)
> when to use groupings or choices or identities, with the last one in > particular in my experience often being poorly understood despite RFC > 8407 mentioning it but perhaps not clear enough.) I considered your comment when preparing -01 of 8407bis, but I finally made no change because I concluded that the current text is clear enough. As a reminder, RFC8407bis has the following: 4.11.1. Fixed-Value Extensibility If the set of values is fixed and the data type contents are controlled by a single naming authority, then an enumeration data type SHOULD be used. ... If extensibility of enumerated values is required, then the "identityref" data type SHOULD be used instead of an enumeration or other built-in type. And the following for IANA-maintained modules: An IANA-maintained module may use identities (e.g., [RFC8675]) or enumerations (e.g., [RFC9108]). The decision about which type to use is left to the module designers and should be made based upon specifics related to the intended use of the IANA-maintained module. For example, identities are useful if the registry entries are organized hierarchically, possibly including multiple inheritances. It is RECOMMENDED that the reasoning for the design choice is documented in the companion specification that registers an IANA- maintained module. Cheers, Med > -----Message d'origine----- > De : netmod <netmod-boun...@ietf.org> De la part de Alexander Clemm > Envoyé : vendredi 8 septembre 2023 20:28 > À : Italo Busi <Italo.Busi=40huawei....@dmarc.ietf.org>; Carsten > Bormann <c...@tzi.org>; netmod <netmod@ietf.org> > Objet : Re: [netmod] List name: singular or plural? > > I agree. I am actually surprised to not see it in RFC 8407. This is > a very useful "best practice" as a design pattern. (I think there are > other useful patterns worth describing as well, such as concerning > when to use groupings or choices or identities, with the last one in > particular in my experience often being poorly understood despite RFC > 8407 mentioning it but perhaps not clear enough.) > --- Alex ____________________________________________________________________________________________________________ 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 netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
