<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"><title>Re: [arin-ppml] Opposed to 2010-9 and 2010-12</title>
</head>
<body>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt"><br>
<br>
<br>
On 10/26/10 12:39 PM, "Milton L Mueller" <<a href="mueller@syr.edu">mueller@syr.edu</a>> wrote:<br>
<br>
</span></font><blockquote><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">worth pursuing further. <br>
<br>
<br>
Putting in hard dates to try to sunset an address range will just lead to endless debate. <br>
<br>
Agreed, but the escalating fees also require a somewhat arbitrary setting of the escalation rate. Double every year, or every two years? Doubling starts after [three][five][N] years?<br>
<br>
Putting in an explicit cost that is only borne by those who need the crutch will result in a natural weaning. <br>
<br>
Agreed<br>
<br>
As much as I don’t want to see 6rd in a different prefix range, maybe that is the out here. Create a specific fee schedule for a dedicated use prefix range, which would enable a path forward in the short term at the same time it motivates providers to get off of the technology asap. <br>
<br>
That might work. Herrin was proposing segregation of prefix ranges for other purposes, got some flak but I can’t remember exactly what for.<br>
<br>
Another possibility might simply be to impose a 6rd surcharge that increases. If I am correct in assuming that 6rd users have to declare what they are doing in order to qualify for the larger blocks of addresses, the fee could be triggered by the declaration rather than the use of a specific address range. <br>
<br>
<br>
</span></font></blockquote>
</body>
</html>