[ALAC] Fwd: [CCWG-ACCT] Timeline for WS1 Bylaws

León Felipe Sánchez Ambía leonfelipe at sanchez.mx
Thu Mar 10 08:33:14 UTC 2016


FYI.

We’ll be having a tight timeline (again)


Best regards,


León

> Inicio del mensaje reenviado:
> 
> De: Mathieu Weill <mathieu.weill at afnic.fr>
> Asunto: [CCWG-ACCT] Timeline for WS1 Bylaws
> Fecha: 9 de marzo de 2016, 5:38:00 p.m. GMT
> Para: "'CCWG Accountability'" <accountability-cross-community at icann.org>
> 
> Hello everyone,
> 
> This is a brief update on the next steps for our work on drafting bylaws to implement the CCWG report. The timeline is tight. Read on to see why.
> 
> At our meeting on Friday we discussed the iterative approach for bylaws drafting, with the co-chairs and rapporteurs forming a first line triage team to check consistency between the draft Bylaws and the CCWG Final Report. Then the documents will be public for CCWG scrutiny and comment before being updated.
> 
> We didn’t have a view about timing on Friday other than that it would have to be soon. Now we have some more information on that.
> 
> We co-chairs were joined by rapporteurs at a dinner on Monday night which included CWG reps, Board members and ICANN staff. The purpose was to make sure the implementation process is well coordinated between the groups in the coming weeks.
> 
> Larry Strickling was at the dinner, and he set out his thoughts about timeframes. An important piece of information from him was that the N.T.I.A. won’t complete its review and assessment of the proposal until the bylaws that implement them are in place (with commencement happening post-transition).
> 
> NTIA has said publicly that it plans to complete its report within about 90 days of receiving the Stewardship and Accountability proposals on 10 March, presuming that the Chartering Organisations approve our proposal. That is because they wish to give the U.S. Congress a suitable period of time to consider their report before the Congress goes into recess for the summer on 15 July.
> 
> Taking these two points together, it means we need to fit the following steps and *rough* dates together:
> 
> Friday 8 April:     CCWG finishes draft bylaws
> 
> then            Board approves draft bylaws for public comment
> 
> Friday 15 April:    Open Public Comment for bylaws
> 
> Sunday 15 May:     Close Public Comment for bylaws
> 
> then            Follow up changes to draft Bylaws based on public comments
>                    and
>                    CCWG sign off of final draft bylaws
> 
> Tuesday 31 May:    Board approves draft bylaws
> 
> 
> In our view, this timeframe is tight but manageable.
> 
> We are in discussion with our external Counsel about how to progress the draft Bylaws over the next couple of weeks. They have some ideas that include intensive discussions with ICANN legal, who know the bylaws well, and will be working on the quick production of a first draft set of bylaws.
> 
> The Implementation Oversight Team will do a very rapid turnaround on the draft, and get it out to you asap, along with a note from our lawyers to confirm compliance with our report.  Our intention is that there is at least four days and preferably a week for review and comments for CCWG members and participants. Then the draft bylaws  will be finalised taking those comments into account, and given to the Board who we expect will rapidly put them out for public comment.
> 
> It’s important for us all to see this as a translation exercise: turning our Proposal into Bylaws. Because of the work we have all done, the intention of the Proposal is clear. Turning that into draft Bylaws language should be reasonably straightforward, and if there are areas of dispute and disagreement, they should be few.
> 
> 
> We will have the chance to discuss this schedule at our implementation meeting on Thursday, but we invite you to consider the draft schedule above, the realities driving it, and to discuss all this in the lead up to our meeting.
> 
> 
> Best,
> 
> Mathieu, Thomas and Leon.
> 
> 
> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org <mailto:Accountability-Cross-Community at icann.org>
> https://mm.icann.org/mailman/listinfo/accountability-cross-community <https://mm.icann.org/mailman/listinfo/accountability-cross-community>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20160310/949b11d8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://atlarge-lists.icann.org/pipermail/alac/attachments/20160310/949b11d8/signature.asc>


More information about the ALAC mailing list