IETF Logo Mail Archive

[TLS] Re: [Seat] Procedural clarification regarding ITU-T SG17 Liaison Officer to IETF SEC area

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Thu, 02 April 2026 08:35 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 32552D5665FC; Thu, 2 Apr 2026 01:35:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775118913; bh=0GwIVCe6x36OVd4xJyLExfVZsiPtrdkva5KmCBhynwk=; h=Date:Subject:From:To:CC:References:In-Reply-To; b=OilEash9SrO8ROQN8JSU9Y5M2e0tSi3XjzUpFIp+Hh55lKgSoch9IyZ7MDiIfT9yL KdBQ8H7vT8Ew2q5GNpKejcZ1hoDnk4RpOvO8plFeWf45xvPq9fc/qt4fS1K3Lc0AuM 1bfION4DZrLX2ntmEJIYXpSZVyEhjzx02wLuowks=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_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=tu-dresden.de
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 DZYXKwMuflnT; Thu, 2 Apr 2026 01:35:12 -0700 (PDT)
Received: from mailout7.zih.tu-dresden.de (mailout7.zih.tu-dresden.de [141.76.32.220]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 3CF03D5665E6; Thu, 2 Apr 2026 01:35:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tu-dresden.de; s=dkim2022; h=Content-Type:In-Reply-To:References:CC:To:From :Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=8FnkS6BbqiWelNJ0Kztt3kpjwhKOX8xKyAogI5glhgs=; b=dvGAMU47OoY9f6dQvAF+pssPJm EE3G4N/i3scVk5MWPDkCtKnwOcbXfodkpQYOkZMjlgTEF7WL84cxxU1TtYvQrnBq5IA/TtnV5+ZXT KJ2lyjQgOt9Q48lqtmEHrcCiTJGbksWQLnskED6t8pD5HR4QbCVROIvdx+9cCH1pp1JZe4mY4/M00 mjE7GM2dY89IX8hXMJbRCVehh2YiDuUmQc4F4dzzI0BDdBcE506DkXnVVnjmTX0Qtvu2iLZLJutMm uoOuK8/OKnGf9WgqErEcE3F6RQwrp0ZZpWx8gE2lg2qut8ubtsaw7zh5ejtuaSuVYyE/CB86nSMj7 yQDLG58w==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout7.zih.tu-dresden.de with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1w8DW7-008kmR-0t; Thu, 02 Apr 2026 10:35:11 +0200
Received: from [10.12.5.228] (141.76.13.165) by msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.2562.37; Thu, 2 Apr 2026 10:35:01 +0200
Message-ID: <13f1ee15-ec49-4ae5-8876-adda007fff89@tu-dresden.de>
Date: Thu, 02 Apr 2026 10:35:01 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
To: saag <saag@ietf.org>
References: <220ca1ba-62a1-41a1-ac37-e7be80de7321@tu-dresden.de>
Content-Language: en-US
In-Reply-To: <220ca1ba-62a1-41a1-ac37-e7be80de7321@tu-dresden.de>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms010205080609040304040205"
X-ClientProxiedBy: MSX-T415.msx.ad.zih.tu-dresden.de (172.26.35.135) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout7.zih.tu-dresden.de
Message-ID-Hash: VGP7UUYKFPQYW2IXNWCDRX5O5FWSQCGH
X-Message-ID-Hash: VGP7UUYKFPQYW2IXNWCDRX5O5FWSQCGH
X-MailFrom: muhammad_usama.sardar@tu-dresden.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "TLS@ietf.org" <tls@ietf.org>, "rats@ietf.org" <rats@ietf.org>, "seat@ietf.org" <seat@ietf.org>, teep@ietf.org, "agent2agent@ietf.org" <agent2agent@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: [Seat] Procedural clarification regarding ITU-T SG17 Liaison Officer to IETF SEC area
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/YJH5U9gDT-cJb-Q88fDrMBnY9KI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

Hi,

Sincere apologies for cross-posting to multiple lists.

Just a quick procedural clarification: The formal process at SG17 is 
expected to conclude in June. At that time, the Liaison Officer will be 
officially designated and communicated by Liaison Statement to the IETF.

Until then, I'm happy to unofficially help bridge /in my personal 
capacity/, as I personally see potential for overlap between SG17 and 
the IETF. Regardless of who is eventually selected for the formal role, 
I would like to see the two organizations collaborating more to benefit 
from each other's work and expertise.

If I can be of any help in the mean time, please feel free to reach out 
to me off-list.

Best regards,

-Usama

v2.46.0 | Report a Bug | By Email | System Status