RFC Style Guide
draft-flanagan-style-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Heather Flanagan , Sandy Ginoza | ||
| Last updated | 2013-05-05 (Latest revision 2012-11-01) | ||
| Replaced by | draft-iab-styleguide, draft-iab-styleguide, RFC 7322 | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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 is a comprehensive summary of the style conventions and editorial policies that apply to the RFC document series. It captures the RFC Editor's fundamental requirements and offers guidance regarding the format and structure of an RFC. While in Internet-Draft format, it should be considered for discussion purposes only. Guidance in from this document will not be applied until published as an RFC. Please send your comments to rfc- interest@rfc-editor.org.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)