[Ctn-crosscom] [GAC] Use of 3-letter country codes as top-level domains - please provide feedback

Lars Hoffmann lars.hoffmann at icann.org
Fri Oct 9 13:35:32 UTC 2015


Dear Nina,
Of course. Thank you for your note.
Best wishes,
Lars 

Lars Hoffmann | Policy Manager
lars.hoffmann at icann.org | tel: +32 491 507680 |skype: lars.hoffmann.icann

ICANN | Internet Corporation for Assigned Names and Numbers
6 Rond Point Schuman | 1040 Brussels | Belgium





On 09/10/2015 14:45, "Pääkkönen Nina" <Nina.Paakkonen at mintc.fi> wrote:

>Dear Mr. Lars Hoffmann,
>
>Finland would like to contribute but unfortunately we are not able to
>submit our answers in due time. So would it be possible that I'll send
>the Finnish input on Monday 19th of October?
>
>With best regards,
>
>Nina Pääkkönen 
>
>Coordinator of International Affairs
>Communications Policy Department
>Ministry of Transport and Communications, Finland
>Tel. +358 295 342217
>twitter @lvmfi
>facebook.com/lvmfi
>lvm.fi
>
>
> Von: Glen de Saint Géry [mailto:Glen at icann.org]
>An: Schneider Thomas BAKOM <Thomas.Schneider at bakom.admin.ch>
>Cc: Olof Nordling <olof.nordling at icann.org>; Tom Dale <tom at acig.com.au>;
>Julia Charvolen <julia.charvolen at icann.org>; Lars Hoffmann
><lars.hoffmann at icann.org>
>Betreff: Use of Country and Territory Names as top-level domains - please
>provide feedback
>
>Dear SO/AC Chair,
>
> As you may be aware, the ccNSO and GNSO Councils have chartered a Cross
>Community Working Group on the Use of Country and Territory Names as
>top-level domains (CWG-UCTN). The objective of the CWG-UCTN is to review
>the current status of representations of country and territory names, as
>they exist under current ICANN policies, guidelines and procedures. In
>addition, the Group has been asked to provide advice regarding the
>feasibility of developing a consistent and uniform set of definitions
>that could be applicable across the respective SO's and AC's for country
>and territory names as top-level domains. Please note that the scope of
>the WG is strictly limited to:
>
>·       Representations of names of Countries, Territories and their
>subdivisions listed on or eligible to be listed on the Alpha-2 code
>International Standard for country codes and codes for their subdivisions
>(ISO 3166-1), (Names of Country and Territory). Other geographical
>indicators, such as regions, are excluded;
>
>·       The use of Country and Territory names as Top Level Domains. The
>use of Country and Territory names as second or other level is excluded.
>
> The CWG-UTCN has divided its work into three work stream: 2-letter
>codes, 3-letter codes, and full names of countries and territories;
>currently the Group is starting its discussion on 3-letter codes and it
>is on this issue specifically that your feedback is being sought at this
>time. Please note that the community will be given ample opportunity to
>comment and provide feedback on all other issues in due course.
>
> To help the CWG-UCTN in its discussion on three-character codes, you
>will find below a number of questions; it would be very helpful to the
>Group if you could provide feedback on some or all questions raised.
>Please do not hesitate to supply any additional comments you may have on
>three-letter codes, as long as they are within the scope of work of the
>CWG (see above).
>
> Please send your comments to Lars Hoffmann (lars.hoffmann at icann.org),
>who is part of the CWG's staff support team, by Friday 9 October 2015. If
>you cannot submit your input by that date, but you would like to
>contribute, please let us know when we can expect to receive your
>contribution so we can plan accordingly.
>
> Your input will be very much appreciated.
>
> With best regards,
>
> Heather Forrest, GNSO (Co-Chair)
>
>Carlos Gutiérrez, GNSO (Co-Chair)
>
>Annebeth Lange, ccNSO (Co-Chair)
>
>Paul Szyndler, ccNSO (Co-Chair)
>
>
>
>
>Questions by the CWG-UCTN on 3-character codes with regard to the use of
>country and territory names as top-level domains
>
> 
>
>1.      In future, should all three-character top-level domains be
>reserved as ccTLDs only and be ineligible for use as gTLDs? What would be
>the advantage or disadvantage of such a policy?
>
>2.      In future, should all three-character top-level domains be
>eligible for use as gTLDs as long as they are not in conflict with the
>existing alpha-3 codes from the ISO 3166-1 list; i.e. the three-character
>version of the same ISO list that is the basis for current ccTLD
>allocation? What would be the advantage or disadvantage of such a policy?
>
>3.      In future, should three-character strings be eligible for use as
>gTLDs if they are not in conflict with existing alpha-3 codes form the
>ISO 3166-1 list and they have received documentation of support or
>non-objection from the relevant government or public authority? What
>would be the advantage or disadvantage of such a policy?
>
>4.      In future, should there be unrestricted use of three-character
>strings as gTLDs if they are not conflicting with any applicable string
>similarity rules? What would be the advantage or disadvantage of such a
>policy?
>
>5.      In future, should all IDN three-character strings be reserved
>exclusively as ccTLDs and be ineligible as IDN gTLDs? What would be the
>advantage or disadvantage of such a policy?
>
>6.      In future, should there be unrestricted use of IDN
>three-character strings if they are not in conflict with existing TLDs or
>any applicable string similarity rules? What would be the advantage or
>disadvantage of such a policy?
>
>7.      Do you have any additional comments that may help the CWG-UCTN in
>its discussion on three-character strings as top-level domains?
>
> 
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5091 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/ctn-crosscom/attachments/20151009/68afa7f0/smime.p7s>


More information about the Ctn-crosscom mailing list