ICANN/DNSO
DNSO Mailling lists archives

[registrars]


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

[registrars] Regarding Tom Keller nomination to the GNSO WHOIS privacy steering group

  • To: <registrars@dnso.org>
  • Subject: [registrars] Regarding Tom Keller nomination to the GNSO WHOIS privacy steering group
  • From: "Bruce Tonkin" <Bruce.Tonkin@melbourneit.com.au>
  • Date: Mon, 9 Jun 2003 10:23:34 +1000
  • Sender: owner-registrars@dnso.org
  • Thread-Index: AcMsWMBsSKZ/qycxQx67Ooe90YhXRgBxHu/g
  • Thread-Topic: Regarding Tom Keller nomination to the GNSO WHOIS privacy steering group

I second the nomination.

Regards,
Bruce Tonkin
Member of the registrars constituency

> -----Original Message-----
> From: Paul Westley [mailto:paul@internetters.co.uk] 
> Sent: Saturday, 7 June 2003 4:24 AM
> To: Bruce Tonkin
> Cc: registrars@dnso.org; Tom Keller; Rick Wesson
> Subject: Re: [registrars] Representation on the GNSO WHOIS 
> privacy steering group
> 
> 
> Hello All,
> 
> I would like to nominate Tom Keller of Schlund as one of our 
> representatives on the GNSO WHOIS privacy steering group. As 
> a European and 
> someone who is very experienced in domain name issues and 
> well versed in 
> the European data protection regulations, Tom is ideally 
> suited to provide 
> a balanced view of the WHOIS privacy issue. He has been active in the 
> Registrars' Constituency for a number of years and with his 
> current GNSO 
> membership, I can highly recommend him for this role.
> 
> Paul Westley
> Internetters
> 
> At 09:00 06/06/03, Bruce Tonkin wrote:
> >Hello All,
> >
> >The GNSO Council has requested that each constituency 
> nominate one or 
> >two representatives to the GNSO WHOIS privacy steering group.  Note 
> >this steering group is not responsible for policy development.  Its 
> >role is to take the large number of issues of the ICANN 
> Staff Managers 
> >report on Privacy and develop terms of reference for one or 
> more task 
> >forces to carry out policy development.  These terms of 
> reference will 
> >need to be approved by the GNSO Council before policy 
> development can 
> >take place.
> >
> >The preference is to appoint the representatives prior to 
> the Montreal 
> >meeting.
> >
> >Given that the representatives will not be "elected 
> officers" under the 
> >new registrar by-laws, I assume we can have a fast track process for 
> >appointment.  Remember that the steering group does not 
> itself develop 
> >or approve policy.
> >
> >I recommend a 7 day nomination period and a 7 day voting period.
> >
> >Regards,
> >Bruce Tonkin
> >Registrars Rep on the GNSO Council
> >
> >
> >
> >-----Original Message-----
> >From: Bruce Tonkin
> >Sent: Friday, 6 June 2003 5:29 PM
> >To: council@dnso.org
> >Subject: [council] WHOIS Privacy steering group
> >
> >
> >Hello All,
> >
> >Just a reminder that all constituencies should appoint one or two 
> >members to the WHOIS privacy steering group prior to the Montreal 
> >meeting.  It is probably preferable if those members will be 
> attending 
> >the Montreal meeting to gain the most benefit from the public forum, 
> >and the opportunity for the steering group to meet in-person at 
> >Montreal.
> >
> >Please inform the GNSO Secretariat of the appointments so that a 
> >mailing list can be set up.
> >
> >The ALAC and the GAC may appoint one or two (non-voting) liaisons to 
> >the Steering Group.  The ccNSO would also be welcome to nominate an 
> >informal liaison also.
> >
> >The objective of the steering group is to:
> >- examine the Staff Manager's report on WHOIS Privacy
> >- review the factual presentations of the ICANN public forum 
> on WHOIS 
> >in Montreal
> >- develop recommendations, for the GNSO Council to approve, 
> to form a 
> >small number (e.g less than 5) of Task Forces to carry out 
> the policy 
> >development process on the major issues identified in the Staff 
> >manager's report (it should be possible to group some of the related 
> >issues for examination within a single task force)
> >- the recommendations should incorporate for each task force 
> a terms of 
> >reference in accordance with the ICANN bylaws (Annex A, 
> Section 7(b)):
> >
> >" Such Charter will include:
> >
> >1. the issue to be addressed by the task force, as such issue was 
> >articulated for the vote before the Council that commenced the PDP;
> >
> >2. the specific timeline that the task force must adhere to, as set 
> >forth below, unless the Board determines that there is a compelling 
> >reason to extend the timeline; and
> >
> >3. any specific instructions from the Council for the task force, 
> >including whether or not the task force should solicit the advice of 
> >outside advisors on the issue."
> >
> >- if the steering group recommends more than two task forces 
> be created 
> >it should recommend to the GNSO Council an order in which the task 
> >force work should be done, and an approximate timeframe for 
> when each 
> >task force will commence and finish
> >
> >Council members and Steering Group members might like to review the 
> >IETF standard RFC2418 on IETF Working Group Guidelines and 
> Procedures 
> >(http://www.ietf.org/rfc/rfc2418.txt).  The standard documents best 
> >practice within the IETF in forming working groups and defining 
> >charters. Section 2.1 (criteria for forming a working group) and 
> >Section 2.2
> >(Charter) are particularly relevant.
> >
> >Regards,
> >Bruce Tonkin
> >GNSO Council Chair
> 
> 


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