Translationtransliterationirt

Download

translationtransliterationirt@icann.org

September 2016

1 participants
2 discussions

FW: [Gnso-impl-thickwhois-rt] Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration
by Brian Aitchison Sept. 21, 2016

Sept. 21, 2016

Hello all, As you may be aware, there have been some notable developments in the roll-out of RDAP; namely, that the provision to include RDAP as a requirement for registries and registrars to implement the ³Thick WHOIS: Consistent Labelling and Display² policy is to be removed (see forwarded email below to the Thick WHOIS IRT). Given T/T¹s dependence on RDAP to accept non-ASCII characters, this development obviously will affect the T/T implementation. Let¹s wait until we have the final verdict on October 4 before having our next call. Staff will discuss RDAP¹s future internally once we have the final details, and then I¹ll send out another Doodle invite to discuss with all of you. But for now, our call for the week of October 5 will be postponed, likely to the next week. Thanks very much everyone, Brian Brian Aitchison, PhD Lead Researcher Operations & Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Direct Line: +1 310 301 8688 Mobile: +1 424 353 9041 Email: brian.aitchison(a)icann.org Skype: brian.aitchison.icann linkedin.com/in/baitchison <http://linkedin.com/in/baitchison> twitter.com/BrianAitch <http://twitter.com/BrianAitch> From: <gnso-impl-thickwhois-rt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Wednesday, September 21, 2016 at 10:41 AM To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)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-20 16-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 "One World, One Internet"

1 0

Doodle poll: T/T Call #4
by Brian Aitchison Sept. 20, 2016

Sept. 20, 2016

Hello all, Time to put our T/T caps back on. Please participate in the doodle poll to indicate your preferred time for our next call: http://doodle.com/poll/c2n6nfiwfpvip8vq I'll send out an invite once the poll concludes. In addition to discussing any recent developments, we¹ll take a look at the next version of our policy language, which we¹re in the process of drafting now. I¹ll send a more specific agenda ahead of the meeting. All best, Brian Brian Aitchison, PhD Lead Researcher Operations & Policy Research Internet Corporation for Assigned Names and Numbers (ICANN) 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Direct Line: +1 310 301 8688 Mobile: +1 424 353 9041 Email: brian.aitchison(a)icann.org Skype: brian.aitchison.icann linkedin.com/in/baitchison <http://linkedin.com/in/baitchison> twitter.com/BrianAitch <http://twitter.com/BrianAitch>

1 0