IETF Logo Mail Archive

[TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3

Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de> Fri, 10 April 2026 17:55 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 95BFDD9C381C for <tls@mail2.ietf.org>; Fri, 10 Apr 2026 10:55:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1775843754; bh=aUq1Uk3QiWX9ThbrVVHkMqcJmK3exeCvn4KaLExbv5Q=; h=Date:Subject:To:CC:References:From:In-Reply-To; b=nDFh1WnqBfVkAmovMNjjIT1mEBd0Xn3CU1uCDVzbH2iBh5XfOKou6h4pAFBU71ccm 6mo0Lgga3GFwj7CthP3MxCaKGFOnbDPM57uDPqXffmFopPb72wIfAdcqZ8H6xz4STO lmaht8/Hs4DNVR+NFzTZtIT0Xkw36DU8l3sVRYK4=
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 OW0N4JEWXcN5 for <tls@mail2.ietf.org>; Fri, 10 Apr 2026 10:55:53 -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 69FC4D9C3521 for <tls@ietf.org>; Fri, 10 Apr 2026 10:53:38 -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:From:References:CC: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=Z+Eqp1ImUCykeNQDELrvBc2EGbB38VXW6QUt8WQbhHE=; b=bxEWWtOpyoEiffSpzS/OZia9+b 225SmOyD9QKkU7w3zG4La/CLhmDGcgawrQxUgf1GNA3U4ww1BOCZRPh6aa3/SUSWhXvOdBiHQGqSL x/n3AxW2Ag4vThP2Nl6x0ujKvjJ5ESDNymv0kuK4FLBLAiz9lS2tRg9bgJhQDoQwlWO0yihK0dhBO k0qe+RnAN/6T6DIdbm3unC/VoHFCqgFQV3z6ldqws99wv/fEnobDZ25YdJ0IVHIRjp+KqAGNwt14u w5bO/ysE5eMXqhE4gHEyDsAFwWZUdr9irTi/mV/L5/R/et7Bid1m41AuwGxwv6R8loGw0S5qoSS5b WWiY6zZA==;
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 1wBG2u-001giM-1j; Fri, 10 Apr 2026 19:53:37 +0200
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.37; Fri, 10 Apr 2026 19:53:31 +0200
Message-ID: <43fd169d-d280-40dd-9d2c-311040bed4ad@tu-dresden.de>
Date: Fri, 10 Apr 2026 19:53:30 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Eric Rescorla <ekr@rtfm.com>
References: <16CF0FDA-7263-461A-9F2B-D37DBEAF5DD9@sn3rd.com> <25c8d414-e4c8-455b-bd64-28132615ba75@cs.tcd.ie> <68f49a81-dd2c-4bea-896a-87da3e6aff68@tu-dresden.de> <CAMjbhoWwvfkfScpbf4-5PBzk__qb+6M4ZzAOba64kk9aXBba5g@mail.gmail.com> <d47a34ab-7fb9-4687-84aa-a5fa6bcf6a6c@tu-dresden.de> <CAMjbhoWBHmJnLx7wRG9iyurAHrSCExxO83G8PN=TnQUidp84SQ@mail.gmail.com> <3e539579-4107-41fc-80a5-824b24c275be@tu-dresden.de> <CABcZeBO59jwCA=vKiJ=QZaU8rPJxKv_WwFGOTot0jR+hpiFuLQ@mail.gmail.com>
Content-Language: en-US
From: Muhammad Usama Sardar <muhammad_usama.sardar@tu-dresden.de>
In-Reply-To: <CABcZeBO59jwCA=vKiJ=QZaU8rPJxKv_WwFGOTot0jR+hpiFuLQ@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-512"; boundary="------------ms040803000702030103090607"
X-ClientProxiedBy: MSX-L416.msx.ad.zih.tu-dresden.de (172.26.34.136) 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: JNSX3NDOEIELIB3NBXNNF3E3PELGHWWS
X-Message-ID-Hash: JNSX3NDOEIELIB3NBXNNF3E3PELGHWWS
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 List <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3
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/Z2Z7b7wEwvMa17EQhYchMR8ST08>
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>

On 10.04.26 19:31, Eric Rescorla wrote:

> On Fri, Apr 10, 2026 at 10:18 AM Muhammad Usama Sardar 
> <muhammad_usama.sardar@tu-dresden.de> wrote:
>
>     What does 'should not' in bold in FIPS documents translate to in
>     IETF BCP 14?
>
> See S 2.1 "Terms and Definitions" in FIPS 204.

Yes, I have read that, but my question is about the exact /translation/ 
to BCP 14. To be more explicit, what I am asking is whether their 
'should not' translates to our SHOULD NOT or MUST NOT?

Best regards,

-Usama

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