<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>OpenID Connect UserInfo 1.0 - draft 01</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="description" content="OpenID Connect UserInfo 1.0 - draft 01">
<meta name="generator" content="xml2rfc v1.36 (http://xml.resource.org/)">
<style type="text/css"><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* 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 { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tbody><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tbody><tr><td class="header">Network Working Group</td><td class="header">N. Sakimura, Ed.</td></tr>
<tr><td class="header">Internet-Draft</td><td class="header">NRI</td></tr>
<tr><td class="header">Intended status: Experimental</td><td class="header">J. Bradley</td></tr>
<tr><td class="header">Expires: November 25, 2011</td><td class="header">Protiviti Government Services</td></tr>
<tr><td class="header"> </td><td class="header">M. Jones</td></tr>
<tr><td class="header"> </td><td class="header">Microsoft</td></tr>
<tr><td class="header"> </td><td class="header">E. Jay</td></tr>
<tr><td class="header"> </td><td class="header">MGI1</td></tr>
<tr><td class="header"> </td><td class="header">May 24, 2011</td></tr>
</tbody></table></td></tr></tbody></table>
<h1><br>OpenID Connect UserInfo 1.0 - draft 01<br>draft-openid-userinfo-0_1.xml</h1>
<h3>Abstract</h3>
<p>This specification describes the schema and format returned by the UserInfo endpoint of OpenID Connect.
</p>
<h3>Requirements Language</h3>
<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in <a class="info" href="#RFC2119">RFC 2119<span> (</span><span class="info">Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a> [RFC2119].
</p>
<h3>Status of this Memo</h3>
<p>
This Internet-Draft is submitted in full
conformance with the provisions of BCP 78 and BCP 79.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current
Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any time.
It is inappropriate to use Internet-Drafts as reference material or to cite
them other than as “work in progress.”</p>
<p>
This Internet-Draft will expire on November 25, 2011.</p>
<h3>Copyright Notice</h3>
<p>
Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved.</p>
<p>
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.</p>
<a name="toc"></a><br><hr>
<h3>Table of Contents</h3>
<p class="toc">
<a href="#anchor1">1.</a>
Terminology<br>
<a href="#anchor2">2.</a>
UserInfo Endpoint<br>
<a href="#anchor3">2.1.</a>
Requests<br>
<a href="#anchor4">2.2.</a>
Responses<br>
<a href="#anchor5">2.2.1.</a>
Example Responses<br>
<a href="#anchor6">2.3.</a>
Errors<br>
<a href="#anchor7">3.</a>
Other Items for Consideration<br>
<a href="#anchor8">4.</a>
To Do<br>
<a href="#IANA">5.</a>
IANA Considerations<br>
<a href="#Security">6.</a>
Security Considerations<br>
<a href="#Acknowledgements">7.</a>
Acknowledgements<br>
<a href="#rfc.references1">8.</a>
Normative References<br>
<a href="#rfc.authors">§</a>
Authors' Addresses<br>
</p>
<br clear="all">
<a name="anchor1"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.1"></a><h3>1.
Terminology</h3>
<p>See <a class="info" href="#OpenID.CC">OpenID Connect Core<span> (</span><span class="info">Recordon, D., Sakimura, N., Bradley, J., de Madeiros, B., and M. Jones, “OpenID Connect Connect Core 1.0,” January 2011.</span><span>)</span></a> [OpenID.CC] for terminology used in this specification.
</p>
<a name="anchor2"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.2"></a><h3>2.
UserInfo Endpoint</h3>
<p>The UserInfo Endpoint returns claims for the authenticated user.
</p>
<p>Claim objects contain members and member values which are the
individual claims and claims values. A claim object is represented by a
JSON object which contains a collection of name/value pairs for the
claims.
</p>
<a name="anchor3"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.2.1"></a><h3>2.1.
Requests</h3>
<p>Clients MAY send requests with the following parameters to the UserInfo Endpoint to obtain further information about the user.
</p>
<p></p>
<blockquote class="text"><dl>
<dt>access_token</dt>
<dd>REQUIRED. The access_token obtained from an OpenID Connect authorization request.
</dd>
<dt>schema</dt>
<dd>OPTIONAL. The schema in which the data is to be returned. The only
predefined value is "openid". If this parameter is not included, the
response may be a proprietary format to support backwards compatibility.
Custom scheme names and responses are out of scope for this
specification.
</dd>
<dt>id</dt>
<dd>RESERVED. This is reserved for backwards compatibility. It MUST be ignored by the endpoint if the "openid" schema is used.
</dd>
</dl></blockquote>
<a name="anchor4"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.2.2"></a><h3>2.2.
Responses</h3>
<p>If the requested schema is "openid", the response SHOULD return a
plain text JSON object which contains a set of claims which are a subset
of the <a class="info" href="#POCO">Portable Contacts<span> (</span><span class="info">Smarr, J., “Portable Contacts 1.0 Draft C.,” August 2008.</span><span>)</span></a>
[POCO] schema. Following the Portable Contacts draft specification,
claim values can be simple strings, boolean values containing the
strings "true" or "false", or complex values which contain child
attributes and their values. In addition, claims can be singular or
plural values. Plural values contain multiple complex values which
contain the "value", and optional "type" and "primary" attributes.
</p>
<p>The following are the subset of claims that are returned:</p>
<blockquote class="text"><dl>
<dt>displayName</dt>
<dd>The display name of the user.
</dd>
<dt>nickname</dt>
<dd>The nickname of the user.
</dd>
<dt>name</dt>
<dd>A complex claim value that contains the formatted, familyName,
givenName, middleName, honorificPrefix, honorificSuffix attributes.
</dd>
<dt>photos</dt>
<dd>An plural claim value that contains canonicalized URLs to the user's profile pictures.
</dd>
<dt>emails</dt>
<dd>A plural claim value that contains canonicalized email addresses for
the user. Each email claim MAY have an optional "type" and a boolean
"primary" attribute. In addition, a boolean "verified" attribute is
defined to indicated whether the email address has been verified. Email
address verification is beyond the scope of this specification.
</dd>
<dt>phoneNumbers</dt>
<dd>A plural claim containing the user's phone numbers. The phone number values are not canonicalized.
</dd>
<dt>urls</dt>
<dd>An plural claim value that contains canonicalized URLs to the user's
web pages. Each claim MAY have an optional "type" attribute to indicate
what kind of URL the value is referring to. E.g. "blog", "profile",
etc.
</dd>
<dt>birthday</dt>
<dd>The user's birthday in the format YYYY-MM-DD. The year value MAY be
set to 0000 when the age of the user is private or the year is not
available.
</dd>
<dt>updated</dt>
<dd>The most recent time that the user's information has been updated. It is represented in full UTC date-time format as defined in <a class="info" href="#RFC3339">RFC 3339<span> (</span><span class="info">Klyne, G., Ed. and C. Newman, “Date and Time on the Internet: Timestamps,” July 2002.</span><span>)</span></a> [RFC3339].
</dd>
<dt>gender</dt>
<dd>The user's gender which can be "male", "female", "undisclosed", or any other value in which the user's gender is defined.
</dd>
<dt>addresses</dt>
<dd>A plural complex value containing the user's addresses. The address
values contains the "formatted", "streetAddress", "locality", "region",
"postalCode", and "country" attributes.
</dd>
<dt>utcOffset</dt>
<dd>The user's current timezone offset in the format +/-HH:MM.
</dd>
<dt>language</dt>
<dd>The user's preferred language as specified by <a class="info" href="#ISO639">ISO639<span> (</span><span class="info">, “ISO639,” .</span><span>)</span></a> [ISO639].
</dd>
<dt></dt>
<dd>
</dd>
</dl></blockquote>
<p>For privacy reasons, OpenID providers may elect to not provide values for some schema elements as part of the "openid" scope.
</p>
<p>The UserInfo endpoint will return claims in JSON format unless a
request for a different format is made by the RP in the Authorization
request. See the <a class="info" href="#OpenID.CC">OpenID Connect Core<span> (</span><span class="info">Recordon, D., Sakimura, N., Bradley, J., de Madeiros, B., and M. Jones, “OpenID Connect Connect Core 1.0,” January 2011.</span><span>)</span></a>
[OpenID.CC] specification on how to request a different format. The
UserInfo Endpoint MUST return a content-type header to indicate which
format is being returned. The following are accepted content types:
</p><table class="all" align="center" border="0" cellpadding="2" cellspacing="2">
<colgroup><col align="left"><col align="left">
</colgroup><tbody><tr><th align="left">Content-Type</th><th align="left">Format Returned</th></tr>
<tr>
<td align="left">application/json</td>
<td align="left">plain text JSON object</td>
</tr>
<tr>
<td align="left">application/jwt</td>
<td align="left">A JWT</td>
</tr>
</tbody></table>
<br clear="all">
<a name="anchor5"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.2.2.1"></a><h3>2.2.1.
Example Responses</h3>
<p>The following is a non-normative normal claims response:
</p>
<p></p>
<div style="display: table; width: 0; margin-left: 3em; margin-right: auto"><pre>{
"name": {"givenName": "Jane", "familyName": "Doe"},
"displayName": "Jane Doe",
"emails": [
{"value": "janedoe@example.com", "primary": true, "verified": true}
],
"photos": [
{"value": "https://example.com/profiles/janedoe/photo.jpg", "type": "photo"},
{"value": "https://example.com/profiles/janedoe/thumb.jpg", "type": "thumbnail"}
]
}</pre></div><p>
</p>
<a name="anchor6"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.2.3"></a><h3>2.3.
Errors</h3>
<p>In addition to the standard <a class="info" href="#OAuth2.0">OAuth 2.0<span> (</span><span class="info">Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, “OAuth 2.0 Authorization Protocol,” November 2011.</span><span>)</span></a> [OAuth2.0] errors, the UserInfor endpoint may return the following errors:
</p>
<p>The Authorization Server includes one of the following error codes with the error response:
</p>
<p></p>
<blockquote class="text"><dl>
<dt>unsupported_schema</dt>
<dd>The requested schema is unsupported.
</dd>
</dl></blockquote>
<a name="anchor7"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.3"></a><h3>3.
Other Items for Consideration</h3>
<p>
</p>
<a name="anchor8"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.4"></a><h3>4.
To Do</h3>
<p></p>
<ol class="text">
<li>Add internationalization/multiple scripts for languages
</li>
</ol>
<a name="IANA"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.5"></a><h3>5.
IANA Considerations</h3>
<p>This document makes no request of IANA.
</p>
<p>Note to RFC Editor: this section may be removed on publication as an RFC.
</p>
<a name="Security"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.6"></a><h3>6.
Security Considerations</h3>
<p>
</p>
<a name="Acknowledgements"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<a name="rfc.section.7"></a><h3>7.
Acknowledgements</h3>
<p>
</p>
<a name="rfc.references1"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<h3>8. Normative References</h3>
<table width="99%" border="0">
<tbody><tr><td class="author-text" valign="top"><a name="Bearer.Token">[Bearer.Token]</a></td>
<td class="author-text">Recordon, D., Jones, M., and D. Hardt, “<a href="http://self-issued.info/docs/draft-ietf-oauth-v2-bearer.html">OAuth 2.0 Protocol: Bearer Tokens</a>,” May 2011.</td></tr>
<tr><td class="author-text" valign="top"><a name="ISO639">[ISO639]</a></td>
<td class="author-text">“<a href="http://www.w3.org/WAI/ER/IG/ert/iso639.htm">ISO639</a>.”</td></tr>
<tr><td class="author-text" valign="top"><a name="JWE">[JWE]</a></td>
<td class="author-text">Jones, M., Bradley, J., and N. Sakimura, “<a href="http://self-issued.info/docs/draft-jones-json-web-signature-01.html">JSON Web Encryption</a>,” March 2011.</td></tr>
<tr><td class="author-text" valign="top"><a name="JWS">[JWS]</a></td>
<td class="author-text">Jones, M., Balfanz, D., Bradley, J., Goland, Y., Panzer, J., Sakimura, N., and P. Tarjan, “<a href="http://self-issued.info/docs/draft-jones-json-web-signature-01.html">JSON Web Signatures</a>,” March 2011.</td></tr>
<tr><td class="author-text" valign="top"><a name="JWT">[JWT]</a></td>
<td class="author-text">Jones, M., Balfanz, D., Bradley, J., Goland, Y., Panzer, J., Sakimura, N., and P. Tarjan, “<a href="http://self-issued.info/docs/draft-jones-json-web-token-03.html">JSON Web Token</a>,” March 2011.</td></tr>
<tr><td class="author-text" valign="top"><a name="OAuth2.0">[OAuth2.0]</a></td>
<td class="author-text">Hammer-Lahav, E., Ed., Recordon, D., and D. Hardt, “<a href="http://tools.ietf.org/html/draft-ietf-oauth-v2-16">OAuth 2.0 Authorization Protocol</a>,” November 2011.</td></tr>
<tr><td class="author-text" valign="top"><a name="OpenID.2.0">[OpenID.2.0]</a></td>
<td class="author-text">specs@openid.net, “OpenID Authentication 2.0,” 2007 (<a href="http://www.openid.net/specs/openid-authentication-2_0.txt">TXT</a>, <a href="http://www.openid.net/specs/openid-authentication-2_0.html">HTML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="OpenID.AB">[OpenID.AB]</a></td>
<td class="author-text">Sakimura, N., Ed., Bradley, J., de Madeiros, B., Ito, R., and M. Jones, “<a href="http://openid4.us/specs/ab/openid-connect-ab-1_0.html">OpenID Connect Artifact Binding 1.0</a>,” January 2011.</td></tr>
<tr><td class="author-text" valign="top"><a name="OpenID.CC">[OpenID.CC]</a></td>
<td class="author-text">Recordon, D., Sakimura, N., Bradley, J., de Madeiros, B., and M. Jones, “<a href="http://openid4.us/specs/ab/openid-connect-core-1_0.html">OpenID Connect Connect Core 1.0</a>,” January 2011.</td></tr>
<tr><td class="author-text" valign="top"><a name="POCO">[POCO]</a></td>
<td class="author-text">Smarr, J., “<a href="http://portablecontacts.net/draft-spec.html">Portable Contacts 1.0 Draft C.</a>,” August 2008.</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td>
<td class="author-text"><a href="mailto:sob@harvard.edu">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>,” BCP 14, RFC 2119, March 1997 (<a href="http://www.rfc-editor.org/rfc/rfc2119.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc2119.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc2119.xml">XML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC3339">[RFC3339]</a></td>
<td class="author-text"><a href="mailto:GK@ACM.ORG">Klyne, G., Ed.</a> and <a href="mailto:chris.newman@sun.com">C. Newman</a>, “<a href="http://tools.ietf.org/html/rfc3339">Date and Time on the Internet: Timestamps</a>,” RFC 3339, July 2002 (<a href="http://www.rfc-editor.org/rfc/rfc3339.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc3339.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc3339.xml">XML</a>).</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC3986">[RFC3986]</a></td>
<td class="author-text"><a href="mailto:timbl@w3.org">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com">Fielding, R.</a>, and <a href="mailto:LMM@acm.org">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>,” STD 66, RFC 3986, January 2005 (<a href="http://www.rfc-editor.org/rfc/rfc3986.txt">TXT</a>, <a href="http://xml.resource.org/public/rfc/html/rfc3986.html">HTML</a>, <a href="http://xml.resource.org/public/rfc/xml/rfc3986.xml">XML</a>).</td></tr>
</tbody></table>
<a name="rfc.authors"></a><br><hr>
<table summary="layout" class="TOCbug" align="right" cellpadding="0" cellspacing="2"><tbody><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></tbody></table>
<h3>Authors' Addresses</h3>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tbody><tr><td class="author-text"> </td>
<td class="author-text">Nat Sakimura (editor)</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Nomura Research Institute, Ltd.</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a></td></tr>
<tr cellpadding="3"><td> </td><td> </td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">John Bradley</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Protiviti Government Services</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:jbradley@mac.com">jbradley@mac.com</a></td></tr>
<tr cellpadding="3"><td> </td><td> </td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Mike Jones</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Microsoft Corporation</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a></td></tr>
<tr cellpadding="3"><td> </td><td> </td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">Edmund Jay</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">MGI1</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:ejay@mgi1.com">ejay@mgi1.com</a></td></tr>
</tbody></table>
</body></html>