ICANN Resolutions » Composition and Scope of the Board Working Group on Registration Data Directory Services (BWG-RDS)
Important note: The Board Resolutions are as reported in the Board Meeting Transcripts, Minutes & Resolutions portion of ICANN's website. Only the words contained in the Resolutions themselves represent the official acts of the Board. The explanatory text provided through this database (including the summary, implementation actions, identification of related resolutions, and additional information) is an interpretation or an explanation that has no official authority and does not represent the purpose behind the Board actions, nor does any explanations or interpretations modify or override the Resolutions themselves. Resolutions can only be modified through further act of the ICANN Board.
This resolution continues the Board's attention to the implementation of the Action Plan adopted by the Board in response to the WHOIS Review Team's recommendations. The Board is asked to adopt the Charter and proposed members of the Board Working Group on Registration Data Directory Services.
Whereas, under the Affirmation of Commitments (AoC), ICANN is committed to conducting periodic reviews of the effectiveness of the WHOIS policy and its implementation.
Whereas, in 2012, the Board adopted a two-pronged approach to address the recommendations of the first WHOIS Review Team, calling for ICANN to (i) continue to fully enforce existing consensus policy and contractual conditions relating to WHOIS, and (ii) create an expert working group to determine the fundamental purpose and objectives of collecting, maintaining and providing access to gTLD registration data, to serve as a foundation for a Board-initiated GNSO policy development process (PDP).
Whereas, upon publication of the EWG's Final Report in June 2014, an informal group of Generic Names Supporting Organization (GNSO) Councilors and ICANN Board members collaborated to propose a Process Framework for structuring a GNSO Policy Development Process (PDP) to successfully address this challenging issue.
On 26 April 2015, the Board adopted that Process Framework and reaffirmed its 2012 request for a Board-initiated PDP to define the purpose of collecting, maintaining and providing access to gTLD registration data, and to consider safeguards for protecting data, using the recommendations in the EWG's Final Report as an input to, and, if appropriate as, the foundation for a new gTLD policy.
Whereas, the Board also approved the formation of a group of Board members that will (i) liaise with the GNSO on the policy development process to examine the EWG's recommended model and propose policies to support the creation of the next generation registration directory services, and (ii) oversee the implementation of the remaining projects arising from the Action Plan adopted by the Board in response to the first WHOIS Review Team's recommendations.
Whereas, the Board Governance Committee proposed a Charter for the Board Working Group on Registration Data Directory Services (BWG-RDS) and identified a recommended slate of Board members to do this work.
Whereas, the BGC has recommended that the following Board members be appointed as members of the BWG-RDS: Steve Crocker, Bruce Tonkin, Erika Mann, Rinalia Abdul Rahim, Markus Kummer, Cherine Chalaby, and Chris Disspain, and the ICANN CEO as an ex-officio member. Given that the current ICANN CEO has announced his resignation from ICANN, the BGC also recommended that the CEO role on the BWG-RDS not be filled until the next CEO takes office.
Resolved (2015.07.28.04), the Board hereby adopts the Charter of the Board Working Group on Registration Data Directory Services.
Resolved (2015.07.28.05), the Board hereby names the following Board members to serve on the BWG-RDS: Steve Crocker, Bruce Tonkin, Erika Mann, Rinalia Abdul Rahim, Markus Kummer, Cherine Chalaby, and Chris Disspain. The Board also names an ex-officio role on the BWG-RDS for ICANN's CEO, however that role will not become operative until the next ICANN CEO takes office.
Why is the Board addressing the issue?
This resolution continues the Board's attention to the implementation of the Action Plan adopted by the Board in response to the WHOIS Review Team's recommendations. It also is a continuation of the Board's 26 April 2015 resolution establishing a Board group to address specific issues related to registration data directory services (BWG-RDS). That resolution indicated that the membership of the Board Working Group would be addressed by the Board Governance Committee (BGC). As contemplated by the Board's 26 April 2015 resolution, the BGC considered the membership of the BWG-RDS and made a recommendation to the Board. The Board's action today adopts the recommendation of the BGC concerning the composition of the BWG-RDS. In addition, the Board is adopting the Charter recommended by the BGC to clarify the scope of the work to be undertaken by the BWG-RDS.
What is the proposal being considered?
Under the Affirmation of Commitments (AoC), ICANN is committed to enforcing its existing policy relating to WHOIS (subject to applicable laws), which "requires that ICANN implement measures to maintain timely, unrestricted and public access to accurate and complete WHOIS information…." The AoC obligates ICANN to organize no less frequently than every three years a community review of WHOIS policy and its implementation to assess the extent to which WHOIS policy is effective and its implementation meets the legitimate needs of law enforcement and promotes consumer trust. Under this timeline, the second WHOIS Review Team is to be convened in late 2015.
In 2012, the first WHOIS Review Team recommended in its Final Report that the Board create a committee to support WHOIS as a strategic priority and ensure the implementation of its recommendations to improve the effectiveness of the WHOIS policy. In response, the Board adopted a two-prong approach that simultaneously directed ICANN to (1) implement improvements to the current WHOIS system based on the Action Plan that was based on the recommendations of the WHOIS Review Team, and (2) launch a new effort, achieved through the creation of the Expert Working Group, to focus on the purpose and provision of gTLD directory services, to serve as the foundation of a Board-initiated GNSO policy development process (PDP).
The effect of the Board's action today, establishing the composition of the BWG-RDS and adopting its Charter, will allow the BWG-RDS to commence: (1) liaising with the GNSO as it conducts the Board-directed GNSO policy development process to examine the EWG's recommended model for the next generation registration directory services, and (2) oversee the implementation of the remaining projects arising from the AoC WHOIS Review Team recommendations Action Plan, and provide oversight and guidance related to the activities of the second WHOIS Review Team when convened.
What factors did the Board find to be significant?
The Board believes that the importance of the WHOIS issue, along with the breadth and scope of the many WHOIS activities currently under way, support the need for a designated group of Board members dedicated to overseeing the entire WHOIS Program, including working with the community on the GNSO PDP, and any future transition to a next generation registration directory services that may emerge following the GNSO PDP Community members participating in the informal Board-GNSO Council effort to develop the Board-approved framework for the PDP also requested the Board's continued involvement in this effort.
What significant materials did the Board review?
The Board reviewed the Charter proposed by the BGC, and the Briefing Papers submitted by Staff.
Are there fiscal impacts or ramifications on ICANN (strategic plan, operating plan, or budget)?
The creation of the BWC-RDS and conduct of its activities is not expected to require additional resources beyond those included in the Board-approved FY16 Operating Plan and Budget.
Are there any security, stability or resiliency issues relating to the DNS?
This action is not expected to have an immediate impact on the security, stability or resiliency of the DNS, though the outcomes of this work may result in positive impacts.
Is public comment required prior to Board action?
As this is a continuation of prior Board actions, this is an Organizational Administrative Action for which public comment is not necessary prior to adoption