RFC 3774: IETF Problem Statement
In plain English — editorial summary, not part of the RFC
This memo summarizes perceived problems in the structure, function, and processes of the Internet Engineering Task Force (IETF). We are attempting to identify these problems, so that they can be addressed and corrected by the IETF community. The problems have been digested and categorized from an extensive discussion which took place on the 'problem-statement' mailing list from November 2002 to September 2003. The problem list has been further analyzed in an attempt to determine the root causes at the heart of the perceived problems: The result will be used to guide the next stage of the process in the Problem Statement working group which is to recommend the structures and processes that will carry out the corrections. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3774
- Published
- May 2004
- Authors
- E. Davies
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- gen
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3844IETF Problem Resolution ProcessCurrent
August 2004
- RFC 7221Handling of Internet-Drafts by IETF Working GroupsCurrent
April 2014
- RFC 2777Publicly Verifiable Nomcom Random SelectionObsoleted
February 2000
- RFC 3797Publicly Verifiable Nominations Committee (NomCom) Random SelectionCurrent
June 2004
- RFC 2007Catalogue of Network Training MaterialsCurrent
October 1996
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 8088How to Write an RTP Payload FormatUpdated
May 2017
- RFC 8789IETF Stream Documents Require IETF Rough ConsensusCurrent
June 2020
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?