fcelda nsec5-draft issues

fcelda / nsec5-draft

Working Copy of the NSEC5 Specification

15 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Suite names in test vectors don't match the specification

#36 fcelda closed 4 years ago
1
Incorporate hash-to-curve by reference

#35 kwantam closed 4 years ago
2
Explain this by showing which bits go where

#34 reyzin closed 6 years ago
0
Explain these using conditional move (cmov)

#33 reyzin closed 6 years ago
1
Explain that this is just Montgomery curve equation

#32 reyzin closed 6 years ago
0
Adaption of Trevor Perrin "synthetic nonce" to VRF.

#31 goldbe closed 6 years ago
1
Add discussion of RFC8020 and RFC 8198

#30 goldbe opened 7 years ago
0
remove "where X denotes Y" from algorithms

#29 fcelda opened 7 years ago
0
the additional pseudorandomness property

#28 goldbe opened 7 years ago
1
OS2ECP failed state

#27 fcelda closed 7 years ago
1
VRF terminology

#26 fcelda closed 7 years ago
2
EC_hash_to_curve2 as the only option

#25 fcelda opened 7 years ago
3
Cleanup EC algorithms

#24 fcelda closed 7 years ago
0
do we want to keep xC2xyC in VRF draft?

#23 goldbe closed 7 years ago
3
Request RR Types

#22 vttale opened 7 years ago
5
Getting full uniqueness

#21 reyzin closed 7 years ago
5
need to define wire format for VRF PKs

#20 reyzin opened 7 years ago
5
ECVRF verifying if curve has cofactor > 1

#19 reyzin closed 7 years ago
2
ECVRF_hash_to_curve1 not usable when input must be kept secret?

#18 reyzin closed 7 years ago
3
"Constraints on options" text in VRF draft

#17 reyzin closed 7 years ago
1
vrf hash_to_curve won't end up in G when cofactor > 1

#16 reyzin closed 7 years ago
2
vrf draft hash-to-curve when sizes don't match

#15 reyzin closed 7 years ago
7
Leo wants to hash the PK as input to ECVRF_hash_to_curve and in MGF1 for the RSA-FDH-VRF

#14 goldbe closed 7 years ago
3
once vrf draft is submitted, edit nsec5 draft to link to it properly

#13 goldbe closed 7 years ago
2
VRF: rename functions, avoid confusion with minus sign

#12 fcelda closed 7 years ago
0
VRF: shorter rationale without any definitions

#11 fcelda closed 7 years ago
0
reference working repo in published draft

#10 vttale closed 7 years ago
1
Hash collision with owner name

#9 vttale opened 7 years ago
1
Private key storage

#8 vttale opened 7 years ago
4
Fix section 8.2, "No Data Responses"

#7 vttale opened 7 years ago
0
Consider consolidating subsections for each Resource Record definition

#6 vttale opened 7 years ago
1
repeated "denial of existence" phrase in abstract could flow more smoothly.

#5 vttale closed 7 years ago
0
need examples

#4 vttale opened 7 years ago
1
break out VRF as separate I-D, and update NSEC5 I-D to refer to it

#3 goldbe closed 7 years ago
1
TTL for NSEC5PROOF

#2 fcelda opened 7 years ago
0
Section 8

#1 goldbe opened 7 years ago
0