Clarifying the Historical Record for RFC 32
draft-flanagan-rfc32alt-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Heather Flanagan | ||
Last updated | 2020-01-09 (Latest revision 2019-07-08) | ||
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 identifies an issue found in the historical record of the RFC Series with regards to RFC 32, a number issued to two separate documents in the early days of the Series. This document serves as a reference point such that errata can be registered against those RFCs that refer to RFC 32.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)