<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Marcos,<div class=""><br class=""></div><div class="">Two more comments.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 29 Oct 2019, at 16:43, Marcos Sanz via Openid-specs-ab <<a href="mailto:openid-specs-ab@lists.openid.net" class="">openid-specs-ab@lists.openid.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">- Section 3.6, "max_path_length" and "naming_constraints": this is new and <br class="">interesting. However, there's no explanation later about when/how these <br class="">parameters are to be processed. Further: I am not sure these parameters <br class="">are well-placed as "metadata", since they are not information from the <br class="">entity about the entity itself, but it's a kind of policy imposed by the <br class="">relevant entity further down the tree. So: What about moving these two to <br class="">"metadata_policy"?</div></div></blockquote><div><br class=""></div>I’ve contemplating giving them a section of their own.</div><div>As you say they don’t really fit as metadata but also they are not about</div><div>metadata policies. They are concerned with trust chain validation.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">- Section 9.2.2.1, step 4: It says "the entity statement is sent to the <br class="">federation_registration_endpoint" and it left me wondering how. If this is <br class="">a POST, it has to be clarified (specially since Section 6 says "all <br class="">operations in the specification make use of a GET request"). An example <br class="">would also help.<br class=""></div></div></blockquote><br class=""></div><div>The sentence about GET requests are about the federation API.</div><div>The client sends its entity statement to the federation_registration_endpoint </div><div>which is not part of the federation API. </div><div>As you guessed POST is used to send the client registration information.</div><br class=""><div class="">
<div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">- Roland</div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">Otium cum dignitate - latin proverb</div></div>
</div>
<br class=""></div></body></html>