mailing list archives
Re: ISP Filter Policies--Effect is what?
From: Steve Schaefer <schaefer () simone dashbit com>
Date: Tue, 8 May 2001 10:16:21 -0700 (PDT)
This discussion is basically correct. Some comments:
1) You always want to advertise the entire block (in this case, a /16).
If you don't own the entire block, then you should have a relationship
with to BGP originator of the block advertisement such that you can
receive traffic from them where you expect it (if, for example, you AS is
not really "well connected".)
2) There is no substitute for looking at things in the real world. To
understand how filtering works and routes propagate, I suggest two
University of Oregon Route Views Project
The route-views.oregon-ix.net router receives BGP from all but a few of
the major backbones and an assortment of others as well. You can query
that router to see who hears what routes. I was able to verify, for
example that Verio filters all Class B subnets (including /18, for
Traceloop (I am affiliated)
The Traceloop network is basically a searchable community of traceroute
servers. You'll have to sign up to get a personal login, since the Guest
Login doesn't have all the features that you'll want. If you type
"AS2914" in the search field (for example), you'll get a list of test
points in Verio's AS (although the formatting is poor). If you type
"www.verio.net" in the search field, you'll get a list of test points in
Verio's AS and some that use Verio for outbound routes, too. By choosing
test points in various AS's, you can see how traffic is actually routed.
Dashbit -- The Leader In Internet Topology
On Tue, 8 May 2001, Murphy, Brennan wrote:
I'm trying to figure out to what degree the existence of these policies
be accounted for in a BGP design which includes sites around the world.
I've read through a few of the threads having to do with Verio's
Filtering Policy. And I read the policies listed here:
Consider the following theoretical scenario:
Site BGP Advertisement to ISP
Amsterdam 126.96.36.199/24 AMSISP
Austin 188.8.131.52/24 Genuity & Internap
SanFran 184.108.40.206/24 Genuity & Internap
Tokyo 220.127.116.11/24 TOKISP
Sydney 18.104.22.168/24 SYDISP
1. Since Verio says they would not accept /24 nets drawn from Class B space,
I assume this means that they don't insert a /16 into their tables so that
the /24 nets appear to Verio customers as unreachable. In this case, a
that wants to extend connectivity to verio customers (and any
other ISP with similar policies) must include a /16 advertisement from at
one of the sites.
2. Suppose a customer of a Verio-like ISP, wishes to go to ftp. foo.org. DNS
returns 22.214.171.124 (in amsterdam, see above). Verio passes the traffic
to the neighbor it received the /16 advertisement from. At this point, the
best thing that could happen
is if that neighbor has the /16 and /24 networks in its route table, right?
means, a path exists for that user to the amsterdam server and the only
with routing to Amsterdam is that Verio possibly handed the traffic to a
neighbor. Am I understanding this issue correctly?
I'm new to BGP. I've tried to get a handle on this issue on my own and by
working with Genuity, Internap and Cisco. No disrespect to those companies
each of them had this vague memory of Verio's policy but couldnt really tell
in plain language how it might affect the above scenario. Obviously, I
to chief engineers. Someone from the CCIE mailing list suggested I browse
the archives of this list, which I did. But I didnt find a clear enough
answer to my questions--perhaps because they are too basic to be discussed
here or I'm not good at using this lists archive search engine.
Either way, any guidance on the above scenario is greatly appreciated.