July 2004 - council - lists.icann.org

Final Dot Net Subcommittee report
by gnso.icann July 30, 2004

July 30, 2004

[To : council[at]gnso.icann.org] Reminder : GNSO Council teleconference on Thursday 5 August, 12:00 UTC to vote on the Final Dot Net Subcommittee report Please find the report here: http://www.gnso.icann.org/issues/dotnet/dotnet-reportv9.pdf If you cannot be present, please let me know who will hold your proxy. Thank you very much. GNSO Secretariat

1 0

RE: [council] Draft Agenda for Council meeting Thursday 5 August 2004
by Niklas_Lagergren＠mpaa.org July 28, 2004

July 28, 2004

Dear Glen et al - I will not be able to join our meeting on August 5th. My proxy goes to Lucy Nichols. Nik > -----Original Message----- > From: Bruce Tonkin [mailto:Bruce.Tonkin@melbourneit.com.au] > Sent: mercredi 28 juillet 2004 9:19 > To: council(a)gnso.icann.org > Cc: gnso.secretariat(a)gnso.icann.org; roseman(a)icann.org; Paul Verhoef; > Kurt Pritz; Jordyn A. Buchanan; jeff.neuman(a)Neustar.us; > BDARVILLE(a)oblon.com > Subject: [council] Draft Agenda for Council meeting Thursday 5 August > 2004 > > > Hello All, > > The focus of this meeting will be to discuss and agree on the criteria > for designating a successor for the .net registry. This issue will be > put to a formal vote. Please ensure that if you are not able > to attend > the meeting, that you appoint a proxy (via email to the Council list). > > Regards, > Bruce Tonkin > > > Agenda for Council meeting Thursday 5 August 2004 > > 12:00 UTC (10pm Melbourne, 1pm London, 8am Washington, 5am > Los Angeles) > > Item 1: Approval of minutes of > 16 June 2004 > http://www.gnso.icann.org/mailing-lists/archives/council/msg00514.html > 12 July 2004 > http://www.gnso.icann.org/mailing-lists/archives/council/msg00519.html > > > Item 2: For decision: Criteria for designating a successor > for the .net > registry > Version 9 (21 July 2004): > http://www.gnso.icann.org/issues/dotnet/dotnet-reportv9.pdf > > > Item 3: Any other business >

1 0

Summary of decisions around WHOIS from the meetings in Kuala Lumpur
by Bruce Tonkin July 28, 2004

July 28, 2004

Hello All, The GNSO Council decided in its meeting in Kuala Lumpur to combine Task force 1 and 2, and continue with task force 3. The current titles of the 3 task forces are: TF1: Restricting access to WHOIS data for marketing purposes TF2: Review of data collected and displayed TF3: Improving Accuracy of collected data Based on the current recommendations in the TF1/2 reports, I recommend the combined TF1 and TF2 be called: "Improving informed consent to the publication of contact data and improving controls for 3rd party access to published contact data" Earlier in the week there was a joint meeting of members of the 3 task forces and the members of the GNSO Council. This is what I understand was agreed as next steps for TF1/2 and TF3: - prioritise the recommendations that have the best consensus, provide a tangible improvement for the Internet community, and are likely to be implementable within the short term (months rather than years) - start with the highest priority recommendations and design a reference implementation (This will provide evidence that the recommendation is implementable, and also provide more information to assist members of the task forces and Council to determine if the recommendation provides a tangible improvement for the Internet Community and thus is appropriate to recommend to the ICANN Board. Note a new consensus recommendation is likely to be a new contractually binding obligation on registries, registrars or registrants. The reference implementation may also help determine how the new policy recommendation should be worded - perhaps adding additional detail to an additional ICANN contractual obligation) - for each recommendation that is implementable determine the cost impacts on the various parties represented within the GNSO (ie business users, non-commercial users, ISP users, registries, registrars, intellectual property owners) - where there are cost implications, determine how those costs should be recovered - for each recommendation determine how the associated improvements can be measured, so that the outcomes of the policy change may be reviewed and further refined >From the task force reports, and the discussions in Kuala Lumpur, examples of priority recommendations that could be considered by the task forces for further analysis include: - more conspicuous notice to registrants of the WHOIS obligations associated with the registrant-registrar agreement - ie ensure that registrants provide "informed consent" to the publication of contact data. A reference implementation could be provided to indicate how a registrant should consent in a typical online registration process. The task force could consider wording a new policy recommendation (obligation for registrars) specifying what "conspicuous notice" means. - additional tiers of access - e.g public access tier, and authenticated access tier (where the 3rd party requesting the data is identifiable) - determine a reference implementation that specifies the data elements available in each tier, and specifies how 3rd parties would be identified and possibly accredited. Note that it is current WHOIS policy that the data should not be used for marketing purposes. This applies to either tier, but the second tier may assist in tracking and enforcement of this existing policy. [NOTE: If tiered access is found to be implementable and found to give a benefit, then many further levels of enhancements are possible, but I urge the task force to consider the simplest implementation first - measure its impact - and then consider further enhancements. The aim should be to make tangible progress.] - improved measurement by ICANN of compliance by registrars and registrants to the existing WHOIS contractual obligations - need to be explicit about what the ICANN staff are being asked to do, and then get an assessment from ICANN staff on the cost of implementing the recommendation and whether it is within the current ICANN budget or would require further funding - improved complaints handling processes - currently complaints about WHOIS accuracy can be either lodged centrally or to each registrar - registrars are required to use "reasonable" efforts to investigate a complaint. The task force may consider creating a reference implementation for what is reasonable (which could include reporting of outcomes to ICANN), and determine whether a new policy recommendation should provide a more specific refinement to the current registrar obligation. Please let me know if I have missed any important points or if you disagree with my interpretation. Regards, Bruce Tonkin

