IETF Logo Mail Archive

Re: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)

Jeffrey Haas <jhaas@pfrc.org> Tue, 10 September 2019 16:57 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 53A9E12089E for <idr@ietfa.amsl.com>; Tue, 10 Sep 2019 09:57:52 -0700 (PDT)
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=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 zrsOalMKxPMZ for <idr@ietfa.amsl.com>; Tue, 10 Sep 2019 09:57:50 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C640312085E for <idr@ietf.org>; Tue, 10 Sep 2019 09:57:50 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id F22DA1E2F3; Tue, 10 Sep 2019 13:00:30 -0400 (EDT)
Date: Tue, 10 Sep 2019 13:00:30 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Robert Raszuk <robert@raszuk.net>
Cc: "Mercia Zheng (merciaz)" <merciaz@cisco.com>, "idr@ietf.org" <idr@ietf.org>, Susan Hares <shares@ndzh.com>
Message-ID: <20190910170030.GA1662@pfrc.org>
References: <003701d561b8$84171680$8c454380$@ndzh.com> <970E5C9A-7251-458B-8F9F-B452BDF58AE6@cisco.com> <CAOj+MMHEGwZ8YuaVvG0-mdKYb1gWbb6+8rM3Onf3X=CQGsbZQA@mail.gmail.com> <20A92BAE-9B85-4876-B26C-98E1BDDACA03@cisco.com> <CAOj+MMEO-btSTkayAnDOv9rBTmU=yVBP20waNSy-O0oa3gNZPg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAOj+MMEO-btSTkayAnDOv9rBTmU=yVBP20waNSy-O0oa3gNZPg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/_2RdiTvqwJFh0-yCs4VRr2O0zlU>
Subject: Re: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)
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: Tue, 10 Sep 2019 16:57:57 -0000

Robert,

On Mon, Sep 09, 2019 at 11:43:34PM +0200, Robert Raszuk wrote:
> While someone could run iBGP in a p2p mode as DC reachability protocol that
> is rather an exception then a rule.

Directly connected iBGP happens.

> Concluding - I think it would be pretty safe to state that draft applies
> only to point-to-point BGP sessions.

But that said, protecting iBGP when it's not directly connected also
happens.  It has a range of caveats.

IMO, it's unwise to unnecessarily restrict when strict mode gets used.  If
you're choosing to use BFD, you'll need this mechanism for interop.

-- Jeff

v2.23.0 | Report a Bug | By Email