Internet Standardization and the IETF

1. Internet Standardization and the IETF Fred Baker IETF Chair

2. Thoughts I would like to address • IETF History, Structure, and Procedure • Who’s who in the IETF • Relations among standards bodies • Who does what and why • The big problems in the Internet • Ongoing work • How we’re going to solve them

3. IETF History 3

4. Internet Engineering Task Force (IETF) • Historical developer of internet-related protocols • http://www.ietf.org • Consortium of individuals from • Research, • Education, • Network operators, and • Internet vendors

5. 500 0 -500 Changed IETF composition and roles 2500 2000 1500 Research/Education primarily US Attendance 1000 Vendor/International 1 4 7 10 13 16 19 22 25 28 31 34 37 40 43 46 IETF Number Actual Avg..

6. Principle for placement of meetings: “If I am doing the work, the meeting should sometimes be in my neighborhood” But most work is done on mailing lists anyway… Non-US Meetings: 1990: Vancouver 1993: Amsterdam 1994: Toronto 1995: Stockholm 1996: Montreal 1997: Munich 1999: Oslo 2000: Adelaide Growth of international involvement in IETF

7. December 1996 11 Countries July 1999 33 Countries IETF Growth by Country Netherlands Italy Other Germany Sweden Other 2% 8% 3% 1.9% 1.8% 5.5% France Canada 2.0% 3% Netherlands 2.2% France USA Canada 4% 3.1% 48% JAPAN Finland UK USA 7.6% 4.2% 71.6% 4% Germany 5% Norway Sweden Japan UK 5% 6% 6% 6%

8. IETF Structure 8

9. IETF structures and key forums • Internet Architecture Board • Internet Engineering Steering Group • Working groups in eight areas

10. Internet Architecture Board (IAB) • Mission • “Supreme court” on appeals of IESG decisions • Think tank for future internet activities • Recent activities • Really worried right now about • End to end model of the internet • Impact of wireless communications

11. Internet Engineering Steering Group (IESG) • Mission • Assure open-ness and adherence to process • Working group chartering and management • “Quality assurance” on specifications • Activities and trends • Currently drawn into a “privacy” debate • Better addressed in area activities

12. Internet Routing Transport Applications Security Network operations and management User services General Working groups in eight areas

13. Internet • Mission • IP/foo specifications • Interface configuration and management • IP developments, mostly IP6 • 15 working groups • Interface mibs, dnsind, dhcp, ipng, IP/cable|ADSL|IEEE 1394, PPP, ion, ...

14. Routing • Mission • “So how does a packet get there, anyway?” • 17 working groups • BGMP, MPLS, MSDP, manet, vrrp, bgp, ospf, idmr, SNA...

15. Transport • Mission • QoS management • End to End delivery issues • Telephony issues • 22 working groups • Diff-serv, int-serv, megaco, sigtran, audio/video, rap, ...

16. Applications • Mission • Infrastructure applications development and extension • Historical applications • 26 working groups • Web, LDAP, edi, nntp, smtp, ftp, telnet, calendaring, mime, etc.

17. Security • Mission • Developing procedures and protocols to enhance security in the internet • 15 working groups • Ipsec, pki, transport layer security, web transaction security, pgp, one time password, etc...

18. Network Operations and Management (O&M) • Mission • Making sure there is operational clue looking at the specifications and procedures • Network management (used to mean SNMP) • Making those two talk with each other • Y2k • 20 working groups • Snmpv3, policy, various mibs, agent extensibility... • Ngtrans, year2000, mbone deployment, routing policy system, ...

19. User Services • Mission • Provide documentation of IETF procedures to less involved communities • 4 working groups • Responsible use of the net • Web elucidation of internet-related developments • FYI updates • User services

20. General • Mission • If we can’t think of another place to put it, it goes here • 1 working group • Poisson: standing rules committee

21. Working group summary • We have ~120 working groups • Not all currently active • Cover support of infrastructure for the commercial IP internet • Not too worried about research network, unless they use the same technology

22. IETF Process 22

23. Membership • IETF members are people • As opposed to nations or companies • Communications tend to be among people • As opposed to working groups, boards, etc.

24. “ ” Fundamental working principle We do not worry about presidents and kings; We work by rough consensus and running code Dr. David C. Clark, Massachusetts Institute of Technology

25. Two types of documents • Internet Drafts • RFC - “Request for Comments”

