Internet Engineering Task Force

The Internet Engineering Task Force (IETF) is an open standards organization, which develops and promotes voluntary Internet standards, in particular the standards that comprise the Internet protocol suite (TCP/IP).[2] It has no formal membership roster or membership requirements. All participants and managers are volunteers, though their work is usually funded by their employers or sponsors.

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

Internet Engineering Task Force
AbbreviationIETF[1]
FormationJanuary 16, 1986 (1986-01-16)
Type
PurposeCreating voluntary standards to maintain and improve the usability and interoperability of the Internet.
Parent organization
Internet Society
Websiteietf.org
Internet
An Opte Project visualization of routing paths through a portion of the Internet
Governance
 Internet portal

The IETF started out as an activity supported by the U.S. federal government, but since 1993 it has operated as a standards-development function under the auspices of the Internet Society, an international membership-based non-profit organization.

Organization

The IETF is organized into a large number of working groups and birds of a feather informal discussion groups, each dealing with a specific topic. The IETF operates in a bottom-up task creation mode, largely driven by these working groups.[3] Each working group has an appointed chairperson (or sometimes several co-chairs); a charter that describes its focus; and what it is expected to produce, and when. It is open to all who want to participate and holds discussions on an open mailing list or at IETF meetings, where the entry fee in July 2014 was US$650 per person.[4] Mid-2018 the fees are: early bird US$700, late payment US$875, student US$150 and a one day pass for US$375.

Rough consensus is the primary basis for decision making. There are no formal voting procedures. Because the majority of the IETF's work is done via mailing lists, meeting attendance is not required for contributors. Each working group is intended to complete work on its topic and then disband. In some cases, the working group will instead have its charter updated to take on new tasks as appropriate.[3]

The working groups are organized into areas by subject matter. Current areas are Applications, General, Internet, Operations and Management, Real-time Applications and Infrastructure, Routing, Security, and Transport.[5] 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 Internet Architecture Board (IAB) oversees the IETF's external relationships and relations with the RFC Editor.[6] The IAB provides long-range technical direction for Internet development. 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.

A Nominating Committee (NomCom) of ten randomly chosen volunteers who participate regularly at meetings is vested with the power to appoint, reappoint, and remove members of the IESG, IAB, IASA, and the IAOC.[7] To date, no one has been removed by a NomCom, although several people have resigned their positions, requiring replacements.

In 1993 the IETF changed from an activity supported by the US Federal Government to an independent, international activity associated with the Internet Society, an international membership-based non-profit organization.[8] Because the IETF itself does not have members, nor is it an organization per se, the Internet Society provides the financial and legal framework for the activities of the IETF and its sister bodies (IAB, IRTF). IETF activities are funded by meeting fees, meeting sponsors and by the Internet Society via its organizational membership and the proceeds of the Public Interest Registry.[9]

In December 2005 the IETF Trust was established to manage the copyrighted materials produced by the IETF.[10]

Steering group

The Internet Engineering Steering Group (IESG) is a body composed of the Internet Engineering Task Force (IETF) chair and area directors. It provides the final technical review of Internet standards and is responsible for day-to-day management of the IETF. It receives appeals of the decisions of the working groups, and the IESG makes the decision to progress documents in the standards track.

The chair of the IESG is the director of the General Area, who also serves as the overall IETF Chair. Members of the IESG include the two directors of each of the following areas:

  • Applications Area (app)
  • Internet Area (int)
  • Operations & Network Management Area (ops)
  • Routing Area (rtg)
  • Real-time Applications and Infrastructure Area (rai)
  • Security Area (sec)
  • Transport and Services Area (tsv) – frequently also referred to as the "Transport Area"

Liaison and ex officio members include:

Meetings

The first IETF meeting was attended by 21 US Federal Government-funded researchers on 16 January 1986. It was a continuation of the work of the earlier GADS Task Force. Representatives from non-governmental entities were invited to attend starting with the fourth IETF meeting in October 1986. Since that time all IETF meetings have been open to the public.[3]

Initially, the IETF met quarterly, but from 1991, it has been meeting three times a year. The initial meetings were very small, with fewer than 35 people in attendance at each of the first five meetings. The maximum attendance during the first 13 meetings was only 120 attendees. This occurred at the 12th meeting held during January 1989. These meetings have grown in both participation and scope a great deal since the early 1990s; it had a maximum attendance of 2,810 at the December 2000 IETF held in San Diego, California. Attendance declined with industry restructuring during the early 2000s, and is currently around 1,200.[11][3]

The location for IETF meetings vary greatly. A list of past and future meeting locations can be found on the IETF meetings page.[12] The IETF strives to hold its meetings near where most of the IETF volunteers are located. For many years, the goal was three meetings a year, with two in North America and one in either Europe or Asia, alternating between them every other year. The current goal is to hold three meetings in North America, two in Europe and one in Asia during a two-year period. However, corporate sponsorship of the meetings is also an important factor and the schedule has been modified from time to time in order to decrease operational costs.

The IETF also organizes hackathons during the IETF meetings. The focus is on implementing code that will improve standards in terms of quality and interoperability.[13]

Operations

