Dear IFR2 Team, Rick and Jonathan have followed up with research on Article 8. Please see below for notes and links to resources. Rick found three docs that appear to confirm that the Ombudsman’s office was selected as a mechanism to provide accountability and prevent capture. Doc 1: A key document that I discovered was a transition proposal at the IANA Stewardship Transition Coordination Group website (https://www.ianacg.org [ianacg.org]<https://urldefense.com/v3/__https:/www.ianacg.org__;!!PtGJab4!_NnzlqA9eD-k8k...>) https://www.ianacg.org/icg-files/documents/IANA-stewardship-transition-propo... [ianacg.org]<https://urldefense.com/v3/__https:/www.ianacg.org/icg-files/documents/IANA-s...> And this appears to be the doc that originally recommended the use of the ICANN Ombuds office. Doc 2: A blog from 17 Feb 2016 “The Role of The Ombudsman Post IANA Transition” by “Office of the Ombudsman” https://www.icann.org/en/blogs/details/the-role-of-the-ombudsman-post-iana-t... A key quote: As part of the IANA transition, and to start the process for the accountability studies for Work Stream 2, I will be holding a session at ICANN 55 at Marrakesh on Wednesday 9th March, at 3:45 p.m. in the Opale room. I will give a presentation on what I do at present, just a brief introduction, and then open for a brainstorming session on what people want. Any changes of course need to come from the community, and many have already begun to comment on the context of the discussions in the CCWG. Here is the meeting session: https://archive.icann.org/meetings/icann55/marrakech/pages/wed-ombudsman-pos... [archive.icann.org]<https://urldefense.com/v3/__https:/archive.icann.org/meetings/icann55/marrak...> Presentation slides: https://archive.icann.org/meetings/icann55/marrakech/downloads/presentation-... [archive.icann.org]<https://urldefense.com/v3/__https:/archive.icann.org/meetings/icann55/marrak...> Transcript is incomplete. No mention of IANA or PTI in either. It focused on the core functions of the Ombuds office. The meeting session also includes a link to the audio, which I did not have time to review. Further from the blog: The primary duties of an ombudsman are (1) to work with individuals and groups in the ICANN Community to explore and assist them in determining options to help resolve conflicts, problematic issues or concerns, and (2) to bring systemic concerns to the attention of the organization for resolution. The blog also says, “what an ombudsman does not do” and includes “Participate in formal investigations or play any role in a formal issue resolution process”. And that’s interesting, I’d think. Doc 3: Another important doc that I found was: https://www.ntia.doc.gov/files/ntia/publications/combined_iana_stewardship_t... [ntia.doc.gov]<https://urldefense.com/v3/__https:/www.ntia.doc.gov/files/ntia/publications/...> On page 7, under the category of “How is accountability addressed? Does the proposal provide adequate checks and balances to protect against capture?”, we find: “Another example of checks and balances is the IANA Customer Service Complaint Resolution Process for the naming related functions. PTI staff is first allowed to address issues after being notified via a complaint ticketing system. Alternatively, or if the issue isn’t resolved satisfactorily, the ICANN Ombudsman or similar service can assist in resolving problems using Alternative Dispute Resolution techniques” (…) “NTIA finds that these proposed checks and balances are more than adequate as they exceed what is currently required under the IANA functions contract with the NTIA.” Broadly, I think that these three docs serve as a reasonable explanation of the role of the ICANN Ombuds office in the CSC resolution process.