<div dir="ltr">John, <div><br></div><div>You asked me to elaborate on what I meant by "pulling back the IANA function" and "membership"</div><div><br></div><div>So right now NTIA has some ability to threaten to break, or actually break the contract for the IANA function, and award that to another organization. I assume the decision to (threaten to) break the contract for the IANA service (or break the MoU or whatever legal document we have) would rest with someone or some body using some process. We need to sort out what body or person has that power, what is the process followed, and to what extend does the ARIN membership (and the memberships of the other RIRs) have input and or oversight into that process. </div><div><br></div><div>Generally yes I mean "community" but when it comes to governance issues we have a history of using ARIN membership not ARIN community. As such I said membership to vaguely mean the ARIN membership (particular to this region's input) and the input of the members of the other 4 regions.</div><div><br></div><div>Does that clarify it?</div><div><br></div><div>Thanks for your service on the CRISP team,</div><div><br></div><div>__Jason</div><div><br></div><div><span class="im"><blockquote><div dir="ltr"><font face="arial,sans-serif">3. How pulling back the IANA function should work post NTIA transition, and what membership oversight there is for it, is completely new ground. I'd argue for CRISP to provide some slides as a starting point for discussion. Maybe slides in a weeks time, and assess where the discussion is 10 days after that?</font></div></blockquote><div><br></div></span><div>Not sure what you mean by “pulling back” and not sure what membership you are talking about? Or do you just mean “community oversight” ? Please elaborate</div><div><br></div><span class="im"><span style="font-family:Calibri,sans-serif;font-size:14px"></span></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 13, 2014 at 4:02 PM, Sweeting, John <span dir="ltr"><<a href="mailto:john.sweeting@twcable.com" target="_blank">john.sweeting@twcable.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>Jason,</div><span class="">
<div><br>
</div>
<div><br>
</div>
<span>
<div>
<div>On 11/13/14, 6:37 AM, "Jason Schiller" <<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>> wrote:</div>
</div>
<div><br>
</div>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">I think I answered this on Bill's thread"RIPE slide deck on the matter."
<div><br>
</div>
<div>In short the ARIN community needs to start shaping some actual text.</div>
<div><br>
</div>
<div>I have tried to separate the non-controversial stuff out, like documenting the current state of things:</div>
<div>- current SLAs</div>
<div>- Internet Number related IANA services our community uses</div>
</div>
</div>
</div>
</blockquote>
</span><span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div>- What is the current Global Policy</div>
<div>- Where does Global Policy come from</div>
<div>- How <span style="font-family:arial,sans-serif;font-size:13px">the GDPD is transparent, open, bottom-up and inclusive </span></div>
<div style="font-family:arial,sans-serif;font-size:13px"><font face="arial,sans-serif">- What are the oversight mechanisms for global policy making</font></div>
<div style="font-family:arial,sans-serif;font-size:13px"><font face="arial,sans-serif">- What are the over sight mechanisms for the operation of the IANA function</font></div>
<div><font face="arial,sans-serif">- and that the community agrees we are commenting in Internet Number Resources</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">I think CRISP, and especially that RIR staff, can go off and put together text on this and as it becomes available share it with the community. (I expect the community will mostly just nod to this).</font></div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>We will work with Michael to get this done</div><span class="">
<div><br>
</div>
<span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">I think the first two questions, 1. What type of legal document, and 2. between whom? Are fairly straight forward. I hope legal council can provide some advice, and after a short community discussion, the ARIN CRISP team
should be able to tell where this community stands (and share with us where other communities stand in reference to this question).
</font></div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>Again, we’ll work with Michael on this as well</div><span class="">
<div><br>
</div>
<span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div><font face="arial,sans-serif">Are all types of legal documents acceptable, in which case we move towards where other communities are headed? Is one type preferred over another, but a short list of the ones that are acceptable? Is the community ambivalent and
happy to defer to council?</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">I'd say maybe a week discussion after we have the advice of council. Once we have an answer to question 1, council and CRISP can go off and write the document and share it with the community. Once we have an answer to question
2, we can pop the names in.</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">3. How pulling back the IANA function should work post NTIA transition, and what membership oversight there is for it, is completely new ground. I'd argue for CRISP to provide some slides as a starting point for discussion.
Maybe slides in a weeks time, and assess where the discussion is 10 days after that?</font></div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>Not sure what you mean by “pulling back” and not sure what membership you are talking about? Or do you just mean “community oversight” ? Please elaborate</div><span class="">
<div><br>
</div>
<span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">4,5. is SLA stuff. Once we have the current SLAs, and the current list of IANA services the community uses, we can try to figure out if the SLAs are sufficient, if not modify them. This is maybe a week of discussion, then
the CRIPS team can modify the consolidated SLA document to include feedback.</font></div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>Agree, this should not be that difficult</div><span class="">
<div><br>
</div>
<span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">We also need to determine the future process for changing the SLAs, and how to provide oversight of the quality of service, how to declare (non-)compliance , and what is the membership oversight. We can try and address these
concerns once we pin down the SLAs, maybe 2 weeks?</font></div>
</div>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
</span><div>It is important to include this. As to the timeline below we’ll get a CRISP team call together to discuss and modify if needed. Thanks for taking the time to lay this out, it is very useful.</div>
<div><br>
</div>
<div>-john</div><div><div class="h5">
<div><br>
</div>
<span>
<blockquote style="BORDER-LEFT:#b5c4df 5 solid;PADDING:0 0 0 5;MARGIN:0 0 0 5">
<div>
<div>
<div dir="ltr">
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">So timelines...</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">If we want the ARIN output by 12/01 so CRISP have 45 days to assemble a single document...</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif">Current SLAs are published in a single doc by 11/17</font></div>
<div><font face="arial,sans-serif">Council publishes a list of legal documents by 11/17 comparing types of legal docs</font></div>
<div><font face="arial,sans-serif"> - contract for IANA services referencing an SLA</font></div>
<div><font face="arial,sans-serif"> - MoU</font></div>
<div><font face="arial,sans-serif"> - Legally binding SLA document</font></div>
<div><font face="arial,sans-serif"> - Something else?</font></div>
<div><font face="arial,sans-serif">One week discussion about which legal doc and between whom 11/17 - 11/23</font></div>
<div>
<div><font face="arial,sans-serif">One week discussion modifications to current SLA and IANA function reporting 11/17 - 11/23</font></div>
</div>
<div><font face="arial,sans-serif">CRISP team to write Legal Agreement 11/24 - 12/14</font></div>
<div><font face="arial,sans-serif">Discussion of 11/24 - 12/07</font></div>
<div><font face="arial,sans-serif"> - future SLA modification process</font></div>
<div><font face="arial,sans-serif"> - oversight of IANA performance </font></div>
<div><font face="arial,sans-serif"> - level of membership oversight</font></div>
<div style="font-family:arial,sans-serif;font-size:13px"><font face="arial,sans-serif">CRISP team to create SLA document 12/08 - 12/14</font></div>
<div style="font-family:arial,sans-serif;font-size:13px"><font face="arial,sans-serif"> - IANA SLA development process</font></div>
<div style="font-family:arial,sans-serif;font-size:13px"><font face="arial,sans-serif"> - IANA performance oversight</font></div>
<div><font face="arial,sans-serif"> - declaration on IANA (non-)compliance </font></div>
<div><font face="arial,sans-serif"> - level of membership oversight</font></div>
<div><font face="arial,sans-serif">Community to review and reiterate Legal and SLA documents when available through 12/14</font></div>
<div><font face="arial,sans-serif">CRISP produce unified doc 12/14 - 01/15/2015</font></div>
<div>
<div><font face="arial,sans-serif">Community to review unified documents when available through 01/11/2015</font></div>
</div>
<div><font face="arial,sans-serif"> - Community to find consensus position on issues through 01/11/2015</font></div>
<div><font face="arial,sans-serif">CRISP collect final modifications 01/11/2015 - 01/15/2015</font></div>
<div>
<div><font face="arial,sans-serif">CRISP to provide final iteration to RIR communities and CSG 01/15/2015</font></div>
</div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><span style="font-family:arial,sans-serif">Community to continue to </span><font face="arial,sans-serif">find consensus position on issues for unified draft 01/15/2015 - 09/2015</font></div>
<div><span style="font-family:arial,sans-serif">CRISP team to inform CSG of significant changes ongoing through 09/2015</span></div>
<div><span style="font-family:arial,sans-serif"><br>
</span></div>
<div><span style="font-family:arial,sans-serif">Community to shift focus to ARIN governance as global consensus discussion winds down through 09/2015</span><span style="font-family:arial,sans-serif"> </span><font face="arial,sans-serif"><br>
</font></div>
<div><span style="font-family:arial,sans-serif"><br>
</span></div>
<div>
<div><span style="font-family:arial,sans-serif">Community to shift focus to IANA Board oversight wrt ratification of Global Policy as ARIN governance discussion winds down through 09/2015</span><span style="font-family:arial,sans-serif"> </span><font face="arial,sans-serif"><br>
</font></div>
</div>
<div><span style="font-family:arial,sans-serif"><br>
</span></div>
<div><font face="arial,sans-serif">Community to shift focus to IANA oversight as IANA Board oversight discussion winds down through 09/2015</font></div>
<div><font face="arial,sans-serif"><br>
</font></div>
<div><font face="arial,sans-serif"> </font><span style="font-family:arial,sans-serif">Community to continue focus to IANA oversight - on going</span></div>
<div><span style="font-family:arial,sans-serif"><br>
</span></div>
<div><span style="font-family:arial,sans-serif">__Jason</span></div>
<div><span style="font-family:arial,sans-serif"><br>
</span></div>
<div><span style="font-family:arial,sans-serif"><br>
</span></div>
<div><font face="arial,sans-serif"><br>
</font></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Nov 11, 2014 at 5:33 PM, Andrew Dul <span dir="ltr">
<<a href="mailto:andrew.dul@quark.net" target="_blank">andrew.dul@quark.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>On 11/10/2014 6:41 AM, Jason Schiller wrote:<br>
> I see this work in various scopes of increasing size.<br>
><br>
> scope 1: documenting the metrics and putting them in a legal framework<br>
> scope 2: ensuring proper community over sight and modification of the<br>
> metrics.<br>
> scope 3: ensuring proper over sight of the IANA function (removal of<br>
> contract)<br>
> scope 4: ensuring proper over sight of ARIN<br>
> scope 5: ensuring proper over sight of the ICANN Board wrt<br>
> ratification of Global Policy Proposals<br>
> scope 6: ensuring proper over sight of ICANN<br>
><br>
> Scopes 1, 2 and 3 are required to transition the NTIA oversight.<br>
><br>
> To some extent 4 may be required if 2 and 3 depend on ARIN staff, or<br>
> ARIN board, or ARIN governance documentation, and not directly the<br>
> membership.<br>
><br>
> Scopes 5 and 6 are not directly impacted by the transition of NTIA<br>
> oversight of the IANA function wrt number resources, but do relate to<br>
> the larger question of removal of the NTIA over sight of IACNN and the<br>
> ability of NTIA to pull the plug if things go wrong.<br>
><br>
> I would argue we should do the following:<br>
> 1. quickly document the SLAs<br>
> 2. propose a straw-man for who holds the legal contract including or<br>
> referencing the SLAs<br>
> 3. document a process for modifying the SLA, transparently reporting<br>
> of the SLA performance to the community<br>
> 4. propose a straw-man for declaring (non-)compliance, and the actions<br>
> taking up to and including removal of the contract<br>
> 5. get community consensus on the straw-man for how holds the legal<br>
> contract, and what is the process for declaring (non-)compliance and<br>
> taking action.<br>
><br>
> Complete this by the end of the month.<br>
><br>
> Then while the CRIP team is working on unifying the outputs of the<br>
> communities, we should focus in on the increasing scope.<br>
><br>
> If the ARIN membership does not own the process for modifying the<br>
> SLAs, judging (non-)compliance, and taking action, then is there the<br>
> proper community oversight of those that do? (This needs to be<br>
> complete prior to the <a href="https://goto.google.com/no-go" target="_blank">go/no-go</a> decision of moving forward with the<br>
> transition)<br>
><br>
> Then beyond that, does the ARIN membership have the proper oversight<br>
> of ARIN in general, such as changes to the ARIN mission statement,<br>
> changes to the ARIN bylaws, and recall of board members, etc.<br>
><br>
> Then beyond that, does the RIR membership have the proper oversight of<br>
> the ICANN Board wrt the ratification of Global Policy. Are we<br>
> comfortable with the ability of the IACNN Board refusing to ratify a<br>
> Global Policy and going to arbitration? Are we comfortable going to<br>
> arbitration for every new Global Policy Proposal? Should there be<br>
> some other ICANN Board oversight? (we need to be comfortable with<br>
> these answers prior to the <a href="https://goto.google.com/no-go" target="_blank">go/no-go</a> decision of moving forward with<br>
> the transition)<br>
><br>
> Then if we solve all those issues, we can look more generally into the<br>
> oversight of ICANN.<br>
><br>
</div>
</div>
Jason,<br>
<br>
A good summary of what work is likely before us in the coming year(s).<br>
A more immediate question might be what needs to be done in the next<br>
couple of weeks before the CRISP group starts its formal work?<br>
<br>
Or to the members of the CRISP group from this region, what discussion<br>
do you still think needs to happen in this region before the global work<br>
starts?<br>
<br>
Andrew<br>
_______________________________________________<br>
Iana-transition mailing list<br>
<a href="mailto:Iana-transition@arin.net" target="_blank">Iana-transition@arin.net</a><br>
<a href="http://lists.arin.net/mailman/listinfo/iana-transition" target="_blank">http://lists.arin.net/mailman/listinfo/iana-transition</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div><font color="#555555" face="'courier new', monospace">
<div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="courier new,monospace">_______________________________________________________<br>
</font>
<div><font face="courier new,monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|<a href="tel:571-266-0006" value="+15712660006" target="_blank">571-266-0006</a></font></div>
<div><font face="courier new,monospace"><br>
</font></div>
</span></div>
</font></div>
</div>
</div>
</div>
</blockquote>
</span><br>
</div></div><hr>
<font face="Arial" color="Gray" size="1">This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely
for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to
this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.<br>
</font>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><font color="#555555" face="'courier new', monospace"><div><span style="color:rgb(0,0,0);font-family:arial"><font color="#555555" face="'courier new', monospace">_______________________________________________________<br></font><div><font face="'courier new', monospace">Jason Schiller|NetOps|<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>|571-266-0006</font></div><div><font face="'courier new', monospace"><br></font></div></span></div></font></div>
</div>