FWD: Re: Working Group Last Call for draft-ietf-bfd-unsolicited (ending 16 August, 2020)

Jeffrey Haas <jhaas@pfrc.org> Mon, 17 August 2020 20:29 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3EA3A10B1 for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Aug 2020 13:29:55 -0700 (PDT)
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=ham 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 N9nYE6Q7rEK3 for <rtg-bfd@ietfa.amsl.com>; Mon, 17 Aug 2020 13:29:53 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 64EED3A10A7 for <rtg-bfd@ietf.org>; Mon, 17 Aug 2020 13:29:52 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 344521E2FB; Mon, 17 Aug 2020 16:41:50 -0400 (EDT)
Date: Mon, 17 Aug 2020 16:41:49 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: rtg-bfd@ietf.org
Subject: FWD: Re: Working Group Last Call for draft-ietf-bfd-unsolicited (ending 16 August, 2020)
Message-ID: <20200817204149.GB1696@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/XIPWeeklHEWpxqrpUtI6_bKZcko>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2020 20:29:55 -0000

I requested additional internal review from my colleagues who work on
Juniper's BFD implementation.  Please find his comments attached.

-- Jeff

-------------------------------8<--- cut here --->8--------------------------

Date: Mon, 17 Aug 2020 16:11:05 -0400
From: Raj Chetan Boddireddy <rchetan@juniper.net>
Subject: Re: Working Group Last Call for draft-ietf-bfd-unsolicited (ending 16 August, 2020)

> On Aug 5, 2020, at 7:38 AM, Raj Chetan Boddireddy <rchetan@juniper.net> wrote:
> 
> Hi Jeff,
>  
> Please find comments below:
>  
> >   o  When BFD is used to keep track of the "liveness" of the nexthop of
> >      static routes.  Although only one side may need the BFD
> >      functionality, currently both sides need to be involved in
> >      specific configuration and coordination and in some cases static
> >      routes are created unnecessarily just for BFD.
> (1) Unsolicited BFD may not be desired since we end-up running BFD detection timers on both peers and ideal mechanism for this case would require running detect timers only on the device tracking nexthop of the static route and trigger the necessary repair when this fails. SBFD seems more apt for this case.
> >   When the passive side receives a BFD Control packet from the active
> >   side with 0 as the "remote-discriminator", and it does not find an
> >   existing session with the same source address as in the packet and
> >   "unsolicited BFD" is allowed on the interface by local policy, it
> >   SHOULD then create a matching BFD session toward the active side
> (2) Linklocal and unnumbers address can be spread across multiple interfaces, existing session must be looked with both source-address and interface id to uniquely identify a session IMO.
>  
>  
> >   procedure for bringing up, maintaining and tearing down the BFD
> >   session.  If the BFD session fails to get established within certain
> >   specified time, or if an established BFD session goes down, the
> >   passive side would stop sending BFD Control packets and delete the
> >   BFD session created until the BFD Control packets is initiated by the
> >   active side again.
> (3) We could  infer that a system participating in a passive role may also seize sending BFD Down packets after the session transitions out of Up state. In which case, the benefit of detecting one-way failures sooner will be lost. If we could send only a select few packets to notify the peer of this transition and we may need to wait for a predetermined duration during teardown. New passive BFD session can be spawned only after this teardown duration has expired.
>  
>  
> >   The "Passive role" may change to the "Active role" when a local
> >   client registers for the same BFD session, and from the "Active role
> >   " to the "Passive role " when there is no longer any locally
> >   registered client for the BFD session.
> (4) When IGP protocol unsubscribes to a BFD session (in the presence of unsolicited passive mode config), shouldn’t we handle this as an AdminDown? Having a passive role may prevent this.
>       If the sessions transitions to a passive role, then we may create a scenario where both end-points for the BFD  session take the passive role.
> Ex:
> -R0 (IGP  + Passive BFD) Active-role                     R1 (IGP + Passive BFD)    Active-role
> -R0 (Passive BFD)              Passive-role                   R1 (IGP + Passive BFD)    Active-role
> At this point ideally we need R0 to send AdminDown to R1 which may not be the case if it transitions to Passive role.
>  
> -R0 (Passive BFD)              Passive-role                   R1 (Passive BFD)               Passive-role
> Furthermore both R0 and R1 may assume passive role and the session may lie in this state until it flaps.
>  
>  
> >   o  Limit the feature to specific interfaces, and to a single-hop BFD
> >      with "TTL=255" [RFC5082].  In addition make sure the source
> >      address of an incoming BFD packet belongs to the subnet of the
> >      interface from which the BFD packet is received.
> (5) Restricting this feature only  to interfaces with matching subnet will restrict this feature for unnumbered interfaces and link-local addresses.
>
> Thanks & Regards,
> Raj Chetan
> 
-------------------------------8<--- cut here --->8--------------------------