Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]

Linda Dunbar <linda.dunbar@futurewei.com> Fri, 20 September 2019 18:59 UTC

Return-Path: <linda.dunbar@futurewei.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 247F312081A for <idr@ietfa.amsl.com>; Fri, 20 Sep 2019 11:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 aa1Ge1u2_hL5 for <idr@ietfa.amsl.com>; Fri, 20 Sep 2019 11:59:22 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750111.outbound.protection.outlook.com [40.107.75.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E05DC12011F for <idr@ietf.org>; Fri, 20 Sep 2019 11:59:21 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OBbuMuzq4cimTzdck8MOLN8TGCH8i1u16sSboyYJXlcAhdTNkGOBHiMOEo3wPuWkEH+QGPjnohs/WnzMgy9m95w1aXD7HTYmMIR1bGTMtUrcaHTUN6Muni8xv/KRmbZGZJqOrI+FsCNoQ3y37nlpUrcgo6sPJPYS/a1zIEK9sTz0EqS+GwNhfEPImr+TDoMyFlH7tu8CWAYqrcKT1a2bGDXZknboEIDUX73C7uPpeSA/xxJS7m//TIVdzbWWJXKDQskGOZPo5tJGPdizcSlwdt7uldT71IWUriNMWwt8w9kkdQMmKkvwkFci4BLQW//TBAsiiMToYAFLx5nsdUW9Zw==
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=+bEioMTDiBcKDkW65p8pVdkquNoJIH9xhWOcpLmLueU=; b=gbmaPZ7NFqqvV3FqWNJdZYXRTofafjrt8rT4XAdTNTHCn4SPLt8rikYsUzGs4qIW1R4W/eow2N1AWDF/FKN0UH2gDNeXCIhm/tyOZzpimfk6uVdQCchjSWzaUZpNd8eK9Tzlc02v/yY8+BeZc9Q2gftMPFUjgsg9yUmjyRocBuSECssD+gyoQRJSrYofr5KqeeFQ/l5XL2tcMTBL6HbdkJef2n+mJGcV6y5+l2Zecnzp3jmoB6JkNO/OoOfiU2tuxg0/nehX8HTNt76HDStv5AEV2p23fXWwnBoffSIKZebiJ+Lpcfixw/D5yOjLUdI2A3Qc8SMC5+Y9uGBh8O4bjg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+bEioMTDiBcKDkW65p8pVdkquNoJIH9xhWOcpLmLueU=; b=DjsBrtAEs49qWJL3EsriSle6LS4/ioH45BqUOsq2MqFD1LcoBeYYepnPnK4oHQjgfGkszHg6DaEky+BRi1DlnhBM6+9dIJqHNiCa529m6xSvtWG2Z7ZwygIwYeRwSucKgQhEvxpY8x7DpBQv+ATczwtKQTW+e413Fsfslk05vkk=
Received: from MN2PR13MB3582.namprd13.prod.outlook.com (10.255.238.139) by MN2PR13MB3215.namprd13.prod.outlook.com (20.179.151.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.20; Fri, 20 Sep 2019 18:59:18 +0000
Received: from MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::ac5e:7fd0:4547:b154]) by MN2PR13MB3582.namprd13.prod.outlook.com ([fe80::ac5e:7fd0:4547:b154%7]) with mapi id 15.20.2305.000; Fri, 20 Sep 2019 18:59:17 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "Chengli (Cheng Li)" <chengli13@huawei.com>, Susan Hares <shares@ndzh.com>, 'idr wg' <idr@ietf.org>
Thread-Topic: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]
Thread-Index: AdVtdHc29FIBUpzKSseFCqrVBuGyHABfmgPQAAtoJ6AAF6uW0AATzNsw
Date: Fri, 20 Sep 2019 18:59:17 +0000
Message-ID: <MN2PR13MB35825B2594C71C6C7E955D8285880@MN2PR13MB3582.namprd13.prod.outlook.com>
References: <016601d56d75$e3756320$aa602960$@ndzh.com> <5A5B4DE12C0DAC44AF501CD9A2B01A8D934B9674@DGGEMM532-MBX.china.huawei.com> <BY5PR13MB35690EA0294F5AD962446DEE85890@BY5PR13MB3569.namprd13.prod.outlook.com> <C7C2E1C43D652C4E9E49FE7517C236CB026DDFD6@dggeml529-mbx.china.huawei.com>
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB026DDFD6@dggeml529-mbx.china.huawei.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=linda.dunbar@futurewei.com;
x-originating-ip: [206.16.17.231]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: f8f7de00-2b26-4c2c-ae00-08d73dfca359
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR13MB3215;
x-ms-traffictypediagnostic: MN2PR13MB3215:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <MN2PR13MB3215693B298F4389803D6B0D85880@MN2PR13MB3215.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0166B75B74
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(366004)(396003)(346002)(136003)(39850400004)(51914003)(189003)(199004)(11346002)(33656002)(81166006)(81156014)(66066001)(316002)(8676002)(6306002)(54896002)(99286004)(236005)(55016002)(3846002)(6246003)(110136005)(6436002)(229853002)(7736002)(8936002)(606006)(2906002)(6116002)(790700001)(9686003)(66946007)(44832011)(76116006)(256004)(52536014)(446003)(66446008)(74316002)(14454004)(86362001)(14444005)(64756008)(186003)(5660300002)(66476007)(76176011)(486006)(66556008)(26005)(966005)(71200400001)(71190400001)(6506007)(7696005)(478600001)(476003)(53546011)(102836004)(25786009); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB3215; H:MN2PR13MB3582.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: vBah2tPGn0m+GFoPswIq057Q9LcTGycxKxfJpRpjhx1JhjXFu51HwBQZcpXAxTZzoaeCqeTK8oiylhCxlXD58qHRW7Cxc48oKPRzKokoBEYXvpO5eyseftxUNCiI7TEE1dnRut6lSxp2HWaUCSdjiauTio/kjTbhdZOks4pTHZl4ZBxt84w7YZUUQu++5z0zmmh3ZTOEqlplRfGV606jWBHgkkOgwypJB2GfCcljqBf4EXLQVu1gWXFy2gf+ODZCPUf8nfJ/Ywp7MxM6ngG9UUce94uzjqK4lacEgsDQadUxIMQJ6m2BoB3VqOLUbH1E4CJIryU2pPGJsaZhR0gDP7No7BD7+kfh604nN3gCv2fK6JJOKAiqOfqPPF0ia2q/wYtW2y1Cmklp4IW4cWgtalcB6yMRcRGSoN3jxom1vZM=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB35825B2594C71C6C7E955D8285880MN2PR13MB3582namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f8f7de00-2b26-4c2c-ae00-08d73dfca359
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Sep 2019 18:59:17.5812 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: NH1y2d4IxUMWPPWdkPVRZPgIUIwsva+ykg9M6qwWd9TqE98bCjF3ePZmV/GMuPNAnU7/j/KkA/9x9fFt86tGIg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB3215
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Cfwindk6nuCRfdEAdQIX_Z7vmHo>
Subject: Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]
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, 20 Sep 2019 18:59:25 -0000

