<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [gnso-thickwhois-dt] weekly status report
- To: "Drazek, Keith" <kdrazek@xxxxxxxxxxxx>
- Subject: Re: [gnso-thickwhois-dt] weekly status report
- From: Volker Greimann <vgreimann@xxxxxxxxxxxxxxx>
- Date: Mon, 24 Sep 2012 19:04:52 +0200
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Keith,<br>
<br>
I see your point, but I do not believe it to be as much of an
issue as you make of it. The registry in any thick whois TLD is
the central repository of all whois data, regardly of where it was
registered. The registrar is responsible to provide the data to
the registry. Verification can be assumed and performed by either.
In the new RAA, registrars will most likely assume some of the
responsibility, but the launch of .XXX has show this can also be
performed on a registry level. In fact, some ccTLDs such as .US
also perform routine validations on the registration requirements.<br>
<br>
On the other hand, we have now seen cases where a "thick registry"
has made modifications to the registration based on court orders
or other events, which were not always notified to the registrar,
i.e. left the registrar database out of synch with the registrar
database, yet these changes were authoritative as far as the
ownership of the domain is concerned. Whereas registrars must
always update the registry to effect a change of data in a thick
TLD. In other words, as the registry database is the last word on
the data, it should be the authoritative source.<br>
<br>
Best,<br>
<br>
Volker<br>
<br>
<br>
</div>
<blockquote
cite="mid:504F95D0035A264EBB1BFAABAA772B950D62E59C@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]-->
<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Tim
raises an important point, including the question of whether
registries or registrars are authoritative for Whois
data.<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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
have concerns about a registry being authoritative for Whois
data when it has no direct connection to the registrant. As
discussed on our last call, the registry receives Whois data
from the Registrar, not from the registrant. As such, the
registry has no way of independently
confirming/verifying/validating that the data is accurate. I
think this distinction becomes more of an issue if there’s a
future requirement for validation or verification of
registrant Whois data, as requested by the
GAC.<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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Ultimately,
having a Thick Whois database at the registry level only
centralizes the data…it doesn’t make it any more accurate,
validated, verified, etc. since registries simply accept
what is submitted by the registrars.<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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
understand that some of the existing thick registries may
already be authoritative for their TLD’s Whois data, so
perhaps we can benefit from their experience.<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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This
issue may or may not fit into the draft charter, but it’s
probably worth discussing further on our next
call.<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>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,
Keith<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>
<div>
<table class="MsoNormalTable" style="width:278.25pt"
border="0" cellpadding="0" cellspacing="0" width="371">
<tbody>
<tr>
<td colspan="2" style="padding:0in 0in 0in 0in">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><img
id="_x0000_i1026"
src="cid:part1.01080706.03070203@key-systems.net"
alt="Verisign" height="2" width="371"></span><span
style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:11.25pt 0in 15.0pt 0in">
<p class="MsoNormal" style="line-height:10.5pt"><b><span
style="font-size:9.0pt;font-family:"Helvetica","sans-serif";color:#006AAA">Keith
Drazek</span></b><span
style="font-size:8.5pt;font-family:"Helvetica","sans-serif";color:#6B6D71"><br>
Director of Policy<br>
<a class="moz-txt-link-abbreviated"
href="mailto:kdrazek@xxxxxxxxxxxx";>kdrazek@xxxxxxxxxxxx</a><br>
<br>
m: +1-571-377-9182<br>
21345 Ridgetop Circle Dulles, VA 20166<br>
<br>
<a moz-do-not-send="true"
href="http://www.verisigninc.com/";><span
style="font-size:9.0pt;color:#006AAA;text-decoration:none">VerisignInc.com</span></a>
<o:p></o:p></span></p>
</td>
<td style="padding:11.25pt 0in 0in 0in" valign="top">
<p class="MsoNormal"><!--[if gte vml 1]><v:shapetype
id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t"
path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">
<v:stroke joinstyle="miter" />
<v:formulas>
<v:f eqn="if lineDrawn pixelLineWidth 0" />
<v:f eqn="sum @0 1 0" />
<v:f eqn="sum 0 0 @1" />
<v:f eqn="prod @2 1 2" />
<v:f eqn="prod @3 21600 pixelWidth" />
<v:f eqn="prod @3 21600 pixelHeight" />
<v:f eqn="sum @0 0 1" />
<v:f eqn="prod @6 1 2" />
<v:f eqn="prod @7 21600 pixelWidth" />
<v:f eqn="sum @8 21600 0" />
<v:f eqn="prod @7 21600 pixelHeight" />
<v:f eqn="sum @10 21600 0" />
</v:formulas>
<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />
<o:lock v:ext="edit" aspectratio="t" />
</v:shapetype><v:shape id="Picture_x0020_2" o:spid="_x0000_s1026"
type="#_x0000_t75" alt="Verisign™"
style='position:absolute;margin-left:3.55pt;margin-top:0;width:54.75pt;height:48pt;z-index:1;visibility:visible;mso-wrap-style:square;mso-wrap-distance-left:0;mso-wrap-distance-top:0;mso-wrap-distance-right:0;mso-wrap-distance-bottom:0;mso-position-horizontal:right;mso-position-horizontal-relative:text;mso-position-vertical:absolute;mso-position-vertical-relative:line'
o:allowoverlap="f">
<v:imagedata
src="imap://vgreimann%40key-systems%2Enet@xxxxxxxxxxxxxxxxxxxx:993/fetch%3EUID%3E/INBOX%3E79681?header=quotebody&part=1.3&filename=image002.gif"
o:href="file:///C:\Users\kdrazek\AppData\Roaming\Microsoft\Signatures\logo.gif"
/>
<w:wrap type="square" anchory="line"/>
</v:shape><![endif]--><!--[if !vml]--><img
src="cid:part3.04030302.00070409@key-systems.net"
alt="Verisign™" v:shapes="Picture_x0020_2"
align="right" height="64" width="73"><!--[endif]--><span
style="font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p>
</td>
</tr>
</tbody>
</table>
<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"><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"">
<a class="moz-txt-link-abbreviated"
href="mailto:owner-gnso-thickwhois-dt@xxxxxxxxx";>owner-gnso-thickwhois-dt@xxxxxxxxx</a>
[<a class="moz-txt-link-freetext"
href="mailto:owner-gnso-thickwhois-dt@xxxxxxxxx";>mailto:owner-gnso-thickwhois-dt@xxxxxxxxx</a>]
<b>On Behalf Of </b>Tim Ruiz<br>
<b>Sent:</b> Monday, September 24, 2012 12:27 PM<br>
<b>To:</b> Mike O'Connor; <a class="moz-txt-link-abbreviated"
href="mailto:Gnso-thickwhois-dt@xxxxxxxxx";>Gnso-thickwhois-dt@xxxxxxxxx</a>
PDP DT<br>
<b>Subject:</b> RE: [gnso-thickwhois-dt] weekly status
report<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">Thanks
Mikey,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">Sorry
I haven't been able to make the calls, one thing or
another has come up. I think the current draft and
changes look good but I do have one
comment/concern.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">It
seems to assumes if all regitries are thick that
registrars will still be required to maintain a set of
WHOIS data themselves. However, if the registries are
all thick and authoritative for WHOIS data then I see no
reason why a registrar should continue to be required to
maintain a duplicate set of the data, especially since
it will also be escrowed by the registry. I would think
a number of registrars would find it useful and cost
effective to simply use a registry's authoritative data
instead of trying to maintain it themselves. And I can
easily see an effort by registrars to change the RAA
and/or policies to reflect that.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">So
I don't think the PDP group should assume that both
registrars and registries will continue to maintain the
data. It may be good to note that possibility. Or
alternatively, that may be a question they want to
consider. I don't think it would necessarily be out of
scope since it is tightly associated with whether all
registries are thick or not, but others may have a
different opinion.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">Best,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">Tim <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"> <o:p></o:p></span></p>
</div>
<blockquote style="border:none;border-left:solid blue
1.5pt;padding:0in 0in 0in
6.0pt;margin-left:6.0pt;margin-top:5.0pt;margin-bottom:5.0pt"
id="replyBlockquote">
<div id="wmQuoteWrapper">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">--------
Original Message --------<br>
Subject: [gnso-thickwhois-dt] weekly status report<br>
From: "Mike O'Connor" <<a moz-do-not-send="true"
href="mailto:mike@xxxxxxxxxx";>mike@xxxxxxxxxx</a>><br>
Date: Sat, September 22, 2012 10:03 am<br>
To: "<a moz-do-not-send="true"
href="mailto:Gnso-thickwhois-dt@xxxxxxxxx";>Gnso-thickwhois-dt@xxxxxxxxx</a>
PDP DT"<br>
<<a moz-do-not-send="true"
href="mailto:Gnso-thickwhois-dt@xxxxxxxxx";>Gnso-thickwhois-dt@xxxxxxxxx</a>><br>
<br>
hi all,<br>
<br>
here's the status report for this week. i *think*
we're wringing out the last issues in the draft. so
this would be a good time to take a look at the latest
version. what seems to be working well is to run your
ideas through the list so then we can work through
them on the call. here's a link to the draft i pushed
out after the last call.<br>
<br>
<a moz-do-not-send="true"
href="http://forum.icann.org/lists/gnso-thickwhois-dt/doc3QzSkLIUIQ.doc";>http://forum.icann.org/lists/gnso-thickwhois-dt/doc3QzSkLIUIQ.doc</a><br>
<br>
and here's the status report. i'm hoping we can get to
a draft we can push out for a consensus call by the
end of the meeting on Thursday.
<br>
<br>
thanks,<br>
<br>
mikey<br>
<br>
<o:p></o:p></span></p>
<div class="MsoNormal" style="text-align:center"
align="center"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black">
<hr align="center" size="2" width="100%">
</span></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:black"><br>
<br>
- - - - - - - - -<br>
phone 651-647-6109 <br>
fax 866-280-2356 <br>
web <a moz-do-not-send="true"
href="http://www.haven2.com";>http://www.haven2.com</a><br>
handle OConnorStP (ID for public places like Twitter,
Facebook, Google, etc.)<o:p></o:p></span></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
Mit freundlichen Grüßen,
Volker A. Greimann
- Rechtsabteilung -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated"
href="mailto:vgreimann@xxxxxxxxxxxxxxx";>vgreimann@xxxxxxxxxxxxxxx</a>
Web: <a class="moz-txt-link-abbreviated"
href="http://www.key-systems.net";>www.key-systems.net</a> / <a
class="moz-txt-link-abbreviated"
href="http://www.RRPproxy.net";>www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated"
href="http://www.domaindiscount24.com";>www.domaindiscount24.com</a> / <a
class="moz-txt-link-abbreviated"
href="http://www.BrandShelter.com";>www.BrandShelter.com</a>
Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
<a class="moz-txt-link-abbreviated"
href="http://www.key-systems.net/facebook";>www.key-systems.net/facebook</a>
<a class="moz-txt-link-abbreviated"
href="http://www.twitter.com/key_systems";>www.twitter.com/key_systems</a>
Geschäftsführer: Alexander Siffrin
Handelsregister Nr.: HR B 18835 - Saarbruecken
Umsatzsteuer ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated"
href="http://www.keydrive.lu";>www.keydrive.lu</a>
Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen
Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder
Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht
nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder
telefonisch in Verbindung zu setzen.
--------------------------------------------
Should you have any further questions, please do not hesitate to contact us.
Best regards,
Volker A. Greimann
- legal department -
Key-Systems GmbH
Im Oberen Werk 1
66386 St. Ingbert
Tel.: +49 (0) 6894 - 9396 901
Fax.: +49 (0) 6894 - 9396 851
Email: <a class="moz-txt-link-abbreviated"
href="mailto:vgreimann@xxxxxxxxxxxxxxx";>vgreimann@xxxxxxxxxxxxxxx</a>
Web: <a class="moz-txt-link-abbreviated"
href="http://www.key-systems.net";>www.key-systems.net</a> / <a
class="moz-txt-link-abbreviated"
href="http://www.RRPproxy.net";>www.RRPproxy.net</a>
<a class="moz-txt-link-abbreviated"
href="http://www.domaindiscount24.com";>www.domaindiscount24.com</a> / <a
class="moz-txt-link-abbreviated"
href="http://www.BrandShelter.com";>www.BrandShelter.com</a>
Follow us on Twitter or join our fan community on Facebook and stay updated:
<a class="moz-txt-link-abbreviated"
href="http://www.key-systems.net/facebook";>www.key-systems.net/facebook</a>
<a class="moz-txt-link-abbreviated"
href="http://www.twitter.com/key_systems";>www.twitter.com/key_systems</a>
CEO: Alexander Siffrin
Registration No.: HR B 18835 - Saarbruecken
V.A.T. ID.: DE211006534
Member of the KEYDRIVE GROUP
<a class="moz-txt-link-abbreviated"
href="http://www.keydrive.lu";>www.keydrive.lu</a>
This e-mail and its attachments is intended only for the person to whom it is
addressed. Furthermore it is not permitted to publish any content of this
email. You must not use, disclose, copy, print or rely on this e-mail. If an
addressing or transmission error has misdirected this e-mail, kindly notify the
author by replying to this e-mail or contacting us by telephone.
</pre>
</body>
</html>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|