<div dir="ltr">Patrik + 1<div>demi</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 18, 2014 at 7:14 AM, Patrik Fältström <span dir="ltr"><<a href="mailto:paf@frobbit.se" target="_blank">paf@frobbit.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On 18 jul 2014, at 05:29, Daniel Karrenberg <<a href="mailto:daniel.karrenberg@ripe.net">daniel.karrenberg@ripe.net</a>> wrote:<br>
<br>
> My input:<br>
><br>
> "The IANA parameters fall into three categories"<br>
</div><div class="">> --><br>
> "The IANA functions are divided into three main categories"<br>
><br>
> Rationale: As I mentioned in the meeting we should not appear to be<br>
> limiting. For instance the IANA does provide service maintaining DNS<br>
> "glue" information for individual root name server operators. This is<br>
> related to domain names but not the same.<br>
<br>
</div>This is very important as IANA (as Daniel says) is doing more things than what can easily be divided in these three categories. They are also entangled with each other. This is also reflected in the contract between ICANN and NTIA.<br>
<br>
Yes, SSAC is very close to be ready with a document describing the functions. When that is ready, it will help us.<br>
<span class="HOEnZb"><font color="#888888"><br>
Patrik<br>
<br>
</font></span><br>_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@icann.org">Internal-cg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/internal-cg" target="_blank">https://mm.icann.org/mailman/listinfo/internal-cg</a><br>
<br></blockquote></div><br></div>