Process for Handling Non-Major Revisions to Existing RFCs

Document Type Expired Internet-Draft (individual)
Author Adam Roach 
Last updated 2019-11-18 (latest revision 2019-05-07)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Adam Roach (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)