Advancement of Application Programming Interface specifications on the IETF Standards Track
draft-pawlowski-apitest-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Brian Pawlowski | ||
Last updated | 2002-11-06 | ||
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
The Internet Standards Process [RFC2026] requires that all IETF Standards Track specifications must have 'multiple, independent, and interoperable implementations' before they can be advanced beyond Proposed Standard status. This document specifies the test which the IESG will use to determine if an Application Programming Interface (API) specification document meets these requirements. It also discusses the rationale for this process.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)