A Fast-Track way to RFC with Running Code

Document Type Expired Internet-Draft (individual)
Author Stephen Farrell 
Last updated 2015-10-14 (latest revision 2013-01-06)
Stream IETF
Intended RFC status Experimental
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Adrian Farrel
IESG note Adrian Farrel (adrian@olddog.co.uk) is the document shepherd
Send notices to (None)

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


This memo describes an optional, fast-track way to progress a working group document to IESG review. It is provided as a process experiment as defined in RFC 3933 for use when working group chairs believe that there is running code that implements a working group Internet-Draft. The motivation is to have the IETF process explicitly consider running code, consistent with the IETF's overall philosophy of running code and rough consensus. In this process all of working group last call, IETF last call, and Area Director review are carried out in the same two week period. Only comments that meet IESG Discuss criteria need to be addressed during this stage, and authors are required to make any changes within two weeks. This experiment will run for one year.


Stephen Farrell (stephen.farrell@cs.tcd.ie)

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