Internet Corporation for Assigned Names and Numbers

ICANN POLICY UPDATE | Volume 09, Issue 06 – June 2009

1 June 2009

PDF Version [200 KB]

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

CONTENTS:

  1. YOUR INPUT NEEDED NOW ON POLICY-RELATED ISSUES
  2. CCNSO TO EXPLORE CCTLD DELEGATION AND RELATED POLICIES
  3. CCNSO ADDS NEW MEMBERS
  4. CCNSO SEEKS REGISTRY PROFILE INFORMATION
  5. GNSO IMPROVEMENTS IMPLEMENTATION ADVANCES WITH FOCUS ON STAKEHOLDER GROUP CHARTERS
  6. GEOGRAPHIC REGIONS REVIEW CHARTER REVISED AND READY FOR BOARD APPROVAL
  7. RIRS DISCUSS GLOBAL POLICY PROPOSAL FOR RECOVERED IPv4 ADDRESS SPACE
  8. SSAC STUDIES, REVIEWS AND ACTIVITIES ADVANCE
  9. WORK UNDER WAY ON GNSO COUNCIL WHOIS REQUIREMENTS
  10. REGISTRATION ABUSE POLICIES GET CLOSER LOOK
  11. GNSO CONSIDERS EXPIRED DOMAIN NAME RECOVERY CHANGES
  12. MAKING IT EASIER TO TRANSFER DOMAINS BETWEEN REGISTRARS
  13. HOW DO WE DEAL WITH FAST FLUXING CYBERCRIMINALS?
  14. AT-LARGE COMMUNITY WELCOMES NEW USER GROUPS
  15. AT-LARGE COMMUNITY ACTIVE ON MANY POLICY FRONTS

The ICANN Policy Update contains brief summaries of issues being addressed by the ICANN community’s bottom-up policy development structure, as well as information on related policy development activities. ICANN’s Policy Staff publishes these monthly updates to maximize transparency and encourage broad community participation in ICANN’s policy development activities.

Links to additional information are included and readers are encouraged to go beyond these brief summaries to learn more about the ICANN community’s work. As always, the Policy Staff welcomes comments and suggestions on how to improve its policy communications efforts. Please send these comments to policy-staff@icann.org.

ICANN Policy Update Available in Russian, Chinese, Arabic, French, Spanish, English

The ICANN Policy Update is available in all six official languages of the United Nations: English (EN), Spanish (ES), French (FR), Arabic (AR), Chinese (Simplified -- siZH), and Russian (RU). The Policy Update is posted on ICANN’s website and available via online subscription. If you would like us to send these updates directly to your inbox each month, simply go to the ICANN subscriptions page, enter your e-mail address, and select "Policy Update" to subscribe. This service is free of charge to subscribers. More information is available at:

What’s on the Calendar for Today?

Keep up-to-date on what’s happening in ICANN policy development by visiting the online calendars of ICANN’s policy development and advisory bodies. Three of the most active calendars include:


1. YOUR INPUT NEEDED NOW ON POLICY-RELATED ISSUES

Numerous public comment periods are open on issues of interest to the ICANN community (check here for a complete list). Act now for the opportunity to share your views on such items as:


2. CCNSO TO EXPLORE CCTLD DELEGATION AND RELATED POLICIES

At a Glance

The Council of the country code Names Supporting Organization (ccNSO) has approved a working group to advise the ccNSO Council on launching a policy development process on the delegation, re-delegation and retirement of ccTLDs

Recent Developments

The ccNSO revisited the need to review and update the current policy for the delegation, re-delegation and retirement of country code Top Level Domains at the Mexico City ICANN meeting. It concluded that as a first step, a working group needed to be established to better understand the scope and issues involved, and to ensure involvement of the GAC as they have an interest in the topic as well.

Next Steps

The ccNSO Secretariat will send out a call for members and observers to the working group. The ccNSO Council expects to appoint members to the working group at its Sydney meeting.

Background

