Sprint Peering Requirements? WAS More network problems (fwd)

I got this from one of our downstream customers.

Is there any truth to this ?

Okay, here's what you can do...Have your ISP contact Sprint and
complain that they don't have connectivity to CRL network
Services. CRL has T3s at several places that Sprint is at, but Sprint
won't peer with them (Sprint has some stupid new requirements,
apparantly, requiring peering at 3 NAPs.) No problem - all of CRLs are
on 7507s :slight_smile:

Anyway, CRL is at 2 NAPs - Washington DC and PacBell. Sprint's just
being stubborn. ...anyway, have them complain to Sprint. The contact
person at CRL is Eric Mehlhaff (415) 837 5300, he's the cheif network

Sprint should take CRL up on CRL's offer :-). CRL has been telling
me for months CRL can't peer at the Washington DC MAE-East because
all of CRL's BGP peer slots at Mae-East are on "allocation." And
therefore CRL doesn't have room for any more peers in DC.

mae-east> show cdp neigh detail
Device ID: gwdca1.crl.com
Entry address(es):
  IP address:
Platform: cisco 2500, Capabilities: Router Trans-Bridge
Interface: Fddi0/0, Port ID (outgoing port): Ethernet1
Holdtime : 166 sec

Version :
Cisco Internetwork Operating System Software
IOS (tm) 3000 Software (IGS-I-L), Version 11.0(2), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1995 by cisco Systems, Inc.
Compiled Mon 25-Sep-95 18:34 by deannaw

In the meantime just dump the Sprintlink traffic through Sprint's T1
line at the CIX, and let Sprint backhaul it to the other coast.

Its a great sales opportunity when Sprint customers call ask why
performance is so bad. Our network engineers may not like Sean Doran,
but our sales people sure do. We've had several Sprint customers buy
direct circuits to our network because Sprint's peering policies caused
their traffic to travel the long way (and sometimes get lost along the
way). As long as Sprint keeps refusing, you get to look like the helpfull
company trying to meet the customer's needs.