ICANN/GNSO GNSO Email List Archives


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

[registrars] RE: Call for Constituency statements on Whois tf 1/2 recommendations

  • To: registrars@xxxxxxxx
  • Subject: [registrars] RE: Call for Constituency statements on Whois tf 1/2 recommendations
  • From: Tim Ruiz <tim@xxxxxxxxxxx>
  • Date: Thu, 23 Dec 2004 05:47:44 -0700
  • Reply-to: Tim Ruiz <tim@xxxxxxxxxxx>
  • Sender: owner-registrars@xxxxxxxxxxxxxx

The expectation that this can be done in time to include in a report by
Jan 31 is optimistic to say the least. The RC bylaws require a 14 day
discussion period *after* a motion is put forward to accept a
position/statement. Then there is a minimum 7 day voting period. This
is a holiday weekend for most, next weekend is a holiday weekend for
most. Throw in some time to actually discuss and draft a position and
some time for the TF to incorporate them in the report and you pretty
much have an impossible task. If it is accomplished, I'm concerned that
it won't have allowed for sufficient input from all interested members
in the RC.

Policy positions are not something we should attempt to fasttrack. This
deadline needs to be moved to something realistic, probably at least

-------- Original Message --------
Subject: [registrars] [dow1-2tf] Call for Constituency statements on
Whois tf 1/2 recommendations (fwd)
From: "Thomas Keller" <tom@xxxxxxxxxx>
Date: Thu, December 23, 2004 3:27 am
To: registrars@xxxxxxxx

Hello all,

please find below the call for constituency statements in regard to the
recommendations to "improve notification and consent for the use of
contact data in the Whois system" of Taskforce 1/2. You can find the
recommendations at:


The taskforce will use the constituency statements to compose a
report including the various statements as well as a summary on how the
constituencies would be impacted by this recommendations.

As I heard at the Cape Town meeting there are several concerns around
this recommendations and now is the right time to step up and raise 
them so that Paul Stahura and I, which are the primary reps on this TF,
can compile them to a report which can be put to a vote. 

Since I'm unsure about the correct procedure of voting I would suggest 
that while we start the debate on this issue our secretary Bob Conelly
should provide us with a shedule on how to proceed to meet the goal
of having a statement ready at January 31.

If you have questions regarding the TF work please don't hesitate to
direct them to Paul or me directly.

I wish you all a merry christmas and a great new year.



----- Forwarded message from GNSO SECRETARIAT
<gnso.secretariat@xxxxxxxxxxxxxx> -----

Reply-To: gnso.secretariat@xxxxxxxxxxxxxx
From: GNSO SECRETARIAT <gnso.secretariat@xxxxxxxxxxxxxx>
To: 12DOW <dow1-2tf@xxxxxxxxxxxxxx>
Subject: [dow1-2tf] Call for Constituency statements on Whois tf 1/2
Date: Wed, 22 Dec 2004 16:34:31 +0100

[To: liaison6c[at]gnso.icann.org; council[at]gnso.icann.org]

Constituency statements should be submitted on or before MONDAY, JANUARY

Call for the submission of constituency statements on the Whois task
Recommendations relating to improving notification and consent for the
contact data in the Whois system.

1. Registrars must ensure that disclosures regarding availability and
third-party access to personal data associated with domain names
actually be
presented to registrants during the registration process.  Linking to an
external web page is not sufficient.

2. Registrars must ensure that these disclosures are set aside from
provisions of the registration agreement if they are presented to
registrants together with that agreement.  Alternatively, registrars may
present data access disclosures separate from the registration
The wording of the notice provided by registrars should, to the extent
feasible, be uniform.

3. Registrars must obtain a separate acknowledgement from registrars
they have read and understand these disclosures.  This provision does
affect registrars' existing obligations to obtain registrant consent to
use of their contact information in the WHOIS system.

The constituency statements should ideally be consistent with the ICANN
bylaws -  GNSO Policy-Development Process.

Section 7, d. Collection of Information.
1. Constituency Statements.
The Representatives will each be responsible for soliciting the position
their constituencies, at a minimum, and other comments as each
Representative deems appropriate, regarding the issue under
This position and other comments, as applicable, should be submitted in
formal statement to the task force chair (each, a "Constituency
within thirty-five (35) calendar days after initiation of the PDP. Every
Constituency Statement shall include at least the following:

(i) If a Supermajority Vote was reached, a clear statement of the
constituency's position on the issue;

(ii) If a Supermajority Vote was not reached, a clear statement of all
positions espoused by constituency members;

(iii) A clear statement of how the constituency arrived at its
Specifically, the statement should detail specific constituency
teleconferences, or other means of deliberating an issue, and a list of
members who participated or otherwise submitted their views;

(iv) An analysis of how the issue would affect the constituency,
any financial impact on the constituency; and

(v) An analysis of the period of time that would likely be necessary to
implement the policy.

GNSO Secretariat
Glen de Saint Géry
GNSO Secretariat

----- End forwarded message -----



(oo)    /|\ A cow is not entirely full of
 | |--/ | *    milk some of it is hamburger!
 w w w  w 

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