Currently the ICANN policy and practices for delegation and re-delegation are reflected in established IANA processes. In carrying-out these processes, IANA follows the ISO 3166-1 list of country-codes published by the ISO 3166 Maintenance Agency. For more information about establishing new ccTLDs, see the IANA’s Procedures for Establishing ccTLDs and IANA’s delegation reports.

Re-delegation of ccTLDs is the process of changing the designated manager(s) of a ccTLD. This process is conducted according to the principles described in ICP-1 and RFC 1591. The policy and process are also reflected in IANA reports that illustrate many of the considerations made in deciding whether or not to re-delegate.

In light of the changed environment and circumstances since RFC 1591 was established in 1994 and refined in 1999, the ccNSO considered it time to review the current policies. The ccNSO wants a better understanding of the issues, if any, relating to the current policies, before taking possible further steps.


3. CCNSO ADDS NEW MEMBERS

At a Glance

The country code Names Supporting Organisation (ccNSO) welcomes two new members.

Recent Developments

.vu (Vanuatu) and .lv (Latvia) have been approved as new ccNSO members. The ccNSO now counts 93 ccTLD operators as members, having added 16 new members in the last year.

More information

Staff Contact

Gabriella Schittek, ccNSO Secretariat


4. CCNSO SEEKS REGISTRY PROFILE INFORMATION

At a Glance

The ccNSO has started to post "Profile" information of each ccTLD registry member to make easier to contact and learn about ccNSO members.

Recent Developments

The ccNSO Secretariat is working with ccNSO members to gain profile information on registries. The information gathering is intended to facilitate interaction with and between registry operators.

Background

The ccNSO Participation Working Group recommended Member Profile pages in their final report. An email was sent to the ccNSO members’ list on 4 June 2009 encouraging all members to submit their profile details. The questions asked include: full name of registry, contact details, founding date, registration model, number of domain names, and history. Filling out the profile is not compulsory nor do all questions need to be answered.

More Information

Staff Contact

Gabriella Schittek, ccNSO Secretariat


5. GNSO IMPROVEMENTS IMPLEMENTATION ADVANCES WITH FOCUS ON STAKEHOLDER GROUP CHARTERS

At a Glance

The Generic Names Supporting Organization (GNSO) community is working to implement a comprehensive series of organizational and structural changes designed to improve the efficiency, effectiveness and accessibility of the organization. Interested community members are encouraged to offer their expertise and brainpower by volunteering to participate in the effort and by joining any one of a number of focused work teams making implementation recommendations.

Recent Developments

Progress continues in overall implementation, coordination and planning for transition to a newly structured GNSO Council. To become familiar with the GNSO’s new structure and organization, please see the discussion and diagrams on the GNSO Improvements webpage.

New Stakeholder Groups – At the 21 May Board meeting the Board determined that most of the five new Stakeholder Group Charters submitted by the community prior to the Mexico City Board meeting required revisions to ensure equitable participation and representation by new constituencies.

The Board directed the Structural Improvements Committee (SIC) and ICANN Staff to make the necessary changes to the Stakeholder Group charters to make them consistent with the Board’s GNSO Improvements Report and related Resolutions, and to post the revised charters, and an explanatory memorandum, for GNSO consultation and public comment.

New GNSO Constituencies – Four new GNSO Constituency candidates have now formally petitioned the Board for approval and recognition. Three of the petitions (CyberSafety, Consumers and IDNgTLD) have been subject to full 30-day public comment forums and Summary-Analysis documents have been prepared for all three proceedings. The City TLD proposal, which was formally submitted on 1 June, is currently the subject of its own Public Comment Forum that runs through July 10.

ICANN Bylaw Amendments - A GNSO Council Restructure Drafting Team has been working on a set of Bylaws Amendments needed to implement the new GNSO structure and processes. The Drafting Team has sought further guidance from the SIC. The Team is scheduled to continue its work in Sydney and the Council hopes to have a Bylaws resolution approved before the conclusion of the Sydney session.

