July 2004 - council - lists.icann.org

ICANN Staff opportunities
by gnso.icann 19 Jul '04

19 Jul '04

[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

2 1

RE: Summary of meeting - Sunday morning 18 July 2004 in Kuala Lumpur to discuss ICANN staff/GNSO interaction
by Cade,Marilyn S - LGCRP 18 Jul '04

18 Jul '04

Dear colleagues Thanks, Bruce, for your notes. I would like to just add a couple of thoughts related to how I view the role of Council, and that we did briefly touch on. Council has really a management role of the GNSO, as well as the critical policy development role. As one of the three SOs of ICANN, it is critical that the gNSO/via its Council, have an ongoing collaboration with the ICANN staff overall. We did also briefly discuss the need for Council to have access to legal advise and the SSAC, in particular, as key resources, given the development and implementation of consensus policy is an absolutely critical element of any changes in gNSO policy. I believe those concepts were supported by all attendees at the a.m. meeting. We should all really consider the meeting this a.m., as the beginning of an ongoing collaboration and dialogue to ensure Council's success, and therefore its contribution to ICANN's success. In Council's contribution to management of the GNSO issues overall, there seem to be a number of items we need to discuss at Council level, such as the representation topic; the liaison relationships with the other two SOs; interaction with the Advisory Committees, including the GAC, etc. In Council, we should begin to establish time to deal with our overall role. -----Original Message----- From: Bruce Tonkin [mailto:Bruce.Tonkin@melbourneit.com.au] Sent: Sunday, July 18, 2004 6:09 AM To: Philip Sheppard; paul.verhoef(a)icann.org; Kurt Pritz; twomey(a)icann.org; Neuman, Jeff; Cade,Marilyn S - LGCRP; kstubbs(a)afilias.info; Ross Wm. Rader Cc: council(a)gnso.icann.org Subject: Summary of meeting - Sunday morning 18 July 2004 in Kuala Lumpur to discuss ICANN staff/GNSO interaction Hello All, Here are my notes from the meeting this morning. There were three main topics discussed: - policy development process - end-to-end project management to deliver outcomes to the ICANN community - ICANN staff resource management (1) Policy development process A document needs to be created as a manual for participants in the policy process. Chairs of task forces or Council should ideally have experience within the GNSO policy development process prior to becoming chairs. The role of a task force or council member is to work as a member of the team to create a new consensus policy. The member should bring their expertise from their relevant constituency, but should work to understand the positions of the other constituencies and identify compromises that lead to an overall improvement for the ICANN community as-a-whole (rather than just the specific constituency). The overall duty of a task force or Council member is to the ICANN community as-a-whole. The role of the chair is to manage the policy development process and ensure that all members of the committee can contribute using their particular skills and expertise. Currently there is a heacvy reliance on chairs to do much of the editing of reports and analysis of public comments or constituency positions. The aim with the additonal ICANN budget is to reduce the reliance on the chairs, and encourage people expeirneced in the GNSO policy process to take on the role of chair. The role of the staff support person is as described in: http://www.icann.org/general/jobs/GNSO-policy-support-officer.htm Ie - Liaise with the Chair and members of the GNSO Council to conduct background research, data gathering and data analysis of current issues of importance to the Council - Assist with the formation of a Task Force or Sub-Committee and provide guidance to those participating in the policy development processes on relevant steps and timelines (as set out in the bylaws) - As part of the policy development processes, assist the GNSO Council and eventual Task Forces or Sub-committees in the management of their tasks, drafting and producing reports, posting and evaluating public comments, as well as related activities, such as coordination and incorporation of reports from outside advisors - Attend meetings of the Council, Task Forces and/or Sub-committees (mostly by teleconference and including outside office hours) - Provide other assistance to the GNSO Council as may be needed to ensure the smooth running of the policy processes - Where relevant, prepare reports and other materials to the ICANN Board The meeting noted that it would be useful for staff support personnel to have a thorough understanding og the ICANN bylaws with respect to policy development, and assist the chair with the process steps necessary to comply with the policy development process. Note although the staff support person is intended to assist in the editing of reports, members must work to contribute the raw material that allows the report to be created using their specific areas of expertise. A report cannot be created in a vacuum. (2) Project management The ICANN community currently has 3 policies in the implementation phase that were approved early in 2003: - transfers - WHOIS - deletes The implementations of these policies are not complete. The ICANN community currently has 3 issues in the policy development phase: - next improvement of WHOIS (broken up into 3 components) - approval process for gtld registry service changes - .net criteria We need to work collectively to establish a project management framework that sets out the steps from issues report, through to policy, through to implementation, through to measurement of outcomes, through to review of policy - and re-start the process. We should be able to report on the projects as a whole to the ICANN community with clear indivations of status and estimated dates for project deliverables. It was recognised that the bylaws specify a set of dates for all issues, when in fact some issues (such as WHOIS) are far more complex and more contentious than other issues (e.g redemption grace period). To encourage participation and build confidence in ICANN we need to work to make incremental improvements to the main policy areas each year, rather than trying for years to form an ideal policy, and then struggling for years to implement that policy. This needs better project management. (3) ICANN staff resource management =================================== In the past there were a few ICANN staff members that were required out of necessity to do everything. With ICANN's new budget there will be additional staff resources available. It is important for ICANN staff to work with the GNSO Council to create a view of the current staff resource allocations across the projects. Projects at different stages will need different skill sets. For example during the policy implementation stage, legal changes may need to be made to registry or registrar agreements. During the policy development stage, legal advice on the current obligations of the contracts may be required. It would be useful for the chairs to have a weekly view of staff (or outside consultants) allocations across the projects, and what work is underway. This will assist us all in planning and understanding where there are resource shortfalls. An understanding of resource allocations will also assist in setting more realistic timelines for specific projects underway. Regards, Bruce Tonkin

1 0

GNSO Council Draft minutes 12 July 2004
by gnso.icann 18 Jul '04

18 Jul '04

Dear Councillors, Please find the draft minutes of the 12 July GNSO Council meeting. If you would like any changes made please let me know. Thank you very much Glen de Saint Géry GNSO Secretariat ************************************************************* 12 July 2004. Proposed agenda and related documents List of attendees: Philip Sheppard - Commercial & Business users C. Marilyn Cade - Commercial & Business users C. Grant Forsyth - Commercial & Business users C. - absent Greg Ruth - ISCPC - absent Antonio Harris - ISCPC Tony Holmes - ISCPC Thomas Keller- Registrars Ross Rader - Registrars - absent Bruce Tonkin - Registrars Ken Stubbs - gTLD registries Philip Colebrook - gTLD registries Cary Karp - gTLD registries Lucy Nichols - Intellectual Property Interests C Niklas Lagergren - Intellectual Property Interests C Kiyoshi Tsuru - Intellectual Property Interests C. Jisuk Woo - Non Commercial users C. - absent Marc Schneiders - Non Commercial users C. Carlos Afonso - Non Commercial users C. - absent Alick Wilson Demi Getschko Amadeu Abril I Abril 16 Council Members Paul Verhoef - Vice President, Policy Development Support Barbara Roseman - ICANN Staff Manager Thomas Roessler - ALAC Liaison Suzanne Sene - GAC Liaison - apologies The WHOIS Task Force Chairs were asked to join the call. Brian Darville - WHOIS Task Force 3 Chair Jeff Neuman - WHOIS Task Force 1 Chair absent - apologies Jordyn Buchanan - Whois Task Force 2 absent - apologies Glen de Saint Géry - GNSO Secretariat MP3 Recording Quorum present at 12:05 UTC, Bruce Tonkin chaired this teleconference. Item 1: Approval of Agenda Agenda approved Item 2: Approval of the Minutes May 6, 2004. Ken Stubbs seconded by Philip Sheppard moved the adoption of the Minutes of May 6, 2004. The motion carried with one abstention from Marc Schneiders Decision 1: The May 6 Minutes were adopted Adoption of the 16 June meeting minutes was deferred to the next meeting. Item 3: Matters arising from 16 June 2004 - update on new staff positions Paul Verhoef reported that the new staff position descriptions had been finalized and would soon be published on the ICANN website. (see http://www.icann.org/general/jobs/GNSO-policy-support-officer.htm ) - plan meetings in Kuala Lumpur regarding interaction Between new ICANN staff roles and GNSO Bruce Tonkin reported that he had arranged a meeting with Senior ICANN staff and some GNSO Council members on Sunday 18 July in Kuala Lumpur, to discuss the expectations for the new staff positions. Any other GNSO Council members who wished were welcome to attend. Item 4: Update on WHOIS task forces Receive an update from the WHOIS task force chairs, Jeff Neuman, Jordyn Buchanan, Brian Darville - reports to be updated by 12 July 2004 - plan meetings in Kuala Lumpur Brian Darville reported that that Task Force 3 would not have a report ready by Kuala Lumpur. There were clear recommendations in the preliminary report, the public comments had been summarized, but the report needed additional work and time. Bruce Tonkin reported that Jordyn Buchanan, Whois task force 2 chair and Jeff Neuman, Whois task force 1 chair, were in similar situations with the Task Force 1 and 2 reports that required merging and would only be ready by the Kuala Lumpur meeting. A few weeks work was still needed on the reports after the Kuala Lumpur meetings. Marilyn Cade commented that the task force reports lacked practical means of implementation on some of the concepts being explored and suggested that at the meeting in Kuala Lumpur it would be more productive to develop such guide lines before completing their work. As a way of moving forward, Bruce Tonkin proposed that the GNSO Council as a whole, when meeting with the task forces in Kuala Lumpur, should go through the task force recommendations select those which seemed to be the most practical to pursue and then recommend that the task forces concentrate on the implementatbility of those in detail. It was suggested that Dan Halloran, who has a thorough understanding of the contracts affecting Registrars and Registries, be present Bruce Tonkin further proposed that the outcome of meeting be summarized in email form so that online comments would be possible. Item 5: Update on Policy Development Process (PDP) for approval process for gtld registry changes - draft preliminary report - due 12 July 2004 Bruce Tonkin reported that he was currently working on the report which would probably be discussed in Kuala Lumpur. The intention was to post the report for a 20 day official public comment period after the Kuala Lumpur meetings after which the report could be finalized. Marilyn Cade, asked about timing. The GNSO Council was asked to develop recommendations to ICANN and were the timeframes being met or should they be modified in order to stay in compliance with the Board's request and the ICANN bylaws with respect to the policy development proces? Bruce Tonkin responded that the original letter from Paul Twomey in October mentioned that the GNSO was to make its recommendations no later than 15 January 2004. Item 6: Re-assignment of .net - report on public comment process Philip Sheppard, reported that the second public comment stage was due to close on 14 July. The comments would then be included in the report and the committee would have an opportunity to agree to the report before it was submitted to the GNSO Council in Kuala Lumpur. A .net sub committee meeting was proposed on Tuesday 20 July from 10:00 to 12:00 in Kuala Lumpur. Constituencies were encouraged to discuss their agreement on the report. One statement had been received from the Commercial and Business Users Constituency and constituencies were encouraged to discuss their agreement on the report. Cary Karp expressed concerned as to whether the policy development process was in process or whether the Board was soliciting advice. Bruce Tonkin proposed seeking legal advice and commented that in a letter from Paul Verhoef to Bruce Tonkin as GNSO Chair, the word "advice" was used but in a subsequent letter from Verisign to ICANN, under the Verisign contract, they believed that it needed to be developed as consensus policy using the full policy development process. Philip Sheppard commented that because of the uncertainty the sub committee had operated from the basis of providing advice but following as closely as possible the guidelines in the policy development process. Bruce Tonkin proposed seeking advice from John Jeffrey at the GNSO Council meeting in Kuala Lumpur Item 7: Guide to GNSO policy development Marilyn Cade addressed the issue commenting that from her experience on other fora, she observed the need for the GNSO Council and the Task Forces to have a guide which explained the formal process that needed to be followed in developing policy with the appropriate links to the applicable parts of the ICANN by laws and other documents. Bruce Tonkin suggested that establishing roles and expectations could possibly be an outcome of the Kuala Lumpur meetings with the staff and certain GNSO Council members. Item 8: Any Other Business a. WISIS Marilyn Cade reminded Council that on Tuesday 20 July, at 8:30 from 10:00 there would be the Workshop on the World Summit on the Information Society (WSIS) information meeting which would be addressed by, among others, Paul Twomey and Marcus Kumar, with comments from the constituencies stakeholders and interest groups. b. Kuala Lumpur meetings timetable: The secretary summarized the Kuala Lumpur meetings timetable: Sunday 20 July 8:30 to 10:00 Breakfast with ICANN senior staff and certain GNSO Council members Monday 19 July 7:30 to 9:00 GNSO Council Brekfast with ICANN Board and senior staff Monday 19 July all day Constituency meetings Monday 19 July 13:00 to 13:45 GAC working group/GNSO Council Monday 19 July 17:00 to 17:30 ccNSO /GNSO Council Monday 19 July 19:00 to 22:00 Official Reception Tuesday 20 July 8:30 to 10:00 WSIS Tuesday 20 July 10:00 to 12:00 .net sub committee Tuesday 20 July 11:00 to 13:00 GNSO Council and Whois task force members Tuesday 20 July 14:00 to 16:00 GNSO Council meeting The program would be emailed to the GNSO Council members. c. ccNSO interaction with the GNSO Council Bruce Tonkin proposed a liaison officer and physical meetings at the ICANN meetings as the appropriate way to interact with the with ccNSO. Marilyn Cade and Ken Stubbs were in favour of establishing liaisons with other supporting organizations as well. Bruce Tonkin mentioned that the Kuala Lumpur agenda would be similar to the agenda of this meeting and afford the opportunity to brief the public on the policy areas being undertaken by the GNSO Council. Bruce Tonkin declared GNSO meeting closed and thanked everybody for participating. The meeting ended: 12:50 UTC. Next GNSO Council meeting will be held in the Grand Ballroom at the Shangri-La Hotel in Kuala Lumpur at 14:00 local time, 06:00 UTC see: Calendar

1 0

Summary of meeting - Sunday morning 18 July 2004 in Kuala Lumpur to discuss ICANN staff/GNSO interaction
by Bruce Tonkin 18 Jul '04

18 Jul '04

Hello All, Here are my notes from the meeting this morning. There were three main topics discussed: - policy development process - end-to-end project management to deliver outcomes to the ICANN community - ICANN staff resource management (1) Policy development process A document needs to be created as a manual for participants in the policy process. Chairs of task forces or Council should ideally have experience within the GNSO policy development process prior to becoming chairs. The role of a task force or council member is to work as a member of the team to create a new consensus policy. The member should bring their expertise from their relevant constituency, but should work to understand the positions of the other constituencies and identify compromises that lead to an overall improvement for the ICANN community as-a-whole (rather than just the specific constituency). The overall duty of a task force or Council member is to the ICANN community as-a-whole. The role of the chair is to manage the policy development process and ensure that all members of the committee can contribute using their particular skills and expertise. Currently there is a heacvy reliance on chairs to do much of the editing of reports and analysis of public comments or constituency positions. The aim with the additonal ICANN budget is to reduce the reliance on the chairs, and encourage people expeirneced in the GNSO policy process to take on the role of chair. The role of the staff support person is as described in: http://www.icann.org/general/jobs/GNSO-policy-support-officer.htm Ie - Liaise with the Chair and members of the GNSO Council to conduct background research, data gathering and data analysis of current issues of importance to the Council - Assist with the formation of a Task Force or Sub-Committee and provide guidance to those participating in the policy development processes on relevant steps and timelines (as set out in the bylaws) - As part of the policy development processes, assist the GNSO Council and eventual Task Forces or Sub-committees in the management of their tasks, drafting and producing reports, posting and evaluating public comments, as well as related activities, such as coordination and incorporation of reports from outside advisors - Attend meetings of the Council, Task Forces and/or Sub-committees (mostly by teleconference and including outside office hours) - Provide other assistance to the GNSO Council as may be needed to ensure the smooth running of the policy processes - Where relevant, prepare reports and other materials to the ICANN Board The meeting noted that it would be useful for staff support personnel to have a thorough understanding og the ICANN bylaws with respect to policy development, and assist the chair with the process steps necessary to comply with the policy development process. Note although the staff support person is intended to assist in the editing of reports, members must work to contribute the raw material that allows the report to be created using their specific areas of expertise. A report cannot be created in a vacuum. (2) Project management The ICANN community currently has 3 policies in the implementation phase that were approved early in 2003: - transfers - WHOIS - deletes The implementations of these policies are not complete. The ICANN community currently has 3 issues in the policy development phase: - next improvement of WHOIS (broken up into 3 components) - approval process for gtld registry service changes - .net criteria We need to work collectively to establish a project management framework that sets out the steps from issues report, through to policy, through to implementation, through to measurement of outcomes, through to review of policy - and re-start the process. We should be able to report on the projects as a whole to the ICANN community with clear indivations of status and estimated dates for project deliverables. It was recognised that the bylaws specify a set of dates for all issues, when in fact some issues (such as WHOIS) are far more complex and more contentious than other issues (e.g redemption grace period). To encourage participation and build confidence in ICANN we need to work to make incremental improvements to the main policy areas each year, rather than trying for years to form an ideal policy, and then struggling for years to implement that policy. This needs better project management. (3) ICANN staff resource management =================================== In the past there were a few ICANN staff members that were required out of necessity to do everything. With ICANN's new budget there will be additional staff resources available. It is important for ICANN staff to work with the GNSO Council to create a view of the current staff resource allocations across the projects. Projects at different stages will need different skill sets. For example during the policy implementation stage, legal changes may need to be made to registry or registrar agreements. During the policy development stage, legal advice on the current obligations of the contracts may be required. It would be useful for the chairs to have a weekly view of staff (or outside consultants) allocations across the projects, and what work is underway. This will assist us all in planning and understanding where there are resource shortfalls. An understanding of resource allocations will also assist in setting more realistic timelines for specific projects underway. Regards, Bruce Tonkin

1 0

Senior Officer Policy Support Coordination role now advertised
by Bruce Tonkin 18 Jul '04

18 Jul '04

------------------------------------------------------------------------ -------- 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>. Department: Policy Development Support Manager's title: VP Policy Development Support Position purpose: 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. Key result areas and KPI's performed: Identify the Key Result Areas (KRAs) (the main responsibilities) of the position. A weighting out of 100% has also be given to indicate how much of an importance the KRA has in the position. These KRAs will form the base of the Performance Plan that is to be developed for the incumbent of the position. Each element of the performance plan will have explicitly defined goals attached in terms of time, quality and delivery outcomes. The Key Result Area for this position is: Support the GNSO policy development processes (50%) Facilitate coordination of policy processes between supporting organisations and advisory committees (30%) Co-ordination with other policy areas, operations and implementation (20%) Responsibilities: (These responsibilities should be read in conjunction with the ICANN bylaws) 1. Tasks in relation to the GNSO: ================================= Liaise with the Chair and members of the GNSO Council to understand current issues of importance to the Council and provide guidance on all steps and timelines of the policy development processes Under the direction and responsibility of the GNSO Council, assist the Council and eventual Task Forces and/or Sub-committees in their policy development responsibilities including the drafting of reports, and support related activities Attend meetings of the GNSO Council, Task Forces and/or Sub-committees (mostly by teleconference and often outside office hours) Provide other assistance to the chair of the GNSO Council as may be needed to ensure the smooth running of the policy process 2. Policy co-ordination tasks within the ICANN structure ========================================================= Liaise with the Chairs and relevant members of the supporting organisations and advisory committees to understand current issues of importance to the ICANN community Assist in the identification of cross-relations and needs for co-ordination within the overall ICANN structure of Supporting Organisations and Advisory Committees for policy or other issues under consideration in the specific areas Maintain relationships with relevant stakeholders Assist the Supporting Organisations and Advisory Committees as and where requested, and where further ICANN staff support is judged desirable 3. Co-ordination tasks between ICANN Departments ================================================= Co-ordinate with relevant ICANN staff, aspects of emerging policies as they relate to other ICANN policies, aspects related to implementation (such as feasibility, resource implications, appropriate feed-back mechanisms), aspects related to legal interpretations of ICANN bylaws Assist relevant ICANN staff with the implementation of policy Identify relevant issues that are likely to come before the ICANN Board and prepare briefings for the ICANN Board Brief ICANN management on relevant matters 4. Reporting ============ On all of the above, report to and coordinate with VP Policy Development Support Skills, experience, knowledge and qualifications: Skills Excellent written and verbal communication skills, particularly in a multi-cultural/language environment Excellent English language writing skills Strong computer literacy Strong internet literacy Excellent listening and analytical skills Excellent research and analysis skills Excellent negotiating skills Well developed ability to synthesise a number of diverse view points Project management skills Multiple language skills an advantage Personal attributes Ability to support diverse stakeholders to move to a common framework and outcome Ability to co-operate and work as part of a team Tolerance for stress Ability to manage and prioritise multiple tasks in processes under pressure Ability to retain focus on priority tasks Adaptability/flexibility Ability to review practices to find more efficient and effective ways to work Comfort in dealing with multiple cultures and time zones that are part of an international organisation A high level of interest and /or experience in the IT sector Experience/Knowledge At least five years experience in developing policy in an environment with conflicting stakeholder views Experience in liaising with senior managers in large corporations and with senior government officials Experience in dealing with contracts and contract negotiations an advantage Experience in working with IT or technology sectors/communities desirable Knowledge of the detailed working of the Internet, including basic knowledge of the technical functioning as well as an understanding of the roles of different organisations in the Internet DNS hierarchy Qualifications A bachelors degree or equivalent experience Exposure to economic and legal disciplines and considerations an advantage Key contacts: Internal VP Policy Development Support Policy Development Support staff Manager Registry Relations Manager Registrar Relations General Counsel's Office Other policy support officers External Chairs and members of the Supporting Organisations and Advisory Committees Members of constituent and stakeholder groups of ICANN Location/Travel: ICANN currently has offices in Marina del Rey, California, and Brussels, Belgium. Candidates are required to be available to work in an ICANN location but the decision on which will be taken in consultation with the successful candidate. The incumbent of this position is expected to attend relevant meetings of the supporting organisations and advisory committees (audio-conferences with participation from all over the world at times convenient to its participants). The incumbent is also expected to travel to ICANN meetings (currently 3 times a year at different locations around the world), and other relevant meetings around the globe.

1 0

GNSO Policy officer position now advertised
by Bruce Tonkin 18 Jul '04

18 Jul '04

From: 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>. Department: Policy Development Support Manager's title: VP Policy Development Support Position purpose: 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 included background research, data gathering and analysis, and drafting of reports under guidance of the GNSO Council. Key result areas and KPI's performed: Identify the Key Result Areas (KRAs) (the main responsibilities) of the position. A weighting out of 100% has also be given to indicate how much of an importance the KRA has in the position. These KRAs will form the base of the Performance Plan that is to be developed for the incumbent of the position. Each element of the performance plan will have explicitly defined goals attached in terms of time, quality and delivery outcomes. The Key Result Area for this position is: Support the GNSO policy development processes (70%) Co-ordination with other policy areas, operations and implementation (30%) Responsibilities: (These responsibilities should be read in conjunction with the bylaws governing the GNSO and related policy processes, see http://www.icann.org/general/bylaws.htm in particular Art. X and Annex A) 1. Tasks in relation to the GNSO ================================ Liaise with the Chair and members of the GNSO Council to conduct background research, data gathering and data analysis of current issues of importance to the Council Assist with the formation of a Task Force or Sub-Committee and provide guidance to those participating in the policy development processes on relevant steps and timelines (as set out in the bylaws) As part of the policy development processes, assist the GNSO Council and eventual Task Forces or Sub-committees in the management of their tasks, drafting and producing reports, posting and evaluating public comments, as well as related activities, such as coordination and incorporation of reports from outside advisors Attend meetings of the Council, Task Forces and/or Sub-committees (mostly by teleconference and including outside office hours) Provide other assistance to the GNSO Council as may be needed to ensure the smooth running of the policy processes Where relevant, prepare reports and other materials to the ICANN Board 2. Co-ordination tasks between ICANN Departments ================================================ Co-ordinate with relevant ICANN staff aspects of emerging policies as they relate to other ICANN policies, aspects related to implementation (such as feasibility, resource implications, appropriate feed-back mechanisms), aspects related to legal interpretations of ICANN bylaws Assist relevant ICANN staff with the implementation of policy Identify relevant issues that are likely to come before the ICANN Board and prepare briefings for the ICANN Board Brief ICANN management on relevant matters 3. Reporting ============ On all of the above, report to and coordinate with VP Policy Development Support Skills, experience, knowledge and qualifications: Skills ====== Excellent written and verbal communication skills, particularly in a multi-cultural/language environment Excellent English language writing skills Strong computer literacy Strong internet literacy Excellent listening and analytical skills Excellent research and analysis skills Well developed ability to synthesise a number of diverse view points into a cohesive document Project management skills, personal time management skillss Multiple language skills an advantage Personal attributes Ability to support diverse stakeholders to move to a common framework and outcome Ability to co-operate and work as part of a team Tolerance for stress Ability to manage and prioritise multiple tasks of processes under pressure Ability to retain focus on priority tasks Adaptability/flexibility Ability to review practices to find more efficient and effective ways to work Comfort in dealing with multiple cultures and time zones that are part of an international organisation A high level of interest and /or experience in the IT sector Experience/Knowledge At least five years experience in developing policy in an environment with conflicting stakeholder views Experience in liaising with senior managers in large corporations and with senior government officials Experience in dealing with contracts and contract negotiations an advantage Experience in working with IT or technology sectors/communities desirable Knowledge of the detailed working of the Internet an advantage Qualifications A bachelors degree or equivalent experience Exposure to economic and legal disciplines and considerations an advantage Key contacts: Internal VP Policy Development Support Policy Development Support staff Manager Registry Relations Manager Registrar Relations General Counsel's Office Other policy support officers External Chair of the GNSO Council, members of the GNSO Council, and of GNSO sub-committees and/or Task Forces Liaisons with other ICANN Supporting Organisations and Advisory Committees Members of GNSO constituent groups Location/Travel: ICANN currently has offices in Marina del Rey, California, and Brussels, Belgium. Candidates are required to be available to work in an ICANN location but the decision on which will be taken in consultation with the successful candidate. The incumbent of this position is expected to attend relevant meetings of constituents, in particular the GNSO Council and the GNSO subcommittees and taskforces (audio-conferences with participation from all over the world at times convenient to its participants). The incumbent is also expected to travel to ICANN meetings (currently 3 times a year at different locations around the world), and other relevant meetings around the globe.

1 0

GNSO Council Schedule in KL
by gnso.icann 17 Jul '04

17 Jul '04

Dear Councillors, Please find the GNSO Council Schedule below: Date Time Topic Agenda Place Monday 19 July 7:30 - 9:00 GNSO Council Breakfast (ICANN Board and ICANN Senior Staff) KELATAN (LL Level) 9:30 -13:00 Constituency meetings (Cross Constituency = IP+ ISP+ BC) Agenda <http://www.icann.org/meetings/kualalumpur/cross-constituency-19jul04.ht m> Grand Ballroom 9:00 - 17:00 Non Commercial Users Constituency Agenda <http://www.icann.org/meetings/kualalumpur/ncuc-19jul04.htm> NEGERI SEMBILAN gTLD Registries Constituency Agenda <http://www.icann.org/meetings/kualalumpur/gtld-19jul04.htm> PERAK Intellectual Property Interests Constituency No meeting foreseen Internet Service Providers and Connectivity Providers Constituency Agenda <http://www.icann.org/meetings/kualalumpur/ispcp-constituency-19jul04.ht m> PENANG Registrars Constituency Agenda <http://www.icann.org/meetings/kualalumpur/registrar-constituency-19jul0 4.htm> SELANGOR 13:00 - 13:45 GAC working group/GNSO Council (lunch boxes served) SARAWAK 15:00 - 16:30 Commercial and Business Users Constituency meeting (Dial-in available for all the meeting) Agenda <http://www.icann.org/meetings/kualalumpur/business-constituency-19jul04 .htm> KELANTAN 17:00 - 17:30 ccNSO/GNSO Council Grand Ballroom 19:30 - 22:00 Official Reception (dress: smart casual) Tuesday 20 July 8:30 - 10:00 WSIS Grand Ballroom 10:00 - 12:00 dot Net sub committee meeting Boardroom 27th Floor 11:00 - 13:00 GNSO Council and Whois task force members present Perak 14:00 - 16:00 GNSO Council Meeting Agenda <http://www.gnso.icann.org/meetings/agenda-gnso-20jul04.htm> Grand Ballroom If you have any questions, please come back to me. Thank you very much. Glen GNSO Secretariat

1 0

GNSO Council teleconference draft minutes June 16 2004
by gnso.icann 16 Jul '04

16 Jul '04

{To council[at]gnso.icann.org] Dear GNSO Council members, Please find the draft minutes of the GNSO Council teleconference held on 16 June 2004. If you would like any changes made please let me know. Thank you very much Glen de Saint Géry GNSO Secretariat 16 June 2004. Proposed <http://gnso.icann.org/meetings/agenda-gnso-15jun04.htm> agenda and related documents List of attendees: Philip Sheppard - Commercial & Business users C. Marilyn Cade - Commercial & Business users C. Grant Forsyth - Commercial & Business users C. Greg Ruth - ISCPC Antonio Harris - ISCPC - absent, Tony Holmes - ISCPC - absent, apologies, proxy to Greg Ruth Thomas Keller- Registrars Ross Rader - Registrars Bruce Tonkin - Registrars Ken Stubbs - gTLD registries Philip Colebrook - gTLD registries Cary Karp - gTLD registries Lucy Nichols - Intellectual Property Interests C - absent - apologies, proxy to Niklas Lagergren Niklas Lagergren - Intellectual Property Interests C Kiyoshi Tsuru - Intellectual Property Interests C. - absent Jisuk Woo - Non Commercial users C. Marc Schneiders - Non Commercial users C. Carlos Afonso - Non Commercial users C. - absent, apologies, proxy to Marc Schneiders Alick Wilson - absent, apologies Demi Getschko - joined call after roll call Amadeu Abril I Abril - absent, apologies proxy to Alick Wilson/Bruce Tonkin 14 Council Members Kurt Pritz - Vice President, Business Operations Paul Verhoef - Vice President, Policy Development Support Barbara Roseman - ICANN Staff Manager Thomas Roessler - ALAC Liaison Suzanne Sene - GAC Liaison Christopher Wilkinson - GAC Secretariat Young Eum Lee - ccTLD Liaison The WHOIS Task Force Chairs were asked to join the call. Jeff Neuman - WHOIS Task Force 1 Chair absent - apologies Jordyn Buchanan - Whois Task Force 2 Brian Darville - WHOIS Task Force 3 Chair Glen de Saint Géry - GNSO Secretariat <http://gnso-audio.icann.org/GNSO-Council-20040616.mp3> MP 3 Recording Quorum present at 12:10 UTC, Bruce Tonkin chaired this teleconference. Item 1: Approval of Agenda Agenda approved Item 2: Approval of the <file:///C:\Program%20Files\Macromedia\Dreamweaver%203\gnso\safe\%3Cfont %20face=%22Arial,%20Helvetica,%20sans-serif%22%3E%3Cb%3EApril%201,%20> April 1, 2004 minutes and the <http://gnso.icann.org/mailing-lists/archives/council/msg00487.html> May 6, 2004 Minutes Ken Stubbs seconded by Philip Sheppard moved the adoption of the <http://gnso.icann.org/meetings/minutes-gnso-1apr04.shtml> April 1, 2004 minutes. The motion carried unanimously Decision 1: The <http://gnso.icann.org/meetings/minutes-gnso-1apr04.shtml> April 1, 2004 minutes were adopted Bruce Tonkin reported that following the May 6, 2004 meeting, Kurt Pritz and Paul Verhoef had provided some clarification and that accordingly, the minutes of the May 6 meeting had been simplified and revised . On the topic of GNSO Staff support, Paul Verhoef stated that in agreement with the GNSO Council there were 3 positions being published on overall policy development support : 1. GNSO Staff Manager's position, that should become a staff position (rather than a consultant as is currently the case) 2. additional support for the GNSO, partly shared with the other supporting organizations 3. a policy analyst position, to follow the isues in the ccNSO and the ASO. When the job descriptions are complete and as soon as the budget is approved the successful candidates would be offered contracts. In summary, the current situation is: Paul Verhoef Vice President, Policy Development Support Barbara Roseman, consultant and acting as ICANN's GNSO Staff Manager Glen de Saint Géry, GNSO Secretariat In addition to the GNSO Staff Manager position, publish 2 additional positions, 1. Policy analyst to follow both ASO and ccNSO 2. Additional support mostly for the GNSO as well as coordination between all supporting organizations. The descriptions for the two positions would be submitted to the GNSO Chair and council members for a round of comments. Furthermore, Paul Verhoef informed the Council that the exact roles of the positions would, among other things, depend on the skills and experience of the recruited candidates. No salary range had yet been discussed. Paul Verhoef commented that it was important for the Council to agree on the role of staff in the GNSO policy development in practise as the staff often finds it difficult to combine the Council's wish for staff to play a pro-active role in the processes while on the other hand not be seen to determine policy. Bruce Tonkin commented that it would be useful to have role descriptions with guidelines and rules of procedure for the task force chairs, task force members and ICANN staff as well as understanding what ICANN means. Kurt Pritz proposed forming a small committee of Council and staff members to write such a framework which could be reviewed and commented on by the whole Council once the job descriptions were published Bruce Tonkin reported that he had spoken to Paul Twomey regarding interaction with different staff roles, how to protect the staff and deal with conflicting views of individual task force members and concluded that ultimately everyone was responsible for reaching consensus. Given that conflicts are difficult to resolve at the Board or the Council level they should ideally be resolved by task force members during the task force process. Timelines and actions: 1. End of June for the job descriptions to be complete 2. Week 21 - 25 June a teleconference between senior ICANN staff such as Paul Verhoef, Kurt Pritz, Paul Twomey, John Jeffrey and a small group of Council members that have actively chaired various task forces and committees over the past few years within the DNSO Names Council/GNSO Council. The aim would be to agree on a set of shared expectations for: - the types of tasks to be assigned to the ICANN staff - the respective role of task force members and chairs - procedures for allocating tasks to ICANN staff in an environment where there are often several policy development processes operating in parallel and hence the chance for contention in the use of resources which could be used during interviews. Topics arising from the minutes of May 6, 2004. 1. Establishing contact with the ccNSO regarding an International Domain Names (IDN) workshop. In the meantime ICANN has scheduled a whole day workshop and there is a program committee so that if individual council members wished to have topics included, they should contact Tina Dam or Dan Halloran at ICANN or Bruce Tonkin. 2. The GNSO Council members and the ccNSO would meet and discuss the best way to liaise between the two groups. Bruce Tonkin proposed that at physical meetings there would be a breakfast or lunch between the two groups and that as with the GAC and the ALAC, one or two people could be appointed from the ccNSO Council to attend GNSO Council meetings and likewise the GNSO Council could appoint representatives to attend ccNSO meetings. Preliminary discussions have been proposed on Monday, 19 July at 5:00 PM in the Grand Ballroom of the Shangri La Hotel in Kuala Lumpur. 3. Christopher Wilkinson reported that the GAC and the GNSO would not be having a full bilateral session as happened in Rome. Suzanne Sene reported that some time would be found for the members of the GAC GNSO working group and interested GNSO Council members to discuss issues arising from possible Whois recommendations. Item 3: Update on WHOIS task forces Receive an update from the WHOIS task force chairs, Jeff Neuman, Jordyn Buchanan, Brian Darville - status of public comment process - next steps - review timetable for completing final reports Jordyn Buchanan on behalf of all 3 task force chairs requested : First, that after the close of the public comment period the Task Forces be allowed to revisit their initial reports so that they may be updated in response to public comment as well as additional feedback from constituencies. Second, some areas of overlap between Task Forces 1 and 2, have been identified and requests may be made of Council to approve procedures designed to resolve any conflict between the two Task Forces' recommendations. Procedures to move forward should still be established. Finally, depending on the level of response seen in the public comment period, the option of extending the length of the public comment period. Suzanne Sene reminded Council that the GAC would not speak to a preliminary report and that it could only take positions at GAC plenary sessions. Any available information from the task forces should be submitted to the GNSO GAC working group which will be meeting on Saturday 17 July in Kuala Lumpur. Marilyn Cade commented on the value, in past task force work, of open teleconferences to provide an opportunity for parties to ask questions of the task force and offer input as part of the public comment process. Bruce Tonkin reminded all task force members that in addition to their advocacy role on behalf of their constituencies, they were also responsible for working cooperatively with other task force members to attempt to reach an ideal consensus position on the policy. Consensus may be defined as a 2/3 minimum vote, but the ideal would be as close to 100% as possible for full community support. Task forces 1 and 2 should also attempt to coordinate their work so that their recommendations are consistent. Task forces should identify where further implementation analysis is necessary for some recommendations before they can be finally voted on by Council Bruce Tonkin seconded by Ken Stubbs proposed a procedural motion that Council approves: - extending the public comment period to Monday 5 July 2004 - reports be updated by Monday 12 July 2004 - task forces are encouraged to initiate public teleconferences to stimulate public comment during the public comment period - that task forces are encouraged to work internally towards a complete consensus position Decision 2: The public comment period be extended to Monday 5 July 2004 - reports be updated by Monday 12 July 2004 - task forces are encouraged to initiate public teleconferences to stimulate public comment during the public comment period - that task forces are encouraged to work internally towards a complete consensus position Item 3: Update on PDP for approval process for gtld registry changes - set a target date for a preliminary report Bruce Tonkin reported that there had been a meeting on May 17/18 and agreement reached on a general framework. The criteria should be organized under two broad categories, competition and stability then request whether Council considers a third category should be added. The aim would be for a preliminary report by 12 July 2004, thus starting the public comment period a week before the Kuala Lumpur ICANN meeting Item 5: Re-assignment of .net Receive an update from the .net Council subcommittee Philip Sheppard, .net Council subcommittee chair, reported that since the .net sub committee had started in mid April 2004, there had been 4 conference calls resulting in a preliminary report which made a set of recommendations divided into two categories: Absolute criteria thresholds that would be expected to be met, related to: Targeting Continuity Policy Compliance Stability, security, technical and financial competence Relative criteria, to be used a basis of comparison for the applications, related to: Promotion of competition Stability, security, technical and financial competence Existing registry services The report was fully supported by all sub committee members, published for the first 20-day Public Comment Period on 28 May 2004 until 18 June 2004. One comment had been received to date. To meet the timetable, the aim was to publish a revised report for final public comment from June 25 to July 15 and have a Final report for the Council to vote on during the Council meeting in Kuala Lumpur on July 20, 2004. Item 6: Any Other Business Marilyn Cade raised the topic of new gTLDs and Bruce Tonkin reported that according to the <http://www.icann.org/general/amend6-jpamou-17sep03.htm> MOU: "Define and implement a predictable strategy for selecting new TLDs using straightforward, transparent, and objective procedures that preserve the stability of the Internet (strategy development to be completed by September 30, 2004 and implementation to commence by December 31, 2004). " It was suggested at the <http://gnso.icann.org/meetings/minutes-gnso-1apr04.shtml> GNSO Council meeting of April 1, 2004 that ICANN staff Manager draw up an Issues report for the Kuala Lumpur GNSO Council meeting. Paul Verhoef reported from the ICANN staff perspective that a strategy had to be developed by September 30 and commence implementation of the strategy by December 31, 2004. Currently expert advice was being sought regarding economic, competition, trademark, intellectual property issues. Several organizations such as: the Organization for Economic Cooperation and Development (OECD) (which has promised to try and declassify their document before the Kuala Lumpur meeting), the World Intellectual Property Organization (WIPO) and the Security and Stability Advisory Committee (ssac) were expected to provide expert advice by September 30, 2004. It was expected that the strategy, based on the staffs' initial assessment of the expert advice as to which questions should be asked and the process of answering them, including the GNSO policy development process, would be in place by December 30, 2004. It was not clear what questions ICANN should be asking themselves, nor was it clear how it could be determined exactly what level of competition was useful or not. Marilyn Cade expressed concern about timeframes, deadlines, that Council seemed to be too far away from the process and that a policy development process should evolve in a timely manner. Paul Verhoef was of the opinion that at the time of drafting the MOU the assumption was that there would be new gTLDs in the traditional sense which was not necessarily a given any more in view of different possibilities of gTLDs such as traditional gTLD's, sTLD's, IDN's, etc and possibly the predictable strategy should be interpreted in a slightly wider sense than it was originally foreseen. The answer to Bruce Tonkin's enquiry whether this would be subject to dialogue between ICANN and the Department of Commerce (DOC) was that there would have to be agreement on the part of DOC as the deadlines and the mandate are also part of the MoU. Kurt Pritz presented the scenario where, as a result of studies, the strategy that would be adopted, or recognized might be that, part of new TLD strategy would be the implementation of full International Domain Names (IDN). That implementation would require policy questions to be answered by the GNSO, technical questions to be answered by other supporting committees so that implementation would have to figure out policy questions. The Kuala Lumpur IDN workshop agenda will be published on the ICANN website. Bruce Tonkin declared GNSO meeting closed and thanked everybody for participating. The meeting ended: 14:00 UTC * Next GNSO Council teleconference tbd * Next GNSO Council meeting will be held in the Grand Ballroom at the Shangri-La Hotel in Kuala Lumpur at 14:00 local time, 06:00 UTC see: <http://gnso.icann.org/calendar/> Calendar _____

1 0

GNSO Secretariat contact # in KL
by gnso.icann 16 Jul '04

16 Jul '04

To GNSO Council members in KL. My cell phone number is: + 6 (0) 17 69 00 939 Thanks Glen de saint Géry GNSO Secretariat

1 0

Draft Agenda for Council meeting Tuesday 20 July 2004 in Kuala Lumpur
by Bruce Tonkin 15 Jul '04

15 Jul '04

Agenda for Council meeting Tuesday 20 July 2004 2pm Kuala Lumpur time Item 1: Report from Security and Stability Advisory Committee [20 mins] - Steve Crocker to present outcomes of review of Sitefinder Item 2: Update on WHOIS task forces (30 mins) Receive an update from the WHOIS task force chairs - reports to be updated by 12 July 2004 - plan meetings in Kuala Lumpur Item 3:Update on PDP for approval process for gtld registry changes (5 mins) - draft report for comment Item 4: Update on Re-assignment of .net advice (10 minutes) Item 5: Update on meetings with ICANN staff regarding policy development processes Item 6: Update on meeting with ccNSO regarding liaisons Item 7: Any other business

1 0