Re: [yang-doctors] Dealing with BFD RFC 9127 client-cfg-parms for PIM, OSPF, ISIS and other BFD clients on some platforms

Jeffrey Haas <jhaas@pfrc.org> Wed, 10 November 2021 16:19 UTC

Return-Path: <jhaas@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 C010B3A117A; Wed, 10 Nov 2021 08:19:23 -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=unavailable 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 mf9cFrehO1NQ; Wed, 10 Nov 2021 08:19:18 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C56AE3A0C80; Wed, 10 Nov 2021 08:18:45 -0800 (PST)
Received: from smtpclient.apple (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id DBF4E1E2D3; Wed, 10 Nov 2021 11:18:44 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <20211110.162600.500050870278537777.id@4668.se>
Date: Wed, 10 Nov 2021 11:18:44 -0500
Cc: "Rob Wilton (rwilton)" <rwilton=40cisco.com@dmarc.ietf.org>, Ladislav Lhotka <ladislav.lhotka@nic.cz>, "<rtg-ads@ietf.org>" <rtg-ads@ietf.org>, yang-doctors@ietf.org, Reshad Rahman <rrahman@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <956838F8-8499-45A7-B4E0-CEB80CE49668@pfrc.org>
References: <20211110140936.GD16907@pfrc.org> <20211110.152419.1470648213167278293.id@4668.se> <20211110143148.GE16907@pfrc.org> <20211110.162600.500050870278537777.id@4668.se>
To: =?utf-8?Q?Martin_Bj=C3=B6rklund?= <mbj+ietf@4668.se>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/NDgsyiGlUVayUcemjy59qD1yNuA>
Subject: Re: [yang-doctors] Dealing with BFD RFC 9127 client-cfg-parms for PIM, OSPF, ISIS and other BFD clients on some platforms
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: Wed, 10 Nov 2021 16:19:24 -0000

Martin,


> On Nov 10, 2021, at 10:26 AM, Martin Björklund <mbj+ietf@4668.se> wrote:
> 
> Jeffrey Haas <jhaas@pfrc.org> wrote:
>> On Wed, Nov 10, 2021 at 03:24:19PM +0100, Martin Björklund wrote:
>>> I'm not ok with this violation in general, but I am ok with it in this
>>> particular case.  Hence my questions.
>> 
>> Understood.
>> 
>>> If it turns out that in the end
>>> you modify the AUTH48-docs and wait for the bis anyway, then I don't
>>> think this is the right way to go.
>> 
>> So, your preference is "ship AUTH48 docs unchanged, even though it'd have a
>> potentially redundant 'feature bfd'"?
> 
> Of course my preference is to not violate the upgrade rules, if
> possible.
> 
> 1.  publish the auth48-docs now with redundant "bfd" feature
> 2.  publish the auth48-docs now and remove the redundant "bfd" feature
> 3.  remove the redundant "bfd" feature and wait for -bis
> 
> I am not sure I understand what the proposal is at this point (as I
> understood it, your original proposal was (1), but also w/o "bfd" in
> -bis).

Correct.  The critical detail the yang doctors was solicited for was if we can proceed with a quick 9127-bis to deal with the missing if-feature.  Adding that if-feature in the -bis avoids having to maintain the contents of a grouping in multiple documents that were otherwise inheriting it.

> 
> With (2), the published docs won't be very useful until the -bis is
> published, right?

It creates a new dependency, yes.

> 
> In the case of (3), I think it is better to make a proper fix to -bis.
> 
> And in the case of (1), you could as well introduce redundant
> "client-cfg-param" features (as I suggested earlier), and avoid the
> proposed -bis YANG upgrade rule violation.
> 
> Anyway, if you still decide to go with (1) or (2), I am ok with the
> proposed -bis.  (I prefer (2) over (1)).

Thanks for your opinion.  We'll hopefully close this with Rob and the routing-ADs shortly.

-- Jeff

> 
> 
> 
> /martin