[Internal-cg] bylaws feedback
jjs at dyalog.net
Tue May 17 10:04:08 UTC 2016
this is to inform you that my email by default, jjs at dyalog.net , had a problem but has now been reset properly.
If there have been any emails exchanged on this list over the past 5 days, would you be kind enough to send me a copy? Thank you.
----- Mail original -----
De: "Russ Housley" <housley at vigilsec.com>
À: "Alissa Cooper" <alissa at cooperw.in>
Cc: "ICG Group" <internal-cg at ianacg.org>
Envoyé: Vendredi 13 Mai 2016 00:32:06
Objet: Re: [Internal-cg] bylaws feedback
Looks ready for sending to me.
-----Ursprüngliche Nachricht----- From: Alissa Cooper
Sent: Wednesday, May 11, 2016 9:11 PM
To: Kavouss Arasteh
Cc: Lynn St.Amour ; Milton L Mueller ; IANA etc etcCoordination Group
Subject: Re: [Internal-cg] bylaws feedback
I’d like us to close out on this. If anyone objects to us submitting the text below as a public comment on the draft bylaws, please say so by Friday, May 13 at 23:59. If there are no objections, I’ll submit it.
The ICG appreciates the opportunity to comment on the draft ICANN Bylaws.
The ICG previously communicated concerns about Section 1.1(d)(ii) to the Bylaws drafting group . However, these concerns were not addressed in the draft Bylaws that were posted for public comment.
Section 1.1(d) "grandfathers" a number of agreements into the Bylaws in order to prevent parties from challenging those agreements on the basis that they violate the ICANN Mission statement. Under Section 1.1(d)(ii), (A) applies to RA/RAA agreements; (B)-(D) apply to agreements between ICANN and the NRO, ASO, IETF, RZM, and PTI; and (E) applies to ICANN's Five-Year Strategic Plan and Five-Year Operating Plan. (F) applies the grandfathering to renewals of the agreements appearing in (B)-(E).
The ICG process was fashioned to ensure that the transition plans reflected the consensus of the Internet community and allowed the operational communities to define their own transition plans. The ICG and the CCWG proposals define those wishes, and any changes to the Bylaws were to be to implement those wishes, nothing more. Yet Sections 1.1(d)(ii)(B)-(E) are outside the scope of both the ICG and the CCWG proposals. Unlike Section 1.1(d)(ii)(A), the substance of which was debated in the CCWG and is documented in paragraph 147 of the CCWG proposal, the substance of (B)-(E) have not enjoyed appropriate community involvement or review. These sections affect much of the Internet community since they apply to agreements with a variety of external parties, including all of the operational communities.
Because several of the referenced agreements have not yet been written and most have not yet been agreed to by the relevant parties, the draft Bylaws essentially allow these external agreements to define ICANN's Mission. This seems like a bad idea for many reasons, not the least of which is that it creates the possibility for the agreements to contradict or circumvent the desires of the community who worked hard to clarify and correctly state ICANN’s Mission throughout the IANA stewardship transition process (see paragraphs 140-147 of the CCWG proposal).
The ICG believes that in order for the Bylaws to be considered consistent with the transition plans, Sections 1.1(d)(ii)(B)-(E) need to be removed, and Section 1.1(d)(ii)(F) needs to be edited to apply only to Section 1.1(d)(ii)(A). This assumes that (F) is indeed called for by paragraph 147 of the CCWG proposal, which we leave for the CCWG to judge.
Alissa Cooper on behalf of the ICG
Internal-cg mailing list
Internal-cg at mm.ianacg.org
More information about the Internal-cg