[Pce] Re: Call for slot in the PCE WG at IETF 125
Adrian Farrel <adrian@olddog.co.uk> Fri, 27 February 2026 10:07 UTC
Return-Path: <adrian@olddog.co.uk>
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 7EDBDBF74D01; Fri, 27 Feb 2026 02:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.797
X-Spam-Level:
X-Spam-Status: No, score=-2.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
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 qrpQm2suWjDs; Fri, 27 Feb 2026 02:07:42 -0800 (PST)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 5865FBF74827; Fri, 27 Feb 2026 02:06:59 -0800 (PST)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.7/8.14.7) with ESMTP id 61RA6pYi006317; Fri, 27 Feb 2026 10:06:51 GMT
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 227734605D; Fri, 27 Feb 2026 10:06:51 +0000 (GMT)
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 15BBD4605A; Fri, 27 Feb 2026 10:06:51 +0000 (GMT)
Received: from asmtp2.iomartmail.com (unknown [10.12.10.249]) by vs2.iomartmail.com (Postfix) with ESMTPS; Fri, 27 Feb 2026 10:06:51 +0000 (GMT)
Received: from LAPTOPK7AS653V (82-69-109-75.dsl.in-addr.zen.co.uk [82.69.109.75]) (authenticated bits=0) by asmtp2.iomartmail.com (8.14.7/8.14.7) with ESMTP id 61RA6n8T004063 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 27 Feb 2026 10:06:50 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Dhruv Dhody' <dd@dhruvdhody.com>, pce@ietf.org
References: <CAP7zK5ZD0F6fackmRz3Sjn+8PF5teae-ounuCATvH3BkoMLk1w@mail.gmail.com>
In-Reply-To: <CAP7zK5ZD0F6fackmRz3Sjn+8PF5teae-ounuCATvH3BkoMLk1w@mail.gmail.com>
Date: Fri, 27 Feb 2026 10:06:48 -0000
Organization: Old Dog Consulting
Message-ID: <115701dca7d0$c9ed23b0$5dc76b10$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_1158_01DCA7D0.C9EE0E10"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQINVkDmgWKR+TBnSXeZoF/c7d0cZrU08zxg
Content-Language: en-gb
X-Originating-IP: 82.69.109.75
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type; s=20221128; bh=mpcDyzwr8Qvlwfw6DsQjY AJX6lllG3HJ9Z/y4pgV8mg=; b=xk9iK1RSp4ALKyChigrirEZ4141F9ZbJrKpvT MdtbAQPsRrqGfjqkHjeu8XhzIRfPy5CPR7AaZciXXr14yXfu1VLR57CMro4+Xb3x xMoJeSk+Fk1oYUzOiEQvaidOXLvxeUB7Fk10EMSPiXpWiy4T+jVA/tBdWeOefZdJ EBDs3VBE5ofWiaJRvP7qokM6dWrqso1FoublY2FwTvwCFtojGQqjDvmzpq6Kezf8 KUaLLNV/WzMSP9CZTVOZNhPmrFjceaRa+2cRiZD0cdoWpncbDF3/V0XF+5tDC2QM C+/bPDgubww70lt/gUvhbvoLOvuToEUxrbQJGW1m45Q3+iePA==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1006-29464.005
X-TM-AS-Result: No--19.504-10.0-31-10
X-imss-scan-details: No--19.504-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1006-29464.005
X-TMASE-Result: 10--19.503900-10.000000
X-TMASE-MatchedRID: JSzpgjECRiE7iuZ/mdYYtto4g/Zvpl9fzVc6h59kV95+3E64qYVhyUVt 5tkKdcRcuohcuWcG2KgM6z3iDvziB5GAt645FF0Sd95C4qPyHP5YqgMpOy5G5K1WeXF3k4R03fn V5X7eaBvPPjrrwf9gD5UXYcPwQc2nqxxYRyql7ks/gf7afIrQU07HfnB/xfeqpsX84hgxtpra2w trEP04wdZPXjgjznq/71Wx2uUbPLdDr8MVm6DK3Vti/oq364XY9TvadhXG9g3gPqVbzYllURvzE jY4Pdnt7IPLxXyVNZRkGI+vgRTxMFGk5uRH0MzCR6RHdVK85hXaOBWaEqUPGKofXa4f40fCVCHl gT24MfuDPJ3sg13mJzZoNXJMbH+nEsGpOXjV8vvG6KjwOvvPJG9cVO2+AmYaYuZ5YtjU2X2CUw9 o0jKgrDICk1lDbuIzmmDwg4h7AdCZEoWHC6Rh/eajpXRMTwmj+qwObAztNgxU1xB5SaFW0yqFmu /h/tw7CkBHQ7k87pIvj6wHfIGxyS2VljVYB9GN45EBnqRCHdVGXqPwoozDveLNRz6Y86fZHWm5U oWAU14YB2fOueQzjxRFJJyf5BJeWQy9YC5qGvzQBQ8SBUzMX5HPiP8gMM5jJy3YeVy0eU5XhqN9 H2OPZ2F5X5yuwTohA/3R8k/14e0=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Message-ID-Hash: AJTLPWM255VNXAPRHRPV3AC4OTIEF7RB
X-Message-ID-Hash: AJTLPWM255VNXAPRHRPV3AC4OTIEF7RB
X-MailFrom: adrian@olddog.co.uk
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
CC: 'pce-chairs' <pce-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: adrian@olddog.co.uk
Subject: [Pce] Re: Call for slot in the PCE WG at IETF 125
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/CYf-e8bmavPk7uj2Clmf2S1V7ik>
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 Dhruv, We’d like a slot in the PCE agenda to discuss: * draft-lee-pce-pcep-ps-optical * presented by Xiao and/or Adrian * in-person attendance * 10 minutes * It’s been a while since this was presented, and we have recently rejuvenated the work. We want to explain how this is important to optical systems, how it builds on the experimental PCEP-LS (which is queued for last call), and set out how we will progress with the document if it is adopted by the working group. Thanks, Adrian PS. We really, really think this document is overdue adoption by the working group! From: Dhruv Dhody <dd@dhruvdhody.com> Sent: 17 February 2026 13:44 To: pce@ietf.org Cc: pce-chairs <pce-chairs@ietf.org> Subject: [Pce] Call for slot in the PCE WG at IETF 125 Hi PCE WG, The PCE WG will be meeting during the IETF 125 [1] week. If you need agenda time to progress some work, please send a slot request to the chairs/secretary <mailto:pce-chairs@ietf.org> pce-chairs@ietf.org by Monday, March 2nd by including: - the draft(s) you want to discuss, - the expected presenter name, - will you be attending in-person or remote, - the requested duration, including question time as part of the slot, - the reason why you want to be on the agenda; What do you want to achieve? Why is a presentation necessary to achieve it? Please note - Asking for a slot does not mean you will get one. We will be prioritizing moving WG work first as well as drafts that were discussed on the mailing list. Please make sure to introduce your new draft or summarize an update on the mailing list. The last date to submit drafts is also Monday, March 2nd [2]. Also, let us know if you have requested agenda time in a different WG session for the same topic. Thanks! Dhruv [1] https://datatracker. <https://datatracker.ietf.org/meeting/125/agenda/> ietf.org/meeting/125/agenda/ [2] https://datatracker. <https://datatracker.ietf.org/meeting/important-dates/> ietf.org/meeting/important-dates/
- [Pce] Re: Call for slot in the PCE WG at IETF 125 Hooman Bidgoli (Nokia)
- [Pce] Re: Call for slot in the PCE WG at IETF 125 zhou.jin6
- [Pce] Call for slot in the PCE WG at IETF 125 Dhruv Dhody
- [Pce] Re: Call for slot in the PCE WG at IETF 125 Adrian Farrel
- [Pce] Re: Call for slot in the PCE WG at IETF 125 zhangli (CE)
- [Pce] Re: Call for slot in the PCE WG at IETF 125 Zafar Ali (zali)
- [Pce] Re: Call for slot in the PCE WG at IETF 125 Zafar Ali (zali)