<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css">DIV {
MARGIN: 0px
}
</style>
<meta name="GENERATOR" content="MSHTML 8.00.7600.16490">
<style title="owaParaStyle"><!--P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
--></style>
</head>
<body ocsi="x">
<div dir="ltr"><font color="#000000" size="2" face="Tahoma">Sorry to respond slowly to this, Lee, have been on the road. Honestly, to me the issue is not at all about insisting that addresses are "inherently property"; it is about the attitudes and policies
that inform the ARIN contracts. </font></div>
<div dir="ltr"><font size="2" face="tahoma">I think the key policy conflicts have to do with transferability, which I continue to believe is very important in the ipv4 context. The terms and conditions under which RIRs can reclaim addresses, and the tying of
address resources to routing and aggregation constraints is another long term area of concern.
</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">I continue to see liberalized transferability as a key to dealing with the address shortages that will probably occur in the short term as the hoped-for migration to ipv6 drags on. Ithink the ARIN policy toward that
is too restrictive, and will not be used. I believe that a more reasonable, less trading-hostile attitude toward address markets would free up a lot of resources for use and rationalize the address scarcity problem by properly pricing addresses. this would
also create another incentive to adopt ipv6. </font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div dir="ltr"><font size="2" face="tahoma">You were probably hoping for something more specific; e.g., alter section x.y.(z) of the NPRM; however, the debate over PP 108 has revealed a continuing, higher-level attitudinal and philosophical disagreement in
the community that makes debates over specifics become proxies for these larger disagreements. As the proponents of 108 have correctly noted, the idea that assignees have no transferable property rights is deeply embedded on documents and policies that go
way back. Lacking the resources and time to review and revise the whole shebang, I have to limit my role to urging and supporting some attitudinal changes that might, in the future, lead to more specific alterations in policy.
</font></div>
<div dir="ltr"><font size="2" face="tahoma"></font> </div>
<div style="DIRECTION: ltr" id="divRpF490303">
<hr tabindex="-1">
<font size="2" face="Tahoma"><b>From:</b> Lee Howard [spiffnolee@yahoo.com]<br>
<b>Sent:</b> Wednesday, February 17, 2010 2:17 PM<br>
<b>To:</b> Milton L Mueller; michael.dillon@bt.com; arin-ppml@arin.net<br>
<b>Subject:</b> Re: [arin-ppml] Policy Proposal 108: Eliminate the term license in the NRPM<br>
</font><br>
</div>
<div></div>
<div>
<div style="FONT-FAMILY: arial,helvetica,sans-serif; FONT-SIZE: 10pt">Milton Mueller wrote:<br>
<div><br>
</div>
<div style="FONT-FAMILY: arial,helvetica,sans-serif; FONT-SIZE: 10pt">> Now we are getting somewhere more reasonable. Yes,
<br>
> contracts can be structured to allow the parties more or <br>
> less rights, more or less exclusivity, more or less <br>
> transferability. But that is a choice. So lets have a <br>
> discussion about that. It is obvious that ARIN does not <br>
> allow free transferability of the rights it assigns, but this is <br>
> just a policy decision it makes and that policy could be <br>
> modified in hundreds of ways. You contribute nothing <br>
> useful to that policy debate by making the word "property <br>
> rights" a taboo and attempting to banish it from the discussion. <br>
<div style="FONT-FAMILY: times new roman,new
york,times,serif; FONT-SIZE: 12pt">
<br>
Can I suggest that this conversation move in that direction?<br>
The back-and-forth of "address cannot be property" vs.<br>
"addresses are inherently property" seems to be deadlocked.<br>
There may be policies that would follow from a definition of<br>
addresses as property; what policies would you propose?<br>
<br>
Lee<br>
</div>
</div>
</div>
<br>
</div>
</body>
</html>