<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div style="-webkit-text-size-adjust: auto;"><br></div><div style="-webkit-text-size-adjust: auto;">On Apr 3, 2014, at 8:04 PM, Rocky <<a href="mailto:rockymm8@gmail.com">rockymm8@gmail.com</a>> wrote:<br><br></div><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><div>
<div><p style="margin: 0px; font-size: 12px;">Scott</p>
<p style="margin: 0px; min-height: 16px;"><br></p>
<p style="margin: 0px;">thanks for your explanation. </p>
<p style="margin: 0px;">1. how can ARIN make sure this 8.2 transfer is not speculating about IPv4?</p></div></div></blockquote><div style="-webkit-text-size-adjust: auto;"><br></div><span style="-webkit-text-size-adjust: auto;">If you can clarify what you mean by speculating in this particular case, we can discuss the various aspects of policy that may help. Or, see below. </span><div style="-webkit-text-size-adjust: auto;"><br><blockquote type="cite"><div><div>
<p style="margin: 0px;">2. if the entity no longer existent, why not return the IPv4 after its dissolved?</p></div></div></blockquote><div><br></div>That would be ideal, and has happened in the past. Now that the IPv4 free pool is nearing exhaustion, though, most successors to companies with IPv4 holdings would prefer to monetize them. The end result to the community (those of us not involved in the transaction) is the same: the addresses get back into use. </div><div><br><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><div><div><p style="margin: 0px;"> or why not update the ARIN database in time after the M/A.</p></div></div></blockquote><div style="-webkit-text-size-adjust: auto;"><br></div><div style="-webkit-text-size-adjust: auto;">Again, that would've been ideal, but in many cases did not happen. Updating records takes work, so unless there's some incentive (like being able to transfer the resources under 8.3) it sometimes gets overlooked or not prioritized. </div><br><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><div><div><p style="margin: 0px;">What you are trying to say make me feel that ARIN policy is encouraging the stockpile of IPv4— some People do it until the IPv4 becomes expensive and some people can benefit huge from its stockpile ( for past many years) by update its registration info via 8.2 transfer to sell a great price after the next 8.3 transfer.</p></div></div></blockquote><div style="-webkit-text-size-adjust: auto;"><br></div><div style="-webkit-text-size-adjust: auto;">Generally, ARIN policy seeks to prevent that on the front end, by requiring justified need for allocations from the free pool. There is also policy in place to prevent "flipping" space after an allocation. </div><br><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><div><div>
<p style="margin: 0px;">the check of utilisation rate under 8.2 is just a formalism and considering the wording there conflicts with RSA, why not delete the utilisation rate requirement in the 8.2? or revise the RSA accordingly.</p></div></div></blockquote><div style="-webkit-text-size-adjust: auto;"><br></div><div><span style="-webkit-text-size-adjust: auto;">The original intent of this language was to encourage ARIN to work with the recipient of the 8.2 transfer to get all the addresses into use. Since the RSA now prevents reclamation, that should probably be removed from the policy, as should "aggregate". But the "</span><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">ARIN will work with the resource holder(s) to return or transfer resources as needed" language would still be operative if we left it in place. </span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">-Scott</span></div><div><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></div><blockquote type="cite" style="-webkit-text-size-adjust: auto;"><div>
<p style="margin: 0px; min-height: 16px;"><br></p></div><div><br></div><div><span style="color: rgb(160, 160, 168);"><br></span></div><div><span style="color: rgb(160, 160, 168);"><br></span></div><div><span style="color: rgb(160, 160, 168);">On Friday, April 4, 2014 at 9:25 AM, <a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a> wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>Send ARIN-PPML mailing list submissions to</div><div> <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></div><div><br></div><div>To subscribe or unsubscribe via the World Wide Web, visit</div><div> <a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></div><div>or, via email, send a message with subject or body 'help' to</div><div> <a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a></div><div><br></div><div>You can reach the person managing the list at</div><div> <a href="mailto:arin-ppml-owner@arin.net">arin-ppml-owner@arin.net</a></div><div><br></div><div>When replying, please edit your Subject line so it is more specific</div><div>than "Re: Contents of ARIN-PPML digest..."</div><div><br></div><div><br></div><div>Today's Topics:</div><div><br></div><div> 1. Re: ARIN-PPML Digest, Vol 106, Issue 8 (Scott Leibrand)</div><div><br></div><div><br></div><div>----------------------------------------------------------------------</div><div><br></div><div>Message: 1</div><div>Date: Thu, 3 Apr 2014 18:25:06 -0700</div><div>From: Scott Leibrand <<a href="mailto:scottleibrand@gmail.com">scottleibrand@gmail.com</a>></div><div>To: Rocky <<a href="mailto:rockymm8@gmail.com">rockymm8@gmail.com</a>></div><div>Cc: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>></div><div>Subject: Re: [arin-ppml] ARIN-PPML Digest, Vol 106, Issue 8</div><div>Message-ID: <<a href="mailto:04DC25C4-5352-4DC8-A114-EA1724DC88EE@gmail.com">04DC25C4-5352-4DC8-A114-EA1724DC88EE@gmail.com</a>></div><div>Content-Type: text/plain; charset="utf-8"</div><div><br></div><div>Rocky,</div><div><br></div><div>Many such 8.2 transfers are efforts to get ARIN's records up to date regarding M&A transactions that happened years ago. It is not possible for a no-longer-existent entity to execute the 8.3 transfer, so it has to be 8.2 transferred to the new entity first. </div><div><br></div><div>Scott</div><div><br></div><blockquote type="cite"><div><div>On Apr 3, 2014, at 6:02 PM, Rocky <<a href="mailto:rockymm8@gmail.com">rockymm8@gmail.com</a>> wrote:</div><div><br></div><div>Hello there,</div><div><br></div><div>What you are planning to do seems like you try to disguise an 8.3 transfer as an 8.2 transfer. </div><div>I do not think it is appropriate for allowing an 8.2 transfer followed by an 8.3/8.4 transfer. </div><div><br></div><div>If the company does not need the IPv4 and the IPv4 are lack of utilisation, why not ask this company to return the IPv4 for the benefit of the community?</div><div><br></div><div>If the company wants to sell the IPv4 after an 8.2 to buyers through an 8.3/8.4, why not the company directly transfer the IPv4 from its original organisation instead of doing an 8.2 first then followed by an 8.3/8.4 transfer. Are the seller trying to hide something or as the seller is afraid of doing something against the policy, so they try to make such an arrangement?</div><div><br></div><div>There is a highly suspicious of ? IPv4 laundry? or ?IPv4 speculation? about this company. Maybe we need more transparency of the buy&sale of the IPv4 to make sure the behaviour of the seller is compatible with policy. </div><div><br></div><div>I suggest to resolve the language conflict between 8.2 transfer policy and RSA and further to suggest to figure out some measures to stop the speculation on IPv4 via an 8.2 then followed by an 8.3/8.4 transfer. If the company does not use the IPv4 after an 8.2 transfer, why not return them to free pool for the benefit of the whole community?</div><div><br></div><div>Any ideas on this ?</div><div><br></div><div><br></div><blockquote type="cite"><div><div>On Friday, April 4, 2014 at 7:43 AM, <a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a> wrote:</div><div><br></div><div>Send ARIN-PPML mailing list submissions to</div><div><a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></div><div><br></div><div>To subscribe or unsubscribe via the World Wide Web, visit</div><div><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></div><div>or, via email, send a message with subject or body 'help' to</div><div><a href="mailto:arin-ppml-request@arin.net">arin-ppml-request@arin.net</a></div><div><br></div><div>You can reach the person managing the list at</div><div><a href="mailto:arin-ppml-owner@arin.net">arin-ppml-owner@arin.net</a></div><div><br></div><div>When replying, please edit your Subject line so it is more specific</div><div>than "Re: Contents of ARIN-PPML digest..."</div><div><br></div><div><br></div><div>Today's Topics:</div><div><br></div><div>1. Re: ARIN-PPML Digest, Vol 106, Issue 7 (Chris R. Squatritto)</div><div>2. Re: Draft Policy ARIN-2014-9: Resolve Conflict Between RSA</div><div>and 8.2 Utilization Requirements (John Curran)</div><div>3. Re: Draft Policy ARIN-2014-9: Resolve Conflict Between RSA</div><div>and 8.2 Utilization Requirements (Milton L Mueller)</div><div>4. Re: Draft Policy ARIN-2014-9: Resolve Conflict Between RSA</div><div>and 8.2 Utilization Requirements (xiaofan yang)</div><div>5. Re: Draft Policy ARIN-2014-9: Resolve Conflict Between RSA</div><div>and 8.2 Utilization Requirements (xiaofan yang)</div><div><br></div><div><br></div><div>----------------------------------------------------------------------</div><div><br></div><div>Message: 1</div><div>Date: Wed, 02 Apr 2014 16:30:45 -0700</div><div>From: "Chris R. Squatritto" <<a href="mailto:csquat@ccsd.net">csquat@ccsd.net</a>></div><div>To: <a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a></div><div>Subject: Re: [arin-ppml] ARIN-PPML Digest, Vol 106, Issue 7</div><div>Message-ID:</div><div><<a href="mailto:fc.004c4e074f3bba733b9aca00e3f873db.4f3bba74@interact.ccsd.net">fc.004c4e074f3bba733b9aca00e3f873db.4f3bba74@interact.ccsd.net</a>></div><div>Content-Type: text/plain; charset="utf-8"</div><div><br></div><div>I am out of the office this week and will not be checking email. Please</div><div>contact Troy Miller for assistance..</div><div><br></div><div>Thank you for contacting me, and have a great day.</div><div><br></div><div>-------------- next part --------------</div><div>An HTML attachment was scrubbed...</div><div>URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20140402/5723c721/attachment-0001.html">http://lists.arin.net/pipermail/arin-ppml/attachments/20140402/5723c721/attachment-0001.html</a>></div><div><br></div><div>------------------------------</div><div><br></div><div>Message: 2</div><div>Date: Wed, 2 Apr 2014 23:59:20 +0000</div><div>From: John Curran <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>></div><div>To: xiaofan yang <<a href="mailto:nikiyangxf@gmail.com">nikiyangxf@gmail.com</a>></div><div>Cc: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>></div><div>Subject: Re: [arin-ppml] Draft Policy ARIN-2014-9: Resolve Conflict</div><div>Between RSA and 8.2 Utilization Requirements</div><div>Message-ID: <<a href="mailto:6BBC9339-AE30-446A-8406-8237A8C3477F@arin.net">6BBC9339-AE30-446A-8406-8237A8C3477F@arin.net</a>></div><div>Content-Type: text/plain; charset="iso-8859-1"</div><div><br></div><blockquote type="cite"><div><div>On Apr 2, 2014, at 4:27 PM, xiaofan yang <<a href="mailto:nikiyangxf@gmail.com">nikiyangxf@gmail.com</a>> wrote:</div><div><br></div><div>Hi John,</div><div><br></div><div>I have further enquiry about ARIN 8.2 process.</div><div><br></div><div>Number one:I am also worried about the costs of doing a 8.2 transfer followed by a 8.3 transfer. I wonder if I will have to involve the legal help to deal with ARIN legal. In my case I bought a company that now is out of business. How complicated does ARIN make this process? I want some assurance that I will be treated equally to any other companies whether it is a big company or a small company like us.</div></div></blockquote><div><br></div><div>Niki -</div><div><br></div><div>You will be treated equally, but in truth I'm not certain that is actually what you want...</div><div>(for example, a process which seems routine for a large organization could still pose</div><div>a disproportionate burden to a smaller organization since organization size is not a</div><div>factor in the verification process.)</div><div><br></div><div>The first and foremost activity is to make sure that we have your organization registered</div><div>as the rightful address holder, and that will require an NRPM 8.2 transfer. It can actually</div><div>be relatively straightforward process, as long as you have clear documentation of the</div><div>purchase of the company. Review the instructions here for additional information about</div><div>what is accepted - <<a href="https://www.arin.net/resources/request/transfers_8_2.html">https://www.arin.net/resources/request/transfers_8_2.html</a>></div><div><br></div><blockquote type="cite"><div>Number two: If we do a 8.2 transfer followed by a 8.3 transfer, will the stated purpose for our number resources remains the same?? I am afraid of that ARIN will not approve our transfer.</div></blockquote><div><br></div><div>If you are the clear party with the rights after your purchase, ARIN will approve your</div><div>transfer. We may note that you have more addresses than you now need, and thus</div><div>we expect you to return or transfer the remainder (but that would seem to line up with</div><div>your intentions in any case.)</div><div><br></div><div>If you have purchased a company without adequate documentation, or if multiple</div><div>parties purchased multiple pieces of the company, or if there some question about</div><div>what was purchased based on the documentation, then it can be more challenging</div><div>to get the resources appropriately listed with you as the rightful holder. You will need</div><div>to apply for the transfer and work with the ARIN Hostmaster to determine if there is</div><div>any issue in your particular case.</div><div><br></div><blockquote type="cite"><div>Number three: As we have bought the company, do we have the property right on those IPs? in our past agreement and future agreement arranged for 8.3, we would like to have some kinds of property right on those IPs, will that conflict with ARIN policy?</div></blockquote><div><br></div><div>Wonderful question - it is ARIN's position that you have a specific set of rights to the</div><div>address blocks in the registry (as defined by the registration services agreement that</div><div>you enter with ARIN), and these rights include:</div><div><br></div><div>(1) The exclusive right to be the registrant of the Included Number Resources within the ARIN database;</div><div>(2) The right to use the Included Number Resources within the ARIN database; and</div><div>(3) The right to transfer the registration of the Included Number Resources pursuant to the Policies.</div><div><br></div><div>ARIN registration services agreement includes a specific disclaimer of property rights</div><div>in the address blocks, as it is inconsistent with the ability to manage the address blocks</div><div>in accordance with community-developed policy in the region. If you have other beliefs</div><div>with respect to your rights, that would probably be an area for you to seek legal advice.</div><div><br></div><div>I hope this helps; please do not hesitate to ask if you have any additional questions.</div><div><br></div><div>Thanks!</div><div>/John</div><div><br></div><div>John Curran</div><div>President and CEO</div><div>ARIN</div><div><br></div><div><br></div><div><br></div><div>------------------------------</div><div><br></div><div>Message: 3</div><div>Date: Thu, 3 Apr 2014 15:33:13 +0000</div><div>From: Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>></div><div>To: "'John Curran'" <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>>, xiaofan yang</div><div><<a href="mailto:nikiyangxf@gmail.com">nikiyangxf@gmail.com</a>></div><div>Cc: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>></div><div>Subject: Re: [arin-ppml] Draft Policy ARIN-2014-9: Resolve Conflict</div><div>Between RSA and 8.2 Utilization Requirements</div><div>Message-ID: <<a href="mailto:1846d87fe7164f22a7c63e9d1fed321e@EX13-MBX-13.ad.syr.edu">1846d87fe7164f22a7c63e9d1fed321e@EX13-MBX-13.ad.syr.edu</a>></div><div>Content-Type: text/plain; charset="us-ascii"</div><div><br></div><div>Niki:</div><div>For most economists and lawyers, the definition of a "property right" involves the right to use, the right to exclude others from using, and the right to transfer. As John's message makes clear, all those rights are present in the number block lease you get from ARIN. So although the RSA makes you formally declaim a property right, what you are getting from the RSA is a bundle of rights that for all practical purposes has the same economic features as a property right.</div><div><br></div><div>-----Original Message-----</div><div><br></div><div>Wonderful question - it is ARIN's position that you have a specific set of rights to the address blocks in the registry (as defined by the registration services agreement that you enter with ARIN), and these rights include:</div><div><br></div><div>(1) The exclusive right to be the registrant of the Included Number Resources within the ARIN database;</div><div>(2) The right to use the Included Number Resources within the ARIN database; and</div><div>(3) The right to transfer the registration of the Included Number Resources pursuant to the Policies.</div><div><br></div><div>ARIN registration services agreement includes a specific disclaimer of property rights in the address blocks, as it is inconsistent with the ability to manage the address blocks in accordance with community-developed policy in the region. If you have other beliefs with respect to your rights, that would probably be an area for you to seek legal advice.</div><div><br></div><div>I hope this helps; please do not hesitate to ask if you have any additional questions.</div><div><br></div><div>Thanks!</div><div>/John</div><div><br></div><div>John Curran</div><div>President and CEO</div><div>ARIN</div><div><br></div><div>_______________________________________________</div><div>PPML</div><div>You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</div><div>Unsubscribe or manage your mailing list subscription at:</div><div><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></div><div>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</div><div><br></div><div><br></div><div>------------------------------</div><div><br></div><div>Message: 4</div><div>Date: Fri, 4 Apr 2014 07:33:04 +0800</div><div>From: xiaofan yang <<a href="mailto:nikiyangxf@gmail.com">nikiyangxf@gmail.com</a>></div><div>To: John Curran <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>></div><div>Cc: "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>" <<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>></div><div>Subject: Re: [arin-ppml] Draft Policy ARIN-2014-9: Resolve Conflict</div><div>Between RSA and 8.2 Utilization Requirements</div><div>Message-ID:</div><div><<a href="mailto:CAPhL6MpzKW1q2Cw9+SfZ+hap6ecwns6JzdBEp+xvK8dF7VMwxg@mail.gmail.com">CAPhL6MpzKW1q2Cw9+SfZ+hap6ecwns6JzdBEp+xvK8dF7VMwxg@mail.gmail.com</a>></div><div>Content-Type: text/plain; charset="iso-8859-1"</div><div><br></div><div>Hi John,</div><div><br></div><div><br></div><div>In basis of your reply, if the block is underutilised,ARIN will either ask</div><div>the company to return the IPs or transfer to other third party via 8.3</div><div>transfer after our 8.2 transfer.</div><div><br></div><div><br></div><div>Say we have two /16 after this 8.2 transfer, what if we only transfer one</div><div>/16 to the other third party via 8.3 transfer, meanwhile, we keep the</div><div>other /16 left unused after our 8.2 transfer for quiet a while. Will ARIN</div><div>ask us to return the remained /16 to the free pool? furthmore, how long</div><div>will ARIN allow us to keep the other /16 unused before we transfer it to</div><div>the third party via 8.3 transfer ?</div><div><br></div><div><br></div><div><br></div><div>Niki</div><div><br></div><div><br></div><div><br></div><div><br></div><blockquote type="cite"><div><div>On Thu, Apr 3, 2014 at 7:59 AM, John Curran <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>> wrote:</div><div><br></div><blockquote type="cite"><div><div>On Apr 2, 2014, at 4:27 PM, xiaofan yang <<a href="mailto:nikiyangxf@gmail.com">nikiyangxf@gmail.com</a>> wrote:</div><div><br></div><div>Hi John,</div><div><br></div><div>I have further enquiry about ARIN 8.2 process.</div><div><br></div><div>Number one:I am also worried about the costs of doing a 8.2 transfer</div></div></blockquote><div>followed by a 8.3 transfer. I wonder if I will have to involve the legal</div><div>help to deal with ARIN legal. In my case I bought a company that now is</div><div>out of business. How complicated does ARIN make this process? I want some</div><div>assurance that I will be treated equally to any other companies whether it</div><div>is a big company or a small company like us.</div><div><br></div><div>Niki -</div><div><br></div><div>You will be treated equally, but in truth I'm not certain that is actually</div><div>what you want...</div><div>(for example, a process which seems routine for a large organization could</div><div>still pose</div><div>a disproportionate burden to a smaller organization since organization</div><div>size is not a</div><div>factor in the verification process.)</div><div><br></div><div>The first and foremost activity is to make sure that we have your</div><div>organization registered</div><div>as the rightful address holder, and that will require an NRPM 8.2</div><div>transfer. It can actually</div><div>be relatively straightforward process, as long as you have clear</div><div>documentation of the</div><div>purchase of the company. Review the instructions here for additional</div><div>information about</div><div>what is accepted - <</div><div><a href="https://www.arin.net/resources/request/transfers_8_2.html">https://www.arin.net/resources/request/transfers_8_2.html</a>></div><div><br></div><blockquote type="cite"><div>Number two: If we do a 8.2 transfer followed by a 8.3 transfer, will</div></blockquote><div>the stated purpose for our number resources remains the same?? I am afraid</div><div>of that ARIN will not approve our transfer.</div><div><br></div><div>If you are the clear party with the rights after your purchase, ARIN will</div><div>approve your</div><div>transfer. We may note that you have more addresses than you now need, and</div><div>thus</div><div>we expect you to return or transfer the remainder (but that would seem to</div><div>line up with</div><div>your intentions in any case.)</div><div><br></div><div>If you have purchased a company without adequate documentation, or if</div><div>multiple</div><div>parties purchased multiple pieces of the company, or if there some</div><div>question about</div><div>what was purchased based on the documentation, then it can be more</div><div>challenging</div><div>to get the resources appropriately listed with you as the rightful holder.</div><div>You will need</div><div>to apply for the transfer and work with the ARIN Hostmaster to determine</div><div>if there is</div><div>any issue in your particular case.</div><div><br></div><blockquote type="cite"><div>Number three: As we have bought the company, do we have the property</div></blockquote><div>right on those IPs? in our past agreement and future agreement arranged</div><div>for 8.3, we would like to have some kinds of property right on those IPs,</div><div>will that conflict with ARIN policy?</div><div><br></div><div>Wonderful question - it is ARIN's position that you have a specific set of</div><div>rights to the</div><div>address blocks in the registry (as defined by the registration services</div><div>agreement that</div><div>you enter with ARIN), and these rights include:</div><div><br></div><div>(1) The exclusive right to be the registrant of the Included Number</div><div>Resources within the ARIN database;</div><div>(2) The right to use the Included Number Resources within the ARIN</div><div>database; and</div><div>(3) The right to transfer the registration of the Included Number</div><div>Resources pursuant to the Policies.</div><div><br></div><div>ARIN registration services agreement includes a specific disclaimer of</div><div>property rights</div><div>in the address blocks, as it is inconsistent with the ability to manage</div><div>the address blocks</div><div>in accordance with community-developed policy in the region. If you have</div><div>other beliefs</div><div>with respect to your rights, that would probably be an area for you to</div><div>seek legal advice.</div><div><br></div><div>I hope this helps; please do not hesitate to ask if you have any</div><div>additional questions.</div><div><br></div><div>Thanks!</div><div>/John</div><div><br></div><div>John Curran</div><div>President and CEO</div><div>ARIN</div></div></blockquote><div>-------------- next part --------------</div><div>An HTML attachment was scrubbed...</div><div>URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20140404/fd4aa749/attachment-0001.html">http://lists.arin.net/pipermail/arin-ppml/attachments/20140404/fd4aa749/attachment-0001.html</a>></div><div><br></div><div>------------------------------</div><div><br></div><div>Message: 5</div><div>Date: Fri, 4 Apr 2014 07:43:43 +0800</div><div>From: xiaofan yang <<a href="mailto:nikiyangxf@gmail.com">nikiyangxf@gmail.com</a>></div><div>To: Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>></div><div>Cc: John Curran <<a href="mailto:jcurran@arin.net">jcurran@arin.net</a>>, "<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>"</div><div><<a href="mailto:arin-ppml@arin.net">arin-ppml@arin.net</a>></div><div>Subject: Re: [arin-ppml] Draft Policy ARIN-2014-9: Resolve Conflict</div><div>Between RSA and 8.2 Utilization Requirements</div><div>Message-ID:</div><div><CAPhL6MrQdn-=<a href="mailto:5g8ZKSntVpVca7pRrwuWLxCAiTrgv2d672wX3A@mail.gmail.com">5g8ZKSntVpVca7pRrwuWLxCAiTrgv2d672wX3A@mail.gmail.com</a>></div><div>Content-Type: text/plain; charset="iso-8859-1"</div><div><br></div><div>Hi Milton,</div><div><br></div><div>thanks for your inspiring reply. Now i know that we have the "ownership"</div><div>of those IPs. as you are one of the AC, i take your reply seriously and</div><div>also this is good news for the community, especially for those legacy</div><div>holders, if the holder of ARIN non-legacy IPs can have the "ownership'</div><div>then the holder of legacy IPs definitely has the ownership on their IPs</div><div>no matter whether they sign the RSA , LRSA or not.</div><div><br></div><div>Hope ARIN will not impose unpredictable "restrictions" when legacy or</div><div>non-legacy holder begins its transfer request. Moreover, when ARIN reject</div><div>a transfer , hope ARIN will not use the "confidential terms" as an excuse</div><div>for not reply communities' questions in ppml. or ARIN will reply with</div><div>bunch of info mean nothing.</div><div>Niki</div><div><br></div><div><br></div><blockquote type="cite"><div><div>On Thu, Apr 3, 2014 at 11:33 PM, Milton L Mueller <<a href="mailto:mueller@syr.edu">mueller@syr.edu</a>> wrote:</div><div><br></div><div>Niki:</div><div>For most economists and lawyers, the definition of a "property right"</div><div>involves the right to use, the right to exclude others from using, and the</div><div>right to transfer. As John's message makes clear, all those rights are</div><div>present in the number block lease you get from ARIN. So although the RSA</div><div>makes you formally declaim a property right, what you are getting from the</div><div>RSA is a bundle of rights that for all practical purposes has the same</div><div>economic features as a property right.</div><div><br></div><div>-----Original Message-----</div><div><br></div><div>Wonderful question - it is ARIN's position that you have a specific set of</div><div>rights to the address blocks in the registry (as defined by the</div><div>registration services agreement that you enter with ARIN), and these rights</div><div>include:</div><div><br></div><div>(1) The exclusive right to be the registrant of the Included Number</div><div>Resources within the ARIN database;</div><div>(2) The right to use the Included Number Resources within the ARIN</div><div>database; and</div><div>(3) The right to transfer the registration of the Included Number</div><div>Resources pursuant to the Policies.</div><div><br></div><div>ARIN registration services agreement includes a specific disclaimer of</div><div>property rights in the address blocks, as it is inconsistent with the</div><div>ability to manage the address blocks in accordance with community-developed</div><div>policy in the region. If you have other beliefs with respect to your</div><div>rights, that would probably be an area for you to seek legal advice.</div><div><br></div><div>I hope this helps; please do not hesitate to ask if you have any</div><div>additional questions.</div><div><br></div><div>Thanks!</div><div>/John</div><div><br></div><div>John Curran</div><div>President and CEO</div><div>ARIN</div><div><br></div><div>_______________________________________________</div><div>PPML</div><div>You are receiving this message because you are subscribed to the ARIN</div><div>Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</div><div>Unsubscribe or manage your mailing list subscription at:</div><div><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></div><div>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</div></div></blockquote><div>-------------- next part --------------</div><div>An HTML attachment was scrubbed...</div><div>URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20140404/57c3a01e/attachment.html">http://lists.arin.net/pipermail/arin-ppml/attachments/20140404/57c3a01e/attachment.html</a>></div><div><br></div><div>------------------------------</div><div><br></div><div>_______________________________________________</div><div>ARIN-PPML mailing list</div><div><a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a></div><div><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></div><div><br></div><div>End of ARIN-PPML Digest, Vol 106, Issue 8</div><div>*****************************************</div></div></blockquote><div><br></div><div>_______________________________________________</div><div>PPML</div><div>You are receiving this message because you are subscribed to</div><div>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).</div><div>Unsubscribe or manage your mailing list subscription at:</div><div><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></div><div>Please contact <a href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</div></div></blockquote><div>-------------- next part --------------</div><div>An HTML attachment was scrubbed...</div><div>URL: <<a href="http://lists.arin.net/pipermail/arin-ppml/attachments/20140403/86ab1c8b/attachment.html">http://lists.arin.net/pipermail/arin-ppml/attachments/20140403/86ab1c8b/attachment.html</a>></div><div><br></div><div>------------------------------</div><div><br></div><div>_______________________________________________</div><div>ARIN-PPML mailing list</div><div><a href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a></div><div><a href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a></div><div><br></div><div>End of ARIN-PPML Digest, Vol 106, Issue 10</div><div>******************************************</div></div></div></span>
</blockquote>
<div>
<br>
</div>
</blockquote></div></body></html>