[DTL] Design Team L - Template for Co-Chairs

[James Gannon]

Christopher,

>From the point of the work of this DT we are merely expanding on the existing requirement of the IANA Functions Contract to provide for a separation mechanism.
As this is already a function of the existing contract I don't believe that exploring additional detail on an already defined requirement of the IANA functions operator we can have any destabilizing influence.

I would in fact suggest that having a solid technical plan to execute a separation if required would be a stabilizing influence on the IANA as it means there would be no last minute planning in the case of a separation being required under any circumstance. The old adage of 'Fail to plan and you're planning to fail" comes to mind.

There is certainly a discussion to be had with the greater CWG on the topic of seperability in the various proposals, but we will be keeping the scope of this DT purely to operationalizing an existing requirement already laid down by NTIA.


From: CW Lists [mailto:lists at christopherwilkinson.eu]
Sent: Monday, March 16, 2015 7:02 PM
To: James Gannon
Cc: dt4 at icann.org
Subject: Re: [DTL] Design Team L - Template for Co-Chairs

Dear James:

Allow me to simply suggest that discussion of separation is in and of itself destabilising.
Should that ever transpire, it would doubtless be conducted under conditions of serious controversy, among stakeholders and internationally,
which would inevitably prejudice the conditions of security and stability upon which the whole transition exercise is predicated.

I am increasingly coming to the view that either some of the more extreme proposals that are being currently adumbrated will be totally ignored, which will unnecessarily weaken the position of the names community in the ICG negotiation, or the CWG will become responsible for destabilising iANA in the sense that the transition finally may not take place or a resolution will materialise outside the multi-stakeholder context.

Regards

CW


On 16 Mar 2015, at 11:29, James Gannon <james at cyberinvasion.net<mailto:james at cyberinvasion.net>> wrote:


Hi Everyone,

If possible I'd like to finalize the template by 23:59 UTC today 16-March, I've added one final section based on the transition areas identified in C.7.3 I think the document has enough detail to go to the co-chairs so I propose final comments by 23:59 UTC.

Christopher with regards to your current comments I feel that while valid that their DT Is going to be looking at the technical aspect of the transition if needed, if an internal to ICANN solution is identified then the work of this DT may not be used in the final proposal however it is still valuable exploratory work both for the CWG and may be valuable to ICANN Disaster Recovery and Stability planning.

I would like some feedback on two items:

*         Is everyone is happy with me leading the DT, I'm relatively new to ICANN but in a way that possible gives me some neutrality on the issues but I want to point out that Guru and Matthew were the ones initially calling for the DT creation so I'm happy to yield to others.
*         DO we feel that the DT has sufficient membership to examine all the areas in question, if not can we identify areas that we would like to target participation from, who would be valuable to this exercise?

Thanks everyone and I hope that we can get started on analyzing and critiquing our source documents in the very near future, and then get working on the other phases ASAP.

James Gannon
Director
Cyber Invasion Ltd
Dun Laoghaire, County Dublin, Ireland
Office: +353 (1)663-8787
Cell: +353 (86)175-3581
Email:james at cyberinvasion.net<mailto:james at cyberinvasion.net?subject=Via:%20Email%20Signature>
GPG: https://keybase.io/jayg

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/dt4/attachments/20150316/1a70d91c/attachment-0001.html>