Re: [Idr] draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt - IPR Call and WG LC (7/14 to 7/28)

Susan Hares <shares@ndzh.com> Fri, 17 July 2020 13:48 UTC

Return-Path: <shares@ndzh.com>
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 83CDB3A0965 for <idr@ietfa.amsl.com>; Fri, 17 Jul 2020 06:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.216
X-Spam-Level: *
X-Spam-Status: No, score=1.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.267, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no 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 HYEyh0sjWK4U for <idr@ietfa.amsl.com>; Fri, 17 Jul 2020 06:48:13 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5C943A095D for <idr@ietf.org>; Fri, 17 Jul 2020 06:48:12 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=50.107.113.53;
From: Susan Hares <shares@ndzh.com>
To: "'Acee Lindem (acee)'" <acee=40cisco.com@dmarc.ietf.org>, "'idr@ietf. org'" <idr@ietf.org>
References: <01a001d65a15$f6cb25d0$e4617170$@ndzh.com> <93996C2E-B4C2-4E94-8E75-86E33B47791F@cisco.com>
In-Reply-To: <93996C2E-B4C2-4E94-8E75-86E33B47791F@cisco.com>
Date: Fri, 17 Jul 2020 09:48:09 -0400
Message-ID: <008e01d65c40$e8631c00$b9295400$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008F_01D65C1F.61546230"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIS7jUp8UCH/KiQLr4Nzd8vkDcPwwKCX7pRqH6QiyA=
Content-Language: en-us
X-Antivirus: AVG (VPS 200717-2, 07/17/2020), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/P2ECLNbpFEGCiD1niq7NwcpYLRk>
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt - IPR Call and WG LC (7/14 to 7/28)
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: Fri, 17 Jul 2020 13:48:14 -0000

Acee: 

 

Thank you for checking that the BGP-LS encodings align with RFC7883 and RFC7884. 

 

Sue 

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Friday, July 17, 2020 9:00 AM
To: Susan Hares; 'idr@ietf. org'
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt - IPR Call and WG LC (7/14 to 7/28)

 

I did a quick read of the draft and support publication. BGP-LS encodings align with RFC 7883 and RFC 7884. 

Thanks,

Acee

 

From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
Date: Tuesday, July 14, 2020 at 3:36 PM
To: IDR List <idr@ietf.org>
Subject: [Idr] draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt - IPR Call and WG LC (7/14 to 7/28)

 

This begins a 2 week WG LC for draft-ietf-idr-bgp-ls-sbfd-extensions-02.txt 

 

You can find the draft at: 

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-sbfd-extensions/

 

You can find the implementations reports at:

https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-sbfd-extensions%20implementations

 

This is a rather short draft (real text about 5 pages). 

Therefore, we are going to combine WG LC and IPR together. 

 

This draft has only one implementation from Nokia.  

 

In your comments please consider: 

1) Do you feel this draft is ready for publication? 

 

2) Should we wait for 2 implementations or publish 

(as the authors request) with 1 implementations? 

 

3) Are there any other implementations we do not know of? 

(open source or vendor implementations)

 

4) Do you know of any deployments of this technology with 

the Nokia implementation or another implementation? 

Has this feature been useful? 

 

Also, please mention support/no support in your reply. 

 

Cheerily, Sue 

(co-chair and shepherd for draft).