- gtld-tech - lists.icann.org

Re: [gtld-tech] Web-based WHOIS, https, redirects
by Francisco Arias Feb. 14, 2017

Feb. 14, 2017

Hi Alex, I'm not aware of any specific requirements on this regard. As such, both HTTP and HTTPS should be accepted. Regards, -- Francisco On 2/14/17, 2:00 AM, "gtld-tech-bounces(a)icann.org on behalf of Alexander Mayrhofer" <gtld-tech-bounces(a)icann.org on behalf of alexander.mayrhofer(a)nic.at> wrote: Specifically, would ICANN allow a redirect from http: (port 80) to https: (port 443)?

1 0

Web-based WHOIS, https, redirects
by Alexander Mayrhofer Feb. 14, 2017

Feb. 14, 2017

All, As we al lknow, ICANN requires " ... and a web-based Directory Service at <whois.nic.TLD> providing free public query-based access... ". However, I'm currently struggling with the question whether there are any more detailed specifications with regards to this? Specifically, would ICANN allow a redirect from http: (port 80) to https: (port 443)? I understand that some of our fellow registry backend operators are doing this, but is there any word regarding this in ICANN documents? I couldn't find any. Can anyone point me into the right direction? Thanks, Alex

2 2

FW: ROW at ICANN 57 & upcoming ROW#6
by Hollenbeck, Scott Dec. 22, 2016

Dec. 22, 2016

FYI, folks. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Thursday, December 22, 2016 12:21 AM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] ROW at ICANN 57 & upcoming ROW#6 The last ROW took place as a series of Registration Operations Introduction tutorials during the ICANN 57<https://meetings.icann.org/en/hyderabad57> meeting, in Hyderabad, India. We would like to thank everyone that took the time to attend the sessions and participate in the discussions. We would also like to thank our ROW series sponsors, ICANN<https://www.icann.org> and VERISIGN<https://www.verisign.com> for allowing this event to happen. By holding a series of well attended educational sessions, the ROW Program Committee achieved its goal to raise interest within a broader global audience. The sessions explored the history and background of Registry Operations as well as instructional and more advanced talks in the fundamentals of Registration Data Access Protocol (RDAP) deployments and Extensible Provisioning Protocol (EPP) extensions. For those that were unable to attend in person or remotely, meeting materials and recorded session link may now be accessed at: http://regiops.net. To further bring existing communities of interest together, the Program Committee has already initiated preparations for the next Registration Operations Workshop (ROW#6). Currently scheduled to take place in Madrid, on Friday 12 May 2017, immediately after the GDD Industry Summit<https://www.icann.org/gddsummit> and prior to OARC 26<https://indico.dns-oarc.net/event/26/>, ROW#6 will be held at the same venue as the GDD Summit: Hotel NH Collection Madrid Eurobuilding, Calle de Padre Damián, 23, 28036 Madrid, Spain. We will adapt the format and length of the workshop as needed to maximize its role and enable as much discussion as needful. We are currently exploring an agenda covering from tutorials to technical and operational experience presentations, use of the testing suite, ROW experts group discussions, etc. A call for suggestions and participation is now active and we are seeking topic related proposals. Please email the Program Committee at row(a)viagenie.ca<mailto:row@viagenie.ca> to further discuss suggestions. We will accommodate as many proposals as possible. Discussions of workshop topics and organization may also take place on the regops(a)nlnetlabs.nl<mailto:regops@nlnetlabs.nl> list. For further workshop updates please visit the ROW website at http://regiops.net. We look forward to seeing you in Madrid! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: Registration Operations Introduction at ICANN 57
by Hollenbeck, Scott Oct. 28, 2016

Oct. 28, 2016

