One document matched: draft-ietf-stir-passport-00.xml
<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY IANA.MediaTypes SYSTEM "http://www.iana.org/assignments/media-types">
<!ENTITY ietf-stir-rfc4474bis SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-stir-rfc4474bis.xml">
<!ENTITY UNICODE SYSTEM "http://www.unicode.org/versions/latest/">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2046.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3261.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3325.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5280.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.6838.xml">
<!ENTITY RFC7515 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7515.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7518.xml">
<!ENTITY RFC7519 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7519.xml">
<!ENTITY RFC7638 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.7638.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<?rfc strict="yes" ?>
<?rfc toc="yes" ?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc rfcedstyle="no" ?>
<?rfc iprnotified="no" ?>
<?rfc colonspace="yes" ?>
<rfc category="std" docName="draft-ietf-stir-passport-00" ipr="trust200902">
<front>
<title abbrev="PASSporT">Persona Assertion Token</title>
<author fullname="Chris Wendt" initials="C." surname="Wendt" role="editor">
<organization>Comcast</organization>
<address>
<postal>
<street>One Comcast Center</street>
<city>Philadelphia</city>
<region>PA</region>
<code>19103</code>
<country>USA</country>
</postal>
<email>chris-ietf@chriswendt.net</email>
</address>
</author>
<author fullname="Jon Peterson" initials="J." surname="Peterson">
<organization>Neustar Inc.</organization>
<address>
<postal>
<street>1800 Sutter St Suite 570</street>
<city>Concord</city>
<region>CA</region>
<code>94520</code>
<country>US</country>
</postal>
<email>jon.peterson@neustar.biz</email>
</address>
</author>
<date month="February" year="2016" />
<area>ART</area>
<workgroup>STIR</workgroup>
<abstract>
<t> This document defines a token format for verifying with non-repudiation the sender of and authorization to send information related to the originator of personal communications. A cryptographic signature is defined to protect the integrity of the information used to identify the originator of a personal communications session toward a terminating entity. The cryptographic signature is defined with the intention that it can confidently verify the originating persona even when the signature is sent to the terminating party over a potentially unsecure channel. The Persona Assertion Token (PASSporT) is particularly useful for many personal communications applications over IP networks and other multi-hop interconnection scenarios where the originating and terminating parties may not have a direct trusted relationship.</t>
</abstract>
</front>
<middle>
<section title="Introduction" anchor="sec.introduction">
<t>In today's IP-enabled telecommunications world, there is a growing concern about the ability to trust incoming invitations for communications sessions, including video, voice and messaging. As an example, modern telephone networks provide the ability to spoof the telephone number for many legitimate purposes including providing network features and services on the behalf of a legitimate telephone number. However, as we have seen, bad actors have taken advantage of this ability for illegitimate and fraudulent purposes meant to trick telephone users to believe they are someone they are not. This problem can be extended to many emerging forms of personal communications.</t>
<t>This document defines a common method for creating and validating a token that cryptographically verifies an originating identity, or more generally a URI or application specific identity string representing the originator of personal communications. Through extended profiles other information associated with the originating party or the transport of the personal communications can be attached to the token. The primary goal of PASSporT is to provide a common framework for signing persona related information in an extensible way. A secondary goal is to provide this functionality independent of any specific personal communications signaling call logic, so that creation and verification of persona information can be implemented in a flexible way and can be used in many personal communications applications including end-to-end applications that require different signaling protocol interworking. It is anticipated that signaling protocol specific guidance will be provided in other related documents and specifications to specify how to use and transport PASSporT tokens, however this is intentionally out of scope for this document.</t>
<t>Note: As of the authoring of this document, <xref target="I-D.ietf-stir-rfc4474bis"></xref> provides details of how to use PASSporT within SIP signaling for the signing and verification of telephone numbers and there is a parallel.</t>
</section>
<section title="Token Overview" anchor="sec.token_overview">
<t>Tokens are a convenient way of encapsulating information with associated digital signatures. They are used in many applications that require authentication, authorization, encryption and other use cases. JSON Web Token (JWT) <xref target="RFC7519"></xref> and JSON Web Signature (JWS) <xref target="RFC7515"></xref> are designed to provide a compact form for many of these purposes and define a specific method and syntax for signing a specific set of information or "claims" within the token and therefore providing an extensible set of claims. Additionally, JWS provides extensible mechanisms for specifying the method and cryptographic algorithms used for the associated digital signatures.</t>
</section>
<section title="PASSporT Definition" anchor="sec.passport_definition">
<t>The PASSporT is constructed based on JWT <xref target="RFC7519"></xref> and JWS <xref target="RFC7515"></xref> specifications. JWS defines the use of JSON data structures in a specified canonical format for signing data corresponding to JOSE header, JWS Payload, and JWS Signature. JWT defines specific set of claims that are represented by specified key value pairs which can be extended with custom keys for specific applications. </t>
<section title="PASSporT Header" anchor="sec.passport_header">
<t>The JWS token header is a JOSE header <xref target="RFC7515"></xref> that defines the type and encryption algorithm used in the token.</t>
<t>An example of the header for the case of a RSASSA-PKCS1-v1_5 SHA-256 digital signature would be the following,
<figure>
<artwork><![CDATA[
{ "typ":"passport",
"alg":"RS256",
"x5u":"https://cert.example.org/passport.crt" }
]]></artwork>
</figure>
</t>
<section title='"typ" (Type) Header Parameter' anchor="sec.typ_header_parameter">
<t>JWS defines the "typ" (Type) Header Parameter to declare the media type <xref target="IANA.MediaTypes"></xref> of the JWS. </t>
<t>This represents that the encoded token is a JWT, and the JWT is a JWS using the RSASSA-PKCS1-v1_5 SHA-256 algorithm.</t>
<t>For PASSporT Token the "typ" header MUST minimally include and begin with "passport".</t>
</section>
<section title='"alg" (Algorithm) Header Parameter' anchor="sec.alg_header_parameter">
<t>For PASSporT, the "alg" should be defined as RS256 as the recommended algorithm. Note that JWA <xref target="RFC7518"></xref> defines other algorithms that may be utilized or updated in the future depending on cryptographic strength requirements guided by current security best practice.</t>
</section>
<section title='"x5u" (X.509 URL) Header Parameter' anchor="sec.x5u_header_parameter">
<t>As defined in JWS, the "x5u" header parameter is used to provide a URI <xref target="RFC3986"></xref> referring to the resource for the X.509 public key certificate or certificate chain <xref target="RFC5280"></xref> corresponding to the key 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 of scope of this document. However, generally this would correspond to an HTTPS or DNSSEC resource with the guidance that it MUST be a TLS protected, per JWS spec.</t>
</section>
</section>
<section title="PASSporT Token Claim" anchor="sec.passport_token_claim">
<t>The token claim should consist of the information which needs to be verified at the terminating party. This claim should correspond to a JWT claim and be encoded as defined by the JWS Payload. </t>
<t>The PASSporT defines the use of a number of standard JWT defined headers as well as two new custom headers corresponding to the two parties associated with personal communications, the originator and terminator. These headers or key value pairs are detailed below.</t>
<t>The JSON claim MUST include the following registered JWT defined claims:</t>
<t>
<list style="symbols">
<t>"iat" - issued at, time the JWT was issued, used for expiration. This is included for securing the token against replay and cut and paste attacks, as explained further in the security considerations in section 7.</t>
</list>
</t>
<t>Verified Token specific claims that MUST be included:</t>
<t>
<list style="symbols">
<t>"orig" - the originating identity claimed. (e.g. for SIP, the FROM or P-AssertedID <xref target="RFC3325"></xref> associated e.164 telephone number, TEL or SIP URI) This SHOULD be in URI format as defined in <xref target="RFC3986"></xref> if appropriate but could also be an application specific identity string.</t>
<t>"term" - the terminating identity claimed as the intended destination by the originating party. (e.g. for SIP, the TO associated e.164 telephone number, TEL or SIP URI) This SHOULD be in URI format as defined in <xref target="RFC3986"></xref> if appropriate but could also be an application specific identity string.</t>
</list>
</t>
<t>An example claim is as follows,
<figure>
<artwork><![CDATA[
{ "iat": 1443208345,
"orig":"+12155551212",
"term":"sip:+12155551213@example.com" }
]]></artwork>
</figure>
</t>
</section>
<section title="PASSporT Signature" anchor="sec.passport_signature">
<t>The signature of the PASSporT is created as specified by JWS using the private key corresponding to the X.509 public key certificate referenced by the "x5u" header parameter. </t>
</section>
</section>
<section title="Extending PASSporT" anchor="sec.extending_passport">
<t>PASSporT represents the bare minimum set of claims needed to assert the originating identity, however there will certainly be new and extended applications and usage of PASSPorT that will need to extending claims to represent other information specific to the origination identities beyond the identity itself.</t>
<t>There are two mechanisms defined to extend PASSporT. The first includes an extension of the base passport claims to include additional claims. An alternative method of extending PASSporT is for applications of PASSporT unrelated to the base set of claims, that will define it's own set of claims. Both are described below.</t>
<section title='"ppt" (PASSporT) header parameter' anchor="sec.passport_header_parameter">
<t>For extended profiles of PASSporT, a new JWS header parameter "ppt" MUST be used with a string that uniquely identifies the profile specification that defines any new claims that would extend the base set of claims of PASSporT.</t>
<t>An example header with an extended PASSporT profile of "foo" is as follows:
<figure>
<artwork><![CDATA[
{ "typ":"passport",
"ppt":"foo",
"alg":"RS256",
"x5u":"https://tel.example.org/passport.crt" }
]]></artwork>
</figure>
</t>
</section>
<section title="Extended PASSporT Claims" anchor="sec.extended_passport_claims">
<t>Future specifications that define such extensions to the PASSporT mechanism MUST explicitly designate what claims they include, the order in which they will appear, and any further information necessary to implement the extension. All extensions MUST incorporate the baseline JWT elements specified in Section 3; claims may only be appended to the claims object specified in there, they can never be subtracted re-ordered. Specifying new claims follows the baseline JWT procedures (<xref target="RFC7519"></xref> Section 10.1). Note that understanding an extension as a verifier is always optional for compliance with this specification (though future specifications or
profiles for deployment environments may make other "ppt" values mandatory). The creator of a PASSporT object cannot assume that verifiers will understand any given extension. Verifiers that do support an extension may then trigger appropriate application-level behavior in the presence of an extension; authors of extensions should provide appropriate extension-specific guidance to application developers on this point.</t>
</section>
<section title="Alternate PASSporT Extension" anchor="sec.alternate_passport_extension">
<t>Some applications may want to use the mechanism of the PASSporT digital signature that is not a superset of the base set of claims of the PASSporT token as defined in Section 3. Rather, a specification may use PASSporT with its own defined set of claims.</t>
<t>In this case, the specification should define its own MIME media type <xref target="RFC2046"></xref> in the "Media Types" registry <xref target="IANA.MediaTypes"></xref>. It is recommended that the MIME subtype start with the string "passport-" to signify that it is related to the PASSporT token. For example, for the "foo" application the MIME type/sub-type could be defined as "application/passport-foo".</t>
</section>
<section title="Registering PASSporT Extensions" anchor="sec.registering_passport_extensions">
<t>In order for interoperability and maintaining uniqueness of the extended PASSporT profile header parameter string, there SHOULD be an industry registry that tracks the definition of the profile strings.</t>
</section>
</section>
<section title="Deterministic JSON Serialization" anchor="sec.deterministic_json_serialization">
<t>In order to provide a deterministic representation of the PASSporT Header and Claims, particularly if PASSporT is used across multiple signaling environments, the JSON header object and JSON Claim object MUST be computed as follows.</t>
<t>The JSON object MUST follow the rules for the construction of the thumbprint of a JSON Web Key (JWK) as defined in <xref target="RFC7638"></xref> Section 3. Each JSON object MUST contain no whitespace or line breaks before or after any syntactic elements and with the required members ordered lexicographically by the Unicode <xref target="UNICODE"></xref> code points of the member names.</t>
<t>In addition, the JSON header and claim members MUST follow the lexicographical ordering and character and string rules defined in <xref target="RFC7638"></xref> Section 3.3.</t>
</section>
<section title="Human Readability" anchor="sec.human_readability">
<t>For many applications, JWT <xref target="RFC7519"></xref> and JWS <xref target="RFC7515"></xref> can use Base64 encoding to the Header and Claims sections as specified. However, many personal communications protocols, such as SIP and XMPP, use a "human readable" format to allow for ease of use and ease of operational debugging and monitoring. As such, specifications using PASSporT may provide guidance on whether Base64 encoding or plain text will be used for the construction of the PASSporT Header and Claim sections.</t>
</section>
<section title="Security Considerations" anchor="sec.security_considerations">
<section title="Avoidance of replay and cut and paste attacks" anchor="sec.avoidance_of_attacks">
<t>There are a number of security considerations for use of the token for avoidance of replay and cut and paste attacks. Verified tokens must be sent along with other application level protocol information (e.g. for SIP an INVITE as defined in <xref target="RFC3261"></xref>). There should be a link between various information provided in the token and information provided by the application level protocol information.</t>
<t>These would include:
<list style="symbols">
<t>"iat" claim should closely correspond to a date/time the message was originated. It should also be within a relative delta time that is reasonable for clock drift and transmission time characteristics associated with the application using the verified token.</t>
<t>"term" claim is included to prevent the ability to use a previously originated message to send to another terminating party</t>
</list>
</t>
</section>
<section title="Solution Considerations" anchor="sec.solution_considerations">
<t>It should be recognized that the use of this token should not, in it's own right, be considered a full solution for absolute non-repudiation of the persona being asserted. This only provides non-repudiation of the signer of PASSporT. If the signer and the persona are not one in the same, which can and often can be the case in telecommunications networks today, protecting the terminating party for being spoofed may take some interpretation or additional verification of the link between the PASSporT signature and the persona being asserted.</t>
<t>In addition, the telecommunications systems and specifications that use PASSporT should in practice provide mechanisms for:
<list style="symbols">
<t>Managing X.509 certificates and X.509 certificate chains to an authorized trust anchor that can be a trusted entity to all participants in the telecommunications network</t>
<t>Accounting for entities that may route calls from other peer or interconnected telecommunications networks that are not part of the "trusted" communications network or may not be following the usage of PASSporT or the profile of PASSporT appropriate to that network</t>
<t>Following best practices around management and security of X.509 certificates</t>
</list>
</t>
</section>
</section>
<section title="IANA Considerations" anchor="sec.iana_considerations">
<section title="Media Type Registration" anchor="sec.media_type_registration">
<section title="Media Type Registry Contents Additions Requested" anchor="sec.media_type_request">
<t>This section registers the "application/passport" media type <xref target="RFC2046"></xref> in the "Media Types" registry <xref target="IANA.MediaTypes"></xref> in the manner described in <xref target="RFC6838"></xref>, which can be used to indicate that the content is a PASSporT defined JWT and JWS.</t>
<t>
<list style="symbols">
<t>Type name: application</t>
<t>Subtype name: passport</t>
<t>Required parameters: n/a</t>
<t>Optional parameters: n/a</t>
<t>Encoding considerations: 8bit; application/passport values are encoded as a series of base64url-encoded values (some of which may be the empty string), each separated from the next by a single period ('.') character.</t>
<t>Security considerations: See the Security Considerations section of RFC 7515.</t>
<t>Interoperability considerations: n/a</t>
<t>Published specification: draft-ietf-stir-passport-00</t>
<t>Applications that use this media type: STIR and other applications that require identity related assertion</t>
<t>Fragment identifier considerations: n/a</t>
<t>Additional information:
<list style="symbols">
<t>Magic number(s): n/a</t>
<t>File extension(s): n/a</t>
<t>Macintosh file type code(s): n/a</t>
</list>
</t>
<t>Person and email address to contact for further information: Chris Wendt, chris-ietf@chriswendt.net</t>
<t>Intended usage: COMMON</t>
<t>Restrictions on usage: none</t>
<t>Author: Chris Wendt, chris-ietf@chriswendt.net</t>
<t>Change Controller: IESG</t>
<t>Provisional registration? No</t>
</list>
</t>
</section>
</section>
<section title="JSON Web Token Claims Registration" anchor="sec.json_web_token_claims_registration">
<section title="Registry Contents Additions Requested" anchor="sec.registry_contents_additions_request">
<t>
<list style="symbols">
<t>Claim Name: "orig"</t>
<t>Claim Description: Originating Identity String</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 3.2 of draft-ietf-stir-passport-00</t>
</list>
</t>
<t>
<list style="symbols">
<t>Claim Name: "term"</t>
<t>Claim Description: Terminating Identity String</t>
<t>Change Controller: IESG</t>
<t>Specification Document(s): Section 3.2 of draft-ietf-stir-passport-00</t>
</list>
</t>
</section>
</section>
</section>
<section title="Acknowledgements" anchor="sec.acknowledgements">
<t>Particular thanks to members of the ATIS and SIP Forum NNI Task Group including Jim McEchern, Martin Dolly, Richard Shockey, John Barnhill, Christer Holmberg, Victor Pascual Avila, Mary Barnes, and Eric Burger for their review, ideas, and contributions. Also thanks to Henning Schulzrinne, Russ Housley, Alan Johnston, and Richard Barnes for valuable feedback on the technical and security aspects of the document.</t>
</section>
</middle>
<back>
<references title="References">
<reference anchor="IANA.MediaTypes" target="Media Types">
<front>
<title>IANA, "Media Types"</title>
<author/>
<date/>
</front>
</reference>
<reference anchor="I-D.ietf-stir-rfc4474bis">
<front>
<title>Authenticated Identity Management in the Session Initiation Protocol (SIP)</title>
<author initials="J" surname="Peterson" fullname="Jon Peterson">
<organization/>
</author>
<author initials="C" surname="Jennings" fullname="Cullen Jennings">
<organization/>
</author>
<author initials="E" surname="Rescorla" fullname="Eric Rescorla">
<organization/>
</author>
<author initials="C" surname="Wendt" fullname="Chris Wendt">
<organization/>
</author>
<date month="February" day="3" year="2016"/>
</front>
<seriesInfo name="Internet-Draft" value="draft-ietf-stir-rfc4474bis-07"/>
<format type="TXT" target="http://www.ietf.org/internet-drafts/draft-ietf-stir-rfc4474bis-07.txt"/>
</reference>
<reference anchor="UNICODE" target="http://www.unicode.org/versions/latest/">
<front>
<title>The Unicode Consortium, "The Unicode Standard"</title>
<author/>
<date/>
</front>
</reference>
<reference anchor="RFC2046" target="http://www.rfc-editor.org/info/rfc2046">
<front>
<title>Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</title>
<author initials="N." surname="Freed" fullname="N. Freed">
<organization/>
</author>
<author initials="N." surname="Borenstein" fullname="N. Borenstein">
<organization/>
</author>
<date year="1996" month="November"/>
</front>
<seriesInfo name="RFC" value="2046"/>
<seriesInfo name="DOI" value="10.17487/RFC2046"/>
</reference>
<reference anchor="RFC3261" target="http://www.rfc-editor.org/info/rfc3261">
<front>
<title>SIP: Session Initiation Protocol</title>
<author initials="J." surname="Rosenberg" fullname="J. Rosenberg">
<organization/>
</author>
<author initials="H." surname="Schulzrinne" fullname="H. Schulzrinne">
<organization/>
</author>
<author initials="G." surname="Camarillo" fullname="G. Camarillo">
<organization/>
</author>
<author initials="A." surname="Johnston" fullname="A. Johnston">
<organization/>
</author>
<author initials="J." surname="Peterson" fullname="J. Peterson">
<organization/>
</author>
<author initials="R." surname="Sparks" fullname="R. Sparks">
<organization/>
</author>
<author initials="M." surname="Handley" fullname="M. Handley">
<organization/>
</author>
<author initials="E." surname="Schooler" fullname="E. Schooler">
<organization/>
</author>
<date year="2002" month="June"/>
</front>
<seriesInfo name="RFC" value="3261"/>
<seriesInfo name="DOI" value="10.17487/RFC3261"/>
</reference>
<reference anchor="RFC3325" target="http://www.rfc-editor.org/info/rfc3325">
<front>
<title>Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks</title>
<author initials="C." surname="Jennings" fullname="C. Jennings">
<organization/>
</author>
<author initials="J." surname="Peterson" fullname="J. Peterson">
<organization/>
</author>
<author initials="M." surname="Watson" fullname="M. Watson">
<organization/>
</author>
<date year="2002" month="November"/>
</front>
<seriesInfo name="RFC" value="3325"/>
<seriesInfo name="DOI" value="10.17487/RFC3325"/>
</reference>
<reference anchor="RFC3986" target="http://www.rfc-editor.org/info/rfc3986">
<front>
<title>Uniform Resource Identifier (URI): Generic Syntax</title>
<author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
<organization/>
</author>
<author initials="R." surname="Fielding" fullname="R. Fielding">
<organization/>
</author>
<author initials="L." surname="Masinter" fullname="L. Masinter">
<organization/>
</author>
<date year="2005" month="January"/>
</front>
<seriesInfo name="STD" value="66"/>
<seriesInfo name="RFC" value="3986"/>
<seriesInfo name="DOI" value="10.17487/RFC3986"/>
</reference>
<reference anchor="RFC5280" target="http://www.rfc-editor.org/info/rfc5280">
<front>
<title>Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile</title>
<author initials="D." surname="Cooper" fullname="D. Cooper">
<organization/>
</author>
<author initials="S." surname="Santesson" fullname="S. Santesson">
<organization/>
</author>
<author initials="S." surname="Farrell" fullname="S. Farrell">
<organization/>
</author>
<author initials="S." surname="Boeyen" fullname="S. Boeyen">
<organization/>
</author>
<author initials="R." surname="Housley" fullname="R. Housley">
<organization/>
</author>
<author initials="W." surname="Polk" fullname="W. Polk">
<organization/>
</author>
<date year="2008" month="May"/>
</front>
<seriesInfo name="RFC" value="5280"/>
<seriesInfo name="DOI" value="10.17487/RFC5280"/>
</reference>
<reference anchor="RFC6838" target="http://www.rfc-editor.org/info/rfc6838">
<front>
<title>Media Type Specifications and Registration Procedures</title>
<author initials="N." surname="Freed" fullname="N. Freed">
<organization/>
</author>
<author initials="J." surname="Klensin" fullname="J. Klensin">
<organization/>
</author>
<author initials="T." surname="Hansen" fullname="T. Hansen">
<organization/>
</author>
<date year="2013" month="January"/>
</front>
<seriesInfo name="BCP" value="13"/>
<seriesInfo name="RFC" value="6838"/>
<seriesInfo name="DOI" value="10.17487/RFC6838"/>
</reference>
<reference anchor="RFC7515" target="http://www.rfc-editor.org/info/rfc7515">
<front>
<title>JSON Web Signature (JWS)</title>
<author initials="M." surname="Jones" fullname="M. Jones">
<organization/>
</author>
<author initials="J." surname="Bradley" fullname="J. Bradley">
<organization/>
</author>
<author initials="N." surname="Sakimura" fullname="N. Sakimura">
<organization/>
</author>
<date year="2015" month="May"/>
</front>
<seriesInfo name="RFC" value="7515"/>
<seriesInfo name="DOI" value="10.17487/RFC7515"/>
</reference>
<reference anchor="RFC7518" target="http://www.rfc-editor.org/info/rfc7518">
<front>
<title>JSON Web Algorithms (JWA)</title>
<author initials="M." surname="Jones" fullname="M. Jones">
<organization/>
</author>
<date year="2015" month="May"/>
</front>
<seriesInfo name="RFC" value="7518"/>
<seriesInfo name="DOI" value="10.17487/RFC7518"/>
</reference>
<reference anchor="RFC7519" target="http://www.rfc-editor.org/info/rfc7519">
<front>
<title>JSON Web Token (JWT)</title>
<author initials="M." surname="Jones" fullname="M. Jones">
<organization/>
</author>
<author initials="J." surname="Bradley" fullname="J. Bradley">
<organization/>
</author>
<author initials="N." surname="Sakimura" fullname="N. Sakimura">
<organization/>
</author>
<date year="2015" month="May"/>
</front>
<seriesInfo name="RFC" value="7519"/>
<seriesInfo name="DOI" value="10.17487/RFC7519"/>
</reference>
<reference anchor="RFC7638" target="http://www.rfc-editor.org/info/rfc7638">
<front>
<title>JSON Web Key (JWK) Thumbprint</title>
<author initials="M." surname="Jones" fullname="M. Jones">
<organization/>
</author>
<author initials="N." surname="Sakimura" fullname="N. Sakimura">
<organization/>
</author>
<date year="2015" month="September"/>
</front>
<seriesInfo name="RFC" value="7638"/>
<seriesInfo name="DOI" value="10.17487/RFC7638"/>
</reference>
</references>
</back>
</rfc>| PAFTECH AB 2003-2026 | 2026-04-23 00:08:51 |