NSFNET: The T1 The Internet Comes of Age

Transcription

1 NSFNET: The T1 The Internet Comes of Age November 29, 2007 Eric Aupperle, Rick Boivie, Paul Bosco, Hans-Werner Braun, Mathew Dovens, Mark Knopper, Yakov Rekhter, Walter Wiebe, Jessica Yu

2 NSFNET & The Evolution of Routing Technology Jessica (JieYun) Yu Merit Network Inc. (Formerly) University of Irvine (Currently) Nov. 29 th, 2007

3 Pioneering New Routing Technology and Architecture New routing architecture: Separation of Interior routing from exterior routing New routing protocol: IS-IS Evolution from EGP to BGP

4 Tackling The Routing Scaling Challenges Routing scaling challenges with the fast growth of NSFNET Routing table doubled every 10 months Classful routing does not scale Classless Internet Domain Routing (CIDR) developed

5 Registered IPv4 Address Allocation History Graph source: online

6 Summary The NSFNET backbone directly contributed to the advancement of routing technology in the Internet: First deployed IS-IS and BGP CIDR development and deployment It was a very unique experience to work on the NSFNET from the very beginning I am very proud of having been part of the team

7 NSFNET: The T1 IBM Overview Walter Wiebe

8 Partner Appreciation & Background IBM ACIS & Communications Joint Studies: CMU Andrew File Server & Campus LAN U of WI VM TCP/IP U of MD DOS TCP/IP Yale LAN/ASCII Gateway Cornell Theory Center / Supercomputer Brown Hypermedia/Computer aided Learning U of M Institutional File Server ACIS related projects: BSD 4.2 Unix for IBM 370 including TCP/IP stack AOS 4.2 and 4.3 (BSD Unix for the IBM RT/PC) o Including TCP/IP stack and h/w and s/w for ethernet and token ring TCP/IP training workshop 4-86 TCP/IP workshop at U of MD in fall of 86 Laureate Series Announced April 1987 VM/TCPIP DOS/TCPIP 8232 Channel to LAN LAN ASCII Gateway Almaden, Yorktown, Kingston, Poughkeepsie, Manassas, Raleigh - R & D collaboration teams

9 T1 NSFNET Key Reviews & Dates NSFNET Project Solicitation IBM reviews: Gomory, Krowe, Goldberg, Lucente Proposal submitted by Merit IBM & MCI as Joint Study partners Simulated backbone network running in Milford lab Contract to develop and manage the NSFNET awarded to Merit MCI & IBM Test network lines planning 1-88, initial HW 02-87, test plan 03-88, order parts 3-88(3488 total) Sys test 5-88, test tools at 13 nodes 5-88, 3,488 parts at AA assm. Depot NSS installs at 13 nodes 6-88 NSFNET goes live New T1 network designed, developed, tested, deployed and cutover in 7.5 months. We have seldom seen a major networking project come off so smoothly and never one of such magnitude despite being new, complex, innovative line speeds an order of magnitude faster & heavy loads 8-88 Letter from FARNet to E. Aupperle

