Re: [Idr] John Scudder's No Objection on draft-ietf-idr-bfd-subcode-04: (with COMMENT)

Jeffrey Haas <jhaas@pfrc.org> Wed, 04 January 2023 17:18 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7130FC1522C1; Wed, 4 Jan 2023 09:18:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id il-rxZRqKa9B; Wed, 4 Jan 2023 09:18:29 -0800 (PST)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 31BDBC1522B0; Wed, 4 Jan 2023 09:18:28 -0800 (PST)
Received: by slice.pfrc.org (Postfix, from userid 1001) id DF78B1E399; Wed, 4 Jan 2023 12:18:27 -0500 (EST)
Date: Wed, 04 Jan 2023 12:18:27 -0500
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Dale W. Carder" <dwcarder@es.net>
Cc: John Scudder <jgs@juniper.net>, The IESG <iesg@ietf.org>, idr-chairs@ietf.org, keyur@arrcus.com, draft-ietf-idr-bfd-subcode@ietf.org, idr@ietf.org
Message-ID: <20230104171826.GA12724@pfrc.org>
References: <166907008195.64042.570174912390531468@ietfa.amsl.com> <20221227223657.GH2719@pfrc.org> <Y7WrvHPH8Wgd3i97@dwc-desktop.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <Y7WrvHPH8Wgd3i97@dwc-desktop.local>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/9vbNocIS2OimAQfPc229gaE3Q14>
Subject: Re: [Idr] John Scudder's No Objection on draft-ietf-idr-bfd-subcode-04: (with COMMENT)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Jan 2023 17:18:30 -0000

Dale,

On Wed, Jan 04, 2023 at 10:39:24AM -0600, Dale W. Carder wrote:
> In looking at RFC 4486 section 4 which describes usage of 8 other Cease 
> NOTIFICATION subcodes, the majority of those (including administrative
> shutdown) are also SHOULD vs MUST.  It looks like the only MUST for that
> matter is for exceeding prefix limits.
> 
> > Put differently, what language would you want in this document to allow for
> > "choose the best error code given the full knowledge available"?
> 
> When reported up to NMS systems, BFD Down is a leading indicator but to
> me it would be expected that it is correlated with other data by an operator 
> to determine root cause for a session being down.  We see similar issues
> for example when BFD is used with IS-IS. 

BGP gets one thing to put into its NOTIFICATION message.  The BGP
implementation may also lack system-wide knowledge that may be visible in
correlation of other events in the system by a NMS.

The best BGP can do here is "this is the reason I'm choosing to report".

> Dale

-- Jeff