RFC 3844: IETF Problem Resolution Process
In plain English — editorial summary, not part of the RFC
This Informational document records the history of discussions in the Problem WG during 2003 of how to resolve the problems described in the IETF Problem Statement. It decomposes each of the problems described into a few areas for improvement and categorizes them as either problems affecting the routine processes used to create standards or problems affecting the fundamental structure and practices of the IETF. Expeditious and non-disruptive solutions are proposed for the problems affecting routine processes. The document also lists suggested ways to handle the development of solutions for the structure and practices problems proposed in IETF discussions. Neither the working group nor the wider IETF has reached consensus on a recommendation for any of the proposals. This document therefore has no alternative but to suggest that the search for structure and practices solutions be handed back to the control of the IESG. While there was working group consensus on the processes for short-term and medium term improvements, there was no working group consensus on the proposals for longer-term improvements. This document therefore includes longer-term improvement proposals only as a matter of record; they must not be regarded as recommendations from the working group. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3844
- Published
- August 2004
- Authors
- E. Davies; J. Hofmann
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- gen
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3774IETF Problem StatementCurrent
May 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?