This is sure to create a number of "big pipe orphans". I wonder if this will create a surge in multihoming attempts? How could you discourage that now? Unlike the recent DSL disasters, you can't just say "buy a T1 if you want reliable service". Even if you are not a PSI customer, it would be foolish not to multihome now. Did C&W consider the route table effects of this new routing policy? KL "Patrick W. Gilmore" wrote:
At 05:44 PM 6/4/2001 -0400, Travis Pugh wrote:
route-views.oregon-ix.net concurs:
route-views.oregon-ix.net>sh ip bgp regex ^3561_174_
route-views.oregon-ix.net>
Yes, but if one or the other has backup peering, it would not look like that. It would look like _3561_.*_174_ or _174_.*_3561_ - prolly the former since AS3561 gives route-views a feed, but AS714 does not.
Looking in route-views for those two patterns, I see only a few routes under 3561.*_174_, probably leakage. There are no routes of the form _174_.*_3561_.
Since route-views does have a feed from AS3561, I would say it is official. Cable and Wireless cannot reach PSI.net.
Congratulations ladies & gentlemen. The first intentional, prolonged, significant (for some values of "significant" :) outage on the Internet. And we were all here to see it....
Wow, in the same week MAE-East dies. Sad time for the 'Net. :((
-travis
-- TTFN, patrick
Did C&W consider the route table effects of this new routing policy?
You must first know what a route table is before you can measure such a thing. The only thing they saw were the dollar signs they "thought" they would bring in. Exactly what happens when finance runs your peering department and the engineers don't have anything to say about it. -Scott
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
You must first know what a route table is before you can measure such a thing. The only thing they saw were the dollar signs they "thought" they would bring in. Exactly what happens when finance runs your peering department and the engineers don't have anything to say about it.
Did they really think that PSI, of all carriers, would be in a position to start BUYING transit? Yeesh.. __ Matt Levine @Home <matt@deliver3.com> @Work <matt@eldosales.com> - http://www.easynews.com PGP Public Key (0x6C0D04CF): http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0D04CF
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Scott Patterson Sent: Monday, June 04, 2001 6:42 PM To: Kevin Loch; nanog@merit.edu Subject: RE: C&W Peering
Did C&W consider the route table effects of this new routing policy?
You must first know what a route table is before you can measure such a thing. The only thing they saw were the dollar signs they "thought" they would bring in. Exactly what happens when finance runs your peering department and the engineers don't have anything to say about it.
-Scott
-----BEGIN PGP SIGNATURE----- Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> iQA/AwUBOxwRYcp0j1NsDQTPEQJhtACgtX3z9OhIBksLu5dBfRN8Y+NiHAwAoMSe WgFg+f09fwH2zQn/EoYUPuDz =qVkt -----END PGP SIGNATURE-----
participants (3)
-
Kevin Loch -
Matt Levine -
Scott Patterson