<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl =
"http://schemas.microsoft.com/repl/" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =
"http://www.passport.com/NameSpace.xsd" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META content="text/html; charset=gb2312" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19154">
<STYLE>@font-face {
font-family: MS Gothic;
}
@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Consolas;
}
@font-face {
font-family: @MS Gothic;
}
@page WordSection1 {size: 612.0pt 792.0pt; margin: 70.85pt 70.85pt 70.85pt 70.85pt; }
P.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
PRE {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-priority: 99; mso-style-link: "Pr¨¦format¨¦ HTML Car"
}
SPAN.PrformatHTMLCar {
FONT-FAMILY: "Courier New"; mso-style-priority: 99; mso-style-link: "Pr¨¦format¨¦ HTML"; mso-style-name: "Pr¨¦format¨¦ HTML Car"
}
SPAN.HTMLPreformattedChar {
FONT-FAMILY: Consolas; mso-style-priority: 99; mso-style-link: "HTML Preformatted"; mso-style-name: "HTML Preformatted Char"
}
P.HTMLPreformatted {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-link: "HTML Preformatted Char"; mso-style-name: "HTML Preformatted"
}
LI.HTMLPreformatted {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-link: "HTML Preformatted Char"; mso-style-name: "HTML Preformatted"
}
DIV.HTMLPreformatted {
MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt; mso-style-link: "HTML Preformatted Char"; mso-style-name: "HTML Preformatted"
}
SPAN.EmailStyle21 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal
}
SPAN.EmailStyle22 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle23 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal
}
SPAN.EmailStyle24 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
OL {
MARGIN-BOTTOM: 0cm
}
UL {
MARGIN-BOTTOM: 0cm
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=FR link=blue vLink=purple>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=262014811-16122011>FYI</SPAN></FONT></DIV>
<DIV> </DIV>
<P style="MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; FONT-SIZE: 10pt"><FONT
color=#000000 face=arial>Kind regards<BR>Wolf-Ulrich </FONT></P><BR>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px" dir=ltr>
<DIV dir=ltr lang=de class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>Von:</B> owner-council@gnso.icann.org
[mailto:owner-council@gnso.icann.org] <B>Im Auftrag von </B>Glen de Saint
G¨¦ry<BR><B>Gesendet:</B> Freitag, 16. Dezember 2011 11:59<BR><B>An:</B>
Council GNSO<BR><B>Betreff:</B> [council] GNSO Council Resolutions - 15
December 2011<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Dear
Councillors,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt"
lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Ahead of
the official GNSO Council minutes, the following two resolutions were passed
at the Council meeting on 15 December 2011.<BR><BR>Please let me know if you
have any questions.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Thank
you.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Kind
regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt"
lang=EN-US><o:p> </o:p></SPAN></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt"
lang=EN-US>Glen<o:p></o:p></SPAN></P><PRE style="TEXT-INDENT: -18pt; MARGIN-LEFT: 36pt; mso-list: l0 level1 lfo2"><![if !supportLists]><B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><SPAN style="mso-list: Ignore">1.<SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></SPAN></SPAN></B><![endif]><B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Competing Proposed Motion on the UDRP PDP </SPAN></B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Whereas the Registration Abuse Policies Working Group submitted a final report to the GNSO Council on 29 May 2010 (see <A href="http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf"><SPAN style="COLOR: windowtext">http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf</SPAN></A>), recommending an issue report on the current state of the UDRP considering both<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>(a) How the UDRP has addressed the problem of cybersquatting to date, and any insufficiencies/inequalities associated with the process, and<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>(b) Whether the definition of cybersquatting inherent within the existing UDRP language needs to be reviewed or updated, and<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Whereas, on February 3, 2011, the GNSO Council requested an Issues Report in accordance with the recommendations of the Registration Abuse Policies Working Group (<A href="http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf"><SPAN style="COLOR: windowtext">http://gnso.icann.org/issues/rap/rap-wg-final-report-29may10-en.pdf</SPAN></A>) and<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Whereas, a Preliminary Issue Report was published on 27 May 2011 (<A href="http://gnso.icann.org/issues/prelim-report-current-state-udrp-27may11-en.pdf"><SPAN style="COLOR: windowtext">http://gnso.icann.org/issues/prelim-report-current-state-udrp-27may11-en.pdf</SPAN></A>) and series of webinars and workshops were held soliciting public comment to allow for the ICANN community to provide feedback on the analysis and recommendations contained therein, and<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Whereas, a Final Issue Report was published on 3 October 2011 (<A href="http://gnso.icann.org/issues/udrp/udrp-final-issue-report-03oct11-en.pdf"><SPAN style="COLOR: windowtext">http://gnso.icann.org/issues/udrp/udrp-final-issue-report-03oct11-en.pdf</SPAN></A>) in which ICANN staff recommended the GNSO Council consider the ¡°perspective of the majority of the ICANN community, and the advice of the Government Advisory Committee (GAC), and the At-Large Advisory Committee¡± and that ¡°a PDP be delayed until after the New gTLD Uniform Rapid Suspension System (URS) has been in operation for at least eighteen months. . . to allow the policy process to be informed by data regarding the effectiveness of the URS, which was modeled on the UDRP, to address the problem of cybersquatting.¡±<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>RESOLVED, that the GNSO approves the initiation of a PDP and the establishment of a Working Group on recommendation #7 of the IRTP Part B Working Group concerning the requirement to lock a domain name subject to UDRP proceedings, which the GNSO Council at its meeting on 22 June 2011 received and agreed to consider when it takes up consideration of the Final Issue Report on the Current State of the UDRP.<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>RESOLVED further, the GNSO Council requests a new Issue Report on the current state of all rights protection mechanisms implemented for both existing and new gTLDs, including but not limited to, the UDRP and URS, should be delivered to the GNSO Council by no later than eighteen (18) months following the delegation of the first new gTLD.<o:p></o:p></SPAN></PRE>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt"
lang=EN-US><o:p> </o:p></SPAN></P><PRE style="TEXT-INDENT: -18pt; MARGIN-LEFT: 36pt; mso-list: l0 level1 lfo2"><![if !supportLists]><B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><SPAN style="mso-list: Ignore">2.<SPAN style="FONT: 7pt 'Times New Roman'"> </SPAN></SPAN></SPAN></B><![endif]><B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Motion for JIG (Joint ccNSO/GNSO IDN Working Group)</SPAN></B><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US> <B>response to August 2011 Board Resolution on Single Character IDN TLDs</B><o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><BR>WHEREAS, the JIG (Joint ccNSO/GNSO IDN Working Group) was formed by mutual charters between the ccNSO and GNSO councils, and extended (ccNSO: <A href="http://ccnso.icann.org/workinggroups/minutes-council-23aug11-en.pdf"><SPAN style="COLOR: windowtext">http://ccnso.icann.org/workinggroups/minutes-council-23aug11-en.pdf</SPAN></A> | GNSO: <A href="http://gnso.icann.org/resolutions/#201107"><SPAN style="COLOR: windowtext">http://gnso.icann.org/resolutions/#201107</SPAN></A>) to complete its work on the 3 identified issues of common interest between the ccNSO and GNSO;<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>WHEREAS, the subject of Single Character IDN TLDs was discussed at the GNSO IDN WG, the GNSO Reserved Names WG and incorporated into the GNSO New gTLD Recommendations, and consistently resulted in community consensus to allow the implementation of Single Character IDN TLDs;<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>WHEREAS, the JIG developed and published an Initial Report on Single Character IDN TLDs (<A href="http://ccnso.icann.org/workinggroups/jig-initial-report-26jul10-en.pdf"><SPAN style="COLOR: windowtext">http://ccnso.icann.org/workinggroups/jig-initial-report-26jul10-en.pdf</SPAN></A>) for public comments (<A href="http://www.icann.org/en/announcements/announcement-2-27jul10-en.htm"><SPAN style="COLOR: windowtext">http://www.icann.org/en/announcements/announcement-2-27jul10-en.htm</SPAN></A>) and incorporated the comments (<A href="http://forum.icann.org/lists/jig-initial-report/pdfaul7JXcqaa.pdf"><SPAN style="COLOR: windowtext">http://forum.icann.org/lists/jig-initial-report/pdfaul7JXcqaa.pdf</SPAN></A>) into a draft Final Report (<A href="http://www.icann.org/en/announcements/announcement-04dec10-en.htm"><SPAN style="COLOR: windowtext">http://www.icann.org/en/announcements/announcement-04dec10-en.htm</SPAN></A>) for further public comments,<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>WHEREAS, the JIG conducted a public session during the Cartagena ICANN meetings (<A href="http://cartagena39.icann.org/node/15395"><SPAN style="COLOR: windowtext">http://cartagena39.icann.org/node/15395</SPAN></A>);<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>WHEREAS, the JIG incorporated comments received (<A href="http://forum.icann.org/lists/jig-draft-final-report/pdfQxF383O30Q.pdf"><SPAN style="COLOR: windowtext">http://forum.icann.org/lists/jig-draft-final-report/pdfQxF383O30Q.pdf</SPAN></A>) and completed a Final Report (<A href="http://ccnso.icann.org/workinggroups/jig-final-report-single-character-idns-30mar11-en.pdf"><SPAN style="COLOR: windowtext">http://ccnso.icann.org/workinggroups/jig-final-report-single-character-idns-30mar11-en.pdf</SPAN></A>) which was approved by the ccNSO (<A href="http://ccnso.icann.org/workinggroups/minutes-council-10may11-en.pdf"><SPAN style="COLOR: windowtext">http://ccnso.icann.org/workinggroups/minutes-council-10may11-en.pdf</SPAN></A>) and GNSO (<A href="http://gnso.icann.org/resolutions/#201107"><SPAN style="COLOR: windowtext">http://gnso.icann.org/resolutions/#201107</SPAN></A>) councils;<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>WHEREAS, the ICANN Board made a resolution at their August 25, 2011 meeting regarding the subject: <A href="http://www.icann.org/en/minutes/resolutions-25aug11-en.htm#5"><SPAN style="COLOR: windowtext">http://www.icann.org/en/minutes/resolutions-25aug11-en.htm#5</SPAN></A>; and,<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>WHEREAS, the JIG considered the resolution and found it to be in contradiction with the community consensus on the matter,<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>NOW THEREFORE RESOLVED that, upon the mutual resolution from both the GNSO and ccNSO councils on the subject, the Council Chairs would send to the ICANN Board the following letter in response to their August 2011 resolution on Single Character IDN TLDs:<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>JIG (Joint ccNSO/GNSO IDN Working Group) Response to ICANN Board Resolution on Single Character IDN TLDs<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Dear ICANN Board,<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>First of all, we appreciate activity at the ICANN Board regarding Single Character IDN TLDs. In response to the August 2011 resolution (<A href="http://www.icann.org/en/minutes/resolutions-25aug11-en.htm#5"><SPAN style="COLOR: windowtext">http://www.icann.org/en/minutes/resolutions-25aug11-en.htm#5</SPAN></A>) however, we express our disappointment and concern on 3 critical aspects:<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US> Both the ccNSO and the GNSO councils have at multiple occasions expressed a consensus principle that the introduction of IDN gTLDs or IDN ccTLDs should not be delayed because of lack of readiness of one category. The August 2011 Board resolution (by specifying that ¡°processes for delegation of single-character IDN TLDs will be made available after the first gTLD application round and conclusion of IDN ccTLD policy work.¡±) perhaps inadvertently conflicted with this community consensus understanding and should be rectified or clarified.<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US> The issue of Single Character IDN TLDs have gone through at least 4 rounds of community discussions, including at the GNSO IDN WG (<A href="http://gnso.icann.org/drafts/idn-wg-fr-22mar07.htm"><SPAN style="COLOR: windowtext">http://gnso.icann.org/drafts/idn-wg-fr-22mar07.htm</SPAN></A>), the GNSO Reserved Names WG (<A href="http://gnso.icann.org/issues/new-gtlds/final-report-rn-wg-23may07.htm"><SPAN style="COLOR: windowtext">http://gnso.icann.org/issues/new-gtlds/final-report-rn-wg-23may07.htm</SPAN></A>), incorporated into the GNSO New gTLD recommendations (<A href="http://gnso.icann.org/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm"><SPAN style="COLOR: windowtext">http://gnso.icann.org/issues/new-gtlds/pdp-dec05-fr-parta-08aug07.htm</SPAN></A>), and of course the JIG report (<A href="http://ccnso.icann.org/workinggroups/jig-final-report-single-character-idns-30mar11-en.pdf"><SPAN style="COLOR: windowtext">http://ccnso.icann.org/workinggroups/jig-final-report-single-character-idns-30mar11-en.pdf</SPAN></A>). Each time there is consistent consensus support from the community for allowing Single Character IDN TLDs in the new gTLD process (including the first round), and no objections were received from any of the ACs. The August 2011 Board resolution specifying that Single Character IDN TLDs not be included in the first round ignores this repeated community consensus without reasonable rationale.<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US> While the August 2011 Board resolution generally requested input from a collection of ACs, there is a lack of progressive direction towards the implementation of Single Character IDN TLDs. Furthermore, while input from ACs is always welcome, given the multitude of public comment periods already conducted for the subject, including participation from SSAC members, with consistent consensus response, such consultation with ACs should not become an arbitrary hurdle for the implementation of Single Character IDN TLDs, especially for the New gTLD process. <o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Single Character IDN TLDs is not simply a ¡°good to have¡± feature, but a necessary requirement for some of the IDN communities in order to allow broadly attractive and competitive gTLDs. As an example, for Chinese IDN TLDs, the prohibition of Single Character IDN TLDs would effectively devoid the community of single-syllable-single-word TLDs, which is otherwise acceptable for English and other alphabetic based language TLDs (e.g. ¡°.word¡± would be an acceptable ASCII single-syllable-single-word TLD, yet a similar single-syllable-single-word TLD ¡°.</SPAN><SPAN style="FONT-FAMILY: 'MS Gothic'; FONT-SIZE: 12pt" lang=ZH-CN>×Ö</SPAN><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>¡± would not be acceptable for Chinese), creating an unjustified situation of inequity, and significantly hindering the adoption of IDN.<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>The JIG, through the ccNSO and GNSO councils therefore sincerely urges the Board to:<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US> Implement the community consensus of allowing Single Character IDN TLDs without restricting such implementation to being after the first round of the new gTLD process, and to decouple the requirement that IDN ccTLD or IDN gTLD mechanisms wait for the other;<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US> If necessary, form an implementation team to assist staff in immediately implementing Single Character IDN TLDs for scripts and languages where the input of a Single Character requires multiple keystrokes (e.g. ideographical scripts, and avoiding the potential technical concern of keyboard layouts identified in the JIG report), and for the team to further guide implementation for other scripts as well as coordinate input from the ACs; and,<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US> Update or amend the New gTLD Applicant Guidebook for such implementation before the application period for the first round is over.<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>The JIG and the significantly affected language communities are prepared to support ICANN staff and Board in the swift implementation of Single Character IDN TLDs without compromising the security and stability of the Internet. The JIG further believes that minor adjustments to the Applicant Guidebook would suffice and is ready to work with staff closely to complete its implementation.<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>We look forward to the positive response and actions from the Board.<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>Sincerely,<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>ccNSO Council (approval: [LINK])<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>GNSO Council (approval: [LINK])<o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US>JIG -- Joint ccNSO/GNSO IDN Working Group <o:p></o:p></SPAN></PRE><PRE><SPAN style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt" lang=EN-US><o:p> </o:p></SPAN></PRE>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt"
lang=EN-US><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt">Glen de Saint
G¨¦ry<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt">GNSO
Secretariat<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt"><A
href="mailto:gnso.secretariat@gnso.icann.org"><SPAN
style="COLOR: windowtext">gnso.secretariat@gnso.icann.org</SPAN></A><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 12pt"><A
href="http://gnso.icann.org"><SPAN
style="COLOR: windowtext">http://gnso.icann.org</SPAN></A><o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BLOCKQUOTE></BODY></HTML>