draft-ietf-stir-passport-01.txt   draft-ietf-stir-passport-02.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: September 24, 2016 Neustar Inc. Expires: November 25, 2016 Neustar Inc.
March 23, 2016 May 24, 2016
Persona Assertion Token Persona Assertion Token
draft-ietf-stir-passport-01 draft-ietf-stir-passport-02
Abstract Abstract
This document defines a token format for verifying with non- This document defines a token format for verifying with non-
repudiation the sender of and authorization to send information repudiation the sender of and authorization to send information
related to the originator of personal communications. A related to the originator of personal communications. A
cryptographic signature is defined to protect the integrity of the cryptographic signature is defined to protect the integrity of the
information used to identify the originator of a personal information used to identify the originator of a personal
communications session (e.g. the telephone number or URI) and verify communications session (e.g. the telephone number or URI) and verify
the accuracy of this information at the destination. The the accuracy of this information at the destination. The
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 September 24, 2016. This Internet-Draft will expire on November 25, 2016.
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
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Token Overview . . . . . . . . . . . . . . . . . . . . . . . 4 2. Token Overview . . . . . . . . . . . . . . . . . . . . . . . 4
3. PASSporT Definition . . . . . . . . . . . . . . . . . . . . . 4 3. PASSporT Definition . . . . . . . . . . . . . . . . . . . . . 4
3.1. PASSporT Header . . . . . . . . . . . . . . . . . . . . . 4 3.1. PASSporT Header . . . . . . . . . . . . . . . . . . . . . 4
3.1.1. "typ" (Type) Header Parameter . . . . . . . . . . . . 4 3.1.1. "typ" (Type) Header Parameter . . . . . . . . . . . . 4
3.1.2. "alg" (Algorithm) Header Parameter . . . . . . . . . 5 3.1.2. "alg" (Algorithm) Header Parameter . . . . . . . . . 5
3.1.3. "x5u" (X.509 URL) Header Parameter . . . . . . . . . 5 3.1.3. "x5u" (X.509 URL) Header Parameter . . . . . . . . . 5
3.2. PASSporT Payload . . . . . . . . . . . . . . . . . . . . 5 3.2. PASSporT Payload . . . . . . . . . . . . . . . . . . . . 5
3.2.1. JWT defined claims . . . . . . . . . . . . . . . . . 5 3.2.1. JWT defined claims . . . . . . . . . . . . . . . . . 5
3.2.1.1. "iat" - Issued at claim . . . . . . . . . . . . . 5 3.2.1.1. "iat" - Issued at claim . . . . . . . . . . . . . 6
3.2.2. PASSporT specific claims . . . . . . . . . . . . . . 5 3.2.2. PASSporT specific claims . . . . . . . . . . . . . . 6
3.2.2.1. Originating and Destination Identities . . . . . 6 3.2.2.1. Originating and Destination Identities . . . . . 6
3.2.2.2. "mky" - Media Key claim . . . . . . . . . . . . . 6 3.2.2.2. "mky" - Media Key claim . . . . . . . . . . . . . 7
3.2.3. Multi-party Communications . . . . . . . . . . . . . 7 3.2.3. Multi-party Communications . . . . . . . . . . . . . 8
3.3. PASSporT Signature . . . . . . . . . . . . . . . . . . . 7 3.3. PASSporT Signature . . . . . . . . . . . . . . . . . . . 8
4. Extending PASSporT . . . . . . . . . . . . . . . . . . . . . 7 4. Extending PASSporT . . . . . . . . . . . . . . . . . . . . . 8
4.1. "ppt" (PASSporT) header parameter . . . . . . . . . . . . 8 4.1. "ppt" (PASSporT) header parameter . . . . . . . . . . . . 8
4.2. Extended PASSporT Claims . . . . . . . . . . . . . . . . 8 4.2. Extended PASSporT Claims . . . . . . . . . . . . . . . . 9
4.3. Alternate PASSporT Extension . . . . . . . . . . . . . . 8 4.3. Alternate PASSporT Extension . . . . . . . . . . . . . . 9
4.4. Registering PASSporT Extensions . . . . . . . . . . . . . 9 4.4. Registering PASSporT Extensions . . . . . . . . . . . . . 9
5. Deterministic JSON Serialization . . . . . . . . . . . . . . 9 5. Deterministic JSON Serialization . . . . . . . . . . . . . . 9
5.1. Example PASSport deterministic JSON form . . . . . . . . 9 5.1. Example PASSport deterministic JSON form . . . . . . . . 10
6. Human Readability . . . . . . . . . . . . . . . . . . . . . . 9 6. Human Readability . . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . 10 7. Security Considerations . . . . . . . . . . . . . . . . . . . 10
7.1. Avoidance of replay and cut and paste attacks . . . . . . 10 7.1. Avoidance of replay and cut and paste attacks . . . . . . 10
7.2. Solution Considerations . . . . . . . . . . . . . . . . . 10 7.2. Solution Considerations . . . . . . . . . . . . . . . . . 11
7.3. Privacy Considerations . . . . . . . . . . . . . . . . . 11 7.3. Privacy Considerations . . . . . . . . . . . . . . . . . 11
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
8.1. Media Type Registration . . . . . . . . . . . . . . . . . 11 8.1. Media Type Registration . . . . . . . . . . . . . . . . . 12
8.1.1. Media Type Registry Contents Additions Requested . . 11 8.1.1. Media Type Registry Contents Additions Requested . . 12
8.2. JSON Web Token Claims Registration . . . . . . . . . . . 12 8.2. JSON Web Token Claims Registration . . . . . . . . . . . 13
8.2.1. Registry Contents Additions Requested . . . . . . . . 12 8.2.1. Registry Contents Additions Requested . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
Appendix A. Appendix A. Example PASSporT JWS Serialization and Appendix A. Example ES256 base PASSporT JWS Serialization and
Signature . . . . . . . . . . . . . . . . . . . . . 15 Signature . . . . . . . . . . . . . . . . . . . . . 15
Appendix B. Appendix B. X.509 Private Key Certificate for A.1. X.509 Private Key Certificate for Example in Appendix A . 17
Example in Appendix A . . . . . . . . . . . . . . . 17 A.2. X.509 Public Key Certificate for Example in Appendix A . 17
Appendix C. Appendix C. X.509 Public Key Certificate for Example Appendix B. Example RS256 base PASSporT JWS Serialization and
in Appendix A . . . . . . . . . . . . . . . . . . . 18 Signature . . . . . . . . . . . . . . . . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18 B.1. X.509 Private Key Certificate for Example in Appendix A . 19
B.2. X.509 Public Key Certificate for Example in Appendix A . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
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. As an communications sessions, including video, voice and messaging. As an
example, modern telephone networks provide the ability to spoof the example, modern telephone networks provide the ability to spoof the
calling party telephone number for many legitimate purposes including calling party telephone number for many legitimate purposes including
providing network features and services on the behalf of a legitimate providing network features and services on the behalf of a legitimate
telephone number. However, as we have seen, bad actors have taken telephone number. However, as we have seen, bad actors have taken
skipping to change at page 4, line 33 skipping to change at page 4, line 35
specified canonical format for signing data corresponding to JOSE specified canonical format for signing data corresponding to JOSE
header, JWS Payload, and JWS Signature. JWT defines specific set of header, JWS Payload, and JWS Signature. JWT defines specific set of
claims that are represented by specified key value pairs which can be claims that are represented by specified key value pairs which can be
extended with custom keys for specific applications. extended with custom keys for specific applications.
3.1. PASSporT Header 3.1. PASSporT Header
The JWS token header is a JOSE header [RFC7515] that defines the type The JWS token header is a JOSE header [RFC7515] that defines the type
and encryption algorithm used in the token. and encryption algorithm used in the token.
An example of the header for the case of a RSASSA-PKCS1-v1_5 SHA-256 An example of the header for the case of an ECDSA P-256 digital
digital signature would be the following, signature would be the following,
{ {
"typ":"passport", "typ":"passport",
"alg":"RS256", "alg":"ES256",
"x5u":"https://cert.example.org/passport.crt" "x5u":"https://cert.example.org/passport.crt"
} }
3.1.1. "typ" (Type) Header Parameter 3.1.1. "typ" (Type) Header Parameter
JWS defines the "typ" (Type) Header Parameter to declare the media JWS defines the "typ" (Type) Header Parameter to declare the media
type [IANA.MediaTypes] of the JWS. type [IANA.MediaTypes] of the JWS.
This represents that the encoded token is a JWT, and the JWT is a JWS
using the RSASSA-PKCS1-v1_5 SHA-256 algorithm.
For PASSporT Token the "typ" header MUST minimally include and begin For PASSporT Token the "typ" header MUST minimally include and begin
with "passport". with "passport". This represents that the encoded token is a JWT of
type passport. Note with extensions explained later in this
document, the typ may be another value if defined as a passport
extension.
3.1.2. "alg" (Algorithm) Header Parameter 3.1.2. "alg" (Algorithm) Header Parameter
For PASSporT, the "alg" should be defined as RS256 as the recommended For PASSporT, the "alg" should be defined as follows, for the
algorithm. Note that JWA [RFC7518] defines other algorithms that may creation of PASSporT tokens and their corresponding digital
be utilized or updated in the future depending on cryptographic signatures,
strength requirements guided by current security best practice.
o ES256 MUST be implemented.
o RS256 SHOULD be implemented
For the verification of PASSporT tokens, both ES256 and RS256 MUST be
supported.
Note that JWA [RFC7518] defines other algorithms that may be utilized
or updated in the future depending on cryptographic strength
requirements guided by current security best practice.
3.1.3. "x5u" (X.509 URL) Header Parameter 3.1.3. "x5u" (X.509 URL) Header Parameter
As defined in JWS, the "x5u" header parameter is used to provide a As defined in JWS, the "x5u" header parameter is used to provide a
URI [RFC3986] referring to the resource for the X.509 public key URI [RFC3986] referring to the resource for the X.509 public key
certificate or certificate chain [RFC5280] corresponding to the key certificate or certificate chain [RFC5280] corresponding to the key
used to digitally sign the JWS. Note: The definition of what the URI used to digitally sign the JWS. Note: The definition of what the URI
represents in terms of the actor serving the X.509 public key is out represents in terms of the actor serving the X.509 public key is out
of scope of this document. However, generally this would correspond of scope of this document. However, generally this would correspond
to an HTTPS or DNSSEC resource with the guidance that it MUST be a to an HTTPS or DNSSEC resource with the guidance that it MUST be a
TLS protected, per JWS spec. TLS protected, per JWS spec.
3.2. PASSporT Payload 3.2. PASSporT Payload
The token payload claims should consist of the information which The token payload claims should consist of the information which
needs to be verified at the destination party. This claim should needs to be verified at the destination party. This claim should
correspond to a JWT claim [RFC7519] and be encoded as defined by the correspond to a JWT claim [RFC7519] and be encoded as defined by the
JWS Payload [RFC7519] JWS Payload [RFC7515]
The PASSporT defines the use of a number of standard JWT defined The PASSporT defines the use of a number of standard JWT defined
headers as well as two new custom headers corresponding to the two headers as well as two new custom headers corresponding to the two
parties associated with personal communications, the originator and parties associated with personal communications, the originator and
terminator. These headers or key value pairs are detailed below. terminator. These headers or key value pairs are detailed below.
3.2.1. JWT defined claims 3.2.1. JWT defined claims
3.2.1.1. "iat" - Issued at claim 3.2.1.1. "iat" - Issued at claim
The JSON claim MUST include the following registered JWT defined The JSON claim MUST include the "iat" [RFC7519] defined claim issued
claims: at. As defined this should be set to a date cooresponding to the
origination of the personal communications. The time value should be
o "iat" - issued at, time the JWT was issued, used for expiration. of the format defined in [RFC7519] Section 2 NumericDate. This is
This is included for securing the token against replay and cut and included for securing the token against replay and cut and paste
paste attacks, as explained further in the security considerations attacks, as explained further in the security considerations in
in section 7. section 7.
3.2.2. PASSporT specific claims 3.2.2. PASSporT specific claims
3.2.2.1. Originating and Destination Identities 3.2.2.1. Originating and Destination Identities
Baseline PASSporT defines claims that convey the identity of the Baseline PASSporT defines claims that convey the identity of the
origination and destination of personal communications represented as origination and destination of personal communications represented as
either telephone numbers or Uniform Resource Indicators (URIs). Some either telephone numbers or Uniform Resource Indicators (URIs). Some
using protocols may require other identifiers for personae; these may using protocols may require other identifiers for personae; these may
be specified as claims through the PASSporT extensibility mechanisms. be specified as claims through the PASSporT extensibility mechanisms.
But for telephone numbers and URIs, the following claims should be But for telephone numbers and URIs, the following claims should be
used: used:
skipping to change at page 6, line 47 skipping to change at page 7, line 15
3.2.2.2. "mky" - Media Key claim 3.2.2.2. "mky" - Media Key claim
Some protocols that use PASSporT convey hashes for media security Some protocols that use PASSporT convey hashes for media security
keys within their signaling in order to bind those keys to the keys within their signaling in order to bind those keys to the
identities established in the signaling layers. One example would be identities established in the signaling layers. One example would be
the DTLS-SRTP key fingerprints carried in SDP via the "a=fingerprint" the DTLS-SRTP key fingerprints carried in SDP via the "a=fingerprint"
attribute; multiple instances of that fingerprint may appear in a attribute; multiple instances of that fingerprint may appear in a
single SDP body corresponding to difference media streams offered. single SDP body corresponding to difference media streams offered.
The "mky" value of PASSporT contains a hexadecimal key presentation The "mky" value of PASSporT contains a hexadecimal key presentation
of any hash(es) necessary to establish media security via DTLS-SRTP. of any hash(es) necessary to establish media security via DTLS-SRTP.
Note that per guidance of Section 5 of this document any whitespace This mky value should be formated in a JSON form including the
and line feeds must be removed, however the exception is that a 'algorithm' and 'digest' keys with the corresponding algorithm and
single space (' ') character between the hash algorithm and the hash hexadecimal values. Note that per guidance of Section 5 of this
should remain. If multiple key fingerprints are associated with a document any whitespace and line feeds must be removed. If there is
sessions establishment, then all non-identical key representations multiple fingerprint values, more than one, the fingerprint values
MUST be concatenated, with a semicolon seperation (';') character, should be constructed as a JSON array denoted by bracket characters.
after sorting the values in alphanumeric order, before inserting them
into the "mky" value in PASSporT.
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 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65:2E:7D:46:3F: a=fingerprint:sha-256 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65:
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
a=fingerprint:sha-256 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19: a=fingerprint:sha-256 4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:
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
the PASSporT Payload object would be: the PASSporT Payload object would be:
{ {
"iat":"1443208345", "iat":"1443208345",
"otn":"12155551212", "otn":"12155551212",
"duri":"sip:alice@example.com", "duri":"sip:alice@example.com",
"mky":"sha-256 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65:2E:7D: "mky":"[
46:3F:54:42:CD:54:F1:7A:03:A2:7D:F9:B0:7F:46:19:B2;sha-256 4A:AD:B9: {
B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB:3E:4B: "algorithm":"sha-256",
65:2E:7D:46:3F:54:42:CD:54:F1" "digest":"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"
},
{
"algorithm":"sha-256",
"digest":"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"
}]"
}
3.2.3. Multi-party Communications 3.2.3. Multi-party Communications
Personal communications in the context of PASSporT can certainly Personal communications in the context of PASSporT can certainly
extend to multi-party scenerios where there is more than one extend to multi-party scenerios where there is more than one
destination identity. In the future, it is anticipated that PASSporT destination identity. In the future, it is anticipated that PASSporT
will be extended to support these cases. will be extended to support these cases.
3.3. PASSporT Signature 3.3. PASSporT Signature
skipping to change at page 8, line 18 skipping to change at page 8, line 42
4.1. "ppt" (PASSporT) header parameter 4.1. "ppt" (PASSporT) header parameter
For extended profiles of PASSporT, a new JWS header parameter "ppt" For extended profiles of PASSporT, a new JWS header parameter "ppt"
MUST be used with a string that uniquely identifies the profile MUST be used with a string that uniquely identifies the profile
specification that defines any new claims that would extend the base specification that defines any new claims that would extend the base
set of claims of PASSporT. set of claims of PASSporT.
An example header with an extended PASSporT profile of "foo" is as An example header with an extended PASSporT profile of "foo" is as
follows: follows:
{ {
"typ":"passport", "typ":"passport",
"ppt":"foo", "ppt":"foo",
"alg":"RS256", "alg":"ES256",
"x5u":"https://tel.example.org/passport.crt" "x5u":"https://tel.example.org/passport.crt"
} }
4.2. Extended PASSporT Claims 4.2. Extended PASSporT Claims
Future specifications that define such extensions to the PASSporT Future specifications that define such extensions to the PASSporT
mechanism MUST explicitly designate what claims they include, the mechanism MUST explicitly designate what claims they include, the
order in which they will appear, and any further information order in which they will appear, and any further information
necessary to implement the extension. All extensions MUST necessary to implement the extension. All extensions MUST
incorporate the baseline JWT elements specified in Section 3; claims incorporate the baseline JWT elements specified in Section 3; claims
may only be appended to the claims object specified; they can never may only be appended to the claims object specified; they can never
be subtracted or re-ordered. Specifying new claims follows the be subtracted or re-ordered. Specifying new claims follows the
skipping to change at page 9, line 41 skipping to change at page 10, line 21
In addition, the JSON header and claim members MUST follow the In addition, the JSON header and claim members MUST follow the
lexicographical ordering and character and string rules defined in lexicographical ordering and character and string rules defined in
[RFC7638] Section 3.3. [RFC7638] Section 3.3.
5.1. Example PASSport deterministic JSON form 5.1. Example PASSport deterministic JSON form
For the example PASSporT Payload shown in Section 3.2.2.2, the For the example PASSporT Payload shown in Section 3.2.2.2, the
following is the deterministic JSON object form. following is the deterministic JSON object form.
{"iat": 1443208345,"otn":"12155551212","duri":"sip:alice@example.com", {"iat": 1443208345,"otn":"12155551212","duri":
"mky":"sha-256 02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65:2E:7D:46:3F:54: "sip:alice@example.com","mky":{"algorithm":"sha-256","digest":
42:CD:54:F1:7A:03:A2:7D:F9:B0:7F:46:19:B2;sha-256 4A:AD:B9:B1:3F:82: "02:1A:CC:54:27:AB:EB:9C:53:3F:3E:4B:65:2E:7D:46:3F:54:42:CD:54:
18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB:3E:4B:65:2E:7D:46:3F:54:42: F1:7A:03:A2:7D:F9:B0:7F:46:19:B2;sha-256 4A:AD:B9:B1:3F:82:18:
CD:54:F1"} 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"}}
6. Human Readability 6. Human Readability
JWT [RFC7519] and JWS [RFC7515] are defined to use Base64 and/or UTF8 JWT [RFC7519] and JWS [RFC7515] are defined to use Base64 and/or UTF8
encoding to the Header, Payload, and Signature sections. However, encoding to the Header, Payload, and Signature sections. However,
many personal communications protocols, such as SIP and XMPP, use a many personal communications protocols, such as SIP and XMPP, use a
"human readable" format to allow for ease of use and ease of "human readable" format to allow for ease of use and ease of
operational debugging and monitoring. As such, specifications using operational debugging and monitoring. As such, specifications using
PASSporT may provide guidance on whether Base64 encoding or plain PASSporT may provide guidance on whether Base64 encoding or plain
text will be used for the construction of the PASSporT Header and text will be used for the construction of the PASSporT Header and
skipping to change at page 14, line 19 skipping to change at page 14, line 47
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>.
[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>.
[RFC3325] Jennings, C., Peterson, J., and M. Watson, "Private
Extensions to the Session Initiation Protocol (SIP) for
Asserted Identity within Trusted Networks", RFC 3325,
DOI 10.17487/RFC3325, November 2002,
<http://www.rfc-editor.org/info/rfc3325>.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>. <http://www.rfc-editor.org/info/rfc3986>.
[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
Infrastructure Certificate and Certificate Revocation List Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008, (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008,
<http://www.rfc-editor.org/info/rfc5280>. <http://www.rfc-editor.org/info/rfc5280>.
skipping to change at page 15, line 12 skipping to change at page 15, line 35
(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"", [UNICODE] "The Unicode Consortium, "The Unicode Standard"",
<http://www.unicode.org/versions/latest/>. <http://www.unicode.org/versions/latest/>.
Appendix A. Appendix A. Example PASSporT JWS Serialization and Appendix A. Example ES256 base PASSporT JWS Serialization and Signature
Signature
For PASSporT, there will always be a JWS with the following members: For PASSporT, there will always be a JWS with the following members:
o "protected", with the value BASE64URL(UTF8(JWS Protected Header)) o "protected", with the value BASE64URL(UTF8(JWS Protected Header))
o "payload", with the value BASE64URL (JWS Payload) o "payload", with the value BASE64URL (JWS Payload)
o "signature", with the value BASE64URL(JWS Signature) o "signature", with the value BASE64URL(JWS Signature)
Note: there will never be a JWS Unprotected Header for PASSporT. Note: there will never be a JWS Unprotected Header for PASSporT.
First, an example PASSporT Protected Header is as follows: First, an example PASSporT Protected Header is as follows:
{ {
"typ":"passport", "typ":"passport",
"alg":"RS256", "alg":"ES256",
"x5u":"https://cert.example.org/passport.crt" "x5u":"https://cert.example.org/passport.crt"
} }
This would be serialized to the form: This would be serialized to the form:
{"typ":"passport","alg":"RS256","x5u":"https://cert.example.org/passport.crt"} {"typ":"passport","alg":"ES256","x5u":"https://cert.example.org/
passport.crt"}
Encoding this with UTF8 and BASE64 encoding produces this value: Encoding this with UTF8 and BASE64 encoding produces this value:
eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IlJTMjU2IiwieDV1IjoiaHR0cHM6Ly9j eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IkVTMjU2IiwieDV1IjoiaHR0cHM6Ly9j
ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNydCJ9 ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNydCJ9
Second, an example PASSporT Payload is as follows: Second, an example PASSporT Payload is as follows:
{ {
"iat":"1443208345", "iat":"1443208345",
"otn":"12155551212", "otn":"12155551212",
"duri":"sip:alice@example.com" "duri":"sip:alice@example.com"
} }
This would be serialized to the form: This would be serialized to the form:
{"iat":"1443208345","otn":"12155551212","duri":"sip:alice@example.com"} {"iat":"1443208345","otn":"12155551212","duri":
"sip:alice@example.com"}
Encoding this with the UTF8 and BASE64 encoding produces this value: Encoding this with the UTF8 and BASE64 encoding produces this value:
eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3RuIjoiMTIxNTU1NTEyMTIiLCJkdXJpIjoi eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3RuIjoiMTIxNTU1NTEyMTIiLCJkdXJp
c2lwOmFsaWNlQGV4YW1wbGUuY29tIn0 Ijoic2lwOmFsaWNlQGV4YW1wbGUuY29tIn0
Computing the digital signature of the PASSporT Signing Input Computing the digital signature of the PASSporT Signing Input
ASCII(BASE64URL(UTF8(JWS Protected Header)) || '.' || BASE64URL(JWS ASCII(BASE64URL(UTF8(JWS Protected Header)) || '.' || BASE64URL(JWS
Payload)) Payload))
AaeXRqm7kHnkZu2j6cQmDCiomZRiaE55bYWhFgnX8xMqpBFq96M0xgMM5OLa9_LM KK89q2RFY-BkKQQhiB0z6-fIaFUy6NDyUboKXOix9XnYLxTCjdw1UHjCbw4Ce
rkuKv2ivK5GZz8OlFrmAirucRlAh8YdUkj5Cr5xPRr-gg9acD9jqJUnQ-ZxpL1yq feKwH_t7W-bnGlZz4pI-rMjfQ
-FFVLhvpbsE5NMPHXUp5lpt62rD-S0NlhwHNCeMqZHxt6T5BmZBXITEd1PRRij_6
FhE3wxWEhZMthWJuEbcPpRMZDu-R7lTNddn62nUKjn3s00R3gm25Dto5Z0dzfQpA
ysJvnbc1QRimfsYqJPUFc57lnglVLf4WrpeZCc8-LcoXeSr_dseDgsrmg2EuHmn5
h1nTOmLgF16ZHm121ZVjiXz2sMFvs9RaIxw0AFkM7rnV56OxAFCRuzMNldiEVf8p
lRZVvqZ4BfVQlCNXNyyVgPOUtNr3ta6yD2H0oANQvvHtwjuSwB9Kruj4Wsu5N7Ik
i4MBs6SWJDmcUV-NW_AHYLaao-IvFVe4oCkJNjsqwwXuLv1TO2sDHdc5sQO5zm21
019PPxw1udHVtywsRVNKLo0RzE0TqYUF7XclCDur7MMOx9SnStV2PFIM7Jejyn9x
54RtJEjOnchaSalfIFr_UXqXgVmRZVTzLDQIlcmHjlhhLnCnNx3sYsAANen8Y8jt
fgJ2ewjGotB4Lq8VYe1FacBKKk0VyCfImXba0u1hB8Q
The final PASSporT token is produced by concatenating the values in The final PASSporT token is produced by concatenating the values in
the order Header.Payload.Signature with period (',') characters. For the order Header.Payload.Signature with period (',') characters. For
the above example values this would produce the following: the above example values this would produce the following:
eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IlJTMjU2IiwieDV1IjoiaHR0cHM6Ly9j eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IkVTMjU2IiwieDV1IjoiaHR0cHM6Ly9j
ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNydCJ9 ZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNydCJ9
. .
eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3RuIjoiMTIxNTU1NTEyMTIiLCJkdXJpIjoi eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3RuIjoiMTIxNTU1NTEyMTIiLCJkdXJpIjoi
c2lwOmFsaWNlQGV4YW1wbGUuY29tIn0 c2lwOmFsaWNlQGV4YW1wbGUuY29tIn0
. .
AaeXRqm7kHnkZu2j6cQmDCiomZRiaE55bYWhFgnX8xMqpBFq96M0xgMM5OLa9_LM KK89q2RFY-BkKQQhiB0z6-fIaFUy6NDyUboKXOix9XnYLxTCjdw1UHjCbw4CefeK
rkuKv2ivK5GZz8OlFrmAirucRlAh8YdUkj5Cr5xPRr-gg9acD9jqJUnQ-ZxpL1yq wH_t7W-bnGlZz4pI-rMjfQ
-FFVLhvpbsE5NMPHXUp5lpt62rD-S0NlhwHNCeMqZHxt6T5BmZBXITEd1PRRij_6
FhE3wxWEhZMthWJuEbcPpRMZDu-R7lTNddn62nUKjn3s00R3gm25Dto5Z0dzfQpA
ysJvnbc1QRimfsYqJPUFc57lnglVLf4WrpeZCc8-LcoXeSr_dseDgsrmg2EuHmn5
h1nTOmLgF16ZHm121ZVjiXz2sMFvs9RaIxw0AFkM7rnV56OxAFCRuzMNldiEVf8p
lRZVvqZ4BfVQlCNXNyyVgPOUtNr3ta6yD2H0oANQvvHtwjuSwB9Kruj4Wsu5N7Ik
i4MBs6SWJDmcUV-NW_AHYLaao-IvFVe4oCkJNjsqwwXuLv1TO2sDHdc5sQO5zm21
019PPxw1udHVtywsRVNKLo0RzE0TqYUF7XclCDur7MMOx9SnStV2PFIM7Jejyn9x
54RtJEjOnchaSalfIFr_UXqXgVmRZVTzLDQIlcmHjlhhLnCnNx3sYsAANen8Y8jt
fgJ2ewjGotB4Lq8VYe1FacBKKk0VyCfImXba0u1hB8Q
Appendix B. Appendix B. X.509 Private Key Certificate for Example in A.1. X.509 Private Key Certificate for Example in Appendix A
Appendix A
-----BEGIN RSA PRIVATE KEY----- -----BEGIN EC PRIVATE KEY-----
MIIJKQIBAAKCAgEAsrKb3NsMgrXTzEcNlg3vaBbI12mG3D9QBn61H8PpsVFIh3MA MHcCAQEEIFeZ1R208QCvcu5GuYyMfG4W7sH4m99/7eHSDLpdYllFoAoGCCqGSM49
XNXjkV64he/eEQou3STTEgSqUXj5kj+jnnVFF0Cd0T6j7SuRvpq5YaiKfXgdUlsv AwEHoUQDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH78YTU8qLS8I5HLHSSmlATLcs
F3LjTRGyoKRNOf16f/zEFiyJBX10vj/LKvnWos1vVTSqBeui2dNLynr0+f1n8b0+ lQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g==
0FZwACceo3qaVwuSNIJWSQgM1qAINBpPEKnrIpdt5fa7mUorJ5gjITys3gjNJ4ee -----END EC PRIVATE KEY-----
sjqUEu5ZGXDgMshVtH2iMceC1393sK6rJ7z+g3jVziSo6vy9lA2wveKMuoqQTwp0
V0IrkzExU7vpTzyx0E3mJNmlgmDp7Whp2HCvKjeG+iPfsuPMDRggUrdy9qG6QTFq
QORzLywTpu78ExYMSfqt94NVhf2Dv+QEPoytT1avN6bwGu/R/84g2z0YMfum5roS
TG5PGP4H56vjML8wNTd6v8Ny8SLAgzG/XBaV7c8Ll2awLEj4FSeBpNzTyDgnLrth
7Tk0LmM8EtO1aozDDEaMFrNy4/L+Uuwxp/wcFADawE9N7VdHa9endEo9V/bu1tkq
ecv1Ma+G4NvJZzD8JTBRVsHNc3zvI0qD0KWCjqPvaIMiiVATVAIW9ZEtUZNm5UVu
DzhcY7QrXNRpGE6ULIXgim66mbfUQ0LFq4G+zUjoRZTA92rFBn4vDKvsPs8CAwEA
AQKCAgEAk3Sc9sbucOGXbuZmyJ6hIhRDELXsacv4vhNKZHbmXMJFBjgYYYLBsRAn
VaZUaV0sxKEBZsngvTAFSPAolLYSGBji4Wo+HJQqRM0qEfLgrJ40G+RQXJoaBFuJ
OdO6QhLvRbOPHvkK7DPU5LSBcuoMefTpXLcDYbVKgVJBJUkG405+ulS+A26AJzAg
sSeXOiK7N4chqkvxRB10B4J6IbcE51trfSp3LQutxpNc0a1evC0pFOhtRIbf7yss
7Lhe2KjFSBWvhEIsrqRpYKsRYs4qetR4IQ3RMW7zBLuzT00lcTyrzf1DeUmJ6YDb
Qkw6Pn9H/yp4sYnDcG2GOrhBNy/s6ZecANLDbKg6MqwszDqLZnIOh7zPV1MPGEjc
LkfLue1CA7FaipDUAlSYDfkaNHEcGFxHEgTuv3zmcuMijgNzCtA71M/6kG41DZa1
8PZmqcw8CmMo+1UD3QwL5hHvMbeCyq1UZQvrTmwSLaGjC/goTjChzrsq5NBQcNNb
eiGUFXciqJlh10NfxT8arefoQ/EDuARiZNvwGDqrGkvZk3/xokGeQi6nf1DL4NtU
wQJyzVDJERFs9SohwkJWlPACFxISbxBztyw3nUvGN2iUQdnglGXmwmo7Ork0uook
R2TV1OS7INVOTiEx8AApdiFXWZ752pB96ww6s5pDP3Isp0yxddECggEBAOuSVK2/
7v9aCzlf+IZiklTkpG9CRkBqEsIj6p9ADBMWahqxlzjKwzGJH55v0U/etqOOZYVV
HFzHIzlfZN1Yy1LXYKKcrwU23rLLiG5IsYFCcX2t1Cw6ZxHEsuMsOi8X8IbhSjJe
xTGmwYiJqdKlSyznFopPtZ0leVqMjHTAMCk36AzRwTMnjOIhA1p1Ru0HPFK1RF/5
/EuAUPws2ur1CDjsJwOQa2gRpInbxzZMCE/J+OqgWz4DMivLMCYT40zSjvY7+sqW
K77khwSm9/wMhuvVDedXHaNcrrQQbrk89oYt0Lx74RjUGc/nF79loQDOTZ/Hc7Fq
1Nj2cuw0rIdJoUkCggEBAMIxrp4jSjdNT62WpnTfejJUdLVvn+3zvuNWcwIpUrIl
ILBINlVofMMKLIi0VuqFc7tJiim+dUufp+taoj4E2rPumxZGMb7m9/XGFIyDY+2j
qJEin6kK8WMT5he94C5uQg3faSzMi+sbEa4HSXMhBOP6iLqSQyUZpq1ecRjOdnDk
bWCAHoRRYKSaPMJRdQjHD5++hItLCo2MiwVFBl2nRVh3vHIYARY3K84BMnvbUayd
nfZB/tGOuvTksMRHcqoDFgXNj5/ymqBzoSpQzCMfH79Sv1uQPkDqKO/YbBT3HVDv
6nKX44Vv4iy9Xwqsv3nTtuq2gpFJU30tfHBVltYB91cCggEAUaJhE+EaeoUCtLxM
TI2mNiMR1Lh7zeC0ZXC64rr4NDklReDbDcQ+RlFFkssfFvWQBzfWeJEZBhHAZCZp
tscJlsiqZU+02zK7k+wyeD1avfd/itUNXNJUW3T1pQHzm9RI9wTliHUNEvq9wIos
PqInXgUq631Z635MApQILIFZbz8/fAnIUOjYypg0KEnR7Vv/jI3ihvwDcUqjRfBp
YNjPI6K6lmKaxfKvOVLfQzKwAq50QyKU2/WRklmUcu2bbEjfX/dDHqdRu5JIM9WE
xGS28MzhR5UJ4U3CAQZcyHaW28LOvjKTu93sn/5uXVZjp/rWLZOZxRbHcfRduPs7
+poKeQKCAQBc8nqppip3ncFtTJYPiodqX5Ic5Xie4/ORzGbvueei7LJgra+T4ZcV
o2D9bZPMXGOwWNqQcGCj+Z7dv1u4Y4pqZOJGHwLgZJx6PnzHZHwH2jVsgi35Mwum
aHfRFUif8JYdHbmxf5XYyfQEX+h/+mXk2J1o72jD8Ssd//4R6YA3OJ5BehEhM/IV
1t0OBP8HXH/V7dJy+U/rwEEqHIeXe+BtH6JK2cJrZ6zHxTrsnWTSQf7BR4U3uCEz
5eHVkH0JcsCvtlvwKqZn9fBF2LZceSEw6eI9aSTi3TEK24Of5Uda3fpRLvHvhEW1
NE6xRU3Aed0rKoAEGhyj5YmSGuU/OWGxAoIBAQDbREen8GWGLFmj0iQFs0I2Jr1k
1iazomLyR9Vvhe8sUu57mE0lKbFo6vt8RPm69NSJ7nMCrSbCwG+qERMdMLK8OuiY
v+W3wvvKcpXCShJ1GpgqKmBdP4VnHKvgHQ/kzdtLDmJI4SkTim1Mi94szSMPIfQw
cMdZAGivDPjdXw95xENLClPOkhjX9t/qZjkZclQyjYCYGJHRxX6J7PdcKRY0/9VV
jgRwxooE2POv11/qSk1O3lhFvjjm5oxr7CKPcHvESk/r8mh+VWO4DaOD4gQ9ke00
2QGhocy3K578uL4ph7nfTR2QD96mxCNX9b2Pj9HG8Qb3wEvtaGBfUu8do2mT
-----END RSA PRIVATE KEY-----
Appendix C. Appendix C. X.509 Public Key Certificate for Example in A.2. X.509 Public Key Certificate for Example in Appendix A
Appendix A
-----BEGIN PUBLIC KEY----- -----BEGIN PUBLIC KEY-----
MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAsrKb3NsMgrXTzEcNlg3v MFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE8HNbQd/TmvCKwPKHkMF9fScavGeH
aBbI12mG3D9QBn61H8PpsVFIh3MAXNXjkV64he/eEQou3STTEgSqUXj5kj+jnnVF 78YTU8qLS8I5HLHSSmlATLcslQMhNC/OhlWBYC626nIlo7XeebYS7Sb37g==
F0Cd0T6j7SuRvpq5YaiKfXgdUlsvF3LjTRGyoKRNOf16f/zEFiyJBX10vj/LKvnW -----END PUBLIC KEY-----
os1vVTSqBeui2dNLynr0+f1n8b0+0FZwACceo3qaVwuSNIJWSQgM1qAINBpPEKnr
Ipdt5fa7mUorJ5gjITys3gjNJ4eesjqUEu5ZGXDgMshVtH2iMceC1393sK6rJ7z+
g3jVziSo6vy9lA2wveKMuoqQTwp0V0IrkzExU7vpTzyx0E3mJNmlgmDp7Whp2HCv
KjeG+iPfsuPMDRggUrdy9qG6QTFqQORzLywTpu78ExYMSfqt94NVhf2Dv+QEPoyt
T1avN6bwGu/R/84g2z0YMfum5roSTG5PGP4H56vjML8wNTd6v8Ny8SLAgzG/XBaV
7c8Ll2awLEj4FSeBpNzTyDgnLrth7Tk0LmM8EtO1aozDDEaMFrNy4/L+Uuwxp/wc
FADawE9N7VdHa9endEo9V/bu1tkqecv1Ma+G4NvJZzD8JTBRVsHNc3zvI0qD0KWC
jqPvaIMiiVATVAIW9ZEtUZNm5UVuDzhcY7QrXNRpGE6ULIXgim66mbfUQ0LFq4G+
zUjoRZTA92rFBn4vDKvsPs8CAwEAAQ==
-----END PUBLIC KEY-----
Authors' Addresses Appendix B. Example RS256 base PASSporT JWS Serialization and Signature
For PASSporT, there will always be a JWS with the following members:
o "protected", with the value BASE64URL(UTF8(JWS Protected Header))
o "payload", with the value BASE64URL (JWS Payload)
o "signature", with the value BASE64URL(JWS Signature)
Note: there will never be a JWS Unprotected Header for PASSporT.
First, an example PASSporT Protected Header is as follows:
{
"typ":"passport",
"alg":"RS256",
"x5u":"https://cert.example.org/passport.crt"
}
This would be serialized to the form:
{"typ":"passport","alg":"RS256","x5u":"https://cert.example.org/
passport.crt"}
Encoding this with UTF8 and BASE64 encoding produces this value:
eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IlJTMjU2IiwieDV1IjoiaHR0cHM
6Ly9jZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNydCJ9
Second, an example PASSporT Payload is as follows:
{
"iat":"1443208345",
"otn":"12155551212",
"duri":"sip:alice@example.com"
}
This would be serialized to the form:
{"iat":"1443208345","otn":"12155551212","duri":
"sip:alice@example.com"}
Encoding this with the UTF8 and BASE64 encoding produces this value:
eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3RuIjoiMTIxNTU1NTEyMTIiLCJkdXJp
Ijoic2lwOmFsaWNlQGV4YW1wbGUuY29tIn0
Computing the digital signature of the PASSporT Signing Input
ASCII(BASE64URL(UTF8(JWS Protected Header)) || '.' || BASE64URL(JWS
Payload))
AaeXRqm7kHnkZu2j6cQmDCiomZRiaE55bYWhFgnX8xMqpBFq96M0xgMM5OLa9
_LMrkuKv2ivK5GZz8OlFrmAirucRlAh8YdUkj5Cr5xPRr-gg9acD9jqJUnQ-Z
xpL1yq-FFVLhvpbsE5NMPHXUp5lpt62rD-S0NlhwHNCeMqZHxt6T5BmZBXITE
d1PRRij_6FhE3wxWEhZMthWJuEbcPpRMZDu-R7lTNddn62nUKjn3s00R3gm25
Dto5Z0dzfQpAysJvnbc1QRimfsYqJPUFc57lnglVLf4WrpeZCc8-LcoXeSr_d
seDgsrmg2EuHmn5h1nTOmLgF16ZHm121ZVjiXz2sMFvs9RaIxw0AFkM7rnV56
OxAFCRuzMNldiEVf8plRZVvqZ4BfVQlCNXNyyVgPOUtNr3ta6yD2H0oANQvvH
twjuSwB9Kruj4Wsu5N7Iki4MBs6SWJDmcUV-NW_AHYLaao-IvFVe4oCkJNjsq
wwXuLv1TO2sDHdc5sQO5zm21019PPxw1udHVtywsRVNKLo0RzE0TqYUF7XclC
Dur7MMOx9SnStV2PFIM7Jejyn9x54RtJEjOnchaSalfIFr_UXqXgVmRZVTzLD
QIlcmHjlhhLnCnNx3sYsAANen8Y8jtfgJ2ewjGotB4Lq8VYe1FacBKKk0VyCf
ImXba0u1hB8Q
The final PASSporT token is produced by concatenating the values in
the order Header.Payload.Signature with period (',') characters. For
the above example values this would produce the following:
eyJ0eXAiOiJwYXNzcG9ydCIsImFsZyI6IlJTMjU2IiwieDV1IjoiaHR0cHM6L
y9jZXJ0LmV4YW1wbGUub3JnL3Bhc3Nwb3J0LmNydCJ9
.
eyJpYXQiOiIxNDQzMjA4MzQ1Iiwib3RuIjoiMTIxNTU1NTEyMTIiLCJkdXJpI
joic2lwOmFsaWNlQGV4YW1wbGUuY29tIn0
.
AaeXRqm7kHnkZu2j6cQmDCiomZRiaE55bYWhFgnX8xMqpBFq96M0xgMM5OLa9
_LMrkuKv2ivK5GZz8OlFrmAirucRlAh8YdUkj5Cr5xPRr-gg9acD9jqJUnQ-Z
xpL1yq-FFVLhvpbsE5NMPHXUp5lpt62rD-S0NlhwHNCeMqZHxt6T5BmZBXITE
d1PRRij_6FhE3wxWEhZMthWJuEbcPpRMZDu-R7lTNddn62nUKjn3s00R3gm25
Dto5Z0dzfQpAysJvnbc1QRimfsYqJPUFc57lnglVLf4WrpeZCc8-LcoXeSr_d
seDgsrmg2EuHmn5h1nTOmLgF16ZHm121ZVjiXz2sMFvs9RaIxw0AFkM7rnV56
OxAFCRuzMNldiEVf8plRZVvqZ4BfVQlCNXNyyVgPOUtNr3ta6yD2H0oANQvvH
twjuSwB9Kruj4Wsu5N7Iki4MBs6SWJDmcUV-NW_AHYLaao-IvFVe4oCkJNjsq
wwXuLv1TO2sDHdc5sQO5zm21019PPxw1udHVtywsRVNKLo0RzE0TqYUF7XclC
Dur7MMOx9SnStV2PFIM7Jejyn9x54RtJEjOnchaSalfIFr_UXqXgVmRZVTzLD
QIlcmHjlhhLnCnNx3sYsAANen8Y8jtfgJ2ewjGotB4Lq8VYe1FacBKKk0VyCf
ImXba0u1hB8Q
B.1. X.509 Private Key Certificate for Example in Appendix A
-----BEGIN RSA PRIVATE KEY-----
MIIJKQIBAAKCAgEAsrKb3NsMgrXTzEcNlg3vaBbI12mG3D9QBn61H8PpsVFIh3MA
XNXjkV64he/eEQou3STTEgSqUXj5kj+jnnVFF0Cd0T6j7SuRvpq5YaiKfXgdUlsv
F3LjTRGyoKRNOf16f/zEFiyJBX10vj/LKvnWos1vVTSqBeui2dNLynr0+f1n8b0+
0FZwACceo3qaVwuSNIJWSQgM1qAINBpPEKnrIpdt5fa7mUorJ5gjITys3gjNJ4ee
sjqUEu5ZGXDgMshVtH2iMceC1393sK6rJ7z+g3jVziSo6vy9lA2wveKMuoqQTwp0
V0IrkzExU7vpTzyx0E3mJNmlgmDp7Whp2HCvKjeG+iPfsuPMDRggUrdy9qG6QTFq
QORzLywTpu78ExYMSfqt94NVhf2Dv+QEPoytT1avN6bwGu/R/84g2z0YMfum5roS
TG5PGP4H56vjML8wNTd6v8Ny8SLAgzG/XBaV7c8Ll2awLEj4FSeBpNzTyDgnLrth
7Tk0LmM8EtO1aozDDEaMFrNy4/L+Uuwxp/wcFADawE9N7VdHa9endEo9V/bu1tkq
ecv1Ma+G4NvJZzD8JTBRVsHNc3zvI0qD0KWCjqPvaIMiiVATVAIW9ZEtUZNm5UVu
DzhcY7QrXNRpGE6ULIXgim66mbfUQ0LFq4G+zUjoRZTA92rFBn4vDKvsPs8CAwEA
AQKCAgEAk3Sc9sbucOGXbuZmyJ6hIhRDELXsacv4vhNKZHbmXMJFBjgYYYLBsRAn
VaZUaV0sxKEBZsngvTAFSPAolLYSGBji4Wo+HJQqRM0qEfLgrJ40G+RQXJoaBFuJ
OdO6QhLvRbOPHvkK7DPU5LSBcuoMefTpXLcDYbVKgVJBJUkG405+ulS+A26AJzAg
sSeXOiK7N4chqkvxRB10B4J6IbcE51trfSp3LQutxpNc0a1evC0pFOhtRIbf7yss
7Lhe2KjFSBWvhEIsrqRpYKsRYs4qetR4IQ3RMW7zBLuzT00lcTyrzf1DeUmJ6YDb
Qkw6Pn9H/yp4sYnDcG2GOrhBNy/s6ZecANLDbKg6MqwszDqLZnIOh7zPV1MPGEjc
LkfLue1CA7FaipDUAlSYDfkaNHEcGFxHEgTuv3zmcuMijgNzCtA71M/6kG41DZa1
8PZmqcw8CmMo+1UD3QwL5hHvMbeCyq1UZQvrTmwSLaGjC/goTjChzrsq5NBQcNNb
eiGUFXciqJlh10NfxT8arefoQ/EDuARiZNvwGDqrGkvZk3/xokGeQi6nf1DL4NtU
wQJyzVDJERFs9SohwkJWlPACFxISbxBztyw3nUvGN2iUQdnglGXmwmo7Ork0uook
R2TV1OS7INVOTiEx8AApdiFXWZ752pB96ww6s5pDP3Isp0yxddECggEBAOuSVK2/
7v9aCzlf+IZiklTkpG9CRkBqEsIj6p9ADBMWahqxlzjKwzGJH55v0U/etqOOZYVV
HFzHIzlfZN1Yy1LXYKKcrwU23rLLiG5IsYFCcX2t1Cw6ZxHEsuMsOi8X8IbhSjJe
xTGmwYiJqdKlSyznFopPtZ0leVqMjHTAMCk36AzRwTMnjOIhA1p1Ru0HPFK1RF/5
/EuAUPws2ur1CDjsJwOQa2gRpInbxzZMCE/J+OqgWz4DMivLMCYT40zSjvY7+sqW
K77khwSm9/wMhuvVDedXHaNcrrQQbrk89oYt0Lx74RjUGc/nF79loQDOTZ/Hc7Fq
1Nj2cuw0rIdJoUkCggEBAMIxrp4jSjdNT62WpnTfejJUdLVvn+3zvuNWcwIpUrIl
ILBINlVofMMKLIi0VuqFc7tJiim+dUufp+taoj4E2rPumxZGMb7m9/XGFIyDY+2j
qJEin6kK8WMT5he94C5uQg3faSzMi+sbEa4HSXMhBOP6iLqSQyUZpq1ecRjOdnDk
bWCAHoRRYKSaPMJRdQjHD5++hItLCo2MiwVFBl2nRVh3vHIYARY3K84BMnvbUayd
nfZB/tGOuvTksMRHcqoDFgXNj5/ymqBzoSpQzCMfH79Sv1uQPkDqKO/YbBT3HVDv
6nKX44Vv4iy9Xwqsv3nTtuq2gpFJU30tfHBVltYB91cCggEAUaJhE+EaeoUCtLxM
TI2mNiMR1Lh7zeC0ZXC64rr4NDklReDbDcQ+RlFFkssfFvWQBzfWeJEZBhHAZCZp
tscJlsiqZU+02zK7k+wyeD1avfd/itUNXNJUW3T1pQHzm9RI9wTliHUNEvq9wIos
PqInXgUq631Z635MApQILIFZbz8/fAnIUOjYypg0KEnR7Vv/jI3ihvwDcUqjRfBp
YNjPI6K6lmKaxfKvOVLfQzKwAq50QyKU2/WRklmUcu2bbEjfX/dDHqdRu5JIM9WE
xGS28MzhR5UJ4U3CAQZcyHaW28LOvjKTu93sn/5uXVZjp/rWLZOZxRbHcfRduPs7
+poKeQKCAQBc8nqppip3ncFtTJYPiodqX5Ic5Xie4/ORzGbvueei7LJgra+T4ZcV
o2D9bZPMXGOwWNqQcGCj+Z7dv1u4Y4pqZOJGHwLgZJx6PnzHZHwH2jVsgi35Mwum
aHfRFUif8JYdHbmxf5XYyfQEX+h/+mXk2J1o72jD8Ssd//4R6YA3OJ5BehEhM/IV
1t0OBP8HXH/V7dJy+U/rwEEqHIeXe+BtH6JK2cJrZ6zHxTrsnWTSQf7BR4U3uCEz
5eHVkH0JcsCvtlvwKqZn9fBF2LZceSEw6eI9aSTi3TEK24Of5Uda3fpRLvHvhEW1
NE6xRU3Aed0rKoAEGhyj5YmSGuU/OWGxAoIBAQDbREen8GWGLFmj0iQFs0I2Jr1k
1iazomLyR9Vvhe8sUu57mE0lKbFo6vt8RPm69NSJ7nMCrSbCwG+qERMdMLK8OuiY
v+W3wvvKcpXCShJ1GpgqKmBdP4VnHKvgHQ/kzdtLDmJI4SkTim1Mi94szSMPIfQw
cMdZAGivDPjdXw95xENLClPOkhjX9t/qZjkZclQyjYCYGJHRxX6J7PdcKRY0/9VV
jgRwxooE2POv11/qSk1O3lhFvjjm5oxr7CKPcHvESk/r8mh+VWO4DaOD4gQ9ke00
2QGhocy3K578uL4ph7nfTR2QD96mxCNX9b2Pj9HG8Qb3wEvtaGBfUu8do2mT
-----END RSA PRIVATE KEY-----
B.2. X.509 Public Key Certificate for Example in Appendix A
-----BEGIN PUBLIC KEY-----
MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAsrKb3NsMgrXTzEcNlg3v
aBbI12mG3D9QBn61H8PpsVFIh3MAXNXjkV64he/eEQou3STTEgSqUXj5kj+jnnVF
F0Cd0T6j7SuRvpq5YaiKfXgdUlsvF3LjTRGyoKRNOf16f/zEFiyJBX10vj/LKvnW
os1vVTSqBeui2dNLynr0+f1n8b0+0FZwACceo3qaVwuSNIJWSQgM1qAINBpPEKnr
Ipdt5fa7mUorJ5gjITys3gjNJ4eesjqUEu5ZGXDgMshVtH2iMceC1393sK6rJ7z+
g3jVziSo6vy9lA2wveKMuoqQTwp0V0IrkzExU7vpTzyx0E3mJNmlgmDp7Whp2HCv
KjeG+iPfsuPMDRggUrdy9qG6QTFqQORzLywTpu78ExYMSfqt94NVhf2Dv+QEPoyt
T1avN6bwGu/R/84g2z0YMfum5roSTG5PGP4H56vjML8wNTd6v8Ny8SLAgzG/XBaV
7c8Ll2awLEj4FSeBpNzTyDgnLrth7Tk0LmM8EtO1aozDDEaMFrNy4/L+Uuwxp/wc
FADawE9N7VdHa9endEo9V/bu1tkqecv1Ma+G4NvJZzD8JTBRVsHNc3zvI0qD0KWC
jqPvaIMiiVATVAIW9ZEtUZNm5UVuDzhcY7QrXNRpGE6ULIXgim66mbfUQ0LFq4G+
zUjoRZTA92rFBn4vDKvsPs8CAwEAAQ==
-----END PUBLIC KEY-----
Authors' Addresses
Chris Wendt Chris Wendt
Comcast Comcast
One Comcast Center One Comcast Center
Philadelphia, PA 19103 Philadelphia, PA 19103
USA USA
Email: chris-ietf@chriswendt.net Email: chris-ietf@chriswendt.net
Jon Peterson Jon Peterson
Neustar Inc. Neustar Inc.
 End of changes. 40 change blocks. 
206 lines changed or deleted 301 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/