<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Well said Scott, Farell and Sam.<div><br></div><div>We know where we are heading policy wise. The Board’s support for the EWG, and the beginning of a series of PDPs that will change the Whois policy rules make that very clear. So we need technical support for a changed policy world</div><div><br></div><div>Holly<br><div><div>On 31 Jan 2016, at 8:48 am, Sam Lanfranco <<a href="mailto:sam@lanfranco.net">sam@lanfranco.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000" style="font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><p class="MsoNormal" style="margin: 0cm 0cm 10pt; line-height: 17px; font-size: 11pt; font-family: Calibri, sans-serif;"><br>Scott makes an important point here.<br> The work of this group is to build in a policy led process that is constrained or enabled by the technology.<br> It is not to build in a technology led process that is constrained or enabled by the policy.<o:p></o:p></p>Sam L.<br><br><div class="moz-cite-prefix"><font color="#330033"><small>On 30/01/2016 4:05 PM, Farell Folly wrote:<br></small></font></div><blockquote cite="mid:CADzHdxfmasd945f1SrMGGEJkPMzSkMyfS0Ln_H0ywdTFwD6D=Q@mail.gmail.com" type="cite"><div dir="ltr"><font color="#330033"><small>Hello,<br><br>>>> Deploying RDAP with the same policies associated with WHOIS gives us the same problems associated with WHOIS.</small></font></div></blockquote><div><font color="#330033"><small> <span class="Apple-converted-space"> </span>Good point and we should discuss about the right strategy to approach this..<br></small></font></div><blockquote cite="mid:CADzHdxfmasd945f1SrMGGEJkPMzSkMyfS0Ln_H0ywdTFwD6D=Q@mail.gmail.com" type="cite"><div class="gmail_extra"><font color="#330033"><small><br clear="all"></small></font><div><div class="gmail_signature"><div dir="ltr"><div><small><font color="#330033">Meilleures salutations,</font><br></small><br></div>--ff--<br></div></div></div><br><div class="gmail_quote"><small>2016-01-30 20:32 GMT+01:00 Hollenbeck, Scott<span class="Apple-converted-space"> </span><span dir="ltr"><<a moz-do-not-send="true" href="mailto:shollenbeck@verisign.com" target="_blank"></a><a class="moz-txt-link-abbreviated" href="mailto:shollenbeck@verisign.com">shollenbeck@verisign.com</a>></span>:<br></small><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex;"><small>So I saw a tweet from Gavin Brown (@GavinBrown) of CentralNic that describes how one particular search engine has indexed the RDAP server of a gTLD registry operator:<br><br><a moz-do-not-send="true" href="https://twitter.com/GavinBrown/status/692718904058191872" rel="noreferrer" target="_blank">https://twitter.com/GavinBrown/status/692718904058191872</a><br><br>This is all the more reason to work on a client authentication specification that includes support for varying responses based on client identity and authorization. I've been working on such a specification and welcome feedback on the approach:<br><br><a moz-do-not-send="true" href="https://datatracker.ietf.org/doc/draft-hollenbeck-weirds-rdap-openid/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/doc/draft-hollenbeck-weirds-rdap-openid/</a><br><br>I know this group is just getting started and is probably not ready to start discussing deep technical topics. This is one of the kinds of things that we're going to need to talk about. It's also an important data point in the discussion about deploying RDAP services before policies are in place that allow operators to take advantage of the new features provided by RDAP. Deploying RDAP with the same policies associated with WHOIS gives us the same problems associated with WHOIS.<br><br>Scott<br>_______________________________________________<br>gnso-rds-pdp-wg mailing list<br><a moz-do-not-send="true" href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br><a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a><br></small></blockquote></div><br></div><br><fieldset class="mimeAttachmentHeader"></fieldset></blockquote><br>_______________________________________________<br>gnso-rds-pdp-wg mailing list<br><a href="mailto:gnso-rds-pdp-wg@icann.org">gnso-rds-pdp-wg@icann.org</a><br><a href="https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg">https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg</a></div></blockquote></div><br></div></body></html>