[saag] Re: Government–Industry Dialogue Public Side Meeting at IETF 126 Vienna

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Fri, 17 July 2026 21:15 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
X-Original-To: saag@mail2.ietf.org
Delivered-To: saag@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2CE4C11895E34 for <saag@mail2.ietf.org>; Fri, 17 Jul 2026 14:15:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1784322923; bh=0R5VDXZvq4cc92NDr/9MqFILhpv8pc71XOKwQENX94o=; h=Date:From:Subject:To:References:In-Reply-To; b=Z8LMK4aN3c8opzYQyYQwRlGTKjUVzhNxhnuGXZDYi+/c5qveY5HSXLboqgJUhK9FD xeSFuNJz+/2h7PhJoG77ut7RktU/AlysQhKfgC+EMMOLh/7CNwRAIxG9J4n7TR7k7s HroPU7qCiDUQVxMEv+Que/MDCCMC8BRkAUKYGeic=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=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 DKQ2Ykc6iOua for <saag@mail2.ietf.org>; Fri, 17 Jul 2026 14:15:22 -0700 (PDT)
Received: from mailout3.zih.tu-dresden.de (mailout3.zih.tu-dresden.de [141.30.67.74]) (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 4D52A11895E21 for <saag@ietf.org>; Fri, 17 Jul 2026 14:15:22 -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:To:Subject :From:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: 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=EtTdVs5MRJQ0vtvI04W6Ydk/dudvidHrsFmgsD/a17o=; b=jYgGKiSAn2TAr6AiluqOP3Xgkp MvFor4wlaAdkzPhtBjq9IYEfdNupJKsu9J5mFAmNEiGAA72QPX7e+u8jL96TW+JBoZOME+1xe5woE Kpy0Q1NOPiTGtYjawMulESCIMRcjN0PJ1fXltcl1ef7h21audki3ukIsUOzo9STefhlhdyw1UzpLw kpm1Rt8z3ifWhiVDe5SNIC3OmFcLkKbpxdsSHHN660lYgMINhryuIF6f3Qe+peW0X/+/fCdhu448t MvXa4qHfWcpmxvYVxReDNcRqWHf9VHUAM1yZ8EGAqJatCqc0pEY0psDl1NdI/+dPqkmmUGyCnfPnk Wpo3bP+w==;
Received: from msx-t422.msx.ad.zih.tu-dresden.de ([172.26.35.139] helo=msx.tu-dresden.de) by mailout3.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 1wkptw-007d3l-32; Fri, 17 Jul 2026 23:15:21 +0200
Received: from [192.168.0.75] (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.45; Fri, 17 Jul 2026 23:15:18 +0200
Message-ID: <f34030f9-ddf4-4430-98fe-61de3ee7dc8c@tu-dresden.de>
Date: Fri, 17 Jul 2026 23:15:12 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
To: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, IETF SAAG <saag@ietf.org>
References: <AS4PR07MB88251AF6A139A9EEBCCEEEC789C62@AS4PR07MB8825.eurprd07.prod.outlook.com> <AS4PR07MB88256FA0117CDE9A45C6ED6689C62@AS4PR07MB8825.eurprd07.prod.outlook.com> <AS4PR07MB8825D8C909770C48999FCE3489C62@AS4PR07MB8825.eurprd07.prod.outlook.com>
Content-Language: en-US
In-Reply-To: <AS4PR07MB8825D8C909770C48999FCE3489C62@AS4PR07MB8825.eurprd07.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms000500050905040007060108"
X-ClientProxiedBy: MSX-L422.msx.ad.zih.tu-dresden.de (172.26.34.142) To msx-t422.msx.ad.zih.tu-dresden.de (172.26.35.139)
X-TUD-Virus-Scanned: mailout3.zih.tu-dresden.de
Message-ID-Hash: OGY5F3RWVH3562DEJUM5U3PINFCD33RG
X-Message-ID-Hash: OGY5F3RWVH3562DEJUM5U3PINFCD33RG
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-saag.ietf.org-0; header-match-saag.ietf.org-1; 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: [saag] Re: Government–Industry Dialogue Public Side Meeting at IETF 126 Vienna
List-Id: Security Area Advisory Group <saag.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/Hc0zZt6dXbBvdikPuNJsOYNoxKE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Owner: <mailto:saag-owner@ietf.org>
List-Post: <mailto:saag@ietf.org>
List-Subscribe: <mailto:saag-join@ietf.org>
List-Unsubscribe: <mailto:saag-leave@ietf.org>

Hi John,

Thanks for organizing this. It is great to have government and industry 
together.

However, could you please clarify whether you want to have "Public Side 
Meeting" or "Private Meeting" as mentioned in [0]? While I am 
interested, your current framing seems not to allow me to participate, 
as I am neither in government nor in industry.

The subject of email says "Public Side Meeting" but as formally stated 
on the official webpage of the side meetings [0]: (*emphasis* my own)

    [Public] Side meetings should be *open* and free to attend to *any
    registered* IETF participant.

So if you want to have Public Side Meeting, I don't think you can limit 
it to government and industry participants. Often government and 
industry participants do not have the time or skills to do the formal 
proofs. Mostly academic and research institute participants help in that 
perspective, and sometimes even find some subtle cases or useful 
assumptions, which may not be obvious while just looking at the 
protocol. I don't see a good reason to exclude such participants.


On the other hand, if you want to have Private Meeting, my understanding 
from [0] is that you would be welcome to limit it to whatever you want, 
but then I don't think you can use the Public Side Meeting rooms for that.


On 17.07.26 08:06, John Mattsson wrote:
> Post-Quantum Cryptography: Government–Industry Dialogue
>
> This side meeting will bring together government and industry 
> stakeholders to discuss [...]

In particular, I find the above scoping of participants problematic for 
Public Side Meeting. So please clarify.

Best,

-Usama


[0] https://www.ietf.org/meeting/side-meetings/