IETF Logo Mail Archive

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]

"Chengli (Cheng Li)" <chengli13@huawei.com> Wed, 18 September 2019 07:20 UTC

Return-Path: <chengli13@huawei.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 3005A120800 for <idr@ietfa.amsl.com>; Wed, 18 Sep 2019 00:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 WmHjPEm9DT_p for <idr@ietfa.amsl.com>; Wed, 18 Sep 2019 00:20:54 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B2F21201CE for <idr@ietf.org>; Wed, 18 Sep 2019 00:20:54 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id C0339D462F9E54CCADDC for <idr@ietf.org>; Wed, 18 Sep 2019 08:20:52 +0100 (IST)
Received: from lhreml718-chm.china.huawei.com (10.201.108.69) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 18 Sep 2019 08:20:52 +0100
Received: from lhreml718-chm.china.huawei.com (10.201.108.69) by lhreml718-chm.china.huawei.com (10.201.108.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 18 Sep 2019 08:20:52 +0100
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml718-chm.china.huawei.com (10.201.108.69) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Wed, 18 Sep 2019 08:20:51 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.58]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0439.000; Wed, 18 Sep 2019 15:20:40 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: 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: AdVtdHc29FIBUpzKSseFCqrVBuGyHAAeqR+g
Date: Wed, 18 Sep 2019 07:20:40 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB026DBF37@dggeml529-mbx.china.huawei.com>
References: <016601d56d75$e3756320$aa602960$@ndzh.com>
In-Reply-To: <016601d56d75$e3756320$aa602960$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.185.75]
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB026DBF37dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/s703_TqKg-1GNAMwKuRM5IPLbJM>
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: Wed, 18 Sep 2019 07:20:57 -0000

Support as a co-author. Path Segment is very useful in SR-MPLS and SRv6 passive PM, Bidirectional Path correlation, etc.
BGP SR Policy is a major mechanism to install SR policy, so I think it is correct to use BGP SR policy to assign path segment since this is part of SR policy.
The reasons to BGP-LS are similar.


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


2)      Is this technology a good way to implement the required

Features in BGP?

Yes



3)      Is this technology ready for adoption?

Yes, the text of  current version is mature and ready for adoption.

Also, we were required to update the IANA part for helping implementation in the previous revision.



4)      Do you have any concerns about adopting this technology?
Yes, we will update the draft to support multiple bidirectional path in ECMP by copying weight TLV to SR Bidir path sub-TLV in the near future.

Many thanks,
Cheng



From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, September 18, 2019 12:35 AM
To: 'idr wg' <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://datatracker.ietf.org/doc/draft-li-idr-sr-policy-path-segment/

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

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.


2)      Is this technology a good way to implement the required

Features in BGP?



3)      Is this technology ready for adoption?



4)      Do you have any concerns about adopting this technology?



Cheers, Susan Hares

v2.23.0 | Report a Bug | By Email