Council and Work Team Implementation Efforts -- The Operations Steering Committee (OSC) and Policy Process Steering Committee (PPSC), created by the GNSO Council, established five Work Teams to develop specific proposals, processes and mechanisms for implementing the GNSO Improvement Recommendations endorsed and adopted by the Board as follows:

PPSC A team to develop recommendations for a new and improved Policy Development Process (PDP)
PPSC A team to develop recommendations for a standardized Working Group model for GNSO policy development
OSC A team to develop recommendations for revised GNSO Council operations
OSC A team to develop recommendations for standard Stakeholder Group and Constituency processes and operations; and
OSC A team to develop recommendations for efforts to improve the various communications functions in the GNSO community that will lead to broader and more effective participation in all policy development activities (e.g., web site design and translation policies).

Announcements encouraging volunteers to join the Work Teams were posted on the main ICANN web page and circulated throughout the GNSO and ALAC communities in early January. Subsequently, the Work Teams were staffed by volunteers from the community and each team met for the first time in Mexico City. The status of each of the Work Teams follows:

PPSC Efforts:

  1. PDP Team

    The PDP Work Team is developing a new policy development process (PDP) (including a report of proposed new bylaws, rules and procedures) that is better aligned with the contractual requirements of ICANN’s consensus policies, expands early issue scoping and fact-finding prior to launch of a PDP, is more flexible and effective, and includes a post-PDP assessment process to measure the effectiveness of policy recommendations. The team is meeting weekly and currently is discussing the pre-PDP planning and initiation phase, which includes initial issue scoping and fact-finding steps. In recent weeks, the team has explored the parties who should be able to "raise an issue" and the types of recommendations and policy outcomes that might result from a PDP.
  2. Working Group Team

    The Working Group Model Work Team is in the process of developing two new guidebooks that are targeted to separate audiences as follows: "Working Group Implementation and Charter Drafting Guidelines" is intended for sponsoring organizations such as the GNSO Council and will contain a comprehensive set of elements to be considered in creating, purposing, funding, staffing, and instructing/guiding a WG to accomplish the desired outcome; and "Working Group Operating Model Guidebook" is intended for leaders/members of working groups and will provide guidance on such elements as structuring, norming ,tasking, reporting, and delivering the outcome(s) as chartered. As of the June ICANN meeting, both outlines have been completed and drafting activities have begun on both documents.

OSC Efforts:

  1. The GNSO Operations Work Team

    This team has developed suggestions for high-level principles to establish the role of the Council as a "strategic manager of the policy process" and is finalizing a draft "Statement of Interest"/"Declaration of Interest" policy. The team is meeting bi-weekly and has begun to consider changes to the GNSO Council Rules of Procedure to meet the requirements of the Board Recommendations for GNSO Improvements.
  2. The Constituency & Stakeholder Group Operations Work Team

    This team is developing a Work Plan and timelines to determine recommendations for best practices in the following areas: a framework for participation in any ICANN Constituency that is objective, standardized, and clearly stated; operating principles that are representative, open, transparent, and democratic; and creating and maintaining a database of all constituency members (and others not formally a part of any constituency) that is up-to-date and publicly accessible. The team is meeting bi-weekly and recently sent an inquiry to Constituencies concerning suggestions relating to the Board Recommendation for a "tool kit" of basic administrative, operational and technical services that could be made available to all Constituencies.
  3. The Communications Work Team

    This team has recently completed its first draft of a set of Business Requirements to improve the GNSO website and, in a phased approach, address basic collaboration as well as limited document management capabilities that were identified as deficient in the Board’s Report on GNSO Improvements. The Team is also working on recommendations to enhance the GNSO’s ability to solicit meaningful community feedback. In addition, the team is considering the current ICANN translation process for documents associated with policy development and recommendations to improve GNSO’s coordination with other ICANN structures.

Next Steps

