-
Notifications
You must be signed in to change notification settings - Fork 27
/
Copy pathdraft-rfcxml-general-template-standard-00.xml
252 lines (213 loc) · 9.23 KB
/
draft-rfcxml-general-template-standard-00.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
<?xml version="1.0" encoding="utf-8"?>
<!--
draft-rfcxml-general-template-standard-00
This template includes examples of the most commonly used features of RFCXML with comments
explaining how to customise them. This template can be quickly turned into an I-D by editing
the examples provided. Look for [REPLACE], [REPLACE/DELETE], [CHECK] and edit accordingly.
Note - 'DELETE' means delete the element or attribute, not just the contents.
Documentation is at https://authors.ietf.org/en/templates-and-schemas
-->
<?xml-model href="rfc7991bis.rnc"?> <!-- Required for schema validation and schema-aware editing -->
<!-- <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> -->
<!-- This third-party XSLT can be enabled for direct transformations in XML processors, including most browsers -->
<!DOCTYPE rfc [
<!ENTITY nbsp " ">
<!ENTITY zwsp "​">
<!ENTITY nbhy "‑">
<!ENTITY wj "⁠">
]>
<!-- If further character entities are required then they should be added to the DOCTYPE above.
Use of an external entity file is not recommended. -->
<rfc
xmlns:xi="http://www.w3.org/2001/XInclude"
category="info"
docName="draft-rfcxml-general-template-standard-00"
ipr="trust200902"
obsoletes=""
updates=""
submissionType="IETF"
xml:lang="en"
version="3">
<!-- [REPLACE]
* docName with name of your draft
[CHECK]
* category should be one of std, bcp, info, exp, historic
* ipr should be one of trust200902, noModificationTrust200902, noDerivativesTrust200902, pre5378Trust200902
* updates can be an RFC number as NNNN
* obsoletes can be an RFC number as NNNN
-->
<front>
<title abbrev="Abbreviated Title">Title [REPLACE]</title>
<!-- [REPLACE/DELETE] abbrev. The abbreviated title is required if the full title is longer than 39 characters -->
<seriesInfo name="Internet-Draft" value="draft-rfcxml-general-template-standard-00 [REPLACE]"/>
<author fullname="fullname [REPLACE]" initials="Initials [REPLACE]" role="editor" surname="Surname [REPLACE]">
<!-- [CHECK]
* initials should not include an initial for the surname
* role="editor" is optional -->
<!-- Can have more than one author -->
<!-- all of the following elements are optional -->
<organization>Organization [REPLACE/DELETE]</organization>
<address>
<postal>
<!-- Reorder these if your country does things differently -->
<street>Street [REPLACE/DELETE]</street>
<city>City [REPLACE/DELETE]</city>
<region>Region [REPLACE/DELETE]</region>
<code>Postal code [REPLACE/DELETE]</code>
<country>Country [REPLACE/DELETE]</country>
<!-- Uses two letter country code -->
</postal>
<phone>Phone [REPLACE/DELETE]</phone>
<email>Email [REPLACE/DELETE]</email>
<!-- Can have more than one <email> element -->
<uri>URI [REPLACE/DELETE]</uri>
</address>
</author>
<date year="2023"/>
<!-- On draft subbmission:
* If only the current year is specified, the current day and month will be used.
* If the month and year are both specified and are the current ones, the current day will
be used
* If the year is not the current one, it is necessary to specify at least a month and day="1" will be used.
-->
<area>General</area>
<workgroup>Internet Engineering Task Force</workgroup>
<!-- "Internet Engineering Task Force" is fine for individual submissions. If this element is
not present, the default is "Network Working Group", which is used by the RFC Editor as
a nod to the history of the RFC Series. -->
<keyword>keyword</keyword>
<!-- [REPLACE/DELETE]. Multiple allowed. Keywords are incorporated into HTML output files for
use by search engines. -->
<abstract>
<t>Abstract [REPLACE]</t>
</abstract>
</front>
<middle>
<section>
<name>Introduction</name>
<t>Introductory text [REPLACE]</t>
<section>
<name>Requirements Language</name>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT
RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
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>
<!-- [CHECK] The 'Requirements Language' section is optional -->
</section>
<section>
<name>Body [REPLACE]</name>
<t>Body text [REPLACE]</t>
<ol>
<li>Ordered list item [REPLACE/DELETE]</li>
</ol>
<ul>
<li>Bulleted list item [REPLACE/DELETE]</li>
</ul>
<dl newline="true">
<!-- Omit newline="true" if you want each definition to start on the same line as the corresponding term -->
<dt>First term: [REPLACE/DELETE]</dt>
<dd>Definition of the first term [REPLACE/DELETE]</dd>
<dt>Second term: [REPLACE/DELETE]</dt>
<dd>Definition of the second term [REPLACE/DELETE]</dd>
</dl>
<table>
<thead>
<!-- [REPLACE/DELETE] a table header is optional -->
<tr><th>Column 1 [REPLACE]</th></tr>
</thead>
<tbody>
<tr><td>Cell [REPLACE]</td></tr>
</tbody>
</table>
<figure>
<name>Source [REPLACE]</name>
<sourcecode name="suggested filename [REPLACE/DELETE]" type="language [REPLACE/DELETE]" markers="true">
<![CDATA[
source code goes here [REPLACE]
]]>
</sourcecode>
<!-- [CHECK] markers="true" means that the rendered file will have <CODE BEGINS> and <CODE ENDS> added -->
</figure>
<figure>
<name>Diagram [REPLACE]</name>
<artset>
<!-- This <artset> includes two <artwork> elements, each of a different type -->
<artwork type="svg" src="https://www.rfc-editor.org/materials/format/svg/stream.svg" />
<!-- [REPLACE] src points to either a local file or a URI. -->
<artwork type="ascii-art" name="stream.txt">
<!-- [REPLACE/DELETE] name recommends a filename to use if the diagram is extracted -->
<![CDATA[
ascii-art diagram goes here [REPLACE]
]]>
</artwork>
</artset>
</figure>
</section>
<section anchor="IANA">
<!-- All drafts are required to have an IANA considerations section. See RFC 8126 for a guide.-->
<name>IANA Considerations</name>
<t>This memo includes no request to IANA. [CHECK]</t>
</section>
<section anchor="Security">
<!-- All drafts are required to have a security considerations section. See RFC 3552 for a guide. -->
<name>Security Considerations</name>
<t>This document should not affect the security of the Internet. [CHECK]</t>
</section>
<!-- NOTE: The Acknowledgements and Contributors sections are at the end of this template -->
</middle>
<back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
<!-- The recommended and simplest way to include a well known reference -->
</references>
<references>
<name>Informative References</name>
<reference anchor="exampleRefMin">
<!-- [REPLACE/DELETE] Example minimum reference -->
<front>
<title>Title [REPLACE]</title>
<author initials="Initials [REPLACE]" surname="Surname [REPLACE]">
<organization/>
</author>
<date year="2006"/>
<!-- [CHECK] -->
</front>
</reference>
<reference anchor="exampleRefOrg" target="http://www.example.com/">
<!-- [REPLACE/DELETE] Example reference written by an organization not a person -->
<front>
<title>Title [REPLACE]</title>
<author>
<organization>Organization [REPLACE]</organization>
</author>
<date year="1984"/>
<!-- [CHECK] -->
</front>
</reference>
</references>
</references>
<section>
<name>Appendix 1 [REPLACE/DELETE]</name>
<t>This becomes an Appendix [REPLACE]</t>
</section>
<section anchor="Acknowledgements" numbered="false">
<!-- [REPLACE/DELETE] an Acknowledgements section is optional -->
<name>Acknowledgements</name>
<t>This template uses extracts from templates written by Pekka Savola, Elwyn Davies and
Henrik Levkowetz. [REPLACE]</t>
</section>
<section anchor="Contributors" numbered="false">
<!-- [REPLACE/DELETE] a Contributors section is optional -->
<name>Contributors</name>
<t>Thanks to all of the contributors. [REPLACE]</t>
<!-- [CHECK] it is optional to add a <contact> record for some or all contributors -->
</section>
</back>
</rfc>