Internet Corporation for Assigned Names and Numbers

ICANN POLICY UPDATE | Volume 11, Issue 3 — March 2011

1 March 2011

PDF Version [651 KB]

Special ICANN 40 "Silicon Valley Meeting in San Francisco" Edition

ICANN 40 Silicon Valley Meeting Logo

http://www.icann.org/en/topics/policy/

CONTENTS:

Across ICANN

  1. Conquer ICANN 40 Schedule Changes with New "Mobile Experience"
  2. Issues Currently Open for Public Comment

ccNSO

  1. Delegation, Redelegation and Retirement WG Posts Final Report for Comment
  2. Incident Response Repository WG Volunteers Needed After Charter Approval
  3. ccNSO to Assist UNESCO with Local Content Survey
  4. ccNSO Council Elects New Chair; APAC Members select new Counselor
  5. Two New Members Raise ccNSO Membership to 113
  6. New Cybercrime and Security Resources Web Page Added
  7. ccNSO Publishes Draft Silicon Valley Public Meeting Agenda

GNSO

  1. Whois Studies and Services Requirement Report to Be Discussed at Silicon Valley
  2. IRTP (Part B) WG Final Report Changed After Public Comments
  3. RAP Recommendations Approved; GNSO Wants Report, Paper and Compliance Input
  4. Post-Expiration Domain Name Recovery Final Report to Incorporate Broad Community Input
  5. GNSO Improvements: New Working Group Guidelines; Comment Sought on Outreach and PDP

ASO

  1. Global IPv4 Address Reclamation Pool and Allocation Plan Moves Forward with RIRs

Joint Efforts

  1. Geographic Regions Review WG Begins Work on Final Report
  2. Other Issues Active as Joint Efforts

At-Large

  1. At-Large Community Prepares for Busy Schedule at Silicon Valley Meeting
  2. Countdown to Completing the ALAC Improvements Begins
  3. At-Large Community Expands to 130 At-Large Structures

SSAC

  1. Security and Stability Advisory Committee (SSAC) Releases 2011 Work Plan
  2. Invitation to Attend Public SSAC Session at the Silicon Valley Meeting

Read in Your Preferred Language

ICANN Policy Update is available in all six official languages of the United Nations. Policy Update is posted on ICANN's website and available via online subscription. To receive the Update in your Inbox each month, visit the ICANN subscriptions page, enter your e-mail address, and select "Policy Update" to subscribe. This service is free of charge.

ICANN Policy Update statement of purpose

Send questions, comments and suggestions to: policy-staff@icann.org.

Policy Supporting Organizations and Advisory Committees

Address Supporting Organization ASO
Country Code Names Supporting Organization ccNSO
Generic Names Supporting Organization GNSO
At-Large Advisory Committee ALAC
Governmental Advisory Committee GAC
Root Server System Advisory Committee RSSAC
Security and Stability Advisory Committee SSAC

Across ICANN

1. Conquer ICANN 40 Schedule Changes with New "Mobile Experience"

For the first time, ICANN has its entire meeting site readily accessible by mobile phones and smart phones. With well over 100 sessions planned at the Silicon Valley meeting in San Francisco, some sessions are subject to last-minute time and location changes. To access the latest, most accurate schedule while on the go, direct your mobile phone's browser to http://me.icann.org (the "me" abbreviates "mobile experience").

The new mobile site, made possible by sponsorship from Neustar, also offers updates on San Francisco weather; provides emergency service numbers; and much more. You can also sort the schedule by your area of interest, with special views (for example) for new attendees, security specialists, or those who want to focus on Board activities.

Wandering the Westin, and not sure where to go next? Try me.icann.org.


2. Issues Currently Open for Public Comment

Numerous public comment periods are open on issues of interest to the ICANN community. Act now for the opportunity to share your views on such topics as:

  • Interim Report of the Internationalized Registration Data Working Group. The Interim Report of the IRD WG summarizes the discussions of the IRD WG to date, provides preliminary recommendations, and seeks input from the community on questions relating to internationalized registration data. Comment period extended to 14 March 2011.
  • ccNSO DRD WG Final Report is posted. The Delegation, Redelegation and Retirement Working Group is soliciting views on whether their recommendations would resolve the short and long term issues identified or whether the community wants to propose alternate recommendations. Please submit comments by 15 March 2011.
  • Proposed Changes to Section 5.0 of the GNSO Council Operating Procedures. The GNSo's Operations Steering Committee (OSC) submitted a revision of Section 5 [PDF, 95 KB] that removes the requirement for Disclosures of Interest, and provides clearer guidance on the contents of Statements of Interest and on updating them in a timely manner. Comment period ends 26 March 2011.
  • Inter-Registrar Transfer Policy Part B Working Group Proposed Final Report contains nine recommendations dealing with the five charter questions it was asked to address, including domain hijacking, the urgent return of an inappropriately transferred name and "lock status." Following review of the public comments received on the Initial Report and further deliberations, the Working Group now presents its proposed Final Report for public comment. The comment period closes on 31 March 2011.
  • The GNSO's Proposed New GNSO Policy Development Process contains 48 recommendations, an outline of the proposed new Annex A, as well as a supporting document to be included in the GNSO Council Operating Procedures as the PDP Manual. Before finalizing its report and submitting it to the GNSO Council for its consideration, the GNSO's PDP Work Team is asking for input. The Public Comment Forum will be open until 1 April 2011.
  • Proposed Framework for the Fiscal Year 2012 (FY12) Operating Plan and Budget provides an overview of the proposed components that will evolve into a full Operating Plan and Budget for 2012. Early and targeted engagement between the ICANN Staff and the leaders of the various SO's, AC's and SG's established an agreed-upon base of services and support that are included in the yearly budget. It is now up to the community to comment on this set of identified priorities and how they should fit into the FY12 plan. The comment period on the plan ends 4 April 11.
  • Draft Proposal for the Study of Issues Related to the Delegation of IDN Variant TLDs is aimed at developing ways to delegate Variant TLDs for the benefit of users in different regions. The comment period on the study proposal for this important issue ends 6 April 2011.
  • The Security, Stability and Resiliency of the DNS Review Team Set of Issues has been posted to solicit input from the community on a set of 10 issues [PDF, 16 KB]. The comment period ends 6 April 2011.
  • Post-Expiration Domain Name Recovery Working Group Proposed Final Report contains 14 recommendations to address five questions about the extent registrants should be able to renew their domain names after they expire. At issue is whether the current policies of registrars on the renewal, transfer and deletion of expired domain names are adequate. Comments on the Final Report close on 7 April 2011.
  • In Proposed Recommendations for a Global Outreach Program the GNSO Operation Steering Committee describes a global GNSO outreach strategy to the public, particularly non-English speakers and those from developing countries/regions, and recommend development of a global outreach program aimed at increasing participation among both current and new members. Comments should be submitted by 10 April 2011.
  • Whois Review Team is seeking community input on their Scope of Work and Roadmap, Outreach and Action Plans, as well as the definitions of "law enforcement," "applicable laws," "producers and maintainers of Whois information," and "consumers." Please submit your comments before 17 April 2011.

For the full list of issues open for public comment, plus recently closed and archived Public Comment Forums, visit the Public Comment page.


ccNSO

3. Delegation, Redelegation and Retirement WG Posts Final Report for Comment

At a Glance

The Delegation, Redelegation and Retirement of ccTLDs WG has posted its Final Report for public comment.

Recent Developments

The ccNSO Delegation, Redelegation and Retirement of ccTLDs WG posted its Final Report for public comment through 15 March 2011. This report includes recommendations to the ccNSO Council including:

  • Initiate a country code policy development process (ccPDP) in time for development of a policy on the retirement of ccTLDs.
  • Establish a working group to provide the ICANN Board and wider community with a Framework of Interpretation (FoI) for the policies on delegation and redelegation of ccTLD's, monitor implementation of the FoI
  • If needed, initiate a ccPDP on delegation and redelegation of ccTLDs.

Next Steps

The WG will publish updated versions of their four full reports (on delegation, retirement, redelegation with and without consent of the incumbent ccTLD manager). After the close of the comment period, the WG will take into account the public input before submitting a Final Report to the ccNSO Council.

Background

The DRD WG advises the ccNSO Council whether it should launch a policy development process to recommend changes to the current policies for delegation, redelegation and retirement of ccTLDs. It considers possible solutions to resolve issues that the DRD WG identifies.

More Information

The WG published its first progress report in February 2010 and subsequent progress reports in June and December 2010. See the charter, progress reports and full reports.

Staff Contact

Bart Boswinkel, ccNSO Senior Policy Advisor


4. Incident Response Repository WG Volunteers Needed After Charter Approval

At a Glance

The ccNSO Council will create a new working group to implement an incident response repository.

Recent Developments

The ccNSO Council decided to create a working group to implement the recommendations of the ccNSO Incident Response Planning Working Group. The new group will focus on finding the most acceptable and optimal solution to implement, operate and maintain a contact detail repository.

Next Steps

At the Silicon Valley meeting, the ccNSO council will discuss and vote on the charter of this working group. Once a charter is adopted, the ccNSO council will call for volunteers.

Background

At the Cartagena meeting, the Incident Response Planning Working Group submitted its final report. The council discussed the recommendations of the WG at its conference call on 1 March 2011. The Incident Response WG was created to develop sustainable mechanisms for the engagement of and interaction with ccTLD registries during incidents that may affect the DNS.

More info

Final Report of the incident response WG [PDF, 284 KB]

Staff Contact

Bart Boswinkel, ccNSO Senior Policy Advisor


5. ccNSO to Assist UNESCO with Local Content Survey

At a Glance

ccNSO will assist UNESCO (United Nations Education, Scientific and Cultural Organization) with a survey on local content creation and local infrastructure.

Recent Developments

The ccNSO Council was approached by UNESCO to assist in conducting a survey. The survey results will help UNESCO prepare a comprehensive study on local content creation and local Internet infrastructure.

Next Steps

Individual ccTLD managers have been approached to respond to the survey and respond to UNESCO.

Staff Contact

Bart Boswinkel, ccNSO Senior Policy Advisor


6. ccNSO Council Elects New Chair; APAC Members Select New Counselor

At a Glance

The ccNSO Council unanimously elected a new ccNSO Chair. The Asia-Pacific ccNSO members selected a new ccNSO Counselor.

Recent Developments

The ccNSO council has unanimously elected Lesley Cowley, .uk (United Kingdom) as the new ccNSO Chair. The Asia-Pacific members have selected Keith Davidson, .nz (New Zealand) to represent their region on the ccNSO council.

Next Steps

Lesley Cowley will replace Chris Disspain, .au (Australia), who is stepping down from his position on 18 March 2011. Keith Davidson will take his seat on the ccNSO Council on 19 March 2011.

Background

Chris Disspain (.au) will take a seat on the ICANN Board in June 2011, and therefore had to step down as Chair of the ccNSO Council. With his departure, a replacement had to be found and the Council selected Lesley Cowley for the ccNSO Chair position. Keith Davidson, .nz (New Zealand) was nominated and seconded to represent Asia-Pacific on the council.

More Information

Staff Contact

Gabriella Schittek, ccNSO Secretariat


7. Two New Members Raise ccNSO Membership to 113

At a Glance

Two new members, The Democratic Republic of Congo and Ukraine, have joined the ccNSO.

Recent Developments

The newest ccNSO members are.cd (Democratic Republic of Congo) and .ua (Ukraine) bringing the membership to 113.

More Information

Staff Contact

Gabriella Schittek, ccNSO Secretariat


8. New Cybercrime and Security Resources Web Page Added

At a Glance

A new Resources Section on the ccNSO web site has been launched which provides links to important security and cybercrime web sites and resources.

Recent Developments

A new resource section on Cybercrime and Security was launched on the ccNSO website with links to security blogs, CERT sites (Computer Emergency Response Teams), security forums, ICANN security resources and security industry sites.

Next Steps

ccNSO plans to continue building the section by adding relevant resources, including community-submitted material.

Background

The ccNSO Participation Working Group suggested in their Final Report (February 2009) that the ccNSO should build a "Resources" page with resources that ccTLDs could share and use. Until now, only Resources such as Legal, Policy, Marketing and Technical Resources were listed. The Cybercrime and Security section is a new addition.

More Information

Staff Contact

Gabriella Schittek, ccNSO Secretariat


9. ccNSO Publishes Draft Silicon Valley Public Meeting Agenda

At a Glance

ccNSO published a draft Silicon Valley meeting agenda and other meeting-related information.

Recent Developments

The ccNSO draft meeting agenda for Silicon Valley meeting in San Francisco together with other meeting preparation material (such as summaries of presentations and ccNSO pre-registration lists) has been published.

Next Steps

Updates to all sections will be made prior to and throughout the meeting.

More Information

Staff Contact

Gabriella Schittek, ccNSO Secretariat


GNSO

10. Whois Studies and Services Requirement Report to Be Discussed at Silicon Valley

At a Glance

Whois is the data repository containing registered domain names, registrant contacts, and other critical information. Because of the global scale and critical importance of Whois, adjustments to it must be handled with great care. Questions persist concerning the use and misuse of this important public resource. The GNSO Council is considering four studies to provide current, reliable information for community discussions about Whois.

Recent Developments

ICANN staff members have completed scoping of all proposed studies for cost and feasibility; the GNSO Council will discuss these studies as well as the Whois Service Requirements Report at the Silicon Valley meeting.

The Whois studies under consideration are grouped into four broad categories:

  • Whois Misuse. This study is to discover to what extent public Whois information is used for harmful purposes. ICANN issued a Request for Proposals (RFP) in September 2009, asking qualified researchers to estimate the costs and feasibility of conducting these studies. The GNSO Council plans to proceed with this study and to announce the research firm selected shortly.
  • Whois Registrant Identification. This effort would examine the extent to which domain names registered by legal persons or for commercial purposes are not clearly represented in Whois data. ICANN issued an RFP, and staff members prepared an analysis of vendor responses for GNSO Council and community consideration. The Council is still considering whether this study should be conducted.
  • Whois Proxy and Privacy Services Abuse Study. This study would focus on the extent to which domain names used to conduct illegal or harmful Internet activities are registered via privacy or proxy services to obscure the perpetrator's identity. ICANN staff posted an RFP on 20 May 2010 to engage independent research organizations to undertake this study. Three responses were received. More Information was requested of those submitting the strongest responses. Staff has analyzed this information and the GNSO Council is now considering next steps. A link to the staff analysis is below.
  • Whois Proxy and Privacy Services Reveal Study. This study would measure proxy and privacy service responsiveness to registrant "identity reveal" requests. An RFP to conduct this study was posted in September 2010 but no bids were received. ICANN staff found that potential bidders had significant concerns with the feasibility of this study, and whether a pool of able volunteers would be willing to participate, given concerns about the sensitivity of data to be shared. To address this concern, staff is proposing that a feasibility survey be conducted to clarify the uncertainties and determine whether a full study would be possible. A link to the most recent staff report is provided below.

At its public meeting in Silicon Valley, the GNSO Council plans to discuss a Whois Service Requirements Report, which was completed last year. This report is a comprehensive list of Whois service requirements based on current policies and previous policy discussions, but does not make policy recommendations.

Some potential requirements included in this report are:

  • A mechanism to find authoritative Whois servers
  • Structured queries
  • A standardized set of query capabilities
  • A well-defined scheme for replies
  • Standardized error messages
  • Improved quality of domain registration data
  • Internationalization
  • Security elements
  • Thick vs. thin Whois
  • A registrar abuse point of contact

More Information

Staff Contact

Liz Gasster, Senior Policy Counselor


11. IRTP (Part B) WG Final Report Changed After Public Comments

At a Glance

The aim of the Inter-Registrar Transfer Policy (IRTP) is to provide a straightforward procedure for domain name holders to transfer their names from one ICANN-accredited registrar to another. The Inter-Registrar Transfer Policy (IRTP) Part B working Group proposed the Expedited Transfer Reverse Policy (ETRP). The ETRP is a fast "reverse transfer" process to return a recently sold domain name to its original owner if it is hijacked, and to correct fraudulent or erroneous transfers.

Recent Developments & Next Steps

Following the review of the public comments received on the Initial Report [PDF, 764 KB], the IRTP Part B Working Group has now finalized its recommendations. This proposed Final Report [PDF, 733 KB] contains nine recommendations including a Registrar Emergency Action Channel, an Issue Report on "Thick" Whois, an Issue Report on "‘Change of Control" function, the modification of denial reasons #6 and #7 of the IRTP, and clarification of Whois status messages in relation to Registrar Lock Status.

The proposed recommendations in the Initial Report were changed substantially following a review of the public comments and continued deliberations, so the WG decided to request another round of public comments. The WG is organizing a session during the Silicon Valley meeting during which it will present the proposed recommendations and allow for Community questions and discussion. Following the closing of the public comment, the WG will review the comments received and finalize the report for submission to the GNSO Council. For further information, please consult the IRTP Part B WG Workspace.

Background

The aim of the Inter-Registrar Transfer Policy (IRTP) is to provide a straightforward procedure for domain name holders to transfer their names from one ICANN-accredited registrar to another. The GNSO Council established a series of five working groups (Parts A through E) to review and consider various revisions to this policy.

The IRTP Part B PDP WG published its Initial Report last year, presenting several preliminary conclusions and recommendations for community input, including a proposed Expedited Transfer Reverse Policy (ETRP). The ETRP is a fast "reverse transfer" process to return a recently sold domain name to its original owner if it is hijacked, and is designed to correct fraudulent or erroneous transfers. It does not address or resolve disputes arising over domain control or use.

The IRTP Part B PDP is the second in a series of five PDPs addressing areas for improvement in the existing Inter-Registrar Transfer Policy. The working group addresses five issues focusing on domain hijacking, the urgent return of an inappropriately transferred name, and lock status. For further details, refer to the group's Charter.

More Information

Staff Contacts

Marika Konings, Senior Policy Director


12. RAP Recommendations Approved; GNSO Wants Report, Paper and Compliance Input

At a Glance

Registries and registrars lack uniformity when dealing with domain name registration abuse, and questions persist about what activities constitute "registration abuse." The GNSO Council launched the Registration Abuse Policies Working group (RAP) WG) to examine registration abuse policies. After reviewing the RAP WG's proposed approach, the GNSO Council is moving ahead with several RAP recommendations.

Recent Developments & Next Steps

The GNSO Council reviewed and discussed the proposed approach of the Registration Abuse Policies (RAP) Implementation Drafting Team (DT) at its working session in Cartagena. At its February 2011 meeting, the Council decided to move ahead with a number of the RAP Recommendations, including:

  • Request an Issue Report on the current state of the Uniform Domain-Name Dispute-Resolution Policy (UDRP).
  • Request a discussion paper on the creation of non-binding best practices to help registrars and registries address the abusive registration of domain names.
  • Move forward on two recommendations that will require input from ICANN Compliance:
    1. Whois Access recommendation #2 requiring the ICANN Compliance Department to publish more data about Whois accessibility, at minimum, annually. This data should include a) the number of registrars that show a pattern of unreasonable restriction of access to their port 43 Whois servers, and b) the results of an annual audit of compliance with all contractual Whois access obligations.
    2. Fake Renewal Notices recommendation #1, which suggests that the GNSO refer this issue to ICANN's Contractual Compliance department for possible enforcement action, including investigation of misuse of Whois data.
  • The GNSO Council has instructed ICANN Policy Staff to "add the remaining RAP Recommendations to the GNSO Project List so that the Council can keep track of the remaining recommendations and address these as appropriate."

ICANN Compliance Staff provided the GNSO Council with its feedback on Whois Access recommendation #2 and Fake Renewal Notices recommendation #1. The Council is expected to discuss the feedback received as well as an initial outline of the Issue Report on the current state of the UDRP at its Silicon Valley meeting (see the meeting schedule for further details).

Background

The RAP WG presented its final report [PDF, 1.7 MB] and recommendations to the GNSO Council in June 2010. The Council then formed a group of volunteers, the Registration Abuse Policies Implementation Drafting Team (RAP DT), to draft a proposed approach to implementing the report's recommendations. The Registration Abuse Policies (Implementation Drafting Team developed a matrix categorizing the RAP WG final report [PDF, 1.7 MB] recommendations in order of priority, expected complexity and required resources and submitted a letter [PDF, 184 KB] to the GNSO Council outlining a recommended approach for its consideration. See the web site for further information.

