January 2007 - council - lists.icann.org

Reschedule of Council meeting 22 Feb to 1 March 2007
by Bruce Tonkin Jan. 19, 2007

Jan. 19, 2007

Hello All, Just a note to confirm that in light of the policy meeting schedule for 22-25 Feb 2006, I have re-scheduled the Council meeting originally scheduled for 22 Feb to the following week on 1 March 2007. The GNSO Council meeting on 22 Feb 2007 is CANCELLED. Regards, Bruce Tonkin

1 0

Draft Agenda for Council meeting - Thursday 1 February 2007
by Bruce Tonkin Jan. 19, 2007

Jan. 19, 2007

Note I have replaced the terminology of "sunrise processes" with the more neutral terminology borrowed from the most recent new gTLD round "Protecting the rights of others". At the request of ICANN staff, I have also added an agenda item 4 to agree the process for selecting ICANN Board Seat #13. Draft Agenda for Council meeting - Thursday 1 February 2007 11:00 LA, 14:00 Washington DC, 19:00 UTC, 20:00 Brussels, 6:00 Melbourne next day 2 February 2007 Item 0: Roll call of Council members on the call Item 1: Update any statements of interest Item 2: Approval of Minutes - 18 January 2007 Item 3: Proposed Working Group on "Protecting the rights of others" - Proposal to form a GNSO working group to consider possible policies and practices that minimize abusive registration activities and other activities that affect the legal rights of others. - Kristina Rosette and Ute Decker to draft terms of reference for Consideration Item 4: Process for electing a replacement for ICANN Board seat #13 Alejandro Pisanty's term on the ICANN Board concludes 6 months after the ICANN annual meeting in 2006 (ie 8 June 2007). As recorded in the minutes of 19 Feb 04 (http://www.gnso.icann.org/meetings/minutes-gnso-19feb04.shtml) Alejandro is not eligible for re-election as he has reached the term limit provisions in the ICANN bylaws ("no Director may serve more than three consecutive terms"). The GNSO must inform the Secretary of ICANN of its selection for Board Seat #13 before 8 May 2007. Note also at any given time, no two Directors selected by a Supporting Organization shall be citizens of the same country or of countries located in the same Geographic Region. Rita Rodin was recently selected by the GNSO to fill ICANN Board Seat #14, and is from North America. (From ICANN bylaws http://www.icann.org/general/bylaws.htm#VI , Article VI, section 8, clauses 1(e) and 3, and Section 2, clause 3) The GNSO Secretariat will propose a timeline/process for consideration. Item 5: Any other business Regards, Bruce Tonkin

1 0

Protecting the rights of others
by Bruce Tonkin Jan. 18, 2007

Jan. 18, 2007

Hello All, For information, here is some text from the 2003/2004 new gTLD round: From: http://www.icann.org/tlds/new-stld-rfp/new-stld-application-parta-15dec0 3.htm " Protecting the rights of others New sTLD registries will be responsible for creating policies and practices that minimize abusive registration activities and other activities that affect the legal rights of others. sTLD registries are required to implement safeguards against allowing unqualified registrations, and to ensure compliance with other ICANN policies designed to protect the rights of others." There is also another section that states: " ..... avoidance of abusive registration practices Operators of sTLDs must implement safeguards to ensure that non-compliant applicants cannot register domain names. Applicants must demonstrate that their proposals address and include precise measures that: - Discourage registration of domain names that infringe intellectual property rights; .. - Reserve specific names to prevent inappropriate name registrations; - Minimize abusive registrations; - Comply with applicable trademark and anti-cybersquatting legislation; - and Provide protections (other than exceptions that may be applicable during the start-up period) for famous name and trademark owners. " Also "Assurance of adequate dispute-resolution mechanisms All gTLD registries must adhere to the ICANN Uniform Dispute Resolution Policy (UDRP). Particular dispute resolution mechanisms are implemented to support situations such as priority of acceptance of applicants in competition for the same name during start-up periods." Regards, Bruce Tonkin

1 0

Marina del Rey GNSO policy work meetings
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Jan. 18, 2007

Jan. 18, 2007

