Hi Benoit, Tom, all,
FWIW, I went with the following changes in
https://author-tools.ietf.org/iddiff?url2=draft-boucadair-netmod-iana-registries-07:
Added this NEW:
Examples of IANA URLs from where to retrieve the latest version of an
IANA-maintained module are: [IANA_BGP-L2_URL], [IANA_PW-Types_URL],
and [IANA_BFD_URL]. [IANA_FOO_URL] is used in the following to refer
to such URLs. These URLs are expected to be sufficiently permanent
and stable.
and updated the IANA considerations that will be included in RFCs as follows:
OLD:
When this registry is modified, the YANG module "iana-foo"
must be updated as defined in RFCXXXX.
NEW:
When this registry is modified, the YANG module "iana-foo"
[IANA_FOO_URL] must be updated as defined in RFCXXXX.
Cheers,
Med
> -----Message d'origine-----
> De : tom petch <ie...@btconnect.com>
> Envoyé : jeudi 19 janvier 2023 13:01
> À : Benoit Claise <benoit.claise=40huawei....@dmarc.ietf.org>;
> BOUCADAIR Mohamed INNOV/NET <mohamed.boucad...@orange.com>; Randy
> Presuhn <randy_pres...@alumni.stanford.edu>; cc...@ietf.org;
> netmod@ietf.org
> Objet : Re: [netmod] What to reference when importing an IANA
> module?
>
> From: netmod <netmod-boun...@ietf.org> on behalf of Benoit Claise
> <benoit.claise=40huawei....@dmarc.ietf.org>
> Sent: 19 January 2023 08:31
>
> Hi Med,
>
> On 1/17/2023 2:46 PM,
> mohamed.boucad...@orange.com<mailto:mohamed.boucad...@orange.com>
> wrote:
> If we want to add an IANA link to update RFC 8407, Section 3.9, a
> couple of remarks:
> - It's not clear what "a normative reference with the IANA URL"
> is.
> Is it https://www.iana.org/assignments/yang-parameters/yang-
> parameters.xhtml?
> Or is it https://www.iana.org/assignments/yang-
> parameters/iana-if-t...@2022-08-24.yang?
> The more precise the later, right?
>
> [Med] None of them. IANA is using dedicated URLs:
> * https://www.iana.org/assignments/iana-bgp-l2-encaps/iana-bgp-l2-
> encaps.xhtml
> * https://www.iana.org/assignments/iana-pseudowire-types/iana-
> pseudowire-types.xhtml
> * https://www.iana.org/assignments/iana-bfd-types/iana-bfd-
> types.xhtml
> That would work.
> We would need
> - to get the guarantee (from IANA) that those URLs are
> permanent
> - to clearly mention that THIS URL type is required for IETF
> YANG modules
>
> <tp>
> No chance. Just as the IETF has reorganised its pages rendering
> URL in most RFC obsolete, so IANA occasionally re-arranges their
> website. Such is life. Hopefully a tombstone would survive to
> direct users where to go.
>
> I note that an IANA-maintained module says that the latest version
> can be obtained from the IANA website but does not give a URL!
>
> Still I think that a URL such as the above which points not to the
> module itself but to the summary page about the module is the best
> we can do for an RFC.
>
> Tom Petch
>
> Regards, Benoit
>
> However, the latter, which is a typical example of IANA
> maintained YANG module does NOT work, as the revision in the URL
> changes with any IAN update
> - So this leads to have both RFC and IANA, so
> https://www.iana.org/assignments/yang-parameters/yang-
> parameters.xhtml + RFC7224 (in the above example)
> - Also, we should make more generic for some other SDOs, as IANA
> is for IETF only.
> And the guidelines are followed by others: BBF, IEEE, etc.
_________________________________________________________________________________________________________________________
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
