A Model for IETF Process Experiments
RFC 3933
also known as BCP 93
Revision differences
Document history
Date | By | Action |
---|---|---|
2023-12-12
|
(System) | Imported membership of rfc3933 in bcp93 via sync to the rfc-index |
2023-12-12
|
(System) | No history of BCP93 is currently available in the datatracker before this point |
2022-10-25
|
(System) | Received changes through RFC Editor sync (changed abstract to 'The IETF has designed process changes over the last ten years in one of two ways: … Received changes through RFC Editor sync (changed abstract to 'The IETF has designed process changes over the last ten years in one of two ways: announcement by the IESG, sometimes based on informal agreements with limited community involvement and awareness, and formal use of the same mechanism used for protocol specification. The first mechanism has often proven to be too lightweight, the second too heavyweight. This document specifies a middle-ground approach to the system of making changes to IETF process, one that relies heavily on a "propose and carry out an experiment, evaluate the experiment, and then establish permanent procedures based on operational experience" model rather than those previously attempted. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.') |
2020-01-21
|
(System) | Received changes through RFC Editor sync (added Verified Errata tag) |
2004-11-23
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
2004-11-23
|
Amy Vezza | [Note]: 'RFC 3933 BCP 93' added by Amy Vezza |
2004-11-05
|
(System) | RFC published |