Re: [yang-doctors] RFC 9127-bis question - impact of reference clauses in an import statement

Mahesh Jethanandani <mjethanandani@gmail.com> Fri, 10 December 2021 00:28 UTC

Return-Path: <mjethanandani@gmail.com>
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 5325C3A15B3; Thu, 9 Dec 2021 16:28:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HISqz5bFzAYM; Thu, 9 Dec 2021 16:28:47 -0800 (PST)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 D76CE3A15B6; Thu, 9 Dec 2021 16:28:46 -0800 (PST)
Received: by mail-pf1-x436.google.com with SMTP id i12so6956972pfd.6; Thu, 09 Dec 2021 16:28:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=4Bd60jDgKSR0k7kqD9pnMTR82T0hVwls/ZNdTDbgnVg=; b=Iymf+Ip05hY+IbxiR4Ul/TZSTHz7wosZsmJl5+1sbIoBeu3VIb1x5G/NXgG/FuYmwc u7pjzMMkVDUS2Zv0t4xBe5grPlmINFqGmDPJVRAWDjxn3WBtPSCdHEthHOhXgOXFdLCx 6I82Sg3eonvJWCudUTi61oWL/dV93C71GpLugMXw9WY5caRO5mmlA9f2I1+MpEHijyAp 4/u7kXfD8FgPlMVqqULEzu6DAldIrh4Wqc6UTD/1FUQhjRV52BZ0fu/xCnK6XDJUhJYf B616NYkDqwZucsBkhMXbqxCnf/x7pGCMftR+WitxOvAn0Y1tDt0cw65Fr4dVvuiGAnnq WXYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=4Bd60jDgKSR0k7kqD9pnMTR82T0hVwls/ZNdTDbgnVg=; b=pSkjTwvNCYdu1k/vPJY9PqfH35WYFzPSgw7ipmJj/O1hkFEC045G5GuYEh395murAd UysRWzPH5RSJNoXhyeDGujmwNyAkh1EziMKmHinZU8PAoIDOjkaIaGV9O6Z0rrfPZdyD FaAWmN9AsaR43P43WP8caaHykbtInhZVAjjmAGgDc03wnHyUWbEFZ9U08Fo6C5dlk/rl CWkwYyZAUjWvUVV7BZPZqFbj9biMlEIAySGUb+WNPumwDrxktg/wW0rUQwHa0dJ8fMum uCA5ipvg84Mn9ru3GYi2/J2pmu3wfkWtPlxeRZPUb/qrrQgIy6JHkXHWOXMpe1tMjHW+ czjw==
X-Gm-Message-State: AOAM530hCxQCvBNwMi/Mz2MIe7UOxiPCMWJFWD4+hsc8eS4ws7HsNgvg vw5w4ayh7T5rcS9/T3iZjMKyiHXG1mSCQw==
X-Google-Smtp-Source: ABdhPJwDiPNE8U89+jfMarSoGaRxIITfcd7vexRoKmEFsyVqFg+k88EvBtpzncUtMeiqrQWYsdO5ig==
X-Received: by 2002:a63:57:: with SMTP id 84mr35677629pga.136.1639096125147; Thu, 09 Dec 2021 16:28:45 -0800 (PST)
Received: from smtpclient.apple (c-69-181-169-15.hsd1.ca.comcast.net. [69.181.169.15]) by smtp.gmail.com with ESMTPSA id q9sm917966pfj.9.2021.12.09.16.28.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Dec 2021 16:28:44 -0800 (PST)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <F6D7E375-FFAE-451D-819C-3D95131DC3F3@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D12D8894-E20E-4179-AD12-7B7061C66E0C"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 9 Dec 2021 16:28:41 -0800
In-Reply-To: <20211209221207.GC22655@pfrc.org>
Cc: YANG Doctors <yang-doctors@ietf.org>, ietfa@btconnect.com, draft-ietf-bfd-rfc9127-bis@ietf.org
To: Jeffrey Haas <jhaas@pfrc.org>
References: <20211209221207.GC22655@pfrc.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/MQTu6uJX1KiXNudSQvPT0OtilLc>
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: Fri, 10 Dec 2021 00:28:52 -0000

And it it helps, here are the set of diffs w.r.t. RFC 9127 that we are proposing. You might want to ignore the boiler template and the Section name changes, which we will get the RFC editor to fix.



> On Dec 9, 2021, at 2:12 PM, Jeffrey Haas <jhaas@pfrc.org> 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 mailing list
> yang-doctors@ietf.org
> https://www.ietf.org/mailman/listinfo/yang-doctors


Mahesh Jethanandani
mjethanandani@gmail.com