25 Apr
2016
25 Apr
'16
2:24 p.m.
For BGP, AT&T is asking that we SWIP the subnet on ARIN. Of course we can't
do that, and I've shared the background that AMPRNET is legacy pre-ARIN ip
space. I'm curious, has anyone run into this in the past? How were the
service provider's concerns addressed?
Thanks,
--
Ryan Turner
25 Apr
25 Apr
2:42 p.m.
For the very few cases where this has come up, ARDC has been willing
to provide a signed LOA on letterhead, and that has been sufficient.
- Brian
On Mon, Apr 25, 2016 at 01:24:04PM -0500, Ryan Elliott Turner wrote:
For BGP, AT&T is asking that we SWIP the subnet on
ARIN. Of course we can't
do that, and I've shared the background that AMPRNET is legacy pre-ARIN ip
space. I'm curious, has anyone run into this in the past? How were the
service provider's concerns addressed?
3:28 p.m.
On 4/25/16 2:24 PM, Ryan Elliott Turner wrote:
For BGP, AT&T is asking that we SWIP the subnet on
ARIN. Of course we can't
do that
Nonsense, it's certainly doable.
Right now 44/8 is setup as a NetType of "direct assignment", meaning it is
only suppose to be used as a contiguous block. Changing this to a "direct
allocation" would enable ARDC to SWIP it via ARIN's interface or setup a
RWHOIS server.
This was prompted by some discussions I had with the ARIN helpdesk at NANOG 62
and a further chat with John Curran. It would not jeopardize or in anyway
change the ownership rights ARDC has in 44/8.
The Technical Advisory Committee voted unanimously to make the direct
allocation change with ARIN around 4-July 2014.
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
3132
days inactive
3132
days old
2 comments
3 participants
participants (3)
-
Brian Kantor -
Bryan Fields -
Ryan Elliott Turner