IETF Logo Mail Archive

Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.txt - 2 week WG adoption call

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 19 April 2019 00:40 UTC

Return-Path: <jefftant.ietf@gmail.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 CCD8C120258 for <idr@ietfa.amsl.com>; Thu, 18 Apr 2019 17:40:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 m9_NO3OHfJsC for <idr@ietfa.amsl.com>; Thu, 18 Apr 2019 17:40:12 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 0A3DD120255 for <idr@ietf.org>; Thu, 18 Apr 2019 17:40:12 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id l18so1795093pgj.6 for <idr@ietf.org>; Thu, 18 Apr 2019 17:40:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=ivlWlGfR3V4ok047771KimwaIiJlE9WxaB+HSNZU84M=; b=cXLZ2CIMfKgf7pw1dfZHZNDy81ZG4/Cz4hEWlXIvtix2CX38WKCrb6WGxqSrLciMgP IMJU6ffT2we3Ytu7UsvdDvRxJmv2ikKvrN6U9HaLuxsBrtAQNxiw9UcBlA1M5e+BhfYJ LPbcBm98H1ZrMsLg8MjUY1TMGxBLMdsE33kaSkKn64EhJGEqkYHWe1/f+4M48wrIXJ5U Px9qYLBmrpbOhH7yHAcHdjvdndpXduLToWc+rEZ4eWSjzYMSHt+hauOOrU8gORRuszj7 ZfQK5x/ECvI+neHmGEHNpKIHzx44J7LHLFaHWC9mlaQ3ETOWajP5ev2CofDDpZiesbFy JchQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=ivlWlGfR3V4ok047771KimwaIiJlE9WxaB+HSNZU84M=; b=rq0wf76ZJPaXPjYn6bF9z1EvTCVl4QdwH2f++dO3N5a6fKh/7rplO/BxPcMhJd+25p pDXEnNCSEEvNCaTMWWLSnweTzSZM5+/NSRVH5RIkF37jt/aJny1m9VhIfOGl1L+PeTE1 hhhM3nfYOTYlT1iOrWFjA+QOvoBo8y4YzqPSWyg79UiRKSsb0HmIDDR42NcG+Ni//pp0 h8pYOb3IQpcXvF3Guzk6ykcCWae9yh1CaK6MgcgzyXWUupSMGpr74tIEVhbAmibt4lU9 xPfXOKmfh4w8aLS4T1uQ3PPIso6FIxY+QPTds5fMpB6/rvGo95tkRvwocICGnJpyygAL +2Qg==
X-Gm-Message-State: APjAAAWDhSErNFKG7eq1E+B73URncPqfUc/DnAP0LXlEnDdh27v3JIfc uOp9Nwyg5OhmUseNmQH0cKfV5xRR
X-Google-Smtp-Source: APXvYqxQrKe49RP2oq9wmjkQl0q6whF6C0bGeKnX7B0iTMti3tNBGwPkDJTnLjRX+lsJx/wwHrZOvQ==
X-Received: by 2002:a63:c60d:: with SMTP id w13mr961577pgg.452.1555634411548; Thu, 18 Apr 2019 17:40:11 -0700 (PDT)
Received: from [192.168.1.17] (c-73-189-13-44.hsd1.ca.comcast.net. [73.189.13.44]) by smtp.gmail.com with ESMTPSA id x24sm4355486pfn.128.2019.04.18.17.40.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Apr 2019 17:40:10 -0700 (PDT)
Date: Thu, 18 Apr 2019 17:40:04 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Message-ID: <9af53b3d-51e2-420a-8ea4-229e687c6dd8@Spark>
In-Reply-To: <SN6PR11MB2845DF1ABF12D8D8FA4586FCC1260@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <015501d4f5f2$7a72ed70$6f58c850$@ndzh.com> <SN6PR11MB2845DF1ABF12D8D8FA4586FCC1260@SN6PR11MB2845.namprd11.prod.outlook.com>
X-Readdle-Message-ID: 9af53b3d-51e2-420a-8ea4-229e687c6dd8@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5cb918e9_72e3413a_622"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/N0XmbUAc0abh-ywAj6X9AeHN6Ho>
Subject: Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.txt - 2 week WG adoption call
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, 19 Apr 2019 00:40:15 -0000

support as co-author
+1 Ketan

Cheers,
Jeff
On Apr 18, 2019, 8:27 AM -0700, Ketan Talaulikar (ketant) <ketant@cisco.com>, wrote:
> Support as co-author.
>
>
> 1. Does adding the announcement of seamless S-BFD descriptors via BGP LS address family benefit network provisioning?
>
> This is not really part of network provisioning as much as distribution of the SBFD discriminators that are flooded within IGP area/level to centralized controllers so that they can be leveraged for SBFD verification of paths across multi-domain/AS (under a single admin domain)
>
>
> 2. Is it important to keep the same BGP-ls information in OSPF, IS-IS, and BGP regarding S-BFD discriminators?
>
> I did not quite follow this question.
>
>
> 3. Is this document mature enough for WG Adoption?
>
> Yes. It is simple extension – like many others in BGP-LS for defining new TLV corresponding to IGP specs. The concerned IGP specs are now rfc7884 and rfc7883 – so definitely quite mature.
>
>
> 4. Are there any issues that the WG should consider to help quicken the pace of the adoption?
>
> SBFD is getting wider use due to it’s simplicity and lightweight procedures. This extension in BGP-LS enables controllers to learn SBFD discriminators for running verifications across domains. So faster adoption would help development of those use-cases.
>
>
> 5. Do you know of planned implementations?  If so, should is this document mature enough to receive early allocation for the BGP-LS code points.
>
> Yes. Early allocation would be requested.
>
> Thanks,
> Ketan
>
>
> From: Idr <idr-bounces@ietf.org> On Behalf Of Susan Hares
> Sent: 18 April 2019 19:55
> To: idr@ietf.org
> Subject: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.txt - 2 week WG adoption call
>
> This begins a 2 week WG adoption call for draft-li-idr-bgp-ls-sbfd-extensions-03.txt.  You can access the document at:
>
> https://datatracker.ietf..org/doc/draft-li-idr-bgp-ls-sbfd-extensions/
>
> During your comments, please consider the following:
>
>
> 1. Does adding the announcement of seamless S-BFD descriptors via BGP LS address family benefit network provisioning?
> 2. Is it important to keep the same BGP-ls information in OSPF, IS-IS, and BGP regarding S-BFD discriminators?
> 3. Is this document mature enough for WG Adoption?
> 4. Are there any issues that the WG should consider to help quicken the pace of the adoption?
> 5. Do you know of planned implementations?  If so, should is this document mature enough to receive early allocation for the BGP-LS code points.
>
>
> Remember that raising issues regarding document during WG adoption will help us speed this BGP-LS WG document toward WG LC.
>
> Cheerily, Susan Hares
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email