AsciiRFC: Authoring Internet-Drafts And RFCs Using AsciiDoc
draft-ribose-asciirfc-08
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ronald Henry Tse , Nick Nicholas , Jeffrey Lau | ||
| Last updated | 2023-08-31 (Latest revision 2018-04-17) | ||
| RFC stream | (None) | ||
| Intended RFC status | Informational | ||
| Formats | |||
| IETF conflict review | conflict-review-ribose-asciirfc | ||
| 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 | Adrian Farrel <rfc-ise@rfc-editor.org>, draft-ribose-asciirfc@ietf.org | ||
| IANA | IANA review state | Version Changed - Review Needed |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes an AsciiDoc syntax extension called AsciiRFC, designed for authoring IETF Internet-Drafts and RFCs. AsciiDoc is a human readable document markup language which affords more granular control over markup than comparable schemes such as Markdown. The AsciiRFC syntax is designed to allow the author to entirely focus on text, providing the full power of the resulting RFC XML through the AsciiDoc language, while abstracting away the need to manually edit XML, including references. This document itself was written and generated into RFC XML v2 (RFC7749) and RFC XML v3 (RFC7991) directly through asciidoctor-rfc, an AsciiRFC generator.
Authors
Ronald Henry Tse
Nick Nicholas
Jeffrey Lau
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)