One even greater source of clarity would be the NTIA. I asked the same question of Larry Strickling personally this week and rather than claim to be a perfect relay agent, I think we should invite him to meet with the ICG. I would hope his diary would have the capacity to accommodate such a meeting. In case you were wondering, he reassured me that he was expecting an identical document to come from ICANN as went to ICANN from the ICG. Like I said, however, I expect we would prefer he said that to us himself. Best regards Narelle
-----Original Message----- From: internal-cg-bounces@icann.org [mailto:internal-cg-bounces@icann.org] On Behalf Of Alissa Cooper Sent: Friday, 17 October 2014 2:02 AM To: Subrenat, Jean-Jacques Cc: internal-cg@icann.org Subject: Re: [Internal-cg] Minor issue with timeline language
In addition to the various statements that have been made about this issue this week, I've also reached out to a few ICANN board and staff folks about the possibility of us issuing a joint statement outlining the proposal transmission steps. So that is an option for us as well if we want to go down that path.
Alissa
On Oct 12, 2014, at 2:17 PM, Subrenat, Jean-Jacques <jjs@dyalog.net> wrote:
Hartmut, good catch! Yes, I should have written ICG instead of IGC. Jean-Jacques.
----- Mail original ----- De: "Hartmut Richard Glaser" <glaser@cgi.br> À: "Jean-Jacques Subrenat" <jjs@dyalog.net>, "Russ Mundy" <mundy@tislabs.com> Cc: internal-cg@icann.org Envoyé: Dimanche 12 Octobre 2014 14:11:14 Objet: Re: [Internal-cg] Minor issue with timeline language
IGC = ICG ???
====================================
On 12/10/14 16:46, Subrenat, Jean-Jacques wrote:
This (Sunday) morning the ALAC received the visit of the CEO/President of ICANN. Fadi started his presentation by underlining the importance of the transition plan, before any other topic. During Q&A, and speaking as a representative of the ALAC, I mentioned that the IGC would be sending its transition plan formally through ICANN, and highlighted the fact that ICANN (Board and/or Staff) should abstain from any modification of the plan itself. I asked him to bring this to the attention of his colleagues on the ICANN Board: he said he would do that.
Jean-Jacques.
----- Mail original ----- De: "Russ Mundy" <mundy@tislabs.com> À: "Jean-Jacques Subrenat" <jjs@dyalog.net> Cc: "Russ Mundy" <mundy@tislabs.com> , "WUKnoben" <wolf-ulrich.knoben@t-online.de> , internal-cg@icann.org Envoyé: Dimanche 12 Octobre 2014 12:36:15 Objet: Re: [Internal-cg] Minor issue with timeline language
In the 14 March announcement, NTIA tasked ICANN with "to convene global stakeholders to develop a proposal to transition the current role played by NTIA" and the IANA Functions contract is between NTIA & ICANN so it is entirely reasonable for NTIA to want the response to their announcement to come from ICANN. I support the solution suggested by Daniel for the ICG to simultaneously deliver the final proposal to both NTIA and ICANN.
I would also like to suggest that we consider some technical means of "signing" the final proposal using something like a gpg/pgp signature and publishing the public key on the ICG web site - in that way, anyone on the Internet can tell if any changes have been made to the ICG proposal.
I would not object to the exact wording suggested by JJ but I do think that the last sentence is unnecessary - I think that it would be much better to use a technical means to get assurance that ICANN would not make any changes to the report.
Russ
On Oct 11, 2014, at 1:38 AM, "Subrenat, Jean-Jacques" <jjs@dyalog.net> wrote:
As stated in a previous email, I suggest once again that we add that the content will not be modified by ICANN or any other entity. Also, the addition proposed by Daniel (ICG sending the plan to NTIA both directly and through ICANN) should be retained.
Thus, "Following on NTIA's request, and consistent with procurement rules within ICANN, the ICG shall submit its Transition Plan to the NTIA directly, as well as formally through ICANN. The content of the plan shall in no way be altered, redacted or modified by ICANN as the designated channel of transmission."
Thanks, Jean-Jacques.
----- Mail original ----- De: "WUKnoben" <wolf-ulrich.knoben@t-online.de> À: "Kavouss Arasteh" <kavouss.arasteh@gmail.com> , "Daniel Karrenberg" <daniel.karrenberg@ripe.net> Cc: internal-cg@icann.org Envoyé: Samedi 11 Octobre 2014 09:18:59 Objet: Re: [Internal-cg] Minor issue with timeline language
I agree here.
Perhaps a reference in our submission/transmission whatsoever to NTIA’s request maybe helpful:
“Following the NTIA request in consistence with procurement rules as well as practical matter, the ICG submits - formally through ICANN - the transition proposal to NTIA.”
Best regards
Wolf-Ulrich
From: Kavouss Arasteh Sent: Friday, October 10, 2014 6:09 PM To: Daniel Karrenberg Cc: internal-cg@icann.org Subject: Re: [Internal-cg] Minor issue with timeline language
Dear All, For me does not matter whether ICG transmit to NTIA,or ICANN transmit , without any edit ,whatsoever, to NTIA,.or ICG transmit to NTIA with a copy to ICANN,or ICG transmit to NTIA and ICANN simultaneously ( not coped to ICANN but transmittal to ICANN) The important issue is ICANN should not touch, edit, comment on the final Report Kavouss
2014-10-10 14:57 GMT+02:00 Daniel Karrenberg < daniel.karrenberg@ripe.net :
publish & transmit to ntia & transmit to icann. these days one cannot any longer distinguish between orignial and copy. ;-)
---------- Sent from a hand held device.
On 10.10.2014, at 13:13, joseph alhadeff < joseph.alhadeff@oracle.com > wrote:
It would seem that if we publish the proposal just after transmission to ICANN and copy NTIA on that missive that we have insured that no one can misunderstand what we proposed.
On 10/10/2014 6:44 AM, Daniel Karrenberg wrote: Jean-Jacques,
Je suggère que nous allons faire notre travail, sans préjudice de ce que autres vont faire avec le résultat. Nous le faisons d'une manière transparente et à ce que tout le monde peut prendre acte du résultat. Une fois que nous avons fait notre travail nous avons terminé et il sera pour les autres à faire leur choix. Il serait vain pour nous de prévoir des règles sur la façon dont ce qui se passera lorsque nous aurons terminé.
Amicalement
Daniel
---------
rough translation:
I suggest we do our job without prejudice about what others will do with it. We do it in a transparent manner and such that everyone can take note of the result. Once we have done our job we are finished and it will be for others to make their choices. It would be futile and therfore unwise for us to stipulate rules on how what will happen after we are finished.
Read: ICANN will be judged by and suffer the consequences of what they do with the final proposal.
Read also: we will be judged by our (futile) debates and actions,
Daniel
---------- Sent from a hand held device.
_______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg _______________________________________________ Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg
Internal-cg mailing list Internal-cg@icann.org https://mm.icann.org/mailman/listinfo/internal-cg