Chicago NAP Update

Sprint, ANS, and MCI will all peer on an AADS FDDI initially. The Routing Arbiter will be there as well. The other customers will peer with this FDDI network via ATM, with the throughput problem as it exists. The current problem is believed to be the KENTROX ASDU. The current operational date for the FDDI is February 28,1995. The groups to be connected in addition to the NSF NSPs are AGIS, Alphanet, Databank, NETCOM, B3 and NET99. There has also been a query by WilTel. All of these customers may not be operational on February 28, 1995 (Sprintlink will not).

OC3c is supported now. T1 via frame relay will also be available. Additional co-location is coming at some unknown point in the future.

What happens if the ADSU can't be fixed?

Use another vendor.

Use Cisco AIP,but DS3 is not yet available.
Use OC3c and AIP which all works now.

If the ADSU is reliable...

Using VBR assumes throttle-back by end device. There is no backpressure in this configuration. Buffering in as many places would make this possible.

Hybrid Configurations

This would require a router run by AADS and this would enforce a routing policy. This is not a good thing, but it could work. Noone is crazy about this idea.

Are there alternatives?

Gigaswitch + co-location suggested -- Costly to AADS.
Wide Area FDDI is possible, but no easy transition to ATM.
FDDI over ATM? Performance and cost issues.

The crowd says that the goal is to make the Internet work, not to promote ATM.

What will AADS do? ...... There will be a SIG meeting for the customers of this NAP tonight.