On the use of HTTP as a Substrate
draft-nottingham-bcp56bis-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark Nottingham | ||
| Last updated | 2017-11-13 (Latest revision 2017-05-10) | ||
| Replaced by | draft-ietf-httpbis-bcp56bis | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpbis-bcp56bis | |
| 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
HTTP is often used as a substrate for other application protocols. This document specifies best practices for these protocols' use of HTTP. Note to Readers The issues list for this draft can be found at https://github.com/mnot/I-D/labels/bcp56bis . The most recent (often, unpublished) draft is at https://mnot.github.io/I-D/bcp56bis/ . Recent changes are listed at https://github.com/mnot/I-D/commits/gh- pages/bcp56bis .
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)