[CFRG] Re: RG Last Call on draft-irtf-cfrg-pairing-friendly-curves-14
Michael Scott <mike.scott@miracl.com> Tue, 06 October 2026 11:13 UTC
Received: from mail-yx1-xb131.google.com (mail-yx1-xb131.google.com [IPv6:2607:f8b0:4864:20::b131]) (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 45D3342 for <cfrg@irtf.org>; Tue, 06 Oct 2026 11:13:27 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=miracl.com header.s=google header.b=QeW2Q8+d; spf=pass (mx.ietf.org: domain of mike.scott@miracl.com designates 2607:f8b0:4864:20::b131 as permitted sender) smtp.mailfrom=mike.scott@miracl.com; dmarc=pass (policy=reject) header.from=miracl.com; arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-yx1-xb131.google.com with SMTP id 956f58d0204a3-6774639a8a4so2464482d50.0 for <cfrg@irtf.org>; Tue, 06 Oct 2026 04:13:27 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1791285200; cv=none; d=google.com; s=arc-20260327; b=CVq6LEieQFeSESs34v7UUcdz76Rf8I4FnvaYpX00/6JAgmBdzzxwqIiJz8GvvtrHM/ zJjbHynn8+VQmC4saTaXJn5kKBBoIJwbd/gtFyrDavEk+/b+1BmQOPNZ5RTBZfPnyBES CQK+i2FbTVXflC62AXwT89IVZcWUn8u4/Sz0WBkeqttbTeM47LHgMzbjoJXC2w7wpX2x dWOkkTJVuigW4jghtnDewlX4w7vI7NWtFrRPfSNJSUBhWF6AjMTgYidKRR2VqZFO830V XgUF7GtUCEMocEq4C29I/xyf++oFB2u5IN96/abylQ7QZh6NxYnZprXaMKCN6lLdrsVF ovfQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20260327; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=O01PzwrKlcegva3Zdv1XibLjduo+wrLmSmEwwTcu0z8=; fh=I9lEgVqUbbytRRgi/jCy6ZkITtajY28AfrFmE7Zgu5s=; b=fLI1S4adcC2gtpp0MO5QY5Z2jerDiczG4IcgMQecg7CsJTI8ltAN4Vm2FfJzoUnqQF nUdw1Z1wTTcm943kiAQ8uv5agLjMUO2fhl7dbiuF8PAdNLcqIBFzsKzXB8TDmBVMADg7 bx4nz7Gqk4PLMNNJxChLVbx0aUz6UD2mCGXt9MZ+aUihLD8bZqf3hcOLpJNOv2V3W95I XvRz++VBnIV7kTIRwOaS8LO2yBZCY5bN0891EL6QJ8SkbNuIByne5whqsHozVfJU5KL3 8fhdReIM1tYRrHWr5AYsDUy7HsFldUvuzFyYu1ddBLYbL0GfP+0OUskG+lFtRhn35Vns nulQ==; darn=irtf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miracl.com; s=google; t=1791285200; x=1791890000; darn=irtf.org; h=content-type:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to :content-type; bh=O01PzwrKlcegva3Zdv1XibLjduo+wrLmSmEwwTcu0z8=; b=QeW2Q8+dWU/zPQIaMXTT0FzDY18shzgEsSjSACgmENsZQfgfzPEd4OalFrf9oKekBi wtyE2ajQd7mrCV9v59dFw0gVXTNYKtGsVo0dltV4zmC7SWvqQeSrPEPDWsvdwtPK25A6 4cFYXcl2lhiZ+GNPikt12kgds/xmArJKEeLFxTiCET5fp3hI+p8WEiO5X3Y2fPjwGFt/ F6sWZgJg71chnPBdiayIci0ElRqz7HQetTg28efCsJOxrqE1s9irjrZxRas3kMjT+dcz t+KiVW0mF/YPsfugrrmoBu4CJQYpsVHOA7MgbsRwJxx70Z2qZZnkfF2lIJc4cOWwALq7 vlWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1791285200; x=1791890000; h=content-type: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=O01PzwrKlcegva3Zdv1XibLjduo+wrLmSmEwwTcu0z8=; b=rwoL1bk1X8dyMzrbXoLcfnTlthKAWys6SFKIvoqJZMv5PWMqHNfirhHN6R9rYZNrP3 sHthoEjFGiA3Vt5PJlAJCnK0s4ofpXh5jSdh2QfQbN0wU2jI60amSV4L+LQ46qIfKk5/ Mn5g0X2bgOKcOk/73EMYNGwwwfVXnXW/Nq+ZXqmFNisi7vH/L365286BwjUh1hPXCFSZ 7xegYGtA0j84Qzb3OTL/ltI6tzVyO10jE7/GjLUEtmdxbNfRcnhSPZQX12xnLiTqXbk5 k6VkKndGYOh8tK4xFn8EHvVSHl1DcreRq96pFexnIVpvsp9Plq/Kr/B0J5TR/mOg3qs6 OTGQ==
X-Gm-Message-State: AFq9FYJcv7WMBmvuipj6ovzn8O+zwweuFkJcOwswnHZOpZffZ2N64/E/ /GMzPD14Ye5OOCeHifiQiU3ZKEgBBoSP3ZvVomiL8SDmR53RtNzJFrDTf4DW3tAcbt5x1U0Fk80 DdKJnjipTrrxcFU8xeg6oRfwCbS/BxUPzBlib4VqIOp/uCLnQE84+LOkVNw==
X-Gm-Gg: AYBFou3WxfFYGck42z3BreQxlgctrWw70Qs9JZR08HkA6a9pRayIdyQMDbZb9EjpbrJ hWkTc0fP8+LZvYN6aG4IFUGOblRKfZZUFHuYTL31+gnXLfoReOUevbcgXD3bMSBo2+CiN9aVnKE /m5vKz1smgdQl1jsGENVzcyNap3JpOzoQXoEz8OKEHYjBU6dQIpyQQKTrnhQOQW7ZayCb89mOQl oCTPW7NfhgiABcOyETsl1WPTgk67feA4862GFrGOn4i2fv19U1ul4o6Ijrju5FcRB3UV66ZXdQL YEDpuwrsiQDEcXb852VytOEZatZZdNQGkMRBWON8lPX5eFETH0GGFdZPJ9UKaD4e2itmq4qWsjI qo4fLUpB3vYNCJRUWZHLUhp2h29mfAGNcRG4A2I7JQy3UHQxy9B+gjQ==
X-Received: by 2002:a05:690e:1444:b0:677:bb39:4c0d with SMTP id 956f58d0204a3-677bd33819bmr4020688d50.39.1791285200396; Tue, 06 Oct 2026 04:13:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAOjisRxC8dvj-qT7FzfzS-foCUqxMXXdsP95b4TXY-j+M2Df5w@mail.gmail.com> <CANeU+ZARcw8ozzhevtBSP8gZuYZcJF76VkwxGCHFFWUDuR_8Rg@mail.gmail.com> <CANMnvkyT2VLxKaLxrmrKTFD1Funb6HNtJKTDQkoXxaX25bm6Jg@mail.gmail.com> <CANMnvkyiCA1BdR4eiBF-a0Vv-KHiWecG=K8pYiTFpNzwLxcq7A@mail.gmail.com> <CANMnvkyzBP7=QiAf5fpcy-3MAW67FrmPkbR9ZPEpg9MPsu13Fg@mail.gmail.com>
In-Reply-To: <CANMnvkyzBP7=QiAf5fpcy-3MAW67FrmPkbR9ZPEpg9MPsu13Fg@mail.gmail.com>
From: Michael Scott <mike.scott@miracl.com>
Date: Tue, 06 Oct 2026 12:13:09 +0100
X-Gm-Features: AclHuK_8r8tGm0ouZl1VS9WmGWJpe1bSreKLm-aWsj9_bD0B4b_hOa1ILjIFQZk
Message-ID: <CAEseHRpkBKMuH=_YCrJnYqP+z18EBee4YaJ6f5cqmGB3V=BGhQ@mail.gmail.com>
To: CFRG <cfrg@irtf.org>
Content-Type: multipart/alternative; boundary="0000000000000fb778065d2a16a0"
X-Spamd-Bar: -----
Message-ID-Hash: 6YEZ6ZGBU4MNFP6AJA7RAPFQPHMKISMC
X-Message-ID-Hash: 6YEZ6ZGBU4MNFP6AJA7RAPFQPHMKISMC
X-MailFrom: mike.scott@miracl.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
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairing-friendly-curves-14
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/ZW460RMOTTEWlz4PxhIqwvD_QYc>
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>
I did a review of the draft 14. I am aware that there are multiple constraints on possible changes that can be made at this stage imposed by already deployed implementations (an inevitable but unfortunate by-product of implementations getting ahead of standardisation) I think the use of t as the curve parameter in section 2 is a little unfortunate, as readers may confuse this with the trace of the Frobenius, commonly denoted by t. In the case of BLS curves the potential for confusion is greater, as t only differs by 1 from the trace. Maybe use u instead of t. In the paragraph summarising attacks on pairing based cryptography, perhaps pairing inversion should be mentioned (https://eprint.iacr.org/2007/256.pdf) I agree with others that it might be simpler to just support a compressed format for serialisation. As it stands the situation for BN462 is rather unsatisfactory - so maybe just mandate an extra byte for the metadata bits, and remove section 5.5 Given that compressed representation is likely to be more popular, maybe pointers to faster methods for calculating square roots in extension fields might be appropriate - see section 6 of https://eprint.iacr.org/2020/1497.pdf Overall I think the draft proposal is in good shape and ready to proceed to the next stage, with or without addressing these points. Mike Scott On Sat, Oct 3, 2026 at 8:13 AM Emil Lundberg <emil= 40yubico.com@dmarc.ietf.org> wrote: > (Re-sending this follow-up to my previous message, as I accidentally > replied only to one individual recipient instead of to the mail list) > > > ...and right after sending that, I realized the decomposition in comment > (2) is even easier to compute than I figured. I was thinking the optimal > base 2 decomposition is non-obvious because 6*t includes a factor 3, but I > now realized you can just write it as 6t + 2 = (2^2 + 2^1)t + 2^1 and the > rest follows immediately from the decomposition of t (and has one term less > than the one I gave in Python!). > > So if you'd like to make a change to address comment (2), it might suffice > to just add a small hint like the above to section A.1 > <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-optimal-ate-pairings-over-b>. > For example, perhaps change > "Let c = 6 * t + 2 for a parameter t [...]" > to: > "Let c = 6 * t + 2 = (2^2 + 2) * t + 2 for a parameter t [...]" > which should make it obvious enough for the reader to figure out how to > derive the decomposition. > > Again, this is non-essential and the document is complete enough without > it. It may be fair to consider this elementary enough to expect readers of > a document at this level to figure this out without such a hint. Either > way, thank you for your consideration. > > Emil Lundberg > Staff Engineer | Yubico <http://www.yubico.com/> > > Den fre 2 okt. 2026 kl 23:15 skrev Emil Lundberg <emil@yubico.com>: >> >>> I have reviewed -14 and am happy to report that with the clarifications >>> to the pairing computation and test vector representations, I have now >>> successfully reproduced the pairing test vectors of all three curves >>> (BLS12-381, BN462 and BLS48-581) in my from-scratch implementation! Thank >>> you for these clarifications, they make the document much easier to >>> interpret correctly. >>> >>> With that I can confirm that in my experience, draft -14 is clear and >>> fairly straightforwardly implementable (once one tracks down and fixes all >>> of one's implementation bugs...). I agree it is fit to publish in its >>> current state. >>> >>> I do have a few more suggestions for possible improvements, though. >>> These are all non-essential, but they would (in my opinion) further >>> strengthen the draft with some yet improved clarity: >>> >>> 1. I had some difficulty reproducing the BN462 pairing, but finally got >>> it working after I noticed that I had missed the notice in the Appendix >>> A >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-computing-the-optimal-ate-p> >>> introduction that pi(p, Q) also needs to operate on Q in untwisted form. >>> Since the pseudocode uses pi only in Section A.1 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-optimal-ate-pairings-over-b>, >>> but not in A.2 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-optimal-ate-pairings-over-ba>, >>> it may be worth considering moving the paragraph about the Frobenius >>> endomorphism ("The computation of the optimal ate pairing uses the p-power >>> Frobenius endomorphism pi [...], pi(p, Q) = (x^p, y^p).") into section A.1 >>> to keep it closer to where it's most relevant (within the scope of this >>> document). >>> >>> 2. I also noted that the pairing for BN curves needs a decomposition >>> of c = 6 * t + 2, which the reader needs to compute themself since one is >>> not stated explicitly - unlike BLS curves which use c = t, whose >>> decomposition is given in section 4. It may be worth considering stating the >>> decomposition of c = 6 * t + 2 too, but it's not strictly necessary since >>> the stated constraints are enough to re-derive one. Here's what I came up >>> with (in Python): >>> >>> t = 2**114 + 2**101 - 2**14 - 1 >>> c = [0]*117 >>> c[2] = 1 >>> c[3] = -1 >>> c[15] = -1 >>> c[16] = -1 >>> c[102] = 1 >>> c[103] = 1 >>> c[115] = 1 >>> c[116] = 1 >>> assert sum(ci * (2**i) for i, ci in enumerate(c)) == 6 * t + 2 >>> >>> 3. It may be worth adding a reference back to section 2.4 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-barreto-lynn-scott-curves> in >>> sections 4.2.1 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-bls-curves-for-the-128-bit-> and >>> 4.3 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-for-256-bit-security> after >>> the definition of t, like section 4.2.2 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-bn-curves-for-the-128-bit-s> >>> already has after its definition of t. I initially made the mistake of >>> assuming the equations for p and r were the same for BLS48 as for BLS12, >>> and it took a while to notice my mistake. A handy link back to section 2.4 >>> would have prevented this mistake. >>> >>> 4. I was a bit surprised to see Table 1 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-serialization-and-validatio> >>> and the text around it going into such detail about the origins of the >>> serializations. My apologies if my earlier review comments came across as >>> overly concerned with these details, if that's what motivated this. I think >>> that Table 1 and its preceding paragraph ("Not all of what follows >>> originates with this document. [...]") are not necessary and could be >>> deleted; I think the first paragraph in section 5 >>> <https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html#name-serialization-and-validatio> is >>> enough of a summary. >>> >>> Like I said these issues are not essential, so you're welcome to ignore >>> these comments if you prefer to keep -14 as the final draft (or indeed if >>> you simply disagree with them). Thank you very much for your work on this, >>> and for your patience with my and others' review comments. >>> >>> Emil Lundberg >>> >>> Staff Engineer | Yubico <http://www.yubico.com/> >>> >>> >>> >>> >>> Den fre 2 okt. 2026 kl 00:54 skrev StJohns, Michael < >>> msj@nthpermutation.com>: >>> >>>> Two small items - can be resolved in the editing pass, >>>> >>>> 1) missing a url reference for NIST sp800-57 part 1 - also NIST isn’t a >>>> great reference tag here. >>>> >>>> 2) capitalization of “optimal ate pairing” - AFAICT this is a name for >>>> a particular pairing model and should be capitalized as such throughout - >>>> Optimal Ate Pairing or abbreviated throughout. Or perhaps optimal Ate >>>> pairing? Since [ver09] is behind a paywall, I can’t confirm this. >>>> >>>> Otherwise looks good from a general readability perspective >>>> >>>> Mike >>>> >>>> On Fri, Sep 25, 2026 at 10:31 Nick Sullivan < >>>> nicholas.sullivan@gmail.com> wrote: >>>> >>>>> Dear CFRG, >>>>> >>>>> This message starts a three-week RG Last Call on >>>>> draft-irtf-cfrg-pairing-friendly-curves-14. The last call ends on Friday >>>>> October 16, 2026: >>>>> >>>>> Pairing-Friendly Curves >>>>> draft-irtf-cfrg-pairing-friendly-curves-14 >>>>> >>>>> https://www.ietf.org/archive/id/draft-irtf-cfrg-pairing-friendly-curves-14.html >>>>> >>>>> The document is intended as an Informational RFC. Please reply on-list >>>>> with your position: ready to publish as-is, ready with specific changes, or >>>>> not ready, together with the technical reasons. This feedback will help the >>>>> chairs judge whether the document is ready for IRSG review and publication. >>>>> >>>>> Some history: The document had an Expert Review by Chloe Martindale in >>>>> 2020. The authors resolved her comments in -05, and a first RG Last Call >>>>> ran on that revision. The curve parameters have not changed since then. >>>>> What has changed is implementer-facing: Section 5 now specifies >>>>> serialization normatively, Section 4 records the curve set and security >>>>> levels after the discussion on this list this spring, Appendix G records >>>>> the scope of the security estimate review, and the test vectors were >>>>> cross-checked against four independent implementations. Reviews from Frank >>>>> Denis, Emil Lundberg, Thomas Bellebaum and Michele Orrù shaped the recent >>>>> revisions, and every issue in the repository is closed. >>>>> >>>>> This last call is about whether the text is technically correct and >>>>> complete, so please ground any objection in a specific problem with the >>>>> document. Detailed comments are best filed as issues on the repository ( >>>>> https://github.com/cfrg/draft-irtf-cfrg-pairing-friendly-curves) >>>>> Positions belong here on the list. >>>>> >>>>> The chairs asked the Crypto Review Panel for a review of -14 in >>>>> September and no panel member was available. Given the 2020 Expert Review >>>>> and the unchanged parameters, we decided not to hold the document for a >>>>> second panel review. Reviews from anyone with the relevant background are >>>>> welcome during this last call. >>>>> >>>>> Thank you, >>>>> 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 mailing list -- cfrg@irtf.org > To unsubscribe send an email to cfrg-leave@irtf.org >
- [CFRG] RG Last Call on draft-irtf-cfrg-pairing-fr… Nick Sullivan
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Salz, Rich
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Brent Zundel
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Frank Denis
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… StJohns, Michael
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Emil Lundberg
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Yumi Sakemi
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Emil Lundberg
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Michael Scott
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Nick Sullivan
- [CFRG] Re: RG Last Call on draft-irtf-cfrg-pairin… Yumi Sakemi