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 14:09 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 602803A1003; Wed, 10 Nov 2021 06:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 k31h8MCCw-Jn; Wed, 10 Nov 2021 06:09:37 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id ACFC63A1019; Wed, 10 Nov 2021 06:09:37 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id EB9271E2D6; Wed, 10 Nov 2021 09:09:36 -0500 (EST)
Date: Wed, 10 Nov 2021 09:09:36 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: Martin =?iso-8859-1?Q?Bj=F6rklund?= <mbj+ietf@4668.se>
Cc: rwilton=40cisco.com@dmarc.ietf.org, ladislav.lhotka@nic.cz, rtg-ads@ietf.org, yang-doctors@ietf.org, rrahman@cisco.com
Message-ID: <20211110140936.GD16907@pfrc.org>
References: <5336F4FE-BDF7-4439-B4C3-0D7B81966AC4@pfrc.org> <20211110.091814.587439478003329736.id@4668.se> <20211110111825.GB16907@pfrc.org> <20211110.131625.788109340841445931.id@4668.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20211110.131625.788109340841445931.id@4668.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/9FyaYLb0K9NDMGhPM0u8yNTkwWo>
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 14:09:40 -0000

Martin,

On Wed, Nov 10, 2021 at 01:16:25PM +0100, Martin Björklund wrote:
> > The intent is to fast track the -bis.  The diff is trivial.
> 
> Ok, but if you can fast-track the bis, is it still important to get the
> AUTH48-docs out before the bis?

Our available actions are constrained by the impression that the -bis
violates the IETF YANG module revision rules.  My impression from this email
is you're okay with this violation.

If you similarly agree that simply shipping the -bis in short order with the
changes is the Right Thing, that helps.  The ADs can determine if we have
consensus to proceed with that as the action and we can move forward.

-- Jeff