From: Erik Sherk[SMTP:sherk@uunet.uu.net]
From: David Schwartz aka Joel Katz[SMTP:stimpson@stimpson.igc.net] Let's look at a hypothetical situation. ISP1 peers at MAE-E and buys transit from MCI there. Now they ask Sprint to peer with them. Let's look at how they reach sites on the west coast.
This is a violation of the rules of Mae-East: it is not to be used for customer connections. ISP1 must have a private connection to MCI.
Erik
Are you saying that MFS will not allow a private connection between two routers located at the MAE facility, even if the connection is _not_ made using the MAE FDDI switch, but is instead a direct (e.g. HSSI or AIP) connection between the two routers?? If so, I haven't seen any documentation to that effect... -- Jim Browning
From: Erik Sherk[SMTP:sherk@uunet.uu.net]
From: David Schwartz aka Joel Katz[SMTP:stimpson@stimpson.igc.net] Let's look at a hypothetical situation. ISP1 peers at MAE-E and buys transit from MCI there. Now they ask Sprint to peer with them. Let's look at how they reach sites on the west coast.
This is a violation of the rules of Mae-East: it is not to be used for customer connections. ISP1 must have a private connection to MCI.
Erik
Are you saying that MFS will not allow a private connection between two routers located at the MAE facility, even if the connection is _not_ made using the MAE FDDI switch, but is instead a direct (e.g. HSSI or AIP) connection between the two routers?? If so, I haven't seen any documentation to that effect...
MFS has nothing to do with this. The issue is using the shared Internet resource (namely the GIGA Switch) to connect customers. The original members of Mae-East aggreed to this when we set up the first peering sessions. The exchanges are for peer to peer traffic, not customer to vendor traffic. Erik
Are you saying that MFS will not allow a private connection between two routers located at the MAE facility, even if the connection is _not_ made using the MAE FDDI switch, but is instead a direct (e.g. HSSI or AIP) connection between the two routers?? If so, I haven't seen any documentation to that effect...
MFS has nothing to do with this. The issue is using the shared Internet resource (namely the GIGA Switch) to connect customers. The original members of Mae-East aggreed to this when we set up the first peering sessions. The exchanges are for peer to peer traffic, not customer to vendor traffic.
Note that this differs mightily from the DEC NAP that I've been helping to create down in Palo Alto. There are four GIGAswitches (two FDDI and two ATM) and it is very much expected that some folks will buy colocation space from DEC and cross-connect over to their transit provider du jour. Someone who just wants to put their servers close to the "backbone" should not and will not be connected to the public GIGAswitches. Running transit routers and doing all the BGP and RADB work to get peering working and keep it working is much too complicated for the average server owner.
On Sat, 11 May 1996, Paul A Vixie wrote:
Are you saying that MFS will not allow a private connection between two routers located at the MAE facility, even if the connection is _not_ made using the MAE FDDI switch, but is instead a direct (e.g. HSSI or AIP) connection between the two routers?? If so, I haven't seen any documentation to that effect...
MFS will allow this in MAE EAST I am aware of. However the connecting circuit (eg. ethernet or FDDI cable) has to be provisioned by MFS and a monthly cross-connect fee. --- Stephen Balbach "Driving the Internet to Work" VP, ClarkNet due to the high volume of mail I receive please quote info@clark.net the full original message in your reply.
participants (4)
-
Erik Sherk -
Jim Browning -
Paul A Vixie -
Stephen Balbach