1 / 26

Internet Engineering Task Force (IETF)

Internet Engineering Task Force (IETF). Tony Hain <alh-ietf@tndh.net>. Agenda. Organization Working Groups Documents Perspective. Agenda. Organization Working Groups Documents Perspective. Role. Historical developer of Internet-related protocols http://www.ietf.org

astra
Download Presentation

Internet Engineering Task Force (IETF)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internet Engineering Task Force (IETF) Tony Hain <alh-ietf@tndh.net>

  2. Agenda Organization Working Groups Documents Perspective

  3. Agenda Organization Working Groups Documents Perspective

  4. Role • Historical developer of Internet-related protocols http://www.ietf.org Consortium of individuals from Research, Education, Network operators, and Internet vendors

  5. Organization Internet Society (ISOC) – Legal entity, funding & insurance Internet Architecture Board (IAB) – Architecture overview, Process appeals Internet Engineering Steering Group (IESG) – Process Management Working Groups (over 100 in 8 areas)

  6. Internet Architecture Board (IAB) • Mission Oversight of IETF, IRTF, IANA, liaisons Think tank for future Internet activities • Recent activities Really worried right now about Integrity of the infrastructure Intrusion of middle-boxes Impact of unbridled creativity Wireless communications

  7. Internet Engineering Steering Group (IESG) • Mission Assure openness and adherence to process Working group chartering and management “Quality assurance” on specifications • Activities and trends Making sure mobile networks are part of the Internet Trying to grow the network (IPv6, routing)

  8. Membership • IETF members are individuals As opposed to nations or companies • Communications tend to be among individuals As opposed to working groups, boards, etc. Have trouble understanding “liaison”

  9. “ ” Fundamental working principle We reject kings, presidents, and voting. We believe in rough consensus and running code. Dr. David C. Clark, Massachusetts Institute of Technology

  10. Changed IETF composition and roles Research/Education primarily US Attendance Vendor/International Actual Avg.

  11. December 1996 (San Jose) 11 Countries July 1999 (Oslo) 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%

  12. Agenda Organization Working Groups Documents Perspective

  13. Internet Routing Transport Applications Security Operations and management General (Sub-IP) Working groups in eight areas

  14. Working group summary • We have more than 100 working groups Not all currently active • Maintain the IPv4 Internet • Enable the IPv6 Internet • Create the mobile Internet • Make all the Internet useful and secure

  15. Development process • Bottom-up Working Group charters developed to support work people want to do • Development process Working groups develop to consensus IESG reviews RFC editor publishes • Specified in RFC 2026

  16. Work model • Primary work is conducted continuously on mail lists • 3 face-to-face meetings per year Used for issues that are not resolved via email 7-10 parallel meetings in 1 to 2 ½ hour segments Mon-Thurs 9am to 10pm Orientation session Sun 12-4

  17. Agenda Organization Working Groups Documents Perspective

  18. Two types of documents • Internet drafts • RFC - “request for comments”

  19. 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 Nine out of ten I-Ds do NOT result in RFCs • Types of drafts Working group documents Submissions to working groups Individual submissions • Expire in 6 months

  20. Historical archive Many kinds of documents Informational Historical Experimental Standards Standards Proposed Draft Full Best current practice RFCs

  21. Agenda Organization Working Groups Documents Perspective

  22. Fundamental perspective of enlightened self-interest • There is no one organization or company which has a corner on intelligence or expertise Good ideas that help our markets come from everywhere and anywhere • Growing the Internet is good for all of us A larger Internet creates larger markets. Larger markets create cheaper products. Cheaper products create more end-user value.

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

  24. Some link layer PPP Network layer IPv4, IPv6 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

  25. SNMP management SMTP mail DNS name services LDAP directory services SSH virtual terminal protocol FTP file transfer HTTP web transfer And more... IETF: infrastructure applications

  26. Thank you

More Related