[DTL] Lets get started!

James Gannon james at cyberinvasion.net
Sun Mar 22 22:43:35 UTC 2015


Hi Christopher,

Thanks for the work on the document I appreciate the input, however much of it is not related to the work on this DT, as we are not questioning the rationale for separating the IANA nor are we discussing the merits of it.
Our DT is limited in scope by design to look at what needs to be done if the IANA did need to move nothing more, any discussions outside of that scope need to be taken to the main mailing list or as comments or redlines on the main CWG proposal draft.

As stated before this DT is not the forum for concerns related to the direction or overall composition of the work of the CWG, I ask that we keep within our (Very limited) mandate for this DT, and fully encourage you to take any overall concerns to the CWG as a whole.

From: CW Lists [mailto:lists at christopherwilkinson.eu]
Sent: Sunday, March 22, 2015 10:39 PM
To: James Gannon
Cc: dt4 at icann.org
Subject: Re: [DTL] Lets get started!

My drafting proposals have been posted to the Google Docs page.

May I also note that in the last day or two a significant group of gTLD and ccTLD Registries have expressed reservations as to the direction of the CWG proposals to date.

It would not be a good idea for the members of this DT4 to be put in the ridiculous position of analysing 'pro forma' propositions that are fundamentally flawed.

CW




Regards

CW


On 20 Mar 2015, at 18:48, James Gannon <james at cyberinvasion.net<mailto:james at cyberinvasion.net>> wrote:


Hey Matt,
Yes great idea I have put it up on Google Docs now: (Again if I have missed anyone permissions wise please let me know)
https://docs.google.com/document/d/1QRiXP9-nxM-h8FgJ_FyM962EwdjnRESrDT2jOtlRZZ0/edit?usp=sharing

The idea with the template is get the overview of what the transition plan encompasses into the draft proposal text, so we should aim to outline the current situation and give a broad overview of the content that we are drafting that will eventually stand as an appendix to the proposal as a whole.

Just to note I won't be in Istanbul next week, so any work everyone can get done over the course of the meeting would be great, I'll try and participate remotely whenever I can.

From: dt4-bounces at icann.org<mailto:dt4-bounces at icann.org> [mailto:dt4-bounces at icann.org<mailto:bounces at icann.org>] On Behalf Of Matthew Shears
Sent: Friday, March 20, 2015 11:41 AM
To: dt4 at icann.org<mailto:dt4 at icann.org>
Subject: Re: [DTL] Lets get started!

James - thanks for this.

I agree that we should use the template and insert the current transition plan (C.7.3) and in the proposed language area do the following for each item in the exiting plan: 1) assessment as to viability/adequacy, and 2) proposed enhancements.   That way for the Monday deadline we can show our assessment and where our thinking is going.  Do we create a new Google Doc for the template or add it into the one we have now?

Matthew
On 3/19/2015 3:05 PM, James Gannon wrote:
Hi All,
I have made some further additions to the document, I have copied across the text of the existing planning document so that we can reference and critique it on the document, I have also added Gurus critique which I believe is a good start for us on Phase 1 of the work namely as assessment of the existing documentation.

I have also started adding some generic check summing and sampling criteria for any data transfer, as these are my own perspective I have added them as suggestions before putting them into the document as text, please feel free to critique any additions.

There are 2 items that I would like to get some input from the team on:

*         What should we aim to have ready for Istanbul?
o   Staff have provided a template for what the changes to the text of the draft proposal should be I have a copy below: (Apologies to anyone who is working in plain text emails the word doc is listed on the CWG list)

[Section Reference] - [Title]

Background / Current State

[describe the current state and any relevant background information]

Issues Identified & Rationale for Changes, if any

[Identify the issues, if any, that are the result of the IANA Stewardship Transition, and provide your rationale for any changes that need to be made as a result of the issues identified]

[Reference the current language of the IANA Functions Contract, if applicable]

Proposed Language

[Provide the current language of the IANA Functions Contract, if applicable]

[Provide your recommended language and/or changes to existing language for inclusion in the Statement of Work]


o   I think that we should have some draft text ready for this by Monday if we can, referring out to the overall technical transition plan which we will be producing.
o   I would welcome some draft language to this end if anyone is able to work on that. Currently the Chairs are asking for draft language to be submitted by 18:00UTC Monday.

*         In order to have an idea of what form some of the systems that we are coming up with a plan for I would like to suggest we ask ICANN to provide a generalized non-confidential architecture of IANAs systems to us eg:
o   Historical Requests are currently contained in a MySQL database, Secure Notification System currently runs on a Sendmail based server.
o   Even with this level of detail we can then start looking at broad data migration and verification planning.

Unfortunately as I am only a participant (And don't work somewhere that will spring for flights!) I won't be able to attend Istanbul in person but I have attempted to block out most of the two days on my calendar to attend remotely wherever I can.

I hope that we can keep up a pace of work get some good text into the draft for Istanbul and hopefully keep working on the overall plan to the best of our abilities.

Thanks in advance,
James

From: James Gannon
Sent: Tuesday, March 17, 2015 11:50 PM
To: James Gannon; dt4 at icann.org<mailto:dt4 at icann.org>
Subject: RE: Lets get started!

And I forgot to mention can we make any changes to the document using the suggestions feature of Google Docs (Change from Editing to Suggesting in top right hand corner) so that we may review the changes/additions as a group before incorporating them.

From: dt4-bounces at icann.org<mailto:dt4-bounces at icann.org> [mailto:dt4-bounces at icann.org] On Behalf Of James Gannon
Sent: Tuesday, March 17, 2015 11:03 PM
To: dt4 at icann.org<mailto:dt4 at icann.org>
Subject: [DTL] Lets get started!

Hi All,
Apologies for not being able to make the call today, thank you to Matt for stepping in on my behalf.

Now that we have been 'presented' to the CWG on today's call, I think that it's time we begin drafting anywhere we can, even if its based on the little information that we have available to us at this point.

To this end I've drawn up a very broad document for us to begin working with, please bear in mind that this is merely intended to give us a platform to begin our drafting work on and is purely my own personal basis to begin work with. I fully expect the document may look very different by the time we are finished with our work.

https://docs.google.com/document/d/10efc2wpt-XkYRU_I2twnSuOPZsN4x6gXD8d5JxnibuQ/edit?usp=sharing

I believe I have added all members of the DT with edit permissions, please let me know if I sent the edit invite to the incorrect address or if you did not receive it (First time working with Google Docs)

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

_______________________________________________
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/20150322/8d8f8b06/attachment-0001.html>


More information about the dt4 mailing list