[53958] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Operational Issues with 69.0.0.0/8...

daemon@ATHENA.MIT.EDU (Alec H. Peterson)
Fri Dec 6 13:05:24 2002

Date: Fri, 06 Dec 2002 11:04:50 -0700
From: "Alec H. Peterson" <ahp@hilander.com>
To: Michael.Dillon@radianz.com, nanog@merit.edu
In-Reply-To: <OF3C942DE3.86C97C48-ON80256C87.005CCF9C-80256C87.005D1EE1@radianz.com>
Errors-To: owner-nanog-outgoing@merit.edu


<Putting on my hat as ARIN AC Chair>

--On Friday, December 6, 2002 16:57 +0000 Michael.Dillon@radianz.com wrote:

>
> This is no longer a technical operational issue so it is out of scope for
> this mailing list.
>
> But if you think that ARIN could do something to solve your problem then
> you should raise the issue on the ARIN public policy mailing list. You
> can  find subscription information for that list here
> http://www.arin.net/mailing_lists/index.html


I see this as purely an operational issue.

ARIN explicitly does not guarantee routability of prefixes it assigns.  If 
service providers choose to filter ARIN allocations, then that is an 
operational decision.  I really don't see what action you expect ARIN to 
take along these lines.

Alec

--
Alec H. Peterson -- ahp@hilander.com
Chief Technology Officer
Catbird Networks, http://www.catbird.com

home help back first fref pref prev next nref lref last post