26. Internet Drafts • Most analogous to ITU “contributions” and “working papers” • Not necessarily work items • Half of all internet drafts are simply documents people have chosen to post • Types of drafts • Working Group documents • Submissions to working groups • Individual Submissions

27. Historical Archive Many kinds of documents Informational Historical Experimental Standards Standards Proposed, Draft, Full Best Current Practice RFCs

28. Development Process • Bottom-up • WG charters developed to support work people want to do • Development Process • Working groups develop • IESG reviews • RFC Editor publishes

29. Relations among standards bodies “Anyone who likes legislation or sausage should watch neither one being made” Baron von Bismarck 29

30. ITU-T IEEE ETSI W3C IETF Various marketing fora ATM Forum ADSL Forum MPLS Forum etc... Historical role of various standards bodies

31. Institute of Electrical and Electronics Engineers (IEEE) • Primarily link layer LAN standards • http://ieee.org/ • Especially LAN standards in 802 series • IEEE 802.1 Bridging • IEEE 802.3 CSMA/CD Networks (Ethernet) • IEEE 802.5 Token Ring Networks

32. European Telecommunications Standards Institute (ETSI) • European Telephony Standards • http://www.etsi.org • GSM Telephones • WAP - Wireless Access Protocol

33. World Wide Web Consortium (W3C) • Primarily Web services • http://www.w3.org • Headed by Tim Berners-Lee, inventor of HTML • Developed HTML, XML, etc.

34. ITU Telecommunication Standardization Sector (ITU-T) • Primarily related to telephony • http://www.itu.int/ITU-T • Consortium of • Telephone companies • Their traditional vendors

35. Various connector standards X.21, V.35, etc. Physical/Link layer network standards X.25, Frame Relay, ATM, SDH Telephony on specific substrate H.32x/H.310 Specific collaboration: H.323 uses IETF Data format Points of possible overlap with IETF IP/SDH MPLS IP/ATM ISO JTC1 voice control IP Telephony call signaling ITU-T Developments

36. Some link layer PPP Network Layer IP4, IP6 Routing protocols Transport Layer TCP, UDP, RTP Security services Transport Layer Security, IPSEC, ISAKMP Telephony Signaling Signaling transport Quality support Differentiated Services Integrated Services IETF: Infrastructure protocols

37. SNMP management SMTP mail DNS name services LDAP Policy services telnet virtual terminal protocol FTP file transfer HTTP Web transfer and more... IETF: Infrastructure applications

38. How IETF sees work divided W3C HTML Voice/ Video Data Telephony HTTP Mail SNMP Signaling • Applications come from all over • IETF • Provides network infrastructure • Tends to use interfaces defined by other bodies UDP RTP TCP Internet Protocol IEEE MPLS Ethernet ATM Frame Relay PPP ETSI A variety of physical layers and interfaces Cellular Radio ITU-T

39. So where is the Internet going? “As for the future, your task is not to foresee, but to enable it.” Antoine de Saint-Exupéry 39

40. IETF vision for the future • Short term • Internet as interconnected competing service providers • Long term • Internet as universal interconnect

41. Internet as interconnected competing service providers • Dominated by • Service Providers and • Large enterprises • A “network of networks” which have different policies and goals

42. Internet as universal interconnect • IETF believes that the internet is the network of tomorrow • Telephone companies seem to agree • But how intelligent a network? • Would like to see common procedures and protocols used throughout • Minimize translation problems

43. Growth of IP Traffic Rel. Bit Volume Traffic Projections for Voice and Data • Email • Information search/access • Subscription services/“Push” • Conferencing/multimedia • Video/imaging 250 Data (IP) 200 150 Circuit Switched Voice 100 Cross over date varies with measuring point 50 “From 2000 on, 80% of ServiceProvider Profits Will Be Derivedfrom IP-Based Services.”Source: CIMI Corp. 1997 1998 1999 2000 2001 Source: Multiple IXC Projections

44. In summary... “I came, I saw, I couldn’t believe my eyes” Julius Caesar, as portrayed in Asterix in Britain 44

45. When standards collide... • Increasingly, convergence of Internet and PSTN networks causes collisions between the bodies that define their protocols and procedures • The solution has to be in finding ways to: • Not compete in standardization • Focus on the problems remaining to be solved

46. The place of standards bodies • Each has its place in the mix • We need to work together on a global basis • Competition between standards promotes inability to • Share solutions to common problems • Communicate among subscribers