- Internet Engineering Task Force
The Internet Engineering Task Force (IETF) develops and promotes
Internet standards, cooperating closely with the W3C and ISO/IEC standard bodies and dealing in particular with standards of the TCP/IPand Internet protocol suite. It is an open standards organization, with no formal membership or membership requirements. All participants and leaders are volunteers, though their work is usually funded by their employers or sponsors; for instance, the current chairperson is funded by VeriSignand the U.S. government's National Security Agency. [cite news|first=Carolyn|last=Duffy Marsan|title=Q&A: Security top concern for new IETF chair|url=http://www.networkworld.com/news/2007/073007-ietf-qa.html|work=Network World|publisher=IDG|date= July 26, 2007|accessdate= 2008-04-20]
The IETF is organized into a large number of working groups and informal discussion groups (BoF)s, each dealing with a specific topic. Each group is intended to complete work on that topic and then disband. Each working group has an appointed chair (or sometimes several co-chairs), along with a charter that describes its focus, and what and when it is expected to produce.
The working groups are organized into "areas" by subject matter. Current areas include: Applications, General, Internet, Operations and Management, Real-time Applications and Infrastructure, Routing, Security, and Transport. Each area is overseen by an "area director" (AD), with most areas having two co-ADs. The ADs are responsible for appointing working group chairs. The area directors, together with the IETF Chair, form the
Internet Engineering Steering Group(IESG), which is responsible for the overall operation of the IETF.
The IETF is formally an activity under the umbrella of the
Internet Society. The IETF is overseen by the Internet Architecture Board(IAB), which oversees its external relationships, and relations with the RFC Editor. The IAB is also jointly responsible for the IETF Administrative Oversight Committee(IAOC), which oversees the IETF Administrative Support Activity(IASA), which provides logistical, etc support for the IETF. The IAB also manages the Internet Research Task Force(IRTF), with which the IETF has a number of cross-group relations.
The first IETF meeting was on
January 16, 1986, consisting of 21 U.S.-government-funded researchers. Initially, it met quarterly, but from 1991, it has been meeting 3 times a year. Representatives from non-governmental entities were invited starting with the fourth IETF meeting, in October of that year. Since that time all IETF meetings have been open to the public. The majority of the IETF's work is done on mailing lists, and meeting attendance is not required for contributors.
The initial meetings were very small, with fewer than 35 people in attendance at each of the first five meetings. The peak attendance in the first 13 meetings was only 120 attendees. This occurred at the 12th meeting held in January 1989. These meetings have grown in both participation and scope a great deal since the early 1990s; it had a peak attendance of almost 3000 at the December 2000 IETF held in San Diego, CA. Attendance declined with industry restructuring in the early 2000s, and is currently around 1200. [cite web
title=Past Meetings of the IETF
During the early 1990s the IETF changed institutional form from an activity of the U.S. government to an independent, international activity associated with the
The IETF has at times been ascribed nearly magical abilities by the trade press, who assumed its mechanisms were responsible for the success of the Internet because it works on the Internet's core protocols. The reality that it is a group of engineers putting together specifications so that multiple vendors' products can operate across networks is considerably more mundane.
The details of its operations have changed considerably as it has grown, but the basic mechanism remains publication of draft specifications, review and independent testing by participants, and republication. Interoperability is the chief test for IETF specifications becoming standards. Most of its specifications are focused on single protocols rather than tightly-interlocked systems. This has allowed its protocols to be used in many different systems, and its standards are routinely re-used by bodies which create full-fledged architectures (e.g.
Because it relies on volunteers and uses "rough consensus and running code" as its touchstone, results can be slow whenever the number of volunteers is either too small to make progress, or when volunteers lack the necessary expertise, or so large as to make consensus difficult. For protocols like SMTP, which is used to transport e-mail for a user community in the many hundreds of millions, there is also considerable resistance to any change which is not fully backwards compatible. Work within the IETF on ways to improve the speed of the standards-making process is ongoing but, because the number of volunteers with opinions on it is very great, consensus mechanisms on how to improve have been slow.
Because the IETF does not have members (nor is it an organisation "per se"), the
Internet Societyprovides the financial and legal framework for the activities of the IETF and its sister bodies (IAB, IRTF,...). Recently the IETF has set up an IETF Trust which manages the copyrighted materials produced by the IETF. IETF activities are funded by meeting fees, meeting sponsors and by the Internet Societyvia its organizational membership and the proceeds of the Public Interest Registry.
The seventieth meeting of the IETF was held in
Vancouver, British Columbia, Canadaon December 2, 2007to December 7, 2007hosted by Cisco Systemsand Microsoft Corporation. [cite web|title=70th IETF - Vancouver, BC, Canada|url=http://www.ietf.org/meetings/70-IETF.html|publisher=ietf.org|accessdate=2007-12-10]
IETF meetings vary greatly in where they are held. They have strived to hold the meetings near where most of the IETF volunteers are located. For a long time, the goal was 3 meetings a year, with 2 in North America and 1 in either Europe or Asia (alternating between them every other year). However, corporate sponsorship of the meetings is typically a more important factor and the schedule has not been kept strictly in order to decrease operational costs.
The IETF Chair is selected by the NOMCOM process specified in RFC 3777 for a 2-year term, renewable.
Before 1993, the IETF Chair was selected by the IAB.
* Mike Corrigan (1986)
* Fred Baker (1996–2001)
Harald Tveit Alvestrand(2001–2005)
Russ Housley(2007–) [ cite web|url=http://www.ietf.org/ietf_chairs_year.html |title=IETF Chairs by year |accessdate=2007-03-23 ]
Request for Comments
IETF Working Group
Internet Engineering Steering Group
Internet Architecture Board
Internet Research Task Force
* [http://www.ietf.org/ The official IETF site]
** [http://www.ietf.org/proceedings/directory.html IETF Online Proceedings]
** [http://www.ietf.org/proceedings/directory2.html Early IETF Proceedings] ("note: large pdf files, one for each volume")
** [http://www.ietf.org/meetings/past.meetings.html Past Meetings of the IETF]
** [http://www.ietf.org/ietf_chairs_year.html IETF Chairs]
* [http://tools.ietf.org/html/fyi17 The Tao of the IETF] : details on how IETF is organized
* [http://iaoc.ietf.org/ IAOC information]
* [http://myietf.unfix.org MyIETF] Personalized notification service on RFC's and drafts with full archive of old drafts etc.
Wikimedia Foundation. 2010.