<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 16/05/2015 14:09, Milton L Mueller
wrote:<br>
</div>
<blockquote
cite="mid:329d1363906f441ebd3c7009b7526dbd@EX13-MBX-13.ad.syr.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><a moz-do-not-send="true"
name="_MailEndCompose"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in
0in 0in 4.0pt">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:4.8pt">But is changing
it REALLY on our critical path?<br>
<br>
<span style="color:#1F497D">M: Well, yes. Early in this
process I heard NTIA staff complain several times that no
one was proposing what to do with .INT and since .INT is
currently part of the IANA functions contract any
transition plan has to deal with it. I agree that _<i>who</i>_
gets .INT is not a critical part of the transition but we
could easily say as part of our proposal: “.INT should be
redelegated to an appropriate registry operator and the
IFO should not be running a TLD unless it it something
that directly touches on the IANA functions (such as
.arpa).”</span></p>
</div>
</div>
</blockquote>
<br>
.INT is a can of worms. <br>
I really think it would be unwise to open it now, at the 11th hour,
as an afterthought, a few days before the end of the 2nd public
consultation. I am of the view that if it ain't broke, don't attempt
to fix it. I definitely to not see a link between it and the
transition of stewardship itself.<br>
Kind regards,<br>
<br>
Olivier<br>
</body>
</html>