[Idr] Re: Early Allocation Requests for IDR WG Drafts for SR - Call for comment (7/13/2025 to 7/20/2025)

linchangwang <linchangwang.04414@h3c.com> Mon, 14 July 2025 07:58 UTC

Return-Path: <linchangwang.04414@h3c.com>
X-Original-To: idr@mail2.ietf.org
Delivered-To: idr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id EF46D43B927F for <idr@mail2.ietf.org>; Mon, 14 Jul 2025 00:58:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w_oB9M1we8yO for <idr@mail2.ietf.org>; Mon, 14 Jul 2025 00:58:06 -0700 (PDT)
Received: from h3cspam02-ex.h3c.com (smtp.h3c.com [60.191.123.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 25A6743B9264 for <idr@ietf.org>; Mon, 14 Jul 2025 00:58:04 -0700 (PDT)
Received: from mail.maildlp.com ([172.25.15.154]) by h3cspam02-ex.h3c.com with ESMTP id 56E7vbSu068362; Mon, 14 Jul 2025 15:57:37 +0800 (+08) (envelope-from linchangwang.04414@h3c.com)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (unknown [10.153.34.10]) by mail.maildlp.com (Postfix) with ESMTP id 28A7020045A4; Mon, 14 Jul 2025 16:02:36 +0800 (CST)
Received: from DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) by DAG6EX08-BJD.srv.huawei-3com.com (10.153.34.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.27; Mon, 14 Jul 2025 15:57:29 +0800
Received: from DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738]) by DAG6EX08-BJD.srv.huawei-3com.com ([fe80::5d6c:b52b:478f:2738%17]) with mapi id 15.02.1258.027; Mon, 14 Jul 2025 15:57:28 +0800
From: linchangwang <linchangwang.04414@h3c.com>
To: Susan Hares <shares@ndzh.com>
Thread-Topic: Early Allocation Requests for IDR WG Drafts for SR - Call for comment (7/13/2025 to 7/20/2025)
Thread-Index: Adv0lOHgg2fIGiX4Tg2BXCFePPivcg==
Date: Mon, 14 Jul 2025 07:57:28 +0000
Message-ID: <885e6b070aa9433ca9ac4bc1150b1dbd@h3c.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.142.193.222]
x-sender-location: DAG2
Content-Type: multipart/alternative; boundary="_000_885e6b070aa9433ca9ac4bc1150b1dbdh3ccom_"
MIME-Version: 1.0
X-DNSRBL:
X-SPAM-SOURCE-CHECK: pass
X-MAIL: h3cspam02-ex.h3c.com 56E7vbSu068362
Message-ID-Hash: 4L4Q7OYHSFN3MXYCZKAY2W7TKW7DJBDE
X-Message-ID-Hash: 4L4Q7OYHSFN3MXYCZKAY2W7TKW7DJBDE
X-MailFrom: linchangwang.04414@h3c.com
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" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Idr] Re: Early Allocation Requests for IDR WG Drafts for SR - Call for comment (7/13/2025 to 7/20/2025)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/xj0XYCGruEh0zu4uZlI9PNwF3vs>
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,

IDR Draft

IANA Registry

Under Registry

Code Point

Description

draft status

draft-ietf-idr-sr-policy-seglist-id<https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-seglist-id/>

SR Policy List Sub-TLVs

BGP Tunnel Encapsulation

TBD (19)

Segment List ID Sub-TLV

Ready based on (-04) text.


It looks good to me.

Thanks,
Changwang (on behalf of  draft-ietf-idr-sr-policy-seglist-id<https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-seglist-id/>  co-authors)

发件人: Susan Hares <shares@ndzh.com>
发送时间: 2025年7月14日 6:34
收件人: idr@ietf.org
主题: [Idr] Early Allocation Requests for IDR WG Drafts for SR - Call for comment (7/13/2025 to 7/20/2025)

The IDR chairs intend to request early allocation for the following SR drafts:

Early allocations - WG drafts, need WG, WG chair and AD approval
SR Policy Segment List Sub-TLVs
(draft-ietf-idr-sr-policy-safi registries)
IDR Draft

IANA Registry

Under Registry

Code Point

Description

draft status

draft-ietf-idr-bgp-srmpls-elp<https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-srmpls-elp/>

SR Policy List Sub-TLVs

BGP Tunnel Encapsulation

TBD (26)

ELP Sub-TLV

Ready based on-03 text

draft-ietf-idr-sr-policy-path-segment<https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-path-segment/>

SR Policy List Sub-TLVs

BGP Tunnel Encapsulation

TBD1 (17)

Path Segment

Ready based on (-13) text, Needs -14 (editorial)

draft-ietf-idr-sr-policy-path-segment<https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-path-segment/>

SR Policy List Sub-TLVs

BGP Tunnel Encapsulation

TBD2 (18)

Reverse Segment List sub-TLV

Ready based on(-13)  text, Needs -14 (editorial)

draft-ietf-idr-sr-policy-seglist-id<https://datatracker.ietf.org/doc/draft-ietf-idr-sr-policy-seglist-id/>

SR Policy List Sub-TLVs

BGP Tunnel Encapsulation

TBD (19)

Segment List ID Sub-TLV

Ready based on (-04) text.



Please respond to this email with comments or send your comments to shares@ndzh.com<mailto:shares@ndzh.com>

Sue Hares
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有新华三集团的保密信息,仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、
或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本
邮件!
This e-mail and its attachments contain confidential information from New H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!