Re: [yang-doctors] RFC 9127-bis question - impact of reference clauses in an import statement
Jeffrey Haas <jhaas@pfrc.org> Tue, 14 December 2021 15:38 UTC
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: yang-doctors@ietfa.amsl.com
Delivered-To: yang-doctors@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 670943A0DEA;
Tue, 14 Dec 2021 07:38:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
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 JTZJSZ0EZnIq; Tue, 14 Dec 2021 07:38:06 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108])
by ietfa.amsl.com (Postfix) with ESMTP id 09D3F3A0DE9;
Tue, 14 Dec 2021 07:38:05 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001)
id 3ACFF1E2FA; Tue, 14 Dec 2021 10:38:04 -0500 (EST)
Date: Tue, 14 Dec 2021 10:38:03 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: yang-doctors@ietf.org
Cc: draft-ietf-bfd-rfc9127-bis@ietf.org, ietfa@btconnect.com
Message-ID: <20211214153803.GA15763@pfrc.org>
References: <20211209221207.GC22655@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20211209221207.GC22655@pfrc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/1014KdghPpBfP4Aga9K2FEKX6qE>
Subject: Re: [yang-doctors] RFC 9127-bis question - impact of reference
clauses in an import statement
X-BeenThere: yang-doctors@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email list of the yang-doctors directorate <yang-doctors.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yang-doctors>,
<mailto:yang-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yang-doctors/>
List-Post: <mailto:yang-doctors@ietf.org>
List-Help: <mailto:yang-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang-doctors>,
<mailto:yang-doctors-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Dec 2021 15:38:11 -0000
Dear YANG doctors, A wonderful end of year holiday gift would be to ship the fix to RFC 9127. Please answer the question below. -- Jeff On Thu, Dec 09, 2021 at 05:12:07PM -0500, Jeffrey Haas wrote: > [Reference message to issue in thread: > https://mailarchive.ietf.org/arch/msg/rtg-bfd/Ajo-ku8EJxiEnZjdkRfdzGIg59A/ ] > > YANG doctors, > > The BFD Working Group is trying to move forward on the RFC 9127-bis work > that was previously discussed with you. I believe there is consensus in how > we will move forward on the modification to the common configuration > grouping and its associated feature statement. This strategy was previously > communicated to you all. > > This is a question about what we put in the -bis document. Previously, the > thinking was we did a full re-issue. Tom Petch, in the thread cited above, > notes that we minimally can't do part of this because there are modules > already delegated to IANA. > > The discussion about the what the internet-draft text should include from > RFC 9127 or not lead to a question I had: Would it not be sufficient to > simply issue an update to the ietf-bfd-types module where all of the impact > is isolated? > > Tom's argument is that the form of the import, which contains references to > RFC 9127, suggest we really want a re-issue so we point to the proper new RFC. > > As an example, from module ietf-bfd: > : import ietf-bfd-types { > : prefix bfd-types; > : reference > : "RFC 9127: YANG Data Model for Bidirectional Forwarding > : Detection (BFD)"; > : } > > As best I am able to tell from RFC 7950, § 7.21.4, reference is partially > meant to be informational. If it was normative, an update to any module > imported by another with a reference would require an update. > > Note that this isn't an import by revision. > > My question is thus what are the rules to issue module updates in such > circumstances? > > Tom and the BFD YANG authors are copied to make sure I haven't > misrepresented the situation. > > -- Jeff
- [yang-doctors] RFC 9127-bis question - impact of … Jeffrey Haas
- Re: [yang-doctors] RFC 9127-bis question - impact… Mahesh Jethanandani
- Re: [yang-doctors] RFC 9127-bis question - impact… Jeffrey Haas
- Re: [yang-doctors] RFC 9127-bis question - impact… Martin Björklund
- Re: [yang-doctors] RFC 9127-bis question - impact… Jeffrey Haas
- Re: [yang-doctors] RFC 9127-bis question - impact… t petch
- Re: [yang-doctors] RFC 9127-bis question - impact… Mahesh Jethanandani
- Re: [yang-doctors] RFC 9127-bis question - impact… t petch
- Re: [yang-doctors] RFC 9127-bis question - impact… Jeffrey Haas
- Re: [yang-doctors] RFC 9127-bis question - impact… Martin Björklund
- Re: [yang-doctors] RFC 9127-bis question - impact… Reshad Rahman
- [yang-doctors] RFC 9127-bis question - impact of … t petch
- Re: [yang-doctors] RFC 9127-bis question - impact… Reshad Rahman
- Re: [yang-doctors] RFC 9127-bis question - impact… Jeffrey Haas
- Re: [yang-doctors] RFC 9127-bis question - impact… Jeffrey Haas
- Re: [yang-doctors] RFC 9127-bis question - impact… Acee Lindem (acee)