Pacific Northwest Gigapop NGN Overview Kampala, Uganda Oct. 16th - 17th 2007

Previous Architecture

Properties of Previous Architecture Primary/Secondary Layer-2 Core  Layer-2 core is actually required due to IBGP filtering and next-hop reachability requirements Different routing tables instantiated on different physical hardware Few 10 Gbps capable devices No formal Layer-2 service offering

Previous Routing Views Two Route Views  Full -- Containing:  Participants  R&E Peers  Internet2  NLR  Commodity Peers  Commodity Transit  Commercial -- Containing:  Participants  R&E Peers  NLR  Commodity Peers  Commodity Transit

Properties of Previous Routing Views Overlapping route types (e.g. Commodity Transit exists in both) Primarily differentiated by inclusion or exclusion of Internet2 routes Makes use of route servers for routing table aggregation Uses IBGP filtering for creation of additional routing tables (instantiated on different hardware)

Previous Layer-3 Services Full Participant  Contains: Participants, R&E Peers, NLR, I2, Com Peers, Com Trans  Built via unfiltered IBGP feeds from the “Full” route servers Commodity Participant  Contains: Participants, R&E Peers, NLR, Com Peers, Com Trans  Built via unfiltered IBGP feeds from the “Com” route servers R&E Participant  Contains: Participants, R&E Peers, NLR, I2, Com Peers  Built via filtered IBGP feeds from the “Full” router servers Internal Participant  Contains: Participants, R&E Peers, NLR, Com Peers  Built via egress EBGP filtering of the Commodity Participant view

Next Generation Network Architecture

Properties of Next Generation Architecture Layer-3 Routed Core Platform and topology agnostic routing tables  Any service on any router Almost all devices support 10 Gbps interfaces Core can migrate to 40 Gbps as needed Formal Layer-2 aggregation and grooming infrastructure Completely updated hardware  Support for up to 1.2 million IPv4 routes

Next Generation Network Routing Views Four Route Views  Commercial -- Containing:  Participants  Commodity Peers  Commodity Transit  Research -- Containing:  Participants  R&E Peers  Internet2 -- Containing:  Participants  Internet2  NLR -- Containing:  Participants  Internet2 Internet2 AUP is handled by inclusion/exclusion of INTERNET2 VRF GP participants themselves have control over which national research backbone they wish to send/receive traffic

Properties of Next Generation Network Routing Views No overlapping route types (except Participants which exist in both) Differentiated by external network connections with a research focus versus a non-research focus Uses MPLS Layer-3 VPNs to instantiate the two routing table views, anywhere in the topology on any platform Uses EBGP filtering to create additional routing table views on a per-participant basis

Next Generation Network Layer-3 Services Full Participant  Contains: Participants, R&E Peers, NLR, I2, Com Peers, Com Trans  Unfiltered EBGP feeds from both “Commercial” and “Research” VPNs Commodity Participant  Contains: Participants, R&E Peers, NLR, Com Peers, Com Trans  Unfiltered EBGP feed from the “Commercial” VPN  Filtered EBGP feed from the “Research” VPN (I2 filtered) R&E Participant  Contains: Participants, R&E Peers, NLR, I2, Com Peers  Filtered EBGP feed from the “Commercial” VPN (Com Trans filtered)  Unfiltered EBGP feed from the “Research” VPN Internal Participant  Contains: Participants, R&E Peers, NLR, Com Peers  Filtered EBGP feed from the “Commercial” VPN (Com Trans filtered)  Filtered EBGP feed from the “Research” VPN (I2 filtered)

Comparison of Layer-3 Participant Connectivity Models Existing route views are provide via one consolidated connection for all destinations NGN route views use two VPNs provisioned over separate logical links using 802.1q or Frame Relay Encapsulation

Next Generation Network Additional Features Commercial and Research VPNs are provided to the participant separately to allow for differential handling Layer-2 lightpath grooming can be provided with connectivity to PacificWave, NLR FrameNet, and Internet2 Intermediate Ethernet aggregation for shared access Layer-3 services

Thank You