ICANN/GNSO GNSO Email List Archives


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

[council] Guidelines for data collection requests relating to task force work

  • To: "Brian Darville" <BDARVILLE@xxxxxxxxx>, "Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>, "Jordyn A. Buchanan" <jbuchanan@xxxxxxxxxxxxxxx>
  • Subject: [council] Guidelines for data collection requests relating to task force work
  • From: "Bruce Tonkin" <Bruce.Tonkin@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 16 Jan 2004 18:24:15 +1100
  • Cc: "Barbara Roseman" <roseman@xxxxxxxxx>, "Suzanne Sene" <ssene@xxxxxxxxxxxx>, <pritz@xxxxxxxxx>, <swinehart@xxxxxxxxx>, <council@xxxxxxxxxxxxxx>, <Christopher.Wilkinson@xxxxxxxxxx>, <twomey@xxxxxxxxx>, "Elisabeth Porteneuve" <Elisabeth.Porteneuve@xxxxxxxxxxxx>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • Thread-index: AcPcAb5BdcG3Xc5YToaDBN8d1Xdf+g==
  • Thread-topic: Guidelines for data collection requests relating to task force work

Hello Brian, Jeff, and Jordyn,

As discussed today I suggest the following approach with respect to
addressing requests for data collection.

(1) Role of Advisory Committees

The Advisory Committees including the Governmental Advisory Committee,
Security and Stability Advisory Committee, Root Server Advisory
Committee, At-Large Advisory Committee are generally expected to review
proposed policy changes that affect their areas of expertise as part of
the public comment processes built into the GNSO policy Development
process.   These committees would not generally participate directly in
GNSO policy development, although it is recognised that members of the
At-Large Advisory Committee have been very helpful in supporting policy
development on behalf of individual Internet users.

In the case of WHOIS, some of these Advisory Committees are conducting
their own activities with respect to considering WHOIS issues, and it is
important, through the liaisons the GNSO has with each of these
committees, that the committees are kept informed of the work in the

(2) Requests for data

A highlight of the recent work on WHOIS policy development has been the
need to collect further data.

A task force should define what data/information needs to be collected,
and then use the personal networks of the task force members and
liaisons to ask individuals or organisations to respond to the data
request within the timeframe allocated by the task force.  The ICANN
Staff manager can also advise the relevant Advisory Committee liaisons,
the ccNSO and the ASO that such information is being sought.  The
relevant liaison can elect to pass on such requests as appropriate to
their members, and their members should respond directly to the task
force (rather than requiring a formal advisory committee or supporting
organisation response).

Given that there are several task forces working on WHOIS, I recommend
that the ICANN Staff Manager collate the various data collection
requests, and inform the Advisory Committees and the ccNSO of the
information being sought.  Advisory Committees, ccNSO, or other groups
(e.g CENTR) that are in the process of doing their own data collection
related to WHOIS, may be able to incorporate some of the questions into
their own surveys.

Each task force should ensure that it does not become reliant on the
data collection plans of other organisations (which may occur over much
longer time scales).  

While questions addressed directly to individuals or organisation is a
useful source of information, the ICANN Staff Manager and task force
members should also seek sources of information that has already been
collected and analysed, potentially over a prolonged period of time.

Bruce Tonkin

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