The Internet Engineering Task Force (IETF) is a large open international community of network designers, operators, vendors, and researchers concerned with the evolution of the Internet architecture and the smooth operation of the Internet. It is open to any interested individual. The IETF Mission Statement is documented in RFC 3935.
The actual technical work of the IETF is done in its working groups, which are organized by topic into several areas (e.g., routing, transport, security, etc.). Much of the work is handled via mailing lists. The IETF holds meetings three times per year.
The IETF working groups are grouped into areas, and managed by Area Directors, or ADs. The ADs are members of the Internet Engineering Steering Group (IESG). Providing architectural oversight is the Internet Architecture Board, (IAB). The IAB also adjudicates appeals when someone complains that the IESG has failed. The IAB and IESG are chartered by the Internet Society (ISOC) for these purposes. The General Area Director also serves as the chair of the IESG and of the IETF, and is an ex-officio member of the IAB.
The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols. The IANA is chartered by the Internet Society (ISOC) to act as the clearinghouse to assign and coordinate the use of numerous Internet protocol parameters.
First-time attendees might find it helpful to read The Tao of the IETF, also available as RFC 4677. First-time attendees may also want to visit the Education (EDU) Team Web site where information and presentations on IETF roles and processes are available.
Finally, you may want to visit the IETF Information Available for Download Web page.
-the IETF plenary session,All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).
-any IETF working group or portion thereof,
-the IESG or any member thereof on behalf of the IESG,
-the IAB or any member thereof on behalf of the IAB,
-any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices,
-the RFC Editor or the Internet-Drafts function
Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details.
A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.
A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.
IETF Secretariat - Please send problem reports to email@example.com.