[Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent Procedures Working Group, 15 May 2017 at 15:00 UTC

Greg Shatan gregshatanipc at gmail.com
Tue May 16 01:27:03 UTC 2017


I don't think that's where we are trying to get to.  Rather "rounds vs.
anyone can apply for a TLD at any time" is one of the big questions for
this WG.  (I guess we know your preferred answer now....)

There are a number of good reasons for categories -- certainly enough not
to dismiss it out of hand.  Turning the TLD space into a "high rollers"
version of the SLD space is a troubling idea, to say the least.

There were certainly problems with the community applications (not really a
separate "round") but something done poorly may be worth doing better.  I'm
sure we have plenty of other horror stories from different parts of the New
gTLD Program and from different perspectives.  We should learn from them,
rather than use them as an excuse to move away from them.

Greg


*Greg Shatan *C: 917-816-6428
S: gsshatan
gregshatanipc at gmail.com


On Mon, May 15, 2017 at 1:17 PM, Rob Hall <rob at momentous.com> wrote:

> I honestly can’t see the purpose of categories.
>
>
>
> If you think of the place we are trying to get to, where anyone can apply
> for a TLD at any time, categories seems to be a waste of time.
>
>
>
> The arguments for them seem to focus on these artificial Rounds we are
> having, and somehow giving someone a leg up on someone else.   I can just
> imagine the loud screaming when someone games the system.   Have we not
> learned anything from the sTLD and community rounds we just went through ?
>
>
>
> Rob.
>
>
>
> *From: *<gnso-newgtld-wg-bounces at icann.org> on behalf of Martin Sutton <
> martin at brandregistrygroup.org>
> *Date: *Monday, May 15, 2017 at 9:25 AM
> *To: *Jeff Neuman <jeff.neuman at comlaude.com>
> *Cc: *"gnso-newgtld-wg at icann.org" <gnso-newgtld-wg at icann.org>
>
> *Subject: *Re: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent
> Procedures Working Group, 15 May 2017 at 15:00 UTC
>
>
>
> That would be helpful.
>
>
>
> I have difficulties reconciling the notion of ignoring categories, as it
> caused no end of problems after applications were submitted and created
> unnecessary delays. Where there are well-defined categories and a proven
> demand, categories can be created and processes refined for that particular
> category, especially where the operating model is very different to the
> traditional selling /distribution to third parties.
>
>
>
> Kind regards,
>
>
>
> Martin
>
>
>
> *Martin Sutton*
>
> Executive Director
>
> Brand Registry Group
>
> martin at brandregistrygroup.org
>
>
>
> On 15 May 2017, at 15:17, Jeff Neuman <jeff.neuman at comlaude.com> wrote:
>
>
>
> Thanks Kurt.  Can you recirculate that article you wrote 6 months ago?  It
> may help our discussions later today.
>
>
>
> *Jeffrey J. Neuman*
>
> *Senior Vice President *|*Valideus USA* | *Com Laude USA*
>
> 1751 Pinnacle Drive, Suite 600
>
> Mclean, VA 22102, United States
>
> E: jeff.neuman at valideus.com or jeff.neuman at comlaude.com
>
> T: +1.703.635.7514 <(703)%20635-7514>
>
> M: +1.202.549.5079 <(202)%20549-5079>
>
> @Jintlaw
>
>
>
>
>
> *From:* gnso-newgtld-wg-bounces at icann.org [mailto:gnso-
> newgtld-wg-bounces at icann.org <gnso-newgtld-wg-bounces at icann.org>] *On
> Behalf Of *Kurt Pritz
> *Sent:* Monday, May 15, 2017 6:35 AM
> *To:* Steve Chan <steve.chan at icann.org>; gnso-newgtld-wg at icann.org
> *Subject:* Re: [Gnso-newgtld-wg] Proposed Agenda: New gTLD Subsequent
> Procedures Working Group, 15 May 2017 at 15:00 UTC
>
>
>
> Hi Everyone:
>
>
>
> In reading the agenda for today’s meeting, I read the spreadsheet
> describing the different TLD types. (See, https://docs.google.com/
> spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJff
> zJAAhEvNlA/edit#gid=1186181551).
>
>
>
> It looks remarkably similar to a chart presented to the ICANN Board in
> 2010 or 2011 as the main argument for *not *adding to the categories of
> TLDs in the last round because they would be problematic (read,
> “impossible”) to implement.
>
>
>
> Even in this spreadsheet, I can argue whether most of the tick marks in
> the cells apply in all cases. This means that each of the many tick marks
> presents a significant barrier to: (1) getting through the policy
> discussion in a timely manner, and (2) a clean implementation.
>
>
>
> Categories of TLDs have always been problematic.
>
>
>
> The single most important lesson from the 2003-04 sponsored TLD round was
> to avoid a system where delegation of domain name registries was predicated
> upon satisfying criteria associated with categories.
>
>
>
> In the last round, the Guidebook provided for two category types:
> community and geographic. In my opinion, the implementation of both was
> problematic: look at the variances in CPE results and the difficulty with
> .AFRICA. This wasn’t just a process failure, the task itself was extremely
> difficult. Just how does an evaluation panel adjudge a government approval
> of a TLD application if one ministry says, ‘yes’ and the other ’no’? This
> sort of issue is simple compared to evaluating community applications.
>
>
>
> The introduction of a number of new gTLD categories with a number of
> different accommodations will lead to a complex and difficult application
> and evaluation process (and an expensive, complicated contractual
> compliance environment). It is inevitable that the future will include
> ongoing attempts to create policy for new categories as they are conceived.
>
> For those who want a smoothly running, fair, predictable gTLD program, the
> creation of categories should be avoided.
>
>
>
> Instead, the outcome of our policy discussion could be a process that
> remains flexible and can adapt to new business models as they are
> developed. An exemption process to certain contractual conditions can be
> created to encourage innovation while ensuring all policy goals embodied in
> the RA are met. Fair and flexible agreements can be written without the
> need, time and complexity of the creation of additional categories or
> separate agreements.
>
>
>
> While an exemption process sounds complex, it is not compared to the
> nightmare that the new gTLD process will become: never adequately
> administering to an ever-increasing number of categories.
>
>
>
> I wrote in more depth about this ~ 6 months ago - and would be happy to
> flesh out my thoughts on this again.
>
>
>
> Best regards,
>
>
>
> Kurt
>
>
>
> ________________
>
> Kurt Pritz
>
> kurt at kjpritz.com
>
> +1.310.400.4184 <(310)%20400-4184>
>
> Skype: kjpritz
>
>
>
>
>
>
>
>
>
>
>
> On May 15, 2017, at 3:43 AM, Steve Chan <steve.chan at icann.org> wrote:
>
>
>
> Dear WG Members,
>
>
>
> Apologies for the late delivery. Below, please find the proposed agenda
> for the New gTLD Subsequent Procedures WG meeting scheduled for Monday, 15
> May 2017 at 15:00 UTC for 90 minutes.
>
>
>
> 1)       Welcome/SOIs
>
> 2)       Work Track Updates
>
> 3)       GDD Summit Recap
>
> 4)       Drafting Team Update – Different TLD Types (
> https://docs.google.com/spreadsheets/d/1mA_hTUhLhJSsfcmoQwREtUqxykZ5KfJff
> zJAAhEvNlA/edit#gid=1186181551)
>
> 5)       Community Comment 2 (CC2) Update – Public Comment available here:
>  https://www.icann.org/public-comments/cc2-new-gtld-
> subsequent-procedures-2017-03-22-en
>
> 6)       ICANN59 Planning
>
> 7)       AOB
>
>
>
> If you need a dial-out or want to send an apology, please email
> gnso-secs at icann.org.
>
>
>
> Best,
>
> Steve
>
>
>
>
>
> *Steven Chan*
>
> Sr. Policy Manager
>
>
>
> *ICANN*
>
> 12025 Waterfront Drive, Suite 300
>
> Los Angeles, CA 90094-2536
>
> steve.chan at icann.org
>
> mobile: +1.310.339.4410 <(310)%20339-4410>
>
> office tel: +1.310.301.5800 <(310)%20301-5800>
>
> office fax: +1.310.823.8649 <(310)%20823-8649>
>
>
>
> Find out more about the GNSO by taking our interactive courses and
> visiting the GNSO Newcomer pages
> <http://gnso.icann.org/sites/gnso.icann.org/files/gnso/presentations/policy-efforts.htm#newcomers>
> .
>
>
>
> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO
>
> Follow the GNSO on Facebook: https://www.facebook.com/icanngnso/
>
> http://gnso.icann.org/en/
>
>
>
> _______________________________________________
> Gnso-newgtld-wg mailing list
> Gnso-newgtld-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg
>
>
>
> _______________________________________________
> Gnso-newgtld-wg mailing list
> Gnso-newgtld-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg
>
>
>
> _______________________________________________
> Gnso-newgtld-wg mailing list
> Gnso-newgtld-wg at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20170515/ed8544a2/attachment-0001.html>


More information about the Gnso-newgtld-wg mailing list