<div dir="ltr">I'm completely in favor of eliminating issues from our list. However, our list is not the only one that matters. In the end, it's the NTIA's list that matters, I'm not sure how to resolve points where our issues differ, but I'm fairly confident that the NTIA is not going to take something off of their list simply because we took it off of ours.<div><br></div><div>On this point in particular, I'm curious how you came to the conclusion that IANA is responsible for <span style="font-size:12.8000001907349px">the technical operations only.and that</span><span style="font-size:12.8000001907349px"> all the policy formation is reserved to the USG,based on your reading of</span><span style="font-size:12.8000001907349px"> C.2.9.4.</span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div>I don't see anything in C.2.9.4 that reserves policy to the USG. It does say that IANA <span style="font-size:12.8000001907349px">shall operate the INT TLD "within the current </span><span style="font-size:12.8000001907349px">registration policies for the TLD".-- but it doesn't say where those policies are set. It certainly doesn't reserve to itself the right to change those policies. In any event, when the IANA Functions Contract goes away, so does C.2.9.4, and any USG limitation on .INT policies goes away with it. This would be a </span></div><div><span style="font-size:12.8000001907349px"><br></span></div><div><span style="font-size:12.8000001907349px">The IANA website does deal with .INT policy in a section called ".INT Policy and Procedures." <a href="http://www.iana.org/domains/int/policy">http://www.iana.org/domains/int/policy</a> This in turn cites to RFC 1591, which merely states </span><span style="color:rgb(0,0,0);white-space:pre-wrap">that "[T]his domain is for organizations established by international </span><span style="color:rgb(0,0,0);white-space:pre-wrap">treaties, or international databases." I don't see any indication here, either, that the USG sets policy on .INT</span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap"><br></span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap">SAC 067 is consistent with this, and states the following: </span></div><div>6.1.1 US Government Involvement in .INT TLD Management
The NTIA has no role in the day-to-day operation of the .INT domain. As .INT
management is considered to be an IANA Function, questions relating to the U.S.
government involvement in setting management policy—e.g., criteria for obtaining a
.INT domain—remain open.</div><div><br></div><div>Based on the foregoing, it seems to me that when the IANA Functions Contract goes away, .INT is IANA's to do with what they will, subject only to the parameters of RFC 1591. If we are okay with that, fine. If we think it should be constrained as it was under the IANA Function Contract, that's fine too. But, I don't think we can merely eliminate the issue from the list.</div><div><br></div><div>Greg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 26, 2015 at 7:04 PM, Andrew Sullivan <span dir="ltr"><<a href="mailto:ajs@anvilwalrusden.com" target="_blank">ajs@anvilwalrusden.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Replying to several messages at once to reduce list traffic.<br>
<br>
On Thu, Feb 26, 2015 at 03:29:21PM +0000, Milton L Mueller wrote:<br>
> Hi, Andrew<br>
> Fiona Alexander of NTIA has made a frequent point of telling us that .int is currently in the IANA contract (C.2.9.4) and a complete proposal will have to decide what to do with it.<br>
><br>
<br>
As I was arguing upthread, it _is_ in the contract, but in a strictly<br>
limited way: the technical operations only. That's what's in C.2.9.4.<br>
In that section, all the policy formation is reserved to the USG:<br>
<br>
The Contractor shall operate the INT TLD within the current<br>
registration policies for the TLD. Upon designation of a successor<br>
registry by the Government, if any, the Contractor shall cooperate<br>
with NTIA to facilitate the smooth transition of operation of the<br>
INT TLD. Such cooperation shall, at a minimum, include timely<br>
transfer to the successor registry of the then-current top-level<br>
domain registration data. The Contractor shall also implement<br>
modifications in performance of the IANA functions as needed upon<br>
mutual agreement of the parties.<br>
<br>
It seems to me that this WG therefore can nicely side-step this issue<br>
by noting that IANA is currently the technical operator but not the<br>
policy authority. So as part of the transition, we can state that the<br>
pre-existing rules remain in effect (no policy changes, and if the USG<br>
designates a new registry then ICANN will cheerfully help). Moreover,<br>
if NTIA believes that the policy authority is also part of this<br>
transfer, then ICANN will follow the same policy while consulting with<br>
existing int registrants to ask them for a new policy authority. No<br>
alterations in int registration policy will be undertaken without the<br>
(what? Rough consensus? Majority preference? I don't care) of all<br>
int registrants.<br>
<br>
That dodges the problem of getting a complete solution to all the<br>
policy issues for int while respecting the NTIA statements and<br>
direction. Moreover, it kicks this problem down the road a bit and<br>
thereby allows us not to have to hammer out all the details right now.<br>
It is consistent with what everyone wants -- ongoing security and<br>
stability -- while yet leaving NTIA an option as to which way we are<br>
to understand the existing agreement. Moreover, it's consistent with<br>
the multistakeholder approach, and we can even enumerate all the<br>
existing affected stakeholders since the zone is so small. (Even if<br>
we extended the affected class to all the potential registrants, the<br>
list is still entirely manageable in size. So there is one<br>
potentially fraught question, and that is whether to use the bigger or<br>
smaller class here.)<br>
<br>
On Thu, Feb 26, 2015 at 06:27:51PM +0100, Olivier MJ Crepin-Leblond wrote:<br>
> Hello all,<br>
><br>
> actually the Management of .INT is a high stakes political game.<br>
><br>
> The ITU has affirmed for many years that they wish to be managing .INT<br>
<br>
I suggest that the above approach neatly avoids us having to debate<br>
whether management of int can pass to ITU without violating any of the<br>
NTIA's directives on this issue. If the ITU can convince all the<br>
relevant stakeholders (however defined -- see above), then they can<br>
run it. If not, then not. And maybe they don't want it any more.<br>
<br>
<br>
On Thu, Feb 26, 2015 at 03:11:43PM +0100, Jaap Akkerhuis wrote:<br>
<br>
> Strickling has repeatedly said that some solution should be presented<br>
> for the .INT situation. What the exact problem needs to be solved is,<br>
> I don't know but I suspect it has to do with the fact that IANA is now<br>
> the registry and the underlining policy doesn't has a real home nor<br>
> versight.<br>
<br>
I agree, and I'm suggesting that the ambiguity is something we should<br>
take advantage of in order to reduce the "must do" items before the<br>
transition.<br>
<br>
Please note that I'm not suggesting this isn't important or something<br>
that ought to be left forever or anything like that. I'm just saying<br>
that, given all the things that we have to achieve in roughly four<br>
months, we had better figure out how to eliminate issues from our list<br>
whenever it is practical and safe to do so. This is, I submit, such a<br>
case; so let's take advantage of that.<br>
<br>
Best regards,<br>
<br>
A<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@anvilwalrusden.com">ajs@anvilwalrusden.com</a><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>
</font></span></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>