The details of IETF operations have changed considerably as the organization has grown, but the basic mechanism remains publication of proposed specifications, development based on the proposals, review and independent testing by participants, and republication as a revised proposal, a draft proposal, or eventually as an Internet Standard. IETF standards are developed in an open, all-inclusive process in which any interested individual can participate. All IETF documents are freely available over the Internet and can be reproduced at will. Multiple, working, useful, interoperable implementations are the chief requirement before an IETF proposed specification can become a standard.[3] Most specifications are focused on single protocols rather than tightly interlocked systems. This has allowed the 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, results can be slow whenever the number of volunteers is either too small to make progress, or so large as to make consensus difficult, or when volunteers lack the necessary expertise. 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 that is not fully backward compatible, except for IPv6. 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 on improvements has been slow to develop.

The IETF cooperates with the W3C, ISO/IEC, ITU, and other standards bodies.[8]

Statistics are available that show who the top contributors by RFC publication are.[14] While the IETF only allows for participation by individuals, and not by corporations or governments, sponsorship information is available from these statistics.

Chairs

The IETF Chairperson is selected by the Nominating Committee (NomCom) process for a 2-year renewable term.[15] Before 1993, the IETF Chair was selected by the IAB.[16]

A list of the past and current Chairs of the IETF follows:

Topics of interest

It works on a broad range of networking technologies which provide foundation for the Internet's growth and evolution.[18]

Automated network management

It aims to improve the efficiency in management of networks as they grow in size and complexity. The IETF is also standardizing protocols for autonomic networking that enables networks to be self managing.[19]

Internet of things

It is a network of physical objects or things that are embedded with electronics, sensors, software and also enables objects to exchange data with operator, manufacturer and other connected devices. Several IETF working groups are developing protocols that are directly relevant to IoT.[20]

New transport technology

Its development provides the ability of internet applications to send data over the Internet. There are some well-established transport protocols such as TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) which are continuously getting extended and refined to meet the needs of the global Internet.[21]

IETF areas

It divides its work into a number of areas that have Working groups that have a relation to an area's focus. Area Directors handle the primary task of area management. Area Directors may be advised by one or more Directorates. The area structure is defined by the Internet Engineering Steering Group. The Nominations Committee can be used to add new members.[22]

Token Binding Protocol

In October 2018, Microsoft and Google engineers introduced a plan to create the Token Binding Protocol in order to stop replay attacks on OAuth tokens.[23]

gollark: Modded Minecraft: because who *needs* free RAM?(netdata gave me another low RAM alert)
gollark: Oh, right. Adding neutrons, then, which would make it unstable, should also work.
gollark: And neutrons.
gollark: Or just adding protons.
gollark: Oh, wow.

See also

References
  1. Jacobsen, O.; Lynch, D. (March 1991). A Glossary of Networking Terms. IETF. p. 7. doi:10.17487/RFC1208. ISSN 2070-1721. RFC 1208.
  2. "Internet Engineering Task Force (IETF)". RIPE Network Coordination Centre. August 10, 2012. Retrieved August 22, 2018.
  3. "Internet Engineering Task Force", Scott Bradner, Open Sources: Voices from the Open Source Revolution, O'Reilly, 1st Edition, January 1999, ISBN 1-56592-582-3. Retrieved 21 July 2014.
  4. "Register for the Next IETF Meeting". IETF. Retrieved July 21, 2014.
  5. "Active IETF Working Groups". IETF. Retrieved July 21, 2014.
  6. "Charter of the Internet Architecture Board (IAB)", RFC 2850, B. Carpenter, May 2000. Retrieved 21 July 2014.
  7. "IETF NomCom", IETF. Retrieved 21 July 2014.
  8. "IETF and the Internet Society", Vint Cerf, Internet Society, 18 July 1995. Retrieved 21 July 2014.
  9. "History", Your Public Internet Registry. Retrieved 21 July 2014.
  10. "IETF Trust", IETF. Retrieved 21 July 2014.
  11. "Past Meetings". IETF. Retrieved July 21, 2014.
  12. "IETF Meetings". IETF. Retrieved January 17, 2012.
  13. "IETF Hackathon". www.ietf.org. Retrieved October 23, 2017.
  14. "IETF document statistics (all documents)", Jari Arkko. Retrieved 21 July 2014.
  15. "IAB and IESG Selection, Confirmation, and Recall Process: Operation of the Nominating and Recall Committees", RFC 3777, J. Galvin (Ed.), June 2004. Retrieved 21 July 2014.
  16. "Past IESG Members and IETF Chairs". IETF. Retrieved July 21, 2014.
  17. "IETF Profile: Alissa Cooper". IETF. Retrieved May 30, 2017.
  18. "Topics of interest". IETF. Retrieved January 16, 2018.
  19. "Automated network management". IETF. Retrieved January 16, 2018.
  20. "The Internet of Things". IETF. Retrieved January 16, 2018.
  21. "New transport technology". IETF. Retrieved January 16, 2018.
  22. "IETF Areas". IETF. Retrieved January 16, 2018.
  23. "Google and Microsoft boffins playing nicely together to stop replay attacks in their tracks".
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.