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

"Albert Fu (BLOOMBERG/ 120 PARK)" <> Sun, 08 September 2019 20:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EB781120026 for <>; Sun, 8 Sep 2019 13:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id xUFMDgNTEXnz for <>; Sun, 8 Sep 2019 13:40:48 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 00CB1120019 for <>; Sun, 8 Sep 2019 13:40:47 -0700 (PDT)
X-BB-Reception-Complete: 08 Sep 2019 16:40:46 -0400
X-IP-Listener: Outgoing Mail
X-IP-MID: 441221354
Received: from (HELO msllnjpmsgsv06) ([]) by with SMTP; 08 Sep 2019 16:40:46 -0400
X-BLP-INETSVC: version=BLP_APP_S_INETSVC_1.0.1; host=mgnj13:25; conid=74
Date: Sun, 8 Sep 2019 20:40:46 -0000
From: "Albert Fu (BLOOMBERG/ 120 PARK)" <>
Reply-To: "Albert Fu" <>
MIME-Version: 1.0
Message-ID: <5D75674E013B067200390058_0_1809@msllnjpmsgsv06>
X-BLP-GUID: 5D75674E013B0672003900580000
Content-Type: multipart/alternative; boundary="BOUNDARY_5D75674E013B067200390058_0_2667_msllnjpmsgsv06"
Content-ID: <ID_5D75674E013B067200390058_0_1782@msllnjpmsgsv06>
Archived-At: <>
Subject: Re: [Idr] =?utf-8?q?WG_adoption_call_for_draft-merciaz-idr-bgp-bfd-s?= =?utf-8?q?trict-mode-02=2Etxt_=289/2_to_9/17/2019=29?=
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 08 Sep 2019 20:40:50 -0000

I support this draft. We have encountered several extended traffic outages without BFD strict mode, and have pushed and deployed BFD strict mode for a while. This draft will provide inter-op between different vendors. We plan to deploy strict mode as a standard on all our WAN circuits.


Albert Fu

From: At: 09/02/19 14:02:10To:
Subject: [Idr] WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt (9/2 to 9/17/2019)

This begins a 2 week WG adoption call for draft-merciaz-idr-bgp-bfd-strict-mode-02.txt which you can access at:
For those who have indicated support for this draft during the lengthy IPR call, you are welcome to comment again
or to trust that the IDR chairs read your comments during the lengthy IPR call. 
Please indicate if you think this draft is a good start for using the BFD technology 
as a check that prevents BGP connectivity until BFD session is established 
(indicating link connectivity).  
Cheerily, Susan Hares 
Idr mailing list