[Idr] 答复: draft-ietf-idr-sr-policy-path-segment-10 - Early Allocations
zhao.detao@zte.com.cn Sat, 17 August 2024 09:40 UTC
Return-Path: <zhao.detao@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 837F6C151094; Sat, 17 Aug 2024 02:40:51 -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 HnOJhyl3tcxj; Sat, 17 Aug 2024 02:40: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 C773EC151091; Sat, 17 Aug 2024 02:40:37 -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 4WmDPG5lq4z5B1Jc; Sat, 17 Aug 2024 17:40:34 +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 4WmDNd2wL0z4xVd2; Sat, 17 Aug 2024 17:40:01 +0800 (CST)
Received: from njy2app01.zte.com.cn ([10.40.12.136]) by mse-fl2.zte.com.cn with SMTP id 47H9ds2O006082; Sat, 17 Aug 2024 17:39:54 +0800 (+08) (envelope-from zhao.detao@zte.com.cn)
Received: from mapi (njy2app02[null]) by mapi (Zmail) with MAPI id mid201; Sat, 17 Aug 2024 17:39:56 +0800 (CST)
Date: Sat, 17 Aug 2024 17:39:56 +0800
X-Zmail-TransId: 2afa66c06fecffffffffa15-f39b8
X-Mailer: Zmail v1.0
Message-ID: <20240817173956973f1DQ89SxZI0ROgnQ1iOXO@zte.com.cn>
In-Reply-To: <CO1PR08MB6611A464B252024B83BE4124B3FB2@CO1PR08MB6611.namprd08.prod.outlook.com>
References: CO1PR08MB6611A464B252024B83BE4124B3FB2@CO1PR08MB6611.namprd08.prod.outlook.com
Mime-Version: 1.0
From: zhao.detao@zte.com.cn
To: shares@ndzh.com
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn 47H9ds2O006082
X-Fangmail-Anti-Spam-Filtered: true
X-Fangmail-MID-QID: 66C07012.001/4WmDPG5lq4z5B1Jc
Message-ID-Hash: 4GPEYEFMTH3UPCXH4A4VJI5TKRONHOZU
X-Message-ID-Hash: 4GPEYEFMTH3UPCXH4A4VJI5TKRONHOZU
X-MailFrom: zhao.detao@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, draft-ietf-idr-sr-policy-path-segment@ietf.org, wu.haisheng@zte.com.cn, shao.xi@zte.com.cn, feng.jun99@zte.com.cn
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] 答复: draft-ietf-idr-sr-policy-path-segment-10 - Early Allocations
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/oq8GNxmT5NL-tqxt70bUtN-2RRU>
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,
SR Policy Segment List Sub-TLVs type 16 already be assigned to Segment Type K
in draft https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-sr-segtypes-ext/
Value Description Reference
-----------------------------------------------------
3 Segment Type C sub-TLV This document
4 Segment Type D sub-TLV This document
5 Segment Type E sub-TLV This document
6 Segment Type F sub-TLV This document
7 Segment Type G sub-TLV This document
8 Segment Type H sub-TLV This document
14 Segment Type I sub-TLV This document
15 Segment Type J sub-TLV This document
16 Segment Type K sub-TLV This document
so woud you like to recommend type 17 for path-segment sub-TLV and type 18 for Reverse Segment List sub-TLV?
Codepoint Description Reference---------- ------------------------------ -------------TBA1 (17) Path Segment sub-TLV This documentTBA2 (18) Reverse Segment List sub-TLV This document
赵德涛
软件平台开发一部/有线研究院/有线产品经营部
中兴通讯股份有限公司
南京市紫荆花路68号南研一期, 邮编: 210012
T: +86 15951883174 M: +86 15951883174
E: zhao.detao@zte.com.cn
Original
From: SusanHares <shares@ndzh.com>
To: idr@ietf.org <idr@ietf.org>;draft-ietf-idr-sr-policy-path-segment@ietf.org <draft-ietf-idr-sr-policy-path-segment@ietf.org>;
Date: 2024年06月07日 21:51
Subject: [Idr] draft-ietf-idr-sr-policy-path-segment-10 - Early Allocations
_______________________________________________
Idr mailing list -- idr@ietf.org
To unsubscribe send an email to idr-leave@ietf.org
Greetings:
Your request for early allocation cannot be processed at this time.
[draft-ietf-idr-sr-policy-safi-04]
(https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-safi/)
has not been approved by the IESG, so values for registry for
SR Policy Segment List Sub-TLVs cannot be assigned.
Codepoint Description Reference ---------- ------------------------------ ------------- TBA1 (16) Path Segment sub-TLV This document TBA2 (17) Reverse Segment List sub-TLV This document
When the registry is created, I will recommend the following two values be assigned.
https://wiki.ietf.org/e/en/group/idr/Early-Allocation-Status
Please make the following editorial changes to your document:
Introduction:
Text: / Further more, in
some scenarios, (e.g., Mobile backhaul transport networks), there are Requirements to support bidirectional path./
New text: / In some scenarios (e.g., Mobile backhaul transport networks), there are
Requirements to support bidirectional path./ Why: The “Further more” is unnecessary, incorrectly spelled, and makes text difficult to read.
Section 3.1
Current: / * Type: to be assigned by IANA./ New: / * Type (TBD1): SR Path Segment Sub-TLV (to be assigned by IANA)./ Section 4.1
Current: / * Type: to be assigned by IANA./ New: / * Type (TBD2): Reverse Path Segment List Sub-TLV (to be assigned by IANA)./ Codepoint Description Reference ---------- ------------------------------ ------------- TBA1 (14) Path Segment sub-TLV This document TBA2 (15) Reverse Segment List sub-TLV This document Cheerily, Susan Hares
- [Idr] draft-ietf-idr-sr-policy-path-segment-10 - … Susan Hares
- [Idr] Re: draft-ietf-idr-sr-policy-path-segment-1… Cheng Li
- [Idr] 答复: draft-ietf-idr-sr-policy-path-segment-1… zhao.detao
- [Idr] Re: draft-ietf-idr-sr-policy-path-segment-1… Susan Hares
- [Idr] Re: draft-ietf-idr-sr-policy-path-segment-1… Cheng Li
- [Idr] Re: draft-ietf-idr-sr-policy-path-segment-1… Susan Hares