ICANN/GNSO GNSO Email List Archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

[council] Board request for GNSO Council advice on second level protections for certain IGO names and acronyms

  • To: "council@xxxxxxxxxxxxxx" <council@xxxxxxxxxxxxxx>
  • Subject: [council] Board request for GNSO Council advice on second level protections for certain IGO names and acronyms
  • From: Marika Konings <marika.konings@xxxxxxxxx>
  • Date: Wed, 16 Jan 2013 02:03:05 -0800
  • Accept-language: en-US
  • Acceptlanguage: en-US
  • List-id: council@xxxxxxxxxxxxxx
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: Ac3z0LMUXRfmXchyRVOrt+gmgIflIA==
  • Thread-topic: Board request for GNSO Council advice on second level protections for certain IGO names and acronyms
  • User-agent: Microsoft-MacOutlook/14.2.5.121010

Dear All,

Reviewing some of the recent Board resolutions, I noticed the following
request which I don't think the GNSO Council has considered yet: 'the Board
requests that the GNSO Council advise the Board by no later than 28 February
2013 if it is aware of any concern such as with the global public interest
or the security or stability of the DNS, that the Board should take into
account in making its decision about whether to include second level
protections for certain IGO names and acronyms by inclusion on a Reserved
Names List in section 2.2.1.2.3 of the Applicant Guidebook, applicable in
all new gTLD registries approved in the first round of the New gTLD Program.
The specific IGO names to be protected shall be those names or acronyms
that: 1) qualify under the current existing criteria to register a domain
name in the .int gTLD; and 2) have a registered .int domain OR a
determination of eligibility under the .int criteria; and 3) apply to ICANN
to be listed on the reserved names list for the second level prior to the
delegation of any new gTLDs by no later than 28 February 2013' (see
http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-26nov12-
en.htm#1.b). You may want to consider how to handle this request.

With best regards,

Marika


Attachment: smime.p7s
Description: S/MIME cryptographic signature



<<< Chronological Index >>>    <<< Thread Index >>>