[CWG-Stewardship] Service Level Expectations Design Team Template

Chris Disspain ceo at auda.org.au
Sun Mar 1 23:45:32 UTC 2015


Hi David,

> Internal changes at IANA _must_ occur with the transition because NTIA is integrated into IANA operations.

I agree and it is that area that I believe the design team should concentrate on in consultation with IANA staff rather than undertaking a full blown study, review and re-vamp of current service levels etc.

How would you recommend that those changes that must occur are dealt with?


Cheers,

Chris

On 2 Mar 2015, at 10:00 , David Conrad <david.conrad at icann.org> wrote:

> Alan,
> 
>> I do have a problem with requirement which would force internal changes within IANA at the same time as the transition is going on. That violates the rule of making as few changes as possible in parallel.
> 
> Apologies for being repetitive, but just to be sure, one more time with emphasis:
> 
> Internal changes at IANA _must_ occur with the transition because NTIA is integrated into IANA operations.
> 
> The process and possibly the code by which root zone updates are made _must_ change.  This _may_ impact the SLEs as specified in C.4.2 of the current IANA Function Contract and hence could impact the outcome of the Design Team.
> 
> It may be appropriate to minimize the internal changes required within IANA during the transition, but there already exists a requirement for some change.
> 
> Regards,
> -drc
> 
> _______________________________________________
> CWG-Stewardship mailing list
> CWG-Stewardship at icann.org
> https://mm.icann.org/mailman/listinfo/cwg-stewardship



More information about the CWG-Stewardship mailing list