There is a conflict between this call and the Reconvened IGO/INGO WG.  I will try to monitor the Adobe Room for this call, but feel I should participate in the RIGOINGOWG call.

Greg

On Thu, Aug 17, 2017 at 2:12 AM, Rinalia Abdul Rahim <rinalia.abdulrahim@gmail.com> wrote:
Apologies for mislabeling. By "collective responsibility" I meant "collective accountability". Pre-breakfast emailing...

Best regards,

Rinalia 

Rinalia Abdul Rahim

On Aug 17, 2017, at 7:59 AM, Rinalia Abdul Rahim <rinalia.abdulrahim@gmail.com> wrote:

Hi. 

This is a personal input from me and not an input from the Board. 

Regarding the responses to the Board's Track 2 and 3 comments on collective responsibility, I think it may be useful to apply the frame of accountability that guided the work of CCWG-Accountability (i.e., participation, transparency, appeal and redress). If within each SO/AC (including for engagement in EC processes), the standards for participation, transparency, appeals and redress apply, then the robustness of decision-making rises and the quality of the aggregate result rises.  This to my mind would enhance "collective responsibility."

The Ombudsbeing (as an alternative to Ombudsman or woman :) can be an additional part of the appeals and redress process as a safeguard in case internal SO/AC processes are not sufficient or failed or preferred by affected community members.  I think allowing for the Ombuds to be invoked in EC-related matters is generally fine.

I believe each SO/AC sets its own standards on participation, transparency, appeal and redress.  The collective "average" on standards could rise with the proposed learning and sharing of best-practices across community and SO/ACs.  What's important is that the SO/ACs are open to it and it seems from the public comments responses that they generally are. That's a good start.

I hope this is useful.

Best regards,

Rinalia

On Thu, Aug 17, 2017 at 6:03 AM, Steve DelBianco <sdelbianco@netchoice.org> wrote:
For those who may desire it for our call, attached is a PDF version of the Google Sheet with proposed responses to public comments 

From: Cheryl Langdon-Orr <langdonorr@gmail.com>
Date: Wednesday, August 16, 2017 at 6:44 PM
To: "ws2-so_ac@icann.org" <ws2-so_ac@icann.org>, Steve DelBianco <sdelbianco@netchoice.org>, farzaneh badii <farzaneh.badii@gmail.com>, Thomas Rickert <thomas@rickert.net>
Cc: Brenda Brewer <mssi-secretariat@icann.org>
Subject: ​Please join the Work Stream 2 - SO/AC Accountability Subgroup Meeting #29 on Thursday 17th August @ 1300 UTC.


Please join the Work Stream 2 - SO/AC Accountability Subgroup Meeting #29 on Thursday 17th August @ 1300 UTC.

CALL DETAILS: Link to Adobe Connect: https://participate.icann.org/mssi-projects 

Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. Enter your Phone Number* (Remember to change the Country Code if needed). 

After joining the call, as a courtesy to others and the presenters, please MUTE your phone. 
This can be done by selecting *6 on your keypad. To UNMUTE select *6 again.  



​Agenda 

0. Call Admin and Roll Call / Apologies (2min-
​ 
 CLO
 )  Apologies 

1. Welcome - Opening Remarks - Our aim and purpose for today's call (3-5 min- 
​​
SDB, CLO)

2. Review (brief) of last meeting  records here and any Action Items (5-10 min- SDB, CLO) 
Refer here to  our Google Doc and any list interaction on changes to draft text. 

3. Primary Agenda Item - Discussion 
(25
​ -35​
 min SDB, FB)
  •  Review Public Comment documentation, and  consideration of any amendments to our recommendations, from our last call and intersession list exchanges. 
Please see  this Document for reference on this item (to be displayed in the call) 

​4​
.  Next Steps. Standing Item - (5 min- CLO, SB)
  • - CCWG still need to determine if any changes to our report are significant or not.
    - If significant changes are recommended, CCWG-Accountability WS2 may require a second public consultation.
    - If changes are not significant, CCWG-Accountability WS2 can forward final recommendations to Chartering Organizations for approval, and then to the ICANN Board for consideration and adoption. Noting the timeline and Key milestone dates.


5.  AOB / Meeting Schedule (5 min- CLO)
August Dates:
Thursday 24th @ 1900 UTC
Thursday 31st @ 0500 UTC



_______________________________________________
Ws2-so_ac mailing list
Ws2-so_ac@icann.org
https://mm.icann.org/mailman/listinfo/ws2-so_ac



_______________________________________________
Ws2-so_ac mailing list
Ws2-so_ac@icann.org
https://mm.icann.org/mailman/listinfo/ws2-so_ac