Re: impact of new gTLDs

Looking at the publicsuffix.org page, it's going to be pretty tricky
maintaing it for the expected ~800 gTLDs to come.  Also because each of
them may have very different rules for how they give them out, what they
will use them for (e.g. I think there is at least one bank that wants to
give all customers <account number>.<gTLD>).  Potentially there will be
millions and just deciding on a proper database to keep them in for fast
searches and more (on e.g. publicsuffix.org) will be fun.

Interesting times ahead ;)

I think (hope?) ICANN should seriously have (has?) considered these
scenarios before just going for the monies .. possibly requiring a service
+ specific API from each gTLD holder to be registered on e.g.
"regapi.<gTLD>"




On Thu, Jun 12, 2014 at 3:37 PM, Robin Berjon <robin@w3.org> wrote:

> On 12/06/2014 12:02 , Anne van Kesteren wrote:
>
>> On Thu, Jun 12, 2014 at 11:14 AM, Akihiro Koike <koike@jprs.co.jp> wrote:
>>
>>> We are a registry operator of new generic top-level domain(gTLD).
>>> Therefore we are interested in the impact of new gTLDs.
>>> I'd like your thoughts on what kind of impact the appearance of new
>>> gTLDs has on software implementation.
>>>
>>
>> The continued growth of https://publicsuffix.org/ would be annoying.
>>
>
> Can you think of an alternative? Because it's looking like we're going to
> keep getting a lot of new TLDs.
>
> --
> Robin Berjon - http://berjon.com/ - @robinberjon
>
>