IETF Logo Mail Archive

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:31 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 1A63E3A104E; Wed, 10 Nov 2021 06:31:52 -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 b-fxp5h_RvLB; Wed, 10 Nov 2021 06:31:49 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 1B68C3A1049; Wed, 10 Nov 2021 06:31:49 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 5E0C61E2D6; Wed, 10 Nov 2021 09:31:48 -0500 (EST)
Date: Wed, 10 Nov 2021 09:31:48 -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: <20211110143148.GE16907@pfrc.org>
References: <20211110111825.GB16907@pfrc.org> <20211110.131625.788109340841445931.id@4668.se> <20211110140936.GD16907@pfrc.org> <20211110.152419.1470648213167278293.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.152419.1470648213167278293.id@4668.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yang-doctors/zPBPZ1PuCx6pANMqZECC4m_EMLE>
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:31:52 -0000

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'"?

-- Jeff

v2.8.7 | Report a Bug | By Email