Streamlining the IETF Administrative Support Activity (IASA)
draft-klensin-iasa-streamline-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. John C. Klensin | ||
| Last updated | 2010-07-05 | ||
| 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
There have been many opportunities to examine the functioning of the IETF Administrative Support Activity (IASA) since its creation in 2005 and the subsequent addition of the IETF Trust to its scope. Suggestions to do so have generally not progressed, in part because of constraints imposed by the IETF Trust. Those constraints have now expired. The IASA has often fallen short of the expectations about openness and transparency called for in BCP 101, with members of the IAOC and IETF Trust claiming excessive workload as a major cause of that problem. This document proposes to change the workload requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)