1. Copyright 2007 CENIC and PNWGP TransitRail: Nationwide Commodity Peering Program February 12, 2007 Minneapolis, MN

2. Copyright 2007 CENIC and PNWGP Premise Successful large-scale commodity Peering can...  Decrease commodity costs and result in overall savings  Reduce reliance on commercial vendors  Increase routing efficiency and flexibility Successful large-scale commodity Peering can...  Decrease commodity costs and result in overall savings  Reduce reliance on commercial vendors  Increase routing efficiency and flexibility

3. Copyright 2007 CENIC and PNWGP TransitRail Is...  NATIONWIDE  Multiple exchange locations around the US;  COMMODITY  packet-agnostic  Connections at commercial peering exchange points;  PEERING  Direct network-to-network bilateral IP Packet exchange  NATIONWIDE  Multiple exchange locations around the US;  COMMODITY  packet-agnostic  Connections at commercial peering exchange points;  PEERING  Direct network-to-network bilateral IP Packet exchange

4. Copyright 2007 CENIC and PNWGP TransitRail Goals Build a robust and reliable network focused on serving the commodity demands of research and education networks; Reduce the overall cost and reliance on traditional Internet transit services; Operate on a cost-recovery, sustainable basis. Build a robust and reliable network focused on serving the commodity demands of research and education networks; Reduce the overall cost and reliance on traditional Internet transit services; Operate on a cost-recovery, sustainable basis.

5. Copyright 2007 CENIC and PNWGP What to Expect TransitRail participants are likely to experience anywhere from a 25% to 60+% reduction in the overall traffic that normally goes over their commodity ISP circuits.

6. Copyright 2007 CENIC and PNWGP CENIC Experience Commodity only - no R&E

7. Copyright 2007 CENIC and PNWGP Who  CENIC and Pacific Northwest Gigapop are jointly developing, and implementing the TransitRail facility;  These groups have significant individual and joint experience with peering facilities and prospective peering partners;  Working with NLR who is providing the underlying network infrastructure.  CENIC and Pacific Northwest Gigapop are jointly developing, and implementing the TransitRail facility;  These groups have significant individual and joint experience with peering facilities and prospective peering partners;  Working with NLR who is providing the underlying network infrastructure.

8. Copyright 2007 CENIC and PNWGP Trial Phase Success  Phase 0 (trial) success  No cost to participants  CENIC, PNWGP shared subset of peers  Helped FRGP defer/avoid adding additional transit capacity, noticeably improved latency  Helped OneNet relieve severe congestion on transit links, estimated ~200Mbps, actual ~500Mbps  Phase 0 (trial) success  No cost to participants  CENIC, PNWGP shared subset of peers  Helped FRGP defer/avoid adding additional transit capacity, noticeably improved latency  Helped OneNet relieve severe congestion on transit links, estimated ~200Mbps, actual ~500Mbps

9. Copyright 2007 CENIC and PNWGP Current Status  West Coast peering transition complete  Los Angeles, Sunnyvale, Seattle on-line  12 Gbps of peering capacity  Washington DC connected  14 Gbps of additional peering capacity in provisioning  Chicago - Signing IRU contract  Equipment received and waiting  West Coast peering transition complete  Los Angeles, Sunnyvale, Seattle on-line  12 Gbps of peering capacity  Washington DC connected  14 Gbps of additional peering capacity in provisioning  Chicago - Signing IRU contract  Equipment received and waiting

10. Copyright 2007 CENIC and PNWGP TransitRail Participants  Seven participants connected  CENIC  Front Range GigaPOP (UCAR)  LEARN (North Texas GigaPOP and Univ of Texas)  OneNet  Pacific Northwest GigaPOP  Pittsburgh Super Computer  Three participants in progress  ENA, MERIT, NCREN  Seven participants connected  CENIC  Front Range GigaPOP (UCAR)  LEARN (North Texas GigaPOP and Univ of Texas)  OneNet  Pacific Northwest GigaPOP  Pittsburgh Super Computer  Three participants in progress  ENA, MERIT, NCREN

11. Copyright 2007 CENIC and PNWGP TransitRail Growth  FRGP is adding 2nd GE to TransitRail

12. Copyright 2007 CENIC and PNWGP Infrastructure  Equipment (CISCO 7600s)  Maintenance - 4 hr on site  10GE WaveNet between routers  Redundant loops to exchange facilities  FrameNet backup links between routers  New autonomous system (11164)  Restrictive peering policy to maximize return  Equipment (CISCO 7600s)  Maintenance - 4 hr on site  10GE WaveNet between routers  Redundant loops to exchange facilities  FrameNet backup links between routers  New autonomous system (11164)  Restrictive peering policy to maximize return

13. Copyright 2007 CENIC and PNWGP Seattle (Westin Bldg) Sunnyvale Los Angeles (Equinix LAP) DC Chicago PAIX 1 Wilshire Equinix LAX Equinix Ashburn Equinix TransitRail - Phase 1

14. Copyright 2007 CENIC and PNWGP Routing Policies  What TransitRail requires of its peers  3-5 locations throughout US  Large amount of traffic exchanged per peer  Reliable Operations  What TransitRail requires of its peers  3-5 locations throughout US  Large amount of traffic exchanged per peer  Reliable Operations

15. Copyright 2007 CENIC and PNWGP Routing Policies  What TransitRail requires of its peering participants  Structured local preference  Maintained IRR object  Willingness to tune announcements to L3/Wiltel/C&W (to attain highest amount of usage)  What TransitRail requires of its peering participants  Structured local preference  Maintained IRR object  Willingness to tune announcements to L3/Wiltel/C&W (to attain highest amount of usage)

16. Copyright 2007 CENIC and PNWGP Business Side  Cost recovery model  NOC support through PNWGP & CENIC  Future upgrades, additional peering locations, will be decided with participants  Per port pricing model  Cost recovery model  NOC support through PNWGP & CENIC  Future upgrades, additional peering locations, will be decided with participants  Per port pricing model

17. Copyright 2007 CENIC and PNWGP TransitRail Support Model Peer Relationships: Level1 support to peers Maintenance Events Interconnect Outages DoS Response Peer contacts Operational EngineeringCustomer SupportTools Customer Facing: PacificWave Speedometer Backbone Interface Trends Ping and Traceroute Looking Glass Customer Reporting: Netflow capture Data processing Report generation Call Center: Customer contacts Trouble Ticket System Detailed Problem Description Abuse Handling Network Outage Monitoring: Customer connections Customer Maintenance Events NLR FrameNet Links TR Backbone Links Troubleshooting: Level2 to Customer Support Testing and Data collection Problem Mitigation TR Access Links Internal: Inventory/Asset Tracking TACACS, RANCID Syslog, Swatch, Cricket TR Planning Tools Management Collocation contracts Peer contracts Customer contracts Customer billing Accts Payable/Receivables Configuration/Design: Address assignment Router configuration Change control TR Access Changes Network Architecture Sr. Technical Staff Technical Escalation Point Capacity Planning Architecture Long term: Routing Changes Customer and Peer Relations

18. Copyright 2007 CENIC and PNWGP Thank you http://www.transitrail.net info@transitrail.net