Images in RFCs
draft-rfc-image-files-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Robert T. Braden , Dr. John C. Klensin | ||
| Last updated | 2012-09-13 (Latest revision 2012-03-12) | ||
| 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
Documents in the RFC series normally use only plain-text ASCII characters and a fixed-width font. However, there is sometimes a need to supplement the ASCII text with images -- e.g., graphics, equations, or pictures. The historic solution to this requirement has allowed secondary PDF and/or Postscript files, but this approach has seldom been used because it is awkward for authors and publisher. This memo sugests a convenient scheme for logically including authoritative diagrams, illustrations, equations, or other graphics within RFCs.
Authors
Robert T. Braden
Dr. John C. Klensin
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)