Hi Italo,

There is currently no explicit (*) guideline for this, but this is a point I 
can add to 
https://datatracker.ietf.org/doc/draft-boucadair-netmod-iana-registries/.

Many RFCs are referencing the RFC that specified the initial version of the 
IANA module: rfc9127, rfc9129, rfc9130, rfc9291, rfc9132, etc.

However, my take on this would be to recommend referencing the IANA as the 
authoritative source but allow for also referencing the RFC that defines the 
initial version of the module.

Cheers,
Med

(*) other than this part from RFC8407:



   The reference MUST

   correspond to the specific module version actually used within the

   specification.


De : netmod <netmod-boun...@ietf.org> De la part de Italo Busi
Envoyé : jeudi 12 janvier 2023 13:21
À : netmod@ietf.org
Cc : cc...@ietf.org
Objet : [netmod] What to reference when importing an IANA module?

Hi all,

Happy New Year

During a WG adoption poll we have received a comment that the URL should be 
added in the reference statement when importing a YANG module maintained by 
IANA and we are not sure how to address this comment

See: https://mailarchive.ietf.org/arch/msg/ccamp/zD6gAfEUlYJ4W3qQlz6Y_gfX5TY/

I have checked RFC8407 but I have not found any guideline on what to reference 
when importing an IANA module

I have checked a couple of examples I knew (RFC8343 and RFC8348) and noted that 
the IANA modules are imported with no reference

I have also noted that within the IANA YANG model registry, the reference for 
the IANA modules is the RFC where the module has been initially defined:

https://www.iana.org/assignments/yang-parameters/yang-parameters.xhtml

What would be your suggestion?

Are there any guidelines I have missed?

Do you know if there are other examples of published RFCs importing an IANA 
module?

Thanks in advance

Italo



_________________________________________________________________________________________________________________________

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

Reply via email to