IETF Logo Mail Archive

[Seat] Re: Fwd: New Version Notification for draft-usama-seat-intra-vs-post-00.txt

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Fri, 16 January 2026 02:26 UTC

Return-Path: <muhammad_usama.sardar@tu-dresden.de>
X-Original-To: seat@mail2.ietf.org
Delivered-To: seat@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 50B54A85F633 for <seat@mail2.ietf.org>; Thu, 15 Jan 2026 18:26:11 -0800 (PST)
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, RCVD_IN_DNSWL_MED=-2.3, 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
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 S1Hal9k2nrx5 for <seat@mail2.ietf.org>; Thu, 15 Jan 2026 18:26:10 -0800 (PST)
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 5FD69A85F622 for <seat@ietf.org>; Thu, 15 Jan 2026 18:26:10 -0800 (PST)
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:CC:From:References:To :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=bYvF3bVU/BSjYxlWBPrFhCUyNUBlpvq94AF1VzHBkng=; b=RJStblx1TnHTbdDayMg8QXgq9W mIOvXrs5FvUKU9GtEsbx9OErigbXqkTYSylw/9uDlKqrOZQ1Wbm8O5eT2BVtkzBEaBAbM3DEnt6Y3 G7HeOqjEZiweHVMI17Ci3pbEYq14cQQJiVa64BJYAO/EW8e8UxZIe4SUkeXfA5e0IDJuah/2Y96zW 72vqjGsOYOHuDrmyv2Gb1k6eZ1iDv6tIjVRHnOJ0a6j2Ac8TVKssf+ctWoIVOPVPP6ng/0J9MkOUH rr688a3p4q+ccFXCfpAK9QPQHL1WjZtZuYPLXU/4MaTeUqlkKC9EebCpjV7/ROneYWsHfRC8m58rI DRrJno4A==;
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.94.2) (envelope-from <muhammad_usama.sardar@tu-dresden.de>) id 1vgZXN-004yOt-06; Fri, 16 Jan 2026 03:26:09 +0100
Received: from [10.12.5.228] (141.76.13.149) 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.35; Fri, 16 Jan 2026 03:25:56 +0100
Message-ID: <bd17ac4f-e5ab-4853-870b-f05bc37eb2d4@tu-dresden.de>
Date: Fri, 16 Jan 2026 03:25:55 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Ayoub Benaissa <ayoub.benaissa=40zama.ai@dmarc.ietf.org>
References: <CAD_oqtdC-aerstGEfJpLoPDexUZmihehSwQgQvFpdJ2tZmYuow@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CAD_oqtdC-aerstGEfJpLoPDexUZmihehSwQgQvFpdJ2tZmYuow@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms070405060709090507020303"
X-ClientProxiedBy: MSX-T414.msx.ad.zih.tu-dresden.de (172.26.35.134) 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: NSHFYIQO3N6K2MAXH7FUSWMCDVZBAACP
X-Message-ID-Hash: NSHFYIQO3N6K2MAXH7FUSWMCDVZBAACP
X-MailFrom: muhammad_usama.sardar@tu-dresden.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: seat@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Seat] Re: Fwd: New Version Notification for draft-usama-seat-intra-vs-post-00.txt
List-Id: "Secure Evidence and Attestation Transport (SEAT) WG" <seat.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/seat/V9VeQGsfqkRnFWGillSmHZggX0g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/seat>
List-Help: <mailto:seat-request@ietf.org?subject=help>
List-Owner: <mailto:seat-owner@ietf.org>
List-Post: <mailto:seat@ietf.org>
List-Subscribe: <mailto:seat-join@ietf.org>
List-Unsubscribe: <mailto:seat-leave@ietf.org>

Hi Ayoub,

On 15.01.26 16:59, Ayoub Benaissa wrote:
> From a practical perspective, I think a post-handshake implementation 
> makes more sense. We have been building an Attested TLS protocol for a 
> web-based application, and we had to do a post-handshake 
> implementation. Intra-handshake requires too much change. For example, 
> you have to reimplement or customize how Nginx (or other) servers 
> speak TLS. This would take months and more to have a standard 
> implementation that is somehow safe to use. It's different in a 
> post-handshake implementation where you can have a full working 
> example in a matter of weeks.

Could you possibly share more details?

Also, we are collecting use cases of attested TLS [0]. Would you be 
willing to share your use case and co-author the use cases draft [0], as 
in write goal, use case and requirement? Thanks.

-Usama

[0] 
https://tls-attestation.github.io/use-cases-and-properties/draft-mihalcea-seat-use-cases.html#section-3

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