[CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version

Paul Rosenzweig paul.rosenzweig at redbranchconsulting.com
Sun Apr 3 15:32:07 UTC 2016


Kavouss is absolutely right.  A side-by-side or redline comparison is essential ….

 

Paul

 

Paul Rosenzweig

paul.rosenzweig at redbranchconsulting.com

O: +1 (202) 547-0660

M: +1 (202) 329-9650

 <http://www.redbranchconsulting.com/index.php?option=com_content&view=article&id=19&Itemid=9> My PGP Key

 

From: accountability-cross-community-bounces at icann.org [mailto:accountability-cross-community-bounces at icann.org] On Behalf Of Kavouss Arasteh
Sent: Sunday, April 3, 2016 9:52 AM
To: Matthew Shears <mshears at cdt.org>
Cc: CCWG Accountability <accountability-cross-community at icann.org>
Subject: Re: [CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version

 

Dear Mathieu,

I have not yet started to examine the doc. However, it is a usual practice everywhere, except CCWG , that any revision to an existing document MUST be made with revision mark in order to enable the proper verification of the changes.

Please understand the matter in a positive direction.

On the other hand, we are asked to examine the draft bylaws which is amendments to the existing bylaws IS THE HIGHEST LEVEL OF LEGAL TEXT WHICH GOVERS THE FUNCTIONING OF ICANN.

we therefore need to be very cautious on how to examine that.

I therefore believe, we need more time between 2-3 weeks to do so.

However, if like the supplemental proposal PREOPARATION everything is purposely scheduled to be done in rush that is something else.

Regards

Kavouss 

 

2016-04-03 15:20 GMT+02:00 Matthew Shears <mshears at cdt.org <mailto:mshears at cdt.org> >:

Agree that if available a comparative doc would be incredibly useful.

Thanks

 

On 4/3/2016 9:16 AM, Sébastien Bachollet wrote:

Thanks Mathieu for those documents.

May I ask for the curent version of the bylaws in the same format of the proposed one’s? (it would have been useful to have comparative document, but I am not requesting it now if it is not an already existing document).

And as some will ask for, all the same documents in PDF will be useful too.

All the best

SeB

 

Skills are useful but diversity is essential.

 

Sébastien Bachollet

+33 6 07 66 89 33

Blog: http://sebastien.bachollet.fr/

Mail: Sébastien Bachollet <sebastien at bachollet.com <mailto:sebastien at bachollet.com> >

 

De : <accountability-cross-community-bounces at icann.org <mailto:accountability-cross-community-bounces at icann.org> > on behalf of Mathieu Weill <mathieu.weill at afnic.fr <mailto:mathieu.weill at afnic.fr> >
Date : dimanche 3 avril 2016 14:16
À : CCWG Accountability <accountability-cross-community at icann.org <mailto:accountability-cross-community at icann.org> >
Objet : [CCWG-ACCT] Fwd: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version

 

Dear colleagues, 

 

In anticipation of our calls this week, please find below a note from the lawyers group, the draft bylaws as well as an issue list. 

 

It is important to read the lawyers notes as they quite efficiently describe the context and status of the work. Please review them for any process related question. 

 

The purpose of our calls this week will be to address the issue list questions (questions 1-7 & 25-34 are for the CCWG, the others for CWG). 

 

Should any other issue be added to the list based on your respective reviews, please raise your questions on the list for transparency. 

 

Best regards,

Mathieu

---------------

Depuis mon mobile, désolé pour le style


Début du message transféré :

Expéditeur: John Jeffrey via bylaws-coord <bylaws-coord at icann.org <mailto:bylaws-coord at icann.org> >
Date: 3 avril 2016 13:16:28 UTC+2
Destinataire: bylaws-coord at icann.org <mailto:bylaws-coord at icann.org> 
Cc: "Flanagan, Sharon" <sflanagan at sidley.com <mailto:sflanagan at sidley.com> >, "Cc: Zagorin, Janet S." <jzagorin at sidley.com <mailto:jzagorin at sidley.com> >, "Hilton, Tyler" <thilton at sidley.com <mailto:thilton at sidley.com> >, ICANN-Adler <ICANN at adlercolvin.com <mailto:ICANN at adlercolvin.com> >, "Hofheimer, Joshua T." <jhofheimer at sidley.com <mailto:jhofheimer at sidley.com> >, "Mohan, Vivek" <vivek.mohan at sidley.com <mailto:vivek.mohan at sidley.com> >, "Clark, Michael A." <mclark at sidley.com <mailto:mclark at sidley.com> >, "Boucher, Rick" <rboucher at sidley.com <mailto:rboucher at sidley.com> >, Sidley ICANN CCWG <sidleyicannccwg at sidley.com <mailto:sidleyicannccwg at sidley.com> >, "Kerry, Cameron" <ckerry at sidley.com <mailto:ckerry at sidley.com> >, "McNicholas, Edward R." <emcnicholas at sidley.com <mailto:emcnicholas at sidley.com> >, Daniel Halloran <daniel.halloran at icann.org <mailto:daniel.halloran at icann.org> >, Amy Stathos <amy.stathos at icann.org <mailto:amy.stathos at icann.org> >, "Boelter, Jessica C.K." <jboelter at sidley.com <mailto:jboelter at sidley.com> >, "Fuller, Miles" <wfuller at sidley.com <mailto:wfuller at sidley.com> >, "Tam, Tennie H." <tennie.tam at sidley.com <mailto:tennie.tam at sidley.com> >
Objet: [bylaws-coord] DRAFT NEW ICANN BYLAWS - 2 April 2016 version
Répondre à: John Jeffrey <john.jeffrey at icann.org <mailto:john.jeffrey at icann.org> >

Dear Bylaws Coordination Group,

Please find attached a document – DRAFT NEW ICANN BYLAWS (vers. 2Apr) (“DRAFT BYLAWS”) for your review and discussion. As you will recall the last full draft was provided to you on 18 March, with the promise to provide another full turn of the DRAFT BYLAWS for your review today on 2 April.  The DRAFT BYLAWS attached is the current working draft among the legal drafting group.  There is also an Issue List attached, which are a set of additional questions and clarifications requested from the Bylaws Coordination Group.

 We ask that you share the attachments with your CCWG, ICG and CWG colleagues who will be reviewing this during this critical work week

Recent Work – During the past two weeks the legal drafting group, made up of Sidley’s team, Adler’s team and ICANN's Legal team reviewed and worked through mark ups and redrafts of the various sections of new ICANN Bylaws.  Also, we have held four separate meetings with the Bylaws Coordination Group during this two-week period asking questions and incorporating that feedback into the new draft.  There is likely to be the need for some additional discussions as we work toward a public comment version of the new ICANN bylaws.

More Work to Do – There is still work to do on the DRAFT BYLAWS, in identifying and working through any remaining provisions in the draft that are not clear, finding any remaining open issues, improving the provisions, and polishing the draft before publication for public comment.  The legal teams remain engaged in review mode and are available for questions and comments during this period.

Legal Teams have not yet “certified” – Since a) the Bylaws Coordination Group, CWG and CCWG have not yet reviewed and reacted to these DRAFT BYLAWS, b) there are still remaining open issues, and c) there is still review and polishing to be done by the legal teams – the legal teams have not indicated yet that the current DRAFT BYLAWS fully meets the recommendations within the Proposals.

