IETF Logo Mail Archive

Re: [Idr] WG Adoption call for draft-peng-idr-segment-routing-te-policy-attr-05 (9/26/2023-10/10/2023)

chen.ran@zte.com.cn Sat, 07 October 2023 08:57 UTC

Return-Path: <chen.ran@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 61270C14CE33 for <idr@ietfa.amsl.com>; Sat, 7 Oct 2023 01:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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, UNPARSEABLE_RELAY=0.001, 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 VDBAVyhEWE1Z for <idr@ietfa.amsl.com>; Sat, 7 Oct 2023 01:57:13 -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 37BD5C14CF12 for <idr@ietf.org>; Sat, 7 Oct 2023 01:57:12 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.251.13]) (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 4S2fLW3blpz4xPFv for <idr@ietf.org>; Sat, 7 Oct 2023 16:57:07 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.5.228.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mxct.zte.com.cn (FangMail) with ESMTPS id 4S2fL01fPKz4xVcN; Sat, 7 Oct 2023 16:56:40 +0800 (CST)
Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl2.zte.com.cn with SMTP id 3978uTi0048997; Sat, 7 Oct 2023 16:56:29 +0800 (+08) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njb2app06[null]) by mapi (Zmail) with MAPI id mid203; Sat, 7 Oct 2023 16:56:31 +0800 (CST)
Date: Sat, 07 Oct 2023 16:56:31 +0800
X-Zmail-TransId: 2afe65211d3f219-a09bc
X-Mailer: Zmail v1.0
Message-ID: <202310071656315813346@zte.com.cn>
In-Reply-To: <BYAPR08MB487268B41AB9991CDA09CAC0B3C2A@BYAPR08MB4872.namprd08.prod.outlook.com>
References: BYAPR08MB487268B41AB9991CDA09CAC0B3C2A@BYAPR08MB4872.namprd08.prod.outlook.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: shares@ndzh.com
Cc: idr@ietf.org
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 3978uTi0048997
X-Fangmail-Gw-Spam-Type: 0
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 65211D63.000/4S2fLW3blpz4xPFv
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/S2pup3nwisbI6FuM3Jvsof4y0H8>
Subject: Re: [Idr] WG Adoption call for draft-peng-idr-segment-routing-te-policy-attr-05 (9/26/2023-10/10/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: Sat, 07 Oct 2023 08:57:17 -0000

Hi WG，
I support this adoption. It is very useful to define new Segment Types for networks using alternate algorithms.

Best Regards,
Ran


Original


From: SusanHares <shares@ndzh.com>
To: idr@ietf.org <idr@ietf.org>;
Date: 2023年09月27日 10:33
Subject: [Idr] WG Adoption call for draft-peng-idr-segment-routing-te-policy-attr-05 (9/26/2023-10/10/2023)

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

 

This begins a 2-week WG adoption call for
draft-peng-idr-segment-routing-te-policy-attr-05
(https://datatracker.ietf.org/doc/draft-peng-idr-segment-routing-te-policy-attr/)
 
In your comments, please indicate
“support” or “no support”.
 
Please also consider the following questions:
 
1) Are these new segment types are useful for networks
Using alternate algorithms?
 
2) This draft will need to align with the
draft-ietf-idr-segment-routing-te-policy
split into  draft-ietf-idr-segment-routing-te-policy
and draft-ietf-idr-sr-segtypes-ext-01.
 
Do you see any issues with this alignment?
 
Cheerily, Sue Hares

v2.23.0 | Report a Bug | By Email