ICANN ICANN Email List Archives

[gnso-dow123]


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-dow123] Proposed revision #1

  • To: Whois TF mailing list <gnso-dow123@xxxxxxxxxxxxxx>, "Jordyn A. Buchanan" <jordyn@xxxxxxxxxxxxx>, Thomas Keller <tom@xxxxxxxxxx>
  • Subject: RE: [gnso-dow123] Proposed revision #1
  • From: Tim Ruiz <tim@xxxxxxxxxxx>
  • Date: Wed, 31 Aug 2005 05:12:54 -0700

<div>Believe it or not, English is my first language.</div>
<div>&nbsp;</div>
<div>I have no vote, but I agree with Tom.</div>
<div>&nbsp;</div>
<div>Tim<BR></div>
<BLOCKQUOTE style="PADDING-LEFT: 8px; MARGIN-LEFT: 8px; BORDER-LEFT:
blue 2px solid"><BR>-------- Original Message --------<BR>Subject: RE:
[gnso-dow123] Proposed revision #1<BR>From: Tim Ruiz
&lt;tim@xxxxxxxxxxx&gt;<BR>Date: Wed, August 31, 2005 7:06 am<BR>To:
Thomas Keller &lt;tom@xxxxxxxxxx&gt;<BR>Cc: Whois TF mailing list
&lt;gnso-dow123@xxxxxxxxxxxxxx&gt;, "Jordyn A.<BR>Buchanan"
&lt;jordyn@xxxxxxxxxxxxx&gt;<BR><BR>I have not vote, but I agree with
Tom. <BR><BR>Tim<BR><BR>-------- Original Message --------<BR>Subject:
Re: [gnso-dow123] Proposed revision #1<BR>From: Thomas Keller
&lt;tom@xxxxxxxxxx&gt;<BR>Date: Wed, August 31, 2005 3:31 am<BR>To:
"Jordyn A. Buchanan" &lt;jordyn@xxxxxxxxxxxxx&gt;<BR>Cc: Whois TF
mailing list
&lt;gnso-dow123@xxxxxxxxxxxxxx&gt;<BR><BR>Jordyn,<BR><BR>thanks for all
the work. Having considered the proposed changes I would<BR>suggest that
we leave the recommendation in its original wording and<BR>simply add
the changes as questions for the public commenting period<BR>and
finalize the preliminary report.<BR><BR>tom<BR><BR>Am 30.08.2005
schrieb Jordyn A. Buchanan:<BR>&gt; This is the first in a series of
e-mails to take up the revisions &nbsp;<BR>&gt; that have been
suggested by various constituencies. &nbsp;We discussed &nbsp;<BR>&gt;
this first change at length today.<BR>&gt; <BR>&gt; I think we are
closest to agreement on language that makes exceptions &nbsp;<BR>&gt;
applicable to all registrars that the conflict applies to (as opposed
&nbsp;<BR>&gt; to all registrars, or to just the registrar making the
request). &nbsp; <BR>&gt; Here's some specific text to discuss.
&nbsp;Paragraph 2 (c) of the policy &nbsp;<BR>&gt; recommendation would
be changed to the following (insertion marked in &nbsp;<BR>&gt; bold
italics):<BR>&gt; <BR>&gt; c. &nbsp;Providing a mechanism for the
recognition, if appropriate, in &nbsp; <BR>&gt; circumstances where the
conflict cannot be otherwise resolved, of an &nbsp;<BR>&gt; exception to
contractual obligations to those registries/registrars &nbsp;<BR>&gt; to
which the specific conflict applies with regard to collection,
&nbsp;<BR>&gt; display and distribution of personally identifiable data
via Whois; and<BR>&gt; <BR>&gt; Similarly, sub-paragraph iv of Step
Three would be replaced with the &nbsp;<BR>&gt; following (changes
marked in bold italics again):<BR>&gt; <BR>&gt; Recommendation of how
the issue should be resolved, which may include &nbsp;<BR>&gt; whether
ICANN should provide an exception for those registrars/ <BR>&gt;
registries to which the specific conflict applies from one or more
&nbsp;<BR>&gt; identified WHOIS contractual provisions. The report
should include a &nbsp;<BR>&gt; detailed justification of its
recommendation, including the &nbsp;<BR>&gt; anticipated impact on the
operational stability, reliability, &nbsp;<BR>&gt; security, or global
interoperability of the Internet's unique &nbsp;<BR>&gt; identifier
systems if the recommendation were to be approved or denied.<BR>&gt;
<BR><BR>Gruss,<BR><BR>tom<BR><BR>(__) &nbsp; &nbsp; &nbsp;
&nbsp;<BR>(OO)_____ &nbsp;<BR>(oo) &nbsp; &nbsp;/|\ A cow is not
entirely full of<BR>| |--/ | * &nbsp; &nbsp;milk some of it is
hamburger!<BR>w w w &nbsp;w </BLOCKQUOTE>




<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy