<div dir="ltr">John,<div><br></div><div>At this point we can only pursue this policy as an ARIN policy as written as we are post Sept 10, and the draft policy text is frozen.</div><div><br></div><div>I suspect the changes to make this global would be significant, unlikely to happen in last call, and even if rewritten on the floor at the public policy meeting (which is nearly prohibited) would likely require another cycle to provide the community enough time to review. </div>
<div><br></div><div>What I was attempting to do was jump start the conversation on a global approach such that if a global policy was desired, that would could possibly short cycle the process by sorting out those details earlier on in the discussion. </div>
<div><br></div><div>At this point a group of international authors are awaiting the out come of our ARIN discussion prior to moving forward. I have also noted that this group is aware of the significant streamlining and rewriting, and have also noted that the LACNIC Policy Manual is more in-line with the original RFC-2050 language that has been stricken. Discussion of the new language has been tabled until after the results of the discussion at ARIN meeting.</div>
<div><br></div><div>The options I presented in my previous email were options of alternative ways to proceed, if movement towards a global direction was desired earlier in the discussion, and are no longer valid. </div>
<div><br></div><div>I am not suggesting we try to make this a draft global policy at this point (sorry if I created any confusion). I was rather trying to explain the comment about considering a global policy proposal, how that could happen given the current text does not impact IANA, and that I was trying to get the community to consider the merits of a global policy and if we should move in that direction earlier in the process.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>__Jason</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 19, 2013 at 8:35 AM, 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="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div>Thanks Jason.</div>
<div><br>
</div>
<div>One other option, which I personally like, is that we can continue to process as is and then if/when there is a global opportunity initiated ARIN can participate in that as well. That one of the nice things about policy, it can be changed as required.</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div style="border-right:medium none;padding-right:0in;padding-left:0in;padding-top:3pt;text-align:left;font-size:11pt;border-bottom:medium none;font-family:Calibri;border-top:#b5c4df 1pt solid;padding-bottom:0in;border-left:medium none">
<span style="font-weight:bold">From: </span>Jason Schiller <<a href="mailto:jschiller@google.com" target="_blank">jschiller@google.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, September 18, 2013 9:24 PM<br>
<span style="font-weight:bold">To: </span>CJ Aronson <<a href="mailto:cja@daydream.com" target="_blank">cja@daydream.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [arin-ppml] Draft Policy ARIN-2013-4: RIR Principles - revised<br>
</div><div><div class="h5">
<div><br>
</div>
<div>
<div>
<div dir="ltr">As written is does not qualify as a global policy nor a globally coordinated policy.
<div><br>
</div>
<div>However one could image it *could* be written, such that IANA would also adopt these principles and these principles should be considered wrt policy of allocation of number resources to RIRs.</div>
<div><br>
</div>
<div>This would mean two things:</div>
<div><br>
</div>
<div>1. we, the global community, should also take these principles in consideration when developing draft global policies.</div>
<div><br>
</div>
<div>2. we, the ARIN region community could pass this (now) global policy, and have it not take effect until the four other regions also pass it and the ICANN board ratify it.</div>
<div><br>
</div>
<div>Optionally we could craft it as a regional policy that automatically gets elevated to a global policy should it pass all five RIRs.</div>
<div><br>
</div>
<div><br>
</div>
<div>The comments were a suggestion about the two points above, and a hint to get people to think if it should be written in such a way as to make it global and binding on IANA.</div>
<div><br>
</div>
<div>___Jason</div>
<div> </div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Sep 18, 2013 at 5:07 PM, CJ Aronson <span dir="ltr">
<<a href="mailto:cja@daydream.com" target="_blank">cja@daydream.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Someone help me here.
<div>I am not sure this would qualify as a "global policy" in terms of the ASO MOU. The document is here
<div><a href="http://archive.icann.org/en/aso/aso-mou-29oct04.htm" target="_blank">http://archive.icann.org/en/aso/aso-mou-29oct04.htm</a><br>
</div>
<div>I have always been told that an global policy is distinctly one that regulates the interaction between ICANN/IANA and the RIRs. Like policies for giving out blocks of address space or ASNs by the IANA, etc. </div>
<div><br>
</div>
<div>The MOU says this and I am not sure this policy would meet this..</div>
<div><br>
</div>
<div>Thanks</div>
<div>----Cathy</div>
<div><br>
</div>
<div>"<b style="font-size:medium;font-family:Arial,Helvetica,sans-serif">5. Global Policy Development Process</b></div>
<blockquote style="font-size:medium;font-family:Arial,Helvetica,sans-serif">
<p>Global policies are defined within the scope of this agreement as Internet number resource policies that have the agreement of all RIRs according to their policy development processes and ICANN, and require specific actions or outcomes on the part of IANA
or any other external ICANN-related body in order to be implemented.</p>
<p>Global policies will be developed in the context of this agreement, according to the processes defined by attachment A to this MoU.</p>
<p>Under this agreement the ICANN Board will ratify proposed global policies in accordance with the Global Policy Development Process, using review procedures as determined by ICANN. ICANN will publish these procedures no later than ninety (90) days from the
date of the signature of this agreement by all parties.</p>
<div>"</div>
<div><br>
</div>
</blockquote>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Sep 18, 2013 at 12:35 PM, Chris Grundemann <span dir="ltr">
<<a href="mailto:cgrundemann@gmail.com" target="_blank">cgrundemann@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>
<div>On Tue, Sep 17, 2013 at 7:21 PM, David Conrad <span dir="ltr"><<a href="mailto:drc@virtualized.org" target="_blank">drc@virtualized.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Chris,<br>
<div><br>
On Sep 17, 2013, at 11:03 AM, Chris Grundemann <<a href="mailto:cgrundemann@gmail.com" target="_blank">cgrundemann@gmail.com</a>> wrote:<br>
> This current text aims to document existing practice based on historical norms which best instruct the driving principles required to successfully operate an RIR.<br>
<br>
</div>
Apologies if this has been discussed before, but is this intended to be a 'global policy' (in the unanimous among all RIRs and ratified by ICANN board sense)?<br>
</blockquote>
<div><br>
</div>
</div>
</div>
<div>Currently ARIN-2013-4 has only been submitted in the ARIN region. There has been some discussion of making it a global proposal, which would require someone submitting the same text in all five regions (and all five regions agreeing to the same text),
but that has not happened at this point.<br>
<br>
</div>
<div>HTH,<br>
</div>
<div>~Chris<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Thanks,<br>
-drc<br>
<br>
<span><font color="#888888"></font></span></blockquote>
</div>
<span><font color="#888888"><br>
<br clear="all">
<span><font color="#888888"><br>
-- <br>
@ChrisGrundemann<br>
<a href="http://chrisgrundemann.com" target="_blank">http://chrisgrundemann.com</a></font></span></font></span></div>
</div>
<span><font color="#888888"><br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</font></span></blockquote>
</div>
<br>
</div>
<br>
_______________________________________________<br>
PPML<br>
You are receiving this message because you are subscribed to<br>
the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>
Unsubscribe or manage your mailing list subscription at:<br>
<a href="http://lists.arin.net/mailman/listinfo/arin-ppml" target="_blank">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>
Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<font color="#555555" face="'courier new', monospace">
<div><span style="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></div></span><br>
<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><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>