Process for Handling Non-Major Revisions to Existing RFCs
draft-roach-bis-documents-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Adam Roach | ||
Last updated | 2019-11-18 (Latest revision 2019-05-07) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses mechanisms the IETF has historically used for updating RFCs subsequent to their publication, and outlines an updated procedure for publishing newer versions (colloquially known as "bis versions") that is appropriate in certain circumstances. This procedure is expected to be easier for both authors and consumers of RFCs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)