RFC 8407:
4. YANG Usage Guidelines
Modules in IETF Standards Track specifications MUST comply with all
syntactic and semantic requirements of YANG 1.1 [RFC7950].
The rule you quoted does not apply since we are talking about an IANA
document.
/js
On Wed, Feb 10, 2021 at 05:25:26PM +0000, Kent Watsen wrote:
>
>
> > On Feb 10, 2021, at 11:46 AM, tom petch <ie...@btconnect.com> wrote:
> >
> > Not quite for me. The current version is that on the IANA website, RFC7317
> > is history at least for IANACH so I think that the YANG reference for the
> > update should be to the IANA website.
> >
>
> Please provide OLD/NEW text.
>
> FWIW, RFC8407 says:
>
> A "revision" statement MUST be present for each published version of
> the module. The "revision" statement MUST have a "reference"
> substatement. It MUST identify the published document that contains
> the module.
>
> So what is the “document”?
>
> revision 2021-MM-DD {
> description
> “Deprecated the 'crypt-hash-md5’ feature per RFC 6151.";
> reference
> "RFC 6151:
> Updated Security Considerations for the MD5
> Message-Digest and the HMAC-MD5 Algorithms";
> }
>
> But note that 6151 was published long before 7317 and, besides, it doesn’t
> “deprecate” MD5.
>
> We can’t reference 8573 because it's NTP-specific. Perhaps iana-crypt-hash
> is fine, and instead ntp-yang-data-model should be republished, augmenting in
> the desired “status” while referencing 8573.
>
> K.
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
--
Juergen Schoenwaelder Jacobs University Bremen gGmbH
Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
