[DTL] How far do we delve into C.7

[James Gannon]

My own personal feeling on this would be that we focus on C.7.3 while taking into account that our work may be informed by and/or lend depth to other areas of the contract.

I don't want to overburden us before we have got off the ground, if we focus on getting the transition plan done and delivered then by all means we may feel that we should go back to the CWG and ask that we examine the CCOP as another Design Team given that we have looked at it as part of our transition planning.

I'm open to other ways of thinking however. But I think our primary goal must be delivering the transition plan first before we do anything else.

-----Original Message-----
From: dt4-bounces at icann.org [mailto:dt4-bounces at icann.org] On Behalf Of Matthew Shears
Sent: Friday, March 20, 2015 11:59 AM
To: dt4 at icann.org
Subject: [DTL] How far do we delve into C.7

All,

If we look at C.7 more broadly and not just the transition plan in C.7.3, we start to have to look at operator requirements and relationships with other interested and affected parties.

For example, C.7.1 spells out some requirements of the contractor: as a part of the COP multiple geographically dispersed redundent sites (preferably 3) in the US and resilient communications paths with interested and affected parties (includes IETF, RIRs, TLD operators, etc. enumerated in C.1.3).  And in C.7.2 we start to get into contingency planning.

When I think about a transition plan I don't necessarily think only of a transition plan to another operator following a re-awarding of the contract or other planned and anticipated transition.  I also think that much of what we are discussing in terms of transition planning would also apply in the situation of attacks, emergencies, etc.  I guess we have to discuss an clarify the scope of our work in terms of C.7 generally.  I am not sure where else COP or CCOP would sit in the CWG's work  - its seems that those would also logically fall to us.  (And James has put in the DIDPs).

Thanks.

Matthew


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