[CFRG] pairing-friendly-curves-14: keep or drop the uncompressed point encoding? (issue #110)

Nick Sullivan <nicholas.sullivan@gmail.com> Mon, 05 October 2026 01:09 UTC

Received: from mail-yx2-x2a.google.com (mail-yx2-x2a.google.com [IPv6:2607:f8b0:4864:41::2a]) (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 4A36E4B for <cfrg@irtf.org>; Mon, 05 Oct 2026 01:09:16 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=gmail.com header.s=20251104 header.b=mghpBtaU; spf=pass (mx.ietf.org: domain of nicholas.sullivan@gmail.com designates 2607:f8b0:4864:41::2a as permitted sender) smtp.mailfrom=nicholas.sullivan@gmail.com; dmarc=pass (policy=none) header.from=gmail.com; arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-yx2-x2a.google.com with SMTP id 00721157ae682-8ac47074ae1so6915637b3.2 for <cfrg@irtf.org>; Sun, 04 Oct 2026 18:09:16 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1791162550; cv=none; d=google.com; s=arc-20260327; b=IsZJxR+m+0TWHEVyx1NL85+pBH3JaRaKqimJL73dI5VYRrgCKxM+Tk21NOd5rw71yY ALaA61IvqJahK9784x/ZBaaaQrP2emSaP+Y/50wmCR19oc8DmFbGnJSt1Ziv7B8MhGSF 9cKKayeLQPEfDGTNUKILXXLrsVkJt0cwU062pjJbAs0W8cVfPE4BQ0+wAwsl5FY7121B 26y+dLJQ2ULX8ZlSfYcT6VVPYT//tQOsKktoWmmW+dANf5wmLmoZxYeqDShMqMP6buwG Y0Mpn97zo4h1mwo7YGxQTubXb1tIdI7sFKUvFyfG7aROfb3G0sFzHlzA9xm8jf85lZl1 huqw==
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:mime-version:dkim-signature; bh=68vPN3jNehR+xa5VvxLWuV9crL3hMvR4TmPE674lqW0=; fh=bwaZQvvWZXCqJVP/pPEuSCIAk/rY4+4Z9yIZvNrn8d0=; b=DPaEeqh4noG3xjevgGF+pAA+H8pyaco5llaLsGTNxhY1etP6i8BL95gcfNqu+jDq4d r+dFEFAnAo4f7MF3nev0zLCMbUjjrk0dQ3UYh/nOmPI71HTraV/MlP2F6KfvAF+F0wx0 QWfpRFGXbMrvHtCbAsJ1l3xogXCoQiqyxp2/lYaaKAxFnk4ExDjRGd51a87Zwd6FW70y S7v2I+BNCfDKEIswIfMtfBSh6tS/fP1ctdGevfnS0/Ia16TbFTnOg6FD4HaMvWbA09cA sBYH1+0Lva/PgEmmtnus5HVieHFp5bGprvKHbqcqygajlEMHHIIc9ZxCGVZuoWF7hftz 0TPg==; darn=irtf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1791162550; x=1791767350; darn=irtf.org; h=content-type:cc:to:subject:message-id:date:from:mime-version:from :to:cc:subject:date:message-id:reply-to:content-type; bh=68vPN3jNehR+xa5VvxLWuV9crL3hMvR4TmPE674lqW0=; b=mghpBtaUYRsqUmZCt5r2jJdNIMkqCBiUShiPPQDOXnzNnFfPG6MNSOF1hDcnmYsdN5 Yc/KB7R9JKIA5DLOjieLbrWNYuI4FqrdahZVlburm+lPjSv+OhHJoiNk43fMHEdLqzav e1UB+okz0AEOdSIbe/Ori16/cLZSyV4UZVRajh8weRbe9nMmKNz80CgOjRTbYZHVb7/w yczVjOtH7GzfHxtlzvIkmV5pt8m0AXYrPxxigCNmafC9IoWqujbVN6XffL6LsbXixS0L xwA0gXO1tqtFevoO/2EEL133SzxGHE9AXDtxEkENl0Z1zl/tXC3Ezq+/ePk6a5FiWozr FRRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1791162550; x=1791767350; h=content-type:cc:to:subject:message-id:date:from:mime-version :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to:content-type; bh=68vPN3jNehR+xa5VvxLWuV9crL3hMvR4TmPE674lqW0=; b=coIeFmUFup1r0RHk/6sV/Cx3ZGZwI9KWvJPjh4AkpvNrLcB69a6Mbwl/yQt959Y1DL HJKNZ5r5SGXtysD6h1Hcnb2YoIo3nyZKIHBJu0665f/gQEncmdfIkIiYTZ0eDo8KJLWD MHcTVOY+mtvFR8aoL2CL0ZtonGVT51c/eIU+M5htuhUO10jnfcQf3eznUVSr8zBIbw94 3fvH4Z4y/J6msBNfQ/v4Q97Zq2NMESlKIBee+G4bAK9DTSXRjIRjuRMJxWtQQ/jIYMhR nNzojgD6A5utSd9DcmlrzjIlmS/mgj6dOhrs+GQk67zyotdNNO29fOknHBJbdAfpjj3q Z4Kw==
X-Gm-Message-State: AFq9FYIPRsY53JvRgPUDdf48xuuRrZNvkp+nUPkoofBfls/qqKntJd2M 6gy0ADC+JTTVK34FN0Y3vuApZNuYbUOUzN6SGNYn/gaxqBJ6glHViVk0wuRF7z8O3hGS4zCux0O te+iEmMpP7vyJYwDWZ8oF2XeC93Pe7U9MdKDv
X-Gm-Gg: AYBFou13LKkAGTXP7YopzfWGX52yobwHZTNVTit6L1hwiu0EYw5H0RXHWLvW2iXc6fk JGSFYA4YHcuR0TtgWFPDrJdHuHePdlI8+UAJ72LBHBxsFJdTOcuNHRClQ8OuuIlsU+IJ9Jnzycp 6MDz5FQhTIZ4QrAqsvXopIIqBshE2lNySm6UAGMsNgqOCqKVG1qPJoOKe8YPlzC1WzrOIeUFkQT H40HKWBVkizcFdZohkvBjzyGi+NV9rhKAEIkEljH8wV8jejn1k3puo9XOcAm0y4Hch6aCwkcbgk juxCPVxbRyfatEbYA3XVI0g5jkfjHdLl2cyKOkAwJbVmrBGhWPeG4KQyZg0derCjNKVIvDHOiBe sDbUaQSr7KKd53zDV1ObDbdHXiywLLyynXtL4hW0fAXIFo7WG3EwbXIaMApadTZVMoqU7tQXCTt wHXuKejgx2WWQPtg==
X-Received: by 2002:a05:690c:47c4:b0:884:c83d:d182 with SMTP id 00721157ae682-8ae33de4fbfmr33271907b3.0.1791162549614; Sun, 04 Oct 2026 18:09:09 -0700 (PDT)
MIME-Version: 1.0
From: Nick Sullivan <nicholas.sullivan@gmail.com>
Date: Mon, 05 Oct 2026 10:08:57 +0900
X-Gm-Features: AclHuK_VFXVghzyNQgou1_hAcsCKT21acPuDFwa6vs93B4KgXaThb7piZdshKjU
Message-ID: <CAOjisRxQ_Vs+3FDwSkM+NdpEH6zZ7g0FpAjyqi3yvEZBJe3rLA@mail.gmail.com>
To: cfrg@irtf.org
Content-Type: multipart/alternative; boundary="000000000000813fa8065d0d87ff"
X-Spamd-Bar: ----
Message-ID-Hash: RUJCAIUJRF2V5YDJHRHU5JAI2QO5S2NT
X-Message-ID-Hash: RUJCAIUJRF2V5YDJHRHU5JAI2QO5S2NT
X-MailFrom: nicholas.sullivan@gmail.com
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] 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/dfx2zm4SNcs9uWZAUrLrJTNnefI>
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>

Dear CFRG,

One open question on draft-irtf-cfrg-pairing-friendly-curves-14 during Last
Call. On September 11, Michele Orrù asked whether the uncompressed point
encoding could be dropped, so that each point has a single encoding. His
concern is that two valid encodings of the same point let someone re-encode
a signature or proof and present it as new. Watson Ladd replied that this
depends on how a protocol compares values, and that a single encoding helps
but isn't strictly necessary. The request is tracked as issue #110 in the
draft's GitHub repository.

The question: should the document keep both the compressed and uncompressed
forms, or drop the uncompressed one?

For context, the same request came up last year and was tracked in #74,
which was closed on September 2 with both forms kept. On October 1, Michele
wrote that "canonical encoding would simplify things for downstream
protocols, but it doesn't block us." Section 5.6.1 of -14 currently
recommends the compressed form for transmitted values and says a protocol
should state which forms it accepts.

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.

Thanks,
Nick, for the CFRG chairs