RFC Style Guide
draft-rpc-rfc7322bis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sandy Ginoza , Jean Mahoney , Alice Russo | ||
| Last updated | 2023-11-06 (Latest revision 2023-05-01) | ||
| Replaces | draft-flanagan-7322bis | ||
| 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 describes the fundamental and unique style conventions and editorial policies currently in use for the RFC Series. It captures the RFC Editor's basic requirements and offers guidance regarding the style and structure of an RFC. Additional guidance is captured on a website that reflects the experimental nature of that guidance and prepares it for future inclusion in the RFC Style Guide. This document obsoletes RFC 7322, "RFC Style Guide". Note: This draft is being developed and discussed in the GitHub repo <https://github.com/rfc-editor/draft-rpc-rfc7322bis>, but any substantive change should be discussed on <rfc-interest@rfc- interest.org>.
Authors
Sandy Ginoza
Jean Mahoney
Alice Russo
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)