From: netmod <[email protected]> on behalf of 
[email protected] <[email protected]>
Sent: 31 March 2022 06:31

Hi Kent,

There are not thousands of RFCs that include a "Module Review Checklist" :-), 
which is the purpose of this erratum. Thanks.

<tp>

I agree.  There may be lots of RFC in error because RFC8407 gets it wrong but 
if the update to the lots of RFC was wanted then it should have been 
investigated last Autumn when the announcement of the change to the TLP was 
made, an announcement that passed me by despite being on all the right mailing 
lists.

When I comment on an I-D to the effect that the TLP is out of date, then the 
response is that it is almost impossible to get the submission tool to accept 
the correct TLP so authors go on including the out of date version, in order to 
submit  and I go on flagging it at submission and at Last Call.  But that is 
one for some other mailing list, I know not which.

Tom Petch

Cheers,
Med

> -----Message d'origine-----
> De : Kent Watsen <[email protected]>
> Envoyé : jeudi 31 mars 2022 00:24
> À : RFC Errata System <[email protected]>
> Cc : BOUCADAIR Mohamed INNOV/NET <[email protected]>; Andy
> Bierman <[email protected]>; [email protected]; IESG
> <[email protected]>; [email protected]
> Objet : Re: [netmod] [Errata Held for Document Update] RFC8407 (6899)
>
> If this Errata is accepted, does it mean that an Errata will be filed
> for the thousands of RFCs that have been published since 2009 when the
> error was introduce in RFC 5691?
>
> Kent
>
>
> > On Mar 30, 2022, at 5:20 PM, RFC Errata System <rfc-editor@rfc-
> editor.org> wrote:
> >
> > The following errata report has been held for document update for
> > RFC8407, "Guidelines for Authors and Reviewers of Documents Containing
> YANG Data Models".
> >
> > --------------------------------------
> > You may review the report below and at:
> > https://www.rfc-editor.org/errata/eid6899
> >
> > --------------------------------------
> > Status: Held for Document Update
> > Type: Editorial
> >
> > Reported by: Mohamed Boucadair <[email protected]> Date
> > Reported: 2022-03-29 Held by: RFC Editor
> >
> > Section: Appendix A
> >
> > Original Text
> > -------------
> >   o  License -- verify that the document contains the Simplified BSD
> >      License in each YANG module or submodule.  Some guidelines
> related
> >      to this requirement are described in Section 3.1.  Make sure that
> >      the correct year is used in all copyright dates.  Use the
> approved
> >      text from the latest TLP document, which can be found at:
> >
> > Corrected Text
> > --------------
> >   o  License -- verify that the document contains the Revised BSD
> >      License in each YANG module or submodule.  Some guidelines
> related
> >      to this requirement are described in Section 3.1.  Make sure that
> >      the correct year is used in all copyright dates.  Use the
> approved
> >      text from the latest TLP document, which can be found at:
> >
> > Notes
> > -----
> > https://trustee.ietf.org/documents/trust-legal-provisions/tlp-5/ says:
> >
> > ==
> > Note: in prior versions of these provisions, the software license was
> erroneously called the “Simplified BSD License” rather than the “Revised
> BSD License”, and many documents that refer to these provisions copied
> the erroneous name. The IETF Trust corrected the error on September 21,
> 2021. The license text itself was always that of the Revised BSD License
> and has not changed.
> > ==
> > --VERIFIER NOTES--
> > Approved by John Levine (Temporary RFC Series Project Manager and
> member of the IETF Trust).
> >
> > --------------------------------------
> > RFC8407 (draft-ietf-netmod-rfc6087bis-20)
> > --------------------------------------
> > Title               : Guidelines for Authors and Reviewers of
> Documents Containing YANG Data Models
> > Publication Date    : October 2018
> > Author(s)           : A. Bierman
> > Category            : BEST CURRENT PRACTICE
> > Source              : Network Modeling
> > Area                : Operations and Management
> > Stream              : IETF
> >
> > _______________________________________________
> > netmod mailing list
> > [email protected]
> > 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.

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to