Skip to main content
Resources

Alignment between the Board Redaction Codes and the Documentary Information Disclosure Policy (DIDP) Defined Conditions for Nondisclosure

20 December 2019

In November 2019, the ICANN Board adopted the recommendations issued by Work Stream 2 (WS2) of the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability). One of those recommendations related to the Transparency of Board Deliberations and included a request for consistency between ICANN's DIDP Defined Conditions for Nondisclosure (Nondisclosure Conditions) and the ICANN Board Redaction Codes. The following chart was developed to provide alignment between the DIDP Nondisclosure Conditions with the Board Redaction Codes. This alignment chart supports the redaction process set out in the Guidelines for Publication of Board Briefing Materials.

Board Redaction Codes Description of the Board Redaction Codes Potential DIDP Nondisclosure Conditions1

Confidential Employment Matter

Sensitive personnel information including:

  • Personnel, medical, contractual, remuneration, and similar records relating to an individual's personal information, when the disclosure of such information would or likely would constitute an invasion of personal privacy, as well as proceedings of internal appeal mechanisms and investigations.
  • Identities of persons considered for and not receiving appointment, including discussion of reasons why appointment was not recommended.

Personnel, medical, contractual, remuneration, and similar records relating to an individual's personal information, when the disclosure of such information would or likely would constitute an invasion of personal privacy, as well as proceedings of internal appeal mechanisms and investigations.

Resolution Text Superseded

Proposed resolutions, when the Board approves a modified or different resolution.

Drafts of all correspondence, reports, documents, agreements, contracts, emails, or any other forms of communication.

Rationale Text Superseded

Proposed rationale statements, when the Board approves a modified or different rationale statement.

Drafts of all correspondence, reports, documents, agreements, contracts, emails, or any other forms of communication.

Item Removed From Agenda2

or

Resolution Not Considered

Items removed from a Board agenda or not discussed.

Relevant DIDP Nondisclosure Conditions may vary based on the subject matter but could include:

  • Internal information that, if disclosed, would or would be likely to compromise the integrity of ICANN's deliberative and decision-making process by inhibiting the candid exchange of ideas and communications, including internal documents, memoranda, and other similar communications to or from ICANN Directors, ICANN Directors' Advisors, ICANN staff, ICANN consultants, ICANN contractors, and ICANN agents.
  • Information exchanged, prepared for, or derived from the deliberative and decision-making process between ICANN, its constituents, and/or other entities with which ICANN cooperates that, if disclosed, would or would be likely to compromise the integrity of the deliberative and decision-making process between and among ICANN, its constituents, and/or other entities with which ICANN cooperates by inhibiting the candid exchange of ideas and communications.
  • Drafts of all correspondence, reports, documents, agreements, contracts, emails, or any other forms of communication.

Draft

Drafts of correspondence, reports, documents, agreements, contracts, emails, or any other forms of communication.

Drafts of all correspondence, reports, documents, agreements, contracts, emails, or any other forms of communication.

Sensitive Delegation Information

Delegation information including:

  • Country code top-level domain (ccTLD) Delegation and Transfer request assessments; and
  • IANA Delegation and Transfer request reports not published at the time the Board Materials are published or modified prior to publication.

Information that relates in any way to the security and stability of the Internet, including the operation of the L Root or any changes, modifications, or additions to the root zone.

Confidential Negotiation Information

or

Confidential Business Information

Strategic negotiations and analysis or business information including:

  • Strategic relationship information, such as identification of proposed strategic partners.
  • Descriptions of external proposals and bids under consideration, including proposals for ICANN meeting locations, particularly those not selected.
  • Information that relates in any way to the assessment of internal or external security issues or risk analyses.

Relevant DIDP nondisclosure conditions include:

  • Internal information that, if disclosed, would or would be likely to compromise the integrity of ICANN's deliberative and decision-making process by inhibiting the candid exchange of ideas and communications, including internal documents, memoranda, and other similar communications to or from ICANN Directors, ICANN Directors' Advisors, ICANN staff, ICANN consultants, ICANN contractors, and ICANN agents.
  • Information provided to ICANN by a party that, if disclosed, would or would be likely to materially prejudice the commercial interests, financial interests, and/or competitive position of such party or was provided to ICANN pursuant to a nondisclosure agreement or nondisclosure provision within an agreement.
  • Trade secrets and commercial and financial information not publicly disclosed by ICANN.

Privileged and Confidential

Information subject to the attorney-client privilege, attorney work product doctrine, or any other applicable privilege, or disclosure of which might prejudice any internal, governmental, or legal investigation.

Information subject to the attorney–client, attorney work product privilege, or any other applicable privilege, or disclosure of which might prejudice any internal, governmental, or legal investigation.

Contact Information Redacted

Personally identifiable information including Board call information/Director and other third-party phone numbers and personal identifier information.

Personnel, medical, contractual, remuneration, and similar records relating to an individual's personal information, when the disclosure of such information would or likely would constitute an invasion of personal privacy, as well as proceedings of internal appeal mechanisms and investigations.


1 ICANN org created the alignment chart to ensure that every Board Redaction Code aligns with at least one DIDP Nondisclosure Condition; however, it should be noted that in some instances, a Board Redaction Code may align with multiple DIDP Nondisclosure Conditions, even if not identified on this chart.

2 As noted in the Guidelines for the Posting of Board Briefing Materials, items that were removed from the agenda or not considered do not fall within the definition of "Board Briefing Materials" and are typically not published on that basis. This information will, in nearly every instance, be appropriately subject to a Defined Condition for Nondisclosure as well.

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."