draft-ietf-jose-jwk-thumbprint-00.txt   draft-ietf-jose-jwk-thumbprint-01.txt 
JOSE Working Group M. Jones JOSE Working Group M. Jones
Internet-Draft Microsoft Internet-Draft Microsoft
Intended status: Standards Track November 10, 2014 Intended status: Standards Track N. Sakimura
Expires: May 14, 2015 Expires: July 26, 2015 NRI
January 22, 2015
JSON Web Key (JWK) Thumbprint JSON Web Key (JWK) Thumbprint
draft-ietf-jose-jwk-thumbprint-00 draft-ietf-jose-jwk-thumbprint-01
Abstract Abstract
This specification defines a means of computing a thumbprint value This specification defines a means of computing a thumbprint value
(a.k.a. digest) of JSON Web Key (JWK) objects analogous to the "x5t" (a.k.a. digest) of JSON Web Key (JWK) objects analogous to the "x5t"
(X.509 Certificate SHA-1 Thumbprint) value defined for X.509 (X.509 Certificate SHA-1 Thumbprint) value defined for X.509
certificate objects. This specification also registers the new JSON certificate objects. This specification also registers the new JSON
Web Signature (JWS) and JSON Web Encryption (JWE) Header Parameters Web Signature (JWS) and JSON Web Encryption (JWE) Header Parameters
and the new JSON Web Key (JWK) member name "jkt" (JWK SHA-256 and the new JSON Web Key (JWK) member name "jkt" (JWK SHA-256
Thumbprint) for holding these values. Thumbprint) for holding these values.
skipping to change at page 1, line 36 skipping to change at page 1, line 37
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 14, 2015. This Internet-Draft will expire on July 26, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 17 skipping to change at page 2, line 18
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3 1.1. Notational Conventions . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. JSON Web Key (JWK) Thumbprint . . . . . . . . . . . . . . . . 3 3. JSON Web Key (JWK) Thumbprint . . . . . . . . . . . . . . . . 3
3.1. Example JWK Thumbprint Computation . . . . . . . . . . . . 4 3.1. Example JWK Thumbprint Computation . . . . . . . . . . . . 4
3.2. JWK Members Used in the Thumbprint Computation . . . . . . 5 3.2. JWK Members Used in the Thumbprint Computation . . . . . . 5
3.2.1. JWK Thumbprint of a Private Key . . . . . . . . . . . 6 3.2.1. JWK Thumbprint of a Private Key . . . . . . . . . . . 6
3.2.2. Why Not Include Optional Members? . . . . . . . . . . 6 3.2.2. Why Not Include Optional Members? . . . . . . . . . . 6
3.3. Order and Representation of Members in Hash Input . . . . 6 3.3. Order and Representation of Members in Hash Input . . . . 7
3.4. JWK Thumbprints of Any Keys . . . . . . . . . . . . . . . 7 3.4. JWK Thumbprints of Keys Not in JWK Format . . . . . . . . 7
4. "jkt" Member Definitions . . . . . . . . . . . . . . . . . . . 7 4. "jkt" Member Definitions . . . . . . . . . . . . . . . . . . . 8
4.1. "jkt" (JWK SHA-256 Thumbprint) JWS Header Parameter . . . 7 4.1. "jkt" (JWK SHA-256 Thumbprint) JWS Header Parameter . . . 8
4.2. "jkt" (JWK SHA-256 Thumbprint) JWE Header Parameter . . . 7 4.2. "jkt" (JWK SHA-256 Thumbprint) JWE Header Parameter . . . 8
4.3. "jkt" (JWK SHA-256 Thumbprint) JWK Parameter . . . . . . . 8 4.3. "jkt" (JWK SHA-256 Thumbprint) JWK Parameter . . . . . . . 8
4.4. Possible Future Alternative Thumbprint Computations . . . 8 4.4. Possible Future Alternative Thumbprint Computations . . . 8
5. Practical JSON and Unicode Considerations . . . . . . . . . . 8 5. Practical JSON and Unicode Considerations . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6.1. JWS and JWE Header Parameter Registration . . . . . . . . 9 6.1. JWS and JWE Header Parameter Registration . . . . . . . . 9
6.1.1. Registry Contents . . . . . . . . . . . . . . . . . . 9 6.1.1. Registry Contents . . . . . . . . . . . . . . . . . . 10
6.2. JSON Web Key Parameters Registration . . . . . . . . . . . 9 6.2. JSON Web Key Parameters Registration . . . . . . . . . . . 10
6.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 9 6.2.1. Registry Contents . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
8. Normative References . . . . . . . . . . . . . . . . . . . . . 10 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 10 8.1. Normative References . . . . . . . . . . . . . . . . . . . 11
Appendix B. Document History . . . . . . . . . . . . . . . . . . 11 8.2. Informative References . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11
Appendix B. Document History . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
This specification defines a means of computing a thumbprint value This specification defines a means of computing a thumbprint value
(a.k.a. digest) of JSON Web Key (JWK) [JWK] objects analogous to the (a.k.a. digest) of JSON Web Key (JWK) [JWK] objects analogous to the
"x5t" (X.509 Certificate SHA-1 Thumbprint) value defined for X.509 "x5t" (X.509 Certificate SHA-1 Thumbprint) value defined for X.509
certificate objects. This specification also registers the new JSON certificate objects. This specification also registers the new JSON
Web Signature (JWS) [JWS] and JSON Web Encryption (JWE) [JWE] Header Web Signature (JWS) [JWS] and JSON Web Encryption (JWE) [JWE] Header
Parameters and the new JSON Web Key (JWK) [JWK] member name "jkt" Parameters and the new JSON Web Key (JWK) [JWK] member name "jkt"
(JWK SHA-256 Thumbprint) for holding these values. (JWK SHA-256 Thumbprint) for holding these values.
skipping to change at page 3, line 36 skipping to change at page 3, line 36
(JWE) [JWE], and JSON Web Algorithms (JWA) [JWA] specifications. (JWE) [JWE], and JSON Web Algorithms (JWA) [JWA] specifications.
This term is defined by this specification: This term is defined by this specification:
JWK Thumbprint JWK Thumbprint
The digest value for a key that is the subject of this The digest value for a key that is the subject of this
specification. specification.
3. JSON Web Key (JWK) Thumbprint 3. JSON Web Key (JWK) Thumbprint
This specification defines the thumbprint of a JSON Web Key (JWK) This specification defines the thumbprint of a JSON Web Key (JWK) as
value as being a function of the REQUIRED members of the key's JWK being a function of the REQUIRED members of the key's JWK
representation. Specifically, this function is the SHA-256 hash of representation and a hash function. Specifically, for a hash
the octets of the UTF-8 representation of a JSON object [RFC7159] function H, this function is the hash with H of the octets of the
constructed containing only the REQUIRED members of a JWK UTF-8 representation of a JSON object [RFC7159] constructed
representing the key and with no white space or line breaks before or containing only the REQUIRED members of a JWK representing the key
after any syntactic elements and with the REQUIRED members ordered and with no white space or line breaks before or after any syntactic
lexicographically by the Unicode code points of the member names. elements and with the REQUIRED members ordered lexicographically by
This JSON object is itself a legal JWK representation of the key the Unicode [UNICODE] code points of the member names. This JSON
value. The details of this computation are further described in object is itself a legal JWK representation of the key. The details
subsequent sections. of this computation are further described in subsequent sections.
3.1. Example JWK Thumbprint Computation 3.1. Example JWK Thumbprint Computation
This section demonstrates the JWK Thumbprint computation for the JWK This section demonstrates the JWK Thumbprint computation for the JWK
below (with long lines broken for display purposes only): below (with long lines broken for display purposes only):
{ {
"kty": "RSA", "kty": "RSA",
"n": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx4cbbfAAt "n": "0vx7agoebGcQSuuPiLJXZptN9nndrQmbXEps2aiAFbWhM78LhWx4cbbfAAt
VT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMstn6 VT86zwu1RK7aPFFxuhDR1L6tSoc_BJECPebWKRXjBZCiFV4n3oknjhMstn6
skipping to change at page 5, line 27 skipping to change at page 5, line 27
55, 100, 48, 122, 103, 100, 65, 90, 72, 122, 117, 54, 113, 77, 81, 55, 100, 48, 122, 103, 100, 65, 90, 72, 122, 117, 54, 113, 77, 81,
118, 82, 76, 53, 104, 97, 106, 114, 110, 49, 110, 57, 49, 67, 98, 79, 118, 82, 76, 53, 104, 97, 106, 114, 110, 49, 110, 57, 49, 67, 98, 79,
112, 98, 73, 83, 68, 48, 56, 113, 78, 76, 121, 114, 100, 107, 116, 112, 98, 73, 83, 68, 48, 56, 113, 78, 76, 121, 114, 100, 107, 116,
45, 98, 70, 84, 87, 104, 65, 73, 52, 118, 77, 81, 70, 104, 54, 87, 45, 98, 70, 84, 87, 104, 65, 73, 52, 118, 77, 81, 70, 104, 54, 87,
101, 90, 117, 48, 102, 77, 52, 108, 70, 100, 50, 78, 99, 82, 119, 101, 90, 117, 48, 102, 77, 52, 108, 70, 100, 50, 78, 99, 82, 119,
114, 51, 88, 80, 107, 115, 73, 78, 72, 97, 81, 45, 71, 95, 120, 66, 114, 51, 88, 80, 107, 115, 73, 78, 72, 97, 81, 45, 71, 95, 120, 66,
110, 105, 73, 113, 98, 119, 48, 76, 115, 49, 106, 70, 52, 52, 45, 99, 110, 105, 73, 113, 98, 119, 48, 76, 115, 49, 106, 70, 52, 52, 45, 99,
115, 70, 67, 117, 114, 45, 107, 69, 103, 85, 56, 97, 119, 97, 112, 115, 70, 67, 117, 114, 45, 107, 69, 103, 85, 56, 97, 119, 97, 112,
74, 122, 75, 110, 113, 68, 75, 103, 119, 34, 125] 74, 122, 75, 110, 113, 68, 75, 103, 119, 34, 125]
The JWK Thumbprint value is the SHA-256 hash of these octets, Using SHA-256 [SHS] as the hash function H, the JWK SHA-256
specifically: Thumbprint value is the SHA-256 hash of these octets, specifically:
[55, 54, 203, 177, 120, 124, 184, 48, 156, 119, 238, 140, 55, 5, 197, [55, 54, 203, 177, 120, 124, 184, 48, 156, 119, 238, 140, 55, 5, 197,
225, 111, 251, 158, 133, 151, 21, 144, 31, 30, 76, 89, 177, 17, 130, 225, 111, 251, 158, 133, 151, 21, 144, 31, 30, 76, 89, 177, 17, 130,
245, 123] 245, 123]
The base64url encoding of this JWK Thumbprint value (which would be The base64url encoding [JWS] of this JWK SHA-256 Thumbprint value
used in the "jkt" members registered below) is: (which would be used in the "jkt" members registered below) is:
NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs NzbLsXh8uDCcd-6MNwXF4W_7noWXFZAfHkxZsRGC9Xs
3.2. JWK Members Used in the Thumbprint Computation 3.2. JWK Members Used in the Thumbprint Computation
Only the REQUIRED members of a key's representation are used when Only the REQUIRED members of a key's representation are used when
computing its JWK Thumbprint value. As defined in JSON Web Key (JWK) computing its JWK Thumbprint value. As defined in JSON Web Key (JWK)
[JWK] and JSON Web Algorithms (JWA) [JWA], the REQUIRED members of an [JWK] and JSON Web Algorithms (JWA) [JWA], the REQUIRED members of an
elliptic curve public key, in lexicographic order, are: elliptic curve public key for the curves specified in Section 6.2.1.1
of [JWK], in lexicographic order, are:
o "crv" o "crv"
o "kty" o "kty"
o "x" o "x"
o "y" o "y"
the REQUIRED members of an RSA public key, in lexicographic order, the REQUIRED members of an RSA public key, in lexicographic order,
are: are:
o "e" o "e"
skipping to change at page 6, line 30 skipping to change at page 6, line 33
3.2.1. JWK Thumbprint of a Private Key 3.2.1. JWK Thumbprint of a Private Key
The JWK Thumbprint of a private key is computed as the JWK Thumbprint The JWK Thumbprint of a private key is computed as the JWK Thumbprint
of the corresponding public key. This has the intentional benefit of the corresponding public key. This has the intentional benefit
that the same JWK Thumbprint value can be computed both by parties that the same JWK Thumbprint value can be computed both by parties
using either the public or private key. The JWK Thumbprint can then using either the public or private key. The JWK Thumbprint can then
be used to refer to both keys of the key pair. Application context be used to refer to both keys of the key pair. Application context
can be used to determine whether the public or the private key is the can be used to determine whether the public or the private key is the
one being referred to by the JWK Thumbprint. one being referred to by the JWK Thumbprint.
This specification defines the method of computing JWK Thumbprints of
private keys for interoperability reasons -- so that different
implementations computing JWK Thumbprints of private keys will
produce the same result.
3.2.2. Why Not Include Optional Members? 3.2.2. Why Not Include Optional Members?
OPTIONAL members of JWKs are intentionally not included in the JWK OPTIONAL members of JWKs are intentionally not included in the JWK
Thumbprint computation so that their absence or presence in the JWK Thumbprint computation so that their absence or presence in the JWK
doesn't alter the resulting value. The JWK Thumbprint value is a doesn't alter the resulting value. The JWK Thumbprint value is a
digest of the key value itself -- not of additional data that may digest of the key value itself -- not of additional data that may
also accompany the key. also accompany the key.
OPTIONAL members are not included so that the JWK Thumbprint refers
to a key -- not a key with an associated set of key attributes. This
has the benefit that while in different application contexts
different subsets of attributes about the key might or might not be
included in the JWK, the JWK Thumbprint of the key remains the same
regardless of which optional attributes are present. Different kinds
of thumbprints could be defined by other specifications that might
include some or all additional JWK members, should use cases arise
where such different kinds of thumbprints would be useful. See
Section 9.1 of [JWK] for notes on some ways to cryptographically bind
attributes to a key.
3.3. Order and Representation of Members in Hash Input 3.3. Order and Representation of Members in Hash Input
The REQUIRED members in the input to the SHA-256 hash function are The REQUIRED members in the input to the hash function are ordered
ordered lexicographically by the Unicode code points of the member lexicographically by the Unicode code points of the member names.
names.
Characters in member names and member values MUST be represented Characters in member names and member values MUST be represented
without being escaped. This means that thumbprints of JWK values without being escaped. This means that thumbprints of JWKs that
that require such characters are not defined by this specification. require such characters are not defined by this specification. (This
(This is not expected to limit the applicability of this is not expected to limit the applicability of this specification, in
specification, in practice, as the REQUIRED members of JWK practice, as the REQUIRED members of JWK representations are not
representations are not expected to use any of these characters.) expected to use any of these characters.) The characters specified
The characters specified as requiring escaping by Section 7 of as requiring escaping by Section 7 of [RFC7159] are quotation mark,
[RFC7159] are quotation mark, reverse solidus (a.k.a. backslash), and reverse solidus (a.k.a. backslash), and the control characters U+0000
the control characters U+0000 through U+001F. through U+001F.
If the JWK key type uses members whose values are themselves JSON If the JWK key type uses members whose values are themselves JSON
objects (as of the time of this writing, none are defined that do), objects (as of the time of this writing, none are defined that do),
the members of those objects must likewise be lexicographically the members of those objects must likewise be lexicographically
ordered. ordered.
If the JWK key type uses members whose values are JSON numbers (as of If the JWK key type uses members whose values are JSON numbers (as of
the time of this writing, none are defined that do), if the numbers the time of this writing, none are defined that do), if the numbers
are integers, they MUST be represented as a JSON number as defined in are integers, they MUST be represented as a JSON number as defined in
Section 6 of [RFC7159] without including a fraction part or exponent Section 6 of [RFC7159] without including a fraction part or exponent
part. For instance, the value "1.024e3" MUST be represented as part. For instance, the value "1.024e3" MUST be represented as
"1024". This means that thumbprints of JWK values that use numbers "1024". This means that thumbprints of JWKs that use numbers that
that are not integers are not defined by this specification. are not integers are not defined by this specification. Also, as
noted in The I-JSON Message Format [I-D.ietf-json-i-json],
implementations cannot expect an integer whose absolute value is
greater than 9007199254740991 (i.e., that is outside the range
[-(2**53)+1, (2**53)-1]) to be treated as an exact value.
See Section 5 for a discussion of further practical considerations See Section 5 for a discussion of further practical considerations
pertaining to the representation of the hash input. pertaining to the representation of the hash input.
3.4. JWK Thumbprints of Any Keys 3.4. JWK Thumbprints of Keys Not in JWK Format
Note that a key need not be in JWK format to create a JWK Thumbprint Note that a key need not be in JWK format to create a JWK Thumbprint
of it. The only prerequisites are that the JWK representation of the of it. The only prerequisites are that the JWK representation of the
key be defined and the party creating the JWK Thumbprint is in key be defined and the party creating the JWK Thumbprint is in
possession of the necessary key material. These are sufficient to possession of the necessary key material. These are sufficient to
create the hash input, as described in Section 3.3. create the hash input from the JWK representation of the key, as
described in Section 3.3.
4. "jkt" Member Definitions 4. "jkt" Member Definitions
This section defines "jkt" (JWK SHA-256 Thumbprint) members used for This section defines "jkt" (JWK SHA-256 Thumbprint) members used for
holding base64url encoded JWK Thumbprint values in JWK, JWS, and JWE holding base64url encoded JWK Thumbprint values in JWK, JWS, and JWE
objects. objects.
4.1. "jkt" (JWK SHA-256 Thumbprint) JWS Header Parameter 4.1. "jkt" (JWK SHA-256 Thumbprint) JWS Header Parameter
The "jkt" (JWK SHA-256 Thumbprint) JWS Header Parameter is a The "jkt" (JWK SHA-256 Thumbprint) JWS Header Parameter is a
skipping to change at page 8, line 18 skipping to change at page 8, line 40
encoded JWK Thumbprint (a.k.a. digest) of the JWK. If present, the encoded JWK Thumbprint (a.k.a. digest) of the JWK. If present, the
JWK Thumbprint value represented MUST have been computed from the JWK Thumbprint value represented MUST have been computed from the
other members of the JWK as described in Section 3. Use of this other members of the JWK as described in Section 3. Use of this
member is OPTIONAL. member is OPTIONAL.
4.4. Possible Future Alternative Thumbprint Computations 4.4. Possible Future Alternative Thumbprint Computations
If, in the future, JWK Thumbprints need to be computed using hash If, in the future, JWK Thumbprints need to be computed using hash
functions other than SHA-256, it is suggested that additional related functions other than SHA-256, it is suggested that additional related
JWK, JWS, and JWE parameters be defined for that purpose. For JWK, JWS, and JWE parameters be defined for that purpose. For
example, it is suggested that a new "jkt#S3-256" (X.509 Certificate example, it is suggested that a new "jkt#S3-256" (JWK SHA-3-256
Thumbprint using SHA-3-256) JWK parameter could be defined by Thumbprint) JWK parameter could be defined by registering it in the
registering it in the IANA JSON Web Key Parameters registry and the IANA JSON Web Key Parameters registry and the IANA JSON Web Signature
IANA JSON Web Signature and Encryption Header Parameters registry. and Encryption Header Parameters registry.
5. Practical JSON and Unicode Considerations 5. Practical JSON and Unicode Considerations
Implementations will almost certainly use functionality provided by Implementations will almost certainly use functionality provided by
the platform's JSON support, such as the JavaScript JSON.parse() the platform's JSON support, such as the JavaScript JSON.parse()
JSON.stringify() functions, when parsing the JWK and emitting the JSON.stringify() functions, when parsing the JWK and emitting the
JSON object used as the SHA-256 hash input. As a practical JSON object used as the hash input. As a practical consideration,
consideration, future JWK member names should be avoided for which future JWK member names should be avoided for which different
different platforms or libraries might emit different platforms or libraries might emit different representations. As of
representations. As of the time of this writing, currently all the time of this writing, currently all defined JWK member names use
defined JWK member names use only printable ASCII characters, which only printable ASCII characters, which should not exhibit this
should not exhibit this problem. problem. Note however, that JSON.stringify() cannot be counted on to
lexicographically sort the members of JSON objects, so while it may
be able to be used to emit some kinds of member values, different
code is likely to be needed to perform the sorting.
In particular, while the operation of lexicographically ordering In particular, while the operation of lexicographically ordering
member names by their Unicode code points is well defined, different member names by their Unicode code points is well defined, different
platform sort functions may produce different results for non-ASCII platform sort functions may produce different results for non-ASCII
characters, in ways that may not be obvious to developers. If characters, in ways that may not be obvious to developers. If
writers of future specifications defining new JWK Key Type values writers of future specifications defining new JWK Key Type values
choose to restrict themselves to ASCII member names (which are for choose to restrict themselves to ASCII member names (which are for
machine and not human consumption anyway), some future machine and not human consumption anyway), some future
interoperability problems might be avoided. interoperability problems might be avoided.
skipping to change at page 10, line 7 skipping to change at page 10, line 36
o Parameter Name: "jkt" o Parameter Name: "jkt"
o Parameter Description: JWK Thumbprint o Parameter Description: JWK Thumbprint
o Used with "kty" Value(s): * o Used with "kty" Value(s): *
o Parameter Information Class: Public o Parameter Information Class: Public
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 4.3 of [[ this document ]] o Specification Document(s): Section 4.3 of [[ this document ]]
7. Security Considerations 7. Security Considerations
The JSON Security Considerations and Unicode security considerations The JSON Security Considerations and Unicode Comparison Security
described in Sections 10.2 and 10.3 of JSON Web Signature (JWS) [JWS] Considerations described in Sections 10.2 and 10.3 of JSON Web
also apply to this specification. Signature (JWS) [JWS] also apply to this specification.
Also, as described in Section 5, some implementations may produce Also, as described in Section 5, some implementations may produce
incorrect results if esoteric or escaped characters are used in the incorrect results if esoteric or escaped characters are used in the
member names. The security implications of this appear to be limited member names. The security implications of this appear to be limited
for JWK Thumbprints of public keys, since while it may result in for JWK Thumbprints of public keys, since while it may result in
implementations failing to identify the intended key, it should not implementations failing to identify the intended key, it should not
leak information, since the information in a public key is already leak information, since the information in a public key is already
public in nature, by definition. public in nature, by definition.
8. Normative References A hash of a symmetric key has the potential to leak information about
the key value. Thus, the JWK Thumbprint of a symmetric key should be
typically be concealed from parties not in possession of the
symmetric key, unless in the application context, the cryptographic
hash used, such as SHA-256, is known to provide sufficient protection
against disclosure of the key value.
8. References
8.1. Normative References
[JWA] Jones, M., "JSON Web Algorithms (JWA)", [JWA] Jones, M., "JSON Web Algorithms (JWA)",
draft-ietf-jose-json-web-algorithms (work in progress), draft-ietf-jose-json-web-algorithms (work in progress),
October 2014. January 2015.
[JWE] Jones, M. and J. Hildebrand, "JSON Web Encryption (JWE)", [JWE] Jones, M. and J. Hildebrand, "JSON Web Encryption (JWE)",
draft-ietf-jose-json-web-encryption (work in progress), draft-ietf-jose-json-web-encryption (work in progress),
October 2014. January 2015.
[JWK] Jones, M., "JSON Web Key (JWK)", [JWK] Jones, M., "JSON Web Key (JWK)",
draft-ietf-jose-json-web-key (work in progress), draft-ietf-jose-json-web-key (work in progress),
October 2014. January 2015.
[JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web [JWS] Jones, M., Bradley, J., and N. Sakimura, "JSON Web
Signature (JWS)", draft-ietf-jose-json-web-signature (work Signature (JWS)", draft-ietf-jose-json-web-signature (work
in progress), October 2014. in progress), January 2015.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data [RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, March 2014. Interchange Format", RFC 7159, March 2014.
[SHS] National Institute of Standards and Technology, "Secure
Hash Standard (SHS)", FIPS PUB 180-4, March 2012.
[UNICODE] The Unicode Consortium, "The Unicode Standard", 1991-,
<http://www.unicode.org/versions/latest/>.
8.2. Informative References
[I-D.ietf-json-i-json]
Bray, T., "The I-JSON Message Format",
draft-ietf-json-i-json-05 (work in progress),
December 2014.
Appendix A. Acknowledgements Appendix A. Acknowledgements
James Manger, Nat Sakimura, and John Bradley participated in James Manger and John Bradley participated in discussions that led to
discussions that led to the creation of this specification. the creation of this specification. Jim Schaad also contributed to
this specification.
Appendix B. Document History Appendix B. 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 ]]
-01
o Addressed issues pointed out by Jim Schaad, including defining the
JWK Thumbprint computation in a manner that allows different hash
functions to be used over time.
o Added Nat Sakimura as an editor.
-00 -00
o Created draft-ietf-jose-jwk-thumbprint-00 from o Created draft-ietf-jose-jwk-thumbprint-00 from
draft-jones-jose-jwk-thumbprint-01 with no normative changes. draft-jones-jose-jwk-thumbprint-01 with no normative changes.
Author's Address Authors' Addresses
Michael B. Jones Michael B. Jones
Microsoft Microsoft
Email: mbj@microsoft.com Email: mbj@microsoft.com
URI: http://self-issued.info/ URI: http://self-issued.info/
Nat Sakimura
Nomura Research Institute
Email: n-sakimura@nri.co.jp
URI: http://nat.sakimura.org/
 End of changes. 31 change blocks. 
69 lines changed or deleted 128 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/