Variances to Provisions of Best Current Practices
draft-resnick-variance-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pete Resnick | ||
| Last updated | 2020-09-28 (Latest revision 2020-03-27) | ||
| 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
From time to time, there are unforeseen circumstances which make following the requirements of a Best Current Practice (BCP) untenable, or where the procedures described in the BCP gives no guidance. This document defines a process for the IETF to grant a variance to any IETF process for a single use or of very short duration.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)