<div dir="ltr"><div><font color="#000000" face="Times New Roman" size="3">

</font><p style="background:white;margin:0cm 0cm 0pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-size:14pt">Dear Jari,,Dear Paul</span></p><font color="#000000" face="Times New Roman" size="3">

</font><p style="background:white;margin:0cm 0cm 0pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-size:14pt">Dear All</span></p><font color="#000000" face="Times New Roman" size="3">

</font><p style="background:white;margin:0cm 0cm 0pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-size:14pt">Thank you Jari for the message and hyperlink providing additional
information in regard  on how the  accountability  has been dealt
till now.</span></p><font color="#000000" face="Times New Roman" size="3">

</font><p style="background:white;margin:0cm 0cm 0pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-size:14pt">However, in order to be quite clear, there seems to be appropriate that anything
relating to accountability is addressed by CCWG a competent group established
for this purpose.</span></p><font color="#000000" face="Times New Roman" size="3">

</font><p style="background:white;margin:0cm 0cm 0pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-size:14pt">Similar Course of action could be equally applied to numbers </span></p><font color="#000000" face="Times New Roman" size="3">

</font><p style="background:white;margin:0cm 0cm 6.75pt;line-height:normal;vertical-align:middle"><span lang="EN-US" style="color:rgb(34,34,34);font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;font-size:14pt">It may there
be good to liaise with them on this regard and seek whether there would be any
additional actions or measures to be taken</span></p><font color="#000000" face="Times New Roman" size="3">

</font><p style="margin:0cm 0cm 10pt"><span lang="EN-US" style="line-height:115%;font-size:14pt"><font color="#000000" face="Calibri"> </font></span></p><font color="#000000" face="Times New Roman" size="3">

</font></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-22 8:57 GMT+01:00 Jari Arkko <span dir="ltr">&lt;<a href="mailto:jari.arkko@piuha.net" target="_blank">jari.arkko@piuha.net</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">First, I agree with the proposed way forward, and that we<br>
should focus on parts B and C now. (With obvious further<br>
work down the line for us when the names proposal is<br>
ready.)<br>
<br>
And I very much agree with this point of view from Joe:<br>
<span><br>
&gt;&gt; Agree with the path forward, and would also suggest that we keep the<br>
&gt;&gt; Names community apprised of our progress on related work as things they<br>
&gt;&gt; may wish to consider in the development of their proposal.<br>
<br>
</span>Finally, back to substance - part B deals with accountability. With<br>
the help of our IANA program at IAB, Russ and I recently<br>
wrote an informational piece that talks about how we view<br>
accountability and stability for protocol parameters. There’s<br>
nothing new here if you’ve read the relevant RFCs, the<br>
proposal, and other documents, but it may be a helpful<br>
explanation of the big picture:<br>
<br>
<a href="http://www.ietf.org/blog/2015/02/ensuring-continuity-of-the-iana-registries/" target="_blank">http://www.ietf.org/blog/2015/02/ensuring-continuity-of-the-iana-registries/</a><br>
<br>
As for the relationship of protocol and number proposals<br>
wrt accountability, I think the arrangements are very similar<br>
and at this point I cannot see any conflicts or missed areas.<br>
Looking forward to input from others.<br>
<br>
For part C, I think the answers from IETF perspective<br>
are rather obvious, as we are continuing existing<br>
practices and the adjustments are relatively minor.<br>
But again, I think we’ve already talked about<br>
the main differences between the protocol<br>
and number proposals, and it seems easy<br>
to find a path forward where they can work<br>
together.<br>
<br>
Cheers,<br>
<br>
Jari<br>
<br>
<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>