RFC 2026 in practice
draft-carpenter-rfc2026-practice-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Brian Carpenter | ||
| Last updated | 2008-07-02 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
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
https://www.ietf.org/archive/id/draft-carpenter-rfc2026-practice-00.txt
https://www.ietf.org/archive/id/draft-carpenter-rfc2026-practice-00.txt
Abstract
This document discusses how RFC 2026, the current description of the IETF standards process, operates in practice. Its main purpose is to document, for information only, how actual practice interprets the formal rules.
Authors
Brian Carpenter (brian.e.carpenter@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)