-
Notifications
You must be signed in to change notification settings - Fork 44
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
Signature specification #102
Conversation
Incorporates #93 |
Can we clarify what is being decided in this PR vs #93 |
Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
Co-authored-by: Milind Gokarn <[email protected]> Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
Signed-off-by: Pritesh Bandi <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General comments on formating. We should always do backquotes for words like alg
, iat
, and exp
... even if they are in the description.
signature-specification.md
Outdated
3. `alg` header values for various signature algorithms: | ||
| Signature Algorithm | "alg" Param Value | | ||
| -------- | -------- | | ||
| ECDSA on secp256r1 with SHA-256 | ES256 | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have a more friendly name for secp256r1
from SECG? like P-256
from NIST?
Also, we need to provide a reference for readers. RFC 8422 Appendix A is a good one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not all algos and curves are in NIST and that's the reason refrained from using NIST curves.
Added reference to RFC 8422 Appendix A for discovery.
@priteshbandi, looks like a few minor clarification items are still open. |
Signed-off-by: Pritesh Bandi <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Summary
First draft of signature specification.
issues for future work
How is this PR different from #93?