<div dir="ltr">It seems fairly clear that changes <u>necessitated</u> by the transition (because the NTIA is gone) will need to be made. It would be good to be clear on what those are. David, do you have some examples? Do we need to check in with the IANA staff to clarify what pieces will be missing that must lead to internal changes at IANA?<div><br></div><div>Making necessary changes should not be too controversial, although <u>what</u> the change might be could be controversial. But first we need to identify those points where change is inevitable.</div><div><br></div><div>I agree with Chris that the Design Team should concentrate on determining what needs to change within IANA as a result of this transition, not what could be changed, so long as we are doing this transition thing.</div><div><br></div><div>Additional changes that are good for everybody should be fairly non-controversial as well, except for workload considerations (which lead to time considerations). Given our time sensitivity, those considerations cannot be easily dismissed. Some type of "cost/benefit" analysis might be helpful here (with "time" and "effort" being the primary costs -- unless there are dollar costs involved as well, which could be an even bigger issue).</div><div><br></div><div>There may also be additional changes that are viewed positively by the direct customers but not so positively by other stakeholders in the names community. I don't have any examples off the top of my head, but if they do occur, they should be parked until after the transition.</div><div><br></div><div>If there's a feeling that additional changes (beyond those necessitated by the facts of the transition) need to be made now because stakeholders have "leverage," or its the "one bite at the apple," then that is troubling for a bigger reason. That means that some believe we will not achieve a goal of long-term accountability by the managers of the IANA function to the names community in general, and the direct customers specifically. (Alternatively, it means people are pushing stuff through now that would never be acceptable later, and that's even more troubling.) I agree with Andrew that it is much important (and much more in scope) to design a system where evolutionary change in IANA operations can reasonably be expected to occur, and where stakeholder concerns will reasonably be able to drive change, than it is to effect a non-transition-essential change just because the time seems ripe. I am not as inalterably opposed to considering some such changes as Andrew appears to be, but I am highly prejudiced against them because of their ability to slow us down and throw us off course. </div><div><br></div><div>Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Mar 1, 2015 at 6:00 PM, David Conrad <span dir="ltr"><<a href="mailto:david.conrad@icann.org" target="_blank">david.conrad@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alan,<br>
<span class=""><br>
> 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.<br>
<br>
</span>Apologies for being repetitive, but just to be sure, one more time with emphasis:<br>
<br>
Internal changes at IANA _must_ occur with the transition because NTIA is integrated into IANA operations.<br>
<br>
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.<br>
<br>
It may be appropriate to minimize the internal changes required within IANA during the transition, but there already exists a requirement for some change.<br>
<br>
Regards,<br>
-drc<br>
<br>
<br>_______________________________________________<br>
CWG-Stewardship mailing list<br>
<a href="mailto:CWG-Stewardship@icann.org">CWG-Stewardship@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/cwg-stewardship" target="_blank">https://mm.icann.org/mailman/listinfo/cwg-stewardship</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365d">Gregory S. Shatan </span></b><b><span style="font-size:8.0pt;font-family:Symbol;color:#17365d">ï</span></b><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#17365d"> </span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#c0504d">Abelman
Frayne & Schwab</span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#365f91">Partner</span></b><span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#4f81bd"> </span></b></span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#4f81bd">| IP |
Technology | Media | Internet</span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#17365d">666 Third Avenue | New York, NY 10017-5621</span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Direct</span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> <span> </span></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-885-9253<span> </span><b>|<span> </span></b></span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Main</span></b><span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> </span></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-949-9022</span><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Fax</span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"> <span> </span></span><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">212-949-9190<span> </span><b>|</b><span> </span></span><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">Cell<span> </span></span></b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#1155cc">917-816-6428</span><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><i><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a href="mailto:gsshatan@lawabel.com" target="_blank">gsshatan@lawabel.com</a></span></i></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy">ICANN-related:<span> </span><i><a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a></i></span></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p>
<p style="margin:0in 0in 0.0001pt;line-height:12pt;background-image:initial;background-repeat:initial"><b><i><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:navy"><a href="http://www.lawabel.com/" target="_blank">www.lawabel.com</a></span></i></b><span style="font-size:9.5pt;font-family:Arial,sans-serif"></span></p></div></div>
</div>