The definitions of 'fair and open'and their implication
as used in IETF Standards Process defined in RFC2026 v3
draft-glassey-fairopen2026-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Todd S. Glassey | ||
| Last updated | 2003-07-23 | ||
| 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
This document tracks the use of the terms Fair and Open as used in RFC2026, and their impact on the processes of the IETF Operations. It also summarizes a set of requirements for other changes to the governance models so stay in concert with the concept that the ETF’s processes be fair and open.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)