<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div><div></div><div>+1. </div><div>Mary Uduma</div><div><br></div><div><br></div><div><div style="font-size:75%;color:#575757">Sent from Samsung Mobile</div></div></div><br><br><br>-------- Original message --------<br>From: Milton L Mueller <mueller@syr.edu> <br>Date: 27/10/2014 01:06 (GMT+09:00) <br>To: Joseph Alhadeff <joseph.alhadeff@oracle.com>,paf@frobbit.se,elise.gerich@icann.org,manal@tra.gov.eg <br>Cc: internal-cg@icann.org <br>Subject: Re: [Internal-cg] ICG FAQ - reflecting comments received until
23Oct14 .. <br> <br><br>I think the best way to say this - simplest and most accurate - is just to delete the word board and say "ICANN is represented on the ICG by two liaisons...." Making a distinction between the board and a IANA liaison is pointless detail that may confuse ordinary readers more than it clarifies. <br><br>> -----Original Message-----<br>> From: internal-cg-bounces@icann.org [mailto:internal-cg-<br>> bounces@icann.org] On Behalf Of Joseph Alhadeff<br>> Sent: Saturday, October 25, 2014 2:30 PM<br>> To: paf@frobbit.se; elise.gerich@icann.org; manal@tra.gov.eg<br>> Cc: internal-cg@icann.org<br>> Subject: Re: [Internal-cg] ICG FAQ - reflecting comments received until<br>> 23Oct14 ..<br>> <br>> We really don't need any more detail than that...<br>> <br>> Sent from my Android phone using TouchDown (www.nitrodesk.com)<br>> <br>> -----Original Message-----<br>> <br>> From: Manal Ismail [manal@tra.gov.eg]<br>> Received: Saturday, 25 Oct 2014, 2:24PM<br>> To: Patrik Fältström [paf@frobbit.se]; Elise Gerich [elise.gerich@icann.org]<br>> CC: internal-cg@icann.org [internal-cg@icann.org]<br>> Subject: Re: [Internal-cg] ICG FAQ - reflecting comments received until<br>> 23Oct14 ..<br>> <br>> Thanks Elise, Hartmut and Patrik ..<br>> <br>> <br>> <br>> I had the same understanding too and have reflected this in earlier versions<br>> .. Yet I changed the text based on the latest draft shared by Jandyr on behalf<br>> of the small drafting group (himself, Lynn & Xiaodong), which I recall was<br>> also supported by Jean-Jacques and Milton ..<br>> <br>> But I see your point and am happy to revert back to the earlier text, which<br>> stated:<br>> <br>> “The Board is represented on the ICG by one liaison. In addition, there is a<br>> liaison to the ICG from the IANA Department. Both liaisons are there to<br>> provide information about the IANA functions and to keep the Board and ICG<br>> informed about the implications of the transition.”<br>> <br>> <br>> <br>> Is this ok? Should I also add the names ?<br>> <br>> <br>> <br>> Kind Regards<br>> <br>> --Manal<br>> <br>> <br>> <br>> From: Patrik Fältström [mailto:paf@frobbit.se]<br>> Sent: Saturday, October 25, 2014 6:06 PM<br>> To: Elise Gerich<br>> Cc: Manal Ismail; internal-cg@icann.org<br>> Subject: Re: [Internal-cg] ICG FAQ - reflecting comments received until<br>> 23Oct14 ..<br>> <br>> <br>> <br>> I support this.<br>> <br>> <br>> <br>> Patrik<br>> <br>> <br>> <br>> On 25 okt 2014, at 17:13, Elise Gerich <elise.gerich@icann.org><br>> wrote:<br>> <br>> <br>> <br>> Dear Manal,<br>> <br>> <br>> <br>> I thought the discussion on list had indicated that it is more accurate<br>> to say, ICANN is represented on the ICG by two liaisons rather than The<br>> Board is represented on the ICG by two liaisons. Kuo-Wei Wu is the Boards<br>> liaison to the ICG, and my role is a liaison from the ICANNs IANA department.<br>> My participation on the committee is not as a representative of the ICANN<br>> Board.<br>> <br>> <br>> <br>> Best regards,<br>> <br>> -- Elise<br>> <br>> <br>> <br>> <br>> <br>> From: Manal Ismail <manal@tra.gov.eg <mailto:manal@tra.gov.eg><br>> ><br>> Date: Wednesday, October 22, 2014 at 11:48 PM<br>> To: "internal-cg@icann.org <mailto:internal-cg@icann.org> "<br>> <internal-cg@icann.org <mailto:internal-cg@icann.org> ><br>> Subject: [Internal-cg] ICG FAQ - reflecting comments received until<br>> 23Oct14 ..<br>> <br>> <br>> <br>> Dear all ..<br>> <br>> Please find attached, and in Dropbox, a new version of ICG<br>> FAQ reflecting the latest views and comments shared .. I have also attached<br>> below the final compilation of answers to Q#15 & Q#16 for your convenience<br>> .. Kindly note that I took the liberty to change "ICG proposal" or "ICG's<br>> proposal" to "proposal submitted by the ICG", to avoid being misunderstood<br>> as attributing the community's proposal solely to the ICG .. Hope this is ok<br>> with everyone ..<br>> <br>> Happy to receive any further remarks or comments ..<br>> <br>> Kind Regards<br>> <br>> --Manal<br>> <br>> ----------------------------------------------------------<br>> <br>> 15. What is the role of the ICANN Board in preparing the<br>> proposal?<br>> <br>> The ICG is independent of the ICANN Board. The Board is<br>> represented on the ICG by two liaisons (Mrs. Elise Gerich, IANA Staff Expert;<br>> and Mr. Kuo-Wei Wu, ICANN Board Liaison), who are there to provide<br>> information about the IANA functions and to keep the Board and the ICG<br>> informed about the implications of the transition. Like any other member of<br>> the community, the ICANN Board can submit comments through the<br>> established procedures for public comment. Consistent with U.S. federal<br>> government procurement rules, the NTIA needs to have the final proposal<br>> submitted to it by the ICANN Board, but the Board does not have community<br>> approval to modify the proposal submitted by the ICG. When the ICG<br>> submits the final proposal to ICANN, it will also be released to the general<br>> public and to NTIA as well.<br>> <br>> 16. How will ICANN Board handle the final proposal<br>> submitted by the ICG?<br>> <br>> The ICG expects that the final proposal, having achieved<br>> consensus on the Coordination Group and within the Operational<br>> Communities, will be welcomed by the ICANN Board and dutifully<br>> transmitted to NTIA.<br>> <br>> ------------------------------------------------------------<br>> <br>> _______________________________________________<br>> Internal-cg mailing list<br>> Internal-cg@icann.org<br>> https://mm.icann.org/mailman/listinfo/internal-cg<br>> <br>> <br>> <br>> _______________________________________________<br>> Internal-cg mailing list<br>> Internal-cg@icann.org<br>> https://mm.icann.org/mailman/listinfo/internal-cg<br>_______________________________________________<br>Internal-cg mailing list<br>Internal-cg@icann.org<br>https://mm.icann.org/mailman/listinfo/internal-cg<br></body>