RE: BCP97bis Mon, 18 October 2021 09:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EEFE93A0B06 for <>; Mon, 18 Oct 2021 02:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dg-QNqNg8Xch for <>; Mon, 18 Oct 2021 02:38:56 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 58EA53A0B0C for <>; Mon, 18 Oct 2021 02:38:56 -0700 (PDT)
Received: from (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 (ESMTP service) with ESMTPS id 4HXsJZ3gbnzBtY2; Mon, 18 Oct 2021 11:38:54 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=ORANGE001; t=1634549934; bh=z7wbwYgakvwhglJjug/cF9UrkYiErrKQa4CFnxg7EL0=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=VbPkdyH+4+DhKJTBZCLLPO/svhm2xG2x6Y3DZPKaPRguKtBcyehuelBI+MaH+naXn 128oSG7YatfRDqZuQw9WrNmGTMGrEM44hi3lzpy+UBxYO6lCJyydoAHefPHOmw33CQ WrquQHe7f4MI0OenkfrS9XxKKutjZHVvZaA6uXmTvXifaVBJgDhigCWmdCf5c5qOHN LLR/sVfO9A2gEv3wDeVxX4noA5JFKZJihsR2oGCZhc2knr+8NTHWyYh1iNYwEKUpUo yNeGfThA50XjFgUQunUFUFeDndwD3i4OsIbDiK9EfX87U3kRACjt6d3473gQoSltty PQwAsbtMW2Jkw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (ESMTP service) with ESMTPS id 4HXsJZ2NHgz2xC9; Mon, 18 Oct 2021 11:38:54 +0200 (CEST)
To: "Murray S. Kucherawy" <>
CC: ietf <>
Subject: RE: BCP97bis
Thread-Topic: BCP97bis
Thread-Index: AQHXw9wEYbcJzymQ9E23b0PBRXQisqvYD6OAgABvb5A=
Date: Mon, 18 Oct 2021 09:38:53 +0000
Message-ID: <19971_1634549934_616D40AE_19971_487_16_787AE7BB302AE849A7480A190F8B93303542DAE1@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <> <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2021-10-18T09:34:59Z; 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=60472641-e9f2-4014-b9b0-43f520b7c783; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93303542DAE1OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 18 Oct 2021 09:39:01 -0000

Hi Murray,

Good idea. You may echo this text from Section 3.9 of RFC8407:

   For every import or include statement that appears in a module

   contained in the specification that identifies a module in a separate

   document, a corresponding normative reference to that document MUST

   appear in the Normative References section.


De : ietf <> De la part de Murray S. Kucherawy
Envoyé : lundi 18 octobre 2021 06:56
À : ietf <>
Objet : Re: BCP97bis

On Sun, Oct 17, 2021 at 9:52 PM Murray S. Kucherawy <<>> wrote:
On Fri, Oct 15, 2021 at 10:12 AM Murray S. Kucherawy <<>> wrote:
I've got a draft that seeks to update BCP 97, which is the guidance around how we handle normative downward references.  It's currently made up of three separate RFCs and an erratum, so this will consolidate those into a single document.  The main mission here, though, is to update the guidance around normative references to external documents, especially those behind paywalls.

The draft is being sponsored by Erik Kline and can be found in the datatracker here:

I've captured the feedback from several of you so far into -01 of this document, which is now posted.  Please let me know if I messed anything up.

It occurs to me that the MIB reference is correct but rather stale by now.  Can anyone dream up a replacement comment about something modern like, say, YANG?



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.