As we have indicated above there is still work to be done, including receiving the feedback from those reviewing these DRAFT BYLAWS this week before the legal teams will be in a position to certify the posting version for Public Comment

Next Steps –

1)   Now until 13 April – members of CCWG, CWG, Bylaws Coordination Group, Board and ICG to complete review of these DRAFT BYLAWS and provide feedback to legal teams;

2)   Now until 18 April, (with particular focus during week of 13-18 April) – legal teams to update DRAFT BYLAWS working in coordination with the Bylaws Drafting Group;

3)   20 April – posting date for public comment period for new proposed bylaws – with legal teams supporting that the new proposed bylaws meets the proposal recommendations.

———

As before, we look forward to working with all of you in the coming days, to get ICANN’s Bylaws in the best form possible to effectuate these important changes.

We hope these views of the documents are useful and that you receive them in the spirit that they are offered… to help all of us to be able to collaborate and work through these Bylaws changes in the most effective way possible — to enable the creation of a new and stronger, community empowered ICANN.

John Jeffrey, Holly Gregory, and Rosemary Fei

_____________________ 

____________________

 

 

 

 

 

_______________________________________________
bylaws-coord mailing list
bylaws-coord at icann.org <mailto:bylaws-coord at icann.org> 
https://mm.icann.org/mailman/listinfo/bylaws-coord

_______________________________________________ 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 

 

_______________________________________________
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

 

-- 
 
Matthew Shears | Director, Global Internet Policy & Human Rights Project
Center for Democracy & Technology | cdt.org <http://cdt.org> 
E: mshears at cdt.org <mailto:mshears at cdt.org>  | T: +44.771.247.2987 <tel:%2B44.771.247.2987> 
 
CDT's Annual Dinner, Tech Prom, is April 6, 2016. Don't miss out - register at cdt.org/annual-dinner <http://cdt.org/annual-dinner> .


_______________________________________________
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

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20160403/e7af7548/attachment-0001.html>


More information about the Accountability-Cross-Community mailing list