<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Derek,<div><br><div><div>On Apr 28, 2014, at 8:58 PM, Derek Calanchini <<a href="mailto:derekc@cnets.net">derekc@cnets.net</a>> wrote:</div><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><div class="moz-cite-prefix">Here are some answers you may have missed:<br>
1.<br>
Arin said the smallest I could request was a /20, I was requesting
a /22. My current /22 is currently owned by Integra...I procured
them from Electric Lightwave before they got eaten by Integra.<br>
<br>
So what does legacy mean? </div></div></blockquote><div><br></div>It means it was allocated prior to the requirement of entering into a Registration Services Agreement.</div><div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><div class="moz-cite-prefix">Arin told me that Integra owned the
IP's I am using. Would it be possible to strong arm them into
letting me reassign them to ATT?<br></div></div></blockquote><div><br></div>Unlikely, but large amounts of money might help convince them. I suspect this approach isn't of interest however.</div><div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><div class="moz-cite-prefix">2.<br>
I did put in the request that I was going to surrender my current
/22 after migration to the newly requested /22.<br></div></div></blockquote><div><br></div>Not relevant. The applicable policy is quite clear: you need to "demonstrate need" for a /20, something that will be a bit challenging for you at this point.</div><div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><div class="moz-cite-prefix">3.<br>
This seems to cover it:<br>
<br>
<a class="moz-txt-link-freetext" href="https://www.arin.net/participate/meetings/reports/ARIN_33/PDF/monday/nobile_policy.pdf">https://www.arin.net/participate/meetings/reports/ARIN_33/PDF/monday/nobile_policy.pdf</a><br>
(is this the draft to prop 207??)<br></div></div></blockquote><div><br></div>No, that's a presentation that is providing information to the community regarding ARIN staff's experiences in implementing the policies the community has developed. One of the things Leslie (the head of registration services) was pointing out was that there were ... issues with existing policy.</div><div><br></div><div>I believe "prop 207" being referenced is <a href="https://www.arin.net/policy/proposals/ARIN_prop_207_orig.html">https://www.arin.net/policy/proposals/ARIN_prop_207_orig.html</a>. I'm guessing Martin's concerns is that policy proposal is way more complicated than what you need. What you appear to need is revising 4.3.2.1 of the NRPM to say /22 instead of /20.</div><div><br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000"><div class="moz-cite-prefix"><b><big>Is there anything I can do to speed this along?
Seriously, I will do authoring, leg work, make
calls...whatever it takes!</big></b><br></div></div></blockquote><br></div><div>To be honest, so far, you are seeing something approaching light speed in the RIR policy world. IIUC, what some folks are suggesting is that the ARIN Board step in and modify policy to address this particular issue before the next ARIN meeting (in Bellevue, WA in early June). This would be somewhat similar to tunneling through a wormhole...</div></div><div><br></div><div>Regards,</div><div>-drc</div><div><br></div></body></html>