Changes to the Internet Standards Process defined by RFC 2026
draft-carpenter-rfc2026-changes-02
| Document | Type |
Expired Internet-Draft
(individual in gen area)
Expired & archived
|
|
|---|---|---|---|
| Author | Brian E. Carpenter | ||
| Last updated | 2015-10-14 (Latest revision 2008-01-16) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Best Current Practice | ||
| Formats | |||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Russ Housley | ||
| 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 defines a number of changes to RFC 2026, the basic definition of the IETF standards process. While some of them are definite changes to the rules, the intention is to preserve the main intent of the original rules, while adapting them to experience and current practice.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)