draft-rfcxml-general-template-annotated.xml   draft-rfcxml-general-template-annotated_AR.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='utf-8'?>
<!-- <!--
draft-rfcxml-general-template-annotated draft-rfcxml-general-template-annotated
This template includes examples of most of the features of RFCXML with co mments explaining This template includes examples of most of the features of RFCXML with co mments explaining
how to customise them, and examples of how to achieve specific formatting . how to customise them, and examples of how to achieve specific formatting .
Documentation is at https://authors.ietf.org/en/templates-and-schemas Documentation is at https://authors.ietf.org/en/templates-and-schemas
--> -->
<?xml-model href="rfc7991bis.rnc"?> <!-- Required for schema validation and s chema-aware editing --> <?xml-model href="rfc7991bis.rnc"?> <!-- Required for schema validation and s chema-aware editing -->
<!DOCTYPE rfc SYSTEM "rfcxml.ent"> <!-- Useful character entities -->
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> <!-- used by XSLT pro cessors --> <?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?> <!-- used by XSLT pro cessors -->
<!DOCTYPE rfc [
<!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<rfc <rfc
xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xi="http://www.w3.org/2001/XInclude"
category="info" category="info"
docName="draft-rfcxml-general-template-annotated" docName="draft-rfcxml-general-template-annotated"
ipr="trust200902" ipr="trust200902"
obsoletes="" obsoletes=""
updates="" updates=""
submissionType="IETF" submissionType="IETF"
xml:lang="en" xml:lang="en"
version="3"> version="3">
<!-- <!--
* docName should be the name of your draft * docName should be the name of your draft
* category should be one of std, bcp, info, exp, historic * category should be one of std, bcp, info, exp, historic
* ipr should be one of trust200902, noModificationTrust200902, noDerivativ esTrust200902, pre5378Trust200902 * ipr should be one of trust200902, noModificationTrust200902, noDerivativ esTrust200902, pre5378Trust200902
* updates can be an RFC number as NNNN * updates can be an RFC number as NNNN
* obsoletes can be an RFC number as NNNN * obsoletes can be an RFC number as NNNN
--> -->
<front> <front>
<title abbrev="Abbreviated Title">Title</title> <!-- https://authors.ietf. org/en/rfcxml-vocabulary#title-4 --> <title abbrev="Abbreviated Title">Title</title> <!-- https://authors.ietf. org/en/rfcxml-vocabulary#title-4 -->
<!-- The abbreviated title is required if the full title is longer than 3 9 characters --> <!-- The abbreviated title is required if the full title is longer than 3 9 characters -->
<seriesInfo name="Internet-Draft" value="draft-rfcxml-general-template-ann otated"/> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#seriesinfo --> <seriesInfo name="Internet-Draft" value="draft-rfcxml-general-template-ann otated"/> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#seriesinfo -->
<!-- Set value to the name of the draft --> <!-- Set value to the name of the draft -->
<author fullname="author's full name" initials="author's initials" role="e <author fullname="author's full name" initials="author's initials"
ditor" surname="author's surname"> <!-- https://authors.ietf.org/en/rfcxml-voc surname="author's surname" role="editor"> <!-- https://authors.ietf
abulary#author --> .org/en/rfcxml-vocabulary#author -->
<!-- initials does not include an initial for the surname -->
<!-- role="editor" is optional --> <!-- role="editor" is optional -->
<!-- Can have more than one author --> <!-- Can have more than one author -->
<!-- all of the following elements are optional --> <!-- All of the following elements are optional -->
<organization>Organization</organization> <!-- https://authors.ietf.org/ en/rfcxml-vocabulary#organization --> <organization>Organization</organization> <!-- https://authors.ietf.org/ en/rfcxml-vocabulary#organization -->
<address> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#address --> <address> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#address -->
<postal> <postal>
<!-- Reorder these if your country does things differently --> <!-- Reorder these if your country does things differently -->
<street>Street</street> <street>Street</street>
<city>City</city> <city>City</city>
<region>Region</region> <region>Region</region>
<code>Postal code</code> <code>Postal code</code>
<country>Country</country> <country>Country</country>
<!-- Uses two letter country code --> <!-- Can use two-letter country code -->
</postal> </postal>
<phone>Phone</phone> <phone>Phone</phone>
<email>Email</email> <email>Email</email>
<!-- Can have more than one <email> element --> <!-- Can have more than one <email> element -->
<uri>URI</uri> <uri>URI</uri>
</address> </address>
</author> </author>
<date year="2021" month="12" day="1"/> <!-- https://authors.ietf.org/en/rf cxml-vocabulary#date --> <date year="2021" month="12" day="1"/> <!-- https://authors.ietf.org/en/rf cxml-vocabulary#date -->
<!-- On draft subbmission: <!-- On draft subbmission:
* If only the current year is specified, the current day and month wi ll be used. * If only the current year is specified, the current day and month wi ll be used.
* If the month and year are both specified and are the current ones, the current day will * If the month and year are both specified and are the current ones, the current day will
be used be used
* If the year is not the current one, it is necessary to specify at l east a month and day="1" will be used. * If the year is not the current one, it is necessary to specify at l east a month and day="1" will be used.
--> -->
<area>General</area> <area>General</area>
<workgroup>Internet Engineering Task Force</workgroup> <workgroup>Internet Engineering Task Force</workgroup>
<!-- "Internet Engineering Task Force" is fine for individual submissions. If this element is <!-- "Internet Engineering Task Force" is fine for individual submissions. If this element is
not present, the default is "Network Working Group", which is used b y the RFC Editor as not present, the default is "Network Working Group", which is used b y the RFC Editor as
a nod to the history of the IETF. --> a nod to the history of the RFC Series. -->
<keyword>template</keyword> <keyword>template</keyword>
<!-- Multiple keywords are allowed. Keywords are incorporated into HTML o utput files for <!-- Multiple keywords are allowed. Keywords are incorporated into HTML o utput files for
use by search engines. --> use by search engines. -->
<abstract> <abstract>
<t>Abstract</t> <t>Abstract</t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section> <section>
<!-- The default attributes for <section> are numbered="true" and toc="def ault" --> <!-- The default attributes for <section> are numbered="true" and toc="def ault" -->
<name>Introduction</name> <name>Introduction</name>
<t>Introductory text</t> <t>Introductory text</t>
<section anchor="requirements"> <section anchor="requirements">
<!-- anchor is an optional attribute --> <!-- anchor is an optional attribute -->
<name>Requirements Language</name> <name>Requirements Language</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
document are to be interpreted as described in <xref target="RFC2119" f RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
ormat="default">RFC 2119</xref>.</t> interpreted as described in BCP 14 <xref target="RFC2119"/>
<xref target="RFC8174"/> when, and only when, they appear in
all capitals, as shown here.</t>
</section> </section>
<!-- The 'Requirements Language' section is optional --> <!-- The 'Requirements Language' section is optional -->
</section> </section>
<section> <section>
<name>Body</name> <name>Body</name>
<t>Body text</t> <t>Body text</t>
</section> </section>
<section> <section>
<name>List examples</name> <name>List examples</name>
<section> <section>
<name>Simple unordered (bullet) list</name> <name>Simple unordered (bullet) list</name>
<t>Text before the list</t> <t>Text before the list</t>
<ul spacing="normal"> <ul spacing="normal">
<li>First bullet</li> <li>First bullet</li>
<li>Second bullet</li> <li>Second bullet</li>
</ul> </ul>
<t>Text after the list.</t> <t>Text after the list.</t>
</section> </section>
<section> <section>
<name>Ordered list with lowercase letters in brackets instead of numbe rs</name> <name>Ordered list with lowercase letters in brackets instead of numbe rs</name>
<ol type="(%c)"> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#ty pe-1 --> <ol type="(%c)"> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#ty pe-1 -->
<li>List item (a)</li> <li>List item (a)</li>
<li>List item (b)</li> <li>List item (b)</li>
</ol> </ol>
</section> </section>
<section> <section>
<name>Continuous numbering in a list that is split by text or sections </name> <name>Continuous numbering in a list that is split by text or sections </name>
<!-- The following two lists render as <!-- The following two lists render as
Text to introduce the list Text to introduce the list
REQ1: This will be "REQ1:" REQ1: This will be "REQ1:"
REQ2: This will be "REQ2:" REQ2: This will be "REQ2:"
Some text in between Some text in between
REQ3: This will be "REQ3:" REQ3: This will be "REQ3:"
REQ4: This will be "REQ4:" REQ4: This will be "REQ4:"
--> -->
<t>Text to introduce the list</t> <t>Text to introduce the list</t>
<ol type="REQ%d:" group="reqs"> <!-- value of group is user-defined h ttps://authors.ietf.org/en/rfcxml-vocabulary#group --> <ol type="REQ%d:" group="reqs"> <!-- value of group is user-defined h ttps://authors.ietf.org/en/rfcxml-vocabulary#group -->
<li>This will be "REQ1:"</li> <li>This will be "REQ1:"</li>
<li>This will be "REQ2:"</li> <li>This will be "REQ2:"</li>
</ol> </ol>
<t>Some text in between</t> <t>Some text in between</t>
<ol type="REQ%d:" group="reqs"> <!-- same value of group as before -- > <ol type="REQ%d:" group="reqs"> <!-- same value of group as before -- >
<li>This will be "REQ3:"</li> <li>This will be "REQ3:"</li>
<li>This will be "REQ4:"</li> <li>This will be "REQ4:"</li>
</ol> </ol>
<section> <section>
<name>Section in-between</name> <name>Section in-between</name>
<t>More text in-between</t> <t>More text in-between</t>
<ol type="REQ%d:" group="reqs"> <!-- same value of group as before --> <ol type="REQ%d:" group="reqs"> <!-- same value of group as before -->
<li>This will be REQ5:</li> <li>This will be REQ5:</li>
<li>This will be REQ6:</li> <li>This will be REQ6:</li>
</ol> </ol>
</section> </section>
</section> </section>
<section> <section>
<name>Definition lists</name> <!-- https://authors.ietf.org/en/rfcxml- vocabulary#dl --> <name>Definition lists</name> <!-- https://authors.ietf.org/en/rfcxml- vocabulary#dl -->
<dl newline="true"> <!-- https://authors.ietf.org/en/rfcxml-vocabulary #newline --> <dl newline="true"> <!-- https://authors.ietf.org/en/rfcxml-vocabulary #newline -->
<!-- Omit newline="true" if you want each definition to start on the s ame line as the corresponding term --> <!-- Omit newline="true" if you want each definition to start on the s ame line as the corresponding term -->
<dt>First term:</dt> <dt>First term:</dt>
<dd>Definition of the first term</dd> <dd>Definition of the first term</dd>
<dt>Second term:</dt> <dt>Second term:</dt>
<dd>Definition of the second term</dd> <dd>Definition of the second term</dd>
</dl> </dl>
</section> </section>
<section> <section>
<name>Lists with hanging labels</name> <name>Lists with hanging labels</name>
<t>the list item is indented the value of indent</t> <!-- https://au thors.ietf.org/en/rfcxml-vocabulary#indent --> <t>the list item is indented the value of indent</t> <!-- https://aut hors.ietf.org/en/rfcxml-vocabulary#indent -->
<dl newline="true" spacing="normal" indent="8"> <dl newline="true" spacing="normal" indent="8">
<!-- Custom indent of 8 with the defintion starting on a new line afte r the term --> <!-- Custom indent of 8 with the definition starting on a new line aft er the term -->
<dt>short</dt> <dt>short</dt>
<dd>With a label shorter than the indent.</dd> <dd>With a label shorter than the indent.</dd>
<dt>fantastically long label</dt> <dt>fantastically long label</dt>
<dd>With a label longer than the indent.</dd> <dd>With a label longer than the indent.</dd>
</dl> </dl>
</section> </section>
</section> </section>
<section> <section>
<name>Tables</name> <name>Tables</name>
<table> <!-- https://authors.ietf.org/rfcxml-vocabulary#table --> <table> <!-- https://authors.ietf.org/rfcxml-vocabulary#table -->
<thead> <!-- https://authors.ietf.org/rfcxml-vocabulary#thead --> <thead> <!-- https://authors.ietf.org/rfcxml-vocabulary#thead -->
<!-- A table header is optional --> <!-- A table header is optional -->
<tr><th>Column 1</th><th>Column 2</th><th>Column 3</th></tr> <tr><th>Column 1</th><th>Column 2</th><th>Column 3</th></tr>
</thead> </thead>
<tbody> <!-- https://authors.ietf.org/rfcxml-vocabulary#tbody --> <tbody> <!-- https://authors.ietf.org/rfcxml-vocabulary#tbody -->
<!-- A table body is required --> <!-- A table body is required -->
<tr><td align="left">Left cell</td><td colspan="2">Colspan cell</td> </tr> <tr><td align="left">Left cell</td><td colspan="2">Colspan cell</td> </tr>
<!-- align can be right, left or center. colspan and rowspan work a s they do in HTML --> <!-- align can be right, left or center. colspan and rowspan work a s they do in HTML -->
<tr><td rowspan="2">Rowspan cell</td><td align="center">Center cell< /td><td align="right">Right cell</td></tr> <tr><td rowspan="2">Rowspan cell</td><td align="center">Center cell< /td><td align="right">Right cell</td></tr>
<tr><td>Cell</td><td>Cell</td></tr> <tr><td>Cell</td><td>Cell</td></tr>
</tbody> </tbody>
<tfoot> <!-- https://authors.ietf.org/rfcxml-vocabulary#tfoot --> <tfoot> <!-- https://authors.ietf.org/rfcxml-vocabulary#tfoot -->
<!-- A table footer is optional --> <!-- A table footer is optional -->
<tr><td rowspan="3">Rowspan footer</td></tr> <tr><td colspan="3">Rowspan footer</td></tr>
</tfoot> </tfoot>
</table> </table>
</section> </section>
<section> <section>
<name>Source code examples</name> <name>Source code example</name>
<t>This is an example c program</t> <t>This is an example C program.</t>
<figure align="center"> <!-- https://authors.ietf.org/en/rfcxml-vocabula ry#figure --> <figure align="center"> <!-- https://authors.ietf.org/en/rfcxml-vocabula ry#figure -->
<name>Source code figure</name> <name>Hello World in C</name>
<sourcecode name="helloworld.c" type="c" markers="true"> <!-- https:// <!-- https://authors.ietf.org/en/rfcxml-vocabulary#sourcecode -->
authors.ietf.org/en/rfcxml-vocabulary#sourcecode -->
<!-- markers="true" means that the rendered file will have <CODE BEGIN S> and <CODE ENDS> added --> <!-- markers="true" means that the rendered file will have <CODE BEGIN S> and <CODE ENDS> added -->
<!-- The CDATA wrapper is optional but is strongly recommended to avoi d any unexpected processing <!-- The CDATA wrapper is optional but is strongly recommended to avoi d any unexpected processing
or issues with angle brackets. --> or issues with angle brackets. -->
<![CDATA[ <sourcecode name="helloworld.c" type="c" markers="true"><![CDATA[
#include <stdio.h> #include <stdio.h>
int main() { int main() {
printf("Hello World"); printf("Hello World");
return 0; return 0;
} }
]]> ]]></sourcecode>
</sourcecode>
</figure> </figure>
</section> </section>
<section> <section>
<name>Adding diagrams</name> <name>Adding diagrams</name>
<figure> <figure>
<name>A box</name> <name>A box</name>
<artset> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#artset -- > <artset> <!-- https://authors.ietf.org/en/rfcxml-vocabulary#artset -- >
<!-- This <artset> includes two <artwork> elements, each of a differen t type. Both are not <!-- This <artset> includes two <artwork> elements, each of a differen t type. Both are not
always needed. See https://authors.ietf.org/e/en/adding-diagrams --> always needed. See https://authors.ietf.org/e/en/adding-diagrams -->
<artwork type="svg" name="box.svg"> <!-- https://authors.ietf.org/e n/rfcxml-vocabulary#artwork --> <artwork type="svg" name="box.svg"> <!-- https://authors.ietf.org/e n/rfcxml-vocabulary#artwork -->
<!-- Inserting the SVG like this is only one way of adding an SVG diagram. Another way is <!-- Inserting the SVG like this is only one way of adding an SVG diagram. Another way is
to use the src attribute to point to an external file or URI. The name attribute to use the src attribute to point to an external file or URI. The name attribute
recommends a filename to use if the artwork is extracted to a file. --> recommends a filename to use if the artwork is extracted to a file. -->
<svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="71.0" height="40.0" viewBox="0 0 71 40"> <svg xmlns="http://www.w3.org/2000/svg" version="1.1" width="71.0" height="40.0" viewBox="0 0 71 40">
<g> <g>
<title>Layer 1</title> <title>Layer 1</title>
<rect x="4.5" y="6.5" width="61.0" height="27.0" stroke="black " stroke-width="1.0" stroke-linecap="square" stroke-linejoin="miter" fill="non e" /> <rect x="4.5" y="6.5" width="61.0" height="27.0" stroke="black " stroke-width="1.0" stroke-linecap="square" stroke-linejoin="miter" fill="non e" />
<text x="33.883" text-anchor="middle" y="26.559"> <text x="33.883" text-anchor="middle" y="26.559">
<tspan fill="black" font-size="13.0">A box</tspan> <tspan fill="black" font-size="13.0">A box</tspan>
</text> </text>
</g> </g>
</svg> </svg>
</artwork> </artwork>
<artwork type="ascii-art" name="box.txt"> <artwork type="ascii-art" name="box.txt">
<![CDATA[ <![CDATA[
+--------+ +--------+
| A box | | A box |
+--------+ +--------+
]]> ]]>
</artwork> </artwork>
</artset> </artset>
</figure> </figure>
</section> </section>
<section anchor="IANA"> <section anchor="IANA">
<!-- All drafts are required to have an IANA considerations section. See R FC 5226 for a guide.--> <!-- All drafts are required to have an IANA considerations section. See R FC 8126 for a guide.-->
<name>IANA Considerations</name> <name>IANA Considerations</name>
<t>This memo includes no request to IANA.</t> <t>This memo includes no request to IANA.</t>
</section> </section>
<section anchor="Security"> <section anchor="Security">
<!-- All drafts are required to have a security considerations section. See RFC 3552 for a guide. --> <!-- All drafts are required to have a security considerations section. See RFC 3552 for a guide. -->
<name>Security Considerations</name> <name>Security Considerations</name>
<t>This document should not affect the security of the Internet.</t> <t>This document should not affect the security of the Internet.</t>
</section> </section>
<!-- NOTE: The Acknowledgements and Contributors sections are at the end o f this template --> <!-- NOTE: The Acknowledgements and Contributors sections are at the end o f this template -->
</middle> </middle>
<back> <back>
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <name>Normative References</name>
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC .3552.xml"/> <xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC .3552.xml"/>
<!-- The recommended and simplest way to include a well known referenc <!-- The recommended and simplest way to include a well-known referenc
e --> e -->
</references>
<references>
<name>Informative References</name>
<reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rf c2119"> <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rf c2119">
<!-- Manually added reference --> <!-- Manually added reference -->
<front> <front>
<title>Key words for use in RFCs to Indicate Requirement Levels</t itle> <title>Key words for use in RFCs to Indicate Requirement Levels</t itle>
<author initials="S." surname="Bradner" fullname="S. Bradner"> <author initials="S." surname="Bradner" fullname="S. Bradner">
<organization/> <organization/>
</author> </author>
<date year="1997" month="March"/> <date year="1997" month="March"/>
<abstract> <abstract>
<t>In many standards track documents several words are used to s ignify the requirements in the specification. These words are often capitalize d. This document defines these words as they should be interpreted in IETF doc uments. This document specifies an Internet Best Current Practices for the Int ernet Community, and requests discussion and suggestions for improvements. <t>In many standards track documents several words are used to s ignify the requirements in the specification. These words are often capitalize d. This document defines these words as they should be interpreted in IETF doc uments. This document specifies an Internet Best Current Practices for the Int ernet Community, and requests discussion and suggestions for improvements.
</t> </t>
</abstract> </abstract>
</front> </front>
<seriesInfo name="BCP" value="14"/> <seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/> <seriesInfo name="RFC" value="2119"/>
<seriesInfo name="DOI" value="10.17487/RFC2119"/> <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference> </reference>
<xi:include href="https://www.rfc-editor.org/refs/bibxml/reference.RFC.
8174.xml"/>
</references>
<references>
<name>Informative References</name>
<reference anchor="exampleRefMin"> <reference anchor="exampleRefMin">
<!-- Example minimum reference --> <!-- Example minimum reference -->
<front> <front>
<title>Title</title> <title>Title</title>
<author initials="Initials" surname="Surname"> <author initials="Initials" surname="Surname">
<organization/> <organization/>
</author> </author>
<date year="2006"/> <date year="2006"/>
</front> </front>
</reference> </reference>
<reference anchor="exampleRefOrg" target="http://www.example.com/"> <reference anchor="exampleRefOrg" target="http://www.example.com/">
<!-- Example reference written by an organization not a person --> <!-- Example reference written by an organization not a person -->
<front> <front>
<title>Title</title> <title>Title</title>
<author> <author>
<organization>Organization</organization> <organization>Organization</organization>
</author> </author>
<date year="1984"/> <date year="1984"/>
</front> </front>
</reference> </reference>
</references> </references>
</references> </references>
<section> <section>
<name>Appendix 1</name> <name>Appendix 1</name>
<t>This becomes an Appendix</t> <t>This becomes an appendix.</t>
</section> </section>
<section anchor="Acknowledgements" numbered="false"> <section anchor="Acknowledgements" numbered="false">
<!-- an Acknowledgements section is optional --> <!-- an Acknowledgements section is optional -->
<name>Acknowledgements</name> <name>Acknowledgements</name>
<t>This template uses extracts from templates written by Pekka Savola, E lwyn Davies and <t>This template uses extracts from templates written by Pekka Savola, E lwyn Davies, and
Henrik Levkowetz.</t> Henrik Levkowetz.</t>
</section> </section>
<section anchor="Contributors" numbered="false"> <section anchor="Contributors" numbered="false">
<!-- a Contributors section is optional --> <!-- a Contributors section is optional -->
<name>Contributors</name> <name>Contributors</name>
<t>Thanks to all of the contributors.</t> <t>Thanks to all of the contributors.</t>
<!-- including contact information for contributors is optional -->
<contact fullname="Jane Doe" initials="J" surname="Doe"><!-- https://aut
hors.ietf.org/en/rfcxml-vocabulary#contact-->
<organization>Acme</organization>
<address>
<email>jdoe@example.com</email>
</address>
</contact>
</section> </section>
</back> </back>
</rfc> </rfc>
 End of changes. 21 change blocks. 
33 lines changed or deleted 51 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/

mirror server hosted at Truenetwork, Russian Federation.