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.

Sign up for GitHub

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

Jump to bottom

added p384ecdsa #2

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

added p384ecdsa #2

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9906117
added p384ecdsa
franziskuskiefer Dec 1, 2015
6eebd9c
Merge branch 'master' of github.com:martinthomson/content-signature
franziskuskiefer Dec 23, 2015
ff8c0cf
Merge upstream branch 'master' of github.com:martinthomson/content-si…
franziskuskiefer Feb 8, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
31 changes: 29 additions & 2 deletions draft-thomson-http-content-signature.md
View file
Open in desktop
Expand Up @@ -139,6 +139,14 @@ p256ecdsa:
without padding. No parameters other than `keyid` can be specified along with
the `p256ecdsa` parameter.

p384ecdsa:

: This parameter contains an ECDSA [X.692] signature on the P-384 curve
[FIPS186]. The signature is produced using the SHA-384 hash [FIPS180-2]. The
resulting signature is encoded using URL-safe variant of base-64 [RFC4648].
No parameters other than `keyid` can be specified along with the `p384ecdsa`
parameter.


Additional header field values can be defined and registered. The parameter
MUST describe how the signature is produced and encoded.
Expand Down Expand Up @@ -167,9 +175,11 @@ Alternatively, explicitly including a public key can allow a verifier to
correctly identify the key that was used if the `keyid` parameter is not
sufficient.

This document defines a new parameter for use with the `Encryption-Key` header
This document defines two new parameters for use with the `Encryption-Key` header
field. The `p256ecdsa` parameter conveys an uncompressed P-256 public key
[X.692] that is encoded using URL-safe variant of base-64 [RFC4648].
[X.692] that is encoded using URL-safe variant of base-64 [RFC4648]. The `p384ecdsa`
parameter conveys an uncompressed P-384 public key [X.692] that is encoded using
URL-safe variant of base-64 [RFC4648].


# Security Considerations {#security}
Expand Down Expand Up @@ -239,6 +249,12 @@ The initial contents of this registry are:
{{csig}} of this document.
* Reference: {{csig}} of this document

### p384ecdsa

* Parameter Name: p384ecdsa
* Purpose: Conveys a signature using P-384, ECDSA and SHA-384 as described in
{{csig}} of this document.
* Reference: {{csig}} of this document

## The p256ecdsa Parameter for the Encryption-Key Header Field

Expand All @@ -251,4 +267,15 @@ The `p256ecdsa` parameter is registered in the "Hypertext Transfer Protocol
the `Content-Signature` header field.
* Reference: {{keys}} of this document

## The p384ecdsa Parameter for the Encryption-Key Header Field

The `p384ecdsa` parameter is registered in the "Hypertext Transfer Protocol
(HTTP) Encryption Parameters" registry established in
[I-D.thomson-http-encryption], with the following values:

* Parameter Name: p384ecdsa
* Purpose: Conveys a signing key for use with the parameter of the same name on
the `Content-Signature` header field.
* Reference: {{keys}} of this document

--- back