<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Kavouss & Colleagues,<div><br></div><div>This thread seems to have two fundamental issues:</div><div><br></div><div>First, how understandable (or non-understandable) are the accountability aspects of the numbers and protocol parameters proposals;</div><div><br></div><div>Second, there is some requirement for the accountability aspects of the three operational communities to be compared or combined in some way.</div><div><br></div><div>- With respect to the first, I believe that both the numbers and protocol parameters existing proposals are each sufficiently clear and complete in their accountability descriptions. Although it might be useful to have some graphical illustrations of their respective processes, I do not see that it is within the remit of the ICG to require these illustrations. </div><div><br></div><div> -- If ICG members (or others) want additional information about what is currently defined in NTIA-ICANN contract, I would suggest reviewing SAC-068 and, if needed, the Contract itself and the referenced agreements. My personal interpretation of what these say is that the numbers operational community and the protocol parameters operational community each have separate, independent agreements outside of the Contract and, further, those agreements are the dominant authority (not the Contract) for how the IANA functions should be carried out for each respective operational community. In short, if these operational communities are satisfied with the accountability mechanisms for their respective functions, it is not within the ICG remit to question or challenge them since the Contract has already put those communities in charge of their respective portions of the IANA functions. (I�d also like to note that there are no similar such provisions for the names community.)</div><div><br></div><div>With respect to the second issue, I see no need (let alone a requirement) to compare the accountability processes between any of the three OCs. This point is emphasized by the fact the current Contract says accountability between two of these communities is defined by the respective operational communities via agreements that are separate and independent from the Contract. When the ICG receives the names proposal, we (the ICG) will have to make a judgement about the compatibility and interoperability of that proposal with the other two - I do not think that it would not be appropriate or fruitful to try to compare the names accountability processes with either the numbers or protocol parameters proposals since each OC is dealing with separate issues and challenges which will require different approaches to accountability.</div><div><br></div><div>Russ (M)</div><div><br></div><div><br></div><div><div><div><div>On Mar 8, 2015, at 11:52 AM, Kavouss Arasteh <<a href="mailto:kavouss.arasteh@gmail.com">kavouss.arasteh@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>Dear Jopseph,</div><div>May I explain a little bit the objectives of the querry.</div><div>The terms and condition and status of accountabilty currently applied to Protocole and numbers are not clear.</div><div>The presentation of these accountability are too complex and it is not clear who is accountable to whom</div><div>I raised this question to Jari , representing Protocol and he agreed to provide diagram clearly indicating the hierarchy of the implementation and application of the accountavblity as curremntly practiced.</div><div>The same is valid for numbers</div><div>Then in regard with the accountabilty after transition sebveral paragraphs spread over various pages deal with7 addressing the post transition accountabilty.</div><div>For me as an ICG member .it is not clear what are the consequence of transition in regard with accoutabilty before and after transition .</div><div>For thse reasons I asked for a comparative tabulated form indicating the accountabilty at various level and the corresponding hierarchy before and after transition.</div><div>Should you have a better way to have such a tabular form which I referred to it as comparative and you seems not to be happy with such term ,please guide me.</div><div>But currently the suituation is tiotally vague</div><div>Regards</div><div>Kavouss </div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-03-08 16:29 GMT+01:00 joseph alhadeff <span dir="ltr"><<a href="mailto:joseph.alhadeff@oracle.com" target="_blank">joseph.alhadeff@oracle.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Colleagues<br>
<br>
Perhaps we should develop a set of questions for all communities to
answer. I'm not sure that its appropriate to ask communities to
develop comparative documents.<br>
<br>
Best-<br>
<br>
Joe<div><div class="h5"><br>
<div>On 3/8/2015 11:00 AM, Kavouss Arasteh
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Step 2 ,ICG Assessement of Cummunity proposals</div>
<div>Dear Vice chair, </div>
<div>May you please ask TWO OPERATIONAL COMMUNITIES a)
ProtoCOL & Parameters and b) Nummbers to
Kindly provide the followings;</div>
<div>A COMPARATIVE Table indicating the prcess of
accountability currently in force and implemented and those
which will be required after Transitiion.</div>
<div>It would be useful to have that comparative Table
enabling ICG Members to better undersatnd how the
accountability of Protocol Parameter and Numbers are
affected by Transition.</div>
<div>The reports of these two communities are difficult to
make such a comparision.</div>
<div>Without that I will have serious difficulties to comment
on the exacteness and appropriateness of the content of
these two comminities on accountability before and after
transition.</div>
<div>By the way, Jari promised to provide a graphic Diagram
regarding internal accountability being carried out by IETF</div>
<div>mOREOVER, aLAN bARRET / Paul Wilson ,are respectfully
requested to provide similar graphic Diagram about the
accountability currently in force in RIRs ,in particular
that RIRs have a more decentralized process of five regional
communities and the overall accountabilities of the entire
Rir s are not clear</div>
<div>Rergards </div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-03-08 15:06 GMT+01:00 Kavouss
Arasteh <span dir="ltr"><<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div dir="auto">
<div>Dear Patrik</div>
<div>Thank you for reply</div>
<div>The question addressed to two operational communities
represented by Jari and Paul or Alan . If my request was
not properly formulated I hereby correct that in raising
these questions and seeking clarifications from protocol
and numbers operational communities AND NOT to ANY ICG
MEMBER </div>
<div>Regards</div>
<div>Kavouss</div>
<div> <br>
<br>
Sent from my iPhone</div>
<div>
<div>
<div><br>
On 8 Mar 2015, at 09:47, Patrik F�ltstr�m <<a href="mailto:paf@frobbit.se" target="_blank">paf@frobbit.se</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div>All,</div>
<div><br>
</div>
<div>This I treat as a request from an ICG member
for further explanation by other ICG members.</div>
<div><br>
</div>
<div> Patrik<br>
</div>
<div><br>
Begin forwarded message:<br>
<br>
</div>
<blockquote type="cite">
<div><b>From:</b> Kavouss Arasteh <<a href="mailto:kavouss.arasteh@gmail.com" target="_blank">kavouss.arasteh@gmail.com</a>><br>
<b>Date:</b> 8 mars 2015 08:30:25 CET<br>
<b>To:</b> Patrik F�ltstr�m <<a href="mailto:paf@frobbit.se" target="_blank">paf@frobbit.se</a>>,
Mohamed El Bashir <<a href="mailto:mbashir@mbash.net" target="_blank">mbashir@mbash.net</a>>,
Alissa Cooper <<a href="mailto:alissa@cooperw.in" target="_blank">alissa@cooperw.in</a>><br>
<b>Subject:</b> <b>Information requested</b><br>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div>
<div dir="ltr">
<table cellpadding="0">
<tbody>
<tr>
<td>
<div><span><font color="#777777">� </font><b><span dir="ltr" name="Patrik">Patrik</span></b><font color="#777777">, </font><b><span dir="ltr" name="Mohamed">Mohamed</span></b><font color="#777777">, <span dir="ltr" name="Alissa">Alissa</span>,
<span dir="ltr" name="WUKnoben">WUKnoben</span>,
<span dir="ltr" name="ICG">ICG</span>
</font></span></div>
<div><font color="#777777"><img alt="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"></font></div>
</td>
</tr>
</tbody>
</table>
<div>
<div style="overflow:hidden">
<div dir="ltr">
<div>Step 2 ,ICG Assessement of
Cummunity proposals</div>
<div>Dear Vice chair, </div>
<div>May you please ask Jari and Alan
Barret or Paul Wilson to provide the
foloowings;</div>
<div>A COMPARATIVE Table indicating
the prcess of accountability
currently in force and implemented
and those which will be required
after Transitiion.</div>
<div>It would be useful to have that
comparative Table enabling ICG
Members to better undersatnd how the
accountability of Protocol Parameter
and Numbers are affected by
Transition.</div>
<div>The reports of these two
communities are difficult to make
such a comparision.</div>
<div>Without that I will have serious
difficulties to comment on the
exacteness and appropriateness of
the content of these two comminities
on accountability before and after
transition.</div>
<div>By the way, Jari promised to
provide a graphic Diagram regarding
internal accountability being
carried out by IETF</div>
<div>mOREOVER, aLAN bARRET / Paul
Wilson ,are respectfully requested
to provide similar graphic Diagram
about the accountability currently
in force in RIRs ,in particular
that RIRs have a more decentralized
process of five regional communities
and the overall accountabilities of
the entire Rir s are not clear</div>
<div>Rergards </div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Internal-cg mailing list</span><br>
<span><a href="mailto:Internal-cg@ianacg.org" target="_blank">Internal-cg@ianacg.org</a></span><br>
<span><a href="http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a></span><br>
</div>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Internal-cg mailing list
<a href="mailto:Internal-cg@ianacg.org" target="_blank">Internal-cg@ianacg.org</a>
<a href="http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Internal-cg mailing list<br>
<a href="mailto:Internal-cg@ianacg.org">Internal-cg@ianacg.org</a><br>
<a href="http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org" target="_blank">http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>Internal-cg mailing list<br><a href="mailto:Internal-cg@ianacg.org">Internal-cg@ianacg.org</a><br>http://ianacg.org/mailman/listinfo/internal-cg_ianacg.org<br></blockquote></div><br></div></div></body></html>