Re: [Idr] Adoption Call for draft-zhang-idr-sr-policy-metric-05 (10/20 to 11/6/2023)

Jingrong Xie <xiejingrong@huawei.com> Wed, 25 October 2023 01:39 UTC

Return-Path: <xiejingrong@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 09DCEC14CF18 for <idr@ietfa.amsl.com>; Tue, 24 Oct 2023 18:39:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hMjyJFVQAys for <idr@ietfa.amsl.com>; Tue, 24 Oct 2023 18:39:15 -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 E8F73C14F75F for <idr@ietf.org>; Tue, 24 Oct 2023 18:39:14 -0700 (PDT)
Received: from lhrpeml100004.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4SFWm63XjZz6K986 for <idr@ietf.org>; Wed, 25 Oct 2023 09:38:30 +0800 (CST)
Received: from kwepemi500004.china.huawei.com (7.221.188.17) by lhrpeml100004.china.huawei.com (7.191.162.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Wed, 25 Oct 2023 02:39:10 +0100
Received: from kwepemi500004.china.huawei.com (7.221.188.17) by kwepemi500004.china.huawei.com (7.221.188.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Wed, 25 Oct 2023 09:39:09 +0800
Received: from kwepemi500004.china.huawei.com ([7.221.188.17]) by kwepemi500004.china.huawei.com ([7.221.188.17]) with mapi id 15.01.2507.031; Wed, 25 Oct 2023 09:39:09 +0800
From: Jingrong Xie <xiejingrong@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Adoption Call for draft-zhang-idr-sr-policy-metric-05 (10/20 to 11/6/2023)
Thread-Index: AdoDfK/TNJV9jfBFQHOxPO5fBvrWRgDZVADw
Date: Wed, 25 Oct 2023 01:39:08 +0000
Message-ID: <1591e4bd00a6400596567e8f79e729bc@huawei.com>
References: <BYAPR08MB4872A7276F17700F768D21CBB3DBA@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872A7276F17700F768D21CBB3DBA@BYAPR08MB4872.namprd08.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.81]
Content-Type: multipart/alternative; boundary="_000_1591e4bd00a6400596567e8f79e729bchuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/E0HacOr-F94BZq_O5E73tqTOSiw>
Subject: Re: [Idr] Adoption Call for draft-zhang-idr-sr-policy-metric-05 (10/20 to 11/6/2023)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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, 25 Oct 2023 01:39:19 -0000

Hi WG:

I support the adoption.
I think the Metric added to a Segment List (in addition to the Weight) is very useful for the use of the SR policy technology. My understanding is through the overall procedure in the introduction of the draft:
(The metric of a Segment List is) calculated by path computation element, delivered to the head node of the device by BGP Update Message, and used by the ingress node to select between multiple SR Policy paths.

Thanks,
Jingrong

本邮件及其附件可能含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments may contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Saturday, October 21, 2023 1:49 AM
To: idr@ietf.org
Subject: [Idr] Adoption Call for draft-zhang-idr-sr-policy-metric-05 (10/20 to 11/6/2023)

This begins a 2-week WG adoption call for draft-zhang-idr-sr-policy-metric-05.txt.
https://datatracker.ietf.org/doc/html/draft-zhang-idr-sr-policy-metric-05

The authors of this draft (Ka Zhang, Jie Dong, and Ketan Talaulikar) should respond to this email
And indicate whether they know of any IPR related to this draft.

This draft proposes adding a “metric” field for each segment list for
SR Policy candidate paths in addition to the existing “weight field”
described by the tunnel attribute for the SR Policy tunnel type:

              Tunnel Type: SR Policy
                 Binding SID
                 Preference
                 Priority
                 Policy Name
                 Policy Candidate Path Name
                 Explicit NULL Label Policy (ENLP)
                 Segment List
                     Weight
                     Metric
                     Segment
                     Segment


As you discuss adopting this draft, consider:


  1.  Do the segment lists need both a weight and a metric?
  2.  Does this draft provide clear instructions on how to process a segment list that has both weight and metric?
  3.  Is this feature needed for SR Policy Candidate routes?

Cheerily, Sue