<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii" />
<title>JWT Claims for W3C Verifiable Credentials Objects 1.0, draft 00</title>
<style type="text/css" title="Xml2Rfc (sans serif)">
/*<![CDATA[*/
a {
text-decoration: none;
}
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a.smpl {
color: black;
}
a:hover {
text-decoration: underline;
}
a:active {
text-decoration: underline;
}
address {
margin-top: 1em;
margin-left: 2em;
font-style: normal;
}
body {
color: black;
font-family: verdana, helvetica, arial, sans-serif;
font-size: 10pt;
max-width: 55em;
}
cite {
font-style: normal;
}
dd {
margin-right: 2em;
}
dl {
margin-left: 2em;
}
ul.empty {
list-style-type: none;
}
ul.empty li {
margin-top: .5em;
}
dl p {
margin-left: 0em;
}
dt {
margin-top: .5em;
}
h1 {
font-size: 14pt;
line-height: 21pt;
page-break-after: avoid;
}
h1.np {
page-break-before: always;
}
h1 a {
color: #333333;
}
h2 {
font-size: 12pt;
line-height: 15pt;
page-break-after: avoid;
}
h3, h4, h5, h6 {
font-size: 10pt;
page-break-after: avoid;
}
h2 a, h3 a, h4 a, h5 a, h6 a {
color: black;
}
img {
margin-left: 3em;
}
li {
margin-left: 2em;
margin-right: 2em;
}
ol {
margin-left: 2em;
margin-right: 2em;
}
ol p {
margin-left: 0em;
}
p {
margin-left: 2em;
margin-right: 2em;
}
pre {
margin-left: 3em;
background-color: lightyellow;
padding: .25em;
}
pre.text2 {
border-style: dotted;
border-width: 1px;
background-color: #f0f0f0;
width: 69em;
}
pre.inline {
background-color: white;
padding: 0em;
}
pre.text {
border-style: dotted;
border-width: 1px;
background-color: #f8f8f8;
width: 69em;
}
pre.drawing {
border-style: solid;
border-width: 1px;
background-color: #f8f8f8;
padding: 2em;
}
table {
margin-left: 2em;
}
table.tt {
vertical-align: top;
}
table.full {
border-style: outset;
border-width: 1px;
}
table.headers {
border-style: outset;
border-width: 1px;
}
table.tt td {
vertical-align: top;
}
table.full td {
border-style: inset;
border-width: 1px;
}
table.tt th {
vertical-align: top;
}
table.full th {
border-style: inset;
border-width: 1px;
}
table.headers th {
border-style: none none inset none;
border-width: 1px;
}
table.left {
margin-right: auto;
}
table.right {
margin-left: auto;
}
table.center {
margin-left: auto;
margin-right: auto;
}
caption {
caption-side: bottom;
font-weight: bold;
font-size: 9pt;
margin-top: .5em;
}
table.header {
border-spacing: 1px;
width: 95%;
font-size: 10pt;
color: white;
}
td.top {
vertical-align: top;
}
td.topnowrap {
vertical-align: top;
white-space: nowrap;
}
table.header td {
background-color: gray;
width: 50%;
}
table.header a {
color: white;
}
td.reference {
vertical-align: top;
white-space: nowrap;
padding-right: 1em;
}
thead {
display:table-header-group;
}
ul.toc, ul.toc ul {
list-style: none;
margin-left: 1.5em;
margin-right: 0em;
padding-left: 0em;
}
ul.toc li {
line-height: 150%;
font-weight: bold;
font-size: 10pt;
margin-left: 0em;
margin-right: 0em;
}
ul.toc li li {
line-height: normal;
font-weight: normal;
font-size: 9pt;
margin-left: 0em;
margin-right: 0em;
}
li.excluded {
font-size: 0pt;
}
ul p {
margin-left: 0em;
}
.comment {
background-color: yellow;
}
.center {
text-align: center;
}
.error {
color: red;
font-style: italic;
font-weight: bold;
}
.figure {
font-weight: bold;
text-align: center;
font-size: 9pt;
}
.filename {
color: #333333;
font-weight: bold;
font-size: 12pt;
line-height: 21pt;
text-align: center;
}
.fn {
font-weight: bold;
}
.hidden {
display: none;
}
.left {
text-align: left;
}
.right {
text-align: right;
}
.title {
color: #990000;
font-size: 18pt;
line-height: 18pt;
font-weight: bold;
text-align: center;
margin-top: 36pt;
}
.vcardline {
display: block;
}
.warning {
font-size: 14pt;
background-color: yellow;
}
@media print {
.noprint {
display: none;
}
a {
color: black;
text-decoration: none;
}
table.header {
width: 90%;
}
td.header {
width: 50%;
color: black;
background-color: white;
vertical-align: top;
font-size: 12pt;
}
ul.toc a::after {
content: leader('.') target-counter(attr(href), page);
}
ul.ind li li a {
content: target-counter(attr(href), page);
}
.print2col {
column-count: 2;
-moz-column-count: 2;
column-fill: auto;
}
}
@page {
@top-left {
content: "Internet-Draft";
}
@top-right {
content: "December 2010";
}
@top-center {
content: "Abbreviated Title";
}
@bottom-left {
content: "Doe";
}
@bottom-center {
content: "Expires June 2011";
}
@bottom-right {
content: "[Page " counter(page) "]";
}
}
@page:first {
@top-left {
content: normal;
}
@top-right {
content: normal;
}
@top-center {
content: normal;
}
}
/*]]>*/
</style>
<link href="#rfc.toc" rel="Contents">
<link href="#rfc.section.1" rel="Chapter" title="1 Introduction">
<link href="#rfc.section.1.1" rel="Chapter" title="1.1 Requirements Language">
<link href="#rfc.section.1.2" rel="Chapter" title="1.2 Terminology">
<link href="#rfc.section.2" rel="Chapter" title="2 JWT Claims for W3C VC Objects">
<link href="#rfc.section.2.1" rel="Chapter" title='2.1 "vc_jwt" Claim'>
<link href="#rfc.section.2.2" rel="Chapter" title='2.2 "vp_jwt" Claim'>
<link href="#rfc.section.2.3" rel="Chapter" title='2.3 "vc_ld" Claim'>
<link href="#rfc.section.2.4" rel="Chapter" title='2.4 "vp_ld" Claim'>
<link href="#rfc.section.3" rel="Chapter" title="3 IANA Considerations">
<link href="#rfc.section.3.1" rel="Chapter" title="3.1 JSON Web Token Claims Registration">
<link href="#rfc.section.3.1.1" rel="Chapter" title="3.1.1 Registry Contents">
<link href="#rfc.section.4" rel="Chapter" title="4 Security Considerations">
<link href="#rfc.references" rel="Chapter" title="5 References">
<link href="#rfc.references.1" rel="Chapter" title="5.1 Normative References">
<link href="#rfc.references.2" rel="Chapter" title="5.2 Informative References">
<link href="#rfc.appendix.A" rel="Chapter" title="A Acknowledgements">
<link href="#rfc.appendix.B" rel="Chapter" title="B Notices">
<link href="#rfc.authors" rel="Chapter">
<meta name="generator" content="xml2rfc version 3.7.0 - https://tools.ietf.org/tools/xml2rfc" />
<link rel="schema.dct" href="http://purl.org/dc/terms/" />
<meta name="dct.creator" content="Jones, M., Yasuda, K., and O. Terbu" />
<meta name="dct.identifier" content="urn:ietf:id:jwt-claims-for-vc-objects-1_0" />
<meta name="dct.issued" scheme="ISO8601" content="2021-04-08" />
<meta name="dct.abstract" content="There are use cases in which it is desirable to communicate data structures defined by the W3C Verifiable Credentials Data Model 1.0 specification as JSON Web Token (JWT) claims. This specification defines and registers JWT claims for communicating each of these four data structures defined by W3C Verifiable Credentials Data Model 1.0 specification: a verifiable credential represented as a JWT, a verifiable presentation represented as a JWT, a verifiable credential represented in JSON-LD, and a verifiable presentation represented in JSON-LD. " />
<meta name="description" content="There are use cases in which it is desirable to communicate data structures defined by the W3C Verifiable Credentials Data Model 1.0 specification as JSON Web Token (JWT) claims. This specification defines and registers JWT claims for communicating each of these four data structures defined by W3C Verifiable Credentials Data Model 1.0 specification: a verifiable credential represented as a JWT, a verifiable presentation represented as a JWT, a verifiable credential represented in JSON-LD, and a verifiable presentation represented in JSON-LD. " />
</head>
<body>
<table class="header">
<tbody>
<tr>
<td class="left"></td>
<td class="right">M. Jones</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">K. Yasuda</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">Microsoft</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">O. Terbu</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">ConsenSys Mesh</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">April 8, 2021</td>
</tr>
</tbody>
</table>
<p class="title">JWT Claims for W3C Verifiable Credentials Objects 1.0, draft 00<br />
<span class="filename">jwt-claims-for-vc-objects-1_0</span></p>
<h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
<p>There are use cases in which it is desirable to communicate data structures defined by the W3C Verifiable Credentials Data Model 1.0 specification as JSON Web Token (JWT) claims. This specification defines and registers JWT claims for communicating each of these four data structures defined by W3C Verifiable Credentials Data Model 1.0 specification: a verifiable credential represented as a JWT, a verifiable presentation represented as a JWT, a verifiable credential represented in JSON-LD, and a verifiable presentation represented in JSON-LD. </p>
<hr class="noprint" />
<h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
<ul class="toc">
<li>1. <a href="#rfc.section.1">Introduction</a>
</li>
<ul><li>1.1. <a href="#rfc.section.1.1">Requirements Language</a>
</li>
<li>1.2. <a href="#rfc.section.1.2">Terminology</a>
</li>
</ul><li>2. <a href="#rfc.section.2">JWT Claims for W3C VC Objects</a>
</li>
<ul><li>2.1. <a href="#rfc.section.2.1">"vc_jwt" Claim</a>
</li>
<li>2.2. <a href="#rfc.section.2.2">"vp_jwt" Claim</a>
</li>
<li>2.3. <a href="#rfc.section.2.3">"vc_ld" Claim</a>
</li>
<li>2.4. <a href="#rfc.section.2.4">"vp_ld" Claim</a>
</li>
</ul><li>3. <a href="#rfc.section.3">IANA Considerations</a>
</li>
<ul><li>3.1. <a href="#rfc.section.3.1">JSON Web Token Claims Registration</a>
</li>
<ul><li>3.1.1. <a href="#rfc.section.3.1.1">Registry Contents</a>
</li>
</ul></ul><li>4. <a href="#rfc.section.4">Security Considerations</a>
</li>
<li>5. <a href="#rfc.references">References</a>
</li>
<ul><li>5.1. <a href="#rfc.references.1">Normative References</a>
</li>
<li>5.2. <a href="#rfc.references.2">Informative References</a>
</li>
</ul><li>Appendix A. <a href="#rfc.appendix.A">Acknowledgements</a>
</li>
<li>Appendix B. <a href="#rfc.appendix.B">Notices</a>
</li>
<li><a href="#rfc.authors">Authors' Addresses</a>
</li>
</ul>
<h1 id="rfc.section.1">
<a href="#rfc.section.1">1.</a> <a href="#Introduction" id="Introduction">Introduction</a>
</h1>
<p id="rfc.section.1.p.1">Numerous kinds systems use JSON Web Tokens (JWTs) <a href="#RFC7519" class="xref">[RFC7519]</a> to communicate claims between parties in a standard manner. The W3C Verifiable Credentials Data Model 1.0 specification <a href="#VC" class="xref">[VC]</a> defines several kinds of JSON-based data structures that could be passed as values of JavaScript Object Notation (JSON) <a href="#RFC8259" class="xref">[RFC8259]</a> objects, including as JWT claim values. </p>
<p id="rfc.section.1.p.2">This specification defines and registers JWT claims for communicating each of these four data structures defined by W3C Verifiable Credentials Data Model 1.0 specification: a verifiable credential represented as a JWT, a verifiable presentation represented as a JWT, a verifiable credential represented in JSON-LD <a href="#JSON-LD" class="xref">[JSON-LD]</a>, and a verifiable presentation represented in JSON-LD. Having these claims means that these data structures can be communicated in a standard way in applicaitons employing JWT claims. </p>
<p id="rfc.section.1.p.3">For example, OpenID Connect <a href="#OpenID.Core" class="xref">[OpenID.Core]</a> uses JWT claims in ID Tokens and as UserInfo Endpoint response values, as well as in other data structures. Note that while ID Tokens are JWTs, UserInfo Endpoint response values are simply JSON objects. The claims defined by this specification could be used in ID Tokens, UserInfo Endpoint responses, and any other data structures employing JWT claims. </p>
<h1 id="rfc.section.1.1">
<a href="#rfc.section.1.1">1.1.</a> <a href="#rnc" id="rnc">Requirements Language</a>
</h1>
<p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <a href="#RFC2119" class="xref">[RFC2119]</a> <a href="#RFC8174" class="xref">[RFC8174]</a> when, and only when, they appear in all capitals, as shown here. </p>
<h1 id="rfc.section.1.2">
<a href="#rfc.section.1.2">1.2.</a> <a href="#Terminology" id="Terminology">Terminology</a>
</h1>
<p id="rfc.section.1.2.p.1">This specification uses the terms defined by <a href="#RFC7519" class="xref">JSON Web Token (JWT)</a> and by <a href="#VC" class="xref">W3C Verifiable Credentials Data Model 1.0</a>. </p>
<h1 id="rfc.section.2">
<a href="#rfc.section.2">2.</a> <a href="#Claims" id="Claims">JWT Claims for W3C VC Objects</a>
</h1>
<p id="rfc.section.2.p.1">This specification defines the following claims for communicating data structures defined by the W3C Verifiable Credentials Data Model 1.0 specification as JWT claims. </p>
<h1 id="rfc.section.2.1">
<a href="#rfc.section.2.1">2.1.</a> <a href="#vc_jwt" id="vc_jwt">"vc_jwt" Claim</a>
</h1>
<p id="rfc.section.2.1.p.1">The <samp>vc_jwt</samp> claim's value is a W3C verifiable credential (VC) object using the JWT representation, which is a JSON string. The claim's value may also be an array of W3C verifiable credential objects using the JWT representation, if the use case calls for multiple JWT VCs. </p>
<h1 id="rfc.section.2.2">
<a href="#rfc.section.2.2">2.2.</a> <a href="#vp_jwt" id="vp_jwt">"vp_jwt" Claim</a>
</h1>
<p id="rfc.section.2.2.p.1">The <samp>vp_jwt</samp> claim's value is a W3C verifiable presentation (VP) object using the JWT representation, which is a JSON string. The claim's value may also be an array of W3C verifiable presentation objects using the JWT representation, if the use case calls for multiple JWT VPs. </p>
<h1 id="rfc.section.2.3">
<a href="#rfc.section.2.3">2.3.</a> <a href="#vc_ld" id="vc_ld">"vc_ld" Claim</a>
</h1>
<p id="rfc.section.2.3.p.1">The <samp>vc_ld</samp> claim's value is a W3C verifiable credential (VC) object using the JSON-LD representation, which is a JSON object. The claim's value may also be an array of W3C verifiable credential objects using the JSON-LD representation, if the use case calls for multiple JSON-LD VCs. </p>
<h1 id="rfc.section.2.4">
<a href="#rfc.section.2.4">2.4.</a> <a href="#vp_ld" id="vp_ld">"vp_ld" Claim</a>
</h1>
<p id="rfc.section.2.4.p.1">The <samp>vp_ld</samp> claim's value is a W3C verifiable presentation (VP) object using the JSON-LD representation, which is a JSON object. The claim's value may also be an array of W3C verifiable presentation objects using the JSON-LD representation, if the use case calls for multiple JSON-LD VPs. </p>
<h1 id="rfc.section.3">
<a href="#rfc.section.3">3.</a> <a href="#IANA" id="IANA">IANA Considerations</a>
</h1>
<h1 id="rfc.section.3.1">
<a href="#rfc.section.3.1">3.1.</a> <a href="#ClaimsRegistry" id="ClaimsRegistry">JSON Web Token Claims Registration</a>
</h1>
<p id="rfc.section.3.1.p.1">This specification registers the Claims defined in <a href="#Claims" class="xref">Section 2</a> in the IANA "JSON Web Token Claims" registry <a href="#IANA.JWT.Claims" class="xref">[IANA.JWT.Claims]</a> established by <a href="#RFC7519" class="xref">[RFC7519]</a>. </p>
<h1 id="rfc.section.3.1.1">
<a href="#rfc.section.3.1.1">3.1.1.</a> <a href="#ClaimsContents" id="ClaimsContents">Registry Contents</a>
</h1>
<p></p>
<ul>
<li>Claim Name: <samp>vc_jwt</samp> </li>
<li>Claim Description: W3C verifiable credential (VC) object using the JWT representation, or an array thereof </li>
<li>Change Controller: OpenID Foundation Artifact Binding Working Group - openid-specs-ab@lists.openid.net </li>
<li>Specification Document(s): <a href="#vc_jwt" class="xref">Section 2.1</a> of this document </li>
</ul>
<p> </p>
<p></p>
<ul>
<li>Claim Name: <samp>vp_jwt</samp> </li>
<li>Claim Description: W3C verifiable presentation (VP) object using the JWT representation, or an array thereof </li>
<li>Change Controller: OpenID Foundation Artifact Binding Working Group - openid-specs-ab@lists.openid.net </li>
<li>Specification Document(s): <a href="#vp_jwt" class="xref">Section 2.2</a> of this document </li>
</ul>
<p> </p>
<p></p>
<ul>
<li>Claim Name: <samp>vc_ld</samp> </li>
<li>Claim Description: W3C verifiable credential (VC) object using the JSON-LD representation, or an array thereof </li>
<li>Change Controller: OpenID Foundation Artifact Binding Working Group - openid-specs-ab@lists.openid.net </li>
<li>Specification Document(s): <a href="#vc_ld" class="xref">Section 2.3</a> of this document </li>
</ul>
<p> </p>
<p></p>
<ul>
<li>Claim Name: <samp>vp_ld</samp> </li>
<li>Claim Description: W3C verifiable presentation (VP) object using the JSON-LD representation, or an array thereof </li>
<li>Change Controller: OpenID Foundation Artifact Binding Working Group - openid-specs-ab@lists.openid.net </li>
<li>Specification Document(s): <a href="#vp_ld" class="xref">Section 2.4</a> of this document </li>
</ul>
<p> </p>
<h1 id="rfc.section.4">
<a href="#rfc.section.4">4.</a> <a href="#Security" id="Security">Security Considerations</a>
</h1>
<p id="rfc.section.4.p.1">The security considerations of <a href="#RFC7519" class="xref">JSON Web Token (JWT)</a> and <a href="#VC" class="xref">W3C Verifiable Credentials Data Model 1.0</a> apply to this specification. </p>
<h1 id="rfc.references">
<a href="#rfc.references">5.</a> References</h1>
<h1 id="rfc.references.1">
<a href="#rfc.references.1">5.1.</a> Normative References</h1>
<table><tbody>
<tr>
<td class="reference"><b id="JSON-LD">[JSON-LD]</b></td>
<td class="top">
<a>Sporny, M.</a>, <a>Longley, D.</a>, <a>Kellogg, G.</a>, <a>Lanthaler, M.</a>, <a>Champin, P.</a> and <a>G. Lindström</a>, "<a href="https://www.w3.org/TR/2020/REC-json-ld11-20200716/">JSON-LD 1.1</a>", W3C Recommendation, July 2020.</td>
</tr>
<tr>
<td class="reference"><b id="RFC2119">[RFC2119]</b></td>
<td class="top">
<a>Bradner, S.</a>, "<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.</td>
</tr>
<tr>
<td class="reference"><b id="RFC7519">[RFC7519]</b></td>
<td class="top">
<a>Jones, M.</a>, <a>Bradley, J.</a> and <a>N. Sakimura</a>, "<a href="https://tools.ietf.org/html/rfc7519">JSON Web Token (JWT)</a>", RFC 7519, DOI 10.17487/RFC7519, May 2015.</td>
</tr>
<tr>
<td class="reference"><b id="RFC8174">[RFC8174]</b></td>
<td class="top">
<a>Leiba, B.</a>, "<a href="https://tools.ietf.org/html/rfc8174">Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</a>", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017.</td>
</tr>
<tr>
<td class="reference"><b id="RFC8259">[RFC8259]</b></td>
<td class="top">
<a>Bray, T.</a>, "<a href="https://tools.ietf.org/html/rfc8259">The JavaScript Object Notation (JSON) Data Interchange Format</a>", STD 90, RFC 8259, DOI 10.17487/RFC8259, December 2017.</td>
</tr>
<tr>
<td class="reference"><b id="VC">[VC]</b></td>
<td class="top">
<a>Sporny, M.</a>, <a>Longley, D.</a> and <a>D. Chadwick</a>, "<a href="https://www.w3.org/TR/2019/REC-vc-data-model-20191119">Verifiable Credentials Data Model 1.0</a>", W3C Recommendation, November 2019.</td>
</tr>
</tbody></table>
<h1 id="rfc.references.2">
<a href="#rfc.references.2">5.2.</a> Informative References</h1>
<table><tbody>
<tr>
<td class="reference"><b id="IANA.JWT.Claims">[IANA.JWT.Claims]</b></td>
<td class="top">
<a>IANA</a>, "<a href="https://www.iana.org/assignments/jwt">JSON Web Token Claims</a>"</td>
</tr>
<tr>
<td class="reference"><b id="OpenID.Core">[OpenID.Core]</b></td>
<td class="top">
<a title="NAT Consulting">Sakimura, N.</a>, <a title="Ping Identity">Bradley, J.</a>, <a title="Microsoft">Jones, M.</a>, <a title="Google">de Medeiros, B.</a> and <a title="Salesforce">C. Mortimore</a>, "<a href="https://openid.net/specs/openid-connect-core-1_0.html">OpenID Connect Core 1.0</a>", OpenID Foundation Standards, February 2014.</td>
</tr>
</tbody></table>
<h1 id="rfc.appendix.A">
<a href="#rfc.appendix.A">Appendix A.</a> <a href="#Acknowledgements" id="Acknowledgements">Acknowledgements</a>
</h1>
<p id="rfc.section.A.p.1">The need for and design of these claims, enabling integration of the JWT and VC worlds, resulted from discussions in the OpenID Connect working group. </p>
<h1 id="rfc.appendix.B">
<a href="#rfc.appendix.B">Appendix B.</a> <a href="#Notices" id="Notices">Notices</a>
</h1>
<p id="rfc.section.B.p.1">Copyright (c) 2021 The OpenID Foundation.</p>
<p id="rfc.section.B.p.2">The OpenID Foundation (OIDF) grants to any Contributor, developer, implementer, or other interested party a non-exclusive, royalty free, worldwide copyright license to reproduce, prepare derivative works from, distribute, perform and display, this Implementers Draft or Final Specification solely for the purposes of (i) developing specifications, and (ii) implementing Implementers Drafts and Final Specifications based on such documents, provided that attribution be made to the OIDF as the source of the material, but that such attribution does not indicate an endorsement by the OIDF. </p>
<p id="rfc.section.B.p.3">The technology described in this specification was made available from contributions from various sources, including members of the OpenID Foundation and others. Although the OpenID Foundation has taken steps to help ensure that the technology is available for distribution, it takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this specification or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any independent effort to identify any such rights. The OpenID Foundation and the contributors to this specification make no (and hereby expressly disclaim any) warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to this specification, and the entire risk as to implementing this specification is assumed by the implementer. The OpenID Intellectual Property Rights policy requires contributors to offer a patent promise not to assert certain patent claims against other contributors and against implementers. The OpenID Foundation invites any interested party to bring to its attention any copyrights, patents, patent applications, or other proprietary rights that may cover technology that may be required to practice this specification. </p>
<h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
<div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Michael B. Jones</span>
<span class="n hidden">
<span class="family-name">Jones</span>
</span>
</span>
<span class="org vcardline">Microsoft</span>
<span class="adr">
<span class="vcardline">
<span class="locality"></span>
<span class="region"></span>
<span class="code"></span>
</span>
<span class="country-name vcardline"></span>
</span>
<span class="vcardline">EMail: <a href="mailto:mbj@microsoft.com">mbj@microsoft.com</a></span>
<span class="vcardline">URI: <a href="https://self-issued.info/">https://self-issued.info/</a></span>
</address>
</div><div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Kristina Yasuda</span>
<span class="n hidden">
<span class="family-name">Yasuda</span>
</span>
</span>
<span class="org vcardline">Microsoft</span>
<span class="adr">
<span class="vcardline">
<span class="locality"></span>
<span class="region"></span>
<span class="code"></span>
</span>
<span class="country-name vcardline"></span>
</span>
<span class="vcardline">EMail: <a href="mailto:kristina.yasuda@microsoft.com">kristina.yasuda@microsoft.com</a></span>
<span class="vcardline">URI: <a href="https://twitter.com/kristinayasuda">https://twitter.com/kristinayasuda</a></span>
</address>
</div><div class="avoidbreak">
<address class="vcard">
<span class="vcardline">
<span class="fn">Oliver Terbu</span>
<span class="n hidden">
<span class="family-name">Terbu</span>
</span>
</span>
<span class="org vcardline">ConsenSys Mesh</span>
<span class="adr">
<span class="vcardline">
<span class="locality"></span>
<span class="region"></span>
<span class="code"></span>
</span>
<span class="country-name vcardline"></span>
</span>
<span class="vcardline">EMail: <a href="mailto:oliver.terbu@mesh.xyz">oliver.terbu@mesh.xyz</a></span>
<span class="vcardline">URI: <a href="https://twitter.com/OliverTerbu">https://twitter.com/OliverTerbu</a></span>
</address>
</div>
</body>
</html>