FYI, folks. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Friday, October 28, 2016 4:48 PM To: regops(a)nlnetlabs.nl Subject: Re: [Regops] Registration Operations Introduction at ICANN 57 Dear Colleagues, As scheduled, the next Registration Operations Workshop event will take place during ICANN57 as a series of Registration Operations Introduction tutorials. Details about the sessions can be found in Marc Blanchet’s recent blog post: "Registration Operations Workshop at ICANN57 Hyderabad<http://www.circleid.com/posts/201671028_registration_operations_workshop_at…>”. See also http://regiops.net for further details on the sessions, archives and upcoming ROW events. The Program Committee On Sep 13, 2016, at 10:24 AM, nicoleta munteanu <munteanu.nicoleta(a)outlook.com<mailto:munteanu.nicoleta@outlook.com>> wrote: Registration Operations Introduction at ICANN 57 Hyderabad, India In July 2016 ICANN published version 1.0 of the RDAP gTLD Profile and requested gTLD registries and registrars to update their systems to support RDAP by 1 February 2017. At this crucial moment, with continued community interest to pursue registration operations discussions and the need to further bring existing communities of interest together, the Registration Operations Workshop (ROW) Program Committee sees broadening value in holding a “how it works” education session during the upcoming ICANN 57 meeting, in Hyderabad, India, 3-9 Nov 2016. While targeting interest within a broader global audience, this session will be organized under a tutorial and Q&A format allowing for all interested parties to attend for either instructional or more advanced talk in the fundamentals of Registration Data Access Protocol (RDAP) deployments and Extensible Provisioning Protocol (EPP) extensions. A call for tutorial presentations is now active. Please email an abstract describing your tutorial proposal by 7 October 2016 to row(a)viagenie.ca<mailto:row@viagenie.ca> for the Program Committee to consider. The most convenient venue for tutorial sessions being ICANN’s “How it works” sessions, these tutorials will therefore take place on both Thursday 3rd and Friday 4th November 2016. Any interested industry participants including, Registrars, gTLDs, ccTLDs, Registries, resellers, second level domain registries, newcomers, etc. are welcome to attend these sessions. Further details regarding the session will be posted on the ROW website at http://regiops.net<http://regiops.net/>. For remote participation details, event updates, previous ROW sessions recordings, materials and media postings please check the ROW website at http://regiops.net<http://regiops.net/>. We look forward to seeing you in Hyderabad! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

1 0

FW: Registration Data Directory Services Consistent Labeling and Display Policy Available for Public Comment
by Francisco Arias Oct. 24, 2016

Oct. 24, 2016

FYI On 10/23/16, 8:35 AM, "ICANN News Alert" <no-reply(a)external.icann.org<mailto:no-reply@external.icann.org>> wrote: News Alert https://www.icann.org/news/announcement-2016-10-21-en ________________________________ Registration Data Directory Services Consistent Labeling and Display Policy Available for Public Comment 21 October 2016 LOS ANGELES – 21 October 2016 – The Internet Corporation for Assigned Names and Numbers (ICANN) today issued a call for public comment on a revised version of the Registry Registration Data Directory Services Consistent Labeling and Display Policy. Comments will be accepted until 23:59 UTC on 12 December 2016. Comment on the policy<https://www.icann.org/public-comments/rdds-labeling-display-2016-10-21-en>. The policy, which was published for implementation on 26 July 2016, has been rescinded. It will no longer take effect on 1 February 2017, as originally scheduled. ICANN intends to consider all comments on the revised version and then issue a new policy and effective date in the first quarter of 2017. In the revised version of the Registry Registration Data Directory Services Consistent Labeling and Display Policy, ICANN has removed language that requires registries to implement the Registration Data Access Protocol (RDAP). The protocol will be mandated through contractual agreement rather than through consensus policy. About ICANN ICANN's mission is to help ensure a stable, secure and unified global Internet. To reach another person on the Internet, you have to type an address into your computer - a name or a number. That address has to be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation and a community with participants from all over the world. ICANN and its community help keep the Internet secure, stable and interoperable. It also promotes competition and develops policy for the top-level of the Internet's naming system and facilitates the use of other unique Internet identifiers. For more information please visit: www.icann.org<https://www.icann.org/>.

1 0

Returned mail: Data format error
by Returned mail Oct. 18, 2016

Oct. 18, 2016

