Re: [CFRG] Classic McEliece

"D. J. Bernstein" <djb@cr.yp.to> Sun, 15 October 2023 14:28 UTC

Return-Path: <djb-dsn2-1406711340.7506@cr.yp.to>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F7BC14CE2E for <cfrg@ietfa.amsl.com>; Sun, 15 Oct 2023 07:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y2z_u6MKJwt1 for <cfrg@ietfa.amsl.com>; Sun, 15 Oct 2023 07:28:50 -0700 (PDT)
Received: from salsa.cs.uic.edu (salsa.cs.uic.edu [131.193.32.108]) by ietfa.amsl.com (Postfix) with SMTP id 9CA80C14CE29 for <cfrg@ietf.org>; Sun, 15 Oct 2023 07:28:50 -0700 (PDT)
Received: (qmail 11122 invoked by uid 1010); 15 Oct 2023 14:28:49 -0000
Received: from unknown (unknown) by unknown with QMTP; 15 Oct 2023 14:28:49 -0000
Received: (qmail 146764 invoked by uid 1000); 15 Oct 2023 14:28:25 -0000
Date: Sun, 15 Oct 2023 14:28:25 -0000
Message-ID: <20231015142825.146762.qmail@cr.yp.to>
From: "D. J. Bernstein" <djb@cr.yp.to>
To: cfrg@ietf.org
Mail-Followup-To: cfrg@irtf.org
In-Reply-To: <LO2P123MB4927E0632FF8C7D5C2292188BCD0A@LO2P123MB4927.GBRP123.PROD.OUTLOOK.COM>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/j-NQCbTyVeopiku0o0bqDbg4JWk>
Subject: Re: [CFRG] Classic McEliece
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Oct 2023 14:28:55 -0000

Peter C writes:
> Almost the entire content of draft-josefsson-mceliece is taken
> verbatim from the first working draft of ISO/IEC 18033-2/AMD2.

No.

1. The Classic McEliece team converted its public specs into ISO format
as a draft of a potential ISO McEliece standard, and released that to
the public in April 2023:

   https://classic.mceliece.org/iso-mceliece-20230419.pdf

Simon derived his public draft from this public document from the
Classic McEliece team.

2. ISO/IEC 18033-2/AMD2 WD1 is not a public document, and is not the
source of Simon's public draft.

Peter's publication of the fact that there's an almost perfect match
between WD1 and Simon's public draft appears to be in violation of the
ISO policy on communication of committee work (ISO publication 100382).
However, ISO policy _does_ allow publication of logistical information,
so I'm free to point out that WD1 was distributed by its editors to the
relevant working group, ISO/IEC SC27 WG2, on 30 August 2023.

Given the almost perfect match between WD1 and the earlier document
iso-mceliece-20230419.pdf, and given the almost perfect match between
Simon's document and iso-mceliece-20230419.pdf, it's not surprising to
observe an almost perfect match between Simon's document and WD1.
Selectively releasing this last bit of information, without even
mentioning the timestamps, is deceptive.

As a side note, CFRG has many people who have suffered through reviewing
different specs for the same cryptosystem; it shouldn't be hard for the
whole group to agree that having unified text is a good thing.

3. Regarding the broader notion that this text somehow belongs to ISO,
I'll quote the ISO/IEC Directives, Part 1, Consolidated ISO Supplement,
2022, Clause 2.13, "Copyright":

   In ISO and IEC, there is an understanding that original material
   contributed to become a part of an ISO, IEC or ISO/IEC publication
   can be copied and distributed within the ISO and/or IEC systems (as
   relevant) as part of the consensus building process, this being
   without prejudice to the rights of the original copyright owner to
   exploit the original text elsewhere.

So, whatever use ISO might decide to make of text contributed by the
Classic McEliece team, ISO doesn't have any sort of exclusivity over
that text.

---D. J. Bernstein (speaking for myself)