<html 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="" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Times;
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:Corbel;
panose-1:2 11 5 3 2 2 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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="EN-US" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D">Great!!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Corbel","sans-serif";
color:#1F497D">Roy<o:p></o:p></span></b></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> NCSG-Discuss [mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU]
<b>On Behalf Of </b>William Drake<br>
<b>Sent:</b> Thursday, December 13, 2012 2:26 AM<br>
<b>To:</b> NCSG-DISCUSS@LISTSERV.SYR.EDU<br>
<b>Subject:</b> Re: [NCSG-Discuss] Fwd: Input Request: 'thick' Whois SG/C Template<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Of course, that'd be the ideal. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Dec 13, 2012, at 2:36, Alain Berranger <<a href="mailto:alain.berranger@gmail.com">alain.berranger@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Hi<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">NPOC inputs are also solicited. Marie-laure Lemineur, NPOC's Program Committee Chair, has joined the “thick” Whois PDP Working Group. Maybe we can work towards an NCSG wide input?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Best, Alain<o:p></o:p></p>
<div>
<p class="MsoNormal">On Sat, Dec 8, 2012 at 1:50 AM, William Drake <<a href="mailto:william.drake@uzh.ch" target="_blank">william.drake@uzh.ch</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">Hi <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Again NCUC inputs are being actively solicited. There's a group of Councilors that I believe includes Wendy and Mary who've been closely engaged on this, plus more recently two of our academic members, Roy Balleste and Joana Kulesza, have
decided to sink their teeth into this. There may other members here who'd take an interest as well. May I suggest that anyone who'd like to help craft a timely and cutting ed response be in touch with the above ASAP? Again, let's broaden the circle of involvement
if we can….<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Bill<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">From:
</span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Glen de Saint Géry <<a href="mailto:Glen@icann.org" target="_blank">Glen@icann.org</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Date:
</span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">December 5, 2012 6:36:45 PM GMT+04:00</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">To:
</span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">William Drake <<a href="mailto:william.drake@uzh.ch" target="_blank">william.drake@uzh.ch</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Cc:
</span></b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Robin Gross <<a href="mailto:robin@ipjustice.org" target="_blank">robin@ipjustice.org</a>>, "<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>" <<a href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a>>,
Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:13.5pt;font-family:"Helvetica","sans-serif"">Subject: Input Request: 'thick' Whois SG/C Template
</span></b><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span lang="FR"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Dear Bill,</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">The “thick” Whois PDP Working Group would appreciate the NCUC’s input through the attached Input Template also in text below: <br>
Thank you.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Kind regards,</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Glen</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Stakeholder Group / Constituency / Input Template ‘thick’ Whois PDP Working Group that the Working Group</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">PLEASE SUBMIT YOUR RESPONSE AT THE LATEST <b>BY 9 January 2012</b> TO THE GNSO SECRETARIAT (</span><u><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:blue"><a href="mailto:gnso.secretariat@gnso.icann.org" target="_blank"><span lang="EN-US">gnso.secretariat@gnso.icann.org</span></a></span></u><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">),
which will forward your statement to the Working Group. If additional time is needed by your SG / C to provide your feedback, please inform the secretariat accordingly, including the expected delivery date so that this can be factored in by the WG.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">The GNSO Council has formed a Working Group of interested stakeholders and Stakeholder Group / Constituency representatives, to collaborate broadly
with knowledgeable individuals and organizations, in order to consider recommendations in relation to ‘thick’ Whois.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">Part of the working group’s effort will be to incorporate ideas and suggestions gathered from Stakeholder Groups, Constituencies through this
template Statement. Please note that the WG is currently in an information-gathering phase. Inserting your response in this form will make it much easier for the Working Group to summarize the responses. This information is helpful to the community in understanding
the points of view of various stakeholders. However, you should feel free to add any information you deem important to inform the working group’s deliberations, even if this does not fit into any of the questions listed below.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">For further information, please visit the WG Workspace (</span><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a href="https://community.icann.org/display/PDP/Home" target="_blank"><span lang="EN-US">https://community.icann.org/display/PDP/Home</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">).</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Process</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<p style="margin-left:.25in;line-height:20.25pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">-</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Please identify the member(s)
of your stakeholder group / constituency who is (are) participating in this working group</span><span lang="FR"><o:p></o:p></span></p>
<p style="margin-left:.25in;line-height:20.25pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">-</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Please identify the members
of your stakeholder group / constituency who participated in developing the perspective(s) set forth below</span><span lang="FR"><o:p></o:p></span></p>
<p style="margin-left:.25in;line-height:20.25pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">-</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Please describe the process
by which your stakeholder group / constituency arrived at the perspective(s) set forth below</span><span lang="FR"><o:p></o:p></span></p>
<p style="margin-left:.25in;line-height:20.25pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">-</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">If not indicated otherwise,
the WG will consider your submission a SG / C position / contribution. Please note that this should not prevent the submission of individual and/or minority views as part of your submission, as long as these are clearly identified.</span><span lang="FR"><o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">Topics:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">The WG is tasked to provide the GNSO Council with a policy recommendation regarding the use of ‘thick’ Whois by all gTLD Registries, both existing
and future. As part of its deliberations, the WG is expected to consider the topics listed below in the context of ‘thick’ Whois. Please provide your stakeholder group’s / constituency’s views, including quantitative and/or empirical information supporting
your views, on these topics in relation to whether or not to require ‘thick’ Whois for all gTLDs and/or provide any information that you think will help the WG in its deliberations (for further information on each of these topics, please see the WG Charter</span><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif""><a href="https://community.icann.org/x/vIg3Ag" target="_blank"><span lang="EN-US">https://community.icann.org/x/vIg3Ag</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">):</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Response consistency - a ‘thick’ Registry
can dictate the labeling and display of Whois information to be sure the information is easy to parse, and all Registrars/clients would have to display it accordingly. This could be considered a benefit but also a potential cost. This might also be a benefit
in the context of internationalized registration data as even with the use of different scripts, uniform data collection and display standards could be applied.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Stability - in the event of a Registrar
business or technical failure, it could be beneficial to ICANN and registrants to have the full set of domain registration contact data stored by four organizations (the Registry, the Registry's escrow agent, the Registrar, and the Registrar's escrow agent),
which would be the case in a ‘thick’ registry.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Accessibility - is the provision of Whois
information at the registry level under the ‘thick’ Whois model more effective and cost-effective than a ‘thin’ model in protecting consumers and users of Whois data and intellectual property owners?</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Impact on privacy and data protection
- how would ‘thick’ Whois affect privacy and data protection, also taking into account the involvement of different jurisdictions with different laws and legislation with regard to data privacy as well as possible cross border transfers of registrant data?</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Cost implications - what are the cost
implications of a transition to 'thick' Whois for Registries, Registrars, registrants and other parties for all gTLDs? Conversely, what are the cost implications to Registries, Registrars, registrants and other parties if no transition is mandated?</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Synchronization/migration - what would
be the impact on the registry and registrar WHOIS and EPP systems for those Registries currently operating a thin registry, both in the migration phase to ‘thick’ WHOIS as well as ongoing operations?</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Authoritativeness - what are the implications
of a ‘thin’ Registry possibly becoming authoritative for registrant Whois data following the transition from a thin-registry model to a thick-registry model. The Working Group should consider the term “authoritative” in both the technical (the repository of
the authoritative data) and policy (who has authority over the data) meanings of the word when considering this issue.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Competition in registry services - what
would be the impact on competition in registry services should all Registries be required to provide Whois service using the ‘thick’ Whois model – would there be more, less or no difference with regard to competition in registry services?</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Existing Whois Applications - What, if
anything, are the potential impacts on the providers of third-party WHOIS-related applications if ‘thick’ WHOIS is required for all gtLDs?</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Data escrow - ‘thick’ Whois might obviate
the need for the registrar escrow program and attendant expenses to ICANN and registrars.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div style="margin-left:.25in">
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:Symbol">·</span><span style="font-size:7.0pt"> </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Registrar Port 43 Whois requirements -
‘thick’ Whois could make the requirement for Registrars to maintain Port 43 Whois access redundant.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">Based on your assessment of these topics, you are also encouraged to indicate whether you think there should or there shouldn’t be a requirement
for ‘thick’ Whois by all gTLD Registries.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">Your view:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span style="font-size:11.0pt;
font-family:"Calibri","sans-serif"">If there is any other information you think should be considered by the WG as part of its deliberations, please feel free to include that here.</span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><b><span lang="FR" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">Other information:</span></b><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="line-height:18.0pt"><span lang="FR" style="font-size:
11.0pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D"> </span><span lang="FR"><o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif""> </span><span lang="FR"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
Alain Berranger, B.Eng, MBA<o:p></o:p></p>
<div>
<p class="MsoNormal">Member, Board of Directors, CECI, <a href="http://www.ceci.ca/en/about-ceci/team/board-of-directors/" target="_blank">http://www.ceci.ca</a><o:p></o:p></p>
<div>
<p class="MsoNormal">Executive-in-residence, Schulich School of Business, <a href="http://www.schulich.yorku.ca" target="_blank">
www.schulich.yorku.ca</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Treasurer, Global Knowledge Partnership Foundation, <a href="http://www.gkpfoundation.org" target="_blank">
www.gkpfoundation.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">NA representative, Chasquinet Foundation, <span style="font-family:"Times","serif";color:#0A246A">
<a href="http://www.chasquinet.org" target="_blank">www.chasquinet.org</a></span><br>
Chair, NPOC, NCSG, ICANN, <a href="http://npoc.org/" target="_blank">http://npoc.org/</a><br>
O:+1 514 484 7824; M:+1 514 704 7824<br>
Skype: alain.berranger<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">AVIS DE CONFIDENTIALITÉ<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Ce courriel est confidentiel et est à l’usage exclusif du destinataire ci-dessus. Toute personne qui lit le présent message sans en être le destinataire, ou l’employé(e) ou la personne responsable de le remettre au destinataire, est par
les présentes avisée qu’il lui est strictement interdit de le diffuser, de le distribuer, de le modifier ou de le reproduire, en tout ou en partie . Si le destinataire ne peut être joint ou si ce document vous a été communiqué par erreur, veuillez nous en
informer sur le champ et détruire ce courriel et toute copie de celui-ci. Merci de votre coopération.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">CONFIDENTIALITY MESSAGE<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">This e-mail message is confidential and is intended for the exclusive use of the addressee. Please note that, should this message be read by anyone other than the addressee, his or her employee or the person responsible for forwarding it
to the addressee, it is strictly prohibited to disclose, distribute, modify or reproduce the contents of this message, in whole or in part. If the addressee cannot be reached or if you have received this e-mail in error, please notify us immediately and delete
this e-mail and destroy all copies. Thank you for your cooperation.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</blockquote>
</div>
</body>
</html>