[Gnso-newgtld-wg-wt2] Work Track 2: Single Base Agreement

Zylstra, Raymond Raymond.Zylstra at neustar.biz
Sun Oct 2 23:21:45 UTC 2016


Dear all,
I wanted to start the discussion on a question that was raised about the Base Agreement just prior to the end of the 22 September call - the question of 'does a single base agreement make sense for all types of registries?' and the need to have different agreements for different categories of TLDs.

I do not believe that the concept of multiple Registry Agreements is warranted. This is an important topic and I believe the discussion should be broader than simply answering the question as posed. Provided below are some issues I believe we should consider in order to respond to the question.


*                    Predictability - This is something that is often talked about, and also applies in this case. As an end user should I expect the same service levels and requirements of TLDs as I navigate the internet? I would argue yes. It seems that we could end up in a situation where 2012 Registry Operators have very different obligations.

*                    Level Playing Field - A level playing field is important for 2012 Applicants and Registry Operators and those future Applicants; introducing a different Registry Agreement for future Applicants may unfairly disadvantage those who have signed the 2012 Registry Agreement.

*                    Status Quo - We currently have a Registry Agreement, albeit with additional Specifications, under which the various categories of TLDs can, and do, operate. While there are certainly situations where the Registry Agreement is not ideal, it is functional; there are things about it which we may not like, but they are not show stoppers.

*                    Where Does the Problem Lie - As with many of you I have experienced many operational issues dealing with ICANN and their lack of understanding of the diverse business models for different TLDs. I don't believe that having a different Registry Agreement will solve that issue, rather it is a case of working with ICANN to resolve those problems, and I for one have had some success with this.

*                    Lengthy Process - Without question the development of, and agreement to, multiple Registry Agreements has the potential seriously compromise the timelines for the commencement of subsequent new gTLDs. Further, on the call brands were singled out; however, I am confident that many Registry Operators could argue some form of unique requirement which they believe required a unique Registry Agreement.

*                    Administrative Burden - The introduction of multiple Registry Agreements and dealing with these new agreements and the 2012 Registry Agreement will introduce massive overhead for ICANN, Registry Operators, Applicants, and service providers.

I trust that the above makes sense and I look forward to your feedback.

Regards,

Raymond Zylstra<https://au.linkedin.com/in/raymondzylstra>
Neustar Inc. / Director - Policy and Compliance
Level 8, 10 Queens Road, Melbourne, Australia VIC 3004
Office +61 3 9866 3710  Mobile +61 416 177 615 / Raymond.Zylstra at neustar.biz<mailto:Raymond.Zylstra at neustar.biz> / www.neustar.biz<http://www.neustar.biz/>

Follow Neustar: LinkedIn<http://www.linkedin.com/company/5349> / Twitter<http://www.twitter.com/neustar>
Reduce your environmental footprint. Print only if necessary.
________________________________
The information contained in this email message is intended only for the use of the recipient(s) named above and may contain confidential and/or privileged information. If you are not the intended recipient you have received this email message in error and any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately and delete the original message.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg-wt2/attachments/20161002/5f933f05/attachment.html>


More information about the Gnso-newgtld-wg-wt2 mailing list