Re: [Idr] draft-peng-idr-segment-routing-te-policy-attr-08
liu.yao71@zte.com.cn Wed, 27 March 2024 14:57 UTC
Return-Path: <liu.yao71@zte.com.cn>
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 63C7BC14F699 for <idr@ietfa.amsl.com>; Wed, 27 Mar 2024 07:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.905
X-Spam-Level:
X-Spam-Status: No, score=-6.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=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, UNPARSEABLE_RELAY=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 kTki5zahsGe3 for <idr@ietfa.amsl.com>; Wed, 27 Mar 2024 07:57:47 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3117CC157938 for <idr@ietf.org>; Wed, 27 Mar 2024 07:57:46 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.5.228.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxhk.zte.com.cn (FangMail) with ESMTPS id 4V4VC90yP0z4xPYf; Wed, 27 Mar 2024 22:57:41 +0800 (CST)
Received: from njb2app05.zte.com.cn ([10.55.22.121]) by mse-fl1.zte.com.cn with SMTP id 42REvYwr041639; Wed, 27 Mar 2024 22:57:34 +0800 (+08) (envelope-from liu.yao71@zte.com.cn)
Received: from mapi (njy2app03[null]) by mapi (Zmail) with MAPI id mid203; Wed, 27 Mar 2024 22:57:38 +0800 (CST)
Date: Wed, 27 Mar 2024 22:57:38 +0800
X-Zmail-TransId: 2afb660433e2ffffffffe03-3a8dd
X-Mailer: Zmail v1.0
Message-ID: <20240327225738882XLvHv5Era9H2s4nGN_dGb@zte.com.cn>
In-Reply-To: <DM6PR08MB4857C367BF5AD08B5BC230E5B32D2@DM6PR08MB4857.namprd08.prod.outlook.com>
References: DM6PR08MB4857C367BF5AD08B5BC230E5B32D2@DM6PR08MB4857.namprd08.prod.outlook.com
Mime-Version: 1.0
From: liu.yao71@zte.com.cn
To: shares@ndzh.com
Cc: idr@ietf.org, hayabusagsm@gmail.com, peng.shaofu@zte.com.cn
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 42REvYwr041639
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 660433E5.000/4V4VC90yP0z4xPYf
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/09fvrsb_-wATVqhuOsy_O6Z_b_s>
Subject: Re: [Idr] draft-peng-idr-segment-routing-te-policy-attr-08
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, 27 Mar 2024 14:57:51 -0000
Hi Sue, As far as I know, Segment Type L, M, N, and O have not been implemented yet. But there're on-going implementations for the original segment types without the optional algorithm field as in draft-ietf-idr-bgp-sr-segtypes-ext. One example is that , for type H, the controller sends the segment sub-TLV with local and remote IPv6 addresses to the headend. And then the headend resolves the specified Local IPv6 Address to the node originating it and then use the Remote IPv6 Address to identify the link adjacency being referred to as well as the adj SID related with it, just following the procedure in RFC 9256 section 4. Yao Original From: SusanHares <shares@ndzh.com> To: idr@ietf.org <idr@ietf.org>; Cc: 刘尧00165286;Gyan Mishra <hayabusagsm@gmail.com>;彭少富10053815; Date: 2024年03月18日 08:12 Subject: draft-peng-idr-segment-routing-te-policy-attr-08 Greetings Yao, Shaofu, and Gyan: Just a few questions prior to the IDR meeting at IETF today. Could you let me know if you know of implementations of Segment Type L, M, N, and O? It would be helpful to know how these segment types will be used in networks. Could you please send an example of how these segments would exist in networks. Sue