[CCWG-ACCT] Work Stream 2 - Board position

[Seun Ojedeji]

Hello,

If this is on the assumption that current board commitments may not be
honoured by upcoming board members. Then I would say it will be unfortunate
for such board member as I expect that not all board member will be new so
the historical status will be passed across to incoming members.

However when such board member doesn't comply, one will then expect that
the compliance/enforcement mechanisms put in place in WS1 Will kick in.
Therefore getting commitment to pursue what has been defined in WS2 from
board will be an important exhibit towards ensuring compliance.

Regards

Sent from my Asus Zenfone2
Kindly excuse brevity and typos.
On 6 Nov 2015 05:00, "Nigel Roberts" <nigel at channelisles.net> wrote:

> I find this helpful. Well done.
>
> I do have some small reservations about the final para which reads "May we
> therefore ask the Board to formally commit to honoring WS2 recommendations?"
>
> They can commit all they like. But what matters is whether there is any
> enforceability (to borrow a term from a source I respect) should a future
> Board not live up to the committments of the present Board.
>
> So I would hope the Board would answer with HOW they would guarantee their
> commitment (which, in good faith, I believe to be indubitable)
>
>
>
> Nigel
>
>
> On 11/05/2015 07:43 PM, Thomas Rickert wrote:
>
>> Dear Bruce,
>> with this e-mail, we would like to formally approach you in your capacity
>> as Board liaison to provide some clarity on how the Board wishes to deal
>> with WS2.
>>
>> As you know, the concept of two Work Streams has been introduced by the
>> Board more than a year ago as follows:
>>
>> “Following the community requested 21-day second round of comments, ICANN
>> received 17 comments. Based on the input received from these comments,
>> staff believes that the strong community comments in the second round of
>> comments support integrating the originally proposed structure
>> (CCG/Coordination Group) into establishing a Cross Community Working Group
>> (CCWG) that incorporates some key elements that have arisen in the
>> dialogues. Additionally, given the input over the course of the dialogue on
>> this process, it's suggested that the CCWG has two work steams, one focused
>> on accountability in view of ICANN's changing historical relationship with
>> the USG, and the second, on the broader accountability issues the community
>> would like to bring to the forefront.”
>>
>> (https://www.icann.org/resources/pages/process-next-steps-2014-10-10-en)
>>
>> This concept was confirmed by NTIA on several occasions and our group has
>> structured its work plan accordingly.
>>
>> We do note that the Board has recently suggested to deal with certain
>> items in the framework of reviews and continuous improvements. However,
>> many CCWG colleagues are concerned that this might lead to a situation
>> where the items the CCWG has identified as WS2 items would not be dealt
>> with with the required attention.
>>
>> We are also aware of concerns that ICANN must not leave major changes to
>> a later point in time to avoid uncertainty about ICANN changing e.g. its
>> governance model after the transition. We note that areas of work for WS2
>> will be published with our report and included in our recommendations. It
>> is a finite list of clearly identified subjects, all of which are
>> important, but none of which would substantially change ICANN other than
>> further enhancing its accountability.
>>
>> May we therefore ask the Board to formally commit to honoring WS2
>> recommendations?
>>
>> Thank you for your attention to this matter.
>>
>> Kind regards,
>> León Sanchez
>> Mathieu Weill
>> Thomas Rickert
>>
>>
>> _______________________________________________
>> Accountability-Cross-Community mailing list
>> Accountability-Cross-Community at icann.org
>> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>>
>> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20151106/506f54fe/attachment.html>