RFC 1718: The Tao of IETF - A Guide for New Attendees of the Internet Engineering Task Force
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3160.
Current document in this lineage: RFC 9592 — Retiring the Tao of the IETF
In plain English — editorial summary, not part of the RFC
The purpose of this For Your Information (FYI) RFC is to explain to the newcomers how the IETF works. This memo provides information for the Internet community. It does not specify an Internet standard. [FYI 17]
Document record
- Document ID
- RFC1718
- Published
- November 1994
- Authors
- IETF Secretariat; G. Malkin
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 23
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 7 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2339An Agreement Between the Internet Society, the IETF, and Sun Microsystems, Inc. in the matter of NFS V.4 ProtocolsCurrent
May 1998
- RFC 2357IETF Criteria for Evaluating Reliable Multicast Transport and Application ProtocolsCurrent
June 1998
- RFC 2436Collaboration between ISOC/IETF and ITU-TObsoleted
October 1998
- RFC 31133GPP-IETF Standardization CollaborationCurrent
June 2001
- RFC 31313GPP2-IETF Standardization CollaborationCurrent
June 2001
- RFC 3233Defining the IETFCurrent
February 2002
- RFC 3356Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration GuidelinesObsoleted
August 2002
- RFC 2028The Organizations Involved in the IETF Standards ProcessObsoleted
October 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?