Revised draft recommendations - 2-character letter-letter combinations in ASCII and country and territory names
Dear Work Track 5 members, In advance of the call this coming Wednesday 22 August at 20:00 UTC, the leadership team is sharing revised draft recommendations on 2-character letter-letter combinations in ASCII and country and territory names. These revisions will be discussed on Wednesday’s call. Feedback is encouraged on the mailing list prior to the call. The following is a summary of the changes since the last version: * Added summary/introductory text on the first page to provide context and clarify the purpose of the document. * Removed language about consensus calls for the moment, so that the group can focus of the content of the draft recommendations. * Clarified in the text of recommendations 1-8 that the recommendations apply to the top level only. * Removed reference to translations from recommendations 3, 4, and 6 for the moment. Since there is currently a range of views on the issue of translations, the leadership team suggests including a question in the Initial Report about this issue (see final section of the attached document for proposed text). Once the group has reviewed community input, the WT can finalize a recommendation on this issue if there is agreement to do so. * Revised recommendation 7 to clarify the text following feedback on the mailing list. * Removed the text “the ICANN community may want to consider. . .” from recommendations 2-8, since there does not appear to be agreement on this language. A recommendation 9 has been added, which focuses only on the scope of work for the PDP. Kind regards, Emily Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976
Hey: I think text should always say “country or territory code” when it says “country code”... Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua
On Aug 20, 2018, at 10:23 AM, Emily Barabas <emily.barabas@icann.org> wrote:
Dear Work Track 5 members,
In advance of the call this coming Wednesday 22 August at 20:00 UTC, the leadership team is sharing revised draft recommendations on 2-character letter-letter combinations in ASCII and country and territory names. These revisions will be discussed on Wednesday’s call. Feedback is encouraged on the mailing list prior to the call.
The following is a summary of the changes since the last version:
Added summary/introductory text on the first page to provide context and clarify the purpose of the document. Removed language about consensus calls for the moment, so that the group can focus of the content of the draft recommendations. Clarified in the text of recommendations 1-8 that the recommendations apply to the top level only. Removed reference to translations from recommendations 3, 4, and 6 for the moment. Since there is currently a range of views on the issue of translations, the leadership team suggests including a question in the Initial Report about this issue (see final section of the attached document for proposed text). Once the group has reviewed community input, the WT can finalize a recommendation on this issue if there is agreement to do so. Revised recommendation 7 to clarify the text following feedback on the mailing list. Removed the text “the ICANN community may want to consider. . .” from recommendations 2-8, since there does not appear to be agreement on this language. A recommendation 9 has been added, which focuses only on the scope of work for the PDP.
Kind regards, Emily
Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976
<Draft Recommendations - country and territory names - 20 August 2018.pdf> <Draft Recommendations - country and territory names - 20 August 2018.docx> _______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5
Javier, “Country code” is an established term of very long standing, going back to RFC 1591 and used many times since in RFCs, the ICANN Bylaws, etc., etc. It’s not within our remit to change it. See, e.g., the IANA website at https://www.iana.org/help/eligible-tlds: Eligible countries for country-code TLDs We are not in the business of deciding what is and what is not a country. Instead, we employ a neutral standard maintained by the ISO 3166 Maintenance Agency. Our policy is to create new country-code top-level domains when the country or territory is listed on the ISO 3166-1 standard. The codes we use are two-letter codes from the ISO 3166-1 standard. The selection of the ISO 3166-1 standard as a basis for country-code top-level domain names was made with the knowledge that ISO has a politically neutral procedure for determining which entities should be and should not be listed in the standard. On Mon, Aug 20, 2018 at 1:06 PM Javier Rua <javrua@gmail.com> wrote:
Hey:
I think text should always say “country or territory code” when it says “country code”...
Javier Rúa-Jovet
+1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua
On Aug 20, 2018, at 10:23 AM, Emily Barabas <emily.barabas@icann.org> wrote:
Dear Work Track 5 members,
In advance of the call this coming Wednesday 22 August at 20:00 UTC, the leadership team is sharing revised draft recommendations on 2-character letter-letter combinations in ASCII and country and territory names. These revisions will be discussed on Wednesday’s call. Feedback is encouraged on the mailing list prior to the call.
The following is a summary of the changes since the last version:
- Added summary/introductory text on the first page to provide context and clarify the purpose of the document. - Removed language about consensus calls for the moment, so that the group can focus of the content of the draft recommendations. - Clarified in the text of recommendations 1-8 that the recommendations apply to the top level only. - Removed reference to translations from recommendations 3, 4, and 6 for the moment. Since there is currently a range of views on the issue of translations, the leadership team suggests including a question in the Initial Report about this issue (see final section of the attached document for proposed text). Once the group has reviewed community input, the WT can finalize a recommendation on this issue if there is agreement to do so. - Revised recommendation 7 to clarify the text following feedback on the mailing list. - Removed the text “the ICANN community may want to consider. . .” from recommendations 2-8, since there does not appear to be agreement on this language. A recommendation 9 has been added, which focuses only on the scope of work for the PDP.
Kind regards,
Emily
*Emily Barabas *| Policy Manager
*ICANN* | Internet Corporation for Assigned Names and Numbers
Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976
<Draft Recommendations - country and territory names - 20 August 2018.pdf>
<Draft Recommendations - country and territory names - 20 August 2018.docx>
_______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5
_______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5
Thx Greg. Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua
On Aug 20, 2018, at 2:22 PM, Greg Shatan <gregshatanipc@gmail.com> wrote:
Javier,
“Country code” is an established term of very long standing, going back to RFC 1591 and used many times since in RFCs, the ICANN Bylaws, etc., etc. It’s not within our remit to change it. See, e.g., the IANA website at https://www.iana.org/help/eligible-tlds: Eligible countries for country-code TLDs
We are not in the business of deciding what is and what is not a country. Instead, we employ a neutral standard maintained by the ISO 3166 Maintenance Agency. Our policy is to create new country-code top-level domains when the country or territory is listed on the ISO 3166-1 standard.
The codes we use are two-letter codes from the ISO 3166-1 standard. The selection of the ISO 3166-1 standard as a basis for country-code top-level domain names was made with the knowledge that ISO has a politically neutral procedure for determining which entities should be and should not be listed in the standard.
On Mon, Aug 20, 2018 at 1:06 PM Javier Rua <javrua@gmail.com> wrote: Hey:
I think text should always say “country or territory code” when it says “country code”...
Javier Rúa-Jovet
+1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua
On Aug 20, 2018, at 10:23 AM, Emily Barabas <emily.barabas@icann.org> wrote:
Dear Work Track 5 members,
In advance of the call this coming Wednesday 22 August at 20:00 UTC, the leadership team is sharing revised draft recommendations on 2-character letter-letter combinations in ASCII and country and territory names. These revisions will be discussed on Wednesday’s call. Feedback is encouraged on the mailing list prior to the call.
The following is a summary of the changes since the last version:
Added summary/introductory text on the first page to provide context and clarify the purpose of the document. Removed language about consensus calls for the moment, so that the group can focus of the content of the draft recommendations. Clarified in the text of recommendations 1-8 that the recommendations apply to the top level only. Removed reference to translations from recommendations 3, 4, and 6 for the moment. Since there is currently a range of views on the issue of translations, the leadership team suggests including a question in the Initial Report about this issue (see final section of the attached document for proposed text). Once the group has reviewed community input, the WT can finalize a recommendation on this issue if there is agreement to do so. Revised recommendation 7 to clarify the text following feedback on the mailing list. Removed the text “the ICANN community may want to consider. . .” from recommendations 2-8, since there does not appear to be agreement on this language. A recommendation 9 has been added, which focuses only on the scope of work for the PDP.
Kind regards,
Emily
Emily Barabas | Policy Manager
ICANN | Internet Corporation for Assigned Names and Numbers
Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976
<Draft Recommendations - country and territory names - 20 August 2018.pdf> <Draft Recommendations - country and territory names - 20 August 2018.docx>
_______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5
Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5
I agree, but I have a case where ISO does not always have a politically neutral procedure: Islas Malvinas They are islands that were governed by Argentina, appropriated by the English for a long time, and from that moment they were claimed by successive Argentine governments. Since the creation of the UN, it has been insisted that both nations sit down to negotiate. ISO considered that those islands were English and assigned the code according to that consideration. Due to the ignorance of these procedures, ICANN received many complaints about this country code. If I had been a government, I would have claimed ISO, not ICANN ... I would have even reserved it ... Still in discussion ... REgards Alberto De: Gnso-newgtld-wg-wt5 <gnso-newgtld-wg-wt5-bounces@icann.org> En nombre de Greg Shatan Enviado el: lunes, 20 de agosto de 2018 03:23 p.m. Para: Javier Rua <javrua@gmail.com> CC: gnso-newgtld-wg-wt5@icann.org Asunto: Re: [Gnso-newgtld-wg-wt5] Revised draft recommendations - 2-character letter-letter combinations in ASCII and country and territory names Javier, “Country code” is an established term of very long standing, going back to RFC 1591 and used many times since in RFCs, the ICANN Bylaws, etc., etc. It’s not within our remit to change it. See, e.g., the IANA website at https://www.iana.org/help/eligible-tlds: Eligible countries for country-code TLDs We are not in the business of deciding what is and what is not a country. Instead, we employ a neutral standard maintained by the ISO 3166 Maintenance Agency. Our policy is to create new country-code top-level domains when the country or territory is listed on the ISO 3166-1 standard. The codes we use are two-letter codes from the ISO 3166-1 standard. The selection of the ISO 3166-1 standard as a basis for country-code top-level domain names was made with the knowledge that ISO has a politically neutral procedure for determining which entities should be and should not be listed in the standard. On Mon, Aug 20, 2018 at 1:06 PM Javier Rua <javrua@gmail.com <mailto:javrua@gmail.com> > wrote: Hey: I think text should always say “country or territory code” when it says “country code”... Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua On Aug 20, 2018, at 10:23 AM, Emily Barabas <emily.barabas@icann.org <mailto:emily.barabas@icann.org> > wrote: Dear Work Track 5 members, In advance of the call this coming Wednesday 22 August at 20:00 UTC, the leadership team is sharing revised draft recommendations on 2-character letter-letter combinations in ASCII and country and territory names. These revisions will be discussed on Wednesday’s call. Feedback is encouraged on the mailing list prior to the call. The following is a summary of the changes since the last version: * Added summary/introductory text on the first page to provide context and clarify the purpose of the document. * Removed language about consensus calls for the moment, so that the group can focus of the content of the draft recommendations. * Clarified in the text of recommendations 1-8 that the recommendations apply to the top level only. * Removed reference to translations from recommendations 3, 4, and 6 for the moment. Since there is currently a range of views on the issue of translations, the leadership team suggests including a question in the Initial Report about this issue (see final section of the attached document for proposed text). Once the group has reviewed community input, the WT can finalize a recommendation on this issue if there is agreement to do so. * Revised recommendation 7 to clarify the text following feedback on the mailing list. * Removed the text “the ICANN community may want to consider. . .” from recommendations 2-8, since there does not appear to be agreement on this language. A recommendation 9 has been added, which focuses only on the scope of work for the PDP. Kind regards, Emily Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas@icann.org <mailto:emily.barabas@icann.org> | Phone: +31 (0)6 84507976 <Draft Recommendations - country and territory names - 20 August 2018.pdf> <Draft Recommendations - country and territory names - 20 August 2018.docx> _______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org <mailto:Gnso-newgtld-wg-wt5@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5 _______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org <mailto:Gnso-newgtld-wg-wt5@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5
Interesting Alberto! ¡Gracias! Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua
On Aug 20, 2018, at 6:31 PM, Alberto Soto <alberto@soto.net.ar> wrote:
I agree, but I have a case where ISO does not always have a politically neutral procedure: Islas Malvinas They are islands that were governed by Argentina, appropriated by the English for a long time, and from that moment they were claimed by successive Argentine governments. Since the creation of the UN, it has been insisted that both nations sit down to negotiate. ISO considered that those islands were English and assigned the code according to that consideration. Due to the ignorance of these procedures, ICANN received many complaints about this country code. If I had been a government, I would have claimed ISO, not ICANN ... I would have even reserved it ... Still in discussion ...
REgards
Alberto
De: Gnso-newgtld-wg-wt5 <gnso-newgtld-wg-wt5-bounces@icann.org> En nombre de Greg Shatan Enviado el: lunes, 20 de agosto de 2018 03:23 p.m. Para: Javier Rua <javrua@gmail.com> CC: gnso-newgtld-wg-wt5@icann.org Asunto: Re: [Gnso-newgtld-wg-wt5] Revised draft recommendations - 2-character letter-letter combinations in ASCII and country and territory names
Javier,
“Country code” is an established term of very long standing, going back to RFC 1591 and used many times since in RFCs, the ICANN Bylaws, etc., etc. It’s not within our remit to change it. See, e.g., the IANA website at https://www.iana.org/help/eligible-tlds: Eligible countries for country-code TLDs We are not in the business of deciding what is and what is not a country. Instead, we employ a neutral standard maintained by the ISO 3166 Maintenance Agency. Our policy is to create new country-code top-level domains when the country or territory is listed on the ISO 3166-1 standard.
The codes we use are two-letter codes from the ISO 3166-1 standard. The selection of the ISO 3166-1 standard as a basis for country-code top-level domain names was made with the knowledge that ISO has a politically neutral procedure for determining which entities should be and should not be listed in the standard.
On Mon, Aug 20, 2018 at 1:06 PM Javier Rua <javrua@gmail.com> wrote: Hey:
I think text should always say “country or territory code” when it says “country code”...
Javier Rúa-Jovet
+1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua
On Aug 20, 2018, at 10:23 AM, Emily Barabas <emily.barabas@icann.org> wrote:
Dear Work Track 5 members,
In advance of the call this coming Wednesday 22 August at 20:00 UTC, the leadership team is sharing revised draft recommendations on 2-character letter-letter combinations in ASCII and country and territory names. These revisions will be discussed on Wednesday’s call. Feedback is encouraged on the mailing list prior to the call.
The following is a summary of the changes since the last version:
Added summary/introductory text on the first page to provide context and clarify the purpose of the document. Removed language about consensus calls for the moment, so that the group can focus of the content of the draft recommendations. Clarified in the text of recommendations 1-8 that the recommendations apply to the top level only. Removed reference to translations from recommendations 3, 4, and 6 for the moment. Since there is currently a range of views on the issue of translations, the leadership team suggests including a question in the Initial Report about this issue (see final section of the attached document for proposed text). Once the group has reviewed community input, the WT can finalize a recommendation on this issue if there is agreement to do so. Revised recommendation 7 to clarify the text following feedback on the mailing list. Removed the text “the ICANN community may want to consider. . .” from recommendations 2-8, since there does not appear to be agreement on this language. A recommendation 9 has been added, which focuses only on the scope of work for the PDP.
Kind regards, Emily
Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas@icann.org | Phone: +31 (0)6 84507976
<Draft Recommendations - country and territory names - 20 August 2018.pdf> <Draft Recommendations - country and territory names - 20 August 2018.docx> _______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5 _______________________________________________ Gnso-newgtld-wg-wt5 mailing list Gnso-newgtld-wg-wt5@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg-wt5
Many thanks for sending these round ahead of the call tomorrow Emily. From my perspective, these are in great shape now, and I’d be happy to see these go on to the initial report. It will be very interesting to see the broader community feedback on the ‘translations into any language’ questions. Best wishes Nick From: Gnso-newgtld-wg-wt5 <gnso-newgtld-wg-wt5-bounces@icann.org> On Behalf Of Emily Barabas Sent: 20 August 2018 15:23 To: gnso-newgtld-wg-wt5@icann.org Subject: [Gnso-newgtld-wg-wt5] Revised draft recommendations - 2-character letter-letter combinations in ASCII and country and territory names Dear Work Track 5 members, In advance of the call this coming Wednesday 22 August at 20:00 UTC, the leadership team is sharing revised draft recommendations on 2-character letter-letter combinations in ASCII and country and territory names. These revisions will be discussed on Wednesday’s call. Feedback is encouraged on the mailing list prior to the call. The following is a summary of the changes since the last version: * Added summary/introductory text on the first page to provide context and clarify the purpose of the document. * Removed language about consensus calls for the moment, so that the group can focus of the content of the draft recommendations. * Clarified in the text of recommendations 1-8 that the recommendations apply to the top level only. * Removed reference to translations from recommendations 3, 4, and 6 for the moment. Since there is currently a range of views on the issue of translations, the leadership team suggests including a question in the Initial Report about this issue (see final section of the attached document for proposed text). Once the group has reviewed community input, the WT can finalize a recommendation on this issue if there is agreement to do so. * Revised recommendation 7 to clarify the text following feedback on the mailing list. * Removed the text “the ICANN community may want to consider. . .” from recommendations 2-8, since there does not appear to be agreement on this language. A recommendation 9 has been added, which focuses only on the scope of work for the PDP. Kind regards, Emily Emily Barabas | Policy Manager ICANN | Internet Corporation for Assigned Names and Numbers Email: emily.barabas@icann.org<mailto:emily.barabas@icann.org> | Phone: +31 (0)6 84507976
participants (5)
-
Alberto Soto -
Emily Barabas -
Greg Shatan -
Javier Rua -
Nick Wenban-Smith