Registrar Stakeholder Group

This article is neutral, but is sponsored by EuroDNS, an ICANN--accredited registrar and member of the RrSG. Learn more about EuroDNS's services here.

link={{{link}}}

ICANNWiki Gold Sponsor

RrSG, or the Registrars Stakeholder Group, is an ICANN Stakeholder Group representing ICANN-accredited registrars. It was first recognized by the ICANN Board on 27 May 1999. The RrSG participates in ICANN's policy-making process and also works as one of the most efficient bodies in raising the voice of the registrars within the ICANN community.

The RrSG is a part of the Contracted Parties House under the Generic Names Support Organization (GNSO), the main policymaking body for ICANN. There are three representatives that are elected to the GNSO Council from the RrSG, where they represent the views of the other members of the RrSG and vote on policy matters. The members of the RrSG have regular meetings with ICANN policy, finance, and registrar and finance liaison staff, as well as with the members of registries, the government, and law enforcement agencies. Within the group, they also exchange vital information to enhance registrar services for their respective customers.

Membership of RrSG

The RrSG welcomes all ICANN-accredited Registrars to join the RrSG and participate in their activities. The fee to join the RrSG is $500.

Structure of the RrSG

• Members of the RrSG: The members of the RrSG consist of ICANN-accredited registrars who have paid the membership fees and fulfilled the requirements for becoming a member.
• Executive Committee: The Executive Committee or Excom of the RrSG is comprised of the Chair, Vice Chair, Secretary, and Treasurer. These four officers manage the RrSG and are elected from the already existing members via nomination by the other members and then candidate selection by majority vote. The term lasts for one year starting from June 1st and ending on May 31st. The Excom is assigned such responsibilities as developing meeting agendas, providing notices of meetings, managing as well as administering elections, supporting the GNSO Council and ICANN Board, facilitating policy coordination meetings and many others.
• GNSO Council Members: The RrSG also includes 3 GNSO Council Members who are elected by the Registrar Stakeholder Group to represent the North America, Europe and Asia-Pacific regions.
• Nominating Committee Member: A NomCom representative is elected by the RrSG to represent the NomCom.
• Support Staff: These include the Secretariat, Website Administrator and Legal Advocate.

Current Staff

Executive Committee

• Matt Serlin, Chair
• Jeff Eckhaus, Vice-Chair/CTO
• James Bladel, Secretary
• Volker Greimann, Treasurer

ICANN Representatives

• Mason Cole, GNSO Representative, North America
• Yoav Keren, GNSO Representative, Asia Pacific
• Stephane Van Gelder, GNSO Representative, Europe
• Krista Papac, Nominating Committee Member

Support Staff

• Cristin Donahue, Secretariat
• Paul Goldstone, Website Administrator

Registrar Constituency

Prior to the GNSO restructuring, the RrSG was known as the Registry Constituency.

Registrar Constituency Positions

On April 17, 2008, the Registrar Constituency submitted its position 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).

Nominating Committee

Policy Development Process