[CFRG] Re: pairing-friendly-curves-14: keep or drop the uncompressed point encoding? (issue #110)
Yumi Sakemi <sakemi-yumi@gmo-connect.jp> Tue, 06 October 2026 14:11 UTC
Received: from ss11.activegate-ss.jp (ss11.activegate-ss.jp [223.27.119.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 1BCAF4B for <cfrg@irtf.org>; Tue, 06 Oct 2026 14:11:33 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmo-connect.jp header.s=20250719200908 header.b=QCWRNfq6; dkim=pass header.d=gmo-connect.jp header.s=google header.b=NuXAfsRu; spf=pass (mx.ietf.org: domain of sakemi-yumi@chronusinc.jp designates 223.27.119.25 as permitted sender) smtp.mailfrom=sakemi-yumi@chronusinc.jp; dmarc=pass (policy=quarantine) header.from=gmo-connect.jp; arc=pass ("google.com:s=arc-20260327:i=1")
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmo-connect.jp; s=20250719200908; t=1791295894; bh=fJDlSnGARyERNsEf++BDUMN2hJKiWv8vDSK+lRaAf6A=; h=References:In-Reply-To:From:Date:Message-ID:Subject:To:Cc; b=QCWRNfq6wbgCOISNKmcz/x749RuxChbvpB4ZvBsWu7oGlsOfZilmmfv9st8M/pME0 ZgcoQieBIj6qNCTkua6I2Avpl31pREvyFa1tY8tb6ZZ77vvZjWQQ9tK6N7qII8D3wd eQw5tfsDJEWOnz5+H+fr7PpgbchWVhkcS/Fgt3SA=
Received: from mail.d.activegate-ss.jp (unknown [10.16.39.40]) (envelope sender: <sakemi-yumi@chronusinc.jp>) (not using TLS) by ss11.activegate-ss.jp (Active!gate) with ESMTP id GXKw27303B; Tue, 6 Oct 2026 23:10:49 +0900
Received: by mail-oi1-f199.google.com with SMTP id 5614622812f47-4a45b3f0bdfso4284132b6e.1; Tue, 06 Oct 2026 07:10:49 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1791295848; cv=none; d=google.com; s=arc-20260327; b=QXxVNhEBt+tO7r7VOhneDjKpGc0ZwaCxWkmT1LxRU8UFEe0U35lZ8Dajygw5bvA+1d eeOqTLpNSfsHlTkzHXL+GaLbWn2R6aYBaB2/PP8uBcvGvYxzU5W+VRw9uxRgqZ/mSP8O xPIS5l4qrAsJEUolSvGsOsEDcRIlCKgohzzTCVpHj6Iw+pq2uobzIvEBw13K9cx1VdUX VKwbtgAeUQCRd0bqiovgjyJOY7Ezp439daU4kZVT9TVgc/L/jyEKfoWsyqgwJy6jiDUv 5hTjI3mAJZmDHeQhD6fpS/NCKM6Djsug23l0xqZvAfZsfNR4d4ql1Q2rtymh6eht4t2r sBJw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:dkim-signature; bh=fJDlSnGARyERNsEf++BDUMN2hJKiWv8vDSK+lRaAf6A=; fh=bwaZQvvWZXCqJVP/pPEuSCIAk/rY4+4Z9yIZvNrn8d0=; b=pTj/IDmmEMkoKbVjexL9f7+cjgTW95/arIan0cObulP5IyBNpTUM07ZRvfhoVXtnp/ wCxKk8ADN0YBECf4rNmE/9Jr1x8loJpLQhjtjeOJQUsdHJVVslijlcdHecZTy2Z23i32 kfSLUV6VAC1jjR/OggiHqKV8/Tl0Fo5yWoKomyBlXkXtt2qHvtLxtkGWJin6jnh88AAm HbJjjb6wbKRmOx5/MzSxKFtaRqrmOOtKSLCCUPouw3e6Qnrgj/bLggDH3dtRxg3S905x oGvGPx/PHS9O+HSMiIHVuo+ODayVgFFgTZ/hx9jKMViJD2ge8LIxsXtnIp+s7RMskgT1 cz+Q==; darn=irtf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmo-connect.jp; s=google; t=1791295848; x=1791900648; darn=irtf.org; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=fJDlSnGARyERNsEf++BDUMN2hJKiWv8vDSK+lRaAf6A=; b=NuXAfsRuc/a+RlslalZXpzm4WPXh916svObhxkVvrmVhZIdTkX5CSEhXdD+6+c+oNJ 6UpDxSpBk3M9tH3P7ibbPbzB916xZKPT2WPvCduZLrC9KTk9tb4N7rwH3CsR64yESw2B gmtQWVP0JCDlLSKTDAGocinAh2Y1NoYo54tqC7IKsW99OudaPpxz+J+tvytAET6s6Jbf gu76Iv9coQaFaiPHpiNCD1R7uklzPWPEN1Uswsia01ECjDJzIN5ihei0V3L/VeSA//Nm WaW1v1ZR+BIk4eMuQbZdpY/wXRM0vq+rVu7AQIYlBGMDJvW9HnVa8tjnHtYU1hgSSOe8 p9iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1791295848; x=1791900648; h=content-type:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to:content-type; bh=fJDlSnGARyERNsEf++BDUMN2hJKiWv8vDSK+lRaAf6A=; b=i8BAeK3nKO4DxjMC2aXq4Ekdmsfvg66Os/2yaCobdqlmZ1/COIjemIotnx3brGyWtX e8/22erU9BpMZuWymBGntEZ+SkV0SuB9ZTKtSD89aHR5PtreefYJydKghuMazXeL6J4X pVlk/UTXfEcv9OV47VEz6M4lYmRpV3N6TqAKkY04qxkdrNhUy0/ZV8aPkduqsSucKwou 1tUjLVr2e3LwwlDAhkdRDHS+1qzBtNqpSCTIMDIbg6xTT1o7KIh0S54np9JOVlpJMzXC Iqrnxu4ei2LSjgoyQ1wKDQpE1OJXojIMdCG0gOEEYNa4pD7AHuRNNk0gMofoChn3gIZb k4mg==
X-Gm-Message-State: AFuF++mAqZkjOKU0WsUYztomSKzg+ukw2oPOo+P+BAObfNnfMPnHaile q57Cd+SOqLACakpLwFm2ci1maC+1P9hXUIWtKRJHw3zTgqUF0JcC8kIlPztW91ZbHDI3xvGQPzp gp6Z4UC0vzUg12JIO7CIR7rT46j9DXNzze2wcf19GIU8fuMgf47txLAxL6qbLKNkIuwKo3QyPP+ OAuj7MFkEZPcZoAl1t28KeQ5nRGTR/Qz75S7BbjU6d3XBBBpY1zz5cS3Co
X-Gm-Gg: AYBFou3AFWVM9ZJ+8cX4xRn+AzjI0H8UV/xvU0U6sI3Rd3koSQDV+Y0MDYZrsv3hlnt QkScYAMDY20PAWSv86tpyVJqNWxsmY91L9lJUmXRboI+81r2HoBl3aAVNKEVx3FXmW+PgYRdvjF sZ3fyNb487MStfg3hA8NPmQA0V7M5yRXukOjMkyS5+M226T0rXdzAaUA3XLX8QXyxpSqAbrW5o
X-Received: by 2002:a05:6808:4f50:b0:4fb:a7f3:4211 with SMTP id 5614622812f47-4fba7f35585mr921103b6e.58.1791295847554; Tue, 06 Oct 2026 07:10:47 -0700 (PDT)
X-Received: by 2002:a05:6808:4f50:b0:4fb:a7f3:4211 with SMTP id 5614622812f47-4fba7f35585mr921056b6e.58.1791295846912; Tue, 06 Oct 2026 07:10:46 -0700 (PDT)
MIME-Version: 1.0
References: <CAOjisRxQ_Vs+3FDwSkM+NdpEH6zZ7g0FpAjyqi3yvEZBJe3rLA@mail.gmail.com> <CAPC=aNXW_sa4qLc0kkZJNzPi8zdc3nj4wfG=6Rg=zerWjJWD_Q@mail.gmail.com>
In-Reply-To: <CAPC=aNXW_sa4qLc0kkZJNzPi8zdc3nj4wfG=6Rg=zerWjJWD_Q@mail.gmail.com>
From: Yumi Sakemi <sakemi-yumi@gmo-connect.jp>
Date: Tue, 06 Oct 2026 23:10:36 +0900
X-Gm-Features: AclHuK9_7yauKs02gYaslP9qQzaZp3YDTxOHwCZzyS9uECL-7fyJSKTvQ-CEojI
Message-ID: <CANZ5RKW8_Q=g4F-nMbLXx_nj_HU1cRkZggg3iEAbM25auycUEw@mail.gmail.com>
To: cfrg@irtf.org
Content-Type: multipart/alternative; boundary="000000000000a4aa37065d2c90a5"
X-Spamd-Bar: ----
Message-ID-Hash: 3QVFNA6WSTMROWF2L3HZWOHPJUQUWUMV
X-Message-ID-Hash: 3QVFNA6WSTMROWF2L3HZWOHPJUQUWUMV
X-MailFrom: sakemi-yumi@chronusinc.jp
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-cfrg.irtf.org-0; header-match-cfrg.irtf.org-1; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: cfrg-chairs@ietf.org, draft-irtf-cfrg-pairing-friendly-curves@ietf.org
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [CFRG] Re: pairing-friendly-curves-14: keep or drop the uncompressed point encoding? (issue #110)
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/5lk3mderGkCKUrkfjrbbSGAFevw>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Owner: <mailto:cfrg-owner@irtf.org>
List-Post: <mailto:cfrg@irtf.org>
List-Subscribe: <mailto:cfrg-join@irtf.org>
List-Unsubscribe: <mailto:cfrg-leave@irtf.org>
Hi all, Thank you, Nick, for raising this on the list, and thank you to Michele, Watson and Jack for your comments, and to Mike Scott for sharing his view on the Last Call thread. We take the concern seriously: when one point has two encodings, problems can arise wherever points are hashed or compared as bytes. We will follow this discussion closely, and once the direction is settled, we will do our best to make the draft support safe use. Hearing from protocol implementers about how they actually use these encodings, as Jack did for Zcash, is very helpful for improving the draft. This is an Informational document whose main purpose is to present pairing-friendly curve parameters, so it is not really in a position to place requirements on other documents. Rather than the authors deciding this alone, we would like to gather what protocol implementers need and reflect it in the draft. It would be especially helpful to hear which forms your protocol accepts, and whether it hashes or compares encoded points. Best regards, Yumi On Mon, Oct 05, 2026 01:50 PM, Jack Grigg <ietf@jackgrigg.com> wrote: > On Mon, Oct 5, 2026 at 2:10 AM Nick Sullivan <nicholas.sullivan@gmail.com> > wrote: > >> The question: should the document keep both the compressed and >> uncompressed forms, or drop the uncompressed one? >> >> If you have a view, especially if you know of a deployment that relies on >> the uncompressed form, please reply on the list as part of the Last Call, >> which ends Friday, October 16. >> > > Quoting my email from December [0]: > > > We do use the uncompressed encoding when storing the verification keys > for > > the Sapling Spend and Output circuits (as an optimisation to avoid > > additional work when loading them from disk, and because we hash-pin > these > > static files), but the points at infinity never occur proofs, and for > > proofs encoded in transactions (i.e. on the wire) we only use compressed > > points. > > So the uncompressed encoding of BLS12-381 has been deployed in > production since October 2018 for the Zcash Sapling parameters (hosted at > various locations around the internet, such as the wagyu-zcash-parameters > Rust crate [1]), and likely in every other ecosystem that built on (forks > of) the bellman crate. However, in Zcash at least we don't "rely" on the > uncompressed form other than as a performance optimisation (the in-band > protocol uses the compressed encoding; we basically follow the Section > 5.6.1 guidance already, if you don't count "downloading the fixed public > parameters once" as "transmitting"). It would certainly be inconvenient if > we needed to re-deploy the Sapling parameters in compressed encoding, but > we can just Not Do That, no matter what the IETF says 🙂 > > I am definitely in favour of only supporting compressed encodings in-band > for protocols, for the reason Michele outlines. If it's easier to ensure > this in IETF protocols by removing uncompressed forms from the draft (and > keeping their performance-related use off-books) then I'm fine with > dropping uncompressed, but I'd say this mainly comes down to what the draft > requires of implementers for equality checks. If a conforming > implementation of the draft is permitted to in any way compare points > without first parsing them, then dropping uncompressed seems necessary to > ensure correctness. > > Cheers, > Jack > > [0] > https://mailarchive.ietf.org/arch/msg/cfrg/-KRy4O7QNfDLklD7wbITxtQ3PA0/ > [1] https://crates.io/crates/wagyu-zcash-parameters > > > >> >> Thanks, >> Nick, for the CFRG chairs >> _______________________________________________ >> 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 >
- [CFRG] pairing-friendly-curves-14: keep or drop t… Nick Sullivan
- [CFRG] Re: pairing-friendly-curves-14: keep or dr… Jack Grigg
- [CFRG] Re: pairing-friendly-curves-14: keep or dr… Yumi Sakemi