The Internet Engineering Task Force (IETF) is beside the Internet Research Task Force (IRTF) one of two working groups of the Internet Architecture Board (IAB). Their order is the development and promotion of Internet standards, in particular those the TCP/IP family. Contrary to the IRTF it worries more about the short term development of the Internets.

It is an open, international combinationcombination combination of network technicians, manufacturers and users, which is responsible for suggestions on the standardisation of the Internets. It does not exist formal membership or condition for member.

The IETF consists of a large number working groups, from which everyone is concerned and intended with a specific topic to terminate the work on this topic and then dissolve. Each working group an appointed chairman (or sometimes several CO chairmen), as well as a Charter those the goal formulated and which is produced when.

The working groups are arranged according to topic area into ranges (AREAs); each range becomes of AREA a Director (AD) (most ranges to have two CO-ADs) cared for; the ADs appoints the chairmen of the working groups. The AREA Directors form together with the IETF chairman the Internet Engineering Steering Group (IESG), who is responsible for the total enterprise of the IETF.

The IETF is formally active under the screen of the Internet Society. The Internet Architecture Board (IAB) cares for the external relations of the IETF as well as to the RFC the editor. The IAB is jointly responsible for the IETF administrative Oversight Committee (IAOC), which cares for the IETF administrative support Activity (IASA), which supports the logistics of the IETF. The IAB managt also the Internet Research Task Force (IRTF) with the IETF some group-spreading relations has.

Ranges

Zurzeit is divided the IETF into 7 ranges:

1. Applications (APP)
2. Generally
3. Internet services (INT)
4. Enterprise (OPS)
5. Routing (RTG)
6. Security
7. Transportation services (TSV)

History

The IETF began in January 1986 with a quarterly meeting of the US Government of paid researchers. Beginning with fourth IETF Meetings in the October of this yearly were invited also representative non--government supplier. Since this time all IETF Meetings for everyone were open. The majority of the work of the IETF been made however by mailing lists and the participation in the Meetings is therefore not necessary for the participations.

The initial Meetings were very small, with less ever than 35 present ones with the first five and a maximum of 120 present ones, with 12. Meeting in January 1989, with the first 13 Meetings. Since beginning of the 1990er the Meetings grew both in participation and area of application strongly; the number of point visitors was with 3000 in July 2000 IETF in San Diego. With the restructuring in the industry into the early 2000ern the number of visitors decreased again and lies momentarily at around the 1500.

During the early 1990er the institutional form of an activity of the US Government changed to an independent, international with the Internet Society connected. The IETF by the technical literature and again already almost magic abilities attributed, there it accepted it is responsible by their work on core minutes for the success of the Internet. The truth that those is it a group of technicians the specifications compiles thereby the products of different manufacturers over networks co-operate can, is substantially more sober.

In the detail the activities changed during the growth of the IETF around some, but the fundamental mechanism remains wanting to become the publication of specification drafts, Review and independent testing by the involved ones and republication interoperability is the main test for IETF specifications the standards. Most specifications concentrate rather on individual minutes as on closely into one another seizing systems. This permitted it that their minutes in many different systems are used and their standards by institutions are by routine reused if it around the development of complete architectures go (e.g. 3GPP CIM).

Since those relies IETF on Freiwillige and "„consent as well as "“as it uses executable code it can be however also slowly if the number of Freiwilliger either too low is around a progress to be made or so largely that a consent is difficult. For minutes such as smtp, which counts for the transport of E-Mail for a community after millions is responsible, there is not also considerable resistance with each change those is by hundred percent downward compatible. At ways the operating speed will increase within the IETF worked - there there however whether the large number of Freiwilliger many opinions over it are, brake the consent mechanisms these efforts themselves.

An introduction to the IETF is in the RFC The Tao OF IETF - to A Novice's Guide ton the Internet Engineering Task Force RFC 3160.

Related links

• http://www.ietf.org/

Articles in category "Internet Engineering Task Force"

We found here 28 articles.

Related Websites

We found here 5 related websites.

• IETF Home Page
  The Internet Engineering Task Force ... Internet-Drafts · IETF Liaison Activities · RFC Pages · IETF IPR Disclosure Page. blue dot Educational Materials ...


• IETF Overview
  The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with ...


• Internet Engineering Task Force - Wikipedia, the free encyclopedia
  The Internet Engineering Task Force (IETF) develops and promotes Internet standards; in particular those of the TCP/IP protocol suite. It is an open, ...


• Internet Engineering Task Force - Wikipedia, the free encyclopedia
  The Internet Engineering Task Force (IETF) develops and promotes Internet standards; in particular those of the TCP/IP protocol suite. It is an open, ...


• The Internet Engineering Task Force
  The Internet Engineering Task Force (IETF) is a large open international community of network designers,...