Could some kind network operator out there, guide me to a FAQ or some other document with regards to interconnecting at MAE-West (or any other MAE). Specifically, some of the things I would like to find out about are probably old hat to most of you, so if you could pass on some of your knowledge, it would be greatly appreciated. Some of the specifics: 1) Requirements for interconnect at MAE-West 2) Cost? 3) Minimum Line Speed 4) Transit? i.e. if the line is for backup purposes only, how can we arrange for transit, etc... 5) Peering agreements etc. So if there is a document or set of documents that have this info in them, if someone could point me in the right direction, I'd surely appreciate it. -Carl Forsythe carlf@mbay.net -- ===================================================================== Carl Forsythe |Webmaster Monterey Bay Internet | carlf@mbay.net | http://www.mbay.net | =====================================================================
On Fri, 5 Jul 1996, Carl Forsythe wrote: |} Could some kind network operator out there, guide me to a FAQ or some |} other document with regards to interconnecting at MAE-West (or any |} other MAE). Specifically, some of the things I would like to find out |} about are probably old hat to most of you, so if you could pass on some |} of your knowledge, it would be greatly appreciated. The best place for info on the MAEs is from MFS, send mail to 'mae-info@mfst.com' with a similar request. -jh-
On Fri, 5 Jul 1996, Carl Forsythe wrote:
|} Could some kind network operator out there, guide me to a FAQ or some |} other document with regards to interconnecting at MAE-West (or any |} other MAE). Specifically, some of the things I would like to find out |} about are probably old hat to most of you, so if you could pass on some |} of your knowledge, it would be greatly appreciated.
The best place for info on the MAEs is from MFS, send mail to 'mae-info@mfst.com' with a similar request.
Since MAE-West is joint operated facility, you might also want to contact Lannce Tatman of AMES. They have pretty reasonable rates and several of the larger providers are there. This is advantagous since the link between MFS and AMES has been known to fail and you will want to keep your peerings up, right? lance@nsipo.nasa.gov -- --bill
Carl, Although MFS is a great source of answers for 1, 2 and 3. They are not a good source for 4 & 5. Since the goal of MFS at the Mae's (and rightfully so) is to make money, they will convince you that it will be a good choice. However, if you are a regional ISP, you can't get peering with most of the big NSPs without having a national network, and then even that may not be enough. Sprint's public policy that 3 DS3s, 24X7 NOC and DS3 backbone suffices for peering, but they have stopped all new peering until the end of summer, leaving Exodus, Compuserve and a few other large networks transitting through CIX and upstream providers. I believe that MCI Internet, ANS, UUNet and a few others have this policy, but will peer if you meet the minimum requirements. Since those networks together are probably 60% or greater of the routes on the Internet, how much of a use will this connection really be. Of course shortest-path out makes great theoretical policy. Why would you, as a local ISP, want your customer's traffic to be backhauled all the way to D.C. and back, just to get to someone down the street. What you'll have to do is weigh the high costs with the small benefit you will derive from joining Mae-West. http://www.mfs.net/MAE has all the current connections on the maes. I'd suggest reading it through and contacting a few of the ISPs and NSPs, gathering their policies and studying the benefits before making a very serious jump. Or at least look into spending a bunch of additional money buying transit services from AGIS or CRL. They both are in the business of servicing ISPs at the IXP level. Both with their own advantages and disadvantages. Robert Bowman Exodus Communications Inc.
Could some kind network operator out there, guide me to a FAQ or some other document with regards to interconnecting at MAE-West (or any other MAE). Specifically, some of the things I would like to find out about are probably old hat to most of you, so if you could pass on some of your knowledge, it would be greatly appreciated.
Some of the specifics:
1) Requirements for interconnect at MAE-West 2) Cost? 3) Minimum Line Speed 4) Transit? i.e. if the line is for backup purposes only, how can we arrange for transit, etc... 5) Peering agreements etc.
So if there is a document or set of documents that have this info in them, if someone could point me in the right direction, I'd surely appreciate it.
-Carl Forsythe carlf@mbay.net
-- ===================================================================== Carl Forsythe |Webmaster Monterey Bay Internet | carlf@mbay.net | http://www.mbay.net | =====================================================================
Robert bowman wrote: Or at least look into spending a bunch of additional money buying transit services from AGIS or CRL. They both are in the business of servicing ISPs at the IXP level. Why would you buy transit from either AGIS or CRL if you could also buy it from MCI, ANS, Sprint or UUNET? Are you saying that if one of these big players has a moretorium on peering, it also does not do transit? ********************************************************************** The COOK Report on Internet Individ. hard copy $150 431 Greenway Ave, Ewing, NJ 08618 USA Small Corp & Gov't $200 (609) 882-2572 phone and fax Corporate $350 Internet: cook@cookreport.com Corporate Site Lic. $650 http://pobox.com/cook/ for new report: "Tracking Internet Infrastructure" ***********************************************************************
ISPs, to the best of my knowledge and also due to Exodus' attempts in the past, cannot buy transit from either UUNet or MCI at an IXP. Maybe they have changed in the past 3-4 weeks, but when we were researching how to get those pesky Sprint routes (due to their lack of new peerings), we had to cross MCI & UUnet off the list, as they do not do it. We didn't bother researching it with Sprint. ANS does do it I believe. Better have reps from each of these places speak rather than myself making assumptions. What I was attempting to get at wasn't plugging AGIS and/or CRL. I was making a point about regional ISPs joining the MAEs. A lot of small ISPs think that a DS3 to Mae-West or Mae-East is a DS3 to the Internet. When realistically it is just the beginning. Rob
Robert bowman wrote: Or at least look into spending a bunch of additional money buying transit services from AGIS or CRL. They both are in the business of servicing ISPs at the IXP level.
Why would you buy transit from either AGIS or CRL if you could also buy it from MCI, ANS, Sprint or UUNET? Are you saying that if one of these big players has a moretorium on peering, it also does not do transit?
********************************************************************** The COOK Report on Internet Individ. hard copy $150 431 Greenway Ave, Ewing, NJ 08618 USA Small Corp & Gov't $200 (609) 882-2572 phone and fax Corporate $350 Internet: cook@cookreport.com Corporate Site Lic. $650 http://pobox.com/cook/ for new report: "Tracking Internet Infrastructure" ***********************************************************************
On Sat, 6 Jul 1996, Gordon Cook wrote:
Robert bowman wrote: Or at least look into spending a bunch of additional money buying transit services from AGIS or CRL. They both are in the business of servicing ISPs at the IXP level.
Why would you buy transit from either AGIS or CRL if you could also buy it from MCI, ANS, Sprint or UUNET? Are you saying that if one of these big players has a moretorium on peering, it also does not do transit?
Well, you may not want to get it form MCI, ANS, or UUNET because they would peer with you, but will not peer with customers. This is where we are at right now, we are building a full clear channel DS3 network, and have a T1 right now into MCI for people we don't peer with. MCI is now ready to peer, but will not until we ditch the T1 we have. We don't want to go with UUNET or ANS because that would kill peering with them. So our only choice is a smaller NSP that has Sprint peering but not a lot of net traffic so it would not kill us not to peer, or Sprint. P.S. I am looking for a copy of Sprints peering contract, if you have it and want to share that would be great. So far I have had problems getting it form Sprint. Nathan Stratton CEO, NetRail, Inc. Tracking the future today! --------------------------------------------------------------------------- Phone (703)524-4800 NetRail, Inc. Fax (703)534-5033 2007 N. 15 St. Suite 5 Email sales@netrail.net Arlington, Va. 22201 WWW http://www.netrail.net/ Access: (703) 524-4802 guest --------------------------------------------------------------------------- "Therefore do not worry about tomorrow, for tomorrow will worry about itself. Each day has enough trouble of its own." Matthew 6:34
On Sat, 6 Jul 1996, Gordon Cook wrote:
Robert bowman wrote: Or at least look into spending a bunch of additional money buying transit services from AGIS or CRL. They both are in the business of servicing ISPs at the IXP level.
Why would you buy transit from either AGIS or CRL if you could also buy it from MCI, ANS, Sprint or UUNET? Are you saying that if one of these big players has a moretorium on peering, it also does not do transit?
One more thing, that reason we and a lot for others don't go with the last logical choice (why not they will not peer until end of summer) is that they will only sign a 1 year contract. They will also not peer with customers, so getting a connection into Sprint to get Sprint routes is a bad idea. You move from not being able to peer for a few months to not being able to peer for a year. Nathan Stratton CEO, NetRail, Inc. Tracking the future today! --------------------------------------------------------------------------- Phone (703)524-4800 NetRail, Inc. Fax (703)534-5033 2007 N. 15 St. Suite 5 Email sales@netrail.net Arlington, Va. 22201 WWW http://www.netrail.net/ Access: (703) 524-4802 guest --------------------------------------------------------------------------- "Therefore do not worry about tomorrow, for tomorrow will worry about itself. Each day has enough trouble of its own." Matthew 6:34
participants (6)
-
bmanning＠isi.edu -
Carl Forsythe -
Gordon Cook -
Jonathan Heiliger -
Nathan Stratton -
Robert Bowman