Re: [Idr] 2 Week WG LC for draft-ietf-idr-segment-routing-te-policy-13.txt

"Wanghaibo (Rainsword)" <rainsword.wang@huawei.com> Sat, 24 July 2021 02:20 UTC

Return-Path: <rainsword.wang@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 0BDAA3A2666; Fri, 23 Jul 2021 19:20:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, 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 Tijf0esS7Xaj; Fri, 23 Jul 2021 19:19:55 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92BB43A2663; Fri, 23 Jul 2021 19:19:55 -0700 (PDT)
Received: from fraeml712-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GWqJT41vdz6D8pD; Sat, 24 Jul 2021 10:04:57 +0800 (CST)
Received: from kwepeml100004.china.huawei.com (7.221.188.19) by fraeml712-chm.china.huawei.com (10.206.15.61) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Sat, 24 Jul 2021 04:19:50 +0200
Received: from kwepeml500001.china.huawei.com (7.221.188.162) by kwepeml100004.china.huawei.com (7.221.188.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Sat, 24 Jul 2021 10:19:48 +0800
Received: from kwepeml500001.china.huawei.com ([7.221.188.162]) by kwepeml500001.china.huawei.com ([7.221.188.162]) with mapi id 15.01.2176.012; Sat, 24 Jul 2021 10:19:48 +0800
From: "Wanghaibo (Rainsword)" <rainsword.wang@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-ietf-idr-segment-routing-te-policy@ietf.org" <draft-ietf-idr-segment-routing-te-policy@ietf.org>
Thread-Topic: [Idr] 2 Week WG LC for draft-ietf-idr-segment-routing-te-policy-13.txt
Thread-Index: AddtCvg2DmulTYiKSCmz2ZRPillyvgTJ01ng
Date: Sat, 24 Jul 2021 02:19:48 +0000
Message-ID: <0a069e9bbe134401957966e0c21dddd3@huawei.com>
References: <010301d76d0b$eec6c1f0$cc5445d0$@ndzh.com>
In-Reply-To: <010301d76d0b$eec6c1f0$cc5445d0$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.153.118]
Content-Type: multipart/alternative; boundary="_000_0a069e9bbe134401957966e0c21dddd3huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/9pq0RwJEbeaLQJO_Slq1yqMRFEo>
Subject: Re: [Idr] 2 Week WG LC for draft-ietf-idr-segment-routing-te-policy-13.txt
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: Sat, 24 Jul 2021 02:20:00 -0000

Hi Sue,

I support the publication of this document.

Best regards,
Haibo

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Wednesday, June 30, 2021 1:27 AM
To: idr@ietf.org
Cc: draft-ietf-idr-segment-routing-te-policy@ietf.org
Subject: [Idr] 2 Week WG LC for draft-ietf-idr-segment-routing-te-policy-13.txt

This begins a 2 week WG LC for the draft-ietf-idr-segment-routing-te-policy-13.txt.
(https://datatracker.ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/)

This draft has an IPR statement (see https://datatracker.ietf.org/ipr/2984/) so the IDR working group members should consider this in their review.

This draft has 3 reported implementations (Cisco IOS-XR, Arista EOS, and Juniper).  You can see the information reported at:
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-segment-routing-te-policy%20implementations%20

The draft describes a new BGP SAFI with a new NLRI for advertising a candidate path of a Segment Routing Policy.

In your comments consider if this draft is:
a) ready for publication,
b) benefits deployments of segment routing,
c) uses the new sub-TLVs for tunnel encapsulation attribute in appropriate ways,
d) adequately describes the new technology.

Thank you, Susan Hares