10 T1 NSFNET Key Reviews & Dates (cont.) 9-88 Interop NSS connects show net to NSFNET. 1 st. First demo of packet video Upgrade to full T1 & NSF Program review rates the performance of the network and partnership Outstanding CA*net(the Canadian national backbone largely patterened on the NSFNET comes on line NSFNET named Foundation for NREN - High Performance Supercomputing Act Upgrade to all Smart cards & full T3 & FDDI 5-92 NSFNET decommissioned An amazing set of experiences & important example of what can be accomplished with cooperation & collaboration between Academia, Gov t and Industry focused on overlapping goals that allowed everyone access & services of the global network.

11 The Nodal Switching System Rick Boivie November 29, 2007

12 June, 1987 It is anticipated that over the next 5 years, NSFNET will reach more than 10,000 mathematicians, scientists and engineers at 200 or more campuses and other research centers. From the 1987 NSF Project Solicitation

13 T1 NSS (1.5 Mb/sec links) IBM RT/PC s w AOS 4.3 (BSD 4.3) Token rings T1 DSU/CSU PSP RCP T1 DSU/CSU PSP T1 DSU/CSU PSP E-PSP Ethernet Flexibility, Scalability, Handled 20%/month traffic growth

14 T1 NSFNET Seattle, WA Ann Arbor, MI Ithaca, NY Palo Alto, CA Salt Lake City, UT Boulder, CO Lincoln, NE Pittsburgh, PA Champaign, IL Princeton, NJ College Park, MD San Diego, CA Atlanta, GA Houston, TX We have seldom seen a major networking project come off so smoothly and never one of such magnitude -- FARnet, 1988

15 EASInet & CAnet NSFNET routers were also used in EASInet (Europe) and CA*Net (Canada) En Fevrier 1990, la premiere liason Internet transatlantique fonctionnant a un debit de 1,5 million de bits par seconde etait mise en service entre le CERN et l'universite de Cornell sur la cote est des Etats-Unis. -- Histoire Europeenne du WEB

16 T3 NSS (45 Mb/sec links) IBM RS/6000, AIX, Deep Adapters Microchannel T3 DSU/CSU RS/960 CPU T3 DSU/CSU RS/960 T3 DSU/CSU RS/960 RS/960 FDDI Disruptions on one link or route should not impact - Autonomous network adapters unaffected routes - Direct card-to-card transfers - New systems, new chips, new adapters, same architecture -Able to handle the 50,000,000 user, 50,000 net Internet of 1995 (far exceeeding NSF s original goals)

17 T3 NSFNET Seattle, WA Palo Alto, CA Salt Lake City, UT Boulder, CO Argonne, IL Lincoln, NE Ann Arbor, MI Ithaca, NY Pittsburgh, Urbana PA Champaign, IL Cambridge, MA Princeton, NJ College Park, MD San Diego, CA Atlanta, GA 50,000,000 users! 50,000 CIDR networks! 93 countries! Far exceeding original requirements Houston, TX IBM did much of the engineering for NSFNET and performed superbly in that activity. We have thought deeply about whether there is another company which we would trust to do this very important job, and we have come up empty. - Back on Track to the NII?, Directors of WestNet, 1996

18 De Tocqueville on Communications & Communications in Michigan I know but one single means of increasing the prosperity of a people that is infallible in practice and that I believe one can count on in all countries as in all spots. This means is naught else but to increase the ease of communications between men... America, which is the country enjoying the greatest sum of prosperity ever yet accorded a nation, is also the country which, proportional to its age and means, has made the greatest efforts to procure the easy communications I was speaking of. In the Michigan forests there is not a cabin so isolated, not a valley so wild, that it does not receive letters and newspapers at least once a week; we saw it ourselves. -- Democracy in America, Alexis de Tocqueville, 1835

19 A More Recent Quote It s clear that the Internet is nothing less than the single most powerful tool we have ever seen for driving business, economic and societal change. Lou Gerstner, former Chairman of IBM

20 NSFNET Intelligent Network Adapters and Reflections Paul Bosco November 29, 2007

21 Reflections on NSFNET Public/Private Partnering NSF/University/Corporate Teamwork Regional/National/International Teamwork Time to Scale/Market Acceleration Research & Development Teams Operational & Management Teams Innovation/Standards Leadership Innovation (IP Routing, Systems,...) Standards (IETF Process, ) Technology/People Transfer Vendors (Cisco, Juniper, ) Operators (AOL, Comcast, )

22 Reflecting on NSFNET 1. Extraordinary Growth Could we possibly need memory for 500 routes someday? Phone system traffic grows at 8%/year, let s plan for 20%/year 2. Application Changes From Remote Access (ex: Super-Computer) To Collaboration (ex: & ftp) 3. Standards Challenges IP vs OSI & ATM 4. Foundation for Success The Web IP Everywhere

23 NSFNET Inter-domain routing Yakov Rekhter

24 In the beginning (1989) January 1989, 12 th IETF TNP ( three napkins protocol ) Produced over lunch by Y. Rekhter (at that time with IBM Research) and K. Lougheed (Cisco) Spring 1989 two interoperable implementations NSFNET/IBM Cisco June 1989 RFC1105 A Border Gateway Protocol (BGP)

25 In the beginning (1989)

26 In the beginning BGP design goals Overcome limitations of EGP-2: eliminate restriction on inter-domain topology to be spanning tree (with ARPANET as a root) eliminate problems caused by IP fragmentation of EGP-2 updates Support few thousand classful IPv4 routes Replace EGP-2 in the NSFNET Backbone Was positioned as a short-term solution, to be (eventually) replaced by a long-term solution

27 18 years later (2007) Four versions (and numerous extensions) later BGP remains the sole inter-domain routing protocol in the Internet Supports Classless Inter-Domain Routing (CIDR) Carries ~240,000 IPv4 routes (as of November 2007) Supports IPv6 inter-domain routing BGP usage extends well beyond inter-domain routing in the Internet: BGP/MPLS VPNs (aka 2547 VPNs), BGP-based VPLS, etc BGP is a widely successful protocol, as it far exceeds its original goals both in terms of scale (being deployed on a scale much greater than originally envisaged), and in terms of purpose (being used in scenarios far beyond the initial design).

28 Lessons learned Short-term solutions tend to stay for a long time; long-term solutions tend to never happen Good Enough solutions are sufficient; Perfect solutions may not be necessary Focus on solving practical problems in real time emphasis on engineering Meet market needs and accommodate technical progress by focusing on flexibility and extendibility Tightly couple evolution and further development with the operational experience and feedback from the service providers