Each OC has its own procedures for ensuring continuity and stability in their proposals.

E.g., the IETF requires ICANN to commit to those parts of the legacy IANA contract that require cooperation with the new operator and continuity; the RIR proposal has similar arrangements.

The biggest transition compatibility problem that the different OCs and ICG identified was the trademarks and domains. If these are moved to an independent (non-IFO) trust, that problem should be resolved.

What we want to avoid is any statement or implication that any one OC has to get the approval of the other OCs to change their IANA functions operator. That won’t fly politically, as we have learned several times.



--MM



From: Matthew Shears [mailto:[log in to unmask]]

Sent: Friday, September 4, 2015 5:02 AM

To: Mueller, Milton L; [log in to unmask]

Subject: Re: [NCSG-Discuss] [Consultation] Important NCSG draft comment on ICG IANA stewardship proposal



Hi Milton,  thanks for the comments, etc.



I don't have any misconception on this matter.  I am just raising a concern I see when it comes to moving to another IFO and how such a change would occur and whether there is a need to coordinate such a change to mitigate any issues related to continuity and stability - that's all.  If we believe that this is not the case nor necessary then fine we can delete.



Others should review/edit the comments and see if they can be supported as an NCSG input - we don't much time - THANKS!



Matthew

On 9/3/2015 9:14 PM, Mueller, Milton L wrote:



I went over it. Made some additions, fleshed out a few things.



But we do have a serious disagreement. Whoever wrote the initial draft is laboring under the misconception that any change in IANA function operators must be coordinated across all three operational communities. This is just not true. The plan (and at least 2 of the 3 OCs involved) assumes that each OC has the ability to select a new IANA functions operator independently for its own part of the functions. None of the numbers and protocols people have expressed any concern about the compatibility implications of doing that. It seems to be only names people who are worried about that.







I would object to all of that language but before deleting it wanted to flag this issue on the list for discussion.







-----Original Message-----



From: NCSG-Discuss [mailto:[log in to unmask]] On Behalf



Of Matthew Shears



Sent: Thursday, September 3, 2015 10:11 AM



To: [log in to unmask]<mailto:[log in to unmask]>



Subject: Re: [NCSG-Discuss] [Consultation] Important NCSG draft comment



on ICG IANA stewardship proposal







Thanks Rafik - this is very "drafty" so please consider it a strawman.







Matthew







On 9/3/2015 2:47 PM, Rafik Dammak wrote:



Hi everyone,







Thanks to Matt, we got a NCSG draft comment for the ICG proposal and



we should submit this asap (the deadline for submission is 8th Sept).



the document is here



https://docs.google.com/document/d/14wO_tu-



liqEqzlMSm_NnGD4_BME7f7Fhg_



Z7d1lwYBc/edit please review it and share your comments. the document



is in suggestion mode to make the review and input more easier.







For reminder, Milton is our representative in the ICG.







Best Regards,







Rafik







--



Matthew Shears



Global Internet Policy and Human Rights



Center for Democracy & Technology (CDT)



+ 44 (0)771 247 2987







--



Matthew Shears



Global Internet Policy and Human Rights



Center for Democracy & Technology (CDT)



+ 44 (0)771 247 2987