[Ws2-staff_acct] CCWG-Accountability-WS2-StaffAcct - Meeting ​Tuesday February 20 1900 UTC CANCELLED

[Bernard Turcotte]

Minor cut and paste error - apologies - fixed below

 B.

On Mon, Feb 19, 2018 at 9:25 AM, Bernard Turcotte <
turcotte.bernard at gmail.com> wrote:

> All,
>
> We have failed to obtain the 5 required confirmations to be able to hold
> the above mentioned call and are therefore forced to cancel it.
>
> As noted below we will now consider the current draft, with amendments
> suggested by Jordan, to be the final recommendations
> ​for  Staff Accountability ​
> ​
> which will be sent to the CCWG-Accountability-WS2 plenary Wednesday 21
> February 1200 UTC unless there is significant objection on the list prior
> to the deadline.
>
> Thank You.
>
> ​
> Bernard Turcotte
> ICANN Staff Support to the CCWG-Accountability-WS2
>
>
> On Wed, Feb 14, 2018 at 7:02 PM, Bernard Turcotte <
> turcotte.bernard at gmail.com> wrote:
>
>> All,
>>
>> Given the positive comments with respect to the latest draft of the
>> recommendations we are proposing the following way forward:
>>
>>
>>    - We are proposing a meeting of the Staff Acct sub-group
>>    ​​
>>    Tuesday February 20 1900 UTC to finalize the latest version of the
>>    recommendations.
>>       - As per the current procedure we will require 5 confirmation of
>>       attendance to confirm the meeting 36 hours prior to the proposed meeting
>>       time.
>>       - Please reply to this email or to the list to confirm you
>>       participation by Monday 19 February 0700 UTC. If we do not obtain 5
>>       confirmations the meeting will be cancelled.
>>    - If we are obliged to cancel the Tuesday 20 February 1900 UTC
>>    meeting we will consider that the latest draft of the recommendations as
>>    final and these will be forwarded to the plenary 21 February for a reading
>>    at its Wednesday 28 February 1900 UTC meeting.
>>
>> Thank You.
>>
>> Bernard Turcotte
>> ICANN Staff Support to the CCWG-Accountability-WS2
>>
>> for Jordan.
>>
>> On Tue, Feb 13, 2018 at 12:54 PM, Jordan Carter <jordan at internetnz.net.nz
>> > wrote:
>>
>>> Thanks Cheryl, Klaus!
>>>
>>> Pam, others?
>>>
>>> Jordan
>>>
>>> On Wed, 14 Feb 2018 at 3:14 AM, Klaus Stoll <kdrstoll at gmail.com> wrote:
>>>
>>>> Dear Jordan
>>>>
>>>> Greeting. Keeping things short and sweet: I support the changes to
>>>> Recommendation 3.
>>>>
>>>> Yours
>>>>
>>>> Klaus
>>>>
>>>> On 2/12/2018 11:34 PM, Jordan Carter wrote:
>>>>
>>>> Hi all
>>>>
>>>> Thanks to Pam and to others for comments and discussion of the proposed
>>>> updated recommendations.
>>>>
>>>> I've had a call with ICANN staff and with Avri as the former
>>>> rapporteur, and I've carefully considered the on list traffic.
>>>>
>>>> I'm proposing a different approach that works service levels back in,
>>>> closer to our original recommendations. You can find that in the re-revised
>>>> Recommendation 3.
>>>>
>>>> This approach may result in ICANN org or board pushback, but I think it
>>>> responds to their key concern about scope of the work on service levels
>>>> while providing a way to make that work, and inviting the organisation to
>>>> commit to service level targets and guidelines that are meaningful for the
>>>> community.
>>>>
>>>> PDFs with track changes and clean are attached.
>>>>
>>>> *I would be grateful if you could share comments about this asap, as we
>>>> will need to take it through the plenary for approval as a first reading on
>>>> 21 Feb. *That means in theory 14 Feb is our deadline to send the
>>>> document around.
>>>>
>>>> *Could I ask for comments within the next 24hrs from send time for this
>>>> message?*
>>>>
>>>> I paste the revised proposed language below too for your reference.
>>>>
>>>> Thanks in advance,
>>>> Jordan
>>>>
>>>>
>>>> *3. ICANN Organization should work with the community to develop and
>>>> publish service level targets and guidelines (similar to the Service Level
>>>> Agreement for the IANA Numbering Services) that clearly define the services
>>>> provided by ICANN to community as well as the service level target for each
>>>> service. In this context:*
>>>>
>>>>
>>>>
>>>> *a) ICANN should work with the community to identify and prioritize the
>>>> classes of services for which service level targets and guidelines will be
>>>> implemented, and to define how service level targets and guidelines will be
>>>> defined.*
>>>>
>>>>
>>>>
>>>> *b) Develop clear and reasonable guidelines for expected behavior
>>>> between ICANN organization and the community for those newly-identified
>>>> activities. *
>>>>
>>>>
>>>>
>>>> *c) Develop and publish the resulting service levels, targets and
>>>> guidelines in a single area on icann.org <http://icann.org/>. These targets
>>>> and guidelines should also inform any regular information acquisition
>>>> mechanism described in recommendation 2 of this report.*
>>>>
>>>>
>>>>
>>>> *The structure and specific timing of this effort should be determined
>>>> by ICANN organization (but be substantially under way before the end of
>>>> 2018). We suggest that representatives of ICANN's executive team, the ICANN
>>>> Board, and SO/AC Leadership participate in this effort to ensure a
>>>> constructive dialogue across all parts of the ICANN community. This work
>>>> should be, and be seen as, a genuine chance for collaboration and improved
>>>> relationships between the Board, organization and community. *
>>>>
>>>>
>>>>
>>>> --
>>>> Jordan Carter
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Ws2-staff_acct mailing listWs2-staff_acct at icann.orghttps://mm.icann.org/mailman/listinfo/ws2-staff_acct
>>>>
>>>> --
>>> Jordan Carter
>>> Group Chief Executive, InternetNZ
>>> +64-21-442-649 <+64%2021%20442%20649>
>>>
>>> Sent on the run, apologies for brevity
>>>
>>> _______________________________________________
>>> Ws2-staff_acct mailing list
>>> Ws2-staff_acct at icann.org
>>> https://mm.icann.org/mailman/listinfo/ws2-staff_acct
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ws2-staff_acct/attachments/20180219/036433c6/attachment.html>