<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
That's kind of like saying if you purchase a property in New York City,
or California, or anyplace with regulations about property taxes...
And you get a really sweet deal with little property tax many years
ago...<br>
<br>
Now, come several years later you want to get a second property in the
area... Is the second property's value/taxation going to supercede the
first one you had? If so, it's unlikely anyone would purchase extra
properties... Or would complicate the system by filing under a "new"
name so as to not fall prey to that scheme.<br>
<br>
You get the first thing under one set of rules and you're getting a
second thing (completely unrelated) under a new set of rules. Two
separate transactions IMHO.<br>
<br>
Personally, I'm kinda bummed I didn't think ahead enough years and
years ago to get legacy space, but that's my problem. ;)<br>
<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html; ">
<meta http-equiv="Content-Style-Type" content="text/css">
<title></title>
<meta name="Generator" content="Cocoa HTML Writer">
<meta name="CocoaVersion" content="1038.25">
<style type="text/css">
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px}
p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica}
p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; color: #04ffbf}
p.p4 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; color: #0b04ff}
</style>
<p class="p1"><span class="Apple-converted-space"> </span></p>
Scott</div>
<br>
Brian Johnson wrote:
<blockquote
cite="mid:29A54911243620478FF59F00EBB12F4701CEE23A@ex01.drtel.lan"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<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;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 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;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I
oppose this proposal as it maintains the current divide
between legacy space and “regular” space. If a legacy holder wants IPv6
space, they would need to sign a regular RSA and join the rest of us.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: Consolas; color: rgb(31, 73, 125);">-
Brian<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div
style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; border-width: medium medium medium 1.5pt; padding: 0in 0in 0in 4pt;">
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:arin-discuss-bounces@arin.net">arin-discuss-bounces@arin.net</a> [<a class="moz-txt-link-freetext" href="mailto:arin-discuss-bounces@arin.net">mailto:arin-discuss-bounces@arin.net</a>] <b>On
Behalf Of </b>Owen DeLong<br>
<b>Sent:</b> Tuesday, February 02, 2010 10:39 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:arin-discuss@arin.net">arin-discuss@arin.net</a><br>
<b>Subject:</b> [arin-discuss] Suggestion 2010.1 -- Initial Fee
Waiver for
IPv6assignments to LRSA signatories<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I have submitted a formal suggestion to the ACSP
recommending that the BoT waive initial<o:p></o:p></p>
<div>
<p class="MsoNormal">assignment fees for IPv6 when the applicant is a
legacy
resource holder that has signed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">the LRSA.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I believe this helps remove most of the barriers
to entry
for legacy IPv4 holders to migrate<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">to IPv6 and is in the best interests of the
community.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">ARIN has informed me that the matter will be
placed on the
Board's finance committee<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">agenda. As such, I would like to encourage
members
here who have an opinion on the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">matter to let the board know what you think,
ideally by
posting a message to this list.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><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"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Below is the message I received from ARIN and
the original
suggestion I submitted:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom: 12pt;"><span
class="apple-style-span"><span style="font-family: "Courier New";">Owen,</span></span><span
style="font-family: "Courier New";"><br>
<br>
<br>
<span class="apple-style-span">This is in response to your suggestion
noted below
and assigned number 2010.1.</span><br>
<br>
<span class="apple-style-span">Thank you for your suggestion relating
to charging
no initial fee related to request for an initial IPv6 allocation and/or
assignments for Legacy Holders that have signed the ARIN Legacy
Registration
Service Agreement. As this relates to fees, this will be added to the
ARIN Board's Finance Committee agenda for 2010.</span><br>
<br>
<span class="apple-style-span">Some other information related to this
suggestion
is that the current IPv6 waiver for allocations for initial requests
and
renewals in 2010 is a 50% fee waiver. For requests in 2011, the
allocation fees
will be 25% waived. </span><br>
<span class="apple-style-span">In terms of assignments, the initial
fee is not
waived. Clients requesting assignment resources pay an initial fee per
request of address space and thereafter pay annual allocation or
maintenance
fees related to the Organizational ID as a whole. Initial fees are to
cover the
effort related to reviewing and analyzing the request, whereas
maintenance fees
are designed to cover the overhead of maintaining objects in the
database.</span><br>
<br>
<span class="apple-style-span">Recent changes were implemented in mid
2009 for
organizations with both ARIN-issued and Legacy Resources. They are
assessed an
Annual Fee based on the ARIN-issued resources and not charged the
Legacy
resource maintenance fee.</span><br>
<br>
<span class="apple-style-span">ARIN is reliant on its active
membership to help
it better serve the community and we want to commend you for your
continuing
activism and service.</span><br>
<br>
<span class="apple-style-span">Regards,</span><br>
<br>
<span class="apple-style-span">Member Services</span><br>
<span class="apple-style-span">American Registry for Internet Numbers
(ARIN)</span><br>
<br>
<span class="apple-style-span">*********************************************</span><br>
<br>
<span class="apple-style-span">2010.1</span><br>
<span class="apple-style-span">01-18-2010 16:58:30</span><br>
<br>
<span class="apple-style-span">ARIN should offer legacy holders that
sign the
LRSA the opportunity to receive an appropriate IPv6 allocation or
assignment
for no initial fee. The applicable standard renewal fees would apply
thereafter.</span><br>
<br>
</span><o:p></o:p></p>
</div>
</div>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
ARIN-Discuss
You are receiving this message because you are subscribed to
the ARIN Discussion Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-discuss@arin.net">ARIN-discuss@arin.net</a>).
Unsubscribe or manage your mailing list subscription at:
<a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-discuss">http://lists.arin.net/mailman/listinfo/arin-discuss</a>
Please contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</pre>
</blockquote>
</body>
</html>