[To: council[at]gnso.icann.org] [To: pdp-pcceg-feb06[at]gnso.icann.org] [To: gtld-council(a)gnso.icann.org] Dear All, At the GNSO Council meeting that has just taken place 18/19 January, the broad agenda for the GNSO policy work meetings was confirmed. Thursday 22 and Friday 23 February will be devoted to work on the new gTLD PDP Dec 06 and Saturday 24 and Sunday 25 will be devoted to work on the PDPFeb06 - GNSO Policies for contractual conditions, existing gTLDs. Observers are welcome, but would the constituencies please let me know as soon as possible how many observers they would like to attend so as to provide adequate working room space and hotel accommodation. Details of the agendas will be following for the PDPDec05 and PDPFeb06 will be following. Thank you. Kind regards, Glen -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Re: GNSO Council teleconf. WHOIS Task force update,18 January 2007,]]
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Jan. 18, 2007

Jan. 18, 2007

Hi Glen: I've got a conflicting meeting, so I'm unlikely to be able to attend. Here's a brief update on the TF activities since Sao Paulo: - We've briefly discussed two new proposals (one from Avri/Wendy/Robin to eliminate Whois or remove all non-technical contact information; and one from Marilyn with ideas to remove port 43 access, limit bulk Whois, and further study the topic). - We've had some further discussions about access to data that might be removed from public view by the TF. We've begun limiting the options from the five presented in the preliminary report. - Public comment period just closed and we've also received several constituency statements. We'll be discussing these next week. - We remain on track for completing our work on February 12 (I hope). Jordyn -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

2 1

by Marilyn Cade Jan. 18, 2007

Jan. 18, 2007

