[Gnso-impl-thickwhois-rt] Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration

[theo geurts]

Dennis,

This looks like the path forward, and I am supportive of the proposed 
path forward as a Registrar.

Perhaps I am jumping the gun here, but how would this dialogue with the 
community take place?
Furthermore, how do we address irregularities within RDAP? Or get 
clarification on a few issues that I assume have not been discussed yet?

Thanks,

Theo


On 21-9-2016 19:58, Anderson, Marc wrote:
>
> Dennis,
>
> Thank you for the excellent explanation and details.  On behalf of 
> Verisign and as a member of the RySG I would like to express my 
> support for the revised CL&D policy and the path forward you have laid 
> out.
>
> Thank you,
>
> Marc Anderson
>
> *From:*gnso-impl-thickwhois-rt-bounces at icann.org 
> [mailto:gnso-impl-thickwhois-rt-bounces at icann.org] *On Behalf Of 
> *Dennis Chang
> *Sent:* Wednesday, September 21, 2016 1:42 PM
> *To:* gnso-impl-thickwhois-rt at icann.org
> *Subject:* [Gnso-impl-thickwhois-rt] Proposed Path Forward | Thick 
> Whois CL&D Policy, RDAP and RySG Request for Reconsideration
>
> Dear IRT members,
>
> As you know, on 7 February 2014, the ICANN Board adopted GNSO 
> consensus policy recommendations regarding the provision of “Thick” 
> Whois by all gTLD registries.
>
> In consultation with the consensus policy Implementation Review Team 
> (IRT), the implementation team identified two expected outcomes in the 
> policy development process (PDP) recommendations:
>
>   * The consistent labeling and display of WHOIS output for all gTLDs
>   * The transition from Thin to Thick WHOIS for .COM, .NET and .JOBS
>
> The first outcome was published as a consensus policy, the Registry 
> Registration Data Directory Services Consistent Labeling and Display 
> Policy 
> <https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en> 
> (CL&D Policy), on 26 July 2016.
>
> In August 2016, the Registry Stakeholder Group (RySG) submitted a 
> Request for Reconsideration 
> <https://www.icann.org/resources/pages/reconsideration-16-10-rysg-request-2016-08-11-en> 
> (RfR) regarding the CL&D Policy. The RfR objects to the inclusion of 
> RDAP as part of the Consensus Policy as RDAP was not contemplated or 
> referenced in the policy recommendations.
>
> To resolve this matter, ICANN proposes the following path forward for 
> the IRT:
>
> 1. ICANN to issue a revised CL&D Policy to all registry operators, 
> removing provision 12. For your reference, provision 12 states: “The 
> implementation of an RDAP service in accordance with the "RDAP 
> Operational Profile for gTLD Registries and Registrars 
> <https://www.icann.org/rdap-gtld-profile>" is required for all gTLD 
> registries in order to achieve consistent labeling and display.” 
> Additionally, I have attached the proposed revised CL&D Policy.
>
> 2. Issue a revised notification to registry operators regarding 
> implementation of the CL&D Policy, clearly indicating what has changed 
> in the revised CL&D Policy.
>
> 3. Set the revised CL&D Policy effective date to allow for full 
> 6-month implementation from the date of the revised notice.
>
> 4. Update the published CL&D Policy on the ICANN website, noting a 
> change has been made. Note: The revised CL&D Policy would _not_ be 
> subject to another Public Comment process.
>
> 5. Rescind the notification sent to registrars to implement RDAP.
>
> ICANN intends to issue notices for registries and registrars to 
> implement RDAP after further dialogue with the community.
>
> Please let us know if you have comments or concerns by responding to 
> this list. Unless we hear otherwise, we intend to move forward with 
> the plan outlined above on 4 October 2016.
>
> —
>
> Kind Regards,
>
> Dennis S. Chang
>
> GDD Services & Engagement Program Director
>
> +1 213 293 7889
>
> Skype: dennisSchang
>
> www.icann.org <http://www.icann.org> "One World, One Internet"
>
>
>
> _______________________________________________
> Gnso-impl-thickwhois-rt mailing list
> Gnso-impl-thickwhois-rt at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-impl-thickwhois-rt/attachments/20160922/b602fb59/attachment-0001.html>