Formalizing IETF Interoperability Reporting
draft-ietf-newtrk-interop-reports-00
| Document | Type |
Expired Internet-Draft
(newtrk WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Larry M Masinter | ||
| Last updated | 2005-10-12 (Latest revision 2005-10-11) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 suggests another way of reforming IETF standards process by formalizing the mechanism for interoperability reporting, as a way of facilitating standards development. It establishes two kinds of reports: a 'Protocol Feature Set', which lays out the set of features from IETF specifications that constitute a protocol, and a 'Protocol Implementation Report', which is submitted by an individual or group to report on implementation and interoperability testing.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)