<div dir="ltr"><div>Dear Joe</div><div>We really do not know what is the matter.</div><div>People became emmotional on something that may exist at all.</div><div>We need to first hear from the Board Liasion to ICG and then possibly act as I suggested not more not less.</div><div>Reagrds</div><div>Kavouss </div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-05-03 13:34 GMT+02:00 Joseph Alhadeff <span dir="ltr"><<a href="mailto:joseph.alhadeff@oracle.com" target="_blank">joseph.alhadeff@oracle.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A clarification for those more nuanced in this topic.� Is the issue ICANN staff messaging or a discord across ICANN messaging across staff?� I gather part of this issue arises from a disconnect between formal positions previously espoused and current actions which call them into question and a need for a public reaffirmation of the former and a cessation of actions that undermine them...<br>
<span class="im HOEnZb"><br>
Joe<br>
<br>
Sent from my iPad<br>
<br>
</span><div class="HOEnZb"><div class="h5">> On Apr 29, 2015, at 2:57 PM, Alissa Cooper <<a href="mailto:alissa@cooperw.in">alissa@cooperw.in</a>> wrote:<br>
><br>
> Since there seems to be good support for us writing a statement as outlined below, I\u2019ve written a draft below. I incorporated the suggestions from Jean-Jacques. Please comment.<br>
><br>
> \u2014<br>
><br>
> ICG Statement on Contracts and Other Agreements<br>
><br>
> As the development of the proposal for the IANA stewardship transition proceeds, operational communities have begun discussions with ICANN concerning contracts and other agreements called for in their community transition proposals. The ICG expects -- as it has from the very beginning of the transition process -- that all interested parties, including ICANN staff, express their opinions about the transition proposals openly and transparently within the community processes. This includes opinions about the provisions, principles, and mechanisms associated with contracts or other agreements between the communities and the IANA functions operator. Attempts to alter or deviate from the community consensus proposals through private negotiations undermine the legitimacy of the transition proposal development process. At a time when all of the communities are focused on accountability, all parties have the same obligation to carry out discussions in an open manner within established community processes.<br>
><br>
> ---<br>
><br>
>> On Apr 26, 2015, at 1:33 PM, Alissa Cooper <<a href="mailto:alissa@cooperw.in">alissa@cooperw.in</a>> wrote:<br>
>><br>
>> The thread below as well as the following paragraph in Milton\u2019s memo raised a question for me:<br>
>><br>
>> \u201c... negotiations between CRISP and ICANN legal raise a very important process issue. As ICG we have viewed ourselves as an entity that receives consensus proposals from the operational communities and does not try to alter them. Shouldn\u2019t we expect the same from ICANN? If ICANN legal is attempting to make major alterations in the terms of the contractual rights exercised by an operational community as part of the transition, isn\u2019t it interfering with the consensus proposal of the affected operational community? There is also the fact that these negotiations are going on behind the scenes and are not transparent to the whole involved community.\u201d<br>
>><br>
>> My understanding is that the IETF folks are encountering some of the same things as CRISP. Do we think it would help if the ICG put out a statement of some sort indicating that we continue to expect all interested parties, including ICANN staff, to express their opinions about the transition proposals openly and transparently within the community processes? And that includes opinions about the acceptability of principles and mechanisms associated with contractual arrangements between the communities and the IANA functions operator?<br>
>><br>
>> Alissa<br>
>><br>
>>> On Apr 24, 2015, at 5:34 AM, Lynn St.Amour <Lynn@LStAmour.org> wrote:<br>
>>><br>
>>> Milton,<br>
>>><br>
>>> A big +1 to "Let me also remind us that this is a bottom up process and ICG has no business modifying or rejecting proposals based on what it thinks NTIA wants.� NTIA\u2019s criteria are public us and they do _not_ include any thing about splitting the IANA functions."<br>
>>><br>
>>> Lynn<br>
>>><br>
>>>> On Apr 23, 2015, at 10:15 AM, Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>> wrote:<br>
>>>><br>
>>>> Hi, reading these notes, I see this from Keith:<br>
>>>><br>
>>>> \u201cNTIA suggests that anything which threatens to split the IANA functions would be difficult for them to accept \u2010 so the idea that Protocols, Numbers or Names would have independent right of contract termination maybe troublesome to NTIA ?\u201d<br>
>>>><br>
>>>> I was not there for the full context, of course, so I may be misinterpreting, but on its face this is incorrect, in my opinion. I would like to know from Keith when and where NTIA suggested this.<br>
>>>><br>
>>>> Let\u2019s keep in mind that IETF already has the right to \u201csplit\u201d or terminate its MoU with ICANN and has had that right for 15 years through various iterations of the IANA contract. CRISP has proposed something similar.<br>
>>>><br>
>>>> Let me also remind us that this is a bottom up process and ICG has no business modifying or rejecting proposals based on what it thinks NTIA wants. NTIA\u2019s criteria are public us and they do _not_ include any thing about splitting the IANA functions.<br>
>>>><br>
>>>> --MM<br>
>>>><br>
>>>> From: Internal-cg [mailto:<a href="mailto:internal-cg-bounces@ianacg.org">internal-cg-bounces@ianacg.org</a>] On Behalf Of Jennifer Chung<br>
>>>> Sent: Wednesday, April 22, 2015 12:10 PM<br>
>>>> To: <a href="mailto:internal-cg@ianacg.org">internal-cg@ianacg.org</a><br>
>>>> Subject: Re: [Internal-cg] ICG Call #15: Attendance list and Chat Transcript<br>
>>>><br>
>>>> Apologies, the attachment was missing to the last email.� Attached please find the chat transcript for ICG Call 15.<br>
>>>><br>
>>>> Best,<br>
>>>><br>
>>>> Jennifer<br>
>>>><br>
>>>> From: Jennifer Chung [mailto:<a href="mailto:jen@icgsec.asia">jen@icgsec.asia</a>]<br>
>>>> Sent: Wednesday, April 22, 2015 12:09 PM<br>
>>>> To: '<a href="mailto:internal-cg@ianacg.org">internal-cg@ianacg.org</a>'<br>
>>>> Subject: ICG Call #15: Attendance list and Chat Transcript<br>
>>>><br>
>>>> Dear All,<br>
>>>><br>
>>>> Please find the chat transcript (attached) and the attendance roll call (below) for Call 15.� Please let me know if you note any discrepancies:<br>
>>>><br>
>>>> ICG Members<br>
>>>> Kavouss Arasteh (GAC)<br>
>>>> Paul Wilson (NRO)<br>
>>>> Daniel Karrenberg (RSSAC)<br>
>>>> Keith Davidson (ccNSO)<br>
>>>> Alissa Cooper (IETF)<br>
>>>> Jean-Jacques Subrenat (ALAC)<br>
>>>> Jari Arkko (IETF)<br>
>>>> Martin Boyle (ccNSO)<br>
>>>> Demi Getschko (ISOC)<br>
>>>> Jandyr Ferreira dos Santos (GAC)<br>
>>>> Keith Drazek (gTLD Registries)<br>
>>>> Jon Nevett (gTLD Registries)<br>
>>>> Lynn St. Amour (IAB)<br>
>>>> Michael Niebel (GAC)<br>
>>>> Narelle Clark (ISOC)<br>
>>>> Russ Housley (IAB)<br>
>>>> Russ Mundy (SSAC)<br>
>>>> Wolf-Ulrich Knoben (GNSO)<br>
>>>> Xiaodong Lee (ccNSO)<br>
>>>> Alan Barrett (NRO)<br>
>>>> Lars-Johan Liman (RSSAC)<br>
>>>> Joseph Alhadeff (ICC/BASIS)<br>
>>>> Mary Uduma (ccNSO)<br>
>>>><br>
>>>> Liaisons<br>
>>>> Elise Gerich (IANA Staff Liaison)<br>
>>>><br>
>>>> Apologies<br>
>>>> Kuo Wei Wu (ICANN Board Liaison)<br>
>>>> James Bladel (GNSO)<br>
>>>> Milton Mueller (GNSO)<br>
>>>> Hartmut Glaser (ASO)<br>
>>>> Manal Ismail (GAC)<br>
>>>> Mohamed El Bashir (ALAC)<br>
>>>> Patrik F�ltstr�m (SSAC)<br>
>>>> Thomas Schneider (GAC)<br>
>>>><br>
>>>> Best Regards,<br>
>>>><br>
>>>> Jennifer<br>
>>>> _______________________________________________<br>
>>>> Internal-cg mailing list<br>
>>>> <a href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a><br>
>>>> <a href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Internal-cg mailing list<br>
>>> <a href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a><br>
>>> <a href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> Internal-cg mailing list<br>
>> <a href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a><br>
>> <a href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a><br>
><br>
><br>
> _______________________________________________<br>
> Internal-cg mailing list<br>
> <a href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a><br>
> <a href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a><br>
<br>
_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@mm.ianacg.org">Internal-cg@mm.ianacg.org</a><br>
<a href="http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://mm.ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a><br>
</div></div></blockquote></div><br></div>