Dear colleagues With apologies for the 'just in time substitution' for tomorrow's Council call agenda item on the Statement of Work for Reserved Names, Chuck Gomes and Marilyn Cade ask that you accept this document as a replacement to the earlier draft which we posted now about 7 days ago. We have received some comments and tried to address them. In addition, we have improved the document and reorganized and streamlined some sections. We make a special effort to note that we believe that the work initiatives can be broken into sub-elements and addressed in even sequential tracks, so that not all work has to be done at the same time. We have discussed in the preparation of this version that we believe that some work will have a higher priority than other. We will work from the document attached above in the discussion on the Statement of Work. In the event that you have trouble with opening documents for any reason, it is pasted below, as well. Thanks to Liz Williams for her assistance. Submitted by Marilyn Cade and Chuck Gomes Draft Statement of Work - Version 2 for Working Group on Reserved Names (WG-RN) I. Formation of the Working Group The Working Group (WG) is chartered by the GNSO Council with an approved statement of work, as defined below. This Statement of Work is intended to guide the work of the group. 1. Voting: In general, the working group should operate using a rough consensus approach. Every effort should be made to arrive at positions that most or all of the group members are willing to support. "Straw poll voting" should be used to determine whether there is rough consensus on particular issues. In order to ensure that each constituency does not have to provide the same number of members, constituencies, regardless of number of representatives, can hold 3 votes, and each individual nominating committee councilor hold one vote. Liaisons are non voting. 2. Membership The Working Group is open for membership to Councilors and to GNSO Constituency members; advisory committees (e.g., ALAC, GAC) may appoint non-voting liaisons to the working group. Members may be added by the constituencies and the Advisory groups at any time during the work of the WG. The ccNSO could be invited to have representatives participate as observers because there may be implications for the treatment of the two letter country codes, which are presently reserved at all levels. The WG may invite external experts as speakers or advisors (in the role of observer) that may be able to constructively contribute to the effort. Every effort should be made to ensure that the working group include and consider the varying points of view on key issues. It is more important that all varying points of view are examined and reflected than for every constituency or group to have representation or equal numbers of members. If this goal is achieved and recommendations are developed that have rough consensus of the group, then the full Council, with balanced representation from all constituencies and NomCom appointees, will then have opportunity to act. Members should be selected who can commit sufficient time during the next three-four months to facilitate achievement of the targeted accomplishments describe in the next section (Working Timeline). The Council will appoint an initial or interim chair [or co-chairs] and the Working Group should, at its initial meeting, elect or confirm the chair and co-chair(s). 3. Working Timeline The Working Group is asked to convene at the earliest possible time and to achieve the following targets: 1. Progress report in the upcoming intercessional working sessions of Dec05 PDP committee and the Feb06 PDP task force, scheduled for February 22-25 2. Deliver written recommendations for next steps forward to the GNSO Council at least one week prior to the start of the Lisbon ICANN meetings 3. Provide any follow-up actions requested by the Council within 30 days after the Lisbon meetings. As appropriate, the Working Group should coordinate throughout with the Dec05 PDP Committee, the Feb06 PDP Task Force and the GNSO Council. II. Purpose of the Working Group The purpose of the WG will be to perform an initial examination of the role and treatment of reserved domain names at the first and second level., with the goal of providing recommendations for further consideration by the TF or Council. This working group should focus initially on defining the role of reserved strings, and how to proceed with a full examination of issues and possible policy recommendations. This will include prioritizing sub-elements of the broad topic of reserved names in a manner that would facilitate breaking the broad topic into smaller parts that could then be divided into separate policy efforts of a more manageable size and that might also allow some less complicated issues to be resolved in a more timely manner so that some policy changes might be included in the introduction of new gTLDs. The treatment of reserved names is a matter of contract for existing gTLDs and will be a matter of contract for future gTLDs. As such it relates to the work of both the Dec05 PDP regarding the Introduction of New gTLDs including IDNs and the Feb06 PDP regarding Contractual Conditions for Existing Registries, Therefore the WG needs to provide an initial examination of reserved names at both the top and second level for both existing and new gTLDs. Should it be determined that the ToR for Feb 06 does not allow for addressing contractual conditions, the WG report to the Council regarding relevant recommendations. III. Working Group Responsibilities, Tasks and Proposed Working Approach A. To perform its initial examination of the role and treatment of reserved domain names at the first (top) level, WG responsibilities and tasks should include but need not be limited to the following: 1. Review the present treatment and process for reservation of names at all levels (using Appendix 6 in the latest gTLD Registry Agreements as examples), including reviewing treatment of reserved names that may differ in existing contracts - link provided in Background Section 2. Review any other discussions to date that have occurred related to reserved names for top level strings for new gTLDs including IDN gTLDs (e.g., the GNSO's Task Force on new gTLDs; constituency comments, etc.) 3. Review any ICANN staff reports related to reserved names - see Background Section 4. Review any relevant technical documents ,e.g., relevant RFCs -see Background Section and determine what technical outreach (IETF, IAB, SSAC,etc.) is needed and complete. 5. Liaise with the ICANN staff as needed, including legal and operational, to identify and review any existing work or relevant experiences related to reserved names processes and procedures 6. Liaise with the ccNSO and the ccTLD community in general as needed regarding the two letter names issues, including whether the present approach, as outlined in Appendix 6, is sufficient or necessary B. Proposed Working Approach for Working Group: 1. Initially, examine the sub-elements of the broad topic of reserved names to consider breaking the broad topic into smaller parts 2. Estimate the complexity of issues associated with each of the sub-elements and briefly describe the elements of complexity (e.g., more controversial issues involving multiple stakeholder groups with competing views might be rated more complex; consultation with the GAC might be rated as more complex; etc.) 3. Prioritize the sub-elements according to these two factors: a. Estimated level of complexity (less complex to higher) b. Importance/relevance to complete any future policy work prior to the introduction of new gTLDs c. Other {to be developed} 4. Identify any sub-elements for which any needed policy work may be able to be completed in time for the introduction of new gTLDs and develop recommendations about how that might best be accomplished/launch development of recommendations 5. Identify the remaining sub elements and establish a working plan to address these, including considering parallel work tracks, if feasible and resources permit, versus sequential work. 6. Prepare and submit an interim report to the relevant PDP group and/or the Council so that any additional policy work needed could be started as soon as possible referencing the Time Line provided by the Council 7. Prepare and submit a final report regarding all of the above for both PDP groups and the Council upon conclusion of work.. Regular progress reports should be provided for both PDP groups and the Council corresponding to scheduled meetings of those groups and the Council. IV. Example of Topics for Reserved Names This section provides an example of a work plan outline for the work of the Working Group. It is provided as an initial resource for potential use by the Working Group and to attempt to help to launch the Working Group quickly, due to the pressures of time limitations. It is not intended to be comprehensive nor prescriptive. It should be assumed that the work will need to ask the question of how reserved names apply to IDNs at both second and first levels, as well as Latin character gTLDs. 1. Identify possible roles and purposes for reserved names at the top level and review and examine those roles and purposes, including how to address the role of reserved names in IDNs 2. Identify and develop proposals to address any policy issues that should be or are under consideration by the existing GNSO PDPs regarding policy considerations related to the role, use, reservation, and release and allocation of reserved names at the top and second level 3. Determine: a. The various roles that reserved names may play in new gTLDs in addressing controversial categories of names, including whether trademark names and country/geopolitical names should have initial or permanent reserved status; etc. b. Whether existing reserved names at the second level should automatically be included at the first level or c. Whether there is different treatment proposed for existing reserved names at the second level, in the first level d. Whether reserved name requirements need to be the same for all gTLDs and, if not, which ones might vary e. Whether there should be a procedure by which staff publishes new categories of reserved names before adding them to registry agreements 4. Discuss and review processes by which names could be put into reserved status at the top level 5. Discuss and propose processes by which names can be unreserved at the top level and made available for allocation, including discussion of whether there are unique treatments in allocation for names that are reserved 6. Discuss whether and how categories of names can be unreserved and allocated at the second level from the existing categories, including second level reservations in single character[1] and two character labels, and reservations for geographic and geopolitical names, to include examination of any existing technical concerns 7. Reconfirm whether there should be a process by which new names or categories are added to the reserved status in the second level (e.g., should we assume that all new strings allocated for operation as registries are reserved at the second level when they are awarded?) Background Materials and Relevant Initiatives to take into account: Background: 1) Existing Registry Agreements Reserved Names (Annex 6 and other examples) http://www.icann.org/registries/agreements.htm 2) Relevant RFCs which discuss reserved names http://www.rfc-editor.org/rfc/rfc2606.txt http://www.ietf.org/rfc./rfc2141.txt http://www.rfc-editor.org/rfc/rfc3491.txt 3) Status report on single letter names - to be provided Relevant Initiatives: (1) PDP 05: developing policy recommendations on new gTLDs, as part of a policy development process called PDP-Dec05. http://www.gnso.icann.org/issues/new-gtlds/ (2) PDP 06 [need link] (3) IDN Working Group http://www.gnso.icann.org/issues/idn-tlds/issues-report-02aug06.htm Submitted by: Marilyn Cade and Chuck Gomes Attachment 1: Additional considerations: For a policy issue to warrant a policy development process it must Meet the following criteria: (A) Is within the scope of ICANN's mission statement; (B) is broadly applicable to multiple situations or organizations; (C) is likely to have lasting value or applicability, albeit with the need for occasional updates; (D) Will establish a guide or framework for future decision-making; or (E) Implicates or affects an existing ICANN policy. _____

