Return-Path: X-Original-To: cfrg@mail2.ietf.org Delivered-To: cfrg@mail2.ietf.org Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C21A4AD6E01 for ; Thu, 13 Mar 2025 06:26:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -1.797 X-Spam-Level: X-Spam-Status: No, score=-1.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, TRACKER_ID=0.1] autolearn=no autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=ibiblio-org.20230601.gappssmtp.com 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 T0P917KBdwqc for ; Thu, 13 Mar 2025 06:26:37 -0700 (PDT) Received: from mail-yb1-xb35.google.com (mail-yb1-xb35.google.com [IPv6:2607:f8b0:4864:20::b35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0C6F6AD6DEB for ; Thu, 13 Mar 2025 06:26:32 -0700 (PDT) Received: by mail-yb1-xb35.google.com with SMTP id 3f1490d57ef6-e62d132a6a7so720769276.3 for ; Thu, 13 Mar 2025 06:26:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ibiblio-org.20230601.gappssmtp.com; s=20230601; t=1741872391; x=1742477191; darn=irtf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=rXdpYkh5f+jJCk3ic/jTL5dzC2I3ULnuomKA8f663WY=; b=hEBJC7kSz299ASlfNCFx8UElIHvm0z44YBHHnLeMbrTV04x65cLbxVckU469AmTVw0 sjOlYzsNRJ2lPzWBf/8yn2HzHE3ZIC7jWyPvVJ0wMQIONIgAUgyMgll/0jWJPk4Sqha8 82ZqPGmAF4zoGPcCDQNrfOxLT80fQQzfMtwGwaWBPzja45TyJi+bagCpGB3ZwZsx4u1w uJciWlqWQTyH4dK7OgmeAfDNVHimrnD+poAxpp7IoR/U6y19APRT9rSn/Kb2C7CSsU5m Qc07+jpK3RoujeLBGj4lhyihFnF4iXt8ZM7b7bEYVCeg4TXU50HhaK2hIzClUfsuwjWy qFIg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741872391; x=1742477191; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=rXdpYkh5f+jJCk3ic/jTL5dzC2I3ULnuomKA8f663WY=; b=g1Ju6U19g1rvf9l+l1zPdN9gUncep/CeQZdTEz4Pw3zvEpnYuzij3AgqbZZ9Kj5DKP bYrBxl2HvAJW8YaB7mB43xBPbus0ApPNxmMl9T+Sz8/G0yb/b5fZWdpTED1h3ez6Sd+f 0JtVyBilAcaXsuzjkWcvTNZ3EpGiqy6yq1T0mVVh29EizdAj2BHPdhIXmnRZuqGSALJs pVjxoPhlF0hNiu321ZA8R3AWeRtEVkq9ZUvuTZMp4GTN9Xc2AF2DeoCtcC4Ugpt+7Asb qjsGuDqn+7dSHVqHre7ZzQueCuS7aY+J4AZM1XFElgPD1IA/JgvEf04JavK0EswA02z2 bu7g== X-Forwarded-Encrypted: i=1; AJvYcCWC6EWPICZfQA4C0juS8JBrp8WfgxQ/xrzdNpak4eRcihIwWaFrj+KlISUECcQuGB/zylBu@irtf.org X-Gm-Message-State: AOJu0Yxi1JK9HTLSTBuSzyUY5TYAUAXeSgsBxh32Gu6smSrOFsiDXl3j XzcM4wotgJqovdbiyo+lryPGqewXrg3LE+ge96y9vuppbP9zC6Z6G+DxZK7CyIoomSg5B2WooJe p6Gt67sueH0b8lB3IqB8pZ0RfBFBElJWVIq8L X-Gm-Gg: ASbGncvXaMOOLFshxJyDgsAgVdIdx1uOjFVF5Rgcurk8BLDCbQzehleBtWytTjMHuqK qrjdqRapUoO1zxGWJXnVFrAAmkeXhkdgnykpUu/fd2mo//LDRt/wqiFtd30D7uc3FONVMt2D0yX pV7y3Aeyn/C8sYCW/skDa2zmXoXcg= X-Google-Smtp-Source: AGHT+IFyZFrCRl2mYC2trElDuXRUfgyt10Xlbx9HYKA3vB5J/XZpJrnLxWaG8/htjpnRG0TOsjT11lj2evaknBdAl90= X-Received: by 2002:a05:6902:72c:b0:e61:1c56:d65e with SMTP id 3f1490d57ef6-e63b5211638mr14869776276.39.1741872391221; Thu, 13 Mar 2025 06:26:31 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Harry Halpin Date: Thu, 13 Mar 2025 13:26:19 +0000 X-Gm-Features: AQ5f1JqW7IOVA7rt8oqpHXNrk_l4LdLZcwUBf11l_7GHFp49h8-MldpxEyg-lVg Message-ID: To: "Blumenthal, Uri - 0553 - MITLL" Content-Type: multipart/alternative; boundary="0000000000001f98a3063039455c" Message-ID-Hash: P36C3QD4VXJ2A54K76GR27AIQY7Z4R4F X-Message-ID-Hash: P36C3QD4VXJ2A54K76GR27AIQY7Z4R4F X-MailFrom: hhalpin@ibiblio.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-cfrg.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: John Mattsson , CFRG X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BCFRG=5D_Re=3A_=5BEXT=5D_Re=3A_NIST_PQC=3A_HQC_Announced_as_a_4t?= =?utf-8?q?h_Round_Selection?= List-Id: Crypto Forum Research Group Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000001f98a3063039455c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable We are also putting Classic McEliece into production in Nym. We have no plans to change to HQC and we would really appreciate a CFRG RFC for Classic McEliece. Yours, Harry On Thu 13 Mar 2025 at 1:11=E2=80=AFPM, Blumenthal, Uri - 0553 - MITLL < uri@ll.mit.edu> wrote: > Even when the burden of exchanging public keys can be alleviated by > pre-provisioning, the sheer size of those keys can make storage > requirements an unacceptable burden. Limiting the set of suitable use > cases. > =E2=80=94 > Regards, > Uri > > Secure Resilient Systems and Technologies > MIT Lincoln Laboratory > > On Mar 13, 2025, at 08:20, John Mattsson 40ericsson.com@dmarc.ietf.org> wrote: > > =EF=BB=BF > Neil Madden wrote: >+1 to this. It would be good to see a CFRG RFC for > Classic McEliece (or a hybrid using it). Yes, now that NIST will not > specify Classic McEliece, I think CRRG definitely should. While HQC is a > good backup algorithm for > ZjQcmQRYFpfptBannerStart > This Message Is From an External Sender > This message came from outside the Laboratory. > > ZjQcmQRYFpfptBannerEnd > > Neil Madden wrote: > >+1 to this. It would be good to see a CFRG RFC for Classic McEliece (or > a hybrid using it). > > > > Yes, now that NIST will not specify Classic McEliece, I think CRRG > definitely should. While HQC is a good backup algorithm for epheral key > exchange in TLS and IPsec, it is not a good algorithm for most use cases = of > static encapsulation key. Classic McEliece is performance vise often the > best choice for static encapsulation keys. > > > > John > _______________________________________________ > CFRG mailing list -- cfrg@irtf.org > To unsubscribe send an email to cfrg-leave@irtf.org > > _______________________________________________ > CFRG mailing list -- cfrg@irtf.org > To unsubscribe send an email to cfrg-leave@irtf.org > --0000000000001f98a3063039455c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We are also putting Classic McEliece into production in N= ym. We have no plans to change to HQC and we would really appreciate a CFRG= RFC for Classic McEliece.=C2=A0


=C2=A0 Yours,
= =C2=A0 =C2=A0 =C2=A0 Harry=C2=A0

On Thu 13 Mar 20= 25 at 1:11=E2=80=AFPM, Blumenthal, Uri - 0553 - MITLL <uri@ll.mit.edu> wrote:
=
Even when the burden of exchanging public keys can be all= eviated by pre-provisioning, the sheer size of those keys can make storage = requirements an unacceptable burden. Limiting the set of suitable use cases= .=C2=A0
=E2=80=94
Regards,
Uri

= Secure Resilient Systems and Technologies
MIT Lincoln Laboratory<= /div>

On Mar 13, 2025, = at 08:20, John Mattsson <john.mattsson=3D40ericsson.com@dmarc.ietf.org> w= rote:

= =EF=BB=BF
ZjQcmQRYFpfptBanne= rStart
This Message Is From an External Sender
This message came from outside the Laboratory.
=C2=A0
ZjQcmQRYFpfptBanne= rEnd

Neil Madden wrote:
>+1 to this. It would be good to see = a CFRG RFC for Classic McEliece (or a hybrid using it).

=C2=A0

Yes, now that NIST will not spe= cify Classic McEliece, I think CRRG definitely should. While HQC is a good = backup algorithm for epheral key exchange in TLS and IPsec, it is not a goo= d algorithm for most use cases of static encapsulation key. Classic McEliece is performance vise often the best cho= ice for static encapsulation keys.

=C2=A0

John

_______________________________________________
CFRG = mailing list -- cfrg@irt= f.org
To unsubscribe send an email to cfrg-leave@irtf.org
<= /div>
_______________________________________________
CFRG mailing list -- cfr= g@irtf.org
To unsubscribe send an email to cfrg-leave@irtf.org
--0000000000001f98a3063039455c--