Cheng,

Thanks for the explanation.

if For data plane, Path Segment is one of the segments in the Segment List, But for Control plane, it is more like a resource or attributes.

Why not have a separate name to represent the "resource or attributes" of the path? Will it be more clear for future, for people who are not in today's IETF discussion?

Linda

From: Chengli (Cheng Li) <chengli13@huawei.com>
Sent: Friday, September 20, 2019 3:16 AM
To: Linda Dunbar <linda.dunbar@futurewei.com>om>; Susan Hares <shares@ndzh.com>om>; 'idr wg' <idr@ietf.org>
Subject: RE: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]

Hi Linda,

Many thanks, please see my reply inline.

Best,
Cheng


From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Linda Dunbar
Sent: Friday, September 20, 2019 3:57 AM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; 'idr wg' <idr@ietf.org<mailto:idr@ietf.org>>
Subject: Re: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]

I have read through both documents. I support WG adoption with the following comments:

Path Segment is one of the segments in the Segment List, correct?
[Cheng] For data plane, yes. But for Control plane, it is more like a resource or attributes.

But draft-li-idr-sr-policy-path-segment-distribution-01 has a statement saying that Path Segment can be a list of SIDs (Section 3 on Page 3). Does it mean that Path Segment can be mapped to multiple SIDs?
"The Path Segment can be used for identifying an SR path(specified by SID list)".
[Cheng] Depends on use cases. If we would like to measure the SR policy, then a Path Segment can map to an SR policy, and it will be shared by the SID lists within the SR policy.

