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)

peng.shaofu@zte.com.cn Mon, 15 July 2024 01:34 UTC

Return-Path: <peng.shaofu@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 9169FC14F6A3 for <idr@ietfa.amsl.com>; Sun, 14 Jul 2024 18:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 WyB2z7nBSSAQ for <idr@ietfa.amsl.com>; Sun, 14 Jul 2024 18:33:57 -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 66E5EC14F60E for <idr@ietf.org>; Sun, 14 Jul 2024 18:33:57 -0700 (PDT)
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 mxhk.zte.com.cn (FangMail) with ESMTPS id 4WMl8y5GHhz5B1Jb; Mon, 15 Jul 2024 09:33:54 +0800 (CST)
Received: from njy2app03.zte.com.cn ([10.40.13.14]) by mse-fl2.zte.com.cn with SMTP id 46F1Xfe8027856; Mon, 15 Jul 2024 09:33:41 +0800 (+08) (envelope-from peng.shaofu@zte.com.cn)
Received: from mapi (njb2app05[null]) by mapi (Zmail) with MAPI id mid201; Mon, 15 Jul 2024 09:33:42 +0800 (CST)
Date: Mon, 15 Jul 2024 09:33:42 +0800
X-Zmail-TransId: 2afd66947c766ce-6abb9
X-Mailer: Zmail v1.0
Message-ID: <20240715093342493cMpYPxHN-gh3LVvUO5TBX@zte.com.cn>
In-Reply-To: <CO1PR08MB66113D017CBDC604530E9090B3A62@CO1PR08MB6611.namprd08.prod.outlook.com>
References: CO1PR08MB66113D017CBDC604530E9090B3A62@CO1PR08MB6611.namprd08.prod.outlook.com
Mime-Version: 1.0
From: peng.shaofu@zte.com.cn
To: shares@ndzh.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 46F1Xfe8027856
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 66947C82.005/4WMl8y5GHhz5B1Jb
Message-ID-Hash: A7IEA6ES2HK3EWJVOYMRX7THY7FOZ6YG
X-Message-ID-Hash: A7IEA6ES2HK3EWJVOYMRX7THY7FOZ6YG
X-MailFrom: peng.shaofu@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/fV7Rjf-TszGB3RsLQlFbOsjobwU>
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,

I am not aware of any IPR related to this draft, and support the adoption.

1. Are new segment types needed for SR routing deployments?  
//Yes
2. Is the specification clear?
//Yes
3. Does this specification align with other spring documents?
//Yes


Regards,
PSF



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