Resolution of this comprehensive effort will require a longer timetable than the Board originally planned. A revised timetable will likely postpone seating of the new GNSO Council until the Seoul, South Korea ICANN meeting in October 2009. In the meantime, the Board will likely discuss the issue of the Stakeholder Group charters at the ICANN Sydney meeting in June 2009. The GNSO Council is also planning to discuss potential Bylaw amendment recommendations at its Open Meeting in Sydney.

Also, the various work teams and steering committees will continue to work on developing recommendations on the broader improvements issues in the hope of realizing the new GNSO as soon as practically possible.

Background

Through a series of decisions at its February, June, August and October 2008 meetings, the ICANN Board has endorsed a series of goals, objectives and recommendations for improving several aspects of the GNSO’s structure and operations. These decisions are a culmination of a two-year effort of independent review, community input and Board deliberations.

Click here for more details.

More Information

Staff Contact

Robert Hoggarth, Senior Policy Director


6. GEOGRAPHIC REGIONS REVIEW CHARTER REVISED AND READY FOR BOARD APPROVAL

At a Glance

The proposed charter of the community-wide working group tasked with the review of ICANN’s system of geographic regions has received favorable community reaction, has been revised consistent with Board input and is now ready for approval.

Recent Developments

The Geographic Regions Working Group developed a proposed charter of work and that document was subjected to a full 30-day public comment forum. The Board discussed the proposed charter during its 23 April and 21 May Board meetings, but withheld approval pending resolution of certain concerns expressed during the meetings regarding the membership make-up of the working group and the processes and working methodology of the group as set forth in the draft charter document. The working group has reviewed those concerns and modified the proposed charter to address them.

Also the working group welcomed two new members in early June. Representatives of the Number Resource Organization (acting to fulfill the role, responsibilities and functions of the Address Supporting Organization) joined the working group effective 1 June 2009.

Next Steps

The proposed charter awaits Board approval and is now likely to be considered at the 26 June Board meeting in Sydney, Australia. The working group will otherwise continue developing its Initial Report draft, which is now likely to be released sometime in July.

Background

Click here for more details.

More Information

Staff Contact

Robert Hoggarth, Senior Policy Director


7. RIRS DISCUSSING GLOBAL POLICY PROPOSAL FOR RECOVERED IPv4 ADDRESS SPACE

At a Glance

Regional Internet Registries (RIRs) are currently discussing a proposed global policy for handling IPv4 address space returned from the RIRs to IANA. According to the proposal, IANA should act as repository of returned address space and allocate such space to the RIRs in smaller blocks than currently, once the free pool of IANA IPv4 address space has been depleted.

Recent Developments

The RIRs discussed the proposal at their most recent meetings. APNIC has adopted the proposal, and it is in final call in AfriNIC. The proposal remains in the discussion stage in the other RIRs.

Next Steps

If adopted by all RIRs, the Number Resource Organization Executive Committee and the Address Supporting Organization Address Council (ASO AC) will review the proposal and then it will be forwarded 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 such unique numbers (approximately 4.3 billion) is being depleted and a 128-bit numbering system (IPv6) will need to take its place.

The proposed global policy has two distinct phases; 1) IANA only receives returned IPv4 address space from the RIRs and 2) IANA continues to receive returned IPv4 address space and also reallocates such space to the RIRs. This proposal is connected to a recently adopted global policy for allocating the remaining IPv4 address space. When that global policy takes effect, it also triggers phase two in the proposal.

Click here for more details.

Next Steps

A Background Report on recovered IPv4 addresses is soon to be announced on the ICANN web site.

More Information

Staff Contact

Olof Nordling, Director Services Relations


8. SSAC STUDIES, REVIEWS AND ACTIVITIES ADVANCE

At a Glance

SSAC has numerous initiatives underway or recently completed, all intended to assure the security and stability of the Internet.

Recent Developments

