[CFRG] Re: RG Last Call on draft-irtf-cfrg-pairing-friendly-curves-14
Emil Lundberg <emil@yubico.com> Fri, 02 October 2026 21:16 UTC
Received: from mail-wm2-x10.google.com (mail-wm2-x10.google.com [IPv6:2a00:1450:4864:31::10]) (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 A883746 for <cfrg@irtf.org>; Fri, 02 Oct 2026 21:16:03 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=yubico.com header.s=google header.b=blApVo4l; spf=pass (mx.ietf.org: domain of emil@yubico.com designates 2a00:1450:4864:31::10 as permitted sender) smtp.mailfrom=emil@yubico.com; dmarc=pass (policy=reject) header.from=yubico.com; arc=pass ("google.com:s=arc-20260327:i=1")
Received: by mail-wm2-x10.google.com with SMTP id 5b1f17b1804b1-4a01ff8c098so1858545e9.3 for <cfrg@irtf.org>; Fri, 02 Oct 2026 14:16:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1790975762; cv=none; d=google.com; s=arc-20260327; b=iD1w6ZaWAYsj4BocJQ6ovczycxF2np41R2t1Kn/EMTEee2hYInwxxCPU9koO72kqY2 fwJ0LbA+nyU6CmKdWyh1QTxzoOSS1VotbQ0mNE0mkmDVjA+hUNP42A4PFVT9JRLz2TRw cjzCEgXgfaANNGfU74gilzFt5BdVL2rk4zTBXCx385iWcD8Y4V5N45CHKJLckWjnQfv0 2adLmggPJW1iUl4pL0dOi7oCYObJRAW2a+6QzhfrlIXEShnReZ1rJvXJSZf37KvFCtC8 BiG0JCQru/s5VqbivDIX6bYjQaEhQpRiKhhN90hI5EyBrdnbnLlb23V1XqMk9vTLY9xM qTJQ==
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=Lk0DjbkfbQ1TsD4Pxg+wHbekj2coW1eMfRfxJvjswtQ=; fh=ky1SF+GAk/nZT/L+5SEmD4y3e7yyBa149MrpEpQdQNo=; b=kXikTjBJ7D6DJFfOW/5RUO6u0koYntMGFmMB9qJCejn/2T10xgbfSCSg0kyLApS9KK AwzTVzCbllfoTm9PuXwOgXisK1Nr6vHqJPXd+kXDc958Y9oWcje8EPt/sCWY8TYkZH7R xUYYHNdzDd4lVVTXU1CDXzvS8h6K0Mu479MTogRtGT6w6GeXOH0bV/gs8PZ/ub4El5WL 7Sm7FyO/f7AMfvG3KsXBMWFvrp/VuuxIRhbI3gp3OqgsOMbTc/hbfWsMP2dE+neHFDF9 1OlePJ36IdEJFcnKws08DNJWFYNOHjzLlcFBVTkB8i24GYfRE5iL06C/84dtLYFf4YXG FfDA==; darn=irtf.org
ARC-Authentication-Results: i=1; mx.google.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yubico.com; s=google; t=1790975762; x=1791580562; 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=Lk0DjbkfbQ1TsD4Pxg+wHbekj2coW1eMfRfxJvjswtQ=; b=blApVo4lmYLafIQVODh6lE0h68Xf+9D0zKnceQVgTnVdojyZ6nPylYFlv2Bife2GHg C8rtT1ZQmUg5ZTIIX9dNy6HnB3mzgqVRyedbNsn/8TlMgXUQO4Z99KFWmS+hKD41X2TK ICMTWatu9Vm3rvTeaw7cWLh+l+cD6avJ0suGBipJHfSiaSi2lA8Tf1h5Q33hofUzcNJQ 9UQdfeAMk5e37ElDAXMvNe5h4SgfOLaiU/15gCUTfW4Kj0uhqKYqfEk1iPU75pEYU1fM g6jGzYXrbLC8xuozMebjLLGfgedalKxiZF/91VzIfqEwzJHEM/yw7xslNJecsOZuviOm A+bA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790975762; x=1791580562; 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=Lk0DjbkfbQ1TsD4Pxg+wHbekj2coW1eMfRfxJvjswtQ=; b=mily+BC+2rAXNoeKxgwSKcKs8CB3r+RgO5dlazHy4QCWMde5aAErbwTPeYZoq9X2zd OkDfZOajhZxfdbNpWR+07RCjT1+nZPQsxQyYTItVrdMWMeIDvkWH5Ib6kc6LW38YquoC gOnQTO3eaFcnk1v9jD5x8jinlCL8J7gkT/Z/E5DwYARx+gdar+xlLlBUs2ZbYCHvbgMO WQSQfgDboKw3TFrEMxq/SJcxrf47wZAEbWhkfd+bcmN7qj7nJ9L5gWl+nFDmhEsJqwrP YHqtvz2HSOJZDUrGf43QfGJaL3PFXJA0hPFazs2VVmXN1Vr8TIC1BLwh3zXbGStSpDjE gyOg==
X-Forwarded-Encrypted: i=1; AKwUvBxu2D2Q0c8dFfotGHpRWz6XebOPmAf239CsJSTIZRpYmV+Zv28EvnkPNC7aYQInwgmWgXko@irtf.org
X-Gm-Message-State: AFuF++n+ax/tl4T2XBML2NwH47g//vh00sji5z/XyqSu34UMEMedF6a1 Qd06yu/Gtc+DsqTHUZLVYFtOVAO989rinJaPtMKb1jL5FFr9ilz9oKpCdpy0PLcGc3knWoCpKHo pRMTmmR2KorWcpddUwLOxBs9jTkBZmMpnkfM+KDhSeg==
X-Gm-Gg: AYBFou18QmASngDbMe63niweHUm2uPU+69NLfsRWhyNZHWu0kjgW8TAPE2L+KKBDYua N3tFRmFF2jrNLJQAAwzF4OMQ+lYI2FxXbz6/P4PUaoj+wo4zhRQq7yAChcqtXzf9T2teH9tDg3x yyHxVA8ItxiOTOCGflxYjfbpry5l9IevHY/Pmmkd0pF7Q9WB596YjflfRKCivN7jvlAa6ov/6TY iy7rzzFEF2/LGNXCvRjeks/vWgEqCIF3tc1AIDLlVP7pNpZl5RAHp70MhbZuGtk4aKncdpE4QCx Ch885uQM1CY1Ld5Wb5RZKY4L/or3+b5+G4FPrYEEoiGlhiQcFx3WehqqCPOf5ZW4Q0Y6THbFtus Hvx+LrbCY/V1KqeAmQXB538PRUBwZuoyNtw==
X-Received: by 2002:a05:600c:4703:b0:4a0:25fe:a4b with SMTP id 5b1f17b1804b1-4a02759442bmr74852075e9.15.1790975762429; Fri, 02 Oct 2026 14:16:02 -0700 (PDT)
MIME-Version: 1.0
References: <CAOjisRxC8dvj-qT7FzfzS-foCUqxMXXdsP95b4TXY-j+M2Df5w@mail.gmail.com> <CANeU+ZARcw8ozzhevtBSP8gZuYZcJF76VkwxGCHFFWUDuR_8Rg@mail.gmail.com>
In-Reply-To: <CANeU+ZARcw8ozzhevtBSP8gZuYZcJF76VkwxGCHFFWUDuR_8Rg@mail.gmail.com>
From: Emil Lundberg <emil@yubico.com>
Date: Fri, 02 Oct 2026 23:15:46 +0200
X-Gm-Features: AclHuK__OdofVmXwmTxjmSw3bBkSpGxRfAT2ClhwZzqt-kMS8wbQpsa3EFJNQtI
Message-ID: <CANMnvkyT2VLxKaLxrmrKTFD1Funb6HNtJKTDQkoXxaX25bm6Jg@mail.gmail.com>
To: msj@nthpermutation.com
Content-Type: multipart/alternative; boundary="0000000000001f0dac065ce20a2a"
X-Spamd-Bar: /
Message-ID-Hash: U2KYWSJ2KEQF7JHAMVPUP3KPYEOKGY6O
X-Message-ID-Hash: U2KYWSJ2KEQF7JHAMVPUP3KPYEOKGY6O
X-MailFrom: emil@yubico.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: Nick Sullivan <nicholas.sullivan@gmail.com>, CFRG <cfrg@irtf.org>, "cfrg-chairs@ietf.org" <cfrg-chairs@ietf.org>, draft-irtf-cfrg-pairing-friendly-curves@ietf.org
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/Zu3VIqg0Tilr5HkRSRBtj4MD0G4>
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 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] 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