[Teas] IETF 124 TEAS WG Session - Call for Slot Requests

Italo Busi <Italo.Busi@huawei.com> Tue, 07 October 2025 14:30 UTC

Return-Path: <Italo.Busi@huawei.com>
X-Original-To: teas@mail2.ietf.org
Delivered-To: teas@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 54B746EAA33B for <teas@mail2.ietf.org>; Tue, 7 Oct 2025 07:30:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.195
X-Spam-Level:
X-Spam-Status: No, score=-4.195 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_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 oIQ47jngzpOZ for <teas@mail2.ietf.org>; Tue, 7 Oct 2025 07:30:46 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A94A96EAA18A for <teas@ietf.org>; Tue, 7 Oct 2025 07:30:26 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4cgz3v3J9Nz6M4d4 for <teas@ietf.org>; Tue, 7 Oct 2025 22:27:07 +0800 (CST)
Received: from dubpeml500003.china.huawei.com (unknown [7.214.146.145]) by mail.maildlp.com (Postfix) with ESMTPS id AF8C31402CB for <teas@ietf.org>; Tue, 7 Oct 2025 22:30:24 +0800 (CST)
Received: from dubpeml100004.china.huawei.com (7.214.146.78) by dubpeml500003.china.huawei.com (7.214.146.145) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 7 Oct 2025 15:30:24 +0100
Received: from dubpeml100004.china.huawei.com ([7.214.146.78]) by dubpeml100004.china.huawei.com ([7.214.146.78]) with mapi id 15.02.1544.011; Tue, 7 Oct 2025 15:30:24 +0100
From: Italo Busi <Italo.Busi@huawei.com>
To: TEAS WG <teas@ietf.org>
Thread-Topic: IETF 124 TEAS WG Session - Call for Slot Requests
Thread-Index: Adw3llW8xMdZ546KTkGLa1ORZqbbSg==
Date: Tue, 07 Oct 2025 14:30:24 +0000
Message-ID: <fc6f6358f71e40209b7968d60c4d6054@huawei.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.207.138]
Content-Type: multipart/alternative; boundary="_000_fc6f6358f71e40209b7968d60c4d6054huaweicom_"
MIME-Version: 1.0
Message-ID-Hash: 7LMG3M72LQELAQIX3CEH6VNV7SUGELOG
X-Message-ID-Hash: 7LMG3M72LQELAQIX3CEH6VNV7SUGELOG
X-MailFrom: Italo.Busi@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.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: [Teas] IETF 124 TEAS WG Session - Call for Slot Requests
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/4NMZOpHd2-R122wlQfVKBjqEWKg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

As per the IETF 124 preliminary agenda (https://datatracker.ietf.org/meeting/124/agenda) the TEAS WG session is scheduled to be held on Tuesday November 4, 2025 at 11:30-13:00 EST (Room Laurier)



As usual, the session will be used to focus on updates, summarizing open issues, and new topics. Please send your slot requests to teas-chairs@ietf.org<mailto:teas-chairs@ietf.org> before the end of the day October 20, 2025 (any TZ).  Please include draft name(s), presenter and desired slot length.



Please note that all authors of working group documents are required to provide a status update to the WG at *every* IETF meeting. Status includes, at a minimum, recent changes, open issues, and plans to complete the document. Status can be provided via:

(a) A report during the IETF session, or

(b) An email to the WG list, sent no later than the Internet-Draft submission cut-off



Regards,



Italo, Pavan and Oscar