Internet Engineering Task Force

From Wikipedia, the free encyclopedia

"IETF" redirects here. For other uses, see IETF (disambiguation).

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/IP and 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 VeriSign and the U.S. government's National Security Agency.[1]

It 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 shut down. 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.

Contents

[edit] IETF working groups

Main article: IETF Working Group

IETF working groups operate on rough consensus, are open to all who want to participate, have discussions on an open mailing list, and may hold meetings at IETF meetings. Unlike, for instance, IEEE working groups, the mailing list consensus is the final arbiter of decision-making, and there is no voting, but rather a consensus decision-making procedure.

An IETF working group is created by the IESG to work on a limited set of tasks described in its charter, and will normally be closed once the work described in its charter is finished. In some cases, the WG will instead have its charter updated to take on new tasks as appropriate.

Details of the IETF working group process can be found in RFC 2418.

[edit] History

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-government vendors were invited starting with the fourth IETF meeting, in October of that year. Since that time all IETF meetings have been open to anyone. The majority of the IETF's work is done on mailing lists, however, 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 and with the peak attendance in the first 13 meetings of only 120 attendees, at the 12th meeting in January of 1989. It has grown in both participation and scope a great deal since the early 90s; 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 1300[citation needed].

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 Internet Society.

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 interoperate across networks is considerably more prosaic.

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. 3GPP IMS).

Because it relies on volunteers and uses "rough consensus and running code" as its touchstone, it can, however, be slow whenever the number of volunteers is either too small to make progress 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 its speed is ongoing but, because the number of volunteers with opinions on it is very great, consensus mechanisms on how to improve have been slow to emerge.

Because the IETF does not have members nor is an organisation per say, the Internet Society provides 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 Society via its organizational membership and the proceeds of the Public Internet Registry.

The seventieth meeting of the IETF was held in Vancouver, British Columbia, Canada on December 2, 2007 to December 7, 2007 hosted by Cisco Systems and Microsoft Corporation.[2]

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.

[edit] The Security area

The computer security area of the IETF as of December 10, 2007 was directed by Tim Polk of the U.S. National Institute of Standards and Technology (NIST) and Sam Hartman whose email address at the time was from the Massachusetts Institute of Technology (MIT), also in the USA. They were supported by a directorate whose participants (active or not) had email addresses from bbn.com, bear.com, cisco.com, cmu.edu, columbia.edu, comcast.net, coopercain.com, gmx.net, hactrn.net, hotmail.com, hyperthought.com, ibm.com, ieca.com, ihtfp.com, imc.org, isode.com, it.su.se, iu-bremen.de, juniper.net, laposte.net, ltsnet.net, microsoft.com, mit.edu, motorola.com, navy.mil, nec.de, networkresonance.com, nokia.com, nortel.com, nortelnetworks.com, opentext.com, orionsec.com, qualcomm.com, rsa.com, safenet-inc.com, sendmail.com, sun.com, tcd.ie, tislabs.com, verisign.com, vigilsec.com, and xmission.com as of December 10, 2007.[3] Public participation takes place on a mailing list named SAAG, which is hosted by MIT and administrated by Polk, Hartman, and Jeffrey I. Schiller of MIT, who is network manager and security architect and former security area director.[4]

Jonathan Zittrain has suggested that Internet users at large might accept responsibility for monitoring code for malware in much the same way Wikipedia users share the task of reverting vandalism.[5] He wrote, "IETF endorsement of one standard or another, while helpful, is no longer crucial" but its "generative network technology can be justified".[6]

[edit] IETF chairs

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.

[edit] See also

[edit] References

  1. ^ Duffy Marsan, Carolyn. "Q&A: Security top concern for new IETF chair", Network World, IDG, July 26, 2007. Retrieved on 2008-04-20. 
  2. ^ 70th IETF - Vancouver, BC, Canada. ietf.org. Retrieved on 2007-12-10.
  3. ^ Active IETF Working Groups. ietf.org. Retrieved on 2007-12-10. and The IETF Security Area. itef.org. Retrieved on 2007-12-10. and Subscribers to secdir, linked from http://sec.ietf.org/security-directorate.html. mit.edu. Retrieved on 2007-12-10.
  4. ^ saag -- IETF Security Area Advisory Group. Massachusetts Institute of Technology. Retrieved on 2007-12-12. and Jeffrey I. Schiller (home page). Massachusetts Institute of Technology (counter started August 12, 2000). Retrieved on 2007-12-12.
  5. ^ Duffy Marsan, Carolyn. "How the iPhone is killing the 'Net", Network World, IDG, April 9, 2008, pp. 4–5. Retrieved on 2008-04-17. 
  6. ^ Zittrain, Jonathan. Chapter 6: The Lessons of Wikipedia, in The Future of the Internet and How to Stop It. Yale Books Unbound, Yale University Press. Retrieved on 2008-04-19.
  7. ^ IETF Chairs by year. Retrieved on 2007-03-23.

[edit] External links