draft-ietf-jose-json-web-algorithms-07.txt   draft-ietf-jose-json-web-algorithms-08.txt 
JOSE Working Group M. Jones JOSE Working Group M. Jones
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Standards Track November 6, 2012 Intended status: Standards Track December 27, 2012
Expires: May 10, 2013 Expires: June 30, 2013
JSON Web Algorithms (JWA) JSON Web Algorithms (JWA)
draft-ietf-jose-json-web-algorithms-07 draft-ietf-jose-json-web-algorithms-08
Abstract Abstract
The JSON Web Algorithms (JWA) specification enumerates cryptographic The JSON Web Algorithms (JWA) specification enumerates cryptographic
algorithms and identifiers to be used with the JSON Web Signature algorithms and identifiers to be used with the JSON Web Signature
(JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK) (JWS), JSON Web Encryption (JWE), and JSON Web Key (JWK)
specifications. specifications.
Status of this Memo Status of this Memo
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 10, 2013. This Internet-Draft will expire on June 30, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 12 skipping to change at page 2, line 12
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 4 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Terms Incorporated from the JWS Specification . . . . . . 4 2.1. Terms Incorporated from the JWS Specification . . . . . . 4
2.2. Terms Incorporated from the JWE Specification . . . . . . 5 2.2. Terms Incorporated from the JWE Specification . . . . . . 5
2.3. Terms Incorporated from the JWK Specification . . . . . . 6 2.3. Terms Incorporated from the JWK Specification . . . . . . 7
2.4. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 7 2.4. Defined Terms . . . . . . . . . . . . . . . . . . . . . . 7
3. Cryptographic Algorithms for JWS . . . . . . . . . . . . . . . 7 3. Cryptographic Algorithms for JWS . . . . . . . . . . . . . . . 7
3.1. "alg" (Algorithm) Header Parameter Values for JWS . . . . 7 3.1. "alg" (Algorithm) Header Parameter Values for JWS . . . . 7
3.2. MAC with HMAC SHA-256, HMAC SHA-384, or HMAC SHA-512 . . . 8 3.2. MAC with HMAC SHA-256, HMAC SHA-384, or HMAC SHA-512 . . . 8
3.3. Digital Signature with RSA SHA-256, RSA SHA-384, or 3.3. Digital Signature with RSA SHA-256, RSA SHA-384, or
RSA SHA-512 . . . . . . . . . . . . . . . . . . . . . . . 9 RSA SHA-512 . . . . . . . . . . . . . . . . . . . . . . . 9
3.4. Digital Signature with ECDSA P-256 SHA-256, ECDSA 3.4. Digital Signature with ECDSA P-256 SHA-256, ECDSA
P-384 SHA-384, or ECDSA P-521 SHA-512 . . . . . . . . . . 10 P-384 SHA-384, or ECDSA P-521 SHA-512 . . . . . . . . . . 10
3.5. Using the Algorithm "none" . . . . . . . . . . . . . . . . 12 3.5. Using the Algorithm "none" . . . . . . . . . . . . . . . . 12
3.6. Additional Digital Signature/MAC Algorithms and 3.6. Additional Digital Signature/MAC Algorithms and
Parameters . . . . . . . . . . . . . . . . . . . . . . . . 12 Parameters . . . . . . . . . . . . . . . . . . . . . . . . 12
4. Cryptographic Algorithms for JWE . . . . . . . . . . . . . . . 12 4. Cryptographic Algorithms for JWE . . . . . . . . . . . . . . . 13
4.1. "alg" (Algorithm) Header Parameter Values for JWE . . . . 12 4.1. "alg" (Algorithm) Header Parameter Values for JWE . . . . 13
4.2. "enc" (Encryption Method) Header Parameter Values for 4.2. "enc" (Encryption Method) Header Parameter Values for
JWE . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 JWE . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.3. Key Encryption with RSAES-PKCS1-V1_5 . . . . . . . . . . . 15 4.3. Key Encryption with RSAES-PKCS1-V1_5 . . . . . . . . . . . 15
4.4. Key Encryption with RSAES OAEP . . . . . . . . . . . . . . 15 4.4. Key Encryption with RSAES OAEP . . . . . . . . . . . . . . 15
4.5. Key Encryption with AES Key Wrap . . . . . . . . . . . . . 15 4.5. Key Encryption with AES Key Wrap . . . . . . . . . . . . . 15
4.6. Direct Encryption with a Shared Symmetric Key . . . . . . 15 4.6. Direct Encryption with a Shared Symmetric Key . . . . . . 16
4.7. Key Agreement with Elliptic Curve Diffie-Hellman 4.7. Key Agreement with Elliptic Curve Diffie-Hellman
Ephemeral Static (ECDH-ES) . . . . . . . . . . . . . . . . 15 Ephemeral Static (ECDH-ES) . . . . . . . . . . . . . . . . 16
4.7.1. Key Derivation for "ECDH-ES" . . . . . . . . . . . . . 16 4.7.1. Key Derivation for "ECDH-ES" . . . . . . . . . . . . . 16
4.8. Composite Plaintext Encryption Algorithms 4.8. Composite Plaintext Encryption Algorithms
"A128CBC+HS256" and "A256CBC+HS512" . . . . . . . . . . . 17 "A128CBC+HS256" and "A256CBC+HS512" . . . . . . . . . . . 17
4.8.1. Key Derivation for "A128CBC+HS256" and 4.8.1. Key Derivation for "A128CBC+HS256" and
"A256CBC+HS512" . . . . . . . . . . . . . . . . . . . 17 "A256CBC+HS512" . . . . . . . . . . . . . . . . . . . 18
4.8.2. Encryption Calculation for "A128CBC+HS256" and 4.8.2. Encryption Calculation for "A128CBC+HS256" and
"A256CBC+HS512" . . . . . . . . . . . . . . . . . . . 19 "A256CBC+HS512" . . . . . . . . . . . . . . . . . . . 19
4.8.3. Integrity Calculation for "A128CBC+HS256" and 4.8.3. Integrity Calculation for "A128CBC+HS256" and
"A256CBC+HS512" . . . . . . . . . . . . . . . . . . . 19 "A256CBC+HS512" . . . . . . . . . . . . . . . . . . . 19
4.9. Plaintext Encryption with AES GCM . . . . . . . . . . . . 19 4.9. Plaintext Encryption with AES GCM . . . . . . . . . . . . 20
4.10. Additional Encryption Algorithms and Parameters . . . . . 20 4.10. Additional Encryption Algorithms and Parameters . . . . . 20
5. Cryptographic Algorithms for JWK . . . . . . . . . . . . . . . 21 5. Cryptographic Algorithms for JWK . . . . . . . . . . . . . . . 21
5.1. "alg" (Algorithm Family) Parameter Values for JWK . . . . 21 5.1. "kty" (Key Type) Parameter Values for JWK . . . . . . . . 21
5.2. JWK Parameters for Elliptic Curve Keys . . . . . . . . . . 21 5.2. JWK Parameters for Elliptic Curve Keys . . . . . . . . . . 22
5.2.1. "crv" (Curve) Parameter . . . . . . . . . . . . . . . 21 5.2.1. "crv" (Curve) Parameter . . . . . . . . . . . . . . . 22
5.2.2. "x" (X Coordinate) Parameter . . . . . . . . . . . . . 22 5.2.2. "x" (X Coordinate) Parameter . . . . . . . . . . . . . 22
5.2.3. "y" (Y Coordinate) Parameter . . . . . . . . . . . . . 22 5.2.3. "y" (Y Coordinate) Parameter . . . . . . . . . . . . . 22
5.3. JWK Parameters for RSA Keys . . . . . . . . . . . . . . . 22 5.3. JWK Parameters for RSA Keys . . . . . . . . . . . . . . . 22
5.3.1. "n" (Modulus) Parameter . . . . . . . . . . . . . . . 22 5.3.1. "n" (Modulus) Parameter . . . . . . . . . . . . . . . 23
5.3.2. "e" (Exponent) Parameter . . . . . . . . . . . . . . . 22 5.3.2. "e" (Exponent) Parameter . . . . . . . . . . . . . . . 23
5.4. Additional Key Algorithm Families and Parameters . . . . . 23 5.4. Additional Key Types and Parameters . . . . . . . . . . . 23
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23
6.1. JSON Web Signature and Encryption Algorithms Registry . . 24 6.1. JSON Web Signature and Encryption Algorithms Registry . . 24
6.1.1. Registration Template . . . . . . . . . . . . . . . . 24 6.1.1. Registration Template . . . . . . . . . . . . . . . . 24
6.1.2. Initial Registry Contents . . . . . . . . . . . . . . 25 6.1.2. Initial Registry Contents . . . . . . . . . . . . . . 25
6.2. JSON Web Key Algorithm Families Registry . . . . . . . . . 27 6.2. JSON Web Key Types Registry . . . . . . . . . . . . . . . 28
6.2.1. Registration Template . . . . . . . . . . . . . . . . 28 6.2.1. Registration Template . . . . . . . . . . . . . . . . 28
6.2.2. Initial Registry Contents . . . . . . . . . . . . . . 28 6.2.2. Initial Registry Contents . . . . . . . . . . . . . . 29
6.3. JSON Web Key Parameters Registration . . . . . . . . . . . 28 6.3. JSON Web Key Parameters Registration . . . . . . . . . . . 29
6.3.1. Registry Contents . . . . . . . . . . . . . . . . . . 29 6.3.1. Registry Contents . . . . . . . . . . . . . . . . . . 29
7. Security Considerations . . . . . . . . . . . . . . . . . . . 29 7. Security Considerations . . . . . . . . . . . . . . . . . . . 29
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 30 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
8.1. Normative References . . . . . . . . . . . . . . . . . . . 30 8.1. Normative References . . . . . . . . . . . . . . . . . . . 31
8.2. Informative References . . . . . . . . . . . . . . . . . . 32 8.2. Informative References . . . . . . . . . . . . . . . . . . 32
Appendix A. Digital Signature/MAC Algorithm Identifier Appendix A. Digital Signature/MAC Algorithm Identifier
Cross-Reference . . . . . . . . . . . . . . . . . . . 33 Cross-Reference . . . . . . . . . . . . . . . . . . . 33
Appendix B. Encryption Algorithm Identifier Cross-Reference . . . 35 Appendix B. Encryption Algorithm Identifier Cross-Reference . . . 35
Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 37 Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 37
Appendix D. Open Issues . . . . . . . . . . . . . . . . . . . . . 37 Appendix D. Open Issues . . . . . . . . . . . . . . . . . . . . . 38
Appendix E. Document History . . . . . . . . . . . . . . . . . . 37 Appendix E. Document History . . . . . . . . . . . . . . . . . . 38
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 41 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 42
1. Introduction 1. Introduction
The JSON Web Algorithms (JWA) specification enumerates cryptographic The JSON Web Algorithms (JWA) specification enumerates cryptographic
algorithms and identifiers to be used with the JSON Web Signature algorithms and identifiers to be used with the JSON Web Signature
(JWS) [JWS], JSON Web Encryption (JWE) [JWE], and JSON Web Key (JWK) (JWS) [JWS], JSON Web Encryption (JWE) [JWE], and JSON Web Key (JWK)
[JWK] specifications. All these specifications utilize JavaScript [JWK] specifications. All these specifications utilize JavaScript
Object Notation (JSON) [RFC4627] based data structures. This Object Notation (JSON) [RFC4627] based data structures. This
specification also describes the semantics and operations that are specification also describes the semantics and operations that are
specific to these algorithms and algorithm families. specific to these algorithms and key types.
Enumerating the algorithms and identifiers for them in this Enumerating the algorithms and identifiers for them in this
specification, rather than in the JWS, JWE, and JWK specifications, specification, rather than in the JWS, JWE, and JWK specifications,
is intended to allow them to remain unchanged in the face of changes is intended to allow them to remain unchanged in the face of changes
in the set of required, recommended, optional, and deprecated in the set of required, recommended, optional, and deprecated
algorithms over time. algorithms over time.
1.1. Notational Conventions 1.1. Notational Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
skipping to change at page 4, line 35 skipping to change at page 4, line 35
document are to be interpreted as described in Key words for use in document are to be interpreted as described in Key words for use in
RFCs to Indicate Requirement Levels [RFC2119]. RFCs to Indicate Requirement Levels [RFC2119].
2. Terminology 2. Terminology
2.1. Terms Incorporated from the JWS Specification 2.1. Terms Incorporated from the JWS Specification
These terms defined by the JSON Web Signature (JWS) [JWS] These terms defined by the JSON Web Signature (JWS) [JWS]
specification are incorporated into this specification: specification are incorporated into this specification:
JSON Web Signature (JWS) A data structure cryptographically securing JSON Web Signature (JWS) A data structure representing a digitally
a JWS Header and a JWS Payload with a JWS Signature value. signed or MACed message. The structure consists of three parts:
the JWS Header, the JWS Payload, and the JWS Signature value.
JWS Header A string representing a JavaScript Object Notation (JSON) JSON Text Object A UTF-8 encoded text string representing a JSON
[RFC4627] object that describes the digital signature or MAC object; the syntax of JSON objects is defined in Section 2.2 of
operation applied to create the JWS Signature value. [RFC4627].
JWS Header A JSON Text Object that describes the digital signature
or MAC operation applied to create the JWS Signature value.
JWS Payload The bytes to be secured -- a.k.a., the message. The JWS Payload The bytes to be secured -- a.k.a., the message. The
payload can contain an arbitrary sequence of bytes. payload can contain an arbitrary sequence of bytes.
JWS Signature A byte array containing the cryptographic material JWS Signature A byte array containing the cryptographic material
that secures the contents of the JWS Header and the JWS Payload. that secures the contents of the JWS Header and the JWS Payload.
Base64url Encoding The URL- and filename-safe Base64 encoding Base64url Encoding The URL- and filename-safe Base64 encoding
described in RFC 4648 [RFC4648], Section 5, with the (non URL- described in RFC 4648 [RFC4648], Section 5, with the (non URL-
safe) '=' padding characters omitted, as permitted by Section 3.2. safe) '=' padding characters omitted, as permitted by Section 3.2.
(See Appendix C of [JWS] for notes on implementing base64url (See Appendix C of [JWS] for notes on implementing base64url
encoding without padding.) encoding without padding.)
Encoded JWS Header Base64url encoding of the bytes of the UTF-8 Encoded JWS Header Base64url encoding of the JWS Header.
[RFC3629] representation of the JWS Header.
Encoded JWS Payload Base64url encoding of the JWS Payload. Encoded JWS Payload Base64url encoding of the JWS Payload.
Encoded JWS Signature Base64url encoding of the JWS Signature. Encoded JWS Signature Base64url encoding of the JWS Signature.
JWS Secured Input The concatenation of the Encoded JWS Header, a JWS Secured Input The concatenation of the Encoded JWS Header, a
period ('.') character, and the Encoded JWS Payload. period ('.') character, and the Encoded JWS Payload.
Collision Resistant Namespace A namespace that allows names to be Collision Resistant Namespace A namespace that allows names to be
allocated in a manner such that they are highly unlikely to allocated in a manner such that they are highly unlikely to
skipping to change at page 5, line 35 skipping to change at page 5, line 42
delegated namespace, the definer of a name needs to take delegated namespace, the definer of a name needs to take
reasonable precautions to ensure they are in control of the reasonable precautions to ensure they are in control of the
portion of the namespace they use to define the name. portion of the namespace they use to define the name.
2.2. Terms Incorporated from the JWE Specification 2.2. Terms Incorporated from the JWE Specification
These terms defined by the JSON Web Encryption (JWE) [JWE] These terms defined by the JSON Web Encryption (JWE) [JWE]
specification are incorporated into this specification: specification are incorporated into this specification:
JSON Web Encryption (JWE) A data structure representing an encrypted JSON Web Encryption (JWE) A data structure representing an encrypted
version of a Plaintext. The structure consists of four parts: the message. The structure consists of five parts: the JWE Header,
JWE Header, the JWE Encrypted Key, the JWE Ciphertext, and the JWE the JWE Encrypted Key, the JWE Initialization Vector, the JWE
Integrity Value. Ciphertext, and the JWE Integrity Value.
Plaintext The bytes to be encrypted -- a.k.a., the message. The Plaintext The bytes to be encrypted -- a.k.a., the message. The
plaintext can contain an arbitrary sequence of bytes. plaintext can contain an arbitrary sequence of bytes.
Ciphertext The encrypted version of the Plaintext. Ciphertext An encrypted representation of the Plaintext.
Content Encryption Key (CEK) A symmetric key used to encrypt the Content Encryption Key (CEK) A symmetric key used to encrypt the
Plaintext for the recipient to produce the Ciphertext. Plaintext for the recipient to produce the Ciphertext.
Content Integrity Key (CIK) A key used with a MAC function to ensure Content Integrity Key (CIK) A key used with a MAC function to ensure
the integrity of the Ciphertext and the parameters used to create the integrity of the Ciphertext and the parameters used to create
it. it.
Content Master Key (CMK) A key from which the CEK and CIK are Content Master Key (CMK) A key from which the CEK and CIK are
derived. When key wrapping or key encryption are employed, the derived. When key wrapping or key encryption are employed, the
CMK is randomly generated and encrypted to the recipient as the CMK is randomly generated and encrypted to the recipient as the
JWE Encrypted Key. When key agreement is employed, the CMK is the JWE Encrypted Key. When direct encryption with a shared symmetric
result of the key agreement algorithm. key is employed, the CMK is the shared key. When key agreement
without key wrapping is employed, the CMK is the result of the key
agreement algorithm.
JWE Header A string representing a JSON object that describes the JSON Text Object A UTF-8 encoded text string representing a JSON
encryption operations applied to create the JWE Encrypted Key, the object; the syntax of JSON objects is defined in Section 2.2 of
JWE Ciphertext, and the JWE Integrity Value. [RFC4627].
JWE Header A JSON Text Object that describes the encryption
operations applied to create the JWE Encrypted Key, the JWE
Ciphertext, and the JWE Integrity Value.
JWE Encrypted Key When key wrapping or key encryption are employed, JWE Encrypted Key When key wrapping or key encryption are employed,
the Content Master Key (CMK) is encrypted with the intended the Content Master Key (CMK) is encrypted with the intended
recipient's key and the resulting encrypted content is recorded as recipient's key and the resulting encrypted content is recorded as
a byte array, which is referred to as the JWE Encrypted Key. a byte array, which is referred to as the JWE Encrypted Key.
Otherwise, when key agreement is employed, the JWE Encrypted Key Otherwise, when direct encryption with a shared or agreed upon
is the empty byte array. symmetric key is employed, the JWE Encrypted Key is the empty byte
array.
JWE Initialization Vector A byte array containing the Initialization
Vector used when encrypting the Plaintext.
JWE Ciphertext A byte array containing the Ciphertext. JWE Ciphertext A byte array containing the Ciphertext.
JWE Integrity Value A byte array containing a MAC value that ensures JWE Integrity Value A byte array containing a MAC value that ensures
the integrity of the Ciphertext and the parameters used to create the integrity of the Ciphertext and the parameters used to create
it. it.
Encoded JWE Header Base64url encoding of the bytes of the UTF-8 Encoded JWE Header Base64url encoding of the JWE Header.
[RFC3629] representation of the JWE Header.
Encoded JWE Encrypted Key Base64url encoding of the JWE Encrypted Encoded JWE Encrypted Key Base64url encoding of the JWE Encrypted
Key. Key.
Encoded JWE Initialization Vector Base64url encoding of the JWE
Initialization Vector.
Encoded JWE Ciphertext Base64url encoding of the JWE Ciphertext. Encoded JWE Ciphertext Base64url encoding of the JWE Ciphertext.
Encoded JWE Integrity Value Base64url encoding of the JWE Integrity Encoded JWE Integrity Value Base64url encoding of the JWE Integrity
Value. Value.
AEAD Algorithm An Authenticated Encryption with Associated Data Authenticated Encryption An Authenticated Encryption algorithm is
(AEAD) [RFC5116] encryption algorithm is one that provides an one that provides an integrated content integrity check.
integrated content integrity check. AEAD encryption algorithms Authenticated Encryption algorithms accept two inputs, the
accept two inputs, the plaintext and the "additional authenticated plaintext and the "additional authenticated data" value, and
data" value, and produce two outputs, the ciphertext and the produce two outputs, the ciphertext and the "authentication tag"
"authentication tag" value. AES Galois/Counter Mode (GCM) is one value. AES Galois/Counter Mode (GCM) is one such algorithm.
such algorithm.
2.3. Terms Incorporated from the JWK Specification 2.3. Terms Incorporated from the JWK Specification
These terms defined by the JSON Web Key (JWK) [JWK] specification are These terms defined by the JSON Web Key (JWK) [JWK] specification are
incorporated into this specification: incorporated into this specification:
JSON Web Key (JWK) A JSON data structure that represents a public JSON Web Key (JWK) A JSON data structure that represents a public
key. key.
JSON Web Key Set (JWK Set) A JSON object that contains an array of JSON Web Key Set (JWK Set) A JSON object that contains an array of
JWKs as a member. JWKs as the value of its "keys" member.
2.4. Defined Terms 2.4. Defined Terms
These terms are defined for use by this specification: These terms are defined for use by this specification:
Header Parameter Name The name of a member of the JSON object Header Parameter Name The name of a member of the JSON object
representing a JWS Header or JWE Header. representing a JWS Header or JWE Header.
Header Parameter Value The value of a member of the JSON object Header Parameter Value The value of a member of the JSON object
representing a JWS Header or JWE Header. representing a JWS Header or JWE Header.
skipping to change at page 12, line 10 skipping to change at page 12, line 27
array. array.
Examples using these algorithms are shown in Appendices A.3 and A.4 Examples using these algorithms are shown in Appendices A.3 and A.4
of [JWS]. of [JWS].
3.5. Using the Algorithm "none" 3.5. Using the Algorithm "none"
JWSs MAY also be created that do not provide integrity protection. JWSs MAY also be created that do not provide integrity protection.
Such a JWS is called a "Plaintext JWS". Plaintext JWSs MUST use the Such a JWS is called a "Plaintext JWS". Plaintext JWSs MUST use the
"alg" value "none", and are formatted identically to other JWSs, but "alg" value "none", and are formatted identically to other JWSs, but
with an empty JWS Signature value. with the empty string for its JWS Signature value.
3.6. Additional Digital Signature/MAC Algorithms and Parameters 3.6. Additional Digital Signature/MAC Algorithms and Parameters
Additional algorithms MAY be used to protect JWSs with corresponding Additional algorithms MAY be used to protect JWSs with corresponding
"alg" (algorithm) header parameter values being defined to refer to "alg" (algorithm) header parameter values being defined to refer to
them. New "alg" header parameter values SHOULD either be registered them. New "alg" header parameter values SHOULD either be registered
in the IANA JSON Web Signature and Encryption Algorithms registry in the IANA JSON Web Signature and Encryption Algorithms registry
Section 6.1 or be a URI that contains a Collision Resistant Section 6.1 or be a value that contains a Collision Resistant
Namespace. In particular, it is permissible to use the algorithm Namespace. In particular, it is permissible to use the algorithm
identifiers defined in XML DSIG [RFC3275], XML DSIG 2.0 identifiers defined in XML DSIG [RFC3275], XML DSIG 2.0
[W3C.CR-xmldsig-core2-20120124], and related specifications as "alg" [W3C.CR-xmldsig-core2-20120124], and related specifications as "alg"
values. values.
As indicated by the common registry, JWSs and JWEs share a common As indicated by the common registry, JWSs and JWEs share a common
"alg" value space. The values used by the two specifications MUST be "alg" value space. The values used by the two specifications MUST be
distinct, as the "alg" value MAY be used to determine whether the distinct, as the "alg" value MAY be used to determine whether the
object is a JWS or JWE. object is a JWS or JWE.
Likewise, additional reserved header parameter names MAY be defined Likewise, additional reserved Header Parameter Names MAY be defined
via the IANA JSON Web Signature and Encryption Header Parameters via the IANA JSON Web Signature and Encryption Header Parameters
registry [JWS]. As indicated by the common registry, JWSs and JWEs registry [JWS]. As indicated by the common registry, JWSs and JWEs
share a common header parameter space; when a parameter is used by share a common header parameter space; when a parameter is used by
both specifications, its usage must be compatible between the both specifications, its usage must be compatible between the
specifications. specifications.
4. Cryptographic Algorithms for JWE 4. Cryptographic Algorithms for JWE
JWE uses cryptographic algorithms to encrypt the Content Master Key JWE uses cryptographic algorithms to encrypt the Content Master Key
(CMK) and the Plaintext. This section specifies a set of specific (CMK) and the Plaintext. This section specifies a set of specific
skipping to change at page 14, line 19 skipping to change at page 14, line 37
The table below is the set of "enc" (encryption method) header The table below is the set of "enc" (encryption method) header
parameter values that are defined by this specification for use with parameter values that are defined by this specification for use with
JWE. These algorithms are used to encrypt the Plaintext, which JWE. These algorithms are used to encrypt the Plaintext, which
produces the Ciphertext. produces the Ciphertext.
+---------------+----------------------------------+----------------+ +---------------+----------------------------------+----------------+
| enc Parameter | Block Encryption Algorithm | Implementation | | enc Parameter | Block Encryption Algorithm | Implementation |
| Value | | Requirements | | Value | | Requirements |
+---------------+----------------------------------+----------------+ +---------------+----------------------------------+----------------+
| A128CBC+HS256 | Composite AEAD algorithm using | REQUIRED | | A128CBC+HS256 | Composite Authenticated | REQUIRED |
| | Encryption algorithm using | |
| | Advanced Encryption Standard | | | | Advanced Encryption Standard | |
| | (AES) in Cipher Block Chaining | | | | (AES) in Cipher Block Chaining | |
| | (CBC) mode with PKCS #5 padding | | | | (CBC) mode with PKCS #5 padding | |
| | [AES] [NIST.800-38A] with an | | | | [AES] [NIST.800-38A] with an | |
| | integrity calculation using HMAC | | | | integrity calculation using HMAC | |
| | SHA-256, using a 256 bit CMK | | | | SHA-256, using a 256 bit CMK | |
| | (and 128 bit CEK) as specified | | | | (and 128 bit CEK) as specified | |
| | in Section 4.8 | | | | in Section 4.8 | |
| A256CBC+HS512 | Composite AEAD algorithm using | REQUIRED | | A256CBC+HS512 | Composite Authenticated | REQUIRED |
| | AES in CBC mode with PKCS #5 | | | | Encryption algorithm using AES | |
| | padding with an integrity | | | | in CBC mode with PKCS #5 padding | |
| | calculation using HMAC SHA-512, | | | | with an integrity calculation | |
| | using a 512 bit CMK (and 256 bit | | | | using HMAC SHA-512, using a 512 | |
| | CEK) as specified in Section 4.8 | | | | bit CMK (and 256 bit CEK) as | |
| | specified in Section 4.8 | |
| A128GCM | AES in Galois/Counter Mode (GCM) | RECOMMENDED | | A128GCM | AES in Galois/Counter Mode (GCM) | RECOMMENDED |
| | [AES] [NIST.800-38D] using 128 | | | | [AES] [NIST.800-38D] using 128 | |
| | bit keys | | | | bit keys | |
| A256GCM | AES GCM using 256 bit keys | RECOMMENDED | | A256GCM | AES GCM using 256 bit keys | RECOMMENDED |
+---------------+----------------------------------+----------------+ +---------------+----------------------------------+----------------+
All the names are short because a core goal of JWE is for the All the names are short because a core goal of JWE is for the
representations to be compact. However, there is no a priori length representations to be compact. However, there is no a priori length
restriction on "alg" values. restriction on "alg" values.
skipping to change at page 17, line 19 skipping to change at page 17, line 41
concatenation. If an "apv" (agreement PartyVInfo) header concatenation. If an "apv" (agreement PartyVInfo) header
parameter is present, Data is set to the result of base64url parameter is present, Data is set to the result of base64url
decoding the "apv" value and Datalen is set to the number of bytes decoding the "apv" value and Datalen is set to the number of bytes
in Data. Otherwise, Datalen is set to 0 and Data is set to the in Data. Otherwise, Datalen is set to 0 and Data is set to the
empty byte string. empty byte string.
SuppPubInfo This is set to the empty byte string. SuppPubInfo This is set to the empty byte string.
SuppPrivInfo This is set to the empty byte string. SuppPrivInfo This is set to the empty byte string.
For all three "alg" values, the digest function used is SHA-256.
4.8. Composite Plaintext Encryption Algorithms "A128CBC+HS256" and 4.8. Composite Plaintext Encryption Algorithms "A128CBC+HS256" and
"A256CBC+HS512" "A256CBC+HS512"
This section defines two composite "enc" algorithms that perform This section defines two composite "enc" algorithms that perform
plaintext encryption using non-AEAD algorithms and add an integrity plaintext encryption using non-Authenticated Encryption algorithms
check calculation, so that the resulting composite algorithms are and add an integrity check calculation, so that the resulting
AEAD. These composite algorithms derive a Content Encryption Key composite algorithms perform Authenticated Encryption. These
(CEK) and a Content Integrity Key (CIK) from a Content Master Key, composite algorithms derive a Content Encryption Key (CEK) and a
per Section 4.8.1. They perform block encryption with AES CBC, per Content Integrity Key (CIK) from a Content Master Key, per
Section 4.8.1. They perform block encryption with AES CBC, per
Section 4.8.2. Finally, they add an integrity check using HMAC SHA-2 Section 4.8.2. Finally, they add an integrity check using HMAC SHA-2
algorithms of matching strength, per Section 4.8.3. algorithms of matching strength, per Section 4.8.3.
A 256 bit Content Master Key (CMK) value is used with the A 256 bit Content Master Key (CMK) value is used with the
"A128CBC+HS256" algorithm. A 512 bit Content Master Key (CMK) value "A128CBC+HS256" algorithm. A 512 bit Content Master Key (CMK) value
is used with the "A256CBC+HS512" algorithm. is used with the "A256CBC+HS512" algorithm.
An example using this algorithm is shown in Appendix A.2 of [JWE]. An example using this algorithm is shown in Appendix A.2 of [JWE].
4.8.1. Key Derivation for "A128CBC+HS256" and "A256CBC+HS512" 4.8.1. Key Derivation for "A128CBC+HS256" and "A256CBC+HS512"
skipping to change at page 20, line 35 skipping to change at page 21, line 4
Examples using this algorithm are shown in Appendices A.1 and A.3 of Examples using this algorithm are shown in Appendices A.1 and A.3 of
[JWE]. [JWE].
4.10. Additional Encryption Algorithms and Parameters 4.10. Additional Encryption Algorithms and Parameters
Additional algorithms MAY be used to protect JWEs with corresponding Additional algorithms MAY be used to protect JWEs with corresponding
"alg" (algorithm) and "enc" (encryption method) header parameter "alg" (algorithm) and "enc" (encryption method) header parameter
values being defined to refer to them. New "alg" and "enc" header values being defined to refer to them. New "alg" and "enc" header
parameter values SHOULD either be registered in the IANA JSON Web parameter values SHOULD either be registered in the IANA JSON Web
Signature and Encryption Algorithms registry Section 6.1 or be a URI Signature and Encryption Algorithms registry Section 6.1 or be a
that contains a Collision Resistant Namespace. In particular, it is value that contains a Collision Resistant Namespace. In particular,
permissible to use the algorithm identifiers defined in XML it is permissible to use the algorithm identifiers defined in XML
Encryption [W3C.REC-xmlenc-core-20021210], XML Encryption 1.1 Encryption [W3C.REC-xmlenc-core-20021210], XML Encryption 1.1
[W3C.CR-xmlenc-core1-20120313], and related specifications as "alg" [W3C.CR-xmlenc-core1-20120313], and related specifications as "alg"
and "enc" values. and "enc" values.
As indicated by the common registry, JWSs and JWEs share a common As indicated by the common registry, JWSs and JWEs share a common
"alg" value space. The values used by the two specifications MUST be "alg" value space. The values used by the two specifications MUST be
distinct, as the "alg" value MAY be used to determine whether the distinct, as the "alg" value MAY be used to determine whether the
object is a JWS or JWE. object is a JWS or JWE.
Likewise, additional reserved header parameter names MAY be defined Likewise, additional reserved Header Parameter Names MAY be defined
via the IANA JSON Web Signature and Encryption Header Parameters via the IANA JSON Web Signature and Encryption Header Parameters
registry [JWS]. As indicated by the common registry, JWSs and JWEs registry [JWS]. As indicated by the common registry, JWSs and JWEs
share a common header parameter space; when a parameter is used by share a common header parameter space; when a parameter is used by
both specifications, its usage must be compatible between the both specifications, its usage must be compatible between the
specifications. specifications.
5. Cryptographic Algorithms for JWK 5. Cryptographic Algorithms for JWK
A JSON Web Key (JWK) [JWK] is a JavaScript Object Notation (JSON) A JSON Web Key (JWK) [JWK] is a JavaScript Object Notation (JSON)
[RFC4627] data structure that represents a public key. A JSON Web [RFC4627] data structure that represents a public key. A JSON Web
Key Set (JWK Set) is a JSON data structure for representing a set of Key Set (JWK Set) is a JSON data structure for representing a set of
JWKs. This section specifies a set of algorithm families to be used JWKs. This section specifies a set of key types to be used for those
for those public keys and the algorithm family specific parameters public keys and the key type specific parameters for representing
for representing those keys. those keys.
5.1. "alg" (Algorithm Family) Parameter Values for JWK 5.1. "kty" (Key Type) Parameter Values for JWK
The table below is the set of "alg" (algorithm family) parameter The table below is the set of "kty" (key type) parameter values that
values that are defined by this specification for use in JWKs. are defined by this specification for use in JWKs.
+-----------------+-------------------------+-----------------------+ +-----------------+------------------------+------------------------+
| alg Parameter | Algorithm Family | Implementation | | kty Parameter | Key Type | Implementation |
| Value | | Requirements | | Value | | Requirements |
+-----------------+-------------------------+-----------------------+ +-----------------+------------------------+------------------------+
| EC | Elliptic Curve [DSS] | RECOMMENDED+ | | EC | Elliptic Curve [DSS] | RECOMMENDED+ |
| | key family | | | | key type | |
| RSA | RSA [RFC3447] key | REQUIRED | | RSA | RSA [RFC3447] key type | REQUIRED |
| | family | | +-----------------+------------------------+------------------------+
+-----------------+-------------------------+-----------------------+
All the names are short because a core goal of JWK is for the All the names are short because a core goal of JWK is for the
representations to be compact. However, there is no a priori length representations to be compact. However, there is no a priori length
restriction on "alg" values. restriction on "kty" values.
The use of "+" in the Implementation Requirements indicates that the The use of "+" in the Implementation Requirements indicates that the
requirement strength is likely to be increased in a future version of requirement strength is likely to be increased in a future version of
the specification. the specification.
5.2. JWK Parameters for Elliptic Curve Keys 5.2. JWK Parameters for Elliptic Curve Keys
JWKs can represent Elliptic Curve [DSS] keys. In this case, the JWKs can represent Elliptic Curve [DSS] keys. In this case, the
"alg" member value MUST be "EC". Furthermore, these additional "kty" member value MUST be "EC". Furthermore, these additional
members MUST be present: members MUST be present:
5.2.1. "crv" (Curve) Parameter 5.2.1. "crv" (Curve) Parameter
The "crv" (curve) member identifies the cryptographic curve used with The "crv" (curve) member identifies the cryptographic curve used with
the key. Curve values from [DSS] used by this specification are: the key. Curve values from [DSS] used by this specification are:
o "P-256" o "P-256"
o "P-384" o "P-384"
skipping to change at page 22, line 32 skipping to change at page 22, line 50
The "y" (y coordinate) member contains the y coordinate for the The "y" (y coordinate) member contains the y coordinate for the
elliptic curve point. It is represented as the base64url encoding of elliptic curve point. It is represented as the base64url encoding of
the coordinate's big endian representation as a byte array. The the coordinate's big endian representation as a byte array. The
array representation MUST not be shortened to omit any leading zero array representation MUST not be shortened to omit any leading zero
bytes contained in the value. For instance, when representing 521 bytes contained in the value. For instance, when representing 521
bit integers, the byte array to be base64url encoded MUST contain 66 bit integers, the byte array to be base64url encoded MUST contain 66
bytes, including any leading zero bytes. bytes, including any leading zero bytes.
5.3. JWK Parameters for RSA Keys 5.3. JWK Parameters for RSA Keys
JWKs can represent RSA [RFC3447] keys. In this case, the "alg" JWKs can represent RSA [RFC3447] keys. In this case, the "kty"
member value MUST be "RSA". Furthermore, these additional members member value MUST be "RSA". Furthermore, these additional members
MUST be present: MUST be present:
5.3.1. "n" (Modulus) Parameter 5.3.1. "n" (Modulus) Parameter
The "n" (modulus) member contains the modulus value for the RSA The "n" (modulus) member contains the modulus value for the RSA
public key. It is represented as the base64url encoding of the public key. It is represented as the base64url encoding of the
value's unsigned big endian representation as a byte array. The value's unsigned big endian representation as a byte array. The
array representation MUST not be shortened to omit any leading zero array representation MUST not be shortened to omit any leading zero
bytes. For instance, when representing 2048 bit integers, the byte bytes. For instance, when representing 2048 bit integers, the byte
skipping to change at page 23, line 8 skipping to change at page 23, line 26
5.3.2. "e" (Exponent) Parameter 5.3.2. "e" (Exponent) Parameter
The "e" (exponent) member contains the exponent value for the RSA The "e" (exponent) member contains the exponent value for the RSA
public key. It is represented as the base64url encoding of the public key. It is represented as the base64url encoding of the
value's unsigned big endian representation as a byte array. The value's unsigned big endian representation as a byte array. The
array representation MUST utilize the minimum number of bytes to array representation MUST utilize the minimum number of bytes to
represent the value. For instance, when representing the value represent the value. For instance, when representing the value
65537, the byte array to be base64url encoded MUST consist of the 65537, the byte array to be base64url encoded MUST consist of the
three bytes [1, 0, 1]. three bytes [1, 0, 1].
5.4. Additional Key Algorithm Families and Parameters 5.4. Additional Key Types and Parameters
Public keys using additional algorithm families MAY be represented Public keys using additional key types MAY be represented using JWK
using JWK data structures with corresponding "alg" (algorithm family) data structures with corresponding "kty" (key type) parameter values
parameter values being defined to refer to them. New "alg" parameter being defined to refer to them. New "kty" parameter values SHOULD
values SHOULD either be registered in the IANA JSON Web Key Algorithm either be registered in the IANA JSON Web Key Types registry
Families registry Section 6.2 or be a URI that contains a Collision Section 6.2 or be a value that contains a Collision Resistant
Resistant Namespace. Namespace.
Likewise, parameters for representing keys for additional algorithm Likewise, parameters for representing keys for additional key types
families or additional key properties SHOULD either be registered in or additional key properties SHOULD either be registered in the IANA
the IANA JSON Web Key Parameters registry [JWK] or be a URI that JSON Web Key Parameters registry [JWK] or be a value that contains a
contains a Collision Resistant Namespace. Collision Resistant Namespace.
6. IANA Considerations 6. IANA Considerations
The following registration procedure is used for all the registries The following registration procedure is used for all the registries
established by this specification. established by this specification.
Values are registered with a Specification Required [RFC5226] after a Values are registered with a Specification Required [RFC5226] after a
two-week review period on the [TBD]@ietf.org mailing list, on the two-week review period on the [TBD]@ietf.org mailing list, on the
advice of one or more Designated Experts. However, to allow for the advice of one or more Designated Experts. However, to allow for the
allocation of values prior to publication, the Designated Expert(s) allocation of values prior to publication, the Designated Expert(s)
skipping to change at page 27, line 46 skipping to change at page 28, line 14
o Implementation Requirements: RECOMMENDED o Implementation Requirements: RECOMMENDED
o Change Controller: IETF o Change Controller: IETF
o Specification Document(s): Section 4.2 of [[ this document ]] o Specification Document(s): Section 4.2 of [[ this document ]]
o Algorithm Name: "A256GCM" o Algorithm Name: "A256GCM"
o Algorithm Usage Location(s): "enc" o Algorithm Usage Location(s): "enc"
o Implementation Requirements: RECOMMENDED o Implementation Requirements: RECOMMENDED
o Change Controller: IETF o Change Controller: IETF
o Specification Document(s): Section 4.2 of [[ this document ]] o Specification Document(s): Section 4.2 of [[ this document ]]
6.2. JSON Web Key Algorithm Families Registry 6.2. JSON Web Key Types Registry
This specification establishes the IANA JSON Web Key Algorithm This specification establishes the IANA JSON Web Key Types registry
Families registry for values of the JWK "alg" (algorithm family) for values of the JWK "kty" (key type) parameter. The registry
parameter. The registry records the "alg" value and a reference to records the "kty" value and a reference to the specification that
the specification that defines it. This specification registers the defines it. This specification registers the values defined in
values defined in Section 5.1. Section 5.1.
6.2.1. Registration Template 6.2.1. Registration Template
"alg" Parameter Value: "kty" Parameter Value:
The name requested (e.g., "example"). This name is case The name requested (e.g., "example"). This name is case
sensitive. Names that match other registered names in a case sensitive. Names that match other registered names in a case
insensitive manner SHOULD NOT be accepted. insensitive manner SHOULD NOT be accepted.
Change Controller: Change Controller:
For Standards Track RFCs, state "IETF". For others, give the name For Standards Track RFCs, state "IETF". For others, give the name
of the responsible party. Other details (e.g., postal address, of the responsible party. Other details (e.g., postal address,
email address, home page URI) may also be included. email address, home page URI) may also be included.
Implementation Requirements: Implementation Requirements:
skipping to change at page 28, line 35 skipping to change at page 29, line 7
in a future version of the specification. in a future version of the specification.
Specification Document(s): Specification Document(s):
Reference to the document(s) that specify the parameter, Reference to the document(s) that specify the parameter,
preferably including URI(s) that can be used to retrieve copies of preferably including URI(s) that can be used to retrieve copies of
the document(s). An indication of the relevant sections may also the document(s). An indication of the relevant sections may also
be included but is not required. be included but is not required.
6.2.2. Initial Registry Contents 6.2.2. Initial Registry Contents
o "alg" Parameter Value: "EC" o "kty" Parameter Value: "EC"
o Implementation Requirements: RECOMMENDED+ o Implementation Requirements: RECOMMENDED+
o Change Controller: IETF o Change Controller: IETF
o Specification Document(s): Section 5.1 of [[ this document ]] o Specification Document(s): Section 5.1 of [[ this document ]]
o "alg" Parameter Value: "RSA" o "kty" Parameter Value: "RSA"
o Implementation Requirements: REQUIRED o Implementation Requirements: REQUIRED
o Change Controller: IETF o Change Controller: IETF
o Specification Document(s): Section 5.1 of [[ this document ]] o Specification Document(s): Section 5.1 of [[ this document ]]
6.3. JSON Web Key Parameters Registration 6.3. JSON Web Key Parameters Registration
This specification registers the parameter names defined in Sections This specification registers the parameter names defined in Sections
5.2 and 5.3 in the IANA JSON Web Key Parameters registry [JWK]. 5.2 and 5.3 in the IANA JSON Web Key Parameters registry [JWK].
6.3.1. Registry Contents 6.3.1. Registry Contents
skipping to change at page 29, line 31 skipping to change at page 29, line 48
o Specification Document(s): Section 5.3.1 of [[ this document ]] o Specification Document(s): Section 5.3.1 of [[ this document ]]
o Parameter Name: "e" o Parameter Name: "e"
o Change Controller: IETF o Change Controller: IETF
o Specification Document(s): Section 5.3.2 of [[ this document ]] o Specification Document(s): Section 5.3.2 of [[ this document ]]
7. Security Considerations 7. Security Considerations
All of the security issues faced by any cryptographic application All of the security issues faced by any cryptographic application
must be faced by a JWS/JWE/JWK agent. Among these issues are must be faced by a JWS/JWE/JWK agent. Among these issues are
protecting the user's private key, preventing various attacks, and protecting the user's private and symmetric keys, preventing various
helping the user avoid mistakes such as inadvertently encrypting a attacks, and helping the user avoid mistakes such as inadvertently
message for the wrong recipient. The entire list of security encrypting a message for the wrong recipient. The entire list of
considerations is beyond the scope of this document, but some security considerations is beyond the scope of this document, but
significant concerns are listed here. some significant concerns are listed here.
The security considerations in [AES], [DSS], [JWE], [JWK], [JWS], The security considerations in [AES], [DSS], [JWE], [JWK], [JWS],
[NIST.800-38A], [NIST.800-38D], [NIST.800-56A], [RFC2104], [RFC3394], [NIST.800-38A], [NIST.800-38D], [NIST.800-56A], [RFC2104], [RFC3394],
[RFC3447], [RFC5116], [RFC6090], and [SHS] apply to this [RFC3447], [RFC5116], [RFC6090], and [SHS] apply to this
specification. specification.
Eventually the algorithms and/or key sizes currently described in Eventually the algorithms and/or key sizes currently described in
this specification will no longer be considered sufficiently secure this specification will no longer be considered sufficiently secure
and will be removed. Therefore, implementers and deployments must be and will be removed. Therefore, implementers and deployments must be
prepared for this eventuality. prepared for this eventuality.
skipping to change at page 30, line 43 skipping to change at page 31, line 14
8.1. Normative References 8.1. Normative References
[AES] National Institute of Standards and Technology (NIST), [AES] National Institute of Standards and Technology (NIST),
"Advanced Encryption Standard (AES)", FIPS PUB 197, "Advanced Encryption Standard (AES)", FIPS PUB 197,
November 2001. November 2001.
[DSS] National Institute of Standards and Technology, "Digital [DSS] National Institute of Standards and Technology, "Digital
Signature Standard (DSS)", FIPS PUB 186-3, June 2009. Signature Standard (DSS)", FIPS PUB 186-3, June 2009.
[JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web [JWE] Jones, M., Rescorla, E., and J. Hildebrand, "JSON Web
Encryption (JWE)", November 2012. Encryption (JWE)", draft-ietf-jose-json-web-encryption
(work in progress), December 2012.
[JWK] Jones, M., "JSON Web Key (JWK)", November 2012. [JWK] Jones, M., "JSON Web Key (JWK)",
draft-ietf-jose-json-web-key (work in progress),
December 2012.
[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web
Signature (JWS)", November 2012. Signature (JWS)", draft-ietf-jose-json-web-signature (work
in progress), December 2012.
[NIST.800-38A] [NIST.800-38A]
National Institute of Standards and Technology (NIST), National Institute of Standards and Technology (NIST),
"Recommendation for Block Cipher Modes of Operation", "Recommendation for Block Cipher Modes of Operation",
NIST PUB 800-38A, December 2001. NIST PUB 800-38A, December 2001.
[NIST.800-38D] [NIST.800-38D]
National Institute of Standards and Technology (NIST), National Institute of Standards and Technology (NIST),
"Recommendation for Block Cipher Modes of Operation: "Recommendation for Block Cipher Modes of Operation:
Galois/Counter Mode (GCM) and GMAC", NIST PUB 800-38D, Galois/Counter Mode (GCM) and GMAC", NIST PUB 800-38D,
skipping to change at page 32, line 43 skipping to change at page 33, line 18
[RFC3275] Eastlake, D., Reagle, J., and D. Solo, "(Extensible Markup [RFC3275] Eastlake, D., Reagle, J., and D. Solo, "(Extensible Markup
Language) XML-Signature Syntax and Processing", RFC 3275, Language) XML-Signature Syntax and Processing", RFC 3275,
March 2002. March 2002.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, Unique IDentifier (UUID) URN Namespace", RFC 4122,
July 2005. July 2005.
[W3C.CR-xmldsig-core2-20120124] [W3C.CR-xmldsig-core2-20120124]
Reagle, J., Solo, D., Datta, P., Hirsch, F., Eastlake, D., Yiu, K., Solo, D., Eastlake, D., Datta, P., Hirsch, F.,
Cantor, S., Roessler, T., and K. Yiu, "XML Signature Reagle, J., Cantor, S., and T. Roessler, "XML Signature
Syntax and Processing Version 2.0", World Wide Web Syntax and Processing Version 2.0", World Wide Web
Consortium CR CR-xmldsig-core2-20120124, January 2012, Consortium CR CR-xmldsig-core2-20120124, January 2012,
<http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124>. <http://www.w3.org/TR/2012/CR-xmldsig-core2-20120124>.
[W3C.CR-xmlenc-core1-20120313] [W3C.CR-xmlenc-core1-20120313]
Eastlake, D., Reagle, J., Roessler, T., and F. Hirsch, Eastlake, D., Reagle, J., Roessler, T., and F. Hirsch,
"XML Encryption Syntax and Processing Version 1.1", World "XML Encryption Syntax and Processing Version 1.1", World
Wide Web Consortium CR CR-xmlenc-core1-20120313, Wide Web Consortium CR CR-xmlenc-core1-20120313,
March 2012, March 2012,
<http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313>. <http://www.w3.org/TR/2012/CR-xmlenc-core1-20120313>.
skipping to change at page 37, line 16 skipping to change at page 37, line 44
| 256 bit | | | | | 256 bit | | | |
| keys | | | | | keys | | | |
+----------+--------+--------------------------+--------------------+ +----------+--------+--------------------------+--------------------+
Appendix C. Acknowledgements Appendix C. Acknowledgements
Solutions for signing and encrypting JSON content were previously Solutions for signing and encrypting JSON content were previously
explored by Magic Signatures [MagicSignatures], JSON Simple Sign explored by Magic Signatures [MagicSignatures], JSON Simple Sign
[JSS], Canvas Applications [CanvasApp], JSON Simple Encryption [JSE], [JSS], Canvas Applications [CanvasApp], JSON Simple Encryption [JSE],
and JavaScript Message Security Format [I-D.rescorla-jsms], all of and JavaScript Message Security Format [I-D.rescorla-jsms], all of
which influenced this draft. Dirk Balfanz, John Bradley, Yaron Y. which influenced this draft.
Goland, John Panzer, Nat Sakimura, and Paul Tarjan all made
significant contributions to the design of this specification and its This specification is the work of the JOSE Working Group, which
related specifications. includes dozens of active and dedicated participants. In particular,
the following individuals contributed ideas, feedback, and wording
that influenced this specification:
Dirk Balfanz, Richard Barnes, John Bradley, Brian Campbell, Breno de
Medeiros, Yaron Y. Goland, Dick Hardt, Jeff Hodges, Edmund Jay, James
Manger, Tony Nadalin, Axel Nennker, John Panzer, Emmanuel Raviart,
Nat Sakimura, Jim Schaad, Hannes Tschofenig, and Sean Turner.
Jim Schaad and Karen O'Donoghue chaired the JOSE working group and Jim Schaad and Karen O'Donoghue chaired the JOSE working group and
Sean Turner and Stephen Farrell served as Security area directors Sean Turner and Stephen Farrell served as Security area directors
during the creation of this specification. during the creation of this specification.
Appendix D. Open Issues Appendix D. Open Issues
[[ to be removed by the RFC editor before publication as an RFC ]] [[ to be removed by the RFC editor before publication as an RFC ]]
The following items remain to be considered or done in this draft: The following items remain to be considered or done in this draft:
o No known open issues. o No known open issues.
Appendix E. Document History Appendix E. Document History
[[ to be removed by the RFC editor before publication as an RFC ]] [[ to be removed by the RFC editor before publication as an RFC ]]
-08
o Changed the name of the JWK key type parameter from "alg" to
"kty".
o Replaced uses of the term "AEAD" with "Authenticated Encryption",
since the term AEAD in the RFC 5116 sense implied the use of a
particular data representation, rather than just referring to the
class of algorithms that perform authenticated encryption with
associated data.
o Applied editorial improvements suggested by Jeff Hodges. Many of
these simplified the terminology used.
o Added seriesInfo information to Internet Draft references.
-07 -07
o Added a data length prefix to PartyUInfo and PartyVInfo values. o Added a data length prefix to PartyUInfo and PartyVInfo values.
o Changed the name of the JWK RSA modulus parameter from "mod" to o Changed the name of the JWK RSA modulus parameter from "mod" to
"n" and the name of the JWK RSA exponent parameter from "xpo" to "n" and the name of the JWK RSA exponent parameter from "xpo" to
"e", so that the identifiers are the same as those used in RFC "e", so that the identifiers are the same as those used in RFC
3447. 3447.
o Made several local editorial changes to clean up loose ends left o Made several local editorial changes to clean up loose ends left
over from to the decision to only support block encryption methods over from to the decision to only support block encryption methods
providing integrity. providing integrity.
-06 -06
o Removed the "int" and "kdf" parameters and defined the new o Removed the "int" and "kdf" parameters and defined the new
composite AEAD algorithms "A128CBC+HS256" and "A256CBC+HS512" to composite Authenticated Encryption algorithms "A128CBC+HS256" and
replace the former uses of AES CBC, which required the use of "A256CBC+HS512" to replace the former uses of AES CBC, which
separate integrity and key derivation functions. required the use of separate integrity and key derivation
functions.
o Included additional values in the Concat KDF calculation -- the o Included additional values in the Concat KDF calculation -- the
desired output size and the algorithm value, and optionally desired output size and the algorithm value, and optionally
PartyUInfo and PartyVInfo values. Added the optional header PartyUInfo and PartyVInfo values. Added the optional header
parameters "apu" (agreement PartyUInfo), "apv" (agreement parameters "apu" (agreement PartyUInfo), "apv" (agreement
PartyVInfo), "epu" (encryption PartyUInfo), and "epv" (encryption PartyVInfo), "epu" (encryption PartyUInfo), and "epv" (encryption
PartyVInfo). PartyVInfo).
o Changed the name of the JWK RSA exponent parameter from "exp" to o Changed the name of the JWK RSA exponent parameter from "exp" to
"xpo" so as to allow the potential use of the name "exp" for a "xpo" so as to allow the potential use of the name "exp" for a
 End of changes. 60 change blocks. 
130 lines changed or deleted 172 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/