- gtld-tech - lists.icann.org

FW: ROW#6: May 12th, 2017 - Madrid
by Hollenbeck, Scott April 24, 2017

April 24, 2017

I’m cross-posting this note at the request of the workshop program committee. Please note that it follows the GDD Summit, so if you happen to be in Madrid it might be worth extending your trip by another day. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Friday, April 21, 2017 2:25 PM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] ROW#6: May 12th, 2017 - Madrid Dear Colleagues, The next Registration Operations Workshop will take place in Madrid, May 12th. Sign up to meet and discuss with your compeers. See Marc Blanchet’s recent blog post for details about the session: "6th Registration Operations Workshop (ROW), Madrid, Friday May 12th 2017<http://www.circleid.com/posts/20170420_6th_registration_operations_workshop…>" We look forward to seeing you in Madrid! The Program Committee http://regiops.net

1 0

FW: Register for ROW#6 - Madrid
by Hollenbeck, Scott March 15, 2017

March 15, 2017

This may be of interest to list members who plan to attend the GDD Summit in May. Scott From: regops [mailto:regops-bounces@nlnetlabs.nl] On Behalf Of Nicoleta Munteanu Sent: Wednesday, March 15, 2017 11:15 AM To: regops(a)nlnetlabs.nl Subject: [EXTERNAL] [Regops] Register for ROW#6 - Madrid With a focus on the Registration Data Access Protocol, the 6th session of the Registration Operations Workshop (ROW) is scheduled to take place in Madrid, on Friday 12 May 2017. To further bring existing communities of interest together, the workshop will be co-located with the events listed below and will take place at the same venue as all the other events: Hotel NH Collection Madrid Eurobuilding, Calle de Padre Damián, 23, 28036 Madrid, Spain. - 9-11 May: ICANN GDD Industry Summit<https://www.icann.org/gddsummit> - 12 May: The 6th Registration Operations Workshop<http://regiops.net> - 13 May: ICANN DNS Symposium<https://www.icann.org/ids> - 14-15 May: OARC 26 (DNS-OARC Workshop)<https://indico.dns-oarc.net/event/26/overview> ROW#6 registration is now open at: http://regiops.net/?page_id=184. The program is being finalized. However, we still have some open presentation slots available; proposals can be submitted to the Program Committee at row(a)viagenie.ca<mailto:row@viagenie.ca> or during the registration process. For other event details and 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

ICANN monitoring system API
by Gustavo Lozano Feb. 17, 2017

Feb. 17, 2017

Hello Colleagues, Specification 10 of the base registry agreement (https://newgtlds.icann.org/sites/default/files/agreements/agreement-approve…) describes the Service Level Requirements and emergency thresholds that a Registry Operator has to comply related to the Registry Services. ICANN has been monitoring compliance of new gTLDs following the algorithms defined in this specification. ICANN provides access to Registry Operators to the incident information of its TLDs through an API currently in beta, and we are planning on releasing the production version in the future. The Registry Operators using the beta API had provided valuable feedback, and the specification to be implemented in the production version has been modified accordingly. Attached you will find the latest draft of this specification. I appreciate your feedback no later than February 24, 2017. Regards, Gustavo

2 1

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