1 / 11

MAE Evolution

MAE Evolution. Tom Bechly Internet Architecture and Technology. MAE ATM - Distributed Exchange Point. MAE-ATM East is a distributed exchange point 8100 Boone Blvd, Vienna – original MAE ATM site 12368 E. Sunrise Valley Drive, Reston (8/1) 21830 UUNet Way, Ashburn (10/16)

caesar-kline
Download Presentation

MAE Evolution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MAE Evolution Tom Bechly Internet Architecture and Technology

  2. MAE ATM - Distributed Exchange Point • MAE-ATM East is a distributed exchange point • 8100 Boone Blvd, Vienna – original MAE ATM site • 12368 E. Sunrise Valley Drive, Reston (8/1) • 21830 UUNet Way, Ashburn (10/16) • Additional site planned for 2001 • New Sites have ATM switches, co-location, and transport • Benefits of distributing MAE • Increased port, circuit, and co-location capacity • Improved resilience and diverse customer connections • MAE-ATM West additional site planned for 2001 MAE Evolution

  3. MAE ATM “Guaranteed” Service • Current MAE ATM is “Guaranteed” service • ABR service where PCR = 2*MCR • MCR can not exceed fixed percentage of access port speed • MCR for DS3 cannot exceed 50% of port speed (22.5 Mbps) • MCR for OC3 cannot exceed 33% of port speed (51.1 Mbps) • MCR of OC12 cannot exceed 25% of port speed (155.5 Mbps) • Total MCR cannot exceed access port speed MAE Evolution

  4. MAE ATM “Best Effort” Service • New “Best Effort” service (11/00) • ABR service with congestion control in core • MCR = 100 cells/second • PCR is set to fixed percentage of access port speed • PCR for DS3 is 100% of port speed (45 Mbps) • PCR for OC3 is 66% of port speed (99.22 Mbps) • PCR for OC12 is 50% of port speed (300.67 Mbps) • Total MCR cannot exceed access port speed • Service types can be mixed on same access port MAE Evolution

  5. MAE-FDDI East Status • MAE-FDDI East is being de-commissioned • MAE-FDDI East at 8100 Boone Blvd and at 1919 Gallows Road will be turned down on 2/28/01 • There is a FAQ on WWW.MAE.NET that covers the MAE East FDDI to ATM migration MAE Evolution

  6. MAE-FDDI West Status • MAE-FDDI West platform was upgraded • Enterasys SSR 8600 implemented at MAE West • Customers connections were migrated to SSR 8600 over period 9/16 thru 10/11 • DEC GigaSwitches at MAE West were powered down on 10/12 • There are no plans to de-commission MAE-FDDI West, at this time • No new customers will be added MAE Evolution

  7. Service Level View MAE Evolution

  8. Service Goals • Public Point of Presence for exchanging traffic • Equal and neutral access to exchange • Fair in that same rules and policies apply to all • Stable Service Interface • Protect shared resources • Enable users to manage Peering relationships • ISP-XXX wants to peer with all • ISP-ZZZ only peers with ISP-AAA • Exchange point leverages advanced technology MAE Evolution

  9. MAE Platform Evolution • Requirement for capacity in both bandwidth and port speeds will exceed current platform • Current architecture won’t scale indefinitely • Future requirement for OC48 access • Currently testing MPLS core with Frame Relay Interface • POS ports with Frame Relay encapsulation • Frame Relay DLCI mapped to LSP at core • Access speed of OC3, OC12, and OC48 MAE Evolution

  10. Frame Relay Interface (Pros) • Service provisioning is straightforward for both Customer and MAE • No routing information exchanged between MAE and CPE • MAE technology can change while preserving stable service level interface • Architecture can be extended to provide multi-service interface with no ATM cell tax • Customer CPE saving in both cost and space MAE Evolution

  11. Frame Relay Interface (Con’s) • Current Juniper implementation connects only alike interfaces (i.e. frame-relay-ccc to frame-relay-ccc) • Current Juniper implementation uses DLCIs from 511 to 1022 for frame-relay-ccc • Interworking with existing ATM (or any other) platform requires gateway MAE Evolution

More Related