draft-ietf-stir-passport-09.txt   draft-ietf-stir-passport-10.txt 
STIR C. Wendt STIR C. Wendt
Internet-Draft Comcast Internet-Draft Comcast
Intended status: Standards Track J. Peterson Intended status: Standards Track J. Peterson
Expires: April 20, 2017 Neustar Inc. Expires: May 4, 2017 Neustar Inc.
October 17, 2016 October 31, 2016
Personal Assertion Token (PASSporT) Personal Assertion Token (PASSporT)
draft-ietf-stir-passport-09 draft-ietf-stir-passport-10
Abstract Abstract
This document defines a method for creating and validating a token This document defines a method for creating and validating a token
that cryptographically verifies an originating identity, or more that cryptographically verifies an originating identity, or more
generally a URI or telephone number representing the originator of generally a URI or telephone number representing the originator of
personal communications. The PASSporT token is cryptographically personal communications. The PASSporT token is cryptographically
signed to protect the integrity of the identity the originator and to signed to protect the integrity of the identity the originator and to
verify the assertion of the identity information at the destination. verify the assertion of the identity information at the destination.
The cryptographic signature is defined with the intention that it can The cryptographic signature is defined with the intention that it can
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 April 20, 2017. This Internet-Draft will expire on May 4, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 31 skipping to change at page 2, line 31
4.1. "typ" (Type) Header Parameter . . . . . . . . . . . . . . 5 4.1. "typ" (Type) Header Parameter . . . . . . . . . . . . . . 5
4.2. "alg" (Algorithm) Header Parameter . . . . . . . . . . . 5 4.2. "alg" (Algorithm) Header Parameter . . . . . . . . . . . 5
4.3. "x5u" (X.509 URL) Header Parameter . . . . . . . . . . . 5 4.3. "x5u" (X.509 URL) Header Parameter . . . . . . . . . . . 5
4.4. Example PASSporT header . . . . . . . . . . . . . . . . . 6 4.4. Example PASSporT header . . . . . . . . . . . . . . . . . 6
5. PASSporT Payload . . . . . . . . . . . . . . . . . . . . . . 6 5. PASSporT Payload . . . . . . . . . . . . . . . . . . . . . . 6
5.1. JWT defined claims . . . . . . . . . . . . . . . . . . . 6 5.1. JWT defined claims . . . . . . . . . . . . . . . . . . . 6
5.1.1. "iat" - Issued At claim . . . . . . . . . . . . . . . 6 5.1.1. "iat" - Issued At claim . . . . . . . . . . . . . . . 6
5.2. PASSporT specific claims . . . . . . . . . . . . . . . . 6 5.2. PASSporT specific claims . . . . . . . . . . . . . . . . 6
5.2.1. Originating and Destination Identity Claims . . . . . 6 5.2.1. Originating and Destination Identity Claims . . . . . 6
5.2.2. "mky" - Media Key claim . . . . . . . . . . . . . . . 8 5.2.2. "mky" - Media Key claim . . . . . . . . . . . . . . . 8
6. PASSporT Signature . . . . . . . . . . . . . . . . . . . . . 9 6. PASSporT Signature . . . . . . . . . . . . . . . . . . . . . 10
7. Compact form of PASSporT . . . . . . . . . . . . . . . . . . 10 7. Compact form of PASSporT . . . . . . . . . . . . . . . . . . 10
7.1. Example Compact form PASSporT Token . . . . . . . . . . . 11 7.1. Example Compact form PASSporT Token . . . . . . . . . . . 11
8. Extending PASSporT . . . . . . . . . . . . . . . . . . . . . 11 8. Extending PASSporT . . . . . . . . . . . . . . . . . . . . . 11
8.1. "ppt" (PASSporT) header parameter . . . . . . . . . . . . 11 8.1. "ppt" (PASSporT) header parameter . . . . . . . . . . . . 12
8.2. Example extended PASSporT header . . . . . . . . . . . . 12 8.2. Example extended PASSporT header . . . . . . . . . . . . 12
8.3. Extended PASSporT Claims . . . . . . . . . . . . . . . . 12 8.3. Extended PASSporT Claims . . . . . . . . . . . . . . . . 13
9. Deterministic JSON Serialization . . . . . . . . . . . . . . 13 9. Deterministic JSON Serialization . . . . . . . . . . . . . . 13
9.1. Example PASSport deterministic JSON form . . . . . . . . 13 9.1. Example PASSport deterministic JSON form . . . . . . . . 14
10. Security Considerations . . . . . . . . . . . . . . . . . . . 14 10. Security Considerations . . . . . . . . . . . . . . . . . . . 15
10.1. Avoidance of replay and cut and paste attacks . . . . . 14 10.1. Avoidance of replay and cut and paste attacks . . . . . 15
10.2. Solution Considerations . . . . . . . . . . . . . . . . 15 10.2. Solution Considerations . . . . . . . . . . . . . . . . 15
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
11.1. Media Type Registration . . . . . . . . . . . . . . . . 15 11.1. Media Type Registration . . . . . . . . . . . . . . . . 16
11.1.1. Media Type Registry Contents Additions Requested . . 15 11.1.1. Media Type Registry Contents Additions Requested . . 16
11.2. JSON Web Token Claims Registration . . . . . . . . . . . 16 11.2. JSON Web Token Claims Registration . . . . . . . . . . . 17
11.2.1. Registry Contents Additions Requested . . . . . . . 16 11.2.1. Registry Contents Additions Requested . . . . . . . 17
11.3. JSON Web Signature and Encryption Header Parameter 11.3. JSON Web Signature and Encryption Header Parameter
Registry . . . . . . . . . . . . . . . . . . . . . . . . 17 Registry . . . . . . . . . . . . . . . . . . . . . . . . 18
11.3.1. Registry Contents Additions Requested . . . . . . . 17 11.3.1. Registry Contents Additions Requested . . . . . . . 18
12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17 11.4. PASSporT Extension Registry Request . . . . . . . . . . 18
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18
13.1. Normative References . . . . . . . . . . . . . . . . . . 17 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
13.2. Informative References . . . . . . . . . . . . . . . . . 19 13.1. Normative References . . . . . . . . . . . . . . . . . . 18
13.2. Informative References . . . . . . . . . . . . . . . . . 20
Appendix A. Example ES256 based PASSporT JWS Serialization and Appendix A. Example ES256 based PASSporT JWS Serialization and
Signature . . . . . . . . . . . . . . . . . . . . . 19 Signature . . . . . . . . . . . . . . . . . . . . . 20
A.1. X.509 Private Key for ES256 Example** . . . . . . . . . . 21 A.1. X.509 Private Key in PKCS#8 format for ES256 Example** . 22
A.2. X.509 Public Key for ES256 Example** . . . . . . . . . . 21 A.2. X.509 Public Key for ES256 Example** . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
In today's IP-enabled telecommunications world, there is a growing In today's IP-enabled telecommunications world, there is a growing
concern about the ability to trust incoming invitations for concern about the ability to trust incoming invitations for
communications sessions, including video, voice and messaging communications sessions, including video, voice and messaging
[RFC7340]. As an example, modern telephone networks provide the [RFC7340]. As an example, modern telephone networks provide the
ability to spoof the calling party telephone number for many ability to spoof the calling party telephone number for many
legitimate purposes including providing network features and services legitimate purposes including providing network features and services
on the behalf of a legitimate telephone number. However, as we have on the behalf of a legitimate telephone number. However, as we have
skipping to change at page 6, line 13 skipping to change at page 6, line 13
an HTTPS or DNSSEC resource using integrity protection. an HTTPS or DNSSEC resource using integrity protection.
4.4. Example PASSporT header 4.4. Example PASSporT header
An example of the header, would be the following, including the An example of the header, would be the following, including the
specified passport type, ES256 algorithm, and a URI referencing the specified passport type, ES256 algorithm, and a URI referencing the
network location of the certificate needed to validate the PASSporT network location of the certificate needed to validate the PASSporT
signature. signature.
{ {
"typ":"passport", "typ":"passport",
"alg":"ES256", "alg":"ES256",
"x5u":"https://cert.example.org/passport.cer" "x5u":"https://cert.example.org/passport.cer"
} }
5. PASSporT Payload 5. PASSporT Payload
The token claims consist of the information which needs to be The token claims consist of the information which needs to be
verified at the destination party. These claims follow the verified at the destination party. These claims follow the
definition of a JWT claim [RFC7519] Section 4 and are encoded as definition of a JWT claim [RFC7519] Section 4 and are encoded as
defined by the JWS Payload [RFC7515] Section 3. defined by the JWS Payload [RFC7515] Section 3.
PASSporT defines the use of a standard JWT defined claim as well as PASSporT defines the use of a standard JWT defined claim as well as
skipping to change at page 7, line 20 skipping to change at page 7, line 20
claim value which is a JSON object representing the asserted identity claim value which is a JSON object representing the asserted identity
of any type (currently either "tn" or "uri") of the originator of the of any type (currently either "tn" or "uri") of the originator of the
personal communications signaling. There MUST be exactly one "orig" personal communications signaling. There MUST be exactly one "orig"
claim with exactly one identity claim object in a PASSporT object. claim with exactly one identity claim object in a PASSporT object.
Note, as explained in Section 3, the originating identity represents Note, as explained in Section 3, the originating identity represents
the calling party and may or may not correspond to the authoritative the calling party and may or may not correspond to the authoritative
signer of the token. signer of the token.
The "dest" is a JSON object with the claim name of "dest" and MUST The "dest" is a JSON object with the claim name of "dest" and MUST
have at least have one identity claim object. The"dest" claim value have at least have one identity claim object. The "dest" claim value
is an array containing one or more identity claim JSON objects is an array containing one or more identity claim JSON objects
representing the destination identities of any type (currently "tn" representing the destination identities of any type (currently "tn"
or "uri"). If the "dest" claim value array contains both "tn" and or "uri"). If the "dest" claim value array contains both "tn" and
"uri" claim names, the JSON object should list the "tn" array first "uri" claim names, the JSON object should list the "tn" array first
and the "uri" array second. Within the "tn" and "uri" arrays, the and the "uri" array second. Within the "tn" and "uri" arrays, the
identity strings should be put in lexicographical order including the identity strings should be put in lexicographical order including the
scheme-specific portion of the URI characters. scheme-specific portion of the URI characters.
Note, as explained in Section 3, the destination identity represents Note, as explained in Section 3, the destination identity represents
the called party and may or may not correspond to the authoritative the called party and may or may not correspond to the authoritative
skipping to change at page 8, line 20 skipping to change at page 8, line 20
to allow for other identity types with new IANA registered unique to allow for other identity types with new IANA registered unique
types to represent these forms. types to represent these forms.
5.2.1.4. Examples 5.2.1.4. Examples
Single originator, with telephone number identity +12155551212, to Single originator, with telephone number identity +12155551212, to
single destination, with URI identity 'sip:alice@example.com', single destination, with URI identity 'sip:alice@example.com',
example: example:
{ {
"dest":{"uri":["sip:alice@example.com"]}, "dest":{"uri":["sip:alice@example.com"]},
"iat":"1443208345", "iat":1443208345,
"orig":{"tn":"12155551212"} "orig":{"tn":"12155551212"}
} }
Single originator, with telephone number identity +12155551212, to Single originator, with telephone number identity +12155551212, to
multiple destination identities, with telephone number identity multiple destination identities, with telephone number identity
+12125551212 and two URI identities, sip:alice@example.com and +12125551212 and two URI identities, sip:alice@example.com and
sip:bob@example.com, example: sip:bob@example.com, example:
{ {
"dest":{ "dest":{
"tn":["12125551212"], "tn":["12125551212"],
"uri":["sip:alice@example.com", "uri":["sip:alice@example.com",
"sip:bob@example.net"] "sip:bob@example.net"]
}, },
"iat":"1443208345", "iat":1443208345,
"orig":{"tn":"12155551212"} "orig":{"tn":"12155551212"}
} }
5.2.2. "mky" - Media Key claim 5.2.2. "mky" - Media Key claim
Some protocols that use PASSporT may also want to protect media Some protocols that use PASSporT may also want to protect media
security keys delivered within their signaling in order to bind those security keys delivered within their signaling in order to bind those
keys to the identities established in the signaling layers. The keys to the identities established in the signaling layers. The
"mky" is an optional PASSporT claim defining the assertion of media "mky" is an optional PASSporT claim defining the assertion of media
key fingerprints carried in SDP [RFC4566] via the "a=fingerprint" key fingerprints carried in SDP [RFC4566] via the "a=fingerprint"
attribute [RFC4572] Section 5. This claim can support either a attribute [RFC4572] Section 5. This claim can support either a
single or multiple fingerprints appearing in a single SDP body single or multiple fingerprints appearing in a single SDP body
corresponding to one or more media streams offered. The "mky" claim corresponding to one or more media streams offered as defined in
MUST be formatted in a JSON form including the "alg" and "dig" claims [I-D.ietf-mmusic-4572-update].
with the corresponding algorithm and hexadecimal values. If there is
more than one fingerprint value associated with different media The "mky" claim MUST be formatted as a JSON object with an array
streams in SDP, the fingerprint values MUST be constructed as a JSON including the "alg" and "dig" claims with the corresponding algorithm
array denoted by bracket characters. For the "dig" claim, the claim and hexadecimal values. If there is more than one fingerprint value
value MUST be the hash hexadecimal value without any colons. associated with different media streams in SDP, the fingerprint
values MUST be constructed as a JSON array denoted by bracket
characters. For the "dig" claim, the claim value MUST be the hash
hexadecimal value without any colons.
The "mky" claim is a JSON object with a claim name of "mky" and a The "mky" claim is a JSON object with a claim name of "mky" and a
claim value of a JSON array. The "mky" claim value JSON array MUST claim value of a JSON array denoted by brackets. The "mky" claim
contain JSON objects with exactly one of both corresponding "alg" and value JSON array MUST be constructed as follows:
"dig" claim objects. The order of the JSON array should be in
lexicographic order of the "alg" claims first followed by the 1. Take each "a=fingerprint" lines carried in the SDP.
corresponding lexicographic order of the "dig" claim values when
there is repeated "alg" claims. Within each of the "mky" claim array 2. Sort the lines based on the UTF8 encoding of the concatenation of
objects the claim objects MUST have "alg" first and "dig" second. the "alg" and "dig" claim value strings.
3. Encode the array in the order of the sorted lines, where each
"mky" array element is a JSON object with two elements
corresponding to the "alg" and "dig" objects, with "alg" first
and "dig" second.
An example claim with "mky" claim is as follows: An example claim with "mky" claim is as follows:
For an SDP offer that includes the following fingerprint values, For an SDP offer that includes the following fingerprint values,
a=fingerprint:sha-256 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E: a=fingerprint:sha-256 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:
5D:49:6B:19:E5:7C:AB:3E:4B:65:2E:7D:46:3F:54:42:CD:54:F1 5D:49:6B:19:E5:7C:AB:3E:4B:65:2E:7D:46:3F:54:42:CD:54:F1
a=fingerprint:sha-256 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65 a=fingerprint:sha-256 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65
:2E:7D:46:3F:54:42:CD:54:F1:7A:03:A2:7D:F9:B0:7F:46:19:B2 :2E:7D:46:3F:54:42:CD:54:F1:7A:03:A2:7D:F9:B0:7F:46:19:B2
the PASSporT Payload object would be: the PASSporT Payload object would be:
{ {
"dest":{"uri":["sip:alice@example.com"]}, "dest":{"uri":["sip:alice@example.com"]},
"iat":"1443208345", "iat":1443208345,
"mky":[ "mky":[
{ {
"alg":"sha-256", "alg":"sha-256",
"dig":"021ACC5427ABEB9C533F3E4B652E7D463F5442CD54 "dig":"021ACC5427ABEB9C533F3E4B652E7D463F5442CD54
F17A03A27DF9B07F4619B2" F17A03A27DF9B07F4619B2"
}, },
{ {
"alg":"sha-256", "alg":"sha-256",
"dig":"4AADB9B13F82183B540212DF3E5D496B19E57C "dig":"4AADB9B13F82183B540212DF3E5D496B19E57C
AB3E4B652E7D463F5442CD54F1" AB3E4B652E7D463F5442CD54F1"
} }
], ],
"orig":{"tn":"12155551212"} "orig":{"tn":"12155551212"}
} }
6. PASSporT Signature 6. PASSporT Signature
The signature of the PASSporT is created as specified by JWS The signature of the PASSporT is created as specified by JWS
[RFC7515] Section 5.1 Steps 1 through 6. PASSporT MUST use the JWS [RFC7515] Section 5.1 Steps 1 through 6. PASSporT MUST use the JWS
Protected Header. For the JWS Payload and the JWS Protected Header, Protected Header. For the JWS Payload and the JWS Protected Header,
the lexicographic ordering and white space rules described in the lexicographic ordering and white space rules described in
Section 4 and Section 5, and JSON serialization rules in Section 9 of Section 4 and Section 5, and JSON serialization rules in Section 9 of
this document MUST be followed. this document MUST be followed.
skipping to change at page 11, line 10 skipping to change at page 11, line 32
ordering and white space serialization rules, particularly in the ordering and white space serialization rules, particularly in the
case where some using protocols or interworking between protocols may case where some using protocols or interworking between protocols may
require switching between full and compact forms and maintaining the require switching between full and compact forms and maintaining the
integrity of the signature. integrity of the signature.
7.1. Example Compact form PASSporT Token 7.1. Example Compact form PASSporT Token
The compact form of the following example token (with line breaks The compact form of the following example token (with line breaks
between period used for readability purposes only) between period used for readability purposes only)
eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9j eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9j
ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9 ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9
. .
eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhdCI eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhdCI
6IjE0NDMyMDgzNDUiLCJvcmlnIjp7InRuIjoiMTIxNTU1NTEyMTIifX0 6IjE0NDMyMDgzNDUiLCJvcmlnIjp7InRuIjoiMTIxNTU1NTEyMTIifX0
. .
rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYsojN rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYsojN
CpTzO3QfPOlckGaS6hEck7w CpTzO3QfPOlckGaS6hEck7w
would be as follows (with line breaks between period used for would be as follows (with line breaks between period used for
readability purposes only) readability purposes only)
..rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYsojN ..rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYsojN
CpTzO3QfPOlckGaS6hEck7w CpTzO3QfPOlckGaS6hEck7w
8. Extending PASSporT 8. Extending PASSporT
PASSporT includes the bare minimum set of claims needed to securely PASSporT includes the bare minimum set of claims needed to securely
assert the originating identity and support the secure properties assert the originating identity and support the secure properties
discussed in various parts of this document. JWT supports a straight discussed in various parts of this document. JWT supports a straight
forward way to add additional asserted or signed information by forward way to add additional asserted or signed information by
simply adding new claims. PASSporT can be extended beyond the simply adding new claims. PASSporT can be extended beyond the
defined base set of claims to represent other information requiring defined base set of claims to represent other information requiring
assertion or validation beyond the originating identity itself as assertion or validation beyond the originating identity itself as
skipping to change at page 12, line 22 skipping to change at page 12, line 45
Moreover, using protocols that support the compact form of PASSporT Moreover, using protocols that support the compact form of PASSporT
MUST have some field to signal "ppt" to relying parties, as the MUST have some field to signal "ppt" to relying parties, as the
compact form of PASSporT omits the JOSE header. compact form of PASSporT omits the JOSE header.
8.2. Example extended PASSporT header 8.2. Example extended PASSporT header
An example header with a PASSporT extension type of "foo" is as An example header with a PASSporT extension type of "foo" is as
follows: follows:
{ {
"alg":"ES256", "alg":"ES256",
"ppt":"foo", "ppt":"foo",
"typ":"passport", "typ":"passport",
"x5u":"https://tel.example.org/passport.cer" "x5u":"https://tel.example.org/passport.cer"
} }
8.3. Extended PASSporT Claims 8.3. Extended PASSporT Claims
Specifications that define extensions to the PASSporT mechanism MUST Specifications that define extensions to the PASSporT mechanism MUST
explicitly specify what claims they include beyond the base set of explicitly specify what claims they include beyond the base set of
claims from this document, the order in which they will appear, and claims from this document, the order in which they will appear, and
any further information necessary to implement the extension. All any further information necessary to implement the extension. All
extensions MUST include the baseline PASSporT claim elements extensions MUST include the baseline PASSporT claim elements
specified in Section 5; claims may only be appended to the claims specified in Section 5; claims may only be appended to the claims
skipping to change at page 13, line 6 skipping to change at page 13, line 30
support an extension may then trigger appropriate application-level support an extension may then trigger appropriate application-level
behavior in the presence of an extension; authors of extensions behavior in the presence of an extension; authors of extensions
should provide appropriate extension-specific guidance to application should provide appropriate extension-specific guidance to application
developers on this point. developers on this point.
An example set of extended claims, extending the first example in An example set of extended claims, extending the first example in
Section 5.2.1.4 using "bar" as the newly defined claim would be as Section 5.2.1.4 using "bar" as the newly defined claim would be as
follows: follows:
{ {
"bar":"beyond all recognition" "bar":"beyond all recognition"
"dest":{"uri":["sip:alice@example.com"]}, "dest":{"uri":["sip:alice@example.com"]},
"iat":"1443208345", "iat":1443208345,
"orig":{"tn":"12155551212"} "orig":{"tn":"12155551212"}
} }
9. Deterministic JSON Serialization 9. Deterministic JSON Serialization
JSON, as a canonical format, can include spaces and line breaks, and JSON objects can include spaces and line breaks, and key value pairs
key value pairs can occur in any order. It is therefore a non- can occur in any order. It is therefore a non-deterministic string
deterministic string format. In order to make the digital signature format. In order to make the digital signature verification work
verification work deterministically, the JSON representation of the deterministically, the JSON representation of the JWS Protected
JWS Protected Header object and JWS Payload object MUST be computed Header object and JWS Payload object MUST be computed as follows.
as follows.
The JSON object MUST follow the rules for the construction of the The JSON object MUST follow the following rules. These rules are
thumbprint of a JSON Web Key (JWK) as defined in [RFC7638] Section 3 based on the thumbprint of a JSON Web Key (JWK) as defined in
Step 1 only. Step 2 should not be performed; as noted in JWK this is Section 3 Step 1 of [RFC7638].
still a legal JWK object.
1. The JSON object MUST contain no whitespace or line breaks before
or after any syntactic elements.
2. JSON objects MUST have the keys ordered lexicographically by the
Unicode [UNICODE] code points of the member names.
3. JSON value literals MUST be lowercase.
4. JSON numbers are to be encoded as integers unless the field is
defined to be encoded otherwise.
5. Encoding rules MUST be applied recursively to member values and
array values.
Note: For any PASSporT extension claims, member names within the
scope of a JSON object MUST NOT be equal to other member names,
otherwise serialization will not be deterministic.
9.1. Example PASSport deterministic JSON form 9.1. Example PASSport deterministic JSON form
This section demonstrate the deterministic JSON serialization for the This section demonstrate the deterministic JSON serialization for the
example PASSporT Payload shown in Section 5.2.1.4. example PASSporT Payload shown in Section 5.2.1.4.
The initial JSON object is shown here: The initial JSON object is shown here:
{ {
"dest":{"uri":["sip:alice@example.com"]}, "dest":{"uri":["sip:alice@example.com"]},
"orig":{"tn":"12155551212"} "orig":{"tn":"12155551212"}
"iat":"1443208345", "iat":1443208345,
"mky":[ "mky":[
{ {
"alg":"sha-256", "alg":"sha-256",
"dig":"021ACC5427ABEB9C533F3E4B652E7D463F5442CD54 "dig":"021ACC5427ABEB9C533F3E4B652E7D463F5442CD54
F17A03A27DF9B07F4619B2" F17A03A27DF9B07F4619B2"
}, },
{ {
"alg":"sha-256", "alg":"sha-256",
"dig":"4AADB9B13F82183B540212DF3E5D496B19E57C "dig":"4AADB9B13F82183B540212DF3E5D496B19E57C
AB3E4B652E7D463F5442CD54F1" AB3E4B652E7D463F5442CD54F1"
} }
], ],
} }
The parent members of the JSON object are as follows: The parent members of the JSON object are as follows:
o "dest" o "dest"
o "orig" o "orig"
skipping to change at page 15, line 43 skipping to change at page 16, line 33
11. IANA Considerations 11. IANA Considerations
11.1. Media Type Registration 11.1. Media Type Registration
11.1.1. Media Type Registry Contents Additions Requested 11.1.1. Media Type Registry Contents Additions Requested
This section registers the "application/passport" media type This section registers the "application/passport" media type
[RFC2046] in the "Media Types" registry in the manner described in [RFC2046] in the "Media Types" registry in the manner described in
[RFC6838], which can be used to indicate that the content is a [RFC6838], which can be used to indicate that the content is a
PASSporT defined JWT and JWS. PASSporT defined JWT.
o Type name: application o Type name: application
o Subtype name: passport o Subtype name: passport
o Required parameters: n/a o Required parameters: n/a
o Optional parameters: n/a o Optional parameters: n/a
o Encoding considerations: 8bit; application/passport values outside
the US-ASCII range are encoded using percent encoding as described o Encoding considerations: 8bit; application/passport values are
in Section 2.1 of [RFC3986] (some values may be the empty string), encoded as a series of base64url-encoded values (some of which may
each separated from the next by a single period ('.') character. be the empty string) separated by period ('.') characters..
o Security considerations: See the Security Considerations o Security considerations: See the Security Considerations
Section of [RFC7515]. Section of [RFC7515].
o Interoperability considerations: n/a o Interoperability considerations: n/a
o Published specification: [RFCThis] o Published specification: [RFCThis]
o Applications that use this media type: STIR and other applications o Applications that use this media type: STIR and other applications
that require identity related assertion that require identity related assertion
o Fragment identifier considerations: n/a o Fragment identifier considerations: n/a
o Additional information: o Additional information:
Magic number(s): n/a File extension(s): n/a Macintosh file type Magic number(s): n/a File extension(s): n/a Macintosh file type
skipping to change at page 17, line 32 skipping to change at page 18, line 22
Header Parameter Name: "ppt" Header Parameter Name: "ppt"
o Header Parameter Description: PASSporT extension identifier o Header Parameter Description: PASSporT extension identifier
o Header Parameter Usage Location(s): JWS o Header Parameter Usage Location(s): JWS
o Change Controller: IESG o Change Controller: IESG
o Specification Document(s): Section 8.1 of [RFCThis] o Specification Document(s): Section 8.1 of [RFCThis]
11.4. PASSporT Extension Registry Request
The IANA is requested to create a new PASSporT Type registry for
'ppt' parameter values. That parameter and its values are defined in
Section 8.1. New registry entries must contain the name of the 'ppt'
parameter value and the specification in which the value is
described. The policy for this registry is Specification Required.
12. Acknowledgements 12. Acknowledgements
Particular thanks to members of the ATIS and SIP Forum NNI Task Group Particular thanks to members of the ATIS and SIP Forum NNI Task Group
including Jim McEchern, Martin Dolly, Richard Shockey, John Barnhill, including Jim McEchern, Martin Dolly, Richard Shockey, John Barnhill,
Christer Holmberg, Victor Pascual Avila, Mary Barnes, Eric Burger for Christer Holmberg, Victor Pascual Avila, Mary Barnes, Eric Burger for
their review, ideas, and contributions also thanks to Henning their review, ideas, and contributions also thanks to Henning
Schulzrinne, Russ Housley, Alan Johnston, Richard Barnes, Mark Schulzrinne, Russ Housley, Alan Johnston, Richard Barnes, Mark
Miller, Ted Hardie, Dave Crocker, Robert Sparks for valuable feedback Miller, Ted Hardie, Dave Crocker, Robert Sparks, Jim Schaad for
on the technical and security aspects of the document. Additional valuable feedback on the technical and security aspects of the
thanks to Harsha Bellur for assistance in coding the example tokens. document. Additional thanks to Harsha Bellur for assistance in
coding the example tokens.
13. References 13. References
13.1. Normative References 13.1. Normative References
[I-D.ietf-mmusic-4572-update]
Holmberg, C., "SDP Fingerprint Attribute Usage
Clarifications", draft-ietf-mmusic-4572-update-07 (work in
progress), September 2016.
[I-D.ietf-stir-rfc4474bis] [I-D.ietf-stir-rfc4474bis]
Peterson, J., Jennings, C., Rescorla, E., and C. Wendt, Peterson, J., Jennings, C., Rescorla, E., and C. Wendt,
"Authenticated Identity Management in the Session "Authenticated Identity Management in the Session
Initiation Protocol (SIP)", draft-ietf-stir-rfc4474bis-13 Initiation Protocol (SIP)", draft-ietf-stir-rfc4474bis-14
(work in progress), September 2016. (work in progress), October 2016.
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
DOI 10.17487/RFC2046, November 1996, DOI 10.17487/RFC2046, November 1996,
<http://www.rfc-editor.org/info/rfc2046>. <http://www.rfc-editor.org/info/rfc2046>.
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
skipping to change at page 19, line 5 skipping to change at page 20, line 9
<http://www.rfc-editor.org/info/rfc7518>. <http://www.rfc-editor.org/info/rfc7518>.
[RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token [RFC7519] Jones, M., Bradley, J., and N. Sakimura, "JSON Web Token
(JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015, (JWT)", RFC 7519, DOI 10.17487/RFC7519, May 2015,
<http://www.rfc-editor.org/info/rfc7519>. <http://www.rfc-editor.org/info/rfc7519>.
[RFC7638] Jones, M. and N. Sakimura, "JSON Web Key (JWK) [RFC7638] Jones, M. and N. Sakimura, "JSON Web Key (JWK)
Thumbprint", RFC 7638, DOI 10.17487/RFC7638, September Thumbprint", RFC 7638, DOI 10.17487/RFC7638, September
2015, <http://www.rfc-editor.org/info/rfc7638>. 2015, <http://www.rfc-editor.org/info/rfc7638>.
[UNICODE] The Unicode Consortium, "The Unicode Standard", June 2016,
<http://www.unicode.org/versions/latest/>.
13.2. Informative References 13.2. Informative References
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>. <http://www.rfc-editor.org/info/rfc3261>.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S., [RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key Housley, R., and W. Polk, "Internet X.509 Public Key
skipping to change at page 19, line 43 skipping to change at page 21, line 6
o "signature", with the value BASE64URL(JWS Signature) o "signature", with the value BASE64URL(JWS Signature)
This example will follow the steps in JWS [RFC7515] Section 5.1, This example will follow the steps in JWS [RFC7515] Section 5.1,
steps 1-6 and 8 and incorporates the additional serialization steps steps 1-6 and 8 and incorporates the additional serialization steps
required for PASSporT. required for PASSporT.
Step 1 for JWS references the JWS Payload, an example PASSporT Step 1 for JWS references the JWS Payload, an example PASSporT
Payload is as follows: Payload is as follows:
{ {
"dest":{"uri":["sip:alice@example.com"]} "dest":{"uri":["sip:alice@example.com"]}
"iat":"1443208345", "iat":1471375418,
"orig":{"tn":"12155551212"} "orig":{"tn":"12155551212"}
} }
This would be serialized to the form (with line break used for This would be serialized to the form (with line break used for
display purposes only): display purposes only):
{"dest":{"uri":["sip:alice@example.com"]},"iat":"1443208345", {"dest":{"uri":["sip:alice@example.com"]},"iat":1471375418,
"orig":{"tn":"12155551212"}} "orig":{"tn":"12155551212"}}
Step 2 Computes the BASE64URL(JWS Payload) producing this value (with Step 2 Computes the BASE64URL(JWS Payload) producing this value (with
line break used for display purposes only): line break used for display purposes only):
eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhdCI eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhdCI
6IjE0NDMyMDgzNDUiLCJvcmlnIjp7InRuIjoiMTIxNTU1NTEyMTIifX0 6MTQ3MTM3NTQxOCwib3JpZyI6eyJ0biI6IjEyMTU1NTUxMjEyIn19
For Step 3, an example PASSporT Protected Header comprising the JOSE For Step 3, an example PASSporT Protected Header comprising the JOSE
Header is as follows: Header is as follows:
{ {
"alg":"ES256", "alg":"ES256",
"typ":"passport", "typ":"passport",
"x5u":"https://cert.example.org/passport.cer" "x5u":"https://cert.example.org/passport.cer"
} }
This would be serialized to the form (with line break used for This would be serialized to the form (with line break used for
display purposes only): display purposes only):
{"alg":"ES256","typ":"passport","x5u":"https://cert.example.org {"alg":"ES256","typ":"passport","x5u":"https://cert.example.org
/passport.cer"} /passport.cer"}
Step 4 Performs the BASE64URL(UTF8(JWS Protected Header)) operation Step 4 Performs the BASE64URL(UTF8(JWS Protected Header)) operation
and encoding produces this value (with line break used for display and encoding produces this value (with line break used for display
purposes only): purposes only):
eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9j eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9j
ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9 ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9
Step 5 and Step 6 performs the computation of the digital signature Step 5 and Step 6 performs the computation of the digital signature
of the PASSporT Signing Input ASCII(BASE64URL(UTF8(JWS Protected of the PASSporT Signing Input ASCII(BASE64URL(UTF8(JWS Protected
Header)) || '.' || BASE64URL(JWS Payload)) using ES256 as the Header)) || '.' || BASE64URL(JWS Payload)) using ES256 as the
algorithm and the BASE64URL(JWS Signature). algorithm and the BASE64URL(JWS Signature).
rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYsojN VLBCIVDCaeK6M4hLJb6SHQvacAQVvoiiEOWQ_iUkqk79UD81fHQ0E1b3_GluIkb
CpTzO3QfPOlckGaS6hEck7w a7UWYRM47ZbNFdOJquE35cw
Step 8 describes how to create the final PASSporT token, Step 8 describes how to create the final PASSporT token,
concatenating the values in the order Header.Payload.Signature with concatenating the values in the order Header.Payload.Signature with
period ('.') characters. For the above example values this would period ('.') characters. For the above example values this would
produce the following (with line breaks between period used for produce the following (with line breaks between period used for
readability purposes only): readability purposes only):
eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9j eyJhbGciOiJFUzI1NiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9j
ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9 ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNlciJ9
. .
eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhdCI eyJkZXN0Ijp7InVyaSI6WyJzaXA6YWxpY2VAZXhhbXBsZS5jb20iXX0sImlhdCI
6IjE0NDMyMDgzNDUiLCJvcmlnIjp7InRuIjoiMTIxNTU1NTEyMTIifX0 6MTQ3MTM3NTQxOCwib3JpZyI6eyJ0biI6IjEyMTU1NTUxMjEyIn19
. .
rq3pjT1hoRwakEGjHCnWSwUnshd0-zJ6F1VOgFWSjHBr8Qjpjlk-cpFYpFYsojN VLBCIVDCaeK6M4hLJb6SHQvacAQVvoiiEOWQ_iUkqk79UD81fHQ0E1b3_GluIkb
CpTzO3QfPOlckGaS6hEck7w a7UWYRM47ZbNFdOJquE35cw
A.1. X.509 Private Key for ES256 Example** A.1. X.509 Private Key in PKCS#8 format for ES256 Example**
-----BEGIN EC PRIVATE KEY----- -----BEGIN PRIVATE KEY-----
MHcCAQEEIFeZ1R208QCvcu5GuYyMfG4W7sH4m99/7eHSDLpdYllFoAoGCCqGSM49 MIGHAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBG0wawIBAQQgi7q2TZvN9VDFg8Vy
AwEHoUQDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH78YTU8qLS8I5HLHSSmlATLcs qCP06bETrR2v8MRvr89rn4i+UAahRANCAAQWfaj1HUETpoNCrOtp9KA8o0V79IuW
lQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g== ARKt9C1cFPkyd3FBP4SeiNZxQhDrD0tdBHls3/wFe8++K2FrPyQF9vuh
-----END EC PRIVATE KEY----- -----END PRIVATE KEY----
A.2. X.509 Public Key for ES256 Example** A.2. X.509 Public Key for ES256 Example**
-----BEGIN PUBLIC KEY----- -----BEGIN PUBLIC KEY-----
MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH
78YTU8qLS8I5HLHSSmlATLcslQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g== 78YTU8qLS8I5HLHSSmlATLcslQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g==
-----END PUBLIC KEY----- -----END PUBLIC KEY-----
Authors' Addresses Authors' Addresses
 End of changes. 46 change blocks. 
135 lines changed or deleted 176 lines changed or added

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