A short history of the RAP WG is available on ICANN's website.

More Information

Staff Contacts

Marika Konings, Senior Policy Director and Margie Milam, Senior Policy Counselor


13. Post-Expiration Domain Name Recovery Final Report to Incorporate Broad Community Input

At a Glance

Should registrants be able to reclaim their domain names after they expire? At issue is whether the current registrar policies regarding the renewal, transfer and deletion of expired domain names are adequate.

Recent Developments

After completing its review of community comments on the initial GNSO Post-Expiration Domain Name Recovery (PEDNR) report [PDF, 1 MB] and the accompanying survey [PDF, 948 KB], the Working Group has updated the report and developed specific recommendations. The proposed Final Report [PDF, 971 KB] was published for comment on 21 February 2011.

The proposed Final Report contains 14 recommendations including:

  • Providing a minimum of eight days after expiration for renewal by registrant.
  • Having unsponsored gTLDs and registrars offer Redemption Grace Periods (RGP).
  • Requiring posting of fees charged for renewal; requiring that at least two notices prior to expiration are sent at set times, one after expiration; that an expired website must explicitly say that registration has expired, and offer instructions on how to redeem the domain.
  • Development of education materials about how to prevent unintentional loss.

A Public Comment Forum will be open until 7 April to accept community input before submission to the GNSO Council for its consideration. The WG is organizing a presentation and discussion of the proposed Final Report in San Francisco at the Silicon Valley Public meeting.

Background

The PEDNR PDP WG published its Initial Report on 31 May 2010 – (see the related community Public Comment Forum). In addition, a survey asked several specific questions about renewal and expiration practices. Nine community comments from nine individuals were submitted, including comments from representatives of the Registrars and Registries Groups, ALAC, and the Commercial and Business Users Constituencies. More than 400 survey responses were received (see summary and analysis).

For a history of the ICANN community's policy development activities related to Post-Expiration Domain Name Recovery, please refer to the PEDNR background page.

More Information

Staff Contact

Marika Konings, Senior Policy Director


14. GNSO Improvements: New Working Group Guidelines; Comment Sought on Outreach and PDP Recommendations

Steering Committee Finalizing Working Group Guidelines; PDP and Outreach Proposals Now Available for Public Comment

At a Glance

Members of the Generic Names Supporting Organization (GNSO) community are working to implement a comprehensive series of organizational changes designed to improve the effectiveness and accessibility of the organization.

The materials in this section relate only the most recent developments regarding implementation of the GNSO Improvements. We hope this streamlined format will allow readers to identify quickly the most recent developments in this area.

To understand the GNSO's new structure and organization, see the discussion and diagrams on the GNSO Improvements Information webpage (GII webpage). For the reasons and history motivating the improvements, see the Background page. The Staff has also created a series of new "dashboard" page for a quick review of implementation activities. There is a Status page and a Timeline Page that are connected to the GII webpage.

Recent Developments

Policy Process Steering Committee Finalizing GNSO Working Group Guidelines

A S ummary and Analysis of the Public Comments regarding the Proposed GNSO Working Group Guidelines was submitted to the GNSO Council for consideration. The Council passed the comments back to the Policy Process Steering Committee ( PPSC) for review. An updated version of the WG Guidelines has been circulated for review by the PPSC and the updated document will be submitted to the Council for adoption at the Silicon Valley meeting. Staff has also been requested to develop a summary of this document for use by WG members once the guidelines have been approved by the GNSO Council.

More Information

 

Final Report Outlines New GNSO Policy Development Process

The GNSO Council's Policy Development Process Work Team (PDP WT) has published its proposed Final Report outlining the new GNSO Policy Development Process. The report contains 46 recommendations, the proposed new Annex A and a PDP Manual. A Public Comment Forum will be open until 1 April. A presentation and discussion of the report and recommendations will be held on Wednesday, 16 March during the ICANN Silicon Valley Meeting.

More Information

Staff Contact

Robert Hoggarth, Senior Policy Director

 

Charter Work for New Implementation Standing Committee Under Way

The GNSO Council has determined that a Standing Committee will be formed to oversee the implementation of improvements prompted by the GNSO Review process. The Council has formed a drafting team that is currently working to develop a charter for the Standing Committee.

 

GNSO Council Seeks Comment on Global Outreach Strategy

In February 2011, the GNSO Council invited the community to provide comments in the public forum on proposed recommendations for a global outreach program. The GNSO Council will review comments and incorporate feedback into their recommendations.

The recommendations developed by the GNSO and published for comment describe a global outreach strategy to relevant members of the public, particularly non-English speakers and those from developing regions; and for development of a global outreach program aimed at increasing participation from both current members of the ICANN community as well as potential members, particularly non-English speakers.

Public comment on the global outreach strategy is another step in the implementation of GNSO Improvements, initiated in October 2009 as identified and approved by the ICANN Board. The Board recommended that the GNSO should develop and implement a targeted outreach program to explore the formation of new constituency groups.

