Defining the IETF
The information below is for an old version of the document that is already published as an RFC.
|Document||Type||This is an older version of an Internet-Draft that was ultimately published as an RFC.|
|Authors||Paul E. Hoffman , Scott O. Bradner|
|Last updated||2013-03-02 (Latest revision 2001-01-12)|
|RFC Editor Note||(None)|
|IESG||IESG state||RFC 3233 (Best Current Practice)|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. BCP 58 RFC 3233 Title: Defining the IETF Author(s): P. Hoffman, S. Bradner Status: Best Current Practice Date: February 2002 Mailbox: email@example.com, firstname.lastname@example.org Pages: 4 Characters: 6401 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-hoffman-what-is-ietf-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3233.txt This document gives a more concrete definition of "the IETF" as it understood today. Many RFCs refer to "the IETF". Many important IETF documents speak of the IETF as if it were an already-defined entity. However, no IETF document correctly defines what the IETF is. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.