[dns-operations] getting .CW recognised in the Google ccTLD tables/databases ...

[Rick Wesson]

on an aside, there will be many new labels entering the roots in the
next 24 months. Thos applications would be very grateful for a
synopsis of your experience.

thanks,

-rick


On Sun, Jan 20, 2013 at 5:07 PM, Rick Wesson
<rick at support-intelligence.com> wrote:
> +1
>
> getting on the mozilla list effects lots of applications.
>
> -rick
>
>
> On Sun, Jan 20, 2013 at 4:55 PM, RijilV <rijilv at riji.lv> wrote:
>> My experience is many people use Mozilla's public suffix list for allowing
>> folks to create resources on their app services.  This is because a large
>> number of TLDs don't support creating records directly off of them, and the
>> 3rd parties don't want to accidentally grant ownership to a higher namespace
>> to an individual.  For example, .uk is a TLD, but you shouldn't let people
>> regirester apps under that because someone could cleverly take co.uk and
>> create sub apps within that that they didn't own.
>>
>> http://publicsuffix.org/list/
>>
>> Incidentally, I don't see .cw in that list.  It is open to submissions...
>> http://publicsuffix.org/submit/
>>
>> .r'
>>
>>
>> On 20 January 2013 16:28, Joe Abley <jabley at hopcount.ca> wrote:
>>>
>>>
>>> On 2013-01-21, at 11:55, .CW Registry Curacao <registry at una.net> wrote:
>>>
>>> > I am not sure this is an issue that you can do anything about, however
>>> > we have been advised by our colleagues from the ccNSO (ICANN) to send you
>>> > this email message.
>>> >
>>> > We need some help with getting our ccTLD registered worldwide.
>>> > Several Internet services sites cannot be used by our customers, because
>>> > the .CW is not recognized.
>>> > In our case it prevents us as university to make use of (for instance)
>>> > Google Apps.
>>>
>>> There are google people on this list who (if they haven't already
>>> contacted you about it) will no doubt be happy to help you out with that
>>> specific problem, in their normal efficient way.
>>>
>>> More generally, there are many people who make assumptions about what a
>>> valid domain name is. A common example (I find) can be found in web forms
>>> which validate e-mail addresses. I can't even remember the number of times I
>>> was told that jabley at ca.afilias.info was invalid when I was working for
>>> Afilias, which always struck me as pleasantly ironic, especially when the
>>> web forms in question were provided by people trying to sell us stuff.
>>>
>>> There's no central registry for broken human expectations of how the DNS
>>> works. You pretty much need to just get used to complaining to the people
>>> who provide individual broken services when you find them.
>>>
>>>
>>> Joe
>>>
>>> _______________________________________________
>>> dns-operations mailing list
>>> dns-operations at lists.dns-oarc.net
>>> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
>>> dns-jobs mailing list
>>> https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
>>
>>
>>
>> _______________________________________________
>> dns-operations mailing list
>> dns-operations at lists.dns-oarc.net
>> https://lists.dns-oarc.net/mailman/listinfo/dns-operations
>> dns-jobs mailing list
>> https://lists.dns-oarc.net/mailman/listinfo/dns-jobs