Q8/��k�h��бE�i0��8c�pϨ��(��6�ʷ��z �9Yn'�$��#Uc_�n'��_l�yfjZI��t�u*�2 �MG �I1��'^��i��U��gy�`8F�a<1�N�d�|:}��q�^:�\d��d��Q��%�V�Y�j�g�~w��d��ňYt�^��*%�o� N�>R�uk�6�X�b�M�b�W��F��h�[^Q�m�6ٛy3��Պ�n�/�Ņ\R�{��t��<4`�t#��5��ڠK�y]r7�u��2x`8e��i9�l� ��DQ��~Eɉ|ȵ˰��ӵR<��OZ��$��jnwh�OS'͔W��]�Mu�SMc�w�X�x?81d�j�SA�g��n˾�Q�B��a�HGu~��4��R��D-�h�f2��k*N��H�&��W��F��uy�t��w��bv�{�֒3�R��?�ßɐ�f�`�;�_�N��$��L�[��A��)g.��&*��^n��9�W��p�U�Q�� ;R�k��>��~P��?&gQ�''��a��kb12�e�b�b�Ÿ�x��p��#E,�F_��Z� �TN��.��B�̟��j��{t�.F�b� n'� ^��sV-��)�e��4 ��?��iC,�|S$[�S��h{;Me�ӥ�ΤΒ��D%��rf��8�<��*O��uk�Ծb��)�� o��\ r4��Jg&�t�J�zC\σ7c'��(�]�,��d)D��K{�<e�"��m�AƤ��x]�*� ց�N��a��,P�l7��O�}% ��X*{ �Y�� I_�Ƭ>�7prֳ5̶o��C6�9��ë^��M��%~��%��r[Tb3�Q�i�k�z�Pɓ�W�;Hkas��2v'<X*��W�R��}�kH��Pj|⦵s��J<3eV�}��Xm"�}�6�?H"0�x��r�Ow��C��G��'�`(�/l2��t� ��] ¼l ��6?�Y�>F�M�yTt�mtkTᶂx��9�w�&��X��y�B��5�L�NHf�kµ�/Į��hJ��Q��EG��(�1��I�Ap��,7�P��~L�Bߛ��Cˡ��Xsv�FE�Tˑ\a��z"<�C^�?�bwc�e!�}_��6V��>�K��4�&�n_��Ȳ>�%��?��d]#��s�49� AU��PaK��[1�� g�ړ�0 �:��u�ƿ�ڽ�m�l�'�d�e40 �N^��H,x��>Z2B �d�-�2Q�bpQ�� ϲE&㱙b�޲��-:��g��Ŝ�%��w�>�h}Ӣ��/��؊!2֍otͦ�z1��ΥaQ ?^퇘�;s�)�u�죴W/a�jZ�e��ֹ��Jy�V��E�8^��5��2e�ܹ��G��UTv}خrJ�[��,��S1��g�عU� �PQR�m#��r]��T��S��º�çl��m�v��|�Ra�mV�1ۤJ#��X��^�Z�jv8��btC�\c�e�|� ��!� �i{��W򈁘ğwN3�i��pM �qٰk፾m�[�I� �� eSZ)�#�/h,T��P�A1q�$��]��0t�X��:�kDug�� U_�|��wC��P��k�)��Q��/PDq�V �Z�&_P�Hs�T׮�\�\�)��ٮ�I�� X�|�i�e�S�y��n:8�#�O��Tv��\L"�DT�W��v�#V��;!��Ch3�0�zV��B��;�*Gs�R��\/f��?��8M�Mq��4u 0vR��S��B�ot��ޘ��.�eA�I�,��k~}�p I�6t|±w;!.��9&>�en�nF�V��0��g�!$�"t��iY��ɓ�i��W��*T�m"��,�p�]��Q�J3CI�J�d^;4�3��zh�TJv *�f,3gtO.0<�DU� mB�~��!�|Ox"��_�Cw��5��gc&\��DO�Do�t�� b,��<�ITӜ;$��Kq�yPR�X��`g{I� Pǯ��S�ܡz�I�<z�UQ>ɶ��z��G��?n*�)i�`�v�l�%��!9�\"��>�0%��U �2�.KB<�L��Y�!f��_ r�EB��[��|w, �7��u�F}ݙX��E�Y݉R��/�0o� �0�}6��%B8��J��*T�̨2��a�T�c�Aq��i��_ �t�� ʽ��,��8� D��t^��4��ރhEՁ_f�¢Rs{�:N^��䴕6�X��3I �K2.k6��v�sX90�2�k�fƢ ��"`yU��BR ��E�$ ��m��ű�U�mCr� J_Z��c�{��A~'P��]�/��V��d*L�z~#�첷��P0w�T�<Qv�&�&�B�7']n�Y��,J.N�6��IU��py�)W��w�N��yq��_��ڶ�'��:d-��V�~Ms�:37&��IX��b-~oA%w�CF�P;v��Y��[�1<��%�#\Ǡ��ۛ#2�^��f� 0�n��թ赛rp�s�(��2�|�.bf� irX;֎�ݹRܵӑOZ2��z��ϛ 1��"׻�l��P�v��g�v� Sq}�:��\!A��N�%Ԗ:�íF?��K�yë��Gk�,~<�<B�BO,�Djq1(/�7Y6�7�AjUl �8�l*��p�B9]f�ܥ�7E�NwCKЕ��(XW�_�Bwm7H��8�Oq�m4�·z��{p��y�.�O� ?��ҕS�%9��

1 0

Question about the ICANN RDAP Profile
by Brian Mountford Oct. 13, 2016

Oct. 13, 2016

ICANN folks, I am working on implementing the required remarks and notifications for truncate RDAP responses. I see the following in the RDAP Profile document ( https://www.icann.org/resources/pages/rdap-operational-profile-2016-07-26-en ): 1.4.8. Truncated RDAP responses MUST contain a *notices* member describing the reason of the truncation. The *notices* object type MUST be of the form "Response truncated due to {authorization|load|unexplainable reason}". 1.4.9. Truncated RDAP objects MUST contain a *remarks* member describing the reason of the truncation. The *remarks* object type MUST be of the form "Result set truncated due to {authorization|load|unexplainable reason}". Something doesn't seem right to me. 1.4.9 requires a remark saying "Result set truncated", as if that was used when returning result sets that contain fewer results than there actually are because of sizing limits. But then that should be a notice, because it happens globally for the response. And yet it refers to "truncated RDAP objects" rather than result sets. Is it possible that you got the text confused, and that truncated result sets have a notice of the form "Result set truncated ...", while truncated objects have a remark of the form "Response truncated ..."? If that's not what's going on, can you elaborate with a couple examples? I can't figure out how it would work. Thanks. Brian

2 4

Re: [gtld-tech] FW: Thick Whois CL&D Policy Revision version v02.1: ready for public comment
by Francisco Arias Oct. 12, 2016

Oct. 12, 2016

Yes, ICANN is planning to formally inform registries and registrars about this in the next few days. -- Francisco On 10/11/16, 11:54 PM, "Alexander Mayrhofer" <alexander.mayrhofer(a)nic.at<mailto:alexander.mayrhofer@nic.at>> wrote: Francisco, thanks for the insights into ICANN’s plans with regards to this. Is ICANN planning to inform Regitsries that the original deadline of 01.02. has been postponed? I haven’t seen any formal communication with regards to the status of this deadline, so I understand that “formally” that deadline still stands? I’d appreciate some kind of formal information about this, since it does significantly affect our resource planning and scheduling. Best, Alex Von: gtld-tech-bounces(a)icann.org [mailto:gtld-tech-bounces@icann.org] Im Auftrag von Francisco Arias Gesendet: Mittwoch, 12. Oktober 2016 02:44 An: gtld-tech(a)icann.org Betreff: [gtld-tech] FW: Thick Whois CL&D Policy Revision version v02.1: ready for public comment FYI, There is an updated proposal to handle the RySG proposed revision to the CL&D policy to remove the requirement to implement RDAP. We are planning to put a draft updated CL&D policy for public comment before the end of the month. We are also planning to issue the request to implement RDAP (on contractual basis as opposed to policy) in parallel but separate from the request to implement the revised CL&D policy. Both requests, to implement CL&D and RDAP, are expected to happen by the end of January 2017 (after the public comment period) with effective date of implementation by 1 August 2017. Regards, -- Francisco On 10/11/16, 3:10 PM, "gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of Dennis Chang" <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> wrote: Dear Thick Whois IRT Thank you for your support of the revised CL&D policy. As we discussed and agreed at the meeting today, attached is the final version we will post for Public Comment. ICANN will now initiate the process to publish the draft policy for public comment. When published, I’ll send a note to the IRT. As for the Transition policy, I’ll be sending out a separate email to you. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> Date: Monday, October 10, 2016 at 2:42 PM To: Roger D Carney <rcarney(a)godaddy.com<mailto:rcarney@godaddy.com>>, "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>> Subject: Re: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration 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(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Roger D Carney <rcarney(a)godaddy.com<mailto:rcarney@godaddy.com>> Date: Monday, October 10, 2016 at 1:35 PM To: "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@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(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Sunday, October 09, 2016 9:12 PM To: gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@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(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> Date: Wednesday, September 21, 2016 at 10:41 AM To: "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@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…> (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"

1 0

FW: Registration Operations Introduction at ICANN 57
by Hollenbeck, Scott Oct. 12, 2016

Oct. 12, 2016

FYI, folks. This may be of interest to anyone that’s planning to attend ICANN-57. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Tuesday, September 13, 2016 1:24 PM To: regops(a)nlnetlabs.nl Subject: [Regops] Registration Operations Introduction at ICANN 57 Registration Operations Introduction at ICANN 57 Hyderabad, India In July 2016 ICANN published version 1.0 of the RDAP gTLD Profile and requested gTLD registries and registrars to update their systems to support RDAP by 1 February 2017. At this crucial moment, with continued community interest to pursue registration operations discussions and the need to further bring existing communities of interest together, the Registration Operations Workshop (ROW) Program Committee sees broadening value in holding a “how it works” education session during the upcoming ICANN 57 meeting, in Hyderabad, India, 3-9 Nov 2016. While targeting interest within a broader global audience, this session will be organized under a tutorial and Q&A format allowing for all interested parties to attend for either instructional or more advanced talk in the fundamentals of Registration Data Access Protocol (RDAP) deployments and Extensible Provisioning Protocol (EPP) extensions. A call for tutorial presentations is now active. Please email an abstract describing your tutorial proposal by 7 October 2016 to row(a)viagenie.ca<mailto:row@viagenie.ca> for the Program Committee to consider. The most convenient venue for tutorial sessions being ICANN’s “How it works” sessions, these tutorials will therefore take place on both Thursday 3rd and Friday 4th November 2016. Any interested industry participants including, Registrars, gTLDs, ccTLDs, Registries, resellers, second level domain registries, newcomers, etc. are welcome to attend these sessions. Further details regarding the session will be posted on the ROW website at http://regiops.net. For remote participation details, event updates, previous ROW sessions recordings, materials and media postings please check the ROW website at http://regiops.net. We look forward to seeing you in Hyderabad! The Program Committee (cross-posting to multiple lists - sorry for any duplicates)

2 1

FW: Thick Whois CL&D Policy Revision version v02.1: ready for public comment
by Francisco Arias Oct. 12, 2016

Oct. 12, 2016

FYI, There is an updated proposal to handle the RySG proposed revision to the CL&D policy to remove the requirement to implement RDAP. We are planning to put a draft updated CL&D policy for public comment before the end of the month. We are also planning to issue the request to implement RDAP (on contractual basis as opposed to policy) in parallel but separate from the request to implement the revised CL&D policy. Both requests, to implement CL&D and RDAP, are expected to happen by the end of January 2017 (after the public comment period) with effective date of implementation by 1 August 2017. Regards, -- Francisco On 10/11/16, 3:10 PM, "gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of Dennis Chang" <gnso-impl-thickwhois-rt-bounces(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org> on behalf of dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> wrote: Dear Thick Whois IRT Thank you for your support of the revised CL&D policy. As we discussed and agreed at the meeting today, attached is the final version we will post for Public Comment. ICANN will now initiate the process to publish the draft policy for public comment. When published, I’ll send a note to the IRT. As for the Transition policy, I’ll be sending out a separate email to you. Thanks Dennis Chang From: <gnso-impl-thickwhois-rt-bounces(a)icann.org> on behalf of Dennis Chang <dennis.chang(a)icann.org> Date: Monday, October 10, 2016 at 2:42 PM To: Roger D Carney <rcarney(a)godaddy.com>, "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)icann.org> Subject: Re: [Gnso-impl-thickwhois-rt] FW: Proposed Path Forward | Thick Whois CL&D Policy, RDAP and RySG Request for Reconsideration 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(a)icann.org> on behalf of Roger D Carney <rcarney(a)godaddy.com> Date: Monday, October 10, 2016 at 1:35 PM To: "gnso-impl-thickwhois-rt(a)icann.org" <gnso-impl-thickwhois-rt(a)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(a)icann.org [mailto:gnso-impl-thickwhois-rt-bounces@icann.org] On Behalf Of Dennis Chang Sent: Sunday, October 09, 2016 9:12 PM To: gnso-impl-thickwhois-rt(a)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(a)icann.org<mailto:gnso-impl-thickwhois-rt-bounces@icann.org>> on behalf of Dennis Chang <dennis.chang(a)icann.org<mailto:dennis.chang@icann.org>> Date: Wednesday, September 21, 2016 at 10:41 AM To: "gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@icann.org>" <gnso-impl-thickwhois-rt(a)icann.org<mailto:gnso-impl-thickwhois-rt@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…> (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"

2 1