<?xml version="1.0" encoding="ISO-8859-1"?>

<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns="http://purl.org/rss/1.0/"
 xmlns:content="http://purl.org/rss/1.0/modules/content/"
 xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
 xmlns:admin="http://webns.net/mvcb/"
>

<channel rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/date.html">
<title>ARIN-PPML Archive</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/date.html</link>
<description>arin-ppml-feed</description>
<items>
 <rdf:Seq>
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026966.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026964.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026965.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026963.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026962.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026961.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026960.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026959.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026958.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026957.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026956.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026955.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026954.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026953.html" />
  <rdf:li rdf:resource="http://lists.arin.net/pipermail/arin-ppml/2013-June/026952.html" />
 </rdf:Seq>
</items>
</channel>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026966.html">
<title>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026966.html</link>
<description>lol. An Amen and two shut-ups!
OK, I&#x2019;ll shut up.


From: Chris James 
Sent: Wednesday, June 19, 2013 2:19 PM
To: Sweeting, John 
Cc: John Curran ; Mike Burns ; arin-ppml at arin.net 
Subject: Re: [arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)

Agreed. [...]</description>
<dc:creator>Mike Burns</dc:creator>
<dc:date>2013-06-19T14:30:06Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[lol. An Amen and two shut-ups!<br/>OK, I&rsquo;ll shut up.<br/><br/><br/>From: Chris James <br/>Sent: Wednesday, June 19, 2013 2:19 PM<br/>To: Sweeting, John <br/>Cc: John Curran ; Mike Burns ; arin-ppml at arin.net <br/>Subject: Re: [arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)<br/><br/>Agreed.<br/><br/>Chris James <br/>Datacate Inc.<br/>2999 Gold Canal Dr.<br/>Rancho Cordova, CA 95670<br/>916-526-0737 o.<br/>916-668-5851 d.<br/><br/><br/><br/><br/>On Wed, Jun 19, 2013 at 11:16 AM, Sweeting, John &lt;john.sweeting at twcable.com&gt; wrote:<br/><br/>  Hi,<br/><br/>  If possible could we move this to a private conversation? This has all been aired on PPML several times before and at this point it serves no purpose. If we could please get back on track and focus on a current draft policy or proposal and state reasons for support or non support it would be very much appreciated. <br/><br/>  Thanks,<br/>  John<br/><br/><br/><br/>  From: John Curran &lt;jcurran at arin.net&gt;<br/>  Date: Wednesday, June 19, 2013 2:12 PM<br/>  To: Mike Burns &lt;mike at nationwideinc.com&gt;<br/>  Cc: &quot;arin-ppml at arin.net&quot; &lt;arin-ppml at arin.net&gt;, Mike Burns &lt;mike at iptrading.com&gt;<br/>  Subject: Re: [arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)<br/><br/><br/>  On Jun 19, 2013, at 12:42 PM, Mike Burns &lt;mike at nationwideinc.com&gt; wrote:<br/><br/><br/>         You may say &quot;legally purchasing&quot; rights, but I truly don&#39;t know what these parties think <br/>         they purchased, since it can&#39;t be the ability to inject routes and have them accepted <br/>         (no one can provide that) nor the right to use the entry in the registry, when the <br/>         circumstances are contrary to policy.<br/><br/>    I guess they figure they are buying what the Nortel bankruptcy judge called the &ldquo;exclusive right to use&rdquo; the addresses.<br/><br/>  Indeed, but those are rights which may be transferred in accordance with policy.  In the case<br/>  of Nortel, this was accomplished by ARIN working with Microsoft and confirming compliance<br/>  and then removing our objection, a point which Nortel&#39;s own filing makes - &quot;10. Second, the <br/>  revisions reflected in the Amended Sale Agreement and Revised Order were the result of <br/>  negotiations between Microsoft, ARIN and NNI and, accordingly, ARIN&rsquo;s counsel has <br/>  informed NNI that it does not oppose entry of the Revised Order. &quot; &lt;NNI Docket #5280&gt;<br/><br/>  No problem buying the rights (that is, after all, what a transfer is) but you also have to wait<br/>  for the approval before considering the deal &quot;closed&quot;, just as in the Nortel case.<br/><br/>    Consider if the buyer of the radio station could begin and continue broadcasting without regard to regulatory approval?<br/>    Does that make a listener un-hear a broadcast? Or would the incentives lead to lots of wildcat radio stations pending approval?<br/><br/><br/>  The safest move is to finalize the sale upon the approval; claiming that it is complete prior<br/>  to that point is rather innovative (and might even be considered fraud if done knowingly...)<br/><br/>  FYI,<br/>  /John<br/><br/>  John Curran<br/>  President and CEO<br/>  ARIN<br/><br/><br/><br/><br/><br/>------------------------------------------------------------------------------<br/>  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/><br/><br/>  _______________________________________________<br/>  PPML<br/>  You are receiving this message because you are subscribed to<br/>  the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).<br/>  Unsubscribe or manage your mailing list subscription at:<br/>  http://lists.arin.net/mailman/listinfo/arin-ppml<br/>  Please contact info at arin.net if you experience any issues.<br/><br/><br/><br/>Confidentiality Note:<br/>The contents of this e-mail message and its attachments, if any, are intended solely for the addressee(s) hereof. If you are not the named addressee, or if you believe this message has been addressed to you in error, you are requested not to read, disclose, reproduce, distribute, disseminate or otherwise use this information. Delivery of this message to any person other than the intended recipient(s) is not intended in any way to waive confidentiality. If you have received this transmission in error, please alert the sender by reply e-mail. It is also requested that you immediately delete this message and its attachments, if any. Thank You.<br/><br/>&copy; 2013 Technicate Solutions Inc.<br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/e200e998/attachment-0001.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026964.html">
<title>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026964.html</link>
<description>
Hi,

If possible could we move this to a private conversation? This has all been aired on PPML several times before and at this point it serves no purpose. If we could please get back on track and focus on a current draft policy or proposal and state reasons for support or non support it would be very much appreciated.

John -

  Excellent idea - I just needed to clarify that &#x22;accuracy of the registry&#x22; is probably a little
  more complex that the phrase appears on the surface.   At long as folks realize that it
  is not necessarily an accuracy issue as much as an &#x22;ease of use of the registry&#x22; issue,
  that will suffice.   I believe that the recent conversation has made that clear for purposes
  of further consideration of the draft policy.

Thanks!
/John

John Curran
President and CEO
ARIN
</description>
<dc:creator>John Curran</dc:creator>
<dc:date>2013-06-19T14:23:28Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[On Jun 19, 2013, at 1:16 PM, &quot;Sweeting, John&quot; &lt;john.sweeting at twcable.com&lt;mailto:john.sweeting at twcable.com&gt;&gt; wrote:<br/><br/>Hi,<br/><br/>If possible could we move this to a private conversation? This has all been aired on PPML several times before and at this point it serves no purpose. If we could please get back on track and focus on a current draft policy or proposal and state reasons for support or non support it would be very much appreciated.<br/><br/>John -<br/><br/>  Excellent idea - I just needed to clarify that &quot;accuracy of the registry&quot; is probably a little<br/>  more complex that the phrase appears on the surface.   At long as folks realize that it<br/>  is not necessarily an accuracy issue as much as an &quot;ease of use of the registry&quot; issue,<br/>  that will suffice.   I believe that the recent conversation has made that clear for purposes<br/>  of further consideration of the draft policy.<br/><br/>Thanks!<br/>/John<br/><br/>John Curran<br/>President and CEO<br/>ARIN<br/><br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/5d1c33f4/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026965.html">
<title>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026965.html</link>
<description>Agreed.

Chris James
Datacate Inc.
2999 Gold Canal Dr.
Rancho Cordova, CA 95670
916-526-0737 o.
916-668-5851 d.



On Wed, Jun 19, 2013 at 11:16 AM, Sweeting, John
&#x3C;john.sweeting at twcable.com&#x3E;wrote:

[...]

Confidentiality Note:
The contents of this e-mail message and its attachments, if any, are  [...]</description>
<dc:creator>Chris James</dc:creator>
<dc:date>2013-06-19T14:19:33Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[Agreed.<br/><br/>Chris James<br/>Datacate Inc.<br/>2999 Gold Canal Dr.<br/>Rancho Cordova, CA 95670<br/>916-526-0737 o.<br/>916-668-5851 d.<br/><br/><br/><br/>On Wed, Jun 19, 2013 at 11:16 AM, Sweeting, John<br/>&lt;john.sweeting at twcable.com&gt;wrote:<br/><br/>&gt;  Hi,<br/>&gt;<br/>&gt;  If possible could we move this to a private conversation? This has all<br/>&gt; been aired on PPML several times before and at this point it serves no<br/>&gt; purpose. If we could please get back on track and focus on a current draft<br/>&gt; policy or proposal and state reasons for support or non support it would be<br/>&gt; very much appreciated.<br/>&gt;<br/>&gt;  Thanks,<br/>&gt; John<br/>&gt;<br/>&gt;<br/>&gt;<br/>&gt;   From: John Curran &lt;jcurran at arin.net&gt;<br/>&gt; Date: Wednesday, June 19, 2013 2:12 PM<br/>&gt; To: Mike Burns &lt;mike at nationwideinc.com&gt;<br/>&gt; Cc: &quot;arin-ppml at arin.net&quot; &lt;arin-ppml at arin.net&gt;, Mike Burns &lt;<br/>&gt; mike at iptrading.com&gt;<br/>&gt; Subject: Re: [arin-ppml] A Redefinition<br/>&gt; ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)<br/>&gt;<br/>&gt;   On Jun 19, 2013, at 12:42 PM, Mike Burns &lt;mike at nationwideinc.com&gt; wrote:<br/>&gt;<br/>&gt;        You may say &quot;legally purchasing&quot; rights, but I truly don&#39;t know<br/>&gt; what these parties think<br/>&gt;    they purchased, since it can&#39;t be the ability to inject routes and have<br/>&gt; them accepted<br/>&gt;    (no one can provide that) nor the right to use the entry in the<br/>&gt; registry, when the<br/>&gt;    circumstances are contrary to policy.<br/>&gt;<br/>&gt;<br/>&gt; I guess they figure they are buying what the Nortel bankruptcy judge<br/>&gt; called the &ldquo;exclusive right to use&rdquo; the addresses.<br/>&gt;<br/>&gt;<br/>&gt;  Indeed, but those are rights which may be transferred in accordance with<br/>&gt; policy.  In the case<br/>&gt; of Nortel, this was accomplished by ARIN working with Microsoft and<br/>&gt; confirming compliance<br/>&gt; and then removing our objection, a point which Nortel&#39;s own filing makes -<br/>&gt; &quot;10. Second, the<br/>&gt; revisions reflected in the Amended Sale Agreement and Revised Order were<br/>&gt; the result of<br/>&gt; negotiations between Microsoft, ARIN and NNI and, accordingly, ARIN&rsquo;s<br/>&gt; counsel has<br/>&gt; informed NNI that it does not oppose entry of the Revised Order. &quot; &lt;NNI<br/>&gt; Docket #5280&gt;<br/>&gt;<br/>&gt;  No problem buying the rights (that is, after all, what a transfer is)<br/>&gt; but you also have to wait<br/>&gt; for the approval before considering the deal &quot;closed&quot;, just as in the<br/>&gt; Nortel case.<br/>&gt;<br/>&gt;<br/>&gt;   Consider if the buyer of the radio station could begin and continue<br/>&gt; broadcasting without regard to regulatory approval?<br/>&gt; Does that make a listener un-hear a broadcast? Or would the incentives<br/>&gt; lead to lots of wildcat radio stations pending approval?<br/>&gt;<br/>&gt;<br/>&gt;  The safest move is to finalize the sale upon the approval; claiming that<br/>&gt; it is complete prior<br/>&gt; to that point is rather innovative (and might even be considered fraud if<br/>&gt; done knowingly...)<br/>&gt;<br/>&gt;  FYI,<br/>&gt; /John<br/>&gt;<br/>&gt;  John Curran<br/>&gt; President and CEO<br/>&gt; ARIN<br/>&gt;<br/>&gt;<br/>&gt;<br/>&gt;<br/>&gt; ------------------------------<br/>&gt; This E-mail and any of its attachments may contain Time Warner Cable<br/>&gt; proprietary information, which is privileged, confidential, or subject to<br/>&gt; copyright belonging to Time Warner Cable. This E-mail is intended solely<br/>&gt; for the use of the individual or entity to which it is addressed. If you<br/>&gt; are not the intended recipient of this E-mail, you are hereby notified that<br/>&gt; any dissemination, distribution, copying, or action taken in relation to<br/>&gt; the contents of and attachments to this E-mail is strictly prohibited and<br/>&gt; may be unlawful. If you have received this E-mail in error, please notify<br/>&gt; the sender immediately and permanently delete the original and any copy of<br/>&gt; this E-mail and any printout.<br/>&gt;<br/>&gt; _______________________________________________<br/>&gt; PPML<br/>&gt; You are receiving this message because you are subscribed to<br/>&gt; the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).<br/>&gt; Unsubscribe or manage your mailing list subscription at:<br/>&gt; http://lists.arin.net/mailman/listinfo/arin-ppml<br/>&gt; Please contact info at arin.net if you experience any issues.<br/>&gt;<br/><br/>-- <br/>Confidentiality Note:<br/>The contents of this e-mail message and its attachments, if any, are <br/>intended solely for the addressee(s) hereof. If you are not the named <br/>addressee, or if you believe this message has been addressed to you in <br/>error, you are requested not to read, disclose, reproduce, distribute, <br/>disseminate or otherwise use this information. Delivery of this message to <br/>any person other than the intended recipient(s) is not intended in any way <br/>to waive confidentiality. If you have received this transmission in error, <br/>please alert the sender by reply e-mail. It is also requested that you <br/>immediately delete this message and its attachments, if any. Thank You.<br/><br/>&copy; 2013 Technicate Solutions Inc.<br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/856f3c05/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026963.html">
<title>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026963.html</link>
<description>Hi,

If possible could we move this to a private conversation? This has all been aired on PPML several times before and at this point it serves no purpose. If we could please get back on track and focus on a current draft policy or proposal and state reasons for support or non support it would be very much appreciated.

Thanks,
John



From: John Curran &#x3C;jcurran at arin.net&#x3C;mailto:jcurran at arin.net&#x3E;&#x3E;
Date: Wednesday, June 19, 2013 2:12 PM
To: Mike Burns &#x3C;mike at nationwideinc.com&#x3C;mailto:mike at nationwideinc.com&#x3E;&#x3E;
Cc: &#x22;arin-ppml at arin.net&#x3C;mailto:arin-ppml at arin.net&#x3E;&#x22; &#x3C;arin-ppml at arin.net&#x3C;mailto:arin-ppml at arin.net&#x3E;&#x3E;, Mike Burns &#x3C;mike at iptrading.com&#x3C;mailto:mike at iptrading.com&#x3E;&#x3E;
Subject: Re: [arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)

On Jun 19, 2013, at 12:42 PM, Mike Burns &#x3C;mike at nationwideinc.com&#x3C;mailto:mike at nationwideinc.com&#x3E;&#x3E; wrote:

   You may say &#x22;legally purchasing&#x22; rights, but I truly don&#x27;t know what these parties think
   they purchased, since it can&#x27;t be the ability to inject routes and have them accepted
   (no one can provide that) nor the right to use the entry in the registry, when the
   circumstances are contrary to policy.

I guess they figure they are buying what the Nortel bankruptcy judge called the &#x201C;exclusive right to use&#x201D; the addresses.

Indeed, but those are rights which may be transferred in accordance with policy.  In the case
of Nortel, this was accomplished by ARIN working with Microsoft and confirming compliance
and then removing our objection, a point which Nortel&#x27;s own filing makes - &#x22;10. Second, the
revisions reflected in the Amended Sale Agreement and Revised Order were the result of
negotiations between Microsoft, ARIN and NNI and, accordingly, ARIN&#x2019;s counsel has
informed NNI that it does not oppose entry of the Revised Order. &#x22; &#x3C;NNI Docket #5280&#x3E;

No problem buying the rights (that is, after all, what a transfer is) but you also have to wait
for the approval before considering the deal &#x22;closed&#x22;, just as in the Nortel case.

Consider if the buyer of the radio station could begin and continue broadcasting without regard to regulatory approval?
Does that make a listener un-hear a broadcast? Or would the incentives lead to lots of wildcat radio stations pending approval?

The safest move is to finalize the sale upon the approval; claiming that it is complete prior
to that point is rather innovative (and might even be considered fraud if done knowingly...)

FYI,
/John

John Curran
President and CEO
ARIN



</description>
<dc:creator>Sweeting, John</dc:creator>
<dc:date>2013-06-19T14:16:51Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[Hi,<br/><br/>If possible could we move this to a private conversation? This has all been aired on PPML several times before and at this point it serves no purpose. If we could please get back on track and focus on a current draft policy or proposal and state reasons for support or non support it would be very much appreciated.<br/><br/>Thanks,<br/>John<br/><br/><br/><br/>From: John Curran &lt;jcurran at arin.net&lt;mailto:jcurran at arin.net&gt;&gt;<br/>Date: Wednesday, June 19, 2013 2:12 PM<br/>To: Mike Burns &lt;mike at nationwideinc.com&lt;mailto:mike at nationwideinc.com&gt;&gt;<br/>Cc: &quot;arin-ppml at arin.net&lt;mailto:arin-ppml at arin.net&gt;&quot; &lt;arin-ppml at arin.net&lt;mailto:arin-ppml at arin.net&gt;&gt;, Mike Burns &lt;mike at iptrading.com&lt;mailto:mike at iptrading.com&gt;&gt;<br/>Subject: Re: [arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)<br/><br/>On Jun 19, 2013, at 12:42 PM, Mike Burns &lt;mike at nationwideinc.com&lt;mailto:mike at nationwideinc.com&gt;&gt; wrote:<br/><br/>   You may say &quot;legally purchasing&quot; rights, but I truly don&#39;t know what these parties think<br/>   they purchased, since it can&#39;t be the ability to inject routes and have them accepted<br/>   (no one can provide that) nor the right to use the entry in the registry, when the<br/>   circumstances are contrary to policy.<br/><br/>I guess they figure they are buying what the Nortel bankruptcy judge called the &ldquo;exclusive right to use&rdquo; the addresses.<br/><br/>Indeed, but those are rights which may be transferred in accordance with policy.  In the case<br/>of Nortel, this was accomplished by ARIN working with Microsoft and confirming compliance<br/>and then removing our objection, a point which Nortel&#39;s own filing makes - &quot;10. Second, the<br/>revisions reflected in the Amended Sale Agreement and Revised Order were the result of<br/>negotiations between Microsoft, ARIN and NNI and, accordingly, ARIN&rsquo;s counsel has<br/>informed NNI that it does not oppose entry of the Revised Order. &quot; &lt;NNI Docket #5280&gt;<br/><br/>No problem buying the rights (that is, after all, what a transfer is) but you also have to wait<br/>for the approval before considering the deal &quot;closed&quot;, just as in the Nortel case.<br/><br/>Consider if the buyer of the radio station could begin and continue broadcasting without regard to regulatory approval?<br/>Does that make a listener un-hear a broadcast? Or would the incentives lead to lots of wildcat radio stations pending approval?<br/><br/>The safest move is to finalize the sale upon the approval; claiming that it is complete prior<br/>to that point is rather innovative (and might even be considered fraud if done knowingly...)<br/><br/>FYI,<br/>/John<br/><br/>John Curran<br/>President and CEO<br/>ARIN<br/><br/><br/><br/><br/>________________________________<br/>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/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/cf50db7a/attachment-0001.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026962.html">
<title>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026962.html</link>
<description>
   You may say &#x22;legally purchasing&#x22; rights, but I truly don&#x27;t know what these parties think
   they purchased, since it can&#x27;t be the ability to inject routes and have them accepted
   (no one can provide that) nor the right to use the entry in the registry, when the [...]</description>
<dc:creator>John Curran</dc:creator>
<dc:date>2013-06-19T14:12:21Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[On Jun 19, 2013, at 12:42 PM, Mike Burns &lt;mike at nationwideinc.com&lt;mailto:mike at nationwideinc.com&gt;&gt; wrote:<br/><br/>   You may say &quot;legally purchasing&quot; rights, but I truly don&#39;t know what these parties think<br/>   they purchased, since it can&#39;t be the ability to inject routes and have them accepted<br/>   (no one can provide that) nor the right to use the entry in the registry, when the<br/>   circumstances are contrary to policy.<br/><br/>I guess they figure they are buying what the Nortel bankruptcy judge called the &ldquo;exclusive right to use&rdquo; the addresses.<br/><br/>Indeed, but those are rights which may be transferred in accordance with policy.  In the case<br/>of Nortel, this was accomplished by ARIN working with Microsoft and confirming compliance<br/>and then removing our objection, a point which Nortel&#39;s own filing makes - &quot;10. Second, the<br/>revisions reflected in the Amended Sale Agreement and Revised Order were the result of<br/>negotiations between Microsoft, ARIN and NNI and, accordingly, ARIN&rsquo;s counsel has<br/>informed NNI that it does not oppose entry of the Revised Order. &quot; &lt;NNI Docket #5280&gt;<br/><br/>No problem buying the rights (that is, after all, what a transfer is) but you also have to wait<br/>for the approval before considering the deal &quot;closed&quot;, just as in the Nortel case.<br/><br/>Consider if the buyer of the radio station could begin and continue broadcasting without regard to regulatory approval?<br/>Does that make a listener un-hear a broadcast? Or would the incentives lead to lots of wildcat radio stations pending approval?<br/><br/>The safest move is to finalize the sale upon the approval; claiming that it is complete prior<br/>to that point is rather innovative (and might even be considered fraud if done knowingly...)<br/><br/>FYI,<br/>/John<br/><br/>John Curran<br/>President and CEO<br/>ARIN<br/><br/><br/><br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/5f0208a0/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026961.html">
<title>[arin-ppml] Fw: A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026961.html</link>
<description>Amen!  ARINs mission is to Allocate and Register. It isn&#x27;t to find ways to Not Allocate and reasons to Not Register.

Sent from my iPhone

On Jun 19, 2013, at 12:40 PM, &#x22;Mike Burns&#x22; &#x3C;mike at nationwideinc.com&#x3C;mailto:mike at nationwideinc.com&#x3E;&#x3E; wrote:

 [...]</description>
<dc:creator>Steven Ryerse</dc:creator>
<dc:date>2013-06-19T14:00:47Z</dc:date>
<dc:subject>[arin-ppml] Fw: A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[Amen!  ARINs mission is to Allocate and Register. It isn&#39;t to find ways to Not Allocate and reasons to Not Register.<br/><br/>Sent from my iPhone<br/><br/>On Jun 19, 2013, at 12:40 PM, &quot;Mike Burns&quot; &lt;mike at nationwideinc.com&lt;mailto:mike at nationwideinc.com&gt;&gt; wrote:<br/><br/><br/>   You started by indicating that this was an issue with registry accuracy, but the fact is that<br/>   when the purported sale is contrary to the policy, the registry still accurately reflects the<br/>   actual party with the rights to the unique registry entry, since the rights only change when<br/>   done in accordance with policy set by the community.   Whether something is being routed<br/>   on the Internet or not is an entirely different matter, as shown operationally from time to time<br/>   by the various route leaks that occur.<br/><br/>   The registry is accurate as long as it follows the community-developed policy; if you don&#39;t<br/>   like the policy, then work to change it.  Regardless, the registry accurately reflects what<br/>   the community indicates it should under the circumstances.<br/><br/>Thanks,<br/>/John<br/><br/>Hi John,<br/><br/>The community has loudly and recently spoken about which goal of RFC-2050 is universally accepted.<br/>That goal is registration. If you want to continue to maintain the fallacy that the entities which are actually routing and using the addresses as their own, after legally purchasing those rights, are not the ones who should be listed in the Whois registry, then you are standing the goal of registration on its head by simply defining all the entries as accurate, in the same way the authorities responded to Galileo (&ldquo;and yet it moves&rdquo;), by asserting the primacy of words over reality.<br/><br/>Nevermind the propriety of maintaining deliberately false abuse contact information for purposes of maintaining a goal of conservation which was designed in the Free Pool Era and which is not appropriate in a world with a transfer market.<br/>If the needs requirement is driving transactions underground, we are asked here to prioritize goals. I argue that the goal of conservation is lower than the goal of registration, has always been so, and with the advent of a pricing paradigm which naturally supports conservation, it is foolish of stewards to maintain one practice in support of a lesser goal in the face of a negative impact on the primary goal.<br/><br/>Regards,<br/>MIke<br/>_______________________________________________<br/>PPML<br/>You are receiving this message because you are subscribed to<br/>the ARIN Public Policy Mailing List (ARIN-PPML at arin.net&lt;mailto:ARIN-PPML at arin.net&gt;).<br/>Unsubscribe or manage your mailing list subscription at:<br/>http://lists.arin.net/mailman/listinfo/arin-ppml<br/>Please contact info at arin.net&lt;mailto:info at arin.net&gt; if you experience any issues.<br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/5b00a4d8/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026960.html">
<title>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026960.html</link>
<description>Hi John,

   You may say &#x22;legally purchasing&#x22; rights, but I truly don&#x27;t know what these parties think 
   they purchased, since it can&#x27;t be the ability to inject routes and have them accepted 
   (no one can provide that) nor the right to use the entry in the registry, when the  [...]</description>
<dc:creator>Mike Burns</dc:creator>
<dc:date>2013-06-19T13:42:34Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition ofIPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[Hi John,<br/><br/>   You may say &quot;legally purchasing&quot; rights, but I truly don&#39;t know what these parties think <br/>   they purchased, since it can&#39;t be the ability to inject routes and have them accepted <br/>   (no one can provide that) nor the right to use the entry in the registry, when the <br/>   circumstances are contrary to policy.<br/><br/>I guess they figure they are buying what the Nortel bankruptcy judge called the &ldquo;exclusive right to use&rdquo; the addresses.<br/>Whatever it is they are buying, they are routing and using the addresses. They move....<br/><br/><br/>   This is not new concept; e.g. you can buy a radio station broadcast license from an <br/>   existing operator, but it&#39;s not actually a sale until it passes regulatory approvals to be <br/>   reassigned to you.  Until that time, your purchase is without any actual substance.   <br/><br/>/John<br/><br/>Consider if the buyer of the radio station could begin and continue broadcasting without regard to regulatory approval?<br/>Does that make a listener un-hear a broadcast? Or would the incentives lead to lots of wildcat radio stations pending approval?<br/><br/>Regards,<br/>Mike<br/><br/><br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/cdd3dd36/attachment-0001.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026959.html">
<title>[arin-ppml] A Redefinition of IPv4 Need postARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026959.html</link>
<description>
[...]

This is part of the service one buys upon telling an ISP you want a
/24 for multihoming per ARIN NRPM 4.2.3.6. Not a fresh, new or
dangerous concept, nor one that fails to work.

IIRC, there was an effort to prevent this once... ISPs that wouldn&#x27;t [...]</description>
<dc:creator>William Herrin</dc:creator>
<dc:date>2013-06-19T13:17:08Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition of IPv4 Need postARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[On Wed, Jun 19, 2013 at 11:32 AM, John Curran &lt;jcurran at arin.net&gt; wrote:<br/>&gt; On Jun 19, 2013, at 8:12 AM, Mike Burns &lt;mike at nationwideinc.com&gt; wrote:<br/>&gt;&gt; Sometimes they buy the ability to route and use the (legacy) addresses<br/>&gt;&gt; without changing that line in the Whois database.<br/>&gt;<br/>&gt; Now that&#39;s quite interesting, given that actually anyone can configure their<br/>&gt; equipment<br/>&gt; to originate routes to any IP address block they wish, and to my knowledge<br/>&gt; there is no<br/>&gt; party that can assure (on behalf of all ISPs globally) that it will be<br/>&gt; actually accepted.<br/><br/>Hi John,<br/><br/>This is part of the service one buys upon telling an ISP you want a<br/>/24 for multihoming per ARIN NRPM 4.2.3.6. Not a fresh, new or<br/>dangerous concept, nor one that fails to work.<br/><br/>IIRC, there was an effort to prevent this once... ISPs that wouldn&#39;t<br/>accept these /24 BGP announcements from their peers. But that<br/>collapsed as its enforcers realized it was costing them business and<br/>is, today, a historical footnote.<br/><br/>Where the block in question is from a legacy registration, what<br/>contractual or legal obligation prevents the holder from making a<br/>lawful assignment larger than /24, without a multihoming (or any<br/>other) requirement? And in perpetuity?<br/><br/>Regards,<br/>Bill Herrin<br/><br/><br/>-- <br/>William D. Herrin ................ herrin at dirtside.com  bill at herrin.us<br/>3005 Crane Dr. ...................... Web: &lt;http://bill.herrin.us/&gt;<br/>Falls Church, VA 22042-3004<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026958.html">
<title>[arin-ppml] A Redefinition of IPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026958.html</link>
<description>
The community has loudly and recently spoken about which goal of RFC-2050 is universally accepted.
That goal is registration. If you want to continue to maintain the fallacy that the entities which are actually routing and using the addresses as their own, after legally purchasing those rights, are not the ones who should be listed in the Whois registry, then you are standing the goal of registration on its head by simply defining all the entries as accurate, in the same way the authorities responded to Galileo (&#x201C;and yet it moves&#x201D;), by asserting the primacy of words over reality.

Mike -

   You may say &#x22;legally purchasing&#x22; rights, but I truly don&#x27;t know what these parties think
   they purchased, since it can&#x27;t be the ability to inject routes and have them accepted
   (no one can provide that) nor the right to use the entry in the registry, when the
   circumstances are contrary to policy.

   This is not new concept; e.g. you can buy a radio station broadcast license from an
   existing operator, but it&#x27;s not actually a sale until it passes regulatory approvals to be
   reassigned to you.  Until that time, your purchase is without any actual substance.

/John

John Curran
President and CEO
ARIN
</description>
<dc:creator>John Curran</dc:creator>
<dc:date>2013-06-19T13:02:34Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition of IPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[On Jun 19, 2013, at 11:35 AM, Mike Burns &lt;mike at iptrading.com&lt;mailto:mike at iptrading.com&gt;&gt; wrote:<br/><br/>The community has loudly and recently spoken about which goal of RFC-2050 is universally accepted.<br/>That goal is registration. If you want to continue to maintain the fallacy that the entities which are actually routing and using the addresses as their own, after legally purchasing those rights, are not the ones who should be listed in the Whois registry, then you are standing the goal of registration on its head by simply defining all the entries as accurate, in the same way the authorities responded to Galileo (&ldquo;and yet it moves&rdquo;), by asserting the primacy of words over reality.<br/><br/>Mike -<br/><br/>   You may say &quot;legally purchasing&quot; rights, but I truly don&#39;t know what these parties think<br/>   they purchased, since it can&#39;t be the ability to inject routes and have them accepted<br/>   (no one can provide that) nor the right to use the entry in the registry, when the<br/>   circumstances are contrary to policy.<br/><br/>   This is not new concept; e.g. you can buy a radio station broadcast license from an<br/>   existing operator, but it&#39;s not actually a sale until it passes regulatory approvals to be<br/>   reassigned to you.  Until that time, your purchase is without any actual substance.<br/><br/>/John<br/><br/>John Curran<br/>President and CEO<br/>ARIN<br/><br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/e9227cca/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026957.html">
<title>[arin-ppml] Fw: A Redefinition of IPv4NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026957.html</link>
<description>
   You started by indicating that this was an issue with registry accuracy, but the fact is that 
   when the purported sale is contrary to the policy, the registry still accurately reflects the 
   actual party with the rights to the unique registry entry, since the rights only change when [...]</description>
<dc:creator>Mike Burns</dc:creator>
<dc:date>2013-06-19T12:40:19Z</dc:date>
<dc:subject>[arin-ppml] Fw: A Redefinition of IPv4NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[<br/>   You started by indicating that this was an issue with registry accuracy, but the fact is that <br/>   when the purported sale is contrary to the policy, the registry still accurately reflects the <br/>   actual party with the rights to the unique registry entry, since the rights only change when<br/>   done in accordance with policy set by the community.   Whether something is being routed<br/>   on the Internet or not is an entirely different matter, as shown operationally from time to time<br/>   by the various route leaks that occur.<br/><br/>   The registry is accurate as long as it follows the community-developed policy; if you don&#39;t <br/>   like the policy, then work to change it.  Regardless, the registry accurately reflects what<br/>   the community indicates it should under the circumstances.<br/><br/>Thanks,<br/>/John<br/><br/>Hi John,<br/><br/>The community has loudly and recently spoken about which goal of RFC-2050 is universally accepted.<br/>That goal is registration. If you want to continue to maintain the fallacy that the entities which are actually routing and using the addresses as their own, after legally purchasing those rights, are not the ones who should be listed in the Whois registry, then you are standing the goal of registration on its head by simply defining all the entries as accurate, in the same way the authorities responded to Galileo (&ldquo;and yet it moves&rdquo;), by asserting the primacy of words over reality.<br/><br/>Nevermind the propriety of maintaining deliberately false abuse contact information for purposes of maintaining a goal of conservation which was designed in the Free Pool Era and which is not appropriate in a world with a transfer market.<br/>If the needs requirement is driving transactions underground, we are asked here to prioritize goals. I argue that the goal of conservation is lower than the goal of registration, has always been so, and with the advent of a pricing paradigm which naturally supports conservation, it is foolish of stewards to maintain one practice in support of a lesser goal in the face of a negative impact on the primary goal.<br/><br/>Regards,<br/>MIke<br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/82348809/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026956.html">
<title>[arin-ppml] A Redefinition of IPv4 NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026956.html</link>
<description>And yet they route...

Mike -

   You started by indicating that this was an issue with registry accuracy, but the fact is that
   when the purported sale is contrary to the policy, the registry still accurately reflects the
   actual party with the rights to the unique registry entry, since the rights only change when
   done in accordance with policy set by the community.   Whether something is being routed
   on the Internet or not is an entirely different matter, as shown operationally from time to time
   by the various route leaks that occur.

   The registry is accurate as long as it follows the community-developed policy; if you don&#x27;t
   like the policy, then work to change it.  Regardless, the registry accurately reflects what
   the community indicates it should under the circumstances.

Thanks,
/John

John Curran
President and CEO
ARIN

</description>
<dc:creator>John Curran</dc:creator>
<dc:date>2013-06-19T12:07:58Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition of IPv4 NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[On Jun 19, 2013, at 10:48 AM, Mike Burns &lt;mike at nationwideinc.com&lt;mailto:mike at nationwideinc.com&gt;&gt; wrote:<br/>And yet they route...<br/><br/>Mike -<br/><br/>   You started by indicating that this was an issue with registry accuracy, but the fact is that<br/>   when the purported sale is contrary to the policy, the registry still accurately reflects the<br/>   actual party with the rights to the unique registry entry, since the rights only change when<br/>   done in accordance with policy set by the community.   Whether something is being routed<br/>   on the Internet or not is an entirely different matter, as shown operationally from time to time<br/>   by the various route leaks that occur.<br/><br/>   The registry is accurate as long as it follows the community-developed policy; if you don&#39;t<br/>   like the policy, then work to change it.  Regardless, the registry accurately reflects what<br/>   the community indicates it should under the circumstances.<br/><br/>Thanks,<br/>/John<br/><br/>John Curran<br/>President and CEO<br/>ARIN<br/><br/><br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/5b61b18f/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026955.html">
<title>[arin-ppml] A Redefinition of IPv4 NeedpostARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026955.html</link>
<description>Now that&#x27;s quite interesting, given that actually anyone can configure their equipment
to originate routes to any IP address block they wish, and to my knowledge there is no
party that can assure (on behalf of all ISPs globally) that it will be actually accepted. [...]</description>
<dc:creator>Mike Burns</dc:creator>
<dc:date>2013-06-19T11:48:42Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition of IPv4 NeedpostARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[Now that&#39;s quite interesting, given that actually anyone can configure their equipment<br/>to originate routes to any IP address block they wish, and to my knowledge there is no<br/>party that can assure (on behalf of all ISPs globally) that it will be actually accepted.<br/>(You might want to get a very clear warranty with that particular purchase.... :-)<br/><br/>FYI,<br/>/John<br/><br/>Hi John,<br/><br/>And yet they route...<br/><br/>FYI,<br/>Mike<br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/1cfe7b02/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026954.html">
<title>[arin-ppml] A Redefinition of IPv4 Need postARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026954.html</link>
<description>
Hi John,

Sometimes Buyers buy the listing in the ARIN database- that&#x27;s a policy-based sale.

It&#x27;s actually rights of use to the unique entry in the single global Internet registry,
which happens to be implemented collectively (and hierarchically) by IANA, the
RIRs, the ISPs/LIRs, etc. [...]</description>
<dc:creator>John Curran</dc:creator>
<dc:date>2013-06-19T11:32:08Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition of IPv4 Need postARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[On Jun 19, 2013, at 8:12 AM, Mike Burns &lt;mike at nationwideinc.com&lt;mailto:mike at nationwideinc.com&gt;&gt; wrote:<br/><br/>Hi John,<br/><br/>Sometimes Buyers buy the listing in the ARIN database- that&#39;s a policy-based sale.<br/><br/>It&#39;s actually rights of use to the unique entry in the single global Internet registry,<br/>which happens to be implemented collectively (and hierarchically) by IANA, the<br/>RIRs, the ISPs/LIRs, etc.  The community also has rights to those same entries,<br/>which are distinct but just as real and a requirement for actual self-governance.<br/>Refer to the number resource policy regarding how these rights interact.<br/><br/>Sometimes they buy the ability to route and use the (legacy) addresses without changing that line in the Whois database.<br/><br/>Now that&#39;s quite interesting, given that actually anyone can configure their equipment<br/>to originate routes to any IP address block they wish, and to my knowledge there is no<br/>party that can assure (on behalf of all ISPs globally) that it will be actually accepted.<br/>(You might want to get a very clear warranty with that particular purchase.... :-)<br/><br/>FYI,<br/>/John<br/><br/>John Curran<br/>President and CEO<br/>ARIN<br/><br/><br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/a9955cd8/attachment.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026953.html">
<title>[arin-ppml] A Redefinition of IPv4 Need post ARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026953.html</link>
<description>You began this discussion some time ago with a policy proposal which attempted to remove needs basis, was soundly rejected by the community, and which you backed off to the same compromise you are again proposing now. The community didn&#x27;t want any part of it back then. [...]</description>
<dc:creator>Mike Burns</dc:creator>
<dc:date>2013-06-19T10:04:54Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition of IPv4 Need post ARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[You began this discussion some time ago with a policy proposal which attempted to remove needs basis, was soundly rejected by the community, and which you backed off to the same compromise you are again proposing now. The community didn&#39;t want any part of it back then. At the time, there was no interest in continuing the discussion and the proposal was abandoned. <br/>Hi Owen,<br/>Just to be accurate, my proposal was never abandoned and is in fact section 8.3 of the NRPM.<br/>Although mostly a rewording of the original 8.3, it did originally call for removing the needs test for transfers but added a 12 month exclusion period between the free pool and the transfer pool, whose purpose was to protect the free pool from those who would repeatedly sell their allocations just to get another from ARIN.<br/>This was my attempt to reconcile the existence of a profit motive in transfers that should not be present for free pool addresses.  In the end I reluctantly removed any limit on needs testing from my policy so that it could be passed in conjunction with the Inter-regional transfer policy, which otherwise would have exposed the ARIN free pool to the aforementioned sell, repeat cycle.<br/>So I dropped the needs test exclusion in favor of opening the global transfer market, not because I came to the realization that I was tilting at windmills with the ARIN policy development community. <br/>Regards,<br/>Mike<br/> <br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;http://lists.arin.net/pipermail/arin-ppml/attachments/20130619/0f36a51d/attachment-0001.html&gt;<br/>]]></content:encoded>
</item>
<item rdf:about="http://lists.arin.net/pipermail/arin-ppml/2013-June/026952.html">
<title>[arin-ppml] A Redefinition of IPv4 Need post ARINrun-out(was:Re:Against2013-4)</title>
<link>http://lists.arin.net/pipermail/arin-ppml/2013-June/026952.html</link>
<description>
[...]

Of course the incumbent&#x27;s assets offer a competitive advantage over
the challenger. With such a prima facie case, the burden rests on who
disagree to disprove it.

What&#x27;s less obvious is:

1. Is this unreasonable?

2. How do ARIN&#x27;s policies interact with this otherwise natural state [...]</description>
<dc:creator>William Herrin</dc:creator>
<dc:date>2013-06-19T09:25:20Z</dc:date>
<dc:subject>[arin-ppml] A Redefinition of IPv4 Need post ARINrun-out(was:Re:Against2013-4)</dc:subject>
<content:encoded><![CDATA[On Tue, Jun 18, 2013 at 4:14 PM, Owen DeLong &lt;owen at delong.com&gt; wrote:<br/>&gt; On Jun 18, 2013, at 7:14 PM, Mike Burns &lt;mike at nationwideinc.com&gt; wrote:<br/>&gt;&gt; 1. It has been argued that the larger ISPs have the prior advantage of<br/>&gt;&gt; holding highly valuable alienable assets which they received for free, which<br/>&gt;&gt; provide them with a competitive advantage over less endowed entities seeking<br/>&gt;&gt; to purchase addresses at a much higher relative price.<br/>&gt;<br/>&gt; Yes, it has been argued. It hasn&#39;t necessarily been substantiated, nor has<br/>&gt; anyone raising said argument provided any real evidence to support it.<br/><br/>Of course the incumbent&#39;s assets offer a competitive advantage over<br/>the challenger. With such a prima facie case, the burden rests on who<br/>disagree to disprove it.<br/><br/>What&#39;s less obvious is:<br/><br/>1. Is this unreasonable?<br/><br/>2. How do ARIN&#39;s policies interact with this otherwise natural state<br/>of affairs? Favorable/neutral/disfavorable to the<br/>incumbent/challenger?<br/><br/>3. Is that unreasonable?<br/><br/><br/>&gt;&gt; Remember the cap on needs-free transfers is designed to free up the market<br/>&gt;&gt; to incentivize more transactions, each of which presumably entails the move<br/>&gt;&gt; of addresses from lower-use states to higher-use states, while providing<br/>&gt;&gt; some protection for market manipulations.<br/><br/>I think I would cautiously favor an experiment in this realm:<br/><br/>* Limit needs-free transfers to receiving one transfer of /20 or less<br/>per year per organization,<br/><br/>* Keep the needs analysis for free pool assignments with a presumption<br/>that a quick transfer out indicates fraud in the original<br/>registration,<br/><br/>* Include a strong publication requirement. Originator and recipient<br/>to be explicitly and publicly called out by ARIN with full details so<br/>that anyone can monitor the status of the experiment.<br/><br/>* We don&#39;t consider expansion from /20 until at least 200 such<br/>transfers go through so that we can work with real data when<br/>predicting the efficacy of an expanded policy.<br/><br/><br/>Regards,<br/>Bill Herrin<br/><br/><br/><br/>-- <br/>William D. Herrin ................ herrin at dirtside.com  bill at herrin.us<br/>3005 Crane Dr. ...................... Web: &lt;http://bill.herrin.us/&gt;<br/>Falls Church, VA 22042-3004<br/>]]></content:encoded>
</item>
</rdf:RDF>