ICANN/GNSO GNSO Email List Archives

[council]

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

Re: [council] Version 2: Proposed motion regarding Personal Data that is collected and retained by registrars

I agree. We need to have some kind of proxy voting in place. Many of us are frequently on airplanes, in other meetings that can't be rescheduled, etc. and need some way for our views to be reflected in the council meeting - proxies are an easy way to do that. Is there even a rationale for why we currently don't allow proxy voting? Thank you. 

Robin


tony.ar.holmes@xxxxxx wrote:


I would like to support Norbert's request, we need to look at the use of
proxy voting again.
Tony 
-----Original Message-----
From: owner-council@xxxxxxxxxxxxxx [mailto:owner-council@xxxxxxxxxxxxxx]
On Behalf Of Norbert Klein
Sent: 19 July 2006 11:19
To: Bruce Tonkin
Cc: Council GNSO
Subject: Re: [council] Version 2: Proposed motion regarding Personal
Data that is collected and retained by registrars

Dear Council Colleagues,
dear Bruce,
dear Glen,
I have not been able to participate in the recent discussions for technical constraints (computer/network). At present, the heavy rainy season makes it difficult to maintain stable wireless and satellite connection ("rain degradation") I will try to be online on Thursday, but 

maybe it will not work for me.
All the more I would like to ask that the council can discuss again the possibility to create proxy vote facilities. 


Norbert

=

Bruce Tonkin wrote:

Hello All,

I have also improved this motion after input from Dan Halloran, Maria
Farrell, Denise Michael, and various members of the GNSO community!

Regards,
Bruce Tonkin


I propose the following new motion:

"The GNSO Council notes that, consistent with generally accepted

privacy

principles, Registrars are required under clause 3.7.7.4 of the
Registrar Accreditation Agreement to provide notice to each new or
renewed Registered Name Holder stating:

(i) The purposes for which any Personal Data collected from the
applicant are intended;

(ii) The intended recipients or categories of recipients of the data
(including the Registry Operator and others who will receive the data
from Registry Operator);

(iii) Which data are obligatory and which data, if any, are voluntary;
and

(iv) How the Registered Name Holder or data subject can access and, if
necessary, rectify the data held about them.

To further understand the range of purposes for which data is

intended,

the GNSO proposes the following steps:

(1) The ICANN staff will review a sample of registrar agreements with
Registered Name Holders to identify some of the purposes for which
registrars collect Personal Data in the course of registering a domain
name for their customers.

(2) The ICANN staff will review a sample of cctld registry or cctld
registrar agreements with registrants to identify some of the purposes
for which these organisations collect Personal Data from registrants.

(3) The ICANN staff will summarise the current material that has
resulted from WHOIS discussions since 2002 that document the current
uses of the data that is currently made public through the WHOIS
service.

(4) Based on the material produced in steps (1), (2) and (3) above,

the

Council will undertake a dialogue with the ICANN Advisory Committee's
such as the GAC, SSAC and ALAC regarding the purposes for collecting
Personal Data, and discuss whether any policy development is required

in

this area consistent with ICANN's mission and core values.

The dialogue should seek to examine and understand consumer

protection,

privacy/data protection and law enforcement perspectives."
<<< Chronological Index >>>    <<< Thread Index >>>