4 3

RE: [council] reserved names work plan
by Gomes, Chuck Jan. 18, 2007

Jan. 18, 2007

I hope my comment did not come across as a criticism of Liz. If so, I apologize. I also very much appreciate her long hours of work and just simply wanted to point out that the draft ToR tasks the WG with making such recommendations so it doesn't seem like the best idea to predetermine their work. Personally, I think her idea is very worthy of further consideration. Chuck -----Original Message----- From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Ross Rader Sent: Thursday, January 18, 2007 11:38 AM To: Philip Sheppard Cc: 'GNSO Council' Subject: Re: [council] reserved names work plan I agree with Chuck. We don't know what the work is or whether we or not we will be engaging in that work. I do appreciate the support we get from Liz - she has been very instrumental in helping us move the ball forward over the past year and a bit (especially in instances where we haven't been so inclined to move), but there is also a natural ordering to events - the first of which includes us deciding whether or not we are going to proceed, and if so, what work we are going to proceed with. Philip Sheppard wrote: > re Chuck wrote: "I think it is premature to be recommending how work should be done". > --------------------------------- > Is it not about time that we as Council started trusting the staff > (whom we asked for so long to have) and respond favourably to useful recommendations? > As someone who works for a secretariat I make work plan > recommendations all the time and my members - some of the top companies in the world - expect no less. > > Surely we want staff to guide us, steer us and help move things forward? > Then the WGs and PDPs decide on the actual policy (and are at liberty > to overturn a staff recommendation). > > I for one like to see paid full time professionals be allowed to do their job. > > Philip > > > >

1 0

RE: [council]
by Gomes, Chuck Jan. 18, 2007

Jan. 18, 2007

Thanks for the input Liz. I have just one comment for now. One of the tasks in the draft SoW for the Reserved Names WG is to make recommendations regarding how future work on reserved names issues should be made so, if we proceed with the WG, I think it is premature to be recommending how work should be done. We should leave it to the WG to make recommendations in that regard. They certainly would have the freedom to come to the same conclusions you have and may, but that should be a result of their work. Chuck -----Original Message----- From: owner-council(a)gnso.icann.org [mailto:owner-council@gnso.icann.org] On Behalf Of Liz Williams Sent: Thursday, January 18, 2007 5:55 AM To: GNSO Council Subject: Re: [council] Colleagues I have just read through this material. I have attached the September 2005 Single Letter Second Level status report which was referred to in the document. This refers to the treatment of reserved names in existing registries. Please note section 2 which outlines the policy questions associated with this work and the questions around any policy for an appropriate allocation method for reserved names that could, in the future, be released for use. It is my recommendation that the two streams of work -- reserved names that relate to new TLDs and reserved names that relate to existing registries -- be treated as two separate projects. There are two purposes to considering reserved names in the new TLDs context -- a list which would guide potential applicants about strings which would be reserved and a list to guide successful applicants about what names may be reserved in any new registry. The work on new TLDs is very time critical and can be integrated into the work on new TLDs which has already taken place. As everyone who has been working on the PDP Feb 06 will be aware, policy discussions for contractual conditions for existing registries are an important and sensitive area of work. The treatment of reserved names for existing registries is contained in each of the existing registry contracts. I would recommend that the GNSO Council consider launching a formal PDP on reserved names in existing registries -- rather than a Working Group -- and prioritise that work according to the Council's program which includes the IDN WG, the new TLDs Committee, the WHOIS working group and the PDP Feb 06. I would note, and the GNSO calendar confirms, that we have an extremely tight schedule of work on new TLDs, PDP Feb 06, the IDN WG and the WHOIS committee. We have a limited number of constituency members to populate working groups and I would hope that we could complete at least one of the four active pieces of work on the Council's agenda prior to taking on another formal PDP. Kind regards. Liz ..................................................... Liz Williams Senior Policy Counselor ICANN - Brussels +32 2 234 7874 tel +32 2 234 7848 fax +32 497 07 4243 mob On 18 Jan 2007, at 02:18, Marilyn Cade wrote: > Dear colleagues > > With apologies for the 'just in time substitution' for tomorrow's > Council call agenda item on the Statement of Work for Reserved Names, > Chuck Gomes and Marilyn Cade ask that you accept this document as a > replacement to the earlier draft which we posted now about 7 days ago. > > > > We have received some comments and tried to address them. In addition, > we have improved the document and reorganized and streamlined some > sections. We make a special effort to note that we believe that the > work initiatives can be broken into sub-elements and addressed in even > sequential tracks, so that not all work has to be done at the same > time. We have discussed in the preparation of this version that we > believe that some work will have a higher priority than other. > > > > We will work from the document attached above in the discussion on the > Statement of Work. In the event that you have trouble with opening > documents for any reason, it is pasted below, as well. > > > > Thanks to Liz Williams for her assistance. > > > > Submitted by Marilyn Cade and Chuck Gomes > > Draft Statement of Work - Version 2 > > for > > Working Group on Reserved Names (WG-RN) > > > > I. Formation of the Working Group The Working Group (WG) is > chartered by the GNSO Council with an approved statement of work, > as defined below. This Statement of Work is intended to guide the > work of the group. 1. Voting: In general, the working group should > operate using a rough consensus approach. Every effort should be > made to arrive at positions that most or all of the group members > are willing to support. "Straw poll voting" should be used to > determine whether there is rough consensus on particular issues. > In order to ensure that each constituency does not have to provide > the same number of members, constituencies, regardless of number of > representatives, can hold 3 votes, and each individual nominating > committee councilor hold one vote. Liaisons are non voting. 2. > Membership The Working Group is open for membership to Councilors > and to GNSO Constituency members; advisory committees (e.g., ALAC, > GAC) may appoint non-voting liaisons to the working group. Members > may be added by the constituencies and the Advisory groups at any > time during the work of the WG. The ccNSO could be invited to have > representatives participate as observers because there may be > implications for the treatment of the two letter country codes, > which are presently reserved at all levels. The WG may invite > external experts as speakers or advisors (in the role of observer) > that may be able to constructively contribute to the effort. Every > effort should be made to ensure that the working group include and > consider the varying points of view on key issues. It is more > important that all varying points of view are examined and > reflected than for every constituency or group to have > representation or equal numbers of members. If this goal is > achieved and recommendations are developed that have rough > consensus of the group, then the full Council, with balanced > representation from all constituencies and NomCom appointees, will > then have opportunity to act. Members should be selected who can > commit sufficient time during the next three-four months to > facilitate achievement of the targeted accomplishments describe in > the next section (Working Timeline). The Council will appoint an > initial or interim chair [or co-chairs] and the Working Group > should, at its initial meeting, elect or confirm the chair and co- > chair(s). 3. Working Timeline The Working Group is asked to > convene at the earliest possible time and to achieve the following > targets:1. Progress report in the upcoming > intercessional working sessions of Dec05 PDP committee and the > Feb06 PDP task force, scheduled for February 22-252. > Deliver written recommendations for next steps forward to the GNSO > Council at least one week prior to the start of the Lisbon ICANN > meetings3. Provide any follow-up actions requested by > the Council within 30 days after the Lisbon meetings. As > appropriate, the Working Group should coordinate throughout with > the Dec05 PDP Committee, the Feb06 PDP Task Force and the GNSO > Council. II. Purpose of the Working Group The purpose of the WG > will be to perform an initial examination of the role and treatment > of reserved domain names at the first and second level., with the > goal of providing recommendations for further consideration by the > TF or Council. This working group should focus initially on > defining the role of reserved strings, and how to proceed with a > full examination of issues and possible policy recommendations. > This will include prioritizing sub-elements of the broad topic of > reserved names in a manner that would facilitate breaking the broad > topic into smaller parts that could then be divided into separate > policy efforts of a more manageable size and that might also allow > some less complicated issues to be resolved in a more timely manner > so that some policy changes might be included in the introduction > of new gTLDs. The treatment of reserved names is a matter of > contract for existing gTLDs and will be a matter of contract for > future gTLDs. As such it relates to the work of both the Dec05 PDP > regarding the Introduction of New gTLDs including IDNs and the > Feb06 PDP regarding Contractual Conditions for Existing Registries, > Therefore the WG needs to provide an initial examination of > reserved names at both the top and second level for both existing > and new gTLDs. Should it be determined that the ToR for Feb 06 > does not allow for addressing contractual conditions, the WG report > to the Council regarding relevant recommendations. III. Working > Group Responsibilities, Tasks and Proposed Working Approach A. To > perform its initial examination of the role and treatment of > reserved domain names at the first (top) level, WG responsibilities > and tasks should include but need not be limited to the following: > 1. Review the present treatment and process for > reservation of names at all levels (using Appendix 6 in the latest > gTLD Registry Agreements as examples), including reviewing > treatment of reserved names that may differ in existing contracts - > link provided in Background Section2. Review any other > discussions to date that have occurred related to reserved names > for top level strings for new gTLDs including IDN gTLDs (e.g., the > GNSO's Task Force on new gTLDs; constituency comments, etc.) > 3. Review any ICANN staff reports related to reserved > names - see Background Section4. Review any relevant > technical documents ,e.g., relevant RFCs -see Background Section > and determine what technical outreach (IETF, IAB, SSAC,etc.) is > needed and complete. 5. Liaise with the ICANN staff as > needed, including legal and operational, to identify and review any > existing work or relevant experiences related to reserved names > processes and procedures6. Liaise with the ccNSO and > the ccTLD community in general as needed regarding the two letter > names issues, including whether the present approach, as outlined > in Appendix 6, is sufficient or necessary B. Proposed Working > Approach for Working Group: 1. Initially, examine > the sub-elements of the broad topic of reserved names to consider > breaking the broad topic into smaller parts2. Estimate > the complexity of issues associated with each of the sub-elements > and briefly describe the elements of complexity (e.g., more > controversial issues involving multiple stakeholder groups with > competing views might be rated more complex; consultation with the > GAC might be rated as more complex; etc.)3. Prioritize > the sub-elements according to these two > factors:a. Estimated level of complexity (less > complex to higher)b. Importance/relevance to > complete any future policy work prior to the introduction of new > gTLDsc. Other {to be developed}4. > Identify any sub-elements for which any needed policy work may be > able to be completed in time for the introduction of new gTLDs and > develop recommendations about how that might best be accomplished/ > launch development of recommendations5. Identify the > remaining sub elements and establish a working plan to address > these, including considering parallel work tracks, if feasible and > resources permit, versus sequential work. 6. Prepare > and submit an interim report to the relevant PDP group and/or the > Council so that any additional policy work needed could be started > as soon as possible referencing the Time Line provided by the > Council7. Prepare and submit a final report regarding > all of the above for both PDP groups and the Council upon > conclusion of work.. Regular progress reports should be provided > for both PDP groups and the Council corresponding to scheduled > meetings of those groups and the Council. IV. Example of Topics > for Reserved Names This section provides an example of a work plan > outline for the work of the Working Group. It is provided as an > initial resource for potential use by the Working Group and to > attempt to help to launch the Working Group quickly, due to the > pressures of time limitations. It is not intended to be > comprehensive nor prescriptive. It should be assumed that the work > will need to ask the question of how reserved names apply to IDNs > at both second and first levels, as well as Latin character gTLDs. > 1. Identify possible roles and purposes for reserved > names at the top level and review and examine those roles and > purposes, including how to address the role of reserved names in > IDNs2. Identify and develop proposals to address any > policy issues that should be or are under consideration by the > existing GNSO PDPs regarding policy considerations related to the > role, use, reservation, and release and allocation of reserved > names at the top and second level3. > Determine:a. The various roles that reserved > names may play in new gTLDs in addressing controversial categories > of names, including whether trademark names and country/ > geopolitical names should have initial or permanent reserved > status; etc.b. Whether existing reserved names > at the second level should automatically be included at the first > level orc. Whether there is different treatment > proposed for existing reserved names at the second level, in the > first leveld. Whether reserved name requirements > need to be the same for all gTLDs and, if not, which ones might > varye. Whether there should be a procedure by > which staff publishes new categories of reserved names before > adding them to registry agreements4. Discuss and > review processes by which names could be put into reserved status > at the top level5. Discuss and propose processes by > which names can be unreserved at the top level and made available > for allocation, including discussion of whether there are unique > treatments in allocation for names that are reserved6. > Discuss whether and how categories of names can be unreserved and > allocated at the second level from the existing categories, > including second level reservations in single character[1] and two > character labels, and reservations for geographic and geopolitical > names, to include examination of any existing technical concerns > 7. Reconfirm whether there should be a process by > which new names or categories are added to the reserved status in > the second level (e.g., should we assume that all new strings > allocated for operation as registries are reserved at the second > level when they are awarded?) > Background Materials and Relevant Initiatives to take into > account: Background: 1) Existing Registry Agreements Reserved > Names (Annex 6 and other examples)http://www.icann.org/registries/ > agreements.htm 2) Relevant RFCs which discuss reserved > names http://www.rfc-editor.org/rfc/ > rfc2606.txt http://www.ietf.org/rfc./ > rfc2141.txt http://www.rfc-editor.org/rfc/rfc3491.txt > 3) Status report on single letter names - to be provided Relevant > Initiatives: (1) PDP 05: developing policy recommendations on > newgTLDs, as part of a policy development process called PDP- > Dec05. http://www.gnso.icann.org/issues/new-gtlds/ (2) PDP 06 > [need link] (3) IDN Working Group http://www.gnso.icann.org/issues/ > idn-tlds/issues-report-02aug06.htm > Submitted by: Marilyn Cade and Chuck Gomes > > > > > Attachment 1: Additional considerations: For a policy issue to > warrant a policy development process it mustMeet the following > criteria: (A) Is within the scope of ICANN's mission statement; (B) > is broadly applicable to multiple situations or organizations; (C) > is likely to have lasting value or applicability, albeit with the > need for occasional updates; (D) Will establish a guide or > framework for future decision-making; or (E) Implicates or affects > an existing ICANN policy. > > > > > > > > > > > > <Draft Statement of Work - WG Reserved Names Revised v2.doc>

3 3

General Counsel will be on the GNSO Council call
by GNSO.SECRETARIAT＠GNSO.ICANN.ORG Jan. 18, 2007

Jan. 18, 2007

[To: council[at]gnso.icann.org] Dear Council Members, John Jeffrey, ICANN General Counsel and Sue Jonklaas from the office of the General Counsel will be on the GNSO Council call later on in the day. They will be willing to respond to questions. Please let me know if you need the dial-in number resent. Thank you. Kind regards, Glen -- Glen de Saint Géry GNSO Secretariat - ICANN gnso.secretariat[at]gnso.icann.org http://gnso.icann.org

1 0

Draft Statement of Work for Sunrise Working Group
by Rosette, Kristina Jan. 16, 2007

Jan. 16, 2007

All, Attached please find a draft statement of work for the Sunrise Working Group. Please circulate online any questions, comments, and/or suggestions. We will try to answer, incorporate, and/or organize before the Council Meeting next week. Kristina Rosette and Ute Decker, drafters

4 3