RFC Style Guide
draft-flanagan-style-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Heather Flanagan , Sandy Ginoza | ||
| Last updated | 2014-02-05 (Latest revision 2014-01-16) | ||
| Replaced by | draft-iab-styleguide | ||
| 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-iab-styleguide | |
| 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 summary of the style conventions and editorial policies that apply to the the RFC Series. It captures the RFC Editor's fundamental requirements and offers guidance regarding the style and structure of an RFC. Guidance provided by this document will not be applied until published as an RFC. Please send your comments about the contents of this document 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.)