Re: [netmod] [Errata Held for Document Update] RFC8407 (6899)

mohamed.boucadair@orange.com Thu, 31 March 2022 05:31 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27FD53A00B2; Wed, 30 Mar 2022 22:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJXUD-Kseqkj; Wed, 30 Mar 2022 22:31:37 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C75D43A00E5; Wed, 30 Mar 2022 22:31:36 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfedar20.francetelecom.fr (ESMTP service) with ESMTPS id 4KTX3V6csxz8tMP; Thu, 31 Mar 2022 07:31:34 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1648704694; bh=9tAggiwgOt5wauqyXBvRv5Yh5X1HxksOhfw8q+J5WCw=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=SUjI5P1KZlxjVK2GkBsWpx0NSsHRZD8HSsV/dQv6HgfwIYYwtKUzMOatBFJRR10Pv 6MyCmiBRPb3Pl63upMaUj90C4K+gMe6icpQJgsu7oLTQ/ZPkgNNXIfMNZmO4mM00hz fwxmDqLtVuq/9jfLB/bNYFSYXgLeRKbiL7DQPe3uABI9F/d9ZiZ0J6c7Z/JAJg89sI wwcgpdAPvKqtCUHgxpTmkp5V7+xiMjz0PTIqfw6p0w4eRmvCeEXvoRGZCq6z1KMu/6 tDjIpYiAvy6le2g3lyI+7ta9eMPxkMSA/mK20kQ4t23TvbvrPH/ye+o3w1PpvgyLfZ gAypnqbNPGdeQ==
From: mohamed.boucadair@orange.com
To: Kent Watsen <kent@watsen.net>, RFC Errata System <rfc-editor@rfc-editor.org>
CC: Andy Bierman <andy@yumaworks.com>, "rfc-ed@rfc-editor.org" <rfc-ed@rfc-editor.org>, IESG <iesg@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] [Errata Held for Document Update] RFC8407 (6899)
Thread-Index: AQHYRHwAoLXcYhZHlU62ij+A4qLCLKzYXzMAgACXZQA=
Content-Class:
Date: Thu, 31 Mar 2022 05:31:34 +0000
Message-ID: <25000_1648704694_62453CB6_25000_113_1_315eaf0b15d04ffea9a7f1f5a7b07324@orange.com>
References: <20220330212032.B1C784C1D2@rfcpa.amsl.com> <0100017fdcedaf32-a7793fc0-367f-4737-a505-6045ecfc74ed-000000@email.amazonses.com>
In-Reply-To: <0100017fdcedaf32-a7793fc0-367f-4737-a505-6045ecfc74ed-000000@email.amazonses.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-03-31T05:26:41Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=f231affa-2b49-492b-a459-b94c3a799096; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.51]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/2Lz3yJguMLb9mZ-Fi0QI9dDP2vM>
Subject: Re: [netmod] [Errata Held for Document Update] RFC8407 (6899)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2022 05:31:43 -0000

Hi Kent, 

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

Cheers,
Med

> -----Message d'origine-----
> De : Kent Watsen <kent@watsen.net>
> Envoyé : jeudi 31 mars 2022 00:24
> À : RFC Errata System <rfc-editor@rfc-editor.org>
> Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; Andy
> Bierman <andy@yumaworks.com>; rfc-ed@rfc-editor.org; IESG
> <iesg@ietf.org>; netmod@ietf.org
> 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 <mohamed.boucadair@orange.com> 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
> > 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.