| From: | "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com> |
|---|---|
| To: | damien clochard <damien(at)dalibo(dot)info>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: New gTLDs available / how to protect the PostgreSQL brand |
| Date: | 2014-04-09 13:58:45 |
| Message-ID: | EC55DC235432104F8255702A8D7344D94379BC78@G9W0339.americas.hpqcorp.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
> -----Original Message-----
> From: pgsql-advocacy-owner(at)postgresql(dot)org [mailto:pgsql-advocacy-
> owner(at)postgresql(dot)org] On Behalf Of damien clochard
> Sent: Wednesday, April 09, 2014 8:46 AM
> To: PostgreSQL Advocacy
> Subject: [pgsql-advocacy] New gTLDs available / how to protect the
> PostgreSQL brand
>
> Hi everyone,
>
> The ICANN has launched a few month ago a new program to release 100
> generic top-level domains (gTLDs), such as ".kitchen", ".sexy", ".tatoo", etc.
> Personally I think this expansion has a flawed justification and that it will only
> do harm to brand owners and create overall confusion. Anyway whether we
> like it or not, these new gTLDs are out there in the wild and I think the
> PostgreSQL community needs to organize itself to protect its brand.
It might be worth reaching out to Afilias (who I believe operates these) to see if there is anything that can be done here. They are big Postgres users and supporters.
Brad.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2014-04-09 14:04:34 | Re: New gTLDs available / how to protect the PostgreSQL brand |
| Previous Message | damien clochard | 2014-04-09 12:45:59 | New gTLDs available / how to protect the PostgreSQL brand |