Skip to main content
Resources

Approved Board Resolutions | Regular Meeting of the ICANN Board

  1. Main Agenda
    1. Thank You to Departing Community Members
    2. Thank You to the 2013 Nominating Committee
  2. Consent Agenda
    1. Approval of Board Meeting Minutes
    2. SSAC Member Reappointments
    3. DNS Risk Management Framework Report and Implementation
    4. SSAC Advisory and NGPC Recommendations on Name Collision
    5. SSAC Advisory on DNSSEC Key Rollover in the Root Zone
    6. Digital Platform Contract
    7. Thank You to Sponsors of ICANN 48 Meeting
    8. Thank You to Interpreters, Staff, Event and Hotel Teams of ICANN 48 Meeting
    9. Thank You to Local Hosts of ICANN 48 Meeting
  3. Main Agenda
    1. Changes to Board Standing Committees
    2. Thank You to Francisco da Silva for his service to the ICANN Board
    3. Thank You to Judith Duavit Vazquez for her service to the ICANN Board
    4. Thank You to Bertrand de La Chapelle for his service to the ICANN Board

 

  1. Main Agenda:

    1. Thank You to Departing Community Members

      Whereas, ICANN wishes to acknowledge the considerable energy and skills that members of the stakeholder community bring to the ICANN process.

      Whereas, in recognition of these contributions, ICANN wishes to acknowledge and thank members of the community when their terms of service on Supporting Organizations and Advisory Committees end.

      Whereas, the following members of the At Large Advisory Committee (ALAC) are leaving their positions:

      • Cheryl Langdon-Orr – ALAC Liaison to the ccNSO
      • Carlton Samuels – ALAC (LACRALO)
      • Rinalia Abdul Rahim – ALAC (AFRALO)
      • Yaovi Atohoun – ALAC (AFRALO)
      • Titi Akinsanmi – ALAC (AFRALO)
      • Sala Tamanikaiwaimaro – ALAC (AFRALO)
      • Natalia Enciso – ALAC (LACRALO)
      • Fatimata Seye Sylla – AFRALO Chair
      • Tijani Ben Jemaa – AFRALO Vice-Chair
      • Aziz Hilali – AFRALO Secretary
      • Darlene Thompson – NARALO Secretary
      • Gareth Shearman – in Memoriam – ALAC (NARALO)

      Resolved (2013.11.21.01), Cheryl Langdon-Orr, Carlton Samuels, Rinalia Abdul Rahim, Yaovi Atohoun, Titi Akinsanmi, Sala Tamanikaiwaimaro, Natalia Enciso, Fatimata Seye Sylla, Tijani Ben Jemaa, Aziz Hilali, and Darlene Thompson have earned the deep appreciation of the Board for their terms of service, and the Board wishes them well in their future endeavors within the ICANN community and beyond.

      Resolved (2013.11.21.02), Gareth Shearman has earned the deep appreciation of the Board for his term of service.

      Whereas, the following RIPE Representative of the Address Supporting Organization (ASO) is leaving his current position and joining the 2014 Nominating Committee:

      • Hans Petter Holen – ASO (RIPE)

      Resolved (2013.11.21.03), Hans Petter Holen has earned the deep appreciation of the Board for his terms of service, and the Board wishes him well in his future endeavors within the ICANN community and beyond.

      Whereas, the following member of the Country Code Names Supporting Organization (ccNSO) Council is leaving his position:

      • Sokol Haxhiu – ccNSO Councilor

      Resolved (2013.11.21.04), Sokol Haxhiu has earned the deep appreciation of the Board for his terms of service, and the Board wishes him well in his future endeavors within the ICANN community and beyond.

      Whereas, the following members of the Generic Names Supporting Organization (GNSO) are leaving their positions:

      • Jeff Neuman – GNSO Councilor
      • Wolf-Ulrich Knoben – GNSO Council Vice-Chair and Councilor
      • Lanre Ajayi – GNSO Councilor
      • Mason Cole – GNSO Council Vice-Chair and Councilor
      • Joy Liddicoat – GNSO Councilor
      • Robin Gross – Chair, Non-Commercial Stakeholder Group (NCSG)
      • Wendy Seltzer – GNSO Councilor
      • Wolfgang Kleinwächter – GNSO Councilor
      • Zahid Jamil – GNSO Councilor

      Resolved (2013.11.21.05), Jeff Neuman, Wolf-Ulrich Knoben, Lanre Ajayi, Mason Cole, Joy Liddicoat, Robin Gross, Wendy Seltzer, Wolfgang Kleinwächter, and Zahid Jamil have earned the deep appreciation of the Board for their terms of service, and the Board wishes them well in their future endeavors within the ICANN community and beyond.

      Whereas, the following member of the Root Server System Advisory Committee (RSSAC) has left his position:

      • Matt Larson - RSSAC Co-Chair

      Resolved (2013.11.21.06), Matt Larson has earned the deep appreciation of the Board for his terms of service, and the Board wishes him well in their future endeavors within the ICANN community and beyond.

      Whereas, the following members of the Security and Stability Advisory Committee (SSAC) are leaving their positions:

      • Jeremy Hitchcock - SSAC Member
      • Vanda Scartezini - SSAC Member

      Resolved (2013.11.21.07), Jeremy Hitchcock and Vanda Scartezini have earned the deep appreciation of the Board for their terms of service, and the Board wishes them well in their future endeavors within the ICANN community and beyond.

    2. Thank You to the 2013 Nominating Committee

      Whereas, ICANN appointed Yrjö Lansipuro as Chair of the 2013 Nominating Committee and Cheryl Langdon-Orr as Chair-Elect of the 2013 Nominating Committee, and Adam Peake was asked to serve as Associate Chair.

      Whereas, the 2013 Nominating Committee consisted of delegates from each of ICANN's constituencies and advisory bodies.

      Resolved (2013.11.21.08), the ICANN Board expresses its deep appreciation to Yrjö Lansipuro, Cheryl Langdon-Orr, Adam Peak, and all of the members of the 2013 Nominating Committee (including Ron Andruff, Howard Benn, Veronica Cretu, Rafik Dammak, Mohamed El Bashir, J. Scott Evans, Hartmut Glaser, Anthony Harris, Ole Jacobsen, Warren Kumari, Bill Manning, John McElwaine, Glenn McKnight, Vanda Scartezini, Waudo Siganga, Ken Stubbs, Stéphane Van Gelder, Siranush Vardanyan, and Jian Zhang) for their dedication, hard work and successful efforts.

  2. Consent Agenda:

    1. Approval of Board Meeting Minutes

      Resolved (2013.11.21.09), the Board approves the minutes of the 23 October 2013 Special Meeting of the ICANN Board.

    2. SSAC Member Reappointments

      Whereas, Article XI, Section 2, Subsection 2 of the Bylaws governs the Security and Stability Advisory Committee (SSAC).

      Whereas, the Board, at Resolution 2010.08.05.07, approved Bylaws revisions that create three-year terms for SSAC members, require staggering of terms, and obligate the SSAC chair to recommend the reappointment of all current SSAC members to full or partial terms to implement the Bylaws revisions.

      Whereas, the Board, at Resolution 2010.08.05.08, appointed SSAC members to terms of one, two, and three years beginning on 01 January 2011 and ending on 31 December 2011, 31 December 2012, and 31 December 2013.

      Whereas, in July 2013 the SSAC Membership Committee initiated an annual review of SSAC members whose terms are ending 31 December 2013 and submitted to the SSAC its recommendations for reappointments.

      Whereas, on 25 September 2013, the SSAC members approved the reappointments.

      Whereas, the SSAC recommends that the Board reappoint the following SSAC members to three-year terms: Roy Arends, Jeffrey Bedser, Sarmad Hussain, Merike Kaeo, Warren Kumari, Matt Larson, Danny McPherson, and Shinta Sato.

      Resolved (2013.11.21.10), the Board accepts the recommendation of the SSAC and reappoints the following SSAC members to three-year terms beginning 01 January 2014 and ending 31 December 2016: Roy Arends, Jeffrey Bedser, Sarmad Hussain, Merike Kaeo, Warren Kumari, Matt Larson, Danny McPherson, and Shinta Sato.

      Rationale for Resolution 2013.11.21.10

      The SSAC is a diverse group of individuals whose expertise in specific subject matters enables the SSAC to fulfill its charter and execute its mission. Since its inception, the SSAC has invited individuals with deep knowledge and experience in technical and security areas that are critical to the security and stability of the Internet's domain name system. The above-mentioned individuals provide the SSAC with the expertise and experience required for the Committee to fulfill its charter and execute its mission.

    3. DNS Risk Management Framework Report and Implementation

      Whereas, on 28 October 2011, the Board formed a DNS Risk Management Framework Working Group to oversee the development of a risk management framework for the DNS as it pertains to ICANN's role and remit as found in the ICANN Bylaws.

      Whereas, the Working Group supported by ICANN staff developed a risk management framework, with input from the ICANN community, which was presented at ICANN's April 2013 meeting in Beijing and updated following the ICANN's July 2013 meeting in Durban.

      Whereas, staff has reviewed the framework and community input, and is prepared to move ahead with implementation.

      Whereas, the Board thanks the members of the DNS Risk Management Framework Working Group for their efforts over the past two years, and directs that the working group be closed. Oversight of staff implementation will transition to the Board Risk Committee.

      Resolved (2013.11.21.11), the Board directs the President and CEO to proceed with implementation of the DNS Risk Management Framework and report back to the Board Risk Committee as needed on the risk assessment and proposed mitigation measures.

      Rationale for Resolution 2013.11.21.11

      In October 2011, the Board created a working group to develop a risk management framework for the DNS as it pertains to ICANN's role as defined in the ICANN Bylaws (see http://www.icann.org/en/groups/board/documents/resolutions-28oct11-en.htm#1.8). The DNS Risk Management Framework Working Group (DNS RMF WG) was formed, consisting of Bill Graham (Chair), Patrik Fältström, Roelof Meijer, Ram Mohan, Ray Plzak, Bill Woodcock, and Suzanne Woolf.

      The Board approved the Charter for the Working Group on 12 March 2012 (http://www.icann.org/en/groups/board/documents/resolutions-16mar12-en.htm#1.6). The Working Group held public workshops at the ICANN meetings in Prague (June 2012) and Toronto (October 2012). After ICANN's issuance of an RFP, Westlake Governance was selected as a DNS risk management consultant. Westlake developed a draft framework following the Toronto meeting, and presented a draft framework for community review after the ICANN meeting in Beijing (April 2013).

      A public comment process was conducted on the DNS risk management framework from 23 August to 5 October 2013. Information on the public comment process is available at http://www.icann.org/en/news/public-comment/dns-rmf-final-23aug13-en.htm.

      The framework uses ISO 31000 as a platform but includes elements learned from the work of the community-driven DNS Security & Stability Analysis Working Group (DSSA). ICANN staff has suggested that more of the work pioneered by the DSSA be incorporated into the implementation of the framework, as this has community support and provides some practical guidance for considering threats to the DNS within ICANN's role and remit. The Westlake report acknowledges that "one size does not fit all" and requires adaptation to best meet the needs of the organization.

      Staff has completed its review of the framework and is proceeding with implementation. A risk assessment is to be conducted using the framework as a guide, and merged into existing enterprise risk management practices at ICANN. Staff is to report on progress to the Board Risk Committee. The DNS RMF Working Group has now completed its work and can be closed.

      Implementation of the DNS risk management framework supports ICANN's on-going completion of the Security, Stability and Resiliency Review Team recommendations and prior resolutions of the Board to develop a security framework for Internet naming and address allocation services. This work is intended to have a positive impact on the community and provide greater awareness of overall risk management within ICANN's role in facilitating the security, stability and resiliency of the Internet's unique identifiers. This risk management framework is not expected to have a fiscal impact on the organization or community.

      This is an Organizational Administrative Function for which public comment has been received.

    4. SSAC Advisory and NGPC Recommendations on Name Collision

      Whereas, on 12 November 2013, the ICANN Security and Stability Advisory Committee (SSAC) published SAC062: SSAC Advisory Concerning the Mitigation of Name Collision Risk.

      Whereas, in SAC 062, the SSAC advice integrates the New gTLD Program Committee's recent decisions on Name Collision Risks, and provides specific recommendations and advice for further work by ICANN to mitigate risks from name collision.

      Whereas, NCPC resolution 2013.10.07.NG02 recommended to the Board a series of follow-up actions for staff and for the Board Risk Committee in relation to the issue of name collisions.

      Resolved (2013.11.21.12), the Board acknowledges the receipt of SAC062: SSAC Advisory Concerning the Mitigation of Name Collision Risk.

      Resolved (2013.11.21.13), the Board directs ICANN's President and CEO to have the SSAC's advice from this Advisory entered into the advice tracking register and to confirm with the SSAC that the entries accurately capture the advice.

      Resolved (2013.11.21.14), the Board directs ICANN's President and CEO to have the advice provided in SAC062 evaluated, and to produce a recommendation to the Board regarding the acceptance of that advice, no later than 90 days from the adoption of this resolution.

      Resolved (2013.11.21.15), in the instances where ICANN recommends that the advice be accepted, the Board directs ICANN's President and CEO to have the feasibility and costs of implementing the advice evaluated, and to provide an implementation plan with timelines and high-level milestones for review by the Board, no later than 120 days from the adoption of this resolution.

      Resolved (2013.11.21.16), the Board adopts the NGPC recommendations: (1) the ICANN Board Risk Committee expressly reviews name collision matters and reports back to the Board, and continues to review and report at regular intervals; (2) the Board directs the ICANN President and CEO to develop a long-term plan to manage name collision at the root; and (3) the Board directs the ICANN President and CEO to work with the community to develop a long-term plan to retain and measure root-server data.

      Rationale for Resolutions 2013.11.21.12 – 2013.11.21.16

      On 12 November 2013, the SSAC published an advisory regarding the mitigation of name collision risks entitled SAC062: SSAC Advisory Concerning the Mitigation of Name Collision Risk. The SSAC's advice integrates ICANN's New gTLD Program Committee's recent decisions on Name Collision Risks, and provides specific recommendations and advice for ICANN to work further to mitigate risks from name collision in the DNS.

      On 7 October 2013, the ICANN Board New gTLD Program Committee made a series of recommendations for consideration by the ICANN Board concerning ongoing management of name collision matters.

      The Board's consideration of recommendations from Supporting Organizations and Advisory Committees in general, and for SAC062 in specific, needs to be informed by an analysis of both the substance of the advice as well as the feasibility and cost of implementing such advice that is deemed acceptable. As a result, there is no immediate impact to ICANN's resources related to approving this resolution. In addition, approving this resolution has no immediate impact on the security, stability or resiliency of the Internet. As appropriate, the future implementation of the SSAC's advice on these issues will likely have a positive impact on the security, stability and resiliency of the DNS.

      This is an Organizational Administrative Function for which public comment is not required.

    5. SSAC Advisory on DNSSEC Key Rollover in the Root Zone

      Whereas, on 12 November 2013, the ICANN Security and Stability Advisory Committee (SSAC) published SAC 063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone.

      Whereas, ensuring the successful DNSSEC Key Rollover in the Root Zone is of critical importance to the security and stability of the Domain Name System.

      Resolved (2013.11.21.17), the Board acknowledges the receipt of SAC 063: SSAC Advisory on DNSSEC Key Rollover in the Root Zone.

      Resolved (2013.11.21.18), the Board directs ICANN's President and CEO to have the SSAC's advice from this Advisory entered into the advice tracking register and to confirm with the SSAC that the entries accurately capture the advice.

      Resolved (2013.11.21.19), the Board directs ICANN's President and CEO to have the advice provided in SAC063 evaluated, and to produce a recommendation to the Board regarding the acceptance of that advice, no later than 90 days from the adoption of this resolution.

      Resolved (2013.11.21.20), in the instances where ICANN recommends that the advice be accepted, the Board directs ICANN's President and CEO to have the feasibility and costs of implementing the advice evaluated, and to provide an implementation plan with timelines and high-level milestones for review by the Board, no later than 120 days from the adoption of this resolution.

      Rationale for Resolutions 2013.11.21.17 – 2013.11.21.20

      On 12 November 2013, the SSAC also published SAC063 regarding the DNSSEC Key Rollover in the Root Zone. The Advisory describes the DNSSEC root zone Key Signing Key (KSK) rollover problem space at a high level, identifies issues that constrain possible solutions, and where appropriate, makes recommendations to the ICANN Board related to root zone KSK rollover.

      The Board's consideration of recommendations from Supporting Organizations and Advisory Committees in general, and for SAC063 in specific, needs to be informed by an analysis of both the substance of the advice as well as the feasibility and cost of implementing such advice that is deemed acceptable. As a result, there is no immediate impact to ICANN's resources related to approving this resolution. In addition, approving this resolution has no immediate impact on the security, stability or resiliency of the Internet. As appropriate, the future implementation of the SSAC's advice on these issues will likely have a positive impact on the security, stability and resiliency of the DNS.

      This is an Organizational Administrative Function for which public comment is not required.

    6. Digital Platform Contract

      Whereas, ICANN recognizes the need to broaden the reach, diversity, and number of participants joining and engaging with the ICANN community and in ICANN's policy development process.

      Whereas, ICANN recognizes the need for easier access to information by all ICANN participants.

      Whereas, ICANN is engaged in a project to enhance its web platform and redesign its web presence, using best practices and standards as well as new technologies available.

      Whereas, the ICANN Labs initiative has produced significant learning and potential solution ideas.

      Whereas, the staff has used this experience to layout the requirements for the development of a new digital platform to allow better engagement of current and future users, and is now ready to launch the project.

      Whereas, although all of the activities involved in this project fall squarely within the purview of ICANN management, since the investment will be more than $500,000, the Board is required to authorize the funding of this project.

      Resolved (2013.11.21.21), the Board authorizes the President and CEO, or his designee(s), to take all actions necessary to contract with NEO Innovations, Inc. to facilitate the development of the new digital platform and the ICANN.org website update, and to make all disbursements called for under that contract in an amount not to exceed [amount redacted for negotiation purposes].

      Rationale for Resolution 2013.11.21.21

      ICANN understands that in order to fulfill its mission, it must expand the depth and breadth of its community and increase engagement.

      That means better engaging with existing participants and newcomers to the organization, and building tools that effectively onboard all the groups including new group of community members. The tools matter, but more importantly, the way we build these tools. It is important to collaborate with our target users to gain a deeper understanding of the problems that we are trying to solve. That way, ICANN is efficient in our approach to increasing engagement and building things that newcomers and actual users will actually use. In this spirit, ICANN has run several experiments over the last few months (that have been written about on ICANN Labs) and spoken to a broad spectrum of the ICANN community.

      The early work centered on the following themes: communication, education, conversation and discovery. Essentially, how newcomers to ICANN can learn more about the organization's work, process, and communities; how they can contribute; and how they can stay engaged over time.

      We have shared, in blog posts and on Twitter, what we've learned in meetings, through the Digital Engagement Advisory Board. We are now applying what we have learned from this testing toward the development of a new ICANN.org website.

      Continuing this process and theme of community involvement in the project to ensure that we build the right solutions, ICANN intends to launch a public beta of a re-designed ICANN.org website. Ultimately, the re-design will focus on software and design solutions, but also on process. And the process, which we have used and will continue to use, relies on complete community involvement and thorough testing of all features.

      Beyond these broad strategic goals noted above, ICANN also knows that it is important to continue to update the ICANN.org technology and to enhance the design of the website. The last update to the website consisted mainly in layout changes, restructuring content display and some technical updates, and was conducted over two years ago, with an approximate cost of $300,000. We are committed to improving out ability to publish information and content, and build applications that help facilitate complex editorial and policy workflows -- all critical to the entire community's operations. This core investment of building new tools under which the ICANN.org website may operate lays out the foundation and infrastructure for a more extensible technology platform to help ICANN achieve its future organizational goals.

      While all of these activities fall squarely within the purview of ICANN management, since the investment will be more that $500,000, the Board is required to authorize management to undertake this financial obligation. This project shall not exceed a total amount of [amount redacted for negotiation purposes].

      We note that given the value of this project, absent an exception, Section 3.2 of ICANN's Procurement Guidelines would require a broad solicitation through a public Request for Proposal (see http://www.icann.org/en/about/financials/procurement-guidelines-21feb10-en.pdf [PDF, 1.03 MB].) However, section 3.3 of the Procurement Guidelines provide for exceptions to this requirement when appropriate. At least two of those exceptions apply in this case and are the reasons why ICANN chose not to issue a broad solicitation. Those reason's include: (i) "[w]hen there is a natural continuation of previous work carried out by the vendor or service provider, and in which competitive bidding would not improve value to ICANN;" and (ii) "[w]hen the incumbent provider demonstrates a clear historic pattern of charging reasonable prices and providing consistently good quality service." The selected vendor satisfies both of these criteria. Further, neither ICANN staff nor members of the ICANN Board have a financial interest in this contract.

      This action will have a financial impact on the organization, but this impact was budgeted for and anticipated to occur in FY14. This action will not have an impact on the security, stability or resiliency of the domain name system.

      This is an Organizational Administrative Function that does not require public comment.

    7. Thank You to Sponsors of ICANN 48 Meeting

      The Board wishes to thank the following sponsors: IPLAN, Afilias Limited, Public Interest Registry, Verisign, Community.Asia, Iron Mountain, Neustar, Inc., UniForum SA T/A ZA Central Registry, .CLUB Domains, LLC, LogicBoxes, NCC Group, CentralNic, Trademark Clearinghouse, Freenom, CORE Association, Architelos, Inc., Uniregistry Corp., and ICANNWIKI.

    8. Thank You to Interpreters, Staff, Event and Hotel Teams of ICANN 48 Meeting

      The Board expresses its deepest appreciation to the scribes, interpreters, technical teams, and the entire ICANN staff for their efforts in facilitating the smooth operation of the meeting.

      The Board would also like to thank the management and staff of the Sheraton Buenos Aires Hotel and Convention Center for providing a wonderful facility to hold this event. Special thanks are extended to George Handley, Manager Convention Sales, Silvina Bracco, Banquet Sales Manager and Fernando Henrichmann, Group Coordinator.

    9. Thank You to Local Hosts of ICANN 48 Meeting

      The Board wishes to extend its thanks to the local host organizer, NIC Argentina, for its support. Special thanks are extended to Dr. Gustavo Justich, National Director, Carlos Marco Liuzzi, Manager, International Liaison Unit, Marcelo Martinez, International Liaison Unit, and the entire NIC Argentina staff.

      The Board also extends thanks to Dr. Juan Manuel Abal Medina, Former Chief of the Cabinet of Ministers of Argentina, for his support of and participation in the meeting.

  3. Main Agenda:

    1. Changes to Board Standing Committees

      Whereas, the reasons that led to the formation of certain standing Board Committees – namely the IANA Committee, the Public and Stakeholder Engagement Committee ("PSEC"), and the Board Global Relationships Committee ("BGRC") – no longer exist.

      Whereas, the Board Governance Committee ("BGC") has considered the relevance of maintaining the IANA Committee, PSEC and BGRC.

      Whereas, the BGC has concluded that the areas in which these committees are focused more properly reside with management and recommends that the Board decommission these standing Board Committees.

      Resolved (2013.11.21.22), the IANA Committee, the Public and Stakeholder Engagement Committee ("PSEC"), and the Board Global Relationships Committee ("BGRC") are hereby decommissioned.

      Resolved (2013.11.21.23), the President and CEO is directed to develop a regular reporting mechanism to the Board on the areas in which these standing Board committees were focused.

      Rationale for Resolutions 2013.11.21.22 – 2013.11.21.23

      Section 1, Article XII of the ICANN Bylaws provides that the Board may establish or eliminate Board committees as the Board deems appropriate. (Bylaws, Art. XII, § 1.) The Board has delegated to the Board Governance Committee ("BGC") the responsibility for periodically reviewing and recommending any adjustments to the charters of Board Committees deemed advisable. (See BGC Charter at http://www.icann.org/en/committees/board-governance/charter.htm.)

      In an effort to streamline operations and maximize efficiency and effectiveness, the BGC reviewed the necessity and appropriateness of moving forward with the current slate of standing Board Committees. The BGC determined that the reasons that led to the formation of the IANA Committee, the Public and Stakeholder Engagement Committee ("PSEC"), and the Board Global Relationships Committee ("BGRC") no longer exist as they did at the formation of these Committees. The BGC noted that these standing Board Committees were formed due to the perceived need for more focused Board involvement in the areas in which these Committees are focused. Since the formation of these three Committees, the areas that these Committees were charged with overseeing have evolved and are now more properly and efficiently handled by management rather than the Board Committees. The BGC noted, and the Board agrees, that the decommissioning of these Committees does not mean that the BGC considers the topics for which these Committees were established of any less import.

      The Board shall continue to maintain oversight and governance over the subject matters in which these Committees were focused through regular reporting from staff to the Board. Specifically, with respect to the subject of global relationships, briefings will be provided to the Board at each public Board meeting. The Board will also continue to remain involved by providing strategic guidance on the topics that would otherwise have been overseen by the IANA Committee, the PSEC and the BGRC.

      Taking this decision will not have a financial impact on ICANN, nor will it have an effect on the security, stability or resiliency of the domain name system.

      This decision is an Organizational Administrative Function that does not require public comment.

    2. Thank You to Francisco da Silva for his service to the ICANN Board

      Whereas, Francisco da Silva was appointed to serve as the Technical Liaison Group ("TLG") Liaison to the ICANN Board on 18 October 2012.

      Whereas, Francisco concludes his term on the ICANN Board on 21 November 2013.

      Whereas, Francisco has served as a Liaison of the following Committees:

      • New gTLD Program Committee
      • Structural Improvements Committee

      Resolved (2013.11.21.24), Francisco da Silva has earned the deep appreciation of the Board for his term of service, and the Board wishes him well in his future endeavors within the ICANN community and beyond.

    3. Thank You to Judith Duavit Vazquez for her service to the ICANN Board

      Whereas, Judith Duavit Vazquez was appointed by the Nominating Committee to the ICANN Board on 28 October 2011.

      Whereas, Judith concluded her term on the ICANN Board on 7 October 2013.

      Whereas, Judith served as a member of the following Committees and Working Groups:

      • Audit Committee
      • New gTLD Program Committee
      • Risk Committee
      • Structural Improvements Committee
      • Board-GAC Recommendation Implementation Working Group

      Resolved (2013.11.21.25), Judith Duavit Vazquez has earned the deep appreciation of the Board for her term of service, and the Board wishes her well in her future endeavors within the ICANN community and beyond.

    4. Thank You to Bertrand de La Chapelle for his service to the ICANN Board

      Whereas, Bertrand de La Chapelle was appointed by the Nominating Committee to the ICANN Board on 10 December 2010.

      Whereas, Bertrand concludes his term on the ICANN Board on 21 November 2013.

      Whereas, Bertrand has served as a member of the following Committees and Working Groups:

      • Governance Committee
      • Global Relations Committee
      • Structural Improvements Committee
      • Board-GAC Recommendation Implementation Working Group

      Resolved (2013.11.21.26), Bertrand de La Chapelle has earned the deep appreciation of the Board for his term of service, and the Board wishes him well in his future endeavors within the ICANN community and beyond.

Published on 21 November 2013

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."