<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">
<p dir="ltr">Hi John, </p>
<p dir="ltr">You were the one who eventually did fix the issue and I do
appreciate that. <br>
</p>
<p dir="ltr">I don't believe that ARIN today will treat anyone
differently than they treated me, as the behavior is based on the rules
and regulations that ARIN runs under. The bar is set too high to allow
objects to be updated, especially if they have not been updated in a
long time.<br>
</p>
<p dir="ltr">I've been around long enough to know a number of
resources/objects be it legacy IP assignments or legacy AS numbers that
are in use today but still reflect old data.
I believe it would be foolhardy to even attempt to correct the
information as it would only cause excess paperwork, wasted time,
management sign-offs, possible loss of the resource or worse.<br>
</p>
<p dir="ltr">Until there is a change in ARIN's behavior that allows for
the acceptance of historical artifacts, the database will never be
correct and there is certainly no reason for people who would like to,
to try and update the information contained within it.</p>
<blockquote style="border: 0px none;"
cite="mid:15A4C5D7-1EAE-4FB5-BF18-5D1BE44F4103@arin.net" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="jcurran@arin.net" photoname="John Curran"
src="cid:part1.07050807.08040000@sonn.com"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:jcurran@arin.net"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">John Curran</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">February 17, 2014
at 2:02 PM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
On Feb 17, 2014, at 4:08 PM, Steve Noble <<a moz-do-not-send="true"
href="mailto:snoble@sonn.com">snoble@sonn.com</a>> wrote:<br>
<div><br class="Apple-interchange-newline">
<br>
</div>
<div>Steve - </div>
<div> </div>
<div> I'll be the first to admit you suffered needlessly, and
appreciate your diligence in </div>
<div> pursuing the correction with ARIN (as it led to us finding an end
case for ASN-</div>
<div> only resource records.) For those who might not remember the
issue, read </div>
<div> <<a moz-do-not-send="true"
href="http://lists.arin.net/pipermail/arin-ppml/2012-September/026100.html">http://lists.arin.net/pipermail/arin-ppml/2012-September/026100.html</a>> </div>
<div> At this time, you should not longer have any problem updating
your ASN records,</div>
<div> and I will apologize again that we did not recognize the issue as
a fallout from our</div>
<div> migration any sooner than we did.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>/John</div>
<div><br>
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="snoble@sonn.com" photoname="Steve Noble"
src="cid:part2.08010800.05010609@sonn.com" name="postbox-contact.jpg"
height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:snoble@sonn.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Steve Noble</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">February 17, 2014
at 1:08 PM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
As a holder of both legacy
and non-legacy ARIN objects, I have been subject to ARIN's registry
update blocks on _non-legacy_ objects that I rightfully control and
use. I spent years (6 I believe) fighting with ARIN to update the
information on one of my ASNs while ARIN continued to bill me for a
'service' which they did not provide. ARIN's unwillingness to update
the database to have correct contact information is not only an
undesirable effect of their policies, but also an indication of ARIN's
lack of concern about having correct information in the database. <br>
<br>
As a consumer, I see no value to the service that ARIN provides. I pay
ARIN's fees only to keep ARIN from giving the AS that I use to someone
else and causing an administrative issue to become an operational issue.<br>
<br>
</div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="mlindsey@lb3law.com" photoname="Lindsey, Marc"
src="cid:part1.07050807.08040000@sonn.com"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:mlindsey@lb3law.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Lindsey, Marc</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">February 17, 2014
at 11:53 AM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<meta content="Microsoft Word 15 (filtered medium)" name="Generator">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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="WordSection1">
<p class="MsoNormal">I advise several large legacy block holders. Some
of them signed the LRSA, but many have not. For them, the burdens
imposed by the LRSA outweigh the benefits. Some on the PPML have
suggested that off-contract legacy holders don’t sign
up with ARIN because they want to be free-riders. But the fees (and
the avoidance of the fees) are not a factor in their LRSA decision.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Based on my experience working with legacy block
holders, I believe adopting a policy substantially similar to RIPE 605
(ARIN prop 203) would go a long way in harmonizing the interests of the
ARIN community with the community of legacy
holders that do not have formal relationships with ARIN. <o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">ARIN’s absolute control over additional allocations
of “free” IPv4 numbers in its region has served as the primary policy
enforcement mechanism. This carrot really only works on recipients that
need more IPv4 numbers, and then only as
long as ARIN has free numbers to give out. It doesn’t directly
influence the behavior of many legacy block holders when they convey
their spare numbers. Legacy holders are a major source of future IPv4
number distributions, and their relevance to the broader
ARIN community will become more prominent as ARIN’s IPv4 free pool
reaches depletion.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the secondary market context, ARIN now relies on
its ability to withhold registry database updates as the primary means
to extend enforcement of its current policies into private transactions
between parties conveying beneficial use
of IPv4 numbers. This, however, is a weak enforcement tool. Two
parties can convey beneficial use of IPv4 numbers in lawful commercial
transactions without updating ARIN’s registry database. But IPv4 number
conveyances not recorded in the registry system
produces very undesirable results – the “reality” in the registry
database will not reflect operational reality, as David Conrad and
others have pointed out in several posts.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Buyers and sellers would prefer to document their
conveyances in a reliable and accurate public registry, but not if the
contingencies and conditions materially and adversely affect their
commercial arrangement. RIPE 605/ ARIN prop 203
recognizes this reality. With a little tweaking, adopting it would go a
long way in minimizing the disincentives now facing legacy holders (and
entities that want to acquire their numbers) when contemplating whether
updating the registry database is worth
the risk of subjecting their transactions to ARIN’s approval process. <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:black">Marc Lindsey</span></b><span
style="color:black"><br>
Levine, Blaszak, Block & Boothby, LLP<br>
2001 L Street, NW Suite 900<br>
Washington, DC 20036<br>
<i>Office:</i> (202) 857-2564<br>
<i>Mobile:</i> (202) 491-3230<br>
<i>Email:</i> </span><span style="color:#1F497D"><a
moz-do-not-send="true" href="mailto:mlindsey@lb3law.com"><span
style="color:#0563C1">mlindsey@lb3law.com</span></a><br>
</span><span style="color:black">Website: </span><span
style="color:#1F497D"><a moz-do-not-send="true"
href="http://www.lb3law.com"><span style="color:#0563C1">www.lb3law.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>_______________________________________________<br>PPML<br>You are
receiving this message because you are subscribed to<br>the ARIN Public
Policy Mailing List (<a class="moz-txt-link-abbreviated" href="mailto:ARIN-PPML@arin.net">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your
mailing list subscription at:<br><a class="moz-txt-link-freetext" href="http://lists.arin.net/mailman/listinfo/arin-ppml">http://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please
contact <a class="moz-txt-link-abbreviated" href="mailto:info@arin.net">info@arin.net</a> if you experience any issues.</div></div>
</blockquote>
</body></html>