Re: [CCAMP] [netmod] What to reference when importing an IANA module?

Hi Randy, 

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : netmod <netmod-bounces@ietf.org> De la part de Randy Presuhn
> Envoyé : vendredi 13 janvier 2023 21:22
> À : ccamp@ietf.org; netmod@ietf.org
> Objet : Re: [netmod] What to reference when importing an IANA
> module?
> 
> Hi -
> 
...
> 
> > Want to take a swing at it?
> 
> Not me.  :-)  There are competing requirements, and the "best"
> answer will very much depend on each situation.  I think the
> *spirit* of the RFC 8407 Section 3.9 is  "point to whatever
> resource will be most enlightening to the developer / user."  But
> the letter of the law is "point to whatever is needed to generate
> a tree of normative reference dependencies" - that is, use what
> will be most helpful to the people writing the standards.  There's
> a point to both kinds of pointers.
> 

[Med] Agree (see my previous answers to Tom). https://datatracker.ietf.org/doc/draft-boucadair-netmod-iana-registries/ currently says: 

   If an IANA-maintained module is imported by another module, a
   normative reference with the IANA URL from where to retrieve the
   IANA-maintained module SHOULD be included.  Although not encouraged,
   referencing the RFC that defines the initial version of the IANA
   module is acceptable in specific cases (e.g., the imported version is
   specifically the initial version, the RFC includes useful description
   about the usage of the module).

Would that be OK with you? Thanks

> When in doubt, my preference is to go whichever way will make it
> harder for implementations to get it wrong.
> 
> Randy
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod

_________________________________________________________________________________________________________________________

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.