Staff Contact

Julie Hedlund, Director, SSAC & Policy Support

 

GNSO Council Takes Steps to Refine its Statement of Interest Procedures

Late in 2010, the GNSO Council identified areas for improvement in Section 5, Statements of Interest, in its GNSO Council Operating Procedures [PDF, 417 KB] that would simplify and clarify the procedures. The GNSO Council tasked its Operations Steering Committee, which oversees changes to the Council's procedures, with completing a revision to improve Section 5.

Last month, the OSC submitted a revised Section 5 [PDF, 95 KB] that removes the requirement for Disclosures of Interest, and provides clearer guidance on the contents of Statements of Interest and on updating them in a timely manner. The document has been posted in the ICANN Public Comment Forum

 

Board Committee Seeks to Improve Process for Recognition of New GNSO Constituencies

At the direction of the ICANN Board's Structural Improvements Committee (SIC), the ICANN Staff conducted a 30-day public consultation forum for community comments concerning the elements of a proposed new "Process for Recognition of New GNSO Constituencies", including its procedures, sequences/steps, forms, tools and evaluation criteria.

Background

In June 2008, the ICANN Board of Directors endorsed a series of recommendations concerning how to improve the GNSO's structures and operations. Among the recommendations endorsed by the Board was that ICANN take steps to clarify and promote the option to self-form new GNSO Constituencies as provided in the ICANN Bylaws, Article X, Section 5(4).

Recognizing that the Bylaws do not contain specific procedural guidance concerning how an interested party might formulate a new Constituency petition, the Board directed Staff in late 2008 to develop a set of procedures that a prospective organizer could follow in submitting a petition to become recognized as a new GNSO Constituency. To date, five prospective Constituency groups have submitted formal New GNSO Constituency petitions in accordance with the process; however, the Board has yet to approve any of those applications.

To address concerns it had regarding the clarity and timing of the original New Constituency petitioning procedure, the Structural Improvements Committee (SIC) embarked on this effort last year and, working with Staff, has completed development of a replacement "Process for Recognition of New GNSO Constituencies." The proposed process significantly modifies the original procedure and is designed to:

  • Optimize the considerable time and effort required to form, organize, and propose a new GNSO Constituency by prescribing a streamlined sequence of steps and associated evaluation criteria that are objective, fair, and transparent --; with ample opportunity for community input ;.
  • Delegate more authority to each GNSO Stakeholder Group in evaluating new Constituency proposals, while maintaining the Board's oversight role.
  • Manage the entire process to a flexible, but specific and limited timeframe ; and.
  • Provide a partial set of criteria for use during the periodic review of the GNSO.

The Public Forum Announcement provides a broader discussion of the background leading to the Public Forum as well as a brief overview of the proposed process.

For more information

Staff Contact

Robert Hoggarth, Senior Policy Director

 

GNSO Web Site Improvement Enters Next Phase

The ICANN Staff is working on the new GNSO web site, based on improvements approved by the GNSO Council last year. ICANN's web team received the new site's design and code from its contractor, and verified that it works perfectly. Staff is now working on moving and creating content for the new site, using the designs debuted in Cartagena (see a copy of the presentation, including screen shots of web frame design pages, here [PDF, 2.01 MB]). The redesigned site will feature more help for new GNSO visitors than the previous site. Review of the new site content will start soon.

More Information

GNSO Improvements Information Web Page


ASO

15. Global IPv4 Address Reclamation Pool and Allocation Plan Moves Forward with RIRs

At a Glance

Now that the Internet Assigned Numbers Authority (IANA) has allocated all the addresses in IPv4, Regional Internet Registries (RIRs) are discussing a proposed global policy for handling IPv4 address space returned from the RIRs to IANA. Under the proposal, IANA would establish a Reclamation Pool of returned address space and, because the free pool of IANA IPv4 address space is depleted, allocate IPv4 address space from this Reclamation Pool to the RIRs in smaller blocks than previously allocated.

Recent Developments

The proposal to establish a Reclamation Pool of returned IPv4 address spaces and allocate them in smaller blocks to the RIRs was discussed by all RIRs at their most recent meetings. The American Registry for Internet Numbers (ARIN) has adopted the proposal. It is in the discussion stage of the policy development processes in the other RIRs.

Next Steps

When the proposal has been adopted by all RIRs, the Number Resource Organization Executive Committee (NRO EC) and the Address Supporting Organization Address Council (ASO AC) will review the proposal and forward the policy to the ICANN Board for ratification and implementation by IANA.

Background

IPv4 is the Internet Protocol addressing system used to allocate unique IP address numbers in 32-bit format. With the massive growth of the Internet user population, the pool of unique numbers (approximately 4.3 billion) is depleted and a 128-bit numbering system (IPv6) will take its place.

The proposed global policy replaces an earlier two-step proposal that did not garner global consensus. The Reclamation Pool will be declared active as soon as the first RIR exhausts its inventory of IPv4 address space, according to threshold criteria defined in the proposal. IANA will, once each quarter, allocate available address blocks from the Reclamation Pool evenly to all RIRs that are eligible for allocations at that time.

