Re: [Idr] Clarifications on draft-ietf-idr-segment-routing-te-policy

"li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com> Thu, 13 April 2023 13:01 UTC

Return-Path: <li_zhenqiang@hotmail.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 C99A9C1522C6; Thu, 13 Apr 2023 06:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.214
X-Spam-Level:
X-Spam-Status: No, score=-1.214 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
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 kR1yFb3EL-OX; Thu, 13 Apr 2023 06:01:49 -0700 (PDT)
Received: from AUS01-ME3-obe.outbound.protection.outlook.com (mail-me3aus01olkn20801.outbound.protection.outlook.com [IPv6:2a01:111:f403:7004::801]) (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 B79E6C1516F8; Thu, 13 Apr 2023 06:01:48 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jGampKse10bC3QzhuksVKd9GiDYj3CkBxWwK/zp/o35VN3Ud9wyyOZrfTQTe5exTIlTQWeMWw768rmknnAqEpoJgjve+BjgXyY4K808qqvK9glrVda5sDmy9s8DAgdKo36wGdJI0VG7Rhy7a4f45vsN+l5I0J7h4Y+hQ2ae4iJKBw9Mt03ZmZeTiOMCXmO9j4hhFl/iWqXZzXxtztRZrx73zdlPlErz9QyyBiwG5uLMgEsOa0rWkTMQ1xYam8ut4QwMcSZayccXL6DN+UvygPVBJM88G3BQtSFstolle27OYoCoO1pm/nJ0OfqrESN2M+idXG2yhb+HXEns4Cjsr9A==
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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=RAkUDbj1DZ1kfn/IkykC3Kz/7zr8Sifp/a28nyHP7aU=; b=h/K68GehTQKPkSa5TdnYVVpFFipF3dFnYYPPQQW3SYLXHgYeaXc+llQZj7psqR5C9uWzLvSIro2RxIwVNi/htw1N55uDwlzHetvBB1se/T6j04zQX868e6llcRfk5lANrWpEUs7+SAMRq9i8vIQ5tvX7B0wiGUuWBd1U6gkRtbsDI0Boe1UBDwlkSMmRW+ZSNA1WgpRYO2pl1NqedGosLhBmwesQ5zwv3wEUEiRVyViXWnZFpH7dxkKkRfG9rAuZNWTKLVkHgy4v6HlQ/yDHnpMDIxHkVhWJSzittSsRq55aNT/WQweqnSMTX4606RfzG5U8RQeAXPtFO8o+ut0bYg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RAkUDbj1DZ1kfn/IkykC3Kz/7zr8Sifp/a28nyHP7aU=; b=R+8CHu2GreCHUvLRkG/mVhcQTrzZfXCvdtJh4iyfsWKZgkhnyhJhtMILkYTgPeaeMobpp+cs0j1NRl8X3oC3VhX49jq55L47ByNJpyIrlKeAUxIfOusfuYEvKsjOBlnSR8x2fhL9ZESOd5kfxhewpZumfgHVaWbSoaJMP38nH7oouaAx1z81cRBcKmiAwWAGOsoTp3GLtDLtPrX20wum1bzzoSyBjGsPfG3UwKtopkJtRDsjkp/eUdD/3s68gJz1dWOQl37edA7BrMOD8nvZfrM739f4g5IXJK8H2dUIYRDJiMoTugug6y9Ht73g5FVU9lkkuULR6/HbgYQt8+jfuA==
Received: from ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM (2603:10c6:220:139::7) by ME3P282MB4016.AUSP282.PROD.OUTLOOK.COM (2603:10c6:220:1b0::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6319.4; Thu, 13 Apr 2023 13:01:42 +0000
Received: from ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM ([fe80::d56b:f98a:25ae:1e88]) by ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM ([fe80::d56b:f98a:25ae:1e88%5]) with mapi id 15.20.6319.004; Thu, 13 Apr 2023 13:01:42 +0000
Date: Thu, 13 Apr 2023 21:01:49 +0800
From: "li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com>
To: Ketan Talaulikar <ketant.ietf@gmail.com>
Cc: authors <draft-ietf-idr-segment-routing-te-policy.authors@ietf.org>, "idr@ietf.org" <idr@ietf.org>, idr-ads <idr-ads@ietf.org>, idr-chairs <idr-chairs@ietf.org>
References: <BYAPR08MB4872737894DA7507D4F54C2BB3AD9@BYAPR08MB4872.namprd08.prod.outlook.com>, <CAB75xn70k8xE3QaNKqHkHn=22gD0NEG65o1uooB6puNx4xWB6A@mail.gmail.com>, <43a2fb5f9f3747ea9c31423d19e332d1@huawei.com>, <CAB75xn4Dk7Ge9VAbB9eQ9Pqh+1mzJH0_29OqX-PB40t1sD9H7Q@mail.gmail.com>, <ME3P282MB29401E421BAE4C236C86DC18FC919@ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM>, <CAH6gdPytvU2w9Fp6DjsnaXBDk9cVvONkptUVQdvusdv7=Mv5Zg@mail.gmail.com>, <MEYP282MB2942D2A3F89D210C01C9107CFC979@MEYP282MB2942.AUSP282.PROD.OUTLOOK.COM>, <CAH6gdPw2HeWfif8w=d_kqGJio+hPwznnf1k3ju8a+F1nyiQREQ@mail.gmail.com>
X-Has-Attach: no
X-Mailer: Foxmail 7.2.9.156[cn]
Message-ID: <ME3P282MB29400D98FC86BECE9A5B3D3AFC989@ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM>
Content-Type: multipart/alternative; boundary="----=_001_NextPart501553546644_=----"
X-TMN: [ZiZX3rlxaBcjOQ5KkGhi9Gdqblj+WpIp]
X-ClientProxiedBy: SGAP274CA0021.SGPP274.PROD.OUTLOOK.COM (2603:1096:4:b6::33) To ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM (2603:10c6:220:139::7)
X-Microsoft-Original-Message-ID: <2023041321014504440111@hotmail.com>
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: ME3P282MB2940:EE_|ME3P282MB4016:EE_
X-MS-Office365-Filtering-Correlation-Id: 9c850668-00fa-4a59-1ef6-08db3c1f39dc
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: IfCFbzg0vlu6P6/nwSVVLJls1y72PWDMM7fMTvzPhb8GBeQHKu9Y4ZMKD/CG6nVxSxbnjJmKBIQWMWgHl6JbSWE03Xsl4vOCIt39X1f31thcQdd16HySaxigZrMFLs16MsFgyVv0iFGqTkjhoEyR8I0BXg/x8bJbkUWBPqMbAF0Pcvel331sObxk6NisZ0ZOLaw/DoJqmejXkdb7MnyUwATMPYud0GDUDPwuFLQZB8vrlEfWnUoYzwuUwu/wjPyrYeVnibeTvgxfRGv8HRExrMjlMiqQXm9D8X1xSZGadUxQWaTrQAj5B9zuVvnkd/libpxYm7R20PKHBlSnTJDqbmhjHZW+bnI3IooVi915EljHfQAeATqz/kEFRt1+tnO+kRbM5aujJT2NNWlGFQsuWMuPVk46gwQbPuH4FqxlvNap0BnTJjI+gNpY8F5DFgOwuZdwcAmIhuCDJe1qgdH6s6YuTQnU535KHRGcmifXqjYfH3lq/wybchQrBBRE9cEdZZij4FjgOFoA8cHbFkz8MFCU8oEH3DzVe8PmU1uURk9p5tDt0HJjJn3p/5LPIuXRUFmn/zyw51cqP14o5gWQff8zdrIzQD1RY3P6Pyxk2BKhPE77AbAqT27GFmR/QENs
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: xPBYbcokQcqJhMOJnLDLF56Eujs7hIQ6LkXAT1JiEPlHMZ3KL2e4SWnUtFQY6DUwe+PbpOUqdoFlLxE9YzvIPm1PPpEBUqkw/55FZHVx0SKt8Qh/GiHmqJ3kUmObiE9IogkvrdaRi0FfhuSdeJuoottH3FcSmYV5cd1rrlynHahAVdXjPLRuaT2qRRPdiKgeHap0HWvFRsBhK9vxddAJ2pyzZFgullB67pCj9wvFo9mbQZIBnHW5pjVbMLvI6Yw0xp9n2UnTsSe5a0O0sSw+sqOBcYCmFObCcFU6oxqfwkW6xoqne6EHHTgb+IrqENQXQDhuqEWgTJdjCjh5lJI+ftLmKT0254ps4kSctHXtkaZZB0m4t1MqbSMh0HYZdI402XXpzY2KiAzvNodrdA3tijWnAnUp46kll1lFZpgjR2WGIntkxlruF2HVsXLOoY9ZT810UAkjvZiLyd902zBKuxBTvQcT4fIwjwjqYlI+8QbCmU5w6LSM4+/Tbm0Pt0NjX1NYu9HxY+dbyojN/cEFrGBhASHTaVXr7jXD6tPwDXlQoDu5aRXl724ENYM0lVHAh+Z1YK5r9JJBcgQmYqE8MxFSlnGSJDEJZk4Z11mvXt0PUv1zIpYQPHDA6/P2jZB9CB7zwHI4qREv+ODNw1wbLc2nLNYtJNuufsfyaqT4l67DNPDi63/flRzfUYA/VqCVMeKx33YiWr6KTOQb8iZJCbHpXSVweNAkNAZ6P0eD+/dODN3GvlorP8dliAZnxyl4FA8x3kePgLfIT3RtX2X3IRWSSbFAI2MjZuElFCxMZq8MRqIfhYHsYuy1hN1XoPNgCDGBbX0fCkaIgV2sKAAMSwjUgcghXcmYt2nbmikpzVkmedErpS7q20+dNf/utq9W/9VT5D3RzpiNq4vAjILe3Qcg4PUPst7MUBxtM59Ubwqzp9fOPi/Vw+LkqtpJh+5FK4C4YAdx3ovgy2KmYEVI5ez3ILI/7+kUAUBMj3ye4ua+clvZ3hYy6j5G3HVeYdFScNAadlMV4suBWGt7bo/ZqNbC4OWMWBoxu1DicSMn35FKtXV4VPwKYbSXpfuY27WJorDumZD4WVcB/6zQWNHO/gBIo5IBRHyFjvyaSUkP2S00YqZWt45CL8N/A2hwzBy3JZyUac7eYlCQE7aa9MKNbYfBM4LmnK9LnGdS6nROO0F33m+vv1KtHKgiM1dir9sPkCIW4gK0pc8TYOfhjflY0gydKnIYBNwK69nGZMYfBR4=
X-OriginatorOrg: sct-15-20-4755-11-msonline-outlook-746f3.templateTenant
X-MS-Exchange-CrossTenant-Network-Message-Id: 9c850668-00fa-4a59-1ef6-08db3c1f39dc
X-MS-Exchange-CrossTenant-AuthSource: ME3P282MB2940.AUSP282.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 13 Apr 2023 13:01:42.3821 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-Transport-CrossTenantHeadersStamped: ME3P282MB4016
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7ZPmIgT5tmS5Rasb56O-h1Pz8DU>
Subject: Re: [Idr] Clarifications on draft-ietf-idr-segment-routing-te-policy
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: Thu, 13 Apr 2023 13:01:49 -0000

Dear Ketan,

Understood. Is it proper to explicitly add some text in the doc like "RR Implementation is RECOMMENDED to provide a policy knob to only reflect related policies to relevant peers according to the route target attached to the policies" ?

I believe this feature is important for large scale deployment of SR policy.

Thank you very much for your consideration.


Best Regards,
Zhenqiang Li

li_zhenqiang@hotmail.com
 
From: Ketan Talaulikar
Date: 2023-04-12 22:55
To: li_zhenqiang@hotmail.com
CC: authors; idr@ietf.org; idr-ads; idr-chairs
Subject: Re: Re: Clarifications on draft-ietf-idr-segment-routing-te-policy
Hi Zhenqiang Li,

The deployment design that you describe can achieve the optimization that you desire by using outbound route policy on the RR to each of its neighbors. The spec does not prevent an implementation from providing a policy knob to achieve the behavior you desire.

Also, consider a deployment design with hierarchical RRs. Would your proposed change not break BGP propagation?

Personally, I do not think we should change the base BGP propagation mechanism for such scenarios. BGP is basically a p2mp distribution protocol and we need to be careful how far we bend it for other purposes.

Thanks,
Ketan


On Sat, Apr 8, 2023 at 6:51 AM li_zhenqiang@hotmail.com <li_zhenqiang@hotmail.com> wrote:
Hello Ketan,

I understand the objective and the current text do satisfy the objective. What I point out is the issue the objective has and the current text should be refined.

suppose a  RR has 100 peers, and 10 SR policies are to be configured on each peer. Follow the current text, RR will reflect 1000 SR policies to each peer and only 1% is needed. 



Best Regards,
Zhenqiang Li

li_zhenqiang@hotmail.com
 
From: Ketan Talaulikar
Date: 2023-04-06 18:29
To: li_zhenqiang@hotmail.com
CC: draft-ietf-idr-segment-routing-te-policy.authors; idr@ietf.org; idr-ads; idr-chairs
Subject: Re: Clarifications on draft-ietf-idr-segment-routing-te-policy
Hi Zhenqiang Li,

The objective was not to change the base BGP decision process or the BGP propagation rules for this SAFI. I hope that explains the current text.

Thanks,
Ketan


On Thu, Apr 6, 2023 at 1:53 PM li_zhenqiang@hotmail.com <li_zhenqiang@hotmail.com> wrote:
Hello authors and all,

Hope it is not too late to make clarifications on this draft. 

This draft says one or more IPv4 address format route target extended community attached to the SR Policy advertisement and that indicates the intended headend of such an SR Policy advertisement.
And a BGP node advertises a received SR Policy NLRI to its IBGP neighbors according to normal IBGP propagation rules. 

Here a BGP node can be a RR(Route Reflector) which will reflect all the SR Policies to its IBGP peers regardless of the route target attached to the policies. So the IBGP peer node as the headend will receive lots of policies that are not intended for it because those policies have no route target that indicates the received peer node. 

In my opinion, the rules for RR to reflect SR policy with route target SHOULD be enhanced. RR SHOULD reflect related policies to relevant peers according to the route target attached to the policies.



Best Regards,
Zhenqiang Li

li_zhenqiang@hotmail.com