SSAC has completed (along with the RSSAC) a draft Terms of Reference (ToR) for the Root Scaling Study. Earlier, the ICANN Board asked that such a study explore the potential impact on root zone stability that might arise when IPv6 address records, IDN top level names, other new TLDs, and new records to support DNS security are added to the root zone.

SSAC has also prepared a comment to the Board on the matter of new GTLDs and the need to expressly prohibit the use of wildcards and synthesized responses at the top level of the DNS. SSAC has on three prior occasions explained how these practices jeopardize the stability of the DNS. This activity is stimulated in part by the expressed intention and implementation of redirection by certain ccTLDs (e.g., CM).

Other SSAC notable activities include:

  • Concluding SAC040, Measures to Protect Domain R egistration Services from Exploitation or Misuse. The report details major episodes of unauthorized access to domain accounts and malicious alteration of registration data to identify exploitable areas in current registration service models. It also describes measures that e-merchants, financial bodies, and enterprise intranets apply to mitigate certain exploits.
  • Concluding an internal review and delivery of its report to the ICANN Board review working group. The SSAC reviewed JAS comments and also offered a committee self-critique (JAS Communications are consultants ICANN retained in October 2008 to perform an independent review of the SSAC)
  • Initiation of a study into the availability of explicit abuse contact information at ICANN accredited registrar web sites. The study relates to SAC038, published in February 2009, and provides supporting data for ICANN and the community to consider when it discusses future RAA amendments.
  • Planning for a "Birds of a Feather" session on internationalizing registration data, to be held on Tuesday 23 June during the Sydney ICANN meeting. The BoF will provide attendees with an overview of the SSAC report on this subject and an opportunity for the community to participate in determining an appropriate way forward.

Next Steps

The ICANN Board will review the root scaling terms of reference and solicit contractors for its implementation. This ToR includes an extensive set of issues and questions and bidders will be required to possess considerable expertise to examine them all. SSAC intends to discuss the SAC040 report with registrars during the Sydney meeting and publish it in July.

Background

Malicious use of domain names has become a mainstay for criminals, "hacktivists," and notoriety seekers. Much of SSAC’s attention is by necessity directed at these events. At the same time, the Internet community is preparing for dramatic changes over the next several years, including the introduction of DNSSEC, IPv6, IDN, and new gTLDs. Each of these changes individually poses new issues; introduced together, even over a span of years, they represent additional complexity and could have cumulative side effects. SSAC will be reviewing these changes for potential new vectors for attacks in both contexts.

More Information

Staff Contact

Dave Piscitello Senior Technology Specialist


9. WORK UNDER WAY ON GNSO COUNCIL WHOIS REQUIREMENTS

At a Glance

WHOIS is the data repository containing registered domain names, registrant contacts and other critical information. Questions persist concerning the use and misuse of this important resource. The GNSO Council continues its inquiries into the suitability of WHOIS going forward.

Recent Developments

Staff intends to release study assessment information serially (as specific analyses on the individual study areas are complete). However, this work is an ongoing effort in which the initial feasibility assessments and cost determinations will likely take several months to complete.  Staff will keep the GNSO Council informed of progress, so that the GNSO can then consider next steps.

Background

The GNSO Council specified six study areas related to WHOIS, involving data misuse, use of non-ASCII character sets, proxy and privacy services, and the provision of inaccurate information.Click here for more details.

More Information

Staff Contact

Liz Gasster, Senior Policy Counselor


10. REGISTRATION ABUSE POLICIES GET CLOSER LOOK

At a Glance

Registries and registrars seem to lack uniform approaches to dealing with domain name registration abuse, and questions persist as to what actions constitute "registration abuse." The GNSO Council has launched a Registration Abuse Policies (RAP) Working Group to take a closer look at registration abuse policies.

Recent Developments

The RAP Working Group is meeting on a bi-weekly basis to address the issues outlined in its charter such as: what is the difference between registration abuse and domain name use abuse; the effectiveness of existing registration abuse policies; and which areas, if any, would be suitable for GNSO policy development to address registration abuse. The RAP WG submitted a status update to the GNSO Council on 2 June as required in its charter in which it outlined its activities to date, including the organization of a workshop on registration abuse in Mexico City; SSAC participation and collaboration, and discussion on the scope and definition of registration abuse.

