[Idr] Re: New Version Notification for draft-ali-idr-srv6-policy-sid-list-optimization-00.txt

Cheng Li <c.l@huawei.com> Thu, 31 October 2024 16:04 UTC

Return-Path: <c.l@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 9F0C9C1519BA for <idr@ietfa.amsl.com>; Thu, 31 Oct 2024 09:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 DwJQlnZtaD63 for <idr@ietfa.amsl.com>; Thu, 31 Oct 2024 09:04:54 -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 569E3C151980 for <idr@ietf.org>; Thu, 31 Oct 2024 09:04:54 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4XfTKC0N51z6GBjC; Fri, 1 Nov 2024 00:02:23 +0800 (CST)
Received: from frapeml100002.china.huawei.com (unknown [7.182.85.26]) by mail.maildlp.com (Postfix) with ESMTPS id 9655F140A9C; Fri, 1 Nov 2024 00:04:51 +0800 (CST)
Received: from frapeml500003.china.huawei.com (7.182.85.28) by frapeml100002.china.huawei.com (7.182.85.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Thu, 31 Oct 2024 17:04:51 +0100
Received: from frapeml500003.china.huawei.com ([7.182.85.28]) by frapeml500003.china.huawei.com ([7.182.85.28]) with mapi id 15.01.2507.039; Thu, 31 Oct 2024 17:04:51 +0100
From: Cheng Li <c.l@huawei.com>
To: "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: New Version Notification for draft-ali-idr-srv6-policy-sid-list-optimization-00.txt
Thread-Index: AQHbI/jbZiuru0mScUO+qmwzngovILKSJ9uUgA7jjfA=
Date: Thu, 31 Oct 2024 16:04:51 +0000
Message-ID: <be3f8511003e4b84845073f6405a0daf@huawei.com>
References: <172954291837.1991687.6680838807285289351@dt-datatracker-78dc5ccf94-w8wgc> <DM6PR11MB4692F14DFE7483603A7A76EDDE4C2@DM6PR11MB4692.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB4692F14DFE7483603A7A76EDDE4C2@DM6PR11MB4692.namprd11.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.203.70.229]
Content-Type: multipart/alternative; boundary="_000_be3f8511003e4b84845073f6405a0dafhuaweicom_"
MIME-Version: 1.0
Message-ID-Hash: U2ATFL5MI7BNJ7QI3LAV2SOB5CUNWTBY
X-Message-ID-Hash: U2ATFL5MI7BNJ7QI3LAV2SOB5CUNWTBY
X-MailFrom: c.l@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Zafar Ali (zali)" <zali@cisco.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: New Version Notification for draft-ali-idr-srv6-policy-sid-list-optimization-00.txt
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/cudqYPCFdOi8B0SKlsZgNtoxRo8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

Hi Zafar,

I have reviewed the draft, which is short but very useful, and also good as a 00 revision draft.

Some comments here.

1.      We need to add the N-flag in the Segment list level as well. Because whether an endpoint node SID can be excluded depends on the SID of a Segment list, instead of the candidate path or a policy. Sure, if all the Segment lists can meet the requirement of excluding the last node SID, then the flag can be set in the candidate path level. Same logic for the BSID in a SR policy. This also apply to the PCEP extension draft. https://datatracker.ietf.org/doc/html/draft-ali-pce-srv6-policy-sid-list-optimization-00.

2.      In Introduction,

“ The SRv6 policy SID list may end with the policy endpoint's Node SID
   or the penultimate hop adjacency SID.”

I think this logic is correct. We need to consider the END.X SID(pointing to the egress node) as well. Hope to highlight this in the document.
The logic should be: if a segment list points to the egress node, then the redundant node SID or the node C-SID(node ID) of VPN SID should be removed.

Thanks,
Cheng




From: Zafar Ali (zali) <zali=40cisco.com@dmarc.ietf.org>
Sent: Tuesday, October 22, 2024 6:16 AM
To: idr@ietf.org
Cc: Zafar Ali (zali) <zali@cisco.com>
Subject: [Idr] FW: New Version Notification for draft-ali-idr-srv6-policy-sid-list-optimization-00.txt

Hi,

We have posted a draft that addresses use cases in which the SRv6 policy's SID list ends with the policy endpoint's node SID, and the traffic steered (over policy) already ensures that it is taken to the policy endpoint.
Draft: https://datatracker.ietf.org/doc/draft-ali-idr-srv6-policy-sid-list-optimization/
We would like to solicit your feedback on the draft.

Thanks

Regards … Zafar

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Monday, October 21, 2024 at 4:36 PM
To: Rajesh M Venkateswaran <melarco@cisco.com<mailto:melarco@cisco.com>>, Rajesh Venkateswaran <melarco@cisco.com<mailto:melarco@cisco.com>>, Zafar Ali (zali) <zali@cisco.com<mailto:zali@cisco.com>>
Subject: New Version Notification for draft-ali-idr-srv6-policy-sid-list-optimization-00.txt
A new version of Internet-Draft
draft-ali-idr-srv6-policy-sid-list-optimization-00.txt has been successfully
submitted by Zafar Ali and posted to the
IETF repository.

Name:     draft-ali-idr-srv6-policy-sid-list-optimization
Revision: 00
Title:    BGP SRv6 Policy SID List Optimization
Date:     2024-10-21
Group:    Individual Submission
Pages:    5
URL:      https://www.ietf.org/archive/id/draft-ali-idr-srv6-policy-sid-list-optimization-00.txt
Status:   https://datatracker.ietf.org/doc/draft-ali-idr-srv6-policy-sid-list-optimization/
HTMLized: https://datatracker.ietf.org/doc/html/draft-ali-idr-srv6-policy-sid-list-optimization


Abstract:

   In some use cases, an SRv6 policy's SID list ends with the policy
   endpoint's node SID, and the traffic steered (over policy) already
   ensures that it is taken to the policy endpoint.  In such cases, the
   SID list can be optimized by excluding the endpoint Node SID when
   installing the policy.  This draft specifies a BGP extension to
   indicate whether the endpoint's node SID needs to be included or
   excluded when installing the SRv6 Policy.



The IETF Secretariat