Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.txt - 2 week WG adoption call
"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 18 April 2019 15:27 UTC
Return-Path: <ketant@cisco.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 162F212038E for <idr@ietfa.amsl.com>; Thu, 18 Apr 2019 08:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=BUlJdE4J; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Asv/r8/+
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 RW6NIj8rUVXv for <idr@ietfa.amsl.com>; Thu, 18 Apr 2019 08:27:21 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF7D312008D for <idr@ietf.org>; Thu, 18 Apr 2019 08:27:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14666; q=dns/txt; s=iport; t=1555601240; x=1556810840; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=5D/s+f1vhbnldQyhdq6ML7RolAaIu4drocQZNL5qhhs=; b=BUlJdE4JW+KcGWWan1kN30QkOhkGPNnMFHi1t1/1Zs4h6Bz/4cAg2Pwt /9JZlQ9k0AvfzJ4krkCYaKAGZ9XX6aO6uc05kiCSwAcFfsL2Vc/hYPhyt LSAOt2JACo5itG55zWf/bcuJ9QsgI0QOVLBS4SioWLRJ8ekFaPbs2Ho7Z 0=;
IronPort-PHdr: 9a23:thFYXhy2XQSOVPnXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YR2N/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuGBFHyKuLCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AYAAAPl7hc/4UNJK1lGwEBAQEDAQEBBwMBAQGBUQYBAQELAYEOLyQsA2hVIAQLKIVtgWgDhFKKQ0qCDZJQhEyBLoF7DgEBIwqDCYE3AoYZIzQJDgEDAQEEAQECAQJtHAyFSgEBAQQdEBMBATgPAgEIDgMEAQEvMh0IAQEEARIIgxuBHUwDHAECDJ4dAooUgiCCeQEBBYFGQYJ5GIINAwaBMgGLSReBQD+BEAFGgkw+gmECAwGBXyQHgw6CJpFrlGEJAoIGhgyMM4ILhiGMW4NiiBaGM4pKgy8CBAIEBQIOAQEFgU84gVZwFYMngWokDBeDTIUUhT9ygSmPSQEB
X-IronPort-AV: E=Sophos;i="5.60,366,1549929600"; d="scan'208,217";a="259988227"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 18 Apr 2019 15:27:19 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by alln-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id x3IFRJh3006932 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 18 Apr 2019 15:27:19 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 18 Apr 2019 10:27:18 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 18 Apr 2019 10:27:17 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 18 Apr 2019 10:27:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aiiyyhCH/+jjH/JI1Bes2YTYsGEvU+uewIAeTAKf8VU=; b=Asv/r8/+oeIioDS3JUigaIt7bl1C1PBhh1JT5VlewxuEijkIClOZTdp/7p0gnGVRbP8FZqqXMwwKUYBz6hw38HTX+9HSkNBPTFzBmzJJ8BbZv+qZA+OYC5Ckx2GnxoCfm2daE+6K9fOdUG+A1bDnSnjdMjpGt9hvKt7spXkDeYc=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB2704.namprd11.prod.outlook.com (52.135.92.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1813.14; Thu, 18 Apr 2019 15:27:16 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::ddd2:508a:e4e8:49b2]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::ddd2:508a:e4e8:49b2%3]) with mapi id 15.20.1792.020; Thu, 18 Apr 2019 15:27:16 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.txt - 2 week WG adoption call
Thread-Index: AdT18PKNf1StrQ3RRRaQiBRQFVL9LwAA0HEQ
Date: Thu, 18 Apr 2019 15:27:16 +0000
Message-ID: <SN6PR11MB2845DF1ABF12D8D8FA4586FCC1260@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <015501d4f5f2$7a72ed70$6f58c850$@ndzh.com>
In-Reply-To: <015501d4f5f2$7a72ed70$6f58c850$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ketant@cisco.com;
x-originating-ip: [2001:420:c0e0:1007::17d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 70fc316f-a319-4a49-88fa-08d6c41256dd
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:SN6PR11MB2704;
x-ms-traffictypediagnostic: SN6PR11MB2704:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <SN6PR11MB2704F4CC512C2155B01B5E3EC1260@SN6PR11MB2704.namprd11.prod.outlook.com>
x-forefront-prvs: 0011612A55
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(39860400002)(346002)(366004)(136003)(199004)(189003)(256004)(5660300002)(6436002)(14444005)(229853002)(46003)(11346002)(446003)(486006)(476003)(110136005)(316002)(8936002)(81156014)(81166006)(99286004)(71200400001)(71190400001)(86362001)(97736004)(52536014)(55016002)(186003)(8676002)(53546011)(76176011)(790700001)(6116002)(54896002)(6306002)(102836004)(7696005)(53936002)(6506007)(478600001)(33656002)(74316002)(68736007)(606006)(9686003)(14454004)(236005)(2501003)(2906002)(966005)(7736002)(25786009)(6246003); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2704; H:SN6PR11MB2845.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 9gHa6nT4hgWYz2exiyIRRi3yognpoYKxVe7Xz7FCzXeHkV3SHPULv1GaIn/PZiIbmxqUsCFISlbyIsZyn1Hzhttrx7rm9D0UhAZJ0rz4ntUu4+vdZP6sFX3KtkFgpDR9d/Iqs354/kV2G33nYCM6ecmU0a51Nn22W0dyQfgH+efB9K57CTnVOc+wSSBKLt/hxfDbE6V961U01HxqulgHJHFzwpqUFhoAzC10XVL38rgza4nJXj4lO08Sg8QG5ABVHAlBKhjmgvoLTC6iscKh9ZHf2oB4+PoIB+zxzL2TJHIjwmV0U2swtPmDHdmcKL9GK0mJ3YjqWecZgDwc4oyxjEzhQ2+4YZnbdh9DZFoqYlZFMVQxcrI/w6HGSVaiNGRpiKY3sC7qTUuEEp5EQkT6h7QyVMqqVJpBl2HOLwT5hvo=
Content-Type: multipart/alternative; boundary="_000_SN6PR11MB2845DF1ABF12D8D8FA4586FCC1260SN6PR11MB2845namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 70fc316f-a319-4a49-88fa-08d6c41256dd
X-MS-Exchange-CrossTenant-originalarrivaltime: 18 Apr 2019 15:27:16.3647 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB2704
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com
X-Outbound-Node: alln-core-11.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lUBJk3dCqoRt7pILsdTvhqBqJQo>
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: Thu, 18 Apr 2019 15:27:23 -0000
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) 1. 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. 1. 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. 1. 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. 1. 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] draft-li-idr-bgp-ls-sbfd-extensions-03.txt … Susan Hares
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Huaimo Chen
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Ketan Talaulikar (ketant)
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Krishna Muddenahally Ananthamurthy (kriswamy)
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Jeff Tantsura
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Zhuangshunwan
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Acee Lindem (acee)
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Ketan Talaulikar (ketant)
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Linda Dunbar
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Dongjie (Jimmy)
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Susan Hares
- Re: [Idr] draft-li-idr-bgp-ls-sbfd-extensions-03.… Ketan Talaulikar (ketant)