Moving Undeployed TCP Extensions to Historic and Informational Status -- An addition to RFC 6247
draft-zimmermann-tcpm-undeployed-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexander Zimmermann , Wesley Eddy , Lars Eggert | ||
| Last updated | 2015-01-30 (Latest revision 2014-07-29) | ||
| 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 reclassifies several TCP extensions that have either been superceded or never seen widespread use to Historic status. The affected RFCs are RFC 675, RFC 721, RFC 879, RFC 1078, and RFC 6013. Additionally, it reclassifies RFC 813, RFC 814, RFC 816, RFC 817, RFC 872, RFC 896, and RFC 964 to Informational status. Most of those RFCs are today part of RFC 1122.
Authors
Alexander Zimmermann
Wesley Eddy
Lars Eggert
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)