-
Notifications
You must be signed in to change notification settings - Fork 4
/
i-d-template.xml
138 lines (108 loc) · 3.18 KB
/
i-d-template.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
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rfc [
<!ENTITY % COMMON SYSTEM ".tools/bplate/common.ent">
%COMMON;
<!ENTITY % WG SYSTEM ".tools/bplate/ietf-wg.ent">
%WG;
<!ENTITY % stdrefs SYSTEM "stdrefs.ent">
%stdrefs;
<!ENTITY % figures SYSTEM "figures.ent">
%figures;
<!ENTITY % yang SYSTEM "yang.ent">
%yang;
]>
<?rfc strict="yes"?>
<?rfc toc="yes"?>
<?rfc tocdepth="3"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" submissionType="IETF" consensus="true">
<front>
<title abbrev="i-d-abbrev">I-D Title</title>
<author fullname="Albert U. Thor" initials="A. U." surname="Thor">
<organization>Example, Inc.</organization>
<address>
<email>a.u.thor@example.com</email>
</address>
</author>
<date year="YYYY-MM-DD"/>
<area/>
&netmod-wg; <!--or another WG -->
<abstract>
<t></t>
</abstract>
</front>
<middle>
<section anchor="introduction" title="Introduction">
<t>
<!-- Use this entity reference for including the standard text
explaining the symbols in YANG tree diagrams. -->
&treesym;
</t>
<!-- Figures are included like this (entity name = file name):
<figure>
&foo-model.tree;
</figure>
Files with figures and YANG modules (see below) should not
contain the <artwork> element - it is added automatically.
-->
</section>
<section anchor="yang" title="YANG Module">
&ed-hint-rfcno-rev;
<!-- YANG modules are included this way:
&ietf-foo.yang;
The <CODE BEGIN/END> delimiters are also added automatically.
-->
</section>
<section anchor="iana" title="IANA Considerations">
&ed-hint-rfcno;
<section anchor="iana-uri" title="URI Registrations">
<t>This document registers a URI in the "IETF XML Registry"
<xref target="RFC3688"/>. The following registration has been
made:</t>
<figure>
<artwork>
URI: urn:ietf:params:xml:ns:yang:%%MODNAME%%
Registrant Contact: The IESG.
XML: N/A, the requested URI is an XML namespace.
</artwork>
</figure>
</section>
<section anchor="iana-yang" title="YANG Module Registrations">
<t>This document registers a YANG module in the "YANG Module
Names" registry <xref target="RFC6020"/>. The following
registration has been made:</t>
<figure>
<artwork>
name: %%MODNAME%%
namespace: urn:ietf:params:xml:ns:yang:%%MODNAME%%
prefix: %%PRF%%
reference: RFC XXXX
</artwork>
</figure>
</section>
</section>
<section anchor="security" title="Security Considerations">
<t></t>
</section>
</middle>
<back>
<references title="Normative References">
&RFC2119;
&RFC3688;
&RFC6020;
<!-- Generate other references by "make refs",
and add entity references here. -->
</references>
<section anchor="rpc-example" title="Example: NETCONF <get> Reply">
<t></t>
<!-- Example XML documents can also be included in the same way:
<figure>
&example-get-reply.xml;
</figure>
-->
</section>
</back>
</rfc>