Growing Pains: The Internet in Adolescence

1. Growing Pains:The Internet in Adolescence Fred Baker ISOC Chairman of the Board

2. Brief History of the Internet Comic Book to Cyberspace

3. Len Kleinrock, 1962 The strength of a chain is its weakest link The strength of a web is its surviving path Datagram Switching Developed at UCLA+Xerox PARC DARPA Funding Datagram Switching

4. Early commercialization Source: http//www.telstra.net/ ops/bgptable.html Killer Applications: Early Business Adoption Borderless Business Mail, FTP, Archie, Network News Consumer Adoption Multi-player Games WWW, IRC Projected routing table growth without CIDR/NAT Moore’s Law and NATs, with aggressive address conservation policy, make routing work today Deployment Period of CIDR

5. Marketing rushes in where engineering fears to tread • Internet bubble: • “Build it and they will come” • “New Economy” where profitability is irrelevant • “.com” era

6. Profitability… • …The Final Frontier. • These are the voyages of the IETF: • It's mission: • To create strange new worlds... • To seek out new life, and new technology... • To Boldly Go Where No I-Geek Has Gone Before.

7. Status of Internet Technology in developed nations • A utility: • Water, Sewer • Electricity, Natural Gas • Telephone • Internet • Internet access and facility is assumed in education, business, and increasingly in society

8. The Digital Divide • “In addressing the digital divide, Uganda and other countries in the region face three broad challenges: • Creating and exploiting access to external information resources; • Creating internal information resources; • Creating and exploiting access to internal information resources. • A common underlying factor that cuts across the three broad challenges is the need for a competent human resource.” Dr. F. F. Tusubira Makerere University, February 2003

9. Telephones/Point to Point Need an address when you call them, and are therefore servers in private realm For web: Sufficient to have clients in private address spaces access servers in global address space Client/Server Architecture is overtaken by events Private Address Realm Global Addressing Realm Private Address Realm

10. Who are today’s application innovators? • Open Source example: Freenet/KaZaA • Large-scale peer-to-peer network • Pools the power of member computers • Create a massive virtual information store • Open to anyone • Highly survivable, private, secure, efficient, • http://www.firenze.linux.it/~marcoc/index.php?page=whatis

11. History of the IETF

12. Originally supporting Research Networks • Dates: • Started 1986 • Non-US participation by 1988 • First non-US meeting: Vancouver, August 1990 • Constituents: • Originally US Government only • Added NSFNET (NRN), education, research • Eventually added vendors • The government left… • International participation

13. Characterizing the community: • Semi-homogenous • People largely knew and trusted each other • “Netiquette” • Anti-social behavior drew direct and public censure as “impolite” • Key interest: • Making the Internet interesting and useful for themselves and their friends.

14. IETF Mission Statement • Make the Internet Work • Whatever it takes… • But what is the Internet? • IPv4? IPv6? MPLS? • Applications like WWW? Mail? VoIP?

15. End to End principle Robustness principle Rough Consensus and Running Code Institutionalized altruism Trust Highly relational Principle of least surprise Openness Anti-kings Achieving “right” results because they are right Historical principles

16. Now supporting all IP-based Networks • Constituents: • Researchers • Network Operators • ISP, NRN, Enterprise • Vendors (large percentage of attendees) • Interactions with various governments… • Fully international participation

17. Characterizing the community: • Heterogeneous • Business reasons for involvement • “Netiquette” • Expectation of safe environment • More based on rules than personal • Key interest: • Defining technology to use or to sell

18. Present principles • Business agenda • Business relationships rather than personal relationships • Political process • Managed Trust: “Trust but verify” • Intellectual Property Issues • About protecting ideas, not sharing them • Civil servants as leaders

19. IETF: in a maze of twisty passages – all different

20. What makes IETF hard? • Lack of trust: • Community sees leaders as a cabal • Leaders see community that designs for narrow scope of applicability or misses key issues • Opaque processes promote questions • RFC Editor • Secretariat • Internet Assigned Number Authority • Internet Engineering Steering Group • Internet Architecture Board

21. What makes IETF hard? • Consensus process • Lack of comment interpreted as consent, but may mean loss of interest • Expectation that “the working group” or “the IETF” should do something: • IETF composed of people, and people do the work

22. The possibilities are exciting

23. Specific issues IETF is dealing with

24. Status of change efforts within the IETF • Structural discussion organized in two phases: • Identify what the problems are (the Problem WG) • Address the problems • Multiple efforts, with individual lifetimes, control patterns and agendas. • Document management processes key to managing work flow

