<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:174656917;
mso-list-type:hybrid;
mso-list-template-ids:1489151630 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:693580105;
mso-list-type:hybrid;
mso-list-template-ids:-252413562 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:806355711;
mso-list-type:hybrid;
mso-list-template-ids:1248333640 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3
{mso-list-id:1890530096;
mso-list-type:hybrid;
mso-list-template-ids:166133492 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l3:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l3:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l3:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Dear Sub Team Members,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Please see below the action items and discussion notes captured by staff from the meeting on 15 December. <i>These high-level notes are designed to help Work Track Sub Team members navigate through the content of the call and are not a substitute for the chat room or the recording.</i> See the chat room and recording on the meetings pages at: <a href="https://community.icann.org/display/NGSPP/Work+Track+2+Meetings">https://community.icann.org/display/NGSPP/Work+Track+2+Meetings</a>. See also the attached slides that are referenced below and posted on the wiki.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Julie<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Julie Hedlund, Policy Director<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Action Items/Discussion Notes 15 December</span></b><span style='font-size:10.5pt;font-family:Calibri'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>ACTION:</span></b><span style='font-size:10.5pt;font-family:Calibri'> Look at the new language of the registry agreement once it comes out and how that language may affect some reservations.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:Calibri'>Reserved Names at the Second Level – See the Google Doc at: <a href="https://docs.google.com/spreadsheets/d/1WgsYlUpKI_QGuIOlOxtu4uBBj8ZWgD0bTw8GCamL3NQ/edit#gid=2486987">https://docs.google.com/spreadsheets/d/1WgsYlUpKI_QGuIOlOxtu4uBBj8ZWgD0bTw8GCamL3NQ/edit#gid=2486987</a>. <o:p></o:p></span></i></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Jeff Neuman:</span></b><span style='font-size:10.5pt;font-family:Calibri'> Remember the default...if we get no comments otherwise, the assumption is that whatever is applicable today will be applicable in the future. So speak up if you have an issue :)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>ICANN/IANA Names -- All Levels and 2nd & 3rd levels; Example reserved at all levels, ASCII only.<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Not adoped/not protected at the second level<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Doesn't seem to be support to change policy to reserve at the second level.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Move in the direction of the AGB to not reserve at the second level.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Before the AGB was final, ICANN had itself, IANA, and some others proposed to be protected, but if it wasn't going to protect other organizations it wasn't going to protect its own.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- The rationale was that if someone could pretent to be ICANN/IANA etc.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Example has been reserved for a long time. Don't need to spend a lot of time on it.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Rubens Kuhl:</span></b><span style='font-size:10.5pt;font-family:Calibri'> I think IANA still deserves such reservation. It's a "household name" of sorts. As in the IANA label only, not all the IANA labels. Example and ROOT-SERVERS are also worth keeping reserved, IMHO. ICANN is not worthy reserving. ;-) Example was also mentioned as an IANA label. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt;font-family:Calibri'>: To reserve anything at second level, there should be a very good reason why. Why ICANN and IANA and not other international organisations?<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Jeff Neuman:</span></b><span style='font-size:10.5pt;font-family:Calibri'> @Annabeth - that is why ICANN took its name off the list<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Rubens Kuhl</span></b><span style='font-size:10.5pt;font-family:Calibri'>: IANA is not an organization, PTI is. IANA is similar to INTERNIC, a long-recalled name with a meaning. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt;font-family:Calibri'>: Exactly :-) That is true, Rubens. You have a point.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Rubens Kuhl:</span></b><span style='font-size:10.5pt;font-family:Calibri'> It's also of note that we could move such names to being "LRO material", as in someone which is not RIPE applies for .RIPE, RIPE could file an LRO. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Greg Shatan:</span></b><span style='font-size:10.5pt;font-family:Calibri'> The iana.org domain name is used for emails instructing changes to the Root Zone, and for the website on which critical information is displayed. PTI also owns iana.com and iana.net.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Jeff Neuman:</span></b><span style='font-size:10.5pt;font-family:Calibri'> @Rubens I know IP attorneys that could make similar arguments :) If a registry wants to reserve other versions of "example" it may do so on its own. But I see no reason why it should be protected by ICANN in all TLDs<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Trang Nguyen</span></b><span style='font-size:10.5pt;font-family:Calibri'>: There was a reserved names working group. The final report is posted at https://gnso.icann.org/en/drafts/rn-wg-fr19mar07.pdf and may provide some background info.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Symbols -- not allow them except for hyphens.<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Jeff Neuman:</span></b><span style='font-size:10.5pt;font-family:Calibri'> the 2009 "recommendation" is the result of the final report from the reserved names working group. <o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Rubens Kuhl:</span></b><span style='font-size:10.5pt;font-family:Calibri'> ICANN disallowed even the hyphen.<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Jeff Neuman:</span></b><span style='font-size:10.5pt;font-family:Calibri'> @Rubens - only when the hyphen is in the 3rd and 4th position<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Greg Shatan:</span></b><span style='font-size:10.5pt;font-family:Calibri'> This probably requires an IETF RFC, I'm guessing. Symbols, that is.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Single and two-character IDNs<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Leave as is (no reservations).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- May be noteworthy to make mention of what is possible.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Annebeth Lange, ccNSO</span></b><span style='font-size:10.5pt;font-family:Calibri'>: Just a heads up for the Standardized Framework for Release of Two-Character ASCII Labels to avoid confusion with corresponding country codes, published yesterday. And a comment to IDNs - there have been instances where a 2-letter IDN is to similar to a 2-letter ASCII, so that it could not be accepted. It was on first level, but still it might appear on second level as well. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Single letters and digits -- accepted at 2nd and 3rd level<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- No reservations. Suggest leaving as is.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Any combination of two letters, digits<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- There is now a measurement to allow for the release for these characters if registries folllow certain policy and implementation requirements to avoid confusion.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Could change policy to note the implementation guidelines.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- This provision is to avoid risk of confusion with the country codes. Could warrant something in the policy acknowledging which combinations raise that concern (letter-letter, number-number).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Susan Payne:</span></b><span style='font-size:10.5pt;font-family:Calibri'> Having said which, am I right in thinking that we are holding over the "country code" issue to discuss in the wider context of geo names? EP, EC, EU, AU, UN<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Annebeth Lange, ccNSO:</span></b><span style='font-size:10.5pt;font-family:Calibri'> As for geo-names, I think that should be kept at first level. GAC has been discussing 2-letter codes from ISO-list 3166 at second level, but I do not think they have - at least so far - been anxious about other geonames at second level.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Tagged Names<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- IDN guidelines are the default; an exception can be granted. Right now IDN guidelines would be ceilings.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Currently the policy to implement the AGB reserves the hyphen in the 3rd and 4th location.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- This isn't the only way the IDN guidelines can be implemented.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Suggesting not changing.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Rubens Kuhl:</span></b><span style='font-size:10.5pt;font-family:Calibri'> I'll note that a registry might be allowed to not follow ICANN IDN Guidelines to the letter, by making an RSEP request that ICANN approves. So the guidelines are not the ultimate restrictions to it<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Jeff Neuman:</span></b><span style='font-size:10.5pt;font-family:Calibri'> The third and 4th hyphens could in theory be used for other types of IETF protocols..but to my knowledge they have not been<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>NIC, WHOIS, WWW -- 2nd & 3rd ASCII (now includes RDDS); IDN<o:p></o:p></span></u></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- This is a pain point for IDN registires -- forced to use ASCII only for the NIC label (could not use non-ASCII script) for the registry operation, but this has already changed.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Talking about two different things -- reservation of the name versus use of the name. Not sure if there would be a change in the reservation policy.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Not trying to translate them is what is important, but could consider saying that any translation could be used by the registry.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- For purposes of blocking a name do not try to translate it. Could change to using either NIC or a translation of NIC...(language that is not as strong).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Alexander Schubert:</span></b><span style='font-size:10.5pt;font-family:Calibri'> Jeff is right! (about there being two different things).<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>