[36027] in North American Network Operators' Group

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

Re: EP.net Issues

daemon@ATHENA.MIT.EDU (Joe Provo)
Thu Mar 22 11:42:10 2001

Date: Thu, 22 Mar 2001 11:29:46 -0500
From: Joe Provo <joe.provo@rcn.com>
To: nanog@merit.edu
Message-ID: <20010322112946.A3129@ultra.net>
Reply-To: joe.provo@rcn.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200103212207.WAA11074@vacation.karoshi.com>; from bmanning@vacation.karoshi.com on Wed, Mar 21, 2001 at 10:07:33PM +0000
Errors-To: owner-nanog-outgoing@merit.edu


On Wed, Mar 21, 2001 at 10:07:33PM +0000, bmanning@vacation.karoshi.com wrote:
> [John Fraizer]
> > Joe, a LOT of providers don't accept 198.32.4.0/24.  We see it on 2 out of
> > four paths.  The other two providers are filtering it.
> 
>  folks are encouraged to filter as they see fit. if folks would 
>  like to establish direct peering, please let me know.

It's often considered a Good Thing to not hear the networks of exchange
points from peers/others. A conservative approach is to filter out 
announcements of EPs to which you are actually connected rather than all
you can find; some folks just squash 198.32/16 and any other addresses
they can find.

It is worth noting that none of 198.32.2/24, 198.32.4/24 or 198.32/16 
have IRR entries; that might adversely affect reachability in defaultless
IRR-strict networks.

Cheers,

Joe

--
Joe Provo                                            Voice  508.486.7471
Director, Internet Planning & Design                 Fax    508.229.2375
Network Deployment & Management, RCN                 <joe.provo@rcn.com>


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