IETF Logo Mail Archive

[Idr] Re: Adoption call for draft-peng-idr-segment-routing-te-policy-attr-11 (7/12/2024 to 7/26/2024)

chen.ran@zte.com.cn Wed, 17 July 2024 09:17 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 E3560C14F603 for <idr@ietfa.amsl.com>; Wed, 17 Jul 2024 02:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 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, 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 LdNBN1Vp-Qsm for <idr@ietfa.amsl.com>; Wed, 17 Jul 2024 02:17:42 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.216.63.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0CBCC14F5F1 for <idr@ietf.org>; Wed, 17 Jul 2024 02:17:39 -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 4WP9M20vjdz8XrS0; Wed, 17 Jul 2024 17:17:34 +0800 (CST)
Received: from njb2app05.zte.com.cn ([10.55.22.121]) by mse-fl1.zte.com.cn with SMTP id 46H9HRd3078804; Wed, 17 Jul 2024 17:17:28 +0800 (+08) (envelope-from chen.ran@zte.com.cn)
Received: from mapi (njb2app07[null]) by mapi (Zmail) with MAPI id mid203; Wed, 17 Jul 2024 17:17:30 +0800 (CST)
Date: Wed, 17 Jul 2024 17:17:30 +0800
X-Zmail-TransId: 2aff66978c2afffffffffaf-20adf
X-Mailer: Zmail v1.0
Message-ID: <20240717171730886ojDvRRTiLHNk30-lEnD6t@zte.com.cn>
In-Reply-To: <CO1PR08MB66113D017CBDC604530E9090B3A62@CO1PR08MB6611.namprd08.prod.outlook.com>
References: CO1PR08MB66113D017CBDC604530E9090B3A62@CO1PR08MB6611.namprd08.prod.outlook.com
Mime-Version: 1.0
From: chen.ran@zte.com.cn
To: shares@ndzh.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn 46H9HRd3078804
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 66978C2E.000/4WP9M20vjdz8XrS0
Message-ID-Hash: LGOXAAGKHOWFKIDFYNSVUX2QYFVDAEDN
X-Message-ID-Hash: LGOXAAGKHOWFKIDFYNSVUX2QYFVDAEDN
X-MailFrom: chen.ran@zte.com.cn
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: idr@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: Adoption call for draft-peng-idr-segment-routing-te-policy-attr-11 (7/12/2024 to 7/26/2024)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/dzcV-PLPwxeyYl4YX3NKWUlYgFs>
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 Sue and WG,

I support the adoption of this draft.  Please see below for answers to related questions.
1. Yes.  I think so. 
2. This document is clear.
3. Yes. This draft defines new segment types for SR-MPLS Adjacency-SIDs based on RFC9256. 

Best Regards,

Ran


Original


From: SusanHares <shares@ndzh.com>
To: idr@ietf.org <idr@ietf.org>;
Date: 2024年07月12日 18:21
Subject: [Idr] Adoption call for draft-peng-idr-segment-routing-te-policy-attr-11 (7/12/2024 to 7/26/2024)

_______________________________________________
Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org
 

This message starts a 2 week adoption call for  
draft-peng-idr-segment-routing-te-policy-attr-11 (7/12/2024 to 7/26/2024)
https://datatracker.ietf.org/doc/draft-peng-idr-segment-routing-te-policy-attr/
 
The authors should respond to this email with their IPR Statement 
(do you know of any IPR related to this draft)? 
 
In your comments, please consider if 
 

Are new segment types needed for SR routing deployments?  

Is the specification clear? 

Does this specification align with other spring documents? 


 
Cheerily, Sue Hares

v2.46.0 | Report a Bug | By Email | System Status