More Information

Staff Contact

Olof Nordling, Director Services Relations


Joint Efforts

16. Geographic Regions Review WG Begins Work on Final Report

Workshop Scheduled For Silicon Valley Meeting

At a Glance

The Geographic Regions Review Working Group (WGGR) is working to identify the different purposes for which ICANN's Geographic Regions are used, determine whether the uses of the Geographic Regions framework continue to meet the requirements of community members and to consider making recommendations relating to the current and future uses and definition of the ICANN Geographic Regions.

Recent Developments

The community-wide WGGR posted its Interim Report for community review prior, during and after the ICANN Cartagena public meeting. The Public Comment Forum recently closed on 30 January and a Staff Summary & Analysis of the submitted comments has been posted in the forum.

Copies of the Interim Report in all six UN languages can be found at the following links:

The WG held a community workshop at the ICANN Cartagena public meeting and another one is scheduled for the ICANN Silicon Valley Public Meeting in San Francisco.

To facilitate its discussion, the WG is utilizing a topic/issues matrix that has been successfully employed in other community working groups. See a copy of the latest working matrix document can be found here – Final Report Draft Issues Matrix (v2) [PDF, 124 KB].

Next Steps

The WG has begun drafting its Final Report. The workshop in San Francisco will help the WG in its drafting efforts. The Final Report, which will include the working group's recommendations (if any), is being planned for publication later this year.

Background

The WG completed its Initial Report in late July 2009 and published the document in all six UN languages for community review and comment.

Click here for further background.

For More Information

Staff Contact

Robert Hoggarth, Senior Policy Director


17. Other Issues Active as Joint Efforts

Increasingly, individual ICANN Supporting Organizations and Advisory Committees have pursued bilateral and multi-lateral discussions regarding matters of common or overlapping interest in recent years. Some of the current issues being discussed include:


At-Large

18. At-Large Community Prepares for Busy Schedule at Silicon Valley Meeting

At a Glance

For months, the At-Large community has used its bottom-up process to develop the structure, format, and content of the At-Large sessions to be held during the ICANN Silicon Valley meeting. As a result, there will be 21 community sessions during the weeklong meeting. This is the largest number of At-Large sessions that the community has ever held at an ICANN Meeting.

Recent Developments

At-Large Meetings scheduled include:

  • ALAC and Regional Leadership Working Sessions 1 and 2
  • At-Large Meetings with the ICANN Board (lunch) GAC, the SSAC, and Registrars
  • NARALO, LACRALO, APRALO Monthly Meetings
  • A NARALO Showcase with Dr. Vint Cerf as keynote speaker
  • Meetings of the At-Large Improvements Working Teams A, B, C, and D
  • Two Policy Discussion Sessions
  • An At-Large Regional Secretariats Meeting
  • An AFRALO/AfrICANN Joint Meeting
  • An ALAC and Regional Leadership Wrap-Up Meeting
  • An ALAC Executive Committee Meeting

These meetings are not just for At-Large community representatives; all sessions are open to all attendees. In addition, the At-Large community members will also participate actively in many of the other meetings taking place during the ICANN Silicon Valley meeting either in person or by using remote participation tools.

Due to the number of sessions, schedules can change at the last minute. Attendees can remain informed of the latest schedule on ICANN's new "mobile experience" meeting site. Direct your mobile phone's browser to http://me.icann.org (the "me" abbreviates "mobile experience").

More Information

  • The schedule of At-Large Meetings by day
  • The entire list of At-Large Meetings, including links to agendas in English, French and Spanish and remote participation instructions

Staff Contact

ICANN At-Large Staff


19. Countdown to Completing the ALAC Improvements Begins

Four Improvements WTs Scheduled to Present Draft Implementation Proposals at Silicon Valley Meeting

At a Glance

The ALAC/At-Large Improvements Project is on schedule for a successful conclusion at the end of March. This would make it the first SO or AC Improvements Project to close up shop – thanks to At-Large's four Improvements Work Teams (WTs).

Background

The ALAC/At-Large Improvements project grew out of the ALAC's 2008 independent review, mandated by ICANN's Bylaws. Based on the findings of this review and the input from two public comment periods, the Board Governance Committee (BGC)-appointed Review Working Group on ALAC Improvements developed 13 recommendations, published in its Final Report [PDF, 270 KB] of June 2009.

