PS: Here's Sprint's sister company's current announcement of routes
*originating* in its AS as I see them - I do hope Sprint takes the honest
path if it does refuse to carry short announcements and not route all bar
4 of these nets, as well as a similar long list from AS1239 I'm
not convinced Sprint has the moral highground here....
Moral high ground does not interest me. Working networks
I have to carry the ^1239_ routes internally anyway to get my
customers able to talk to each other. I don't need to carry
your routes at all, unless one of my customers wants to talk
to you. It's a simple thing, elegantly described by Jeff Young
earlier today. It was also elegantly described by Yakov
Rekhter in his CIDRD presentation of the concepts of Push and Pull.
Ordinarily I would answer "filter away; we've been prepared
for this kind of filter being applied against us since day
#1 (although admittedly it's not going to be too pretty if
someone wants to talk to you and suddenly can't. been there,
done that)". As a mechanism for motivating our customers to
aggregate better than they could, an important provider doing a
similar sort of inbound filtering likely would be much more
widely effective than the occasional Seanogram to various
customers warning of doom and the possibilities of being
filtered, which sometimes seem to be completely ignored.
This filtering is analagous to how ANS is able to get people
to register their prefixes in the RADB or run into inbound
announcement filters that will stop you from talking with
AOL and other ANS customers.
As you note, AS 4000 is run by a different company, and you
shouldn't punish them just because I'm an arrogant asshole,
as I have no control over or involvement with their routing
(I'm not even sure that I'm entirely popular over there. )
However, yes, they are not aggregating as well as they could
be, and are announcing more-specific-routes that are
completely subsumed by aggregates.
Some of those folks are here and should feel free to speak
for themselves. Hi guys!