<div dir="ltr"><div class="gmail_default" style="font-size:small">Thanks for the reminder, Chris!<br><br></div><div class="gmail_default" style="font-size:small">Rinalia<br></div><div class="gmail_default" style="font-size:small"><br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 15, 2016 at 5:04 AM, Chris LaHatte <span dir="ltr"><<a href="mailto:chris.lahatte@icann.org" target="_blank">chris.lahatte@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It is worth noting my powers to inspect as well in this context.<br>
<br>
The ombudsman in Clause 3<br>
<br>
" 3. have the right to have access to (but not to publish if otherwise<br>
confidential) all necessary information and records from ICANN staff and<br>
constituent bodies to enable an informed evaluation of the complaint and to<br>
assist in dispute resolution where feasible (subject only to such<br>
confidentiality obligations as are imposed by the complainant or any<br>
generally applicable confidentiality policies adopted by ICANN);"<br>
<br>
So there has been much discussion about access to documents, but in the<br>
context of a complaint by the community I have that power. I am surprised<br>
this has been rarely used.<br>
<br>
<br>
<br>
Chris LaHatte<br>
Ombudsman<br>
Blog <a href="https://omblog.icann.org/" rel="noreferrer" target="_blank">https://omblog.icann.org/</a><br>
Webpage <a href="http://www.icann.org/en/help/ombudsman" rel="noreferrer" target="_blank">http://www.icann.org/en/help/ombudsman</a><br>
<br>
<br>
Confidentiality<br>
All matters brought before the Ombudsman shall be treated as confidential. <br>
The Ombudsman shall also take all reasonable steps necessary to preserve the<br>
privacy of, and to avoid harm to, those parties not involved in the<br>
complaint being investigated by the Ombudsman.The Ombudsman shall only make<br>
inquiries about, or advise staff or Board members of the existence and<br>
identity of, a complainant in order to further the resolution of the<br>
complaint. The Ombudsman shall take all reasonable steps necessary to<br>
ensure that if staff and Board members are made aware of the existence and<br>
identity of a complainant, they agree to maintain the confidential nature of<br>
such information, except as necessary to further the resolution of a<br>
complaint<br>
<span class="im HOEnZb"><br>
-----Original Message-----<br>
From: <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a><br>
[mailto:<a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>] On Behalf Of Bruce<br>
Tonkin<br>
Sent: Wednesday, January 13, 2016 10:25 PM<br>
To: Accountability Cross Community<br>
<<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
Subject: [CCWG-ACCT] Further Board feedback on Inspection rights<br>
<br>
<br>
</span><div class="HOEnZb"><div class="h5">First, the Board agrees with an inspection right that limited to accounting<br>
books and records. The Board also agrees that the inspection right can be<br>
invoked by a single SO or AC. The inspection right, however, does not need<br>
to be a right reserved to the Sole Designator. As explained in the Board's<br>
Comments on the Third Draft Proposal, the inspection right should be a<br>
community right, and not a right reserved to the Sole Designator. Giving<br>
the Sole Designator a right of inspection - as opposed to making it a right<br>
held by the community - represents a significant and inappropriate change to<br>
the Sole Designator. The Sole Designator can be used to enforce the<br>
community's right of inspection (through the escalation process, if ICANN<br>
errs in response). Particularly when a single SO or AC could invoke the<br>
inspection right, requiring that demand to go through a community process to<br>
direct the Sole Designator seems to add complexity that is not necessary. <br>
<br>
The Board therefore recommends changing the words of Paragraph 20 to "the<br>
CCWG-Accountability recommends including in the ICANN Bylaws the right for<br>
SOs or ACs to inspect as outlined in California Corporations Code 6333,<br>
although this specific article reference would not be mentioned in the<br>
Bylaws." <br>
<br>
For Paragraph 21, "This inspection right is distinct from the Document<br>
Information Disclosure Policy (DIDP). While any eligible party can file a<br>
request according to the DIDP, Inspection Rights are only accessible to SOs<br>
or ACs. The scopes are also different as explained below." "Unlike the<br>
exercise of the other community powers, which require community engagement<br>
and escalation before initiating a request for action by the EC, the<br>
CCWG-Accountability recommends that a petition for inspection be brought<br>
directly by a single SO/AC or by multiple SO/ACs through making a written<br>
demand on ICANN for the requested materials. If the Board refused or ignored<br>
the request, the petitioning SO/AC(s) could then initiate an escalating<br>
community decision-making process to enforce the demand on the Board,<br>
requiring community consensus."<br>
<br>
<br>
The Board agrees with the inclusion of an investigation right, and notes<br>
that the language proposed in the redline reflects the Board's comments.<br>
<br>
Finally, the Board reaffirms its commitment to addressing improvements to<br>
the DIDP in WS2, and thanks the CCWG for the clarification in the document<br>
on the differences between the inspection right and the DIDP.<br>
<br>
Regards,<br>
Bruce Tonkin<br>
<br>
Board Liaison to the CCWG<br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</div></div><br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>