These recommendations can be divided into four areas of ALAC and At-Large improvement. Consequently, the ALAC established four WTs, each focused on one of these areas. They are:

  • WT A on clarifying ALAC's continuing purpose within the ICANN Bylaws (see WT A's Workspace);
  • WT B on increasing ALS participation and removing related barriers (see WT B's Workspace);
  • WT C on reviewing and improving ALAC and At-Large planning processes (see WT C's Workspace); and
  • WT D on enhancing ALAC's policy advice processes (see WT D's Workspace).

Next Steps

With members from all five of At-Large's Regional At-Large Organizations (RALOs), each At-Large Improvements WT began meeting in September 2010. Six months later, the WTs are heading toward ICANN's 40th International Public Meeting in Silicon Valley, ready to conclude their work.

The ALAC and RALO officers have dedicated a significant amount of the At-Large calendar in Silicon Valley to the At-Large Improvements Project. During the ALAC and Regional Leadership Working Session on Sunday, 13 March, the four Improvements WTs are scheduled to present their draft implementation proposals to the ALAC and At-Large membership and receive feedback during a two-hour session. On Thursday, 17 March, during the ALAC & Regional Leadership Wrap-Up, the WTs are scheduled to present their final proposals to the ALAC.

Here is a preview of the WTs' specific proposals:

  • WT A will propose revisions to the ICANN Bylaws that strengthen the mandate of the ALAC and At-Large, as the ICANN's primary home of individual Internet users, to offer policy and other advice, act as a tool of ICANN's accountability, and conduct outreach.
  • WT B will propose a series of new training and communication initiatives for the ALS's, many tailored to their specific regions.
  • WT C will propose improvements to the ALAC's strategic, operational, and budgetary planning, specifically geared toward enhancing participation by the regions and ALS's in these processes.
  • WT D will propose improvements to the ALAC's policy advice development (PAD) process, including multiple points at which extensions can be requested, more policy input from the ALS's, and the availability of more accessible background material.

Many of the WTs will be presenting their proposals in the context of flowcharts depicting revamped ALAC and At-Large processes, such as this detail from WT D's proposed new ALAC PAD:

Flowchart of At-Large Improvements Work Team D's proposed new ALAC PAD

For more information

For further details on the ALAC/At-Large Improvements project, see these additional resources:

Staff Contact

Seth Greene, At-Large Improvements Project Manager


20. At-Large Community Expands to 130 At-Large Structures

At a Glance

The Cook Islands Internet Action Group has been accredited to the At-Large community as an At-Large Structure ("ALS"), bringing the total number of ALSs to 130.

Recent Developments

The At-Large Advisory Committee (ALAC) has certified the Cook Islands Internet Action Group (CIIAG) as an At-Large Structure (ALS). The certification included due diligence carried out by ICANN staff and regional advice provided by the Asia, Australasia and Pacific Islands Regional At-Large Organization (APRALO).

  • Cook Islands Internet Action Group (CIIAG) [PDF, 117 KB], based in Avarua, Rarotonga, Cook Islands consists of 43 Internet users, most of whom live on Rarotonga Island and work in both the public and the private sector. CIIAG works to promote the development of effective policies to ensure quality broadband and mobile services and to encourage equitable and affordable access to the Internet. CIIAG is also actively engaged in technical capacity building to ensure that the Cook Islands can fully utilize the potential the Internet brings to small, remote Island states.

Background

One of the strengths of the At-Large community is that it incorporates the views of a set of globally diverse, Internet user organizations. The views of these grassroots organizations are collected through an internal policy development process and find representation in the official documents of the ALAC.

More Information

Staff Contact

Matthias Langenegger, At-Large Secretariat


SSAC

21. Security and Stability Advisory Committee (SSAC) Releases 2011 Work Plan

Review of registry transition program, study of spoofed IP addresses and registrant risk analysis part of the plan

At a Glance

The SSAC prepares a work plan each year to present ideas and preliminary work prior to developing specific project plans. The 2011 Plan has now been published.

Recent Developments

The SSAC has published its 2011 Work Plan [PDF, 114 KB]. The Work Plan for 2011, presents the ideas and preliminary work to develop specific project plans. This is important because it provides notice to the community of issues on the horizon. For 2011, those issues include an SSAC review of ICANN's registry transition program; a study of current trends in using spoofed IP addresses for malicious traffic; and an analysis of the risks a registrant must manage to reduce the possibility of losing the zone file information associated with a domain name.

The Report also provides a brief description of the work products completed by the SSAC in 2010.

More Information

Staff Contact

Julie Hedlund, Director, SSAC & Policy Support


22. Invitation to Attend Public SSAC Session at the Silicon Valley Meeting

At a Glance

At the ICANN Silicon Valley meeting, the SSAC will hold a public session, two sessions on DNS security (DNSSEC), and will co-host a public meeting with GNSO on the Internationalized Registration Data Working Group.

Background

Topics at the Public Meeting on March 15 will include:

  • SSAC Review: Registry Transition
  • Source Address Validation
  • DNS Zone Risk Analysis
  • SSAC Improvements and Outcomes

The SSAC will also hold two sessions on DNS security (DNSSEC). The first is a session on Monday, 14 March for those unfamiliar with DNSSEC entitled, "DNSSEC for Everybody: A Beginner's Guide." During this interactive session, we hope to demystify DNSSEC and show how to easily and quickly deploy DNSSEC into a business.

The second session is a DNSSEC workshop on Wednesday, 16 March with public presentations, panels, and discussion with those actively engaged in the deployment of DNSSEC.

In addition, the SSAC — together with the GNSO — will hold a public session of the Internationalized Registration Data Working Group that will provide a brief update on the comments received on the Group's Interim Report.

More Information

See the SSAC schedule of meetings

Staff Contact

Julie Hedlund, Director, SSAC & Policy Support

update-mar11-en [PDF, 667kB]

Stay Connected

  • News Alerts:
  • Newsletter:
  • Compliance Newsletter:
  • Policy Update: