| PX = Private eXchange (private peering). sorry 'bout any confusion. Uhm, OK, so what's the difference between that and a customer connection across which BGP is spoken? Sean.
| PX = Private eXchange (private peering). sorry 'bout any confusion.
Uhm, OK, so what's the difference between that and a customer connection across which BGP is spoken?
Whether or not they announce non-(Sprint)-customer routes, such as AS1? -- Alex Bligh GX Networks (formerly Xara Networks)
On Thu, 13 Aug 1998, Sean M. Doran wrote:
Uhm, OK, so what's the difference between that and a customer connection across which BGP is spoken?
Sean.
I'm starting to get lost here, so maybe someone can restate things in a way that's educational and appropriate to the charter of the list. The question above is rather interesting, and what I'd like to know is what are the various types of "peering" that various ISPs have arranged between each other? "public" - each ISP is at a public exchange point and traffic that is destined to/from each provider moves across whatever hardware is provided at the exchange point. This could exist at all exchange points where both parties have an adequate presence. Possible additional cost if traffic that would come from another peer is shifted here and bandwidth to the exchange needs to be increased. "private" - A connection exists either via PTP, ATM, FR, or whatever else you can think of between the involved parties. One or both parties pay for the link. One time hardware outlay. Seems expensive. Less expensive than "buying" an DS3 or higher port from the provider. Who buys from whom? Who pays? These must be NDA'd. Can anyone cite some examples of what some providers *might* do to make it a fair trade when this is an NDA'd agreement? "public/private hybrid" - Existing exchange point equipment and connections are used. Purchase ether/fddi cable from MFS to run between your equipment. Cheap? No telco charges, consolidate your pipes. So what was the Exodus/GTEI agreement like? Did it fit neatly into one of these categories? Are there other more esoteric arrangements? Is GTEI basically trying to get Exodus as a "customer" in a round-about way? That certainly seems like an easy way to make more cash. "I'll talk to you, but only if you buy 'Peering Bundle #A13' from us at $100,000/mo. and you have no other options. We are big, and this is what you need to do to be a peer." Is this an accurate assessment? Please set me on track if I'm misunderstanding the concepts at work here... Thanks, Charles =-----------------= = | Charles Sprickman Internet Channel | | INCH System Administration Team (212)243-5200 | | spork@inch.com access@inch.com | = =----------------=
So what was the Exodus/GTEI agreement like? Did it fit neatly into one of these categories? Are there other more esoteric arrangements? Is GTEI basically trying to get Exodus as a "customer" in a round-about way? That certainly seems like an easy way to make more cash. "I'll talk to you, but only if you buy 'Peering Bundle #A13' from us at $100,000/mo. and you have no other options. We are big, and this is what you need to do to be a peer."
Who knows? Exodus people and GTE folks each have their own side of the story which will doubtless be different. I don't like to see any kind of dispute/disagreement like this and I hope that its resolved soon. The suffering party here is the customer of both providers and their customers customers. Everyone raving on about it on this list probably won't help either parties. Lines will be crossed and as what always happens in email people will misunderstand and the situation is liable to worsen. I hope all parties come to a more amicable agreement soon though, things like this don't help the fragile business Internet Service Provision is. Regards, Neil. -- Neil J. McRae. Alive and Kicking. Domino: In the glow of the night. neil@DOMINO.ORG NetBSD/sparc: 100% SpF (Solaris protection Factor) Free the daemon in your <A HREF="http://www.NetBSD.ORG/">computer!</A>
Comments below:
On Thu, 13 Aug 1998, Sean M. Doran wrote:
Uhm, OK, so what's the difference between that and a customer connection across which BGP is spoken?
Sean.
I'm starting to get lost here, so maybe someone can restate things in a way that's educational and appropriate to the charter of the list.
The question above is rather interesting, and what I'd like to know is what are the various types of "peering" that various ISPs have arranged between each other?
"public" - each ISP is at a public exchange point and traffic that is destined to/from each provider moves across whatever hardware is provided at the exchange point. This could exist at all exchange points where both parties have an adequate presence. Possible additional cost if traffic that would come from another peer is shifted here and bandwidth to the exchange needs to be increased.
"private" - A connection exists either via PTP, ATM, FR, or whatever else you can think of between the involved parties. One or both parties pay for the link. One time hardware outlay. Seems expensive. Less expensive than "buying" an DS3 or higher port from the provider. Who buys from whom? Who pays? These must be NDA'd. Can anyone cite some examples of what some providers *might* do to make it a fair trade when this is an NDA'd agreement?
"public/private hybrid" - Existing exchange point equipment and connections are used. Purchase ether/fddi cable from MFS to run between your equipment. Cheap? No telco charges, consolidate your pipes.
So what was the Exodus/GTEI agreement like? Did it fit neatly into one of these categories? Are there other more esoteric arrangements? Is GTEI basically trying to get Exodus as a "customer" in a round-about way? That certainly seems like an easy way to make more cash. "I'll talk to you, but only if you buy 'Peering Bundle #A13' from us at $100,000/mo. and you have no other options. We are big, and this is what you need to do to be a peer."
The only arrangement I can talk about is the GTEI/Exodus one. As I have stated before, there are two private interconnects between the providers. These are local loop DS3s, one in the Bay Area, one in Washington D.C. greater area. Both local loops were purchased/provisioned by Exodus. Hardware was purchased by the respective parties on both ends of the circuit. Both parties feed MEDs/specific networks to the other parties of their OWN networks/customer networks (a non-transit agreement). No money exchanges hands. Each party agrees to backhaul to the "best-exit" (based upon the MEDs and Specifics with MEDs). This was designed to alleviate the asymmetric traffic flows (BBN requests more data from Exodus than Exodus requests from BBN). So it's yet another private interconnect agreement, not mentioned in the above.
Is this an accurate assessment? Please set me on track if I'm misunderstanding the concepts at work here...
Thanks,
Charles
=-----------------= = | Charles Sprickman Internet Channel | | INCH System Administration Team (212)243-5200 | | spork@inch.com access@inch.com | = =----------------=
On Thu, 13 Aug 1998, Charles Sprickman wrote:
On Thu, 13 Aug 1998, Sean M. Doran wrote:
Uhm, OK, so what's the difference between that and a customer connection across which BGP is spoken?
There are two differences: Purchased PX Customer Connection == =================== $: $0 >$0 Routes: Just the All other providers'
The question above is rather interesting, and what I'd like to know is what are the various types of "peering" that various ISPs have arranged between each other?
I'd think there are two; public exchange (MAE's, etc), and PX (it is be a PtP DS[1|3], Frame PVC, ATM VC, whatever. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Atheism is a non-prophet organization. I route, therefore I am. Alex Rubenstein, alex@nac.net, KC2BUO, ISP/C Charter Member Father of the Network and Head Bottle-Washer Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834 Don't choose a spineless ISP; we have more backbone! http://www.nac.net -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
On Thu, 13 Aug 1998, Sean M. Doran wrote:
| PX = Private eXchange (private peering). sorry 'bout any confusion.
Uhm, OK, so what's the difference between that and a customer connection across which BGP is spoken?
Transit. ------------------------------------------------------------------ Jon Lewis <jlewis@fdt.net> | Spammers will be winnuked or Network Administrator | drawn and quartered...whichever Florida Digital Turnpike | is more convenient. ______http://inorganic5.fdt.net/~jlewis/pgp for PGP public key____
participants (7)
-
Alex Bligh
-
alex@nac.net
-
Charles Sprickman
-
Jon Lewis
-
Neil J. McRae
-
Robert Bowman
-
Sean M. Doran