The following statement of draft-li-idr-sr-policy-path-segment-distribution-01 seems to indicate that Path Segment is one of the Path attributes, just like an attribute for the Path QoS attribute, is it correct?
"For each SR path, it may also have its own path attributes, and Path Segment is one of them."
[Cheng] Correct.

draft-li-idr-bgp-ls-sr-policy-path-segment-03 has a statement in the Abstract stating that the document is to define ways for collecting configuration and states of SR policies by BGP-LS. So, it really not SR Policies Extensions (as stated in the title), is it?
[Cheng] I am not sure about what kind of extension belongs to SR policies extension. If I make a mistake, we can modify the title.
                 As my understanding , this extension is for collecting states of SR policies, then it is a SR policy extension.

Linda Dunbar



From: Idr [mailto:idr-bounces@ietf.org<mailto:idr-bounces@ietf..org>] On Behalf Of Susan Hares
Sent: Wednesday, September 18, 2019 12:35 AM
To: 'idr wg' <idr@ietf.org<mailto:idr@ietf.org>>
Subject: [Idr] Adoption: draft-li-idr-bgp-ls-sr-policy-path-segment-03.txt and draft-li-sr-policy-path-segment-01.txt [9/17 to 10/1/2019]

This begins a 2 week WG Adoption call two related drafts [9/17 to 10/1/2019]

  *   draft-li-bgp-ls-sr-policy-path-segment-03.txt and
  *   draft-li-idr-sr-policy-path-segment-01.txt.

You can access these two drafts at the following location:

https://datatracker.ietf.org/doc/draft-li-idr-bgp-ls-sr-policy-path-segment/<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-li-idr-bgp-ls-sr-policy-path-segment%2F&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cfc71199bcad34efa093608d73da2c0d3%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637045641561053885&sdata=3IIFnDFwEMatkK24DfoWTpj1JCQ4k60%2FpOnmqwUAjmo%3D&reserved=0>

https://datatracker.ietf..org/doc/draft-li-idr-sr-policy-path-segment/<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-li-idr-sr-policy-path-segment%2F&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cfc71199bcad34efa093608d73da2c0d3%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637045641561053885&sdata=GScgio9fqeJIVw0VoqcynIUFVe0pyP3v90QMhXRKF9M%3D&reserved=0>

The authors have pointed out that the adoption of this
draft since the following  SR-MPLS Path Segment draft has been adopted:

https://tools.ietf.org/html/draft-ietf-spring-mpls-path-segment-00<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-spring-mpls-path-segment-00&data=02%7C01%7Clinda.dunbar%40futurewei.com%7Cfc71199bcad34efa093608d73da2c0d3%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637045641561063877&sdata=iCZKAyty4%2FNOoN8RJbHBhyg%2BJrKH3cMQWnr%2BQ7N8Yzg%3D&reserved=0>

Please consider the following questions in your responses?


  1.  Should this SR Policy technology be included in BGP for SR-MPLS



Spring has adopted the draft, but IDR can provide feedback

to spring about putting this technology in BGP.


  1.  Is this technology a good way to implement the required

Features in BGP?



  1.  Is this technology ready for adoption?



  1.  Do you have any concerns about adopting this technology?



Cheers, Susan Hares