This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
draft-brown-regtype.xml.in
321 lines (247 loc) · 13 KB
/
draft-brown-regtype.xml.in
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
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
<?xml version="1.0" encoding="us-ascii"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!-- when the namespace version bumps, update this and it will update
everywhere -->
<!ENTITY VERSION "0.2">
<!ENTITY I-D.narten-iana-considerations-rfc2434bis SYSTEM
"http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.narten-iana-considerations-rfc2434bis.xml">
<!ENTITY RFC2119 SYSTEM
"http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3688 SYSTEM
"http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml">
<!ENTITY RFC5730 SYSTEM
"http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5730.xml">
<!ENTITY RFC5731 SYSTEM
"http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5731.xml">
<!ENTITY RFC7451 SYSTEM
"http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7451.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<?rfc comments="yes" ?>
<?rfc inline="yes" ?>
<rfc category="exp" docName="draft-brown-epp-regtype-00" ipr="trust200902">
<front>
<title abbrev="Registration Type Extension">Registration Type Extension for
the Extensible Provisioning Protocol (EPP)</title>
<author fullname="Gavin Brown" initials="G" surname="Brown">
<organization>CentralNic Group plc</organization>
<address>
<postal>
<street>35-39 Moorgate</street>
<city>London</city>
<region>England</region>
<code>EC2R 6AR</code>
<country>GB</country>
</postal>
<phone>+44 20 33 88 0600</phone>
<email>gavin.brown@centralnic.com</email>
<uri>https://www.centralnic.com</uri>
</address>
</author>
<date month="May" year="2016" />
<area>Applications</area>
<workgroup>Internet Engineering Task Force</workgroup>
<keyword>EPP, XML</keyword>
<abstract><t>This document describes an Extensible Provisioning Protocol
(EPP) extension mapping for registration types.</t></abstract>
</front>
<middle>
<section title="Introduction">
<t>This document describes a general purpose framework whereby an EPP
client can provide an EPP server with a simple token-based registration
"type" for domain objects.</t>
<section title="Conventions Used in This Document">
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in
<xref target="RFC2119">RFC 2119</xref>.</t>
<t>XML is case sensitive. Unless stated otherwise, XML specifications
and examples provided in this document MUST be interpreted in the
character case presented in order to develop a conforming
implementation.</t>
<t>"regtype" is used as an abbreviation for
"urn:ietf:params:xml:ns:regtype-&VERSION;". The XML namespace prefix
"regtype" is used, but implementations MUST NOT depend on it and instead
employ a proper namespace-aware XML parser and serializer to interpret
and output the XML documents.</t>
<t>(Note to RFC Editor: remove the following paragraph before
publication as an RFC.)</t>
<t>The XML namespace prefix above contains a version number,
specifically "&VERSION;". This version number will increment with
successive versions of this document, and will reach 1.0 if and when
this document is published as an RFC. This permits clients to
distinguish which version of the extension a server has implemented.</t>
</section>
</section>
<section title="Extension Elements">
<t>This document defines a single extension element, <regtype:type>.
The XML schema (which can be found in the "Formal Syntax" section below)
allows the contents of this element to be any valid token.</t>
<t>The semantics of this token are not discussed in this document; and
are a matter of mutual prior agreement between client and server.</t>
</section>
<section title="EPP Command Mapping">
<t>A detailed description of the EPP syntax and semantics can be found in
<xref target="RFC5730" />.</t>
<section title="EPP Query Commands">
<t>This extension does not add any elements to the EPP <poll>
command and response.</t>
<section title="EPP <check> Command">
<t>This extension defines additional elements for the EPP
<check> command.</t>
<t>The <check> command MAY contain an <extension> element
which MAY contain a <regtype:check> element. The <regtype:check>
element contains a <regtype:type> element which contains a token.</t>
<t>Example <check> command:</t>
<figure><artwork>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="text"
href="examples/check-command.txt" /></artwork></figure>
<t>This extension does not define additional elements for <check>
responses. When a server receeives a <check> command containing the
above elements, it MUST validate the supplied <regtype:type> token
when determining the availability of the domains in the <domain:check>
element, according to its own policy. If any subsequent <create>
commands for the domains would be rejected because the value of the
<regtype:type> element would not be permitted, then the "avail"
attribute of the <domain:name> elements MUST BE false. The server
MAY include a description of the nature of the policy violation in the
<domain:reason> element.</t>
</section>
<section title="EPP <info> Command">
<t>This extension defines additional elements for the EPP
<info> command and response.</t>
<t>When a server receives an <info> command for a domain for which
a "type" attribute has been stored, it MAY (depending on server policy)
include a <regtype:infData> element in the <extension> element
of the response. This element MUST include a <regtype:type> element
which includes the token that has been stored for the domain name.</t>
<t>Example <info> response:</t>
<figure><artwork>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="text"
href="examples/info-response.txt" /></artwork></figure>
</section>
</section>
<section title="EPP Transform Commands">
<t>This extension does not add elements to the EPP <delete>,
<renew> or <transfer> commands and responses.</t>
<section title="EPP <create> Command">
<t>This extension adds elements to the EPP <create> command.
No additional elements are defined for the EPP <create> response.</t>
<t>When submitting a <create> command to the server, the client
MAY include in the <extension> element a <regtype:create>
element.</t>
<t>This element MUST include a <regtype:type> element
which includes the token for the domain name.</t>
<t>Example <create> command:</t>
<figure><artwork>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="text"
href="examples/create-command.txt" /></artwork></figure>
<t>A server MAY choose to reject the <create> command if it
considers the value of the <regtype:create> to be invalid, in
which case it should return a 2306 "Parameter value policy" error.</t>
</section>
<section title="EPP <update> Command">
<t>This extension adds elements to the EPP <update> command.
No additional elements are defined for the EPP <update> response.</t>
<t>When submitting an <update> command to the server, the client
MAY include in the <extension> element a <regtype:update>
element. This element MUST include a <regtype:chg> element
which includes <regtype:type> element, which contains the new
token for the domain name.</t>
<t>Example <update> command:</t>
<figure><artwork>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" parse="text"
href="examples/update-command.txt" /></artwork></figure>
<t>A server MAY choose to reject the <update> command if it
considers the value of the <regtype:update> to be invalid, in
which case it should return a 2306 "Parameter value policy" error.</t>
</section>
</section>
<section title="Formal Syntax">
<t>An EPP object mapping is specified in XML Schema notation. The formal
syntax presented here is a complete schema representation of the object
mapping suitable for automated validation of EPP XML instances.</t>
<t>Copyright (c) 2015 IETF Trust and the persons identified as authors
of the code. All rights reserved.</t>
<t>Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:</t>
<t><list style="symbols">
<t>Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.</t>
<t>Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
distribution.</t>
<t>Neither the name of Internet Society, IETF or IETF Trust, nor the
names of specific contributors, may be used to endorse or promote
products derived from this software without specific prior written
permission.</t>
</list></t>
<t>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</t>
<figure><artwork>
BEGIN
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="regtype.xsd"
parse="text"/>
END</artwork></figure>
</section>
</section>
<section anchor="Security" title="Security Considerations">
<t>The mapping extensions described in this document do not provide any
security services beyond those described by <xref target="RFC5730">EPP</xref>,
the <xref target="RFC5731">EPP domain name mapping</xref>, and protocol
layers used by EPP. The security considerations described in these other
specifications apply to this specification as well.</t></section>
<section anchor="IANA" title="IANA Considerations">
<section title="XML Namespace">
<t>This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in <xref target="RFC3688" />.
The folllowing URI assignment is requested of the IANA:</t>
<t>URI: urn:ietf:params:xml:ns:regtype-&VERSION;</t>
<t>Registrant Contact: See the "Author's Address" section of this
document.</t>
<t>XML: See the "Formal Syntax" section of this document.</t>
</section>
<section title="EPP Extension Registry">
<t>The EPP extension described in this document should be registered
by the IANA in the EPP Extension Registry described in <xref
target="RFC7451"/>. The details of the registration are as follows:</t>
<t>Name of Extension: EPP Fee Extension</t>
<t>Document status: Experimental</t>
<t>Reference: (insert reference to RFC version of this document)</t>
<t>Registrant Name and Email Address: See the "Author's Address" section
of this document.</t>
<t>TLDs: any</t>
<t>IPR Disclosure: none</t>
<t>Status: active</t>
<t>Notes: none</t>
</section>
</section>
</middle>
<back>
<references title="Normative References">
&RFC2119;
&RFC3688;
&RFC5730;
&RFC5731;
&RFC7451;
</references>
</back>
</rfc>