This article was automatically translated from the original Turkish version.

Established in 1986, the IETF (Internet Engineering Task Force) is the leading standards development organization for the internet. Because the standards created voluntarily for the advancement of the internet have been widely adopted by internet users, network operators, and hardware vendors since its inception, the IETF has played a key role in shaping the evolution of the internet. The work of this organization, which operates on a voluntary basis, is generally supported by employers or other sponsors.
The name now known as the IETF was first used during the fourth meeting of the Gateway Algorithms and Data Structures Task Force, a subcommittee of DARPA, held in January 1986. This meeting is also recognized as the first IETF gathering. At the same meeting, it was decided to establish the Internet Architecture Task Force (INARC) alongside the IETF. While the IETF was intended to focus on short-term operational problems, the INARC group was planned to concentrate on long-term research issues. The IETF’s responsibilities were defined as follows;
At the 21st meeting, in the declaration, the first introduction of the Internet Society, the organization that would later become the IETF’s parent body to promote internationalization and openness, was presented along with its mission.
There is no formal membership system within the IETF. Any individual may contribute to the organization by subscribing to working group email lists or by registering for IETF meetings. Everyone involved in the IETF is considered a volunteer. The organization charges fees only for attendance at meetings.
The IETF publishes its technical documentation under the name RFC. The term RFC, first used in 1969, stands for Requests For Comments. RFCs address the technical foundations of the internet, including addressing, routing, and transport technologies, and explain how these should be implemented. RFCs also cover protocols such as WebRTC and QUIC, which are now used daily by billions of people worldwide. Software developers, hardware manufacturers, and network operators from around the globe voluntarily adopt and implement the technical details and specifications outlined in RFCs.
The RFC series began in April 1969 with a publication titled "Host Software" written by Steve Crocker. The original intent of the earliest RFCs was not to create an archive of standards, but rather to solicit feedback and comments on ideas and proposals. The role of the "RFC Editor" was introduced several years after the first RFC publication. Although the exact date when the term "RFC Editor" was first used is unknown, it was formally established in July 1984 via RFC902. The responsibilities of the RFC Editor include reviewing and editing RFCs prior to publication.
The IETF Chair is selected by the Internet Architecture Board after being nominated by the Nomination Committee. Members of the Nomination Committee are chosen in a complex and random manner; details regarding the selection of Nomination Committee members are described in RFC 3797.

No Discussion Added Yet
Start discussion for "IETF (Internet Engineering Task Force)" article
History
Participation in the Organization
IETF RFC
History of IETF RFC
Some Important RFC Documents in History
Chairs