1 0

Draft Agenda for Council meeting Thursday 5 August 2004
by Bruce Tonkin July 28, 2004

July 28, 2004

Hello All, The focus of this meeting will be to discuss and agree on the criteria for designating a successor for the .net registry. This issue will be put to a formal vote. Please ensure that if you are not able to attend the meeting, that you appoint a proxy (via email to the Council list). Regards, Bruce Tonkin Agenda for Council meeting Thursday 5 August 2004 12:00 UTC (10pm Melbourne, 1pm London, 8am Washington, 5am Los Angeles) Item 1: Approval of minutes of 16 June 2004 http://www.gnso.icann.org/mailing-lists/archives/council/msg00514.html 12 July 2004 http://www.gnso.icann.org/mailing-lists/archives/council/msg00519.html Item 2: For decision: Criteria for designating a successor for the .net registry Version 9 (21 July 2004): http://www.gnso.icann.org/issues/dotnet/dotnet-reportv9.pdf Item 3: Any other business

1 0

Re: [council] Revised Report on Designating a Successor Operator for the .net Registry (21 July)
by Amadeu Abril i Abril July 22, 2004

July 22, 2004

Thanks Philip. I saw those changes, but I was unsure whether any other minor thing had also been refined. Amadeu

1 0

Revised Report on Designating a Successor Operator for the .net Registry (21 July)
by gnso.icann July 22, 2004

July 22, 2004

[To : council[at]gnso.icann.org ;liaison6c[at]gnso.icann.org] [To : ga[at]gnso.icann.org; announce[at]gnso.icann.org] Please find the Final Revised GNSO Report on Designating a Successor Operator for the .net Registry (PDF 21 July) http://www.gnso.icann.org/issues/dotnet/dotnet-reportv9.pdf GNSO Secretariat

2 1

GNSO CounciL KL meeting captioning July 20
by gnso.icann July 21, 2004

July 21, 2004

[To : council[at]gnso.icann.org ;liaison6c[at]gnso.icann.org] [To : ga[at]gnso.icann.org; announce[at]gnso.icann.org] The following is the output of the real-time captioning taken during the GNSO Council Meeting held on 20 July in Kuala Lumpur, Malaysia <http://www.icann.org/meetings/kualalumpur/captioning-gnso-council-20jul 04.htm> http://www.icann.org/meetings/kualalumpur/captioning-gnso-council-20jul0 4.htm Note: Although the captioning output is largely accurate, in some cases it is incomplete or inaccurate due to inaudible passages or transcription errors. It is posted as an aid to understanding the proceedings at the session, but should not be treated as an authoritative record. GNSO Secretariat

1 0

TR : pppresentations at GNSO Council
by gnso.icann July 20, 2004

July 20, 2004

My pleasure. Here's the presentation. [To <mailto:council@gnso.icann.org> council(a)gnso.icann.org ] Please find Steve Crockers presentation on the Wild Card issue and DNSSEC to the GNSO Council meeting in Kuala Lumpur on July 20, 2004. Thank you. Glen de Saint Géry GNSO Secretariat

1 0

RE: GNSO Council meeting Tuesday 20 July
by Grant Forsyth July 20, 2004

July 20, 2004

Good afternoon fellow Councillors I am trying to dial into the Council meeting but am not able to connect as, according to the recorded message, "the conference call is already full" If there is a way around this, please call me on my mobile and let me know how to rectify the problem Thanks PS My mobile number is +64 29 912 5759 Grant Forsyth Manager Industry & Regulatory Affairs TelstraClear Cnr Taharoto & Northcote Roads Private Bag 92143 AUCKLAND ph +64 9 912 5759 fx + 64 9 912 4077 Mb 029 912 5759 -----Original Message----- From: gnso.icann [mailto:gnso.secretariat@gnso.icann.org] Sent: Tuesday, 20 July, 2004 12:08 To: Grant Forsyth Subject: GNSO Council meeting Tuesday 20 July Hi Grant ! Miss you ! Really thought that you would be able to hop over as it is not so far ! Please forgive me for not sending the telephone dial in! It is the same system as the GNSO teleconfs. The dial in is: Scheduled Conference Date: Tuesday, July 20, 2004 Scheduled Start Time: Auckland, New Zealand UTC+12+0DST 18:00 ( 6:00 pm) Scheduled End Time: 2 hours later Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Participant Access Code: 35790 If you cannot participate, please give your proxy to someone and please let me know! Thanks so much! Glen

1 0

RE: [council] ICANN Staff opportunities
by Alick Wilson July 20, 2004

July 20, 2004

Colleagues, my comments apply to the first two of the three positions advertised (GNSO Policy Support Officer and Senior Officer Policy Support Coordination), not to the third. Alick -----Original Message----- From: Alick Wilson [mailto:alick.wilson@xendra.co.nz] Sent: Tuesday, 20 July 2004 12:15 a.m. To: 'gnso.icann'; 'council' Subject: RE: [council] ICANN Staff opportunities Colleagues Given the importance to GNSO Council of these staff positions, I think it is essential that all applicants short listed by ICANN management be interviewed by the Chairman of Council and one other member of council (preferably one who is professionally experienced in the area of public policy). Also, can we confirm that a wide enough search and/or wide enough advertising is being undertaken to ensure that only well suited candidates are short listed? Alick Wilson -----Original Message----- From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of gnso.icann Sent: Monday, 19 July 2004 12:03 p.m. To: 'council' Subject: [council] ICANN Staff opportunities [To : council[at]gnso.icann.org; liaison6c[at]gnso.icann.org] [To : ga[at]gnso.icann.org; announce[at]gnso.icann.org] Please find the recently published ICANN Staff Opportunities at: <http://www.icann.org/general/jobs.htm> http://www.icann.org/general/jobs.htm <http://www.icann.org/general/jobs.htm#GNSOPolicySupportOfficer> http://www.icann.org/general/jobs.htm#GNSOPolicySupportOfficer GNSO Policy Support Officer The Internet Corporation for Assigned Names and Numbers (ICANN) has an immediate job opening for a GNSO Policy Support Officer. The key purpose of this role is to support the GNSO Council in the development or updating of technical policies related to generic top-level domains. Support tasks include background research, data gathering and analysis, and drafting of reports under guidance of the GNSO Council. A full position description, including key area of responsibities, skills, experience, knowledge and qualifications can be found at < <http://www.icann.org/general/jobs/GNSO-policy-support-officer.htm> http://www.icann.org/general/jobs/GNSO-policy-support-officer.htm>. Please submit your resume and cover letter via email to our staff at <mailto:opportunities@icann.org> opportunities(a)icann.org. Senior Officer Policy Support Coordination The Internet Corporation for Assigned Names and Numbers (ICANN) has an immediate job opening for a Senior Officer Policy Support Coordinator. The key purpose of this role is to support the GNSO Council in the development and updating of technical policies related to generic top-level domains and to facilitate co-ordination of policy processes between all of ICANN's Supporting Organisations and Advisory Committees. A full position description, including key area of responsibities, skills, experience, knowledge and qualifications can be found at < <http://www.icann.org/general/jobs/senior-officer-policy-support-coordin ation.htm> http://www.icann.org/general/jobs/senior-officer-policy-support-coordina tion.htm>. Please submit your resume and cover letter via email to our staff at <mailto:opportunities@icann.org> opportunities(a)icann.org. _____ Policy Support Officer The Internet Corporation for Assigned Names and Numbers (ICANN) has an immediate job opening for a Policy Support Officer. The key purpose of this role is to analyse technological, economic and legal developments of importance to ICANN's policy development processes. A full position description, including key area of responsibities, skills, experience, knowledge and qualifications can be found at < <http://www.icann.org/general/jobs/policy-support-officer.htm> http://www.icann.org/general/jobs/policy-support-officer.htm>. Please submit your resume and cover letter via email to our staff at <mailto:opportunities@icann.org> opportunities(a)icann.org. GNSO Secretariat

1 0