25. IETF Mission: a shared viewpoint? • The logical response to this: • formulate the IETF's mission in terms that the community can agree with. • The Problem WG design team working on a proposal • What is needs to say: • “The IETF makes the Internet work” • The internet consists of SOHO, Enterprise, and provider networks

26. Effective Engineering Practices • Engineering practices not necessarily well designed • Proposals: • COACH BOF explored possible practices, but no clear proposals • SIRS experiment seeks to get experienced review

27. Handling Large and/or Complex Problems • Thought across areas and in architecture required. • IAB responsible for architectural thought • SIRS experiment intended to bring more cross-area review. • No current activity focused on changing how we handle large and/or complex problems.

28. Three stage standards hierarchy not (properly) utilized • Most of today’s internet runs on: • Proposed Standards • First stage standards • Not necessarily tested for interoperability • Best Current Practices • Policies • Informational documents • Example: PPPOE

29. Workload Exceeds the Number of Fully Engaged Participants • Suggestions to increase motivation for participants have been floated. • But perhaps this is OK?

30. IETF Management Structure vs. Complexity of the IETF • IESG task seems to have accreted too much effort • Management and Quality Assurance • An Advisory Committee discussing business relationships

31. Education issues • Concern: • Working Group process does not always lead to closure • IETF Participants and Leaders Inadequately Prepared • Closure is often reachable if desired • Not obvious that it is always desired

32. The EDU Team • Training programs: • Working Group Chairs • Documents Editors • EDU Team trains • It doesn’t generally suggest changes

33. The IESG is rapidly approaching a solution

34. Sounds like bad news • Not really • The IETF is just deciding what it wants to be when it grows up… • Quite a bit of good work going on there • Other groups of interest • NANOG, Apricot, RIPE, etc • Many others

35. What is next for the Internet?

36. High-end research backbones • Combining IP routing and optical routing in overlay networks • “Designer networks” for research purposes • Production networks for applications • What parts of network to research? • Routing (IP, Optical) • Applications • IPv6-based

37. 10GE STM-64/OC-192 STM-16/OC-48 GE 建議電路 Optical Production Research Production Backbone

38. 10GE STM-64/OC-192 STM-16/OC-48 GE 建議電路 Optical Production Research Research Backbone

39. 電路數量 (#) 10GE STM-64/OC-192 STM-16/OC-48 GE 建議電路 Optical Production Research Optical Network (2) (2) (2) (2) (6) (2) (2) (6) (6) (3) (3) (2) (2) (4) (2) (2) (2) (2) (2)

40. Proposed UN-FAO “Growing Connection”: Ghana 384 KBPS Or E1 Internet Long distance IEEE 802.11 Database.library.de Village.school.gh several PCs + Router Village.school.gh several PCs + Router Village.school.gh several PCs + Router 40 40 40

41. “Enterprise” infrastructure network Connects roaming devices which themselves form the infrastructure Neighbor relationships change randomly in routing Not appropriate as backbone Fundamental issue: Not “can I find the addressed device/prefix in my network”, but “Is there a usable route to the addressed device/prefix.” Manet looks at a mobile infrastructure 41 41 41

42. We trust people to access servers and do limited operations on them As a result, we limit our applications by the power of the servers we run them on Today’s Client/Server access control 42 42 42

43. Let everyone talk Distributed computing Peer computers to perform function, not server Central Authentication/ Authorization Access control Accountability Peer-peer access control model 43 43 43

44. What needs to change? • Effective prophylactic security • Addressing systems behind firewalls • Firewall ≠ Network Address Translator • Secure Firewall Traversal • Next-generation-Kerberos style interaction control servers • Good point-to-point application software and models (Freenet/KaZaA?)

45. “As new IP communications services and devices become available, they may stimulate new demand and increase VoIP traffic flows beyond the growth rates characteristic of the traditional voice telephony market. … the total market may reach … six percent of the world's forecasted international traffic for the calendar year 2001” Telegeography 2002 45 45 45

46. Voice/Video on IP networks Billing/ Authorization Control Plane Data Path

47. Video on Demand… Internet Router located in the POP Video-on-demand Server located in the POP 100-baseT to Home Carrying multiple Video streams plus Voice and data

48. Growing Up… • Profitability… • User-friendly applications… • Manageable applications and networks • Convergence…

49. Growing Pains:The Internet in Adolescence Fred Baker ISOC Chairman of the Board