<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Justin,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In his review comments, Brian wrote:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://openid.net/specs/openid-connect-registration-1_0-14.html#ClientRegisterResponse">http://openid.net/specs/openid-connect-registration-1_0-14.html#ClientRegisterResponse</a><br>
2.2.1. Client Register Operation Response<br>
<br>
This section and 2.2.3 have "Additionally, the server MUST include all registered metadata about a client as described in
<a href="http://openid.net/specs/openid-connect-registration-1_0-14.html#ClientRegistration">
Section 2.1</a>, including any fields that the server has provisioned on the client's behalf." What is the expected behavior for default values from 2.1 (that very well might not be stored anywhere).<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Justin, can you answer Brian’s question about the intent of the text about “fields that the server has provisioned on the client's behalf”? He seems to be raising a point of ambiguity in the registration spec as currently worded.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One aspect of this is whether in an update operation:<o:p></o:p></p>
<p class="MsoNormal">(1) the client should be expected to be able to provide new values for these fields that it didn’t previously request in its initial reservation request,<o:p></o:p></p>
<p class="MsoNormal">(2) the client should be prohibited from providing new values for these fields that it didn’t previously request in its initial reservation request,<o:p></o:p></p>
<p class="MsoNormal">(3) it is unspecified whether the client can providing new values for these fields that it didn’t previously request in its initial reservation request,<o:p></o:p></p>
<p class="MsoNormal">(4) whether the client must provide the same values for these fields that it didn’t previously request in its initial reservation request.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I believe that if we’re going to allow the registration responses to contain the values of fields that were not in the initial registration request and that are potentially not specified in the OpenID Connect specifications, that these
questions need to be answered.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Thanks,<o:p></o:p></p>
<p class="MsoNormal"> -- Mike<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>