Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: T3 or not to T3

  • From: Avi Freedman
  • Date: Mon Jul 22 01:47:24 1996

> It's pretty easy to enforce "no transit" at the packet filtering level
> -- only packets destined for my nets will be allowed in.  Is there some
> other aspect of filtering I'm forgetting about?  We have a dedicated
> and backup network engineer at any rate.  The border router would be a
> cisco 7200 or 7500 series with 128Mb.
> 
> Dean

Hmm...  If you do provide transit for others, making a dynamic filter
can be difficult if you base transit on as-path filters rather than
route filters.  

I hear that Sprint, one of the few large providers (that imposes filters
on customer BGP sessions) that still bases customer peering filters on 
as-path filters rather than on a per-session route filter list either 
manually constructed or built automagically from databases, is considering 
going or is going to go to route filtering its customer sessions rather 
than as-path filtering.  Now, I'm talking here about the BGP sessions, 
not the actual flow of data.  And it's been a long weekend, sorry if that
sentence was hard to parse.

Avi

- - - - - - - - - - - - - - - - -




Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.