[Pce] 回复: WG Last Call: draft-ietf-pce-pcep-ls-06 (Ends 2026-05-28)
"Lixiao(lx)" <lixiao33@huawei.com> Thu, 14 May 2026 02:16 UTC
Return-Path: <lixiao33@huawei.com>
X-Original-To: pce@mail2.ietf.org
Delivered-To: pce@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id D5547EE10A72; Wed, 13 May 2026 19:16:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778725006; bh=swk1Zym1e3QXcPRaClvGi+ydFswh+NX2XjsMUra4HSY=; h=From:To:Subject:Date:References:In-Reply-To; b=Ydext6c4DPx2u07EioawWUFQYSipS9uLfyuugd/aVEsGr+uNdSO1yGxc8Mrtho28X IJOXC4qF5kZKRiz2SHgy3KOIg1Zk+Pl0BPQKCq3nRTT8Gsdw8ATy7IGQFv4zUrP5DR fxjfYF6EIu6FR1UgVWYz95ZyKVZT9xyqzfl8JJVA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_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 135jFNKuwf_y; Wed, 13 May 2026 19:16:44 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (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 B8C73EE10A6D; Wed, 13 May 2026 19:16:44 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.224.83]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4gGDTr04LLzHnGfQ; Thu, 14 May 2026 10:16:32 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id BFD3840575; Thu, 14 May 2026 10:16:42 +0800 (CST)
Received: from kwepemf200006.china.huawei.com (7.202.181.232) by kwepemh500011.china.huawei.com (7.202.181.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 14 May 2026 10:16:42 +0800
Received: from kwepemf500005.china.huawei.com (7.202.181.243) by kwepemf200006.china.huawei.com (7.202.181.232) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Thu, 14 May 2026 10:16:42 +0800
Received: from kwepemf500005.china.huawei.com ([7.202.181.243]) by kwepemf500005.china.huawei.com ([7.202.181.243]) with mapi id 15.02.1544.011; Thu, 14 May 2026 10:16:42 +0800
From: "Lixiao(lx)" <lixiao33@huawei.com>
To: Julien Meuric <julien.meuric@orange.com>, "draft-ietf-pce-pcep-ls@ietf.org" <draft-ietf-pce-pcep-ls@ietf.org>, "pce@ietf.org" <pce@ietf.org>
Thread-Topic: [Pce] WG Last Call: draft-ietf-pce-pcep-ls-06 (Ends 2026-05-28)
Thread-Index: AQHc4vhwAWa7hYzuVEijyDSrQxbyQ7YMySKg
Date: Thu, 14 May 2026 02:16:42 +0000
Message-ID: <5d1f2b877e18486a91b8005e27c5feb7@huawei.com>
References: <177869025567.1156217.14319693213969247690@dt-datatracker-54557f87b8-lnrkh>
In-Reply-To: <177869025567.1156217.14319693213969247690@dt-datatracker-54557f87b8-lnrkh>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.24.181.49]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: 5NPWJG6COHH2EUW3WUFC6CTWIL7TRROL
X-Message-ID-Hash: 5NPWJG6COHH2EUW3WUFC6CTWIL7TRROL
X-MailFrom: lixiao33@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Pce] 回复: WG Last Call: draft-ietf-pce-pcep-ls-06 (Ends 2026-05-28)
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/PmtNDEBoF2LhDKVL5WjE9nakZdM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>
Hi chairs, WG, I support moving this draft forward for publication. This draft provides a highly efficient mechanism for PCEP to carry link-state information, significantly enhancing the network visibility and path computation capabilities of the PCE architecture. This work is extremely valuable for optical networking. Thanks Regards -----邮件原件----- 发件人: Julien Meuric via Datatracker <noreply@ietf.org> 发送时间: 2026年5月14日 0:38 收件人: draft-ietf-pce-pcep-ls@ietf.org; pce@ietf.org 主题: [Pce] WG Last Call: draft-ietf-pce-pcep-ls-06 (Ends 2026-05-28) This message starts a WG Last Call for: draft-ietf-pce-pcep-ls-06 This Working Group Last Call ends on 2026-05-28 Abstract: In order to compute and provide optimal paths, Path Computation Elements (PCEs) require an accurate and timely Traffic Engineering Database (TED). Traditionally, this TED has been obtained from a link state (LS) routing protocol supporting the traffic engineering extensions. This document extends the Path Computation Element Communication Protocol (PCEP) with Link-State and TE Information as an experimental extension to allow gathering more deployment and implementation feedback on the use of PCEP in this way. File can be retrieved from: Please review and indicate your support or objection to proceed with the publication of this document by replying to this email keeping pce@ietf.org in copy. Objections should be explained and suggestions to resolve them are highly appreciated. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [1]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/ The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-ls/ There is also an HTML version available at: https://www.ietf.org/archive/id/draft-ietf-pce-pcep-ls-06.html A diff from the previous version is available at: https://author-tools.ietf.org/iddiff?url2=draft-ietf-pce-pcep-ls-06 _______________________________________________ Pce mailing list -- pce@ietf.org To unsubscribe send an email to pce-leave@ietf.org
- [Pce] WG Last Call: draft-ietf-pce-pcep-ls-06 (En… Julien Meuric via Datatracker
- [Pce] 回复: WG Last Call: draft-ietf-pce-pcep-ls-06… Lixiao(lx)
- [Pce] Re: WG Last Call: draft-ietf-pce-pcep-ls-06… Adrian Farrel
- [Pce] Re: WG Last Call: draft-ietf-pce-pcep-ls-06… Italo Busi