IETF global options and processing instructions
This page collects the header rules, author-attribute conventions, and xml2rfc processing-instruction guidance that accompany the IETF document attributes (AsciiRFC v3) and AsciiRFC v2 references. The attributes themselves are documented there.
AsciiRFC v3 (RFC XML v3)
Document header attributes
Metanorma-IETF allows setting the RFC XML document header using the following document attributes. Complying with AsciiDoc syntax, no blank lines are permitted between the title, listing of authors, and the document attributes.
Also following AsciiDoc syntax, character entities will be ignored in the document header: \ in the header for example will be rendered as  .
.Example of document metadata for an IETF document
= The Holy Hand Grenade of Antioch
Arthur son of Uther Pendragon
:doctype: internet-draft
:submission-type: independent
:intended-series: informational
:docnumber: draft-camelot-holy-grenade-01
:status: informationalProcessing instructions for `xml2rfc`
The xml2rfc tool accepts processing instructions of the form <?rfc keyword='value'?>: see https://xml2rfc.tools.ietf.org/authoring/README.html#processing.instructions . (Of these, sort-refs, sym-refs and toc-include are also present in the RFC XML v3 specification, as attributes of the root rfc element: v3-specific document attributes.)
Those processing instructions which apply to the entire document can also be specified in Metanorma-IETF as document attributes.
The processing-instruction attributes (:artworkdelimiter:, :toc-include:, and so on) are documented in the AsciiRFC v3 document attributes reference.
Exceptionally, compact, toc-include, sym-refs, sort-refs and strict are is set by default to yes, subcompact to no, and toc-depth to 4.
AsciiRFC v2 (RFC XML v2)
Document header attributes
Metanorma-IETF allows setting the RFC XML document header using the following document attributes. Complying with AsciiDoc syntax, no blank lines are permitted between the title, listing of authors, and the document attributes. Also following AsciiDoc syntax, character entities will be ignored in the document header: \ in the header for example will be rendered as &nbsp;.
Processing instructions for `xml2rfc`
The xml2rfc tool accepts processing instructions of the form <?rfc keyword='value'?>: see https://xml2rfc.tools.ietf.org/authoring/README.html#processing.instructions . (Of these, sort-refs, sym-refs and toc-include are also present in the RFC XML v3 specification, as attributes of the root rfc element: v3-specific document attributes.)
Those processing instructions which apply to the entire document can also be specified in Metanorma-IETF as document attributes.
The xml2rfc tool accepts processing instructions of the form <?rfc keyword='value'?>: see https://xml2rfc.tools.ietf.org/authoring/README.html#processing.instructions . (Of these, sort-refs, sym-refs and toc-include are also present in the RFC XML v3 specification, as attributes of the root rfc element: v3-specific document attributes.) Those processing instructions which apply to the entire document can also be specified in Metanorma-IETF as document options.
The processing-instruction attributes are documented in the AsciiRFC v2 document attributes reference.
Exceptionally, compact, toc-include, sym-refs, sort-refs and strict are is set by default to yes, subcompact to no, and toc-depth to 4.
The additional document option rfc2629xslt (default value: true) injects into the document header the processing instruction <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>, which impacts on the output of xml2rfc.