Re: [Idr] BGP Auto-Discovery Protocol State Requirements

Jeffrey Haas <jhaas@pfrc.org> Thu, 18 March 2021 16:19 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 D370C3A2ED5 for <idr@ietfa.amsl.com>; Thu, 18 Mar 2021 09:19:56 -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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-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 UUIvLwT3J_75 for <idr@ietfa.amsl.com>; Thu, 18 Mar 2021 09:19:55 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE5C3A2ED4 for <idr@ietf.org>; Thu, 18 Mar 2021 09:19:54 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 9D2AA1E409; Thu, 18 Mar 2021 12:41:23 -0400 (EDT)
Date: Thu, 18 Mar 2021 12:41:23 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: idr@ietf.org
Message-ID: <20210318164123.GE29692@pfrc.org>
References: <20210316210203.GC29692@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210316210203.GC29692@pfrc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ymOfes9yeNPNJdhiKs_6_7sgo3I>
Subject: Re: [Idr] BGP Auto-Discovery Protocol State Requirements
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 18 Mar 2021 16:19:57 -0000

Off-list discussion with Tony Przygienda did suggest the following can use
some clarification:

On Tue, Mar 16, 2021 at 05:02:03PM -0400, Jeffrey Haas wrote:
> 
> GTSM: MANDATORY
> If you're using GTSM for your sessions, TCP may not even establish unless
> it's on.
> 
> Robert points out existing security considerations about using GTSM.
> They apply here as well.
> 
> ---
> 
> BFD Configuration: OPTIONAL?
> 
> Some BGP implementations don't let their sessions come up or stay up if
> there's a mis-match in BFD between the systems.
> 
> See draft-ietf-idr-bgp-bfd-strict-mode.  Making support for this draft
> mandatory would let this state requirement be dropped.

These two are effectively a bit each.

GTSM needs to know if it's running or not.  

BFD needs to know if it's running or not.  BFD itself handles negotiating
sessions.  No parameters need to be exchanged.  BFD session type is derived
from the IP address of the session.

-- Jeff