IETF Stream Documents Require IETF Rough Consensus
RFC 8789
part of BCP 9
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2024-08-28
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2024-07-30
|
(System) | Received changes through RFC Editor sync (removed Errata tag) |
|
2024-07-27
|
(System) | Received changes through RFC Editor sync (added Errata tag) |
|
2023-12-12
|
(System) | Imported membership of rfc8789 in bcp9 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP9 is currently available in the datatracker before this point |
|
2020-06-17
|
(System) | Received changes through RFC Editor sync (created alias RFC 8789, changed abstract to 'This document requires that the IETF never publish any IETF Stream … Received changes through RFC Editor sync (created alias RFC 8789, changed abstract to 'This document requires that the IETF never publish any IETF Stream RFCs without IETF rough consensus. This updates RFC 2026.', changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2020-06-17, changed IESG state to RFC Published, created updates relation between draft-halpern-gendispatch-consensusinformational and RFC 2026) |
|
2020-06-17
|
(System) | RFC published |