|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Sprint Peering Requirements? WAS More network problems (fwd)
I got this from one of our downstream customers. Is there any truth to this ? [email protected] ---------- Forwarded message ---------- Date: Fri, 15 Mar 1996 11:07:57 -0700 From: Nate Williams <[email protected]> To: [email protected] Subject: More network problems OK, here's the scoop, from the network weenie at Walnut Creek. > 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 :-) > > 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 > engineer. > > (pass this info on to Sprint, but don't have your ISP call CRL - Eric > would just be annoyed). > > Eric is trying to force Sprint to peer with them at DS3 speeds > (45mbit), and this might help. Right now, I can get to WC in-directly by going through sri.com, but this isn't acceptable as I need direct IP connectivity to get the latest source bits. Nate |