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

[Dennis Chang]

Thanks Roger for your support.
At our last meeting, we heard from Marc, Joyce and Ray of their support also.
Steve replied with his support today and Marc had already provided his support via email.

So I have the following list of IRT members’ support so far.

Marc Anderson
Theo Geurts
Steve Metalitz
Joyce Lin
Ray Fassett
Roger Carney

And we’ve received NO objections.

Could we hear from other IRT members not on the list so far?

Thanks
Dennis Chang

From: <gnso-impl-thickwhois-rt-bounces at icann.org> on behalf of Roger D Carney <rcarney at godaddy.com>
Date: Monday, October 10, 2016 at 1:35 PM
To: "gnso-impl-thickwhois-rt at icann.org" <gnso-impl-thickwhois-rt at icann.org>
Subject: Re: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration

Good Afternoon,

Thanks Dennis, as stated on the call we do support this updated version of the CL&D policy.


Thanks
Roger


From: gnso-impl-thickwhois-rt-bounces at icann.org [mailto:gnso-impl-thickwhois-rt-bounces at icann.org] On Behalf Of Dennis Chang
Sent: Sunday, October 09, 2016 9:12 PM
To: gnso-impl-thickwhois-rt at icann.org
Subject: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration

Dear IRT Members,

Thanks for your review and support of this policy revision process.

To the initial plan that we shared with you on 21 September 2015, we are proposing one change.

Public comment.  Upon further consideration, we’ve decided to put the revision of the CL&D policy document out for a public comment.  Although, the change to the policy language is simple and it does not change the intended implementation, we felt that a public comment would best support the transparency of the process.

It’s our goal to secure the support of the IRT for this plan by our next meeting on 11 October 2016 and proceed with the public comment.  Please review the attached revised policy and provide your comment prior to the meeting if possible.

Thanks
Dennis Chang

From: <gnso-impl-thickwhois-rt-bounces at icann.org<mailto:gnso-impl-thickwhois-rt-bounces at icann.org>> on behalf of Dennis Chang <dennis.chang at icann.org<mailto:dennis.chang at icann.org>>
Date: Wednesday, September 21, 2016 at 10:41 AM
To: "gnso-impl-thickwhois-rt at icann.org<mailto:gnso-impl-thickwhois-rt at icann.org>" <gnso-impl-thickwhois-rt at icann.org<mailto: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"


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