Hi Italo, all, FYI, I have created an issue to record this one: https://github.com/boucadair/rfc8407bis/issues/4
This will be addressed in the next iteration. Cheers, Med > -----Message d'origine----- > De : netmod <[email protected]> De la part de Italo Busi > Envoyé : mardi 5 septembre 2023 15:47 > À : Carsten Bormann <[email protected]>; netmod <[email protected]> > Objet : Re: [netmod] List name: singular or plural? > > I am wondering whether this convention cannot be documented in > rfc8407bis > > My 2 cents > > Italo > > > -----Original Message----- > > From: Carsten Bormann <[email protected]> > > Sent: martedì 29 agosto 2023 21:27 > > To: netmod <[email protected]> > > Subject: [netmod] List name: singular or plural? > > > > Should list names be singular or plural? > > > > > > Archived-At: > > > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmai > > larchive.ietf.org%2Farch%2Fmsg%2Flast- > &data=05%7C01%7Cmohamed.boucadai > > > r%40orange.com%7C8ab1b02b2060459b209008dbae169832%7C90c7a20af34b40bfbc > > > 48b9253b6f5d20%7C0%7C0%7C638295184290469219%7CUnknown%7CTWFpbGZsb3d8ey > > > JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300 > > > 0%7C%7C%7C&sdata=SvKKMTOcSACbisRp878NmGOKqgarI0%2BfLngMqiEXLAg%3D&rese > > rved=0 > > call/Nh_O8sREv7mBri2_lbIaijorjNE> > > As a convention, in IETF YANG modules, the node name of a list is in > > the singular form. > > Above the list there can be a container with a name in the plural > form. > > > > This seems to be supported by the example in 4.26 in RFC 8407. > > > > > > Archived-At: > > > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmai > > larchive.ietf.org%2Farch%2Fmsg%2Flast- > &data=05%7C01%7Cmohamed.boucadai > > > r%40orange.com%7C8ab1b02b2060459b209008dbae169832%7C90c7a20af34b40bfbc > > > 48b9253b6f5d20%7C0%7C0%7C638295184290625453%7CUnknown%7CTWFpbGZsb3d8ey > > > JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300 > > > 0%7C%7C%7C&sdata=KRCHbRc6YGk8wrEf2PzSy73O3scV4ZC2nAVgpVATXCo%3D&reserv > > ed=0 > > call/ERVfU5u9vwFe5VxOHcRN72EgBHY> > > The usual YANG convention is for a list to be plural and the leaf > > singular. You have the plural list but not the leaf. And who needs > > the container? This is mpls not a common module that might be > > augmented so what does the container give apart from complexity? > > > > (Note that this is contradicting the above.) > > > > > > RFC 9243 has plural for leaf-list interfaces { > > also RFC 9127 list interfaces { > > > > > > All examples in RFC 9254 (YANG-CBOR) have singular list names > > > > > > RFC8040: > > container interfaces { > > description "System interfaces."; > > list interface { > > > > RFC6243: > > container interfaces { > > description "Example interfaces group"; > > list interface { > > description "Example interface entry"; > > > > The singular list name seems to be quite popular with a plural > container name. > > Where there is no such container name, it gets a bit more mixed. > > > > Is there a document that I could consult? > > > > Grüße, Carsten > > > > > > _______________________________________________ > netmod mailing list > [email protected] > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. > ietf.org%2Fmailman%2Flistinfo%2Fnetmod&data=05%7C01%7Cmohamed.boucadai > r%40orange.com%7C8ab1b02b2060459b209008dbae169832%7C90c7a20af34b40bfbc > 48b9253b6f5d20%7C0%7C0%7C638295184290625453%7CUnknown%7CTWFpbGZsb3d8ey > JWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C300 > 0%7C%7C%7C&sdata=RQtuIvzNaCAXPelPoeNBukegj%2F8AEQULnJhpqlYqzno%3D&rese > rved=0 ____________________________________________________________________________________________________________ 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
