[Gnso-newgtld-wg] Notes on Registry Services
jeff.neuman at comlaude.com
Fri Sep 6 13:42:10 UTC 2019
Rubens is correct. And although the language states that the registries are free to deploy, it does not mean that they are free to deploy and nothing is disclosed. Furthermore the 15 day period is not a back and forth negotiation with ICANN. It is solely for ICANN to make sure the request is complete and for them to quickly analyze whether there are an security, stability, etc. concerns.
Senior Vice President
Com Laude | Valideus
E: jeff.neuman at comlaude.com<mailto:jeff.neuman at comlaude.com>
From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces at icann.org> On Behalf Of Rubens Kuhl
Sent: Thursday, September 5, 2019 6:44 PM
To: gnso-newgtld-wg at icann.org
Subject: Re: [Gnso-newgtld-wg] Notes on Registry Services
Em 5 de set de 2019, à(s) 18:37:000, Aikman-Scalese, Anne <AAikman at lrrc.com<mailto:AAikman at lrrc.com>> escreveu:
Thanks Jeff. I have followed up with the IPC pursuant to the "Action Item" from the call.
My understanding is that RSEP jurisdiction includes proposing new services and involves a 15 day "preliminary determination" period. If ICANN org determines that the registry service does not involve significant Security and Stability implications or raise "significant competition issues" , the proposed new service can remain "confidential" and the Registry Operator is free to deploy the new service after the 15 day period when ICANN determines no such issues are involved. Hence, if I were a registry, I would rather have that discussion and determination made with ICANN Org than via public comment. A description of the RSEP “preliminary determination” process is pasted below along with a link to the RSEP “workflow”. Please let me know if the text on the ICANN website is somehow incorrect.
The text on the workflow states what is seen by registries that an RSEP is published while ICANN does security, stability and competition review.
It's only unpublished during completeness check, but as soon as it deemed to have all elements for a decision to make, it's published while ICANN makes such determination.
This can be seen in https://www.icann.org/resources/pages/rsep-2014-02-19-en : there are two requests by ZACR for Registry Lock in African TLDs there are listed as "ICANN Review". Everyone can see what those requests are and help ICANN make a determination.
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see www.comlaude.com<https://comlaude.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnso-newgtld-wg