| # | Request | Submitted on | Addressed on | Response Provided |
|---|---|---|---|---|
| 3 | ICANN org reads recommendation 1.1 as elements of diversity all groups should reach alignment on, and strive towards. Furthermore, it understands through recommendation 1.2 that there may be instances where the diversity criteria may not be applicable to a group due to its unique governance, setup, or nature, and that in implementing recommendation 1.2, the groups should identify those, if any, and provide rationale for why a or several diversity element(s) cannot be met. | 17 August 2021 |
| This is an accurate interpretation of recommendations 1.1 and 1.2. |
| 2 | The ICANN organization should improve visibility and transparency of the organization’s existing accountability mechanisms, by posting on icann.org in one dedicated area the following - [...] 7.1.1.6 The roles descriptions included in this overall report. Does 7.1.1.6 refer to roles descriptions embedded in the 7.1.1.5 ICANN Delegation of Authority Guidelines document https://www.icann.org/en/system/files/files/delegation-of-authority-guidelines-08nov16-en.pdf, or items 1, 2, 3, 4 listed on p. 322 of the WS2 Final Report https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf? | 6 May 2021 | 12 June 2021 | 7.1.1.6 refer to roles descriptions 1, 2, 3, 4 listed on p. 322 of the WS2 Final Report |
| 1 | 6.3.7 A glossary for explaining acronyms used by SO/AC/Groups is recommended. The ICANN org glossary includes terminology, including SO/ACs’ terminology that is perennial. As the recommendation is located in the SO/AC Accountability set of recommendations, is it the intent that each SO/AC would create a glossary of temporary terminology? | 6 May 2021 | 7 May 2021 - WS2-IT Mtg #4 | Each SO/AC is to maintain its own glossary. |
