RC

The Registrar Constituency (Registrar Stake Holder Group) is one of the constituencies under the Generic Name Supporting Organization (GNSO) set forth by ICANN's bylaws. It is composed of ICANN accredited registrars and it promotes and represents their interests to ICANN.

The Registrar Constituency does not act as a Registrar Trade Association and it does not represent collective registrar views or interests in any other forum other than the GNSO and ICANN. It does not facilitate or promote anti-competitive actions among registrars. Mason Cole is the curren Chairman of the Registrar Stake Holder Group.

Membership and Structure

The Registrar Constituency is composed of ICANN accredited registrars with a Secretariat, responsible for evaluating the applications for membership, and four elected officers, which include the Chairman, Secretary, Treasurer and Technology Officer; there are also two GNSO Council Representatives; and Registrar Stakeholder Group Task Force Representatives.

Meetings

The meetings of the Registrars Constituency should correspond to the schedules of ICANN meetings and conduct meetings as necessary. Members of the constituency must receive the notices 45 days before the scheduled meetings.

Registrar Constituency Positions

On April 17, 2008, the Registrar Constituency submitted its positions regarding the Board Governance Committee Working Group’s Report for Recommended GNSO Improvements, which include:

Adopting a Working Group Model

• Supported the adoption of working group model because it promotes a participation from a broader set of constituencies and transfers the policy making work load of the council to the community.
• Cautioned the possibility of risks wherein the working group maybe “hijacked” by a particular interest group.
• Recommended safeguards to reduce possible risks as well as transparency in handling conflicts of interests and clear guidelines to appeal the decisions of the chairman.
• Expressed its concern over the size of the working group, which might become larger than expected. ICANN should provide enough staff and administrative support and ICANN funding should be limited only to reasonable expenses to efficiently and productively carry out its operations.

Revising the Policy Development Project (PDP)'

• It supports the revision of the PDP in conjunction with ICANN Policy requirements.
• The Bylaws should be amended to clear out consensus policies, which will be created only based on defined issues related to certain procedures based on ICANN contracts.
• The PDP timeline should be dynamic for the Council to evaluate properly the time needed for every project before scheduling it.
• It also suggested the development of procedural framework to ensure a systematic and predictable process.

Restructuring the GNSO Council

• It supports the GNSO Council restructuring and revision of the constituency representation and voting rights plans as well as the term limits for councilors and ensuring geographic diversity of the Council members.
• The Constituency agreed that the Council must have the authority to determine if the working group complied with the rules through a large majority. If not solutions should be undertaken.
• Requested further clarification on the relationship between noncommercial registrants’ with ALAC as well as with the members of the former General Assembly active lists.

Enhancing Constituencies and Improving Communication and Coordination with ICANN Structures

• It supported frequent communications among GNSO constituents with other Supporting Organizations and Advisory Committees.

Generic Names Supporting Organization. Develops and recommends to the Board substantive policies relating to generic top-level domains and other responsibilities set forth in the Bylaws (ICANN Bylaws).

Policy Development Process