Section 10 of RFC 2026, and the author does not provide the IETF
with any rights other than to publish as an Internet-Draft.
RFC 2629 Writing I-Ds and RFCs using XML June 1999
In the latter case, a copyright notice will not be automatically
inserted during processing by an XML application.
Consult [3] for further details.
Finally, if the Internet-Draft is being submitted to an automated
process, then the "docName" attribute should be present in the
"" tag at the beginning of the file. The value of this attribute
contains the document (not file) name associated with this Internet-
Draft, e.g.,
<rfc ipr="full" docName="draft-mrose-writing-rfcs-01">
...
2.2.8 Everything in the Front
So, putting it all together, we have, e.g.,
Writing I-Ds and RFCs using XML
<author initials="M.T." surname="Rose"
fullname="Marshall T. Rose">
<organization>Invisible Worlds, Inc.</organization>
660 York Street
M/S 40
San Francisco CA
94110
US
+1 415 695 3975
mrose@not.invisible.net
http://invisible.net/
<date month="February" year="1999" />
General
RFC Beautification Working Group
RFC
Request for Comments
I-D
RFC 2629 Writing I-Ds and RFCs using XML June 1999
Internet-Draft
XML
Extensible Markup Language
This memo presents a technique for using XML
(Extensible Markup Language) as a source format
for documents in the Internet-Drafts (I-Ds) and
Request for Comments (RFC) series.
2.3 The Middle
The "middle" element contains all the sections of the document except
for the bibliography and appendices:
...
<section ...>
<section ...>
<section ...>
...
The "middle" element consists of one or more "section" elements.
2.3.1 The section Element
Each "section" element contains a section of the document. There is a
mandatory attribute, "title", that identifies the title of the
section. There is also an optional attribute, "anchor", that is used
for cross-referencing with the "xref" element (Section 2.3.1.4),
=6= |