Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Various editorial updates #275

Merged
merged 6 commits into from
Jul 10, 2023
Merged

Various editorial updates #275

merged 6 commits into from
Jul 10, 2023

Conversation

BasileiosKal
Copy link
Contributor

Main changes:

  • Renaming the base points of G1/G2
  • Removed the Definitions (we are explicitly defining everything in the operation)
  • Updated the ProofGen/ProofVerify explanatory section

+ couple of terminology and operation description updates

8. C = Bbar * r2^ + Abar * r3^ + H_j1 * m^_j1 + ... + H_jU * m^_jU + D * c
9. cv = calculate_challenge(Abar, Bbar, C, (i1, ..., iR),
8. T = Abar * r3^ + Bbar * r2^ + H_j1 * m^_j1 + ... + H_jU * m^_jU
9. T = T + D * c
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a line length issue? Also, switching the order of Abar and Bbar without switching r2 and r3 doesn't seem worth it to me :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh boy another breaking change 😅. Switched r2 with r3 in #276 (with updated fixtures)

Copy link
Contributor Author

@BasileiosKal BasileiosKal Jul 6, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a line length issue?

Yeap sadly

@@ -202,8 +199,8 @@ e
r
: The prime order of the G1 and G2 subgroups.

P1, P2
: points on G1 and G2 respectively. For a pairing-friendly curve, this document denotes operations in E1 and E2 in additive notation, i.e., P + Q denotes point addition and x \* P denotes scalar multiplication. Operations in GT are written in multiplicative notation, i.e., a \* b is field multiplication.
BP, BP'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not BP1 and BP2, the ' character might be hard to understand in the middle of the spec.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indent was to use the notation from pairing-friendly curves draft. But yea its hard to see. Changed to use BP1 and BP2.

@@ -538,7 +509,7 @@ Procedure:
8. B = P1 + Q_1 * domain + H_1 * msg_1 + ... + H_L * msg_L
9. Abar = A * r1
10. Bbar = B * r1 - Abar * e
11. C = Bbar * r2 + Abar * r3 + H_j1 * m~_j1 + ... + H_jU * m~_jU
11. T = Abar * r3 + Bbar * r2 + H_j1 * m~_j1 + ... + H_jU * m~_jU
12. c = calculate_challenge(Abar, Bbar, C, (i1, ..., iR),
Copy link
Contributor

@christianpaquin christianpaquin Jul 7, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change C to T on line 12 since it's been renamed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed. Thanks!

@@ -202,8 +199,8 @@ e
r
: The prime order of the G1 and G2 subgroups.

P1, P2
: points on G1 and G2 respectively. For a pairing-friendly curve, this document denotes operations in E1 and E2 in additive notation, i.e., P + Q denotes point addition and x \* P denotes scalar multiplication. Operations in GT are written in multiplicative notation, i.e., a \* b is field multiplication.
BP, BP'
Copy link
Contributor

@christianpaquin christianpaquin Jul 7, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't use BP (the G1 base point) in the spec, so we can get rid of it.

Copy link
Contributor Author

@BasileiosKal BasileiosKal Jul 7, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BP (renamed to BP1) is used in the PR in the description of P1 in the ciphersuite (i.e., that P1 != BP1).

Still could most likely remove it, but better be on the safe side??

@BasileiosKal
Copy link
Contributor Author

Discussed on the WG call on the 10 of July. Will wait for reviews before resolving

@BasileiosKal
Copy link
Contributor Author

Discussed on the WG call of the 10th of July. Multiple approvals. Editorial updates. Merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants