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

Hi Italo, all,

Please see inline.

Cheers,
Med

> -----Message d'origine-----
> De : netmod <netmod-bounces@ietf.org> De la part de Italo Busi
> Envoyé : vendredi 13 janvier 2023 20:16
> À : Benoit Claise <benoit.claise@huawei.com>; tom petch
> <ietfc@btconnect.com>; netmod@ietf.org
> Cc : ccamp@ietf.org
> Objet : Re: [netmod] What to reference when importing an IANA
> module?
> 
> I am having the feeling that the discussion is converging about
> the recommendation to reference the URL instead of the RFC where
> the initial version of the YANG module has been published
> 
> Is my understanding correct?
> 
> I agree it would be good to document such a guideline in an update
> to RFC 8407
> 
> I think it would be better to document this in
> https://datatracker.ietf.org/doc/draft-boucadair-netmod-iana-
> registries/ as proposed earlier by Med
> 

[Med] FWIW, I have already updated the text to cover this. Will tweak that text as appropriate.  

> If we follow this approach, I think it is quite important to also
> recommend in the guidelines that the following text exists in the
> YANG module description:
> 
>        This version of this YANG module is part of RFC XXXX; see
>        the RFC itself for full legal notices.";
> 

[Med] This is already covered in RFC8407; appendix B.

> Those who the module overview, need to know that it is available
> in RFC XXXX and the initial revision statement will go deeper and
> deeper in the module to be easily found
> 
> My 2 cents
> 
> Italo
> 
> > -----Original Message-----
> > From: Benoit Claise <benoit.claise@huawei.com>
> > Sent: venerdì 13 gennaio 2023 17:26
> > To: tom petch <ietfc@btconnect.com>; Italo Busi
> > <Italo.Busi@huawei.com>; netmod@ietf.org
> > Cc: ccamp@ietf.org
> > Subject: Re: [netmod] What to reference when importing an IANA
> module?
> >
> > Hi Tom,
> > > Yes I do think that people outside the IETF may be ignorant of
> the
> > > nuances of the way the IETF works and  may not realise that a
> URL to
> > > the IANA website must be used in preference to an RFC.  There
> is
> > > more to YANG modules than extracting the code from somewhere
> in
> > > order to incorporate it into something.  I have even seen RFC
> > > reference the obsolete list of possibilities  in the RFC that
> set up
> > > an IANA registry
> > If this is the case (And Randy supports this), then we should
> update RFC 8047.
> >
> > Regards, B.
> _______________________________________________
> 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.