Next Steps

The working group will host an open meeting at the ICANN meeting in Sydney to inform the community of its ongoing work and allow for questions from and discussions with the broader ICANN community.

Background

Click here for more details.

More Information

Staff Contacts

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


11. GNSO CONSIDERS EXPIRED DOMAIN NAME RECOVERY CHANGES

At a Glance

To what extent should registrants be able to reclaim 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.

Recent Developments

Following the initiation of a Policy Development Process (PDP) on Post-Expiration Domain Name Recovery (PEDNR) by the GNSO Council on 7 May, a drafting team was formed to develop a charter for a PEDNR Working Group. The drafting team has now completed its work and has submitted the proposed charter to the GNSO Council for consideration. This charter proposes that the Working Group initially shall:

  1. Pursue the availability of further information from ICANN compliance staff to understand how current RAA provisions and consensus policies regarding deletion, auto-renewal, and recovery of domain names following expiration are enforced;
  2. Review and understand the current domain name life cycle;
  3. Review current registrar practices regarding domain name expiration, renewal, and post-expiration recovery.

The Working Group shall then consider the following questions:

  1. Whether adequate opportunity exists for registrants to redeem their expired domain names;
  2. Whether expiration-related provisions in typical registration agreements are clear and conspicuous enough;
  3. Whether adequate notice exists to alert registrants of upcoming expirations;
  4. Whether additional measures need to be implemented to indicate that once a domain name enters the Auto-Renew Grace Period, it has expired (e.g., hold status, a notice on the site with a link to information on how to renew, or other options to be determined);
  5. Whether to allow the transfer of a domain name during the RGP.

The Working Group is expected to organize an issue update / workshop at the Seoul meeting, in addition to an update to the GNSO Council. The Working Group should consider recommendations for best practices as well as--or instead of--recommendations for Consensus Policy.

Next Steps

The GNSO Council is expected to consider and vote on the proposed Working Group charter at its next meeting on Wednesday 24 June at the ICANN meeting in Sydney. A Post-Expiration Domain Name Recovery Workshop will take place that same day.

Background

During the ICANN meeting in Cairo, the ALAC voted to request an Issues Report on the subject of registrants being able to recover domain names after their formal expiration date. The ALAC request was submitted to the GNSO Council on 20 November 2008. ICANN Staff prepared the Issues Report on post-expiration domain name recovery and submitted it to the GNSO Council on 5 December 2008. ICANN Staff provided the GNSO Council with clarifications on the questions raised in a motion that was adopted at its 18 December meeting. The GNSO Council reviewed these clarifications during its meeting on 29 January and agreed to create a Post-Expiration Domain Name Recovery drafting team to eventually propose a charter and provide recommendations.

Click here for more details.

More Information

Staff Contact

Marika Konings, Policy Director


12. MAKING IT EASIER TO TRANSFER DOMAINS BETWEEN REGISTRARS

At a Glance

The Inter-Registrar Transfer Policy (IRTP) aims to provide a straightforward procedure for domain name holders to transfer their names from one ICANN-accredited registrar to another. The GNSO is reviewing and considering revisions to this policy.

Recent Developments

IRTP Issues – Set B

Following the request from the GNSO Council for an Issues Report on a second set of issues related to the overall review of the IRTP, ICANN staff submitted this Issues Report on 15 May 2009. The Issues Report addresses whether:

  • A process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report (http:/www.icann.org/announcements/hijacking-report-12jul05.pdf; see also http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm);
  • Additional provisions on undoing inappropriate transfers are needed, especially with regard to disputes between a Registrant and Admin Contact. The policy is clear that the Registrant can overrule the AC, but how this is implemented is currently at the discretion of the registrar;
  • Special provisions are needed for a change of registrant near a change of registrar. The policy does not currently deal with change of registrant, which often figures in hijacking cases;
  • Standards or best practices should be implemented regarding use of Registrar Lock status (e.g., when it may/may not, should/should not be applied);
  • And if so, how best to clarify denial reason #7: A domain name was already in "lock status" provided that the Registrar provides a readily accessible and reasonable means for the Registered Name Holder to remove the lock status.

Staff has recommended that the GNSO Council initiate a Policy Development Process (PDP).

Next Steps

The GNSO Council will consider the Issues Report and is expected to vote at its next meeting on 24 June at the ICANN meeting in Sydney on whether to initiate a PDP or not. If a PDP is initiated, it will also consider a charter for an IRTP Part B Working Group.

An IRTP Part B Brainstorming session has been scheduled for Sunday 21 June from 8.00 – 9.30.

Background

As part of a broader review of the Inter-Registrar Transfer Policy, the first in a set of five distinct policy development processes (PDPs) has now been completed and a second one is in preparation.

Click here for more details.

More Information

Staff Contact

Marika Konings, Policy Director


13. HOW DO WE DEAL WITH FAST FLUXING CYBERCRIMINALS?

At a Glance

Fast flux attacks refer to techniques used by cybercriminals to evade detection by rapidly modifying IP addresses and/or name servers. The GNSO is exploring appropriate action.

Recent Developments and Next Steps

The Working Group is reviewing the public comments received and working on finalizing its report.

Background

Following a SSAC Advisory on Fast Flux Hosting and an Issues Report, the GNSO Council launched a Policy Development Process (PDP) on Fast Flux Hosting in May 2008. The Working Group published its Initial Report in January 2009, which discusses a series of questions about fast flux hosting and the range of possible answers developed by Working Group members. The Report also outlines potential next steps for Council deliberation. These next steps may include further work items for the Working Group or policy recommendations for constituency and community review and comment, and for Council deliberation.

Click here for more details .

More Information

Staff Contact

Marika Konings, Policy Director


14. AT-LARGE COMMUNITY WELCOMES NEW USER GROUPS

At a Glance

Two new organizations representing individual Internet users have been accredited to the At-Large community as At-Large Structures ("ALSes"), bringing the total number of ALSes to 114.

Recent Developments

The At-Large Advisory Committee ("ALAC") has certified AUI and the E-Seniors Association following a process that involved due diligence carried out by ICANN staff and regional advice provided by EURALO.

AUI, based in Madrid, Spain, was established in 1995 and currently has 2,870 individual members and 67 government and business organizations as members. AUI (which translates from Spanish loosely as "Association of Users of the Internet") has been very active in Internet-related initiatives, including launching the World Day of the Internet in 2005 and founding IGFSpain.

Based in Paris, France, E-Seniors Association seeks to increase access to the Internet and ICT networks for the elderly and disabled persons. E-Seniors Association provides training on effective use of the Internet and capacity building in secure on-line communication, e-commerce and e-administration activities.

More Information

Staff Contact

Policy Staff supporting At-Large


15. AT-LARGE COMMUNITY ACTIVE ON MANY POLICY FRONTS

At a Glance

At-Large is advancing on an ambitious and diverse program of policy advice development.

Recent Developments

At-Large, like other ICANN communities, is busy developing consensus positions on many policy areas in an environment with many open public consultations. The subjects of active work in At-Large include:

  • New gTLDs, including IRT (Trademark) Working Group Final Report
  • FY 2010 Operating Plan and Budget
  • Draft Security, Stability and Resiliency Report
  • At-Large proposals for Improvements to the Public Consultation Process
  • Draft Travel Procedure for FY2010
  • IDN Fast Track v3 proposals
  • "Improving Institutional Confidence – The Way Forward" documents posted by the ICANN Staff.

More Information

Staff Contact

Policy Staff supporting At-Large
update-jun09-en [PDF, 203kB]

Stay Connected

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