<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:2027250822;
mso-list-type:hybrid;
mso-list-template-ids:606873114 20370002 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"\(%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>Owen – I’m not up to the task of convincing you to change your beliefs about the nature of the rights (or lack of rights) embodied in legacy numbers. I will simply point out that the proposed policy at issue (i.e., establishing a definition for legacy resources) is itself an acknowledgment that there is, in practice, a meaningful distinction between legacy and non-legacy numbers. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>I accept the constructive criticism regarding the structure of my proposed revision to the definition. I’ve restated it below in a way that, hopefully, is more readable:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>A legacy resource is an IPv4 address or Autonomous System Number that satisfies both of the following two criteria:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><span style='mso-list:Ignore'>(1)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>it was issued to an entity (other than a Regional Internet Registry) or individual (the “original legacy holder”) prior to ARIN's inception on Dec 22, 1997 either by an organization authorized by the United States to perform the Internet Assigned Numbers Authority (“IANA”) functions or an Internet Registry; and<o:p></o:p></span></p><p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo1'><![if !supportLists]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><span style='mso-list:Ignore'>(2)<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>it has not been returned to<span class=apple-converted-space> </span><span style='color:black'>a</span><span class=apple-converted-space> </span>Regional Internet Registry under a binding written agreement between the original legacy holder (or its legal successor or assign)<span class=apple-converted-space> </span><span style='color:black'>and the RIR<span class=apple-converted-space> </span></span>for subsequent allocation<span class=apple-converted-space><span style='color:black'> </span></span><span style='color:black'>and assignment</span><span class=apple-converted-space> </span>in accordance<span class=apple-converted-space> </span><span style='color:black'>with<span class=apple-converted-space> </span></span>such RIR’s number resource policies<span class=apple-converted-space><span style='color:black'> </span></span><span style='color:black'>and membership (or service) agreements</span>.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p></o:p></span></p><p class=MsoListParagraph><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'>-Marc<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Owen DeLong [mailto:owen@delong.com] <br><b>Sent:</b> Tuesday, June 05, 2012 3:26 PM<br><b>To:</b> Lindsey, Marc<br><b>Cc:</b> 'arin-ppml@arin.net'<br><b>Subject:</b> Re: [arin-ppml] ARIN-prop-172 Additional definition for NRPM Section 2 - Legacy Resources<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Jun 5, 2012, at 12:06 PM, Lindsey, Marc wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I support creating a definition<span class=apple-converted-space> </span><span style='color:black'>in the NRPM of</span><span class=apple-converted-space> </span>legacy resources so that future policy proposals can properly acknowledge and address the distinction between the bundle of rights associated with legacy<span class=apple-converted-space> </span><span style='color:black'>numbers</span><span class=apple-converted-space> </span>and<span class=apple-converted-space> </span><span style='color:black'>the specifically defined contract rights attributable to<span class=apple-converted-space> </span></span>non-legacy resources. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>What distinction would that be?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I remain unconvinced that any such distinction exists other than some ability to remain static and not pay fees.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>I would<span class=apple-converted-space> </span><span style='color:black'>, however,<span class=apple-converted-space> </span></span>suggest some revisions to the definition<span class=apple-converted-space> </span><span style='color:black'>as<span class=apple-converted-space> </span></span>proposed.<span style='color:black'> The revised definition is as follows:</span><o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>A legacy resource is an IPv4 address or Autonomous System Number that (a) was issued to an entity (other than a Regional Internet Registry) or individual (the “original legacy holder”) prior to ARIN's inception on Dec 22, 1997 either by an organization authorized by the United States to perform the Internet Assigned Numbers Authority (“IANA”) functions or an Internet Registry, and (b) has not been returned to<span class=apple-converted-space> </span><span style='color:black'>a</span><span class=apple-converted-space> </span>Regional Internet Registry under a binding written agreement between the original legacy holder (or its legal successor or assign)<span class=apple-converted-space> </span><span style='color:black'>and the RIR<span class=apple-converted-space> </span></span>for subsequent allocation<span class=apple-converted-space><span style='color:black'> </span></span><span style='color:black'>and assignment</span><span class=apple-converted-space> </span>in accordance<span class=apple-converted-space> </span><span style='color:black'>with<span class=apple-converted-space> </span></span>such RIR’s number resource policies<span class=apple-converted-space><span style='color:black'> </span></span><span style='color:black'>and membership (or service) agreements</span>.</span><span style='font-size:10.5pt;font-family:"Calibri","sans-serif"'><o:p></o:p></span></p></div></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>That's a very complex and difficult to parse runon sentence.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As much as it pains me to do so, I have to agree with Milton that the best definition is: "Legacy allocations/assignments are those allocations/assignments maintained in the ARIN database not covered by any form of RSA between ARIN and the recipient."<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Owen<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>