<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Opposed as written.<div><br></div><div>Removal of the needs test from section 8.2 is contrary to the interests of the community.</div><div><br></div><div>I do like the provision offered in 8.2 subparagraph 3, but I see no reason to use LRSA there instead of RSA.</div><div><br></div><div>I do not like placing the dependency on the current text of 172 as that definition is fundamentally flawed and the tremendous opposition to that proposal expressed by the community to date leads me to believe that said definition is unlikely to become policy.</div><div><br></div><div>I would suggest, instead, that the proposal be modified as follows:</div><div><br></div><div>Unless a definition of legacy resource has already been added to section 2, the following shall be added to section 2:</div><div><br></div><div>[insert your chosen definition of legacy resource here]</div><div><br></div><div>As to the rationale...</div><div>Merely notifying ARIN does not put their ability to retain and use the resources at risk. Transferring them outside of ARIN policy places them at risk. Notifying ARIN merly calls ARIN's attention to the fact, which is, admittedly increasing the risk. However, I still do not buy the theory that just because people might rob banks, we should make bank robbery legal. Just because people might transfer outside of ARIN policy and fail to record those transfers with ARIN does not mean that we should modify our policy to permit such transfers.</div><div><br></div><div>Owen</div><div><br></div><div><div><div>On Jun 14, 2012, at 3:01 PM, Lindsey, Marc wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Policy Proposal Name</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><span class="Apple-converted-space"> </span>– Revisions to M&A Transfer Requirements<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Proposal Originator</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><span class="Apple-converted-space"> </span>– Marc Lindsey<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Proposal Version</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><span class="Apple-converted-space"> </span>- 1<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Date</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><span class="Apple-converted-space"> </span>– June 14, 2012<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Policy type</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><span class="Apple-converted-space"> </span>– Modification to existing policy<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Policy term</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><span class="Apple-converted-space"> </span>- Permanent<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Policy Statement</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><o:p></o:p></span></div><h4 style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; font-weight: bold; "><span style="font-family: Arial, sans-serif; font-weight: normal; ">Delete sections 8.1. and 8.2 in their entirety and replace them with the following:<o:p></o:p></span></h4><p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; "><b><span style="font-family: Arial, sans-serif; ">8.1 Principles<o:p></o:p></span></b></p><p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-family: Arial, sans-serif; ">ARIN will not change its WHOIS database to record the transfer of number resources between organizations unless such transfer complies with this Section 8. ARIN is tasked with making prudent decisions when evaluating registration transfer requests.<o:p></o:p></span></p><h4 style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; font-weight: bold; "><a name="eight2"></a><span style="font-family: Arial, sans-serif; ">8.2. Mergers and Acquisitions<o:p></o:p></span></h4><p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-family: Arial, sans-serif; ">When the transfer of any number resource is requested by the current registrant or its successor or assign (the “new entity”), ARIN will transfer the registration of such number resources to the new entity upon receipt of evidence that the new entity has lawfully acquired the resources from the current registrant as the result of a merger, acquisition, reorganization or name change. ARIN will maintain an up-to-date list of acceptable types of documentation. Transfers under this Section 8.2 shall not be contingent upon the new entity’s justification of need for the transferred numbers. <o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-family: Arial, sans-serif; ">If the transfer request pertains to non-legacy number resources, the new entity shall be required to execute, in its own name, an RSA covering the transferred numbers, and pay the applicable registration fees. <o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-family: Arial, sans-serif; ">If the transfer request pertains to legacy numbers, the transfer shall not be contingent upon the new entity entering into an RSA, LRSA or any of form of written agreement with ARIN. For each transfer of legacy numbers under this Section 8.2, ARIN shall assess, and the new entity shall pay, a one-time “Legacy Record Change Fee” as set forth in the fee schedule<span class="Apple-converted-space"> </span><i>unless</i><span class="Apple-converted-space"> </span>the new entity elects, in its discretion, to enter into an LRSA covering the transferred legacy numbers and pays the applicable registration fees.<o:p></o:p></span></p><p style="margin-right: 0in; margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', serif; "><span style="font-family: Arial, sans-serif; ">[Note: This proposal incorporates the definition of “legacy number” from proposal 172 as revised June 6, 2012. The amount of the Legacy Record Change fee is TBD]<o:p></o:p></span></p><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Rationale<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">– The current version of 8.2 actually discourages legacy holders from (a) updating the WHOIS database, and (b) paying fees to assist with records management associated with the WHOIS database. Some entities that currently control resources do not attempt to update the WHOIS records because the current transfer process puts at risk their ability to retain and use their numbers. Under the current process, legacy holders or their lawful successors must first prove that they are the lawful successor (which is necessary and appropriate). But they then must also justify their need to continue using numbers they obtained prior to ARIN’s existence. Once they pass the needs hurdle, they must then execute an RSA (not even an LRSA) that alters their rights and subjects their numbers to audit and possible revocation under then-current policy. <o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 12pt; font-family: Arial, sans-serif; ">For non-legacy registrants, the process should also be less burdensome and uncertain. Ensuring the continuity of a company’s IP addressing scheme as part of an M&A transactions should be within the control of the entities directly involved. ARIN’s discretionary approval of transfers in this context introduces an undesirable and unnecessary contingency. Entities concerned about whether their M&A related update request will be approved by ARIN simply do not attempt to fully update the records.<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Minimizing the barriers for both legacy and non-legacy holders to update the WHOIS database when changes are required to accurately reflect normal corporate reorganization activities will help increase the accuracy of the WHOIS database, which benefits the community as a whole. <o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; font-family: Arial, sans-serif; ">Timetable for implementation</span></b><span style="font-size: 12pt; font-family: Arial, sans-serif; "><span class="Apple-converted-space"> </span>- Immediate<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><o:p> </o:p></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><b><span style="font-size: 12pt; color: rgb(64, 64, 64); ">Marc Lindsey<o:p></o:p></span></b></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="color: rgb(104, 102, 103); ">Levine, Blaszak, Block & Boothby, LLP<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="color: rgb(104, 102, 103); ">2001 L Street, NW Suite 900<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="color: rgb(104, 102, 103); ">Washington, DC 20036<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="color: rgb(89, 89, 89); ">Phone:</span><span style="color: rgb(0, 123, 175); "><span class="Apple-converted-space"> </span>(202) 857-2564<o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="color: rgb(104, 102, 103); ">Email:</span><span style="color: blue; "><span class="Apple-converted-space"> </span></span><span style="color: rgb(0, 123, 175); "><a href="mailto:adelgado@lb3law.com" style="color: blue; text-decoration: underline; "><span style="color: rgb(0, 123, 175); ">mlindsey@lb3law.com</span></a></span><span style="color: rgb(0, 51, 153); "><o:p></o:p></span></div><div style="margin-right: 0in; margin-left: 0in; font-size: 11pt; font-family: Calibri, sans-serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span style="color: rgb(104, 102, 103); ">Website:</span><span style="color: rgb(0, 51, 153); "><span class="Apple-converted-space"> </span></span><span style="color: rgb(0, 123, 175); "><a href="x-msg://295/www.lb3law.com" style="color: blue; text-decoration: underline; "><span style="color: rgb(0, 123, 175); ">www.lb3law.com</span></a></span><span style="color: blue; "><o:p></o:p></span></div></div>_______________________________________________<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" style="color: blue; text-decoration: underline; ">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" style="color: blue; text-decoration: underline; ">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact<span class="Apple-converted-space"> </span><a href="mailto:info@arin.net" style="color: blue; text-decoration: underline; ">info@arin.net</a><span class="Apple-converted-space"> </span>if you experience any issues.</div></span></blockquote></div><br></div></body></html>