Dear Stephen, All,

Thanks for your input.  
When items items are brought to the attention of the Triage Committee, the committee members have 2 days to respond. 
According to the ccNSO Council Triage Committee Charter (http://ccnso.icann.org/about/council/triage/charter-triage-30mar16-en.pdf ), the Secretariat should allow the Councillors to have two (working) days to decide on the recommendation of the Triage Committee.  This is also included in a graphical representation of the Triage Process, published here: Prioritisation Model followed by the Triage Group 

My apologies, the timeframe between Tuesday 5 April 2016 at 07:24 UTC and Wednesday 6 April 23:59 UTC indeed does not correspond to 2 full working days.  I will make sure to allow for sufficient time at the next occasion, respecting what has been stipulated in the ccNSO Council Triage Committee Charter.

Best regards,

Joke Braeken
ccNSO Policy Advisor 

Follow @ccNSO on Twitter: https://twitter.com/ccNSO
Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/


From: Stephen Deerhake <sdeerhake@nic.as>
Organization: AS Domain Registry
Reply-To: "sdeerhake@nic.as" <sdeerhake@nic.as>
Date: Tuesday 5 April 2016 at 09:59
To: Joke Braeken <joke.braeken@icann.org>, "ccnso-council@icann.org" <ccnso-council@icann.org>
Subject: RE: Triage recommendation 09-2016, Call for Volunteers: Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Implementation and Work Stream 2

 

This has my approval, but going forward I think it is unreasonable of ICANN Staff to put a Triage request to Council wth a 24hr turn-around time:

 

Date of submission to Council: 5 April 2016

Deadline Council decision: 6 April 2016, 23:59 UTC

 

This is really unrealistic.  Who is running the show here?

 

Best Regards,

 

/Stephen

From: owner-ccnso-council@icann.org [mailto:owner-ccnso-council@icann.org] On Behalf Of Joke Braeken
Sent: Tuesday, April 05, 2016 3:24 AM
To: ccnso-council@icann.org
Subject: [ccnso-council] Triage recommendation 09-2016, Call for Volunteers: Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Implementation and Work Stream 2

 

Dear Councillors,

 

Please find below the proposed triage recommendation 09-2016.  Kindly provide me with your input by the end of 6 April, 23:59 UTC, in case you do not agree with the proposed recommendation. Thank you.

 

Topic:   09-2016 - Call for Volunteers:  Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) Implementation and Work Stream 2

Originator: ICANN, CCWG Accountability

Summary of request: With the completion of the Work Stream 1 report and delivery to NTIA in March 2016 <https://www.icann.org/news/announcement-2016-03-10-en>, work is beginning on the implementation of the Work Stream 1 recommendations, followed by the development of a Work Stream 2 report. The CCWG-Accountability is open to anyone who wishes to join, and the group welcomes all interested stakeholders to join in this next phase.

Date received: 29 March 2016

Last day for Comments/input/response, if any: The next meeting of the CCWG-Accountability will take place on Tuesday, 5 April from 19:00-21:00 UTC to review draft Bylaw language as a part of implementation of Work Stream 1.  The group anticipates finalizing discussions on the draft Bylaws in mid-April. After these discussions are completed, the group will focus on the inventory of Work Stream 2 items.

Recommended action, if any: Distribute the call for volunteers via the e-mail lists and twitter. Done.

Expertise needed, if any: policy, legal, strategic, operation, managerial

Date of submission to Triage Committee: 30 March 2016

Recommendation received by Triage Committee: 01 April 2016, 23:59 UTC

Date of submission to Council: 5 April 2016

Deadline Council decision: 6 April 2016, 23:59 UTC

Impact on ccNSO/ccTLDs: middle

 

Best regards,

 

Joke Braeken

ccNSO Policy Advisor 

 

Follow @ccNSO on Twitter: https://twitter.com/ccNSO

Follow the ccNSO on Facebook: https://www.facebook.com/ccnso/