Re: [Idr] IPR call and WG LC for draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1/2020 to 11/16/2020)

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Tue, 03 November 2020 10:54 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 1B2313A1629 for <idr@ietfa.amsl.com>; Tue, 3 Nov 2020 02:54:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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=MFv4+Egw; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=0YpQVjZp
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 3ucmhsdv8epD for <idr@ietfa.amsl.com>; Tue, 3 Nov 2020 02:54:30 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE1E53A1625 for <idr@ietf.org>; Tue, 3 Nov 2020 02:54:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27576; q=dns/txt; s=iport; t=1604400869; x=1605610469; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=jKCLH1qKRspj0celADhqoW4O83Pi5qbYLyY6QLyds/8=; b=MFv4+Egw6PUy1FjRyVfSX0B1I22kyO03Rq/gjlE0zD2is4+vAkQuR0Tt RMSKuV8rNaD2D7hK6qzwf0RZTU0+fsq7iqcvrvpkw58PQfrpxP1/CPgZK okRPS2kr8m26JlVFgpX0wXTOIrZaBalrJPL4yq1pkU0wNp56GK4ueF232 M=;
IronPort-PHdr: =?us-ascii?q?9a23=3A5WIHKRUrBDz9r0eYRMmlG9ejBMnV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSBNyFufJZgvXbsubrXmlTqZqCsXVXdptKWl?= =?us-ascii?q?dFjMgNhAUvDYaDDlGzN//laSE2XaEgHF9o9n22Kw5ZTcD5YVCBomC78jMTXB?= =?us-ascii?q?74MFk9KuH8AIWHicOx2qi78IHSZAMdgj27bPtyIRy6oB+XuNMRhN5pK706zV?= =?us-ascii?q?3CpX4bdg=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AeAgByNaFf/51dJa1iGwEBAQEBAQE?= =?us-ascii?q?BBQEBARIBAQEDAwEBAYIPgSMvUQdwWS8uhD2DSQONUIEEl3uBQoERA1QLAQE?= =?us-ascii?q?BDQEBJQgCBAEBg0t/AheBcgIlOBMCAwEBCwEBBQEBAQIBBgRxhWEMhXIBAQE?= =?us-ascii?q?BAxIRChMBATgPAgEGAhEDAQEBIQcDAgICMBQJCAEBBAESCBqDBYF+TQMuAQ6?= =?us-ascii?q?TT5BqAoE7iGh2gTKDBAEBBYFHQYMNGIIQAwaBOIJyg3GCRIQTG4FBP4ERQ4I?= =?us-ascii?q?aBy4+gQSBWQEBAgEBgSYBEgEjHg0JgmEzgiyQKoM6hxqMC5APgQwKgm2EEYR?= =?us-ascii?q?5kiGDGIoSkg+CM4dZi3SBfoh6kmSCaAIEAgQFAg4BAQWBayNncHAVO4JpUBc?= =?us-ascii?q?CDY4fDBcUgzqFFIVEdAIBNQIGAQkBAQMJfIsILYIXAQE?=
X-IronPort-AV: E=Sophos;i="5.77,447,1596499200"; d="scan'208,217";a="579166786"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Nov 2020 10:54:28 +0000
Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 0A3AsSoH031409 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 3 Nov 2020 10:54:28 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 3 Nov 2020 04:54:27 -0600
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 3 Nov 2020 05:54:27 -0500
Received: from NAM04-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Tue, 3 Nov 2020 04:54:26 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Wt231/QebD2qLlGv2gyqgp9F068Qz12bta/9hHaF8wBUyLil4AnXyyR0leBTOXMqw069AuOL5knjahij/ghPV9B2rfVHpU8GrijRjI40FUPbNz7oyhlOOqYtHMmAWcCZaAk/tradMgQyCKfyT+urJAaP3sbOT3a9oGmgdpQjtggkxc80MLSvqHZkHFcDG1z/h8srDxizLuM2s8p1BOEd8GmKjabgtk9Crf7cKii671By/rk6B1s917NfgI/iJcnPpqKR/a9ZDij4mVNCw+rIqLKd3WcoVx92ALKcK0FSAoznHwGrMMUOKugl91sR9F/yNR+PpbByGsZURYZz0KxImg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jKCLH1qKRspj0celADhqoW4O83Pi5qbYLyY6QLyds/8=; b=M/2bYGQOkkZhdR8lG4gY2pDbTHGQvZr1HS895Ba4Ib9EEL9NUzZyp6140itTPQhV/Edqru+P01KPGTB9fUIYZPlupVNKZeFBD23SPMRbggS+vKANR5HiMjOJMuY92+B5F80HUHgKW4d6a+fSxJAGx4vz+GOA3rVe91oGMrodd0KY9+l4l+0mIANk3A1oGB7Plvk9j9dYYr3YY+qONxc2ZCAOMFtQ0BsDXD8OFU3e26ZsorXdJ82ZBdCsHECoUgFeOa9oQAe7HiCgbhQsZeGu2FrRpi3bUYoN9FCikANCKx5NF9lCG3phsD+trZFxGEmsUqMquRGMZXp6LDzRFa2sqg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jKCLH1qKRspj0celADhqoW4O83Pi5qbYLyY6QLyds/8=; b=0YpQVjZpM0tZf51r14Yqh0O+rQIszX1RNe/m/FRasvqcY8MU2pdmRdweh0u5pr5WfeAUdAYEYkuyEgLOpGCMx6pZMCWLDqKVEGl4ZVzAoFWuyBDCL3dnFrSTMeiL778gMqB8e2RtJeE3PyXFFZqWchmeQSncrDbo8p6Jw3a2LZ8=
Received: from MW3PR11MB4570.namprd11.prod.outlook.com (2603:10b6:303:5f::22) by MWHPR11MB1662.namprd11.prod.outlook.com (2603:10b6:301:e::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.19; Tue, 3 Nov 2020 10:54:26 +0000
Received: from MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::d4d5:97f0:17b5:2f77]) by MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::d4d5:97f0:17b5:2f77%6]) with mapi id 15.20.3499.032; Tue, 3 Nov 2020 10:54:25 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Tianran Zhou <zhoutianran@huawei.com>, Susan Hares <shares@ndzh.com>, "'Acee Lindem (acee)'" <acee=40cisco.com@dmarc.ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] IPR call and WG LC for draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1/2020 to 11/16/2020)
Thread-Index: AdawxZFiqE7+Vp6ETxeuJxQP7/0gpQAKEOIAABHdwwAAIg9qgAAETbcA
Date: Tue, 3 Nov 2020 10:54:25 +0000
Message-ID: <MW3PR11MB4570CFF58C5CA2BEA092811EC1110@MW3PR11MB4570.namprd11.prod.outlook.com>
References: <045d01d6b0c7$c5eb4900$51c1db00$@ndzh.com> <B27A2389-0994-44FC-B7D1-184C596FFCE6@cisco.com> <07a301d6b135$4cf97c10$e6ec7430$@ndzh.com> <170e41c89c0a4a81b05f9e063bbeb931@huawei.com>
In-Reply-To: <170e41c89c0a4a81b05f9e063bbeb931@huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2001:420:5504:1250:515c:dce7:ff51:3438]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0ed74872-5b91-49c6-f963-08d87fe6d494
x-ms-traffictypediagnostic: MWHPR11MB1662:
x-microsoft-antispam-prvs: <MWHPR11MB16623C3AC6E39261A9927C99C1110@MWHPR11MB1662.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: i4ildgxaJe2ZYfUG46rH+EBvyuhcdqOa62/uYuPb6TdxPm5RVy42lLYL0oL05oOH1KJxOucGp9/OfmP1i6IweIu7KRifCa2Iz5hawIbCTh62LI6DhSWqjDVe4uC43Pydfj19yvTaHDq4Qjp0PQZQDQ1T4fA26Kea37QjC2TvVSYcf2Lxj8E3jiFV02x9do2d21+ykHONYmqUc0qegmx3ACWhXzZhZLyE2hFLrT5nmtSoaZMvJgpQ+uF8mZM3AROQv9yOyCjGxu8nRPbH320au4ci6dqXoQgjYzN1PZZhQojfQqz12O7BLw9jZZ+A7csz6/4Hz7dQCqhD1N7dFBJZ8sHLDO0lYzhGDSu1/gY5phJSVXVWmrLHlQXI2VqgMkRV4H02nIh2Piqi+cG9FxSbaQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW3PR11MB4570.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(366004)(346002)(136003)(376002)(39860400002)(110136005)(76116006)(316002)(33656002)(66556008)(66476007)(52536014)(186003)(66946007)(7696005)(83380400001)(86362001)(5660300002)(66446008)(2906002)(64756008)(9686003)(166002)(478600001)(9326002)(8676002)(55016002)(966005)(8936002)(71200400001)(6506007)(53546011); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: l/IcrI0w2yuAaC34j0cRi1UyNPzrGlEkzQe73cL0vRy2jRb0dAg9nxUsIpY3s2kQlZK33GoZNa0Up+mhGIyutl/eZHb4EiSnC05biHMy77iMCL0OH89lCvYtG2PEHO4Btk/w4+xeOMTkpxUima9b2Nvr8pJeBkPjDYqDOD24udo1lXtnip4p/G+ej3bgTFWLlUnBJR3xxHKCmash71hDcDxGY+P+cAZekW89KaOrK90hrHhUJEkb30An4Tz9qZIosTG2CuzyswqQbpUkteZQWSgXV/3HHZH5w9+N3+D5ZS+Hh+ljwucDh39SwtUOTmRbNdEYlfWFJAVgQyFo3+LPUZ623u6qGIn1ex5EUd+76xJbAVnND2VZVLAaoPWffSfHQFEeXSFolan+Yph+CFw6Qosr1lDuOkehkV2CFsxd5EyxeO72zcuGF9io3nqg9YucF0M96jT7zql5k1uGa0IDn0m5OZY2Ux7aXAC3IJJEmuXhwJ/astCNt7JoauvnQDyv79FuUxu8IyxobWIH07revWIwUl2AFYbhyNFdNN1ZzlVmTpTwYus6/nGD4QvoMGD2ZKZrIB8Hk3nqle7n0Vgwq9kc6ji1J+opuPCoiCbI2mxT5xK32w+yHZ+dCsMF7ip+IwWPbbMYD9Lad1mmSaaaYdHNArKnc/voz/sJ8Rc+k+KOYNWmkuDLLF8zNlUgmj/3FxSYYBwvSgVWhovVWBtBXA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR11MB4570CFF58C5CA2BEA092811EC1110MW3PR11MB4570namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR11MB4570.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0ed74872-5b91-49c6-f963-08d87fe6d494
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Nov 2020 10:54:25.6722 (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-CrossTenant-userprincipalname: 3BgXeGsuj20TCo9CCevYwyp3NIluCKzUciDytygUPWkD9IyitV1s10atGDbW7grDaAPkILuRNKbc6lelwNmGqg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1662
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/CNcjA-nBd7IvUTKgllqdIu0mXEk>
Subject: Re: [Idr] IPR call and WG LC for draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1/2020 to 11/16/2020)
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, 03 Nov 2020 10:54:33 -0000

Hi Tianran,

Please check inline below.

From: Idr <idr-bounces@ietf.org> On Behalf Of Tianran Zhou
Sent: 03 November 2020 14:14
To: Susan Hares <shares@ndzh.com>om>; 'Acee Lindem (acee)' <acee=40cisco.com@dmarc.ietf.org>rg>; idr@ietf.org
Subject: Re: [Idr] IPR call and WG LC for draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1/2020 to 11/16/2020)

Hi Authors,

I have several comments on this draft:

1. In the introduction:
I believe “Segment Identifier (SID) is often used as a shorter reference for "SRv6 Segment". ”  is not correct.

[KT] RFC8402 says “A segment is often referred to by its Segment Identifier (SID).” – I will update to use similar text.

2. In section 3.1:
The O-bit has dependency on I-D.ietf-6man-spring-srv6-oam. IMO, this cannot pass the LC before ietf-6man-spring-srv6-oam.
[KT] FYI - draft-ietf-6man-spring-srv6-oam has completed WGLC in 6man WG and is awaiting shepherd write-up. There is no such dependency.

And is there any other flag?
[KT] No other at this time.

3. There are several use of “A SRv6 SID” in the draft. I think it should be “An SRv6 SID”.
[KT] Ack – will fix.

4. In section 8:
You introduced the SID Structure TLV only with the format. It seems interesting.
I would like to see more text on this. For example, what’s the usage, how to deal with it, what’s the fault process.
[KT] The usage of this BGP-LS extension like the base BGP-LS spec and all other extensions is to provide (rather convey) topology information from the IGP to various applications like PCE or controllers. What and how those applications use the information for is outside the scope of BGP-LS. Also note that BGP-LS does not perform semantic validation of its TLVs. Please check https://tools.ietf.org/html/draft-ietf-idr-rfc7752bis-05#section-7.2.2 for further details.

Thanks,
Ketan

Thanks,
Tianran


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Tuesday, November 3, 2020 12:29 AM
To: 'Acee Lindem (acee)' <acee=40cisco.com@dmarc.ietf.org<mailto:acee=40cisco.com@dmarc.ietf.org>>; idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [Idr] IPR call and WG LC for draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1/2020 to 11/16/2020)

Acee:

Thank you  for noting that the URL is incorrect.   The correct URL is at:

https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-srv6-ext/

Sue


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Acee Lindem (acee)
Sent: Monday, November 2, 2020 7:58 AM
To: Susan Hares; idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [Idr] IPR call and WG LC for draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1/2020 to 11/16/2020)

Hi Sue, IDR WG,
I support publication of the document. Note that the URL below is for the flex-algo BGP-LS draft.
Thanks,
Acee

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Sunday, November 1, 2020 at 10:26 PM
To: IDR List <idr@ietf.org<mailto:idr@ietf.org>>
Subject: [Idr] IPR call and WG LC for draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1/2020 to 11/16/2020)

This begins an IPR call and a 2 week WG LC for
draft-ietf-idr-bgpls-srv6-ext-04.txt (11/1 to 11/16/2020)

You can access the draft at:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-flex-algo/

This draft focus on the BGP-LS support for SRv6.
Spring has proposed the SRv6 support in RFC8402
(see section 3.1.3 for mechanisms and section 8.2 for
Security considerations).

There are two implementations: Cisco and GoBGP
You can see the implementation report at:
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgpls-srv6-ext%20implementations

In your responses, please consider the following questions:
a) Is the SRv6 technology ready for deployment or
are there known issues?

b) Will SRv6 provide valuable support for
deployments of BGP-LS in support of source routing
(aka spring)?

c) Is this draft ready for publication?

If you know of additional implementations, please send
a note to the idr chairs with the information or
respond to this email.

Cheers, Susan Hares