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
/
Copy pathdraft-brown-regtype.html
712 lines (671 loc) · 33.3 KB
/
draft-brown-regtype.html
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
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en"><head><title>Registration Type Extension for
the Extensible Provisioning Protocol (EPP)</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="description" content="Registration Type Extension for
the Extensible Provisioning Protocol (EPP)">
<meta name="keywords" content="EPP, XML">
<meta name="generator" content="xml2rfc v1.36 (http://xml.resource.org/)">
<style type='text/css'><!--
body {
font-family: verdana, charcoal, helvetica, arial, sans-serif;
font-size: small; color: #000; background-color: #FFF;
margin: 2em;
}
h1, h2, h3, h4, h5, h6 {
font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif;
font-weight: bold; font-style: normal;
}
h1 { color: #900; background-color: transparent; text-align: right; }
h3 { color: #333; background-color: transparent; }
td.RFCbug {
font-size: x-small; text-decoration: none;
width: 30px; height: 30px; padding-top: 2px;
text-align: justify; vertical-align: middle;
background-color: #000;
}
td.RFCbug span.RFC {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: bold; color: #666;
}
td.RFCbug span.hotText {
font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif;
font-weight: normal; text-align: center; color: #FFF;
}
table.TOCbug { width: 30px; height: 15px; }
td.TOCbug {
text-align: center; width: 30px; height: 15px;
color: #FFF; background-color: #900;
}
td.TOCbug a {
font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif;
font-weight: bold; font-size: x-small; text-decoration: none;
color: #FFF; background-color: transparent;
}
td.header {
font-family: arial, helvetica, sans-serif; font-size: x-small;
vertical-align: top; width: 33%;
color: #FFF; background-color: #666;
}
td.author { font-weight: bold; font-size: x-small; margin-left: 4em; }
td.author-text { font-size: x-small; }
/* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */
a.info {
/* This is the key. */
position: relative;
z-index: 24;
text-decoration: none;
}
a.info:hover {
z-index: 25;
color: #FFF; background-color: #900;
}
a.info span { display: none; }
a.info:hover span.info {
/* The span will display just on :hover state. */
display: block;
position: absolute;
font-size: smaller;
top: 2em; left: -5em; width: 15em;
padding: 2px; border: 1px solid #333;
color: #900; background-color: #EEE;
text-align: left;
}
a { font-weight: bold; }
a:link { color: #900; background-color: transparent; }
a:visited { color: #633; background-color: transparent; }
a:active { color: #633; background-color: transparent; }
p { margin-left: 2em; margin-right: 2em; }
p.copyright { font-size: x-small; }
p.toc { font-size: small; font-weight: bold; margin-left: 3em; }
table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; }
td.toc { font-size: small; font-weight: bold; vertical-align: text-top; }
ol.text { margin-left: 2em; margin-right: 2em; }
ul.text { margin-left: 2em; margin-right: 2em; }
li { margin-left: 3em; }
/* RFC-2629 <spanx>s and <artwork>s. */
em { font-style: italic; }
strong { font-weight: bold; }
dfn { font-weight: bold; font-style: normal; }
cite { font-weight: normal; font-style: normal; }
tt { color: #036; }
tt, pre, pre dfn, pre em, pre cite, pre span {
font-family: "Courier New", Courier, monospace; font-size: small;
}
pre {
text-align: left; padding: 4px;
color: #000; background-color: #CCC;
}
pre dfn { color: #900; }
pre em { color: #66F; background-color: #FFC; font-weight: normal; }
pre .key { color: #33C; font-weight: bold; }
pre .id { color: #900; }
pre .str { color: #000; background-color: #CFF; }
pre .val { color: #066; }
pre .rep { color: #909; }
pre .oth { color: #000; background-color: #FCF; }
pre .err { background-color: #FCC; }
/* RFC-2629 <texttable>s. */
table.all, table.full, table.headers, table.none {
font-size: small; text-align: center; border-width: 2px;
vertical-align: top; border-collapse: collapse;
}
table.all, table.full { border-style: solid; border-color: black; }
table.headers, table.none { border-style: none; }
th {
font-weight: bold; border-color: black;
border-width: 2px 2px 3px 2px;
}
table.all th, table.full th { border-style: solid; }
table.headers th { border-style: none none solid none; }
table.none th { border-style: none; }
table.all td {
border-style: solid; border-color: #333;
border-width: 1px 2px;
}
table.full td, table.headers td, table.none td { border-style: none; }
hr { height: 1px; }
hr.insert {
width: 80%; border-style: none; border-width: 0;
color: #CCC; background-color: #CCC;
}
--></style>
</head>
<body>
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1">
<tr><td class="header">Internet Engineering Task Force</td><td class="header">G. Brown</td></tr>
<tr><td class="header">Internet-Draft</td><td class="header">CentralNic Group plc</td></tr>
<tr><td class="header">Intended status: Experimental</td><td class="header">May 2016</td></tr>
<tr><td class="header">Expires: November 2, 2016</td><td class="header"> </td></tr>
</table></td></tr></table>
<h1><br />Registration Type Extension for
the Extensible Provisioning Protocol (EPP)<br />draft-brown-epp-regtype-00</h1>
<h3>Abstract</h3>
<p>This document describes an Extensible Provisioning Protocol
(EPP) extension mapping for registration types.
</p>
<h3>Status of this Memo</h3>
<p>
This Internet-Draft is submitted in full
conformance with the provisions of BCP 78 and BCP 79.</p>
<p>
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current
Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.</p>
<p>
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any time.
It is inappropriate to use Internet-Drafts as reference material or to cite
them other than as “work in progress.”</p>
<p>
This Internet-Draft will expire on November 2, 2016.</p>
<h3>Copyright Notice</h3>
<p>
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.</p>
<p>
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.</p>
<a name="toc"></a><br /><hr />
<h3>Table of Contents</h3>
<p class="toc">
<a href="#anchor1">1.</a>
Introduction<br />
<a href="#anchor2">1.1.</a>
Conventions Used in This Document<br />
<a href="#anchor3">2.</a>
Extension Elements<br />
<a href="#anchor4">3.</a>
EPP Command Mapping<br />
<a href="#anchor5">3.1.</a>
EPP Query Commands<br />
<a href="#anchor6">3.1.1.</a>
EPP <check> Command<br />
<a href="#anchor7">3.1.2.</a>
EPP <info> Command<br />
<a href="#anchor8">3.2.</a>
EPP Transform Commands<br />
<a href="#anchor9">3.2.1.</a>
EPP <create> Command<br />
<a href="#anchor10">3.2.2.</a>
EPP <update> Command<br />
<a href="#anchor11">3.3.</a>
Formal Syntax<br />
<a href="#Security">4.</a>
Security Considerations<br />
<a href="#IANA">5.</a>
IANA Considerations<br />
<a href="#anchor12">5.1.</a>
XML Namespace<br />
<a href="#anchor13">5.2.</a>
EPP Extension Registry<br />
<a href="#rfc.references1">6.</a>
Normative References<br />
<a href="#rfc.authors">§</a>
Author's Address<br />
</p>
<br clear="all" />
<a name="anchor1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1"></a><h3>1.
Introduction</h3>
<p>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.
</p>
<a name="anchor2"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.1.1"></a><h3>1.1.
Conventions Used in This Document</h3>
<p>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
<a class='info' href='#RFC2119'>RFC 2119<span> (</span><span class='info'>Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.</span><span>)</span></a> [RFC2119].
</p>
<p>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.
</p>
<p>"regtype" is used as an abbreviation for
"urn:ietf:params:xml:ns:regtype-0.2". 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.
</p>
<p>(Note to RFC Editor: remove the following paragraph before
publication as an RFC.)
</p>
<p>The XML namespace prefix above contains a version number,
specifically "0.2". 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.
</p>
<a name="anchor3"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.2"></a><h3>2.
Extension Elements</h3>
<p>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.
</p>
<p>The semantics of this token are not discussed in this document; and
are a matter of mutual prior agreement between client and server.
</p>
<a name="anchor4"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3"></a><h3>3.
EPP Command Mapping</h3>
<p>A detailed description of the EPP syntax and semantics can be found in
<a class='info' href='#RFC5730'>[RFC5730]<span> (</span><span class='info'>Hollenbeck, S., “Extensible Provisioning Protocol (EPP),” August 2009.</span><span>)</span></a>.
</p>
<a name="anchor5"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1"></a><h3>3.1.
EPP Query Commands</h3>
<p>This extension does not add any elements to the EPP <poll>
command and response.
</p>
<a name="anchor6"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1.1"></a><h3>3.1.1.
EPP <check> Command</h3>
<p>This extension defines additional elements for the EPP
<check> command.
</p>
<p>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.
</p>
<p>Example <check> command:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
C: <?xml version="1.0" encoding="UTF-8" standalone="no"?>
C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <check>
C: <domain:check
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.xyz</domain:name>
C: </domain:check>
C: </check>
C: <extension>
C: <regtype:check
C: xmlns:regtype="urn:ietf:params:xml:ns:regtype-0.2">
C: <regtype:type>foobar</regtype:type>
C: </regtype:check>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C: </epp></pre></div>
<p>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.
</p>
<a name="anchor7"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.1.2"></a><h3>3.1.2.
EPP <info> Command</h3>
<p>This extension defines additional elements for the EPP
<info> command and response.
</p>
<p>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.
</p>
<p>Example <info> response:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
S: <?xml version="1.0" encoding="utf-8" standalone="no"?>
S: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
S: <response>
S: <result code="1000">
S: <msg>Command completed successfully</msg>
S: </result>
S: <resData>
S: <domain:infData
S: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
S: <domain:name>example.com</domain:name>
S: <domain:roid>EXAMPLE1-REP</domain:roid>
S: <domain:status s="ok" />
S: <domain:registrant>jd1234</domain:registrant>
S: <domain:contact type="admin">sh8013</domain:contact>
S: <domain:contact type="tech">sh8013</domain:contact>
S: <domain:ns>
S: <domain:hostObj>ns1.example.com</domain:hostObj>
S: <domain:hostObj>ns1.example.net</domain:hostObj>
S: </domain:ns>
S: <domain:clID>ClientX</domain:clID>
S: <domain:crID>ClientY</domain:crID>
S: <domain:crDate>1999-04-03T22:00:00.0Z</domain:crDate>
S: <domain:upID>ClientX</domain:upID>
S: <domain:upDate>1999-12-03T09:00:00.0Z</domain:upDate>
S: <domain:exDate>2005-04-03T22:00:00.0Z</domain:exDate>
S: <domain:trDate>2000-04-08T09:00:00.0Z</domain:trDate>
S: <domain:authInfo>
S: <domain:pw>2fooBAR</domain:pw>
S: </domain:authInfo>
S: </domain:infData>
S: </resData>
S: <extension>
S: <regtype:infData
S: xmlns:regtype="urn:ietf:params:xml:ns:regtype-0.2">
S: <regtype:type>foobar</regtype:type>
S: </regtype:infData>
S: </extension>
S: <trID>
S: <clTRID>ABC-12345</clTRID>
S: <svTRID>54322-XYZ</svTRID>
S: </trID>
S: </response>
S: </epp>
</pre></div>
<a name="anchor8"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2"></a><h3>3.2.
EPP Transform Commands</h3>
<p>This extension does not add elements to the EPP <delete>,
<renew> or <transfer> commands and responses.
</p>
<a name="anchor9"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.1"></a><h3>3.2.1.
EPP <create> Command</h3>
<p>This extension adds elements to the EPP <create> command.
No additional elements are defined for the EPP <create> response.
</p>
<p>When submitting a <create> command to the server, the client
MAY include in the <extension> element a <regtype:create>
element.
</p>
<p>This element MUST include a <regtype:type> element
which includes the token for the domain name.
</p>
<p>Example <create> command:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <create>
C: <domain:create
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name>
C: <domain:period unit="y">2</domain:period>
C: <domain:ns>
C: <domain:hostObj>ns1.example.net</domain:hostObj>
C: <domain:hostObj>ns2.example.net</domain:hostObj>
C: </domain:ns>
C: <domain:registrant>jd1234</domain:registrant>
C: <domain:contact type="admin">sh8013</domain:contact>
C: <domain:contact type="tech">sh8013</domain:contact>
C: <domain:authInfo>
C: <domain:pw>2fooBAR</domain:pw>
C: </domain:authInfo>
C: </domain:create>
C: </create>
C: <extension>
C: <regtype:create
C: xmlns:regtype="urn:ietf:params:xml:ns:regtype-0.2">
C: <regtype:type>foobar</regtype:type>
C: </regtype:create>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C: </epp>
</pre></div>
<p>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.
</p>
<a name="anchor10"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.2.2"></a><h3>3.2.2.
EPP <update> Command</h3>
<p>This extension adds elements to the EPP <update> command.
No additional elements are defined for the EPP <update> response.
</p>
<p>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.
</p>
<p>Example <update> command:
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
C: <?xml version="1.0" encoding="utf-8" standalone="no"?>
C: <epp xmlns="urn:ietf:params:xml:ns:epp-1.0">
C: <command>
C: <update>
C: <domain:update
C: xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">
C: <domain:name>example.com</domain:name>
C: </domain:update>
C: </update>
C: <extension>
C: <regtype:update
C: xmlns:regtype="urn:ietf:params:xml:ns:regtype-0.2">
C: <regtype:chg>
C: <regtype:type>foobar</regtype:type>
C: </regtype:chg>
C: </regtype:update>
C: </extension>
C: <clTRID>ABC-12345</clTRID>
C: </command>
C: </epp>
</pre></div>
<p>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.
</p>
<a name="anchor11"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.3.3"></a><h3>3.3.
Formal Syntax</h3>
<p>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.
</p>
<p>Copyright (c) 2015 IETF Trust and the persons identified as authors
of the code. All rights reserved.
</p>
<p>Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
</p>
<p></p>
<ul class="text">
<li>Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
</li>
<li>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.
</li>
<li>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.
</li>
</ul>
<p>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.
</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>
BEGIN
<?xml version="1.0" encoding="utf-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:regtype="urn:ietf:params:xml:ns:regtype-0.2"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
targetNamespace="urn:ietf:params:xml:ns:regtype-0.2"
elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<annotation>
<documentation>Extensible Provisioning Protocol
v1.0 domain name extension schema for
registration type.</documentation>
</annotation>
<!--
Child elements found in EPP commands and responses
-->
<element name="check" type="regtype:checkType" />
<element name="infData" type="regtype:infDataType" />
<element name="create" type="regtype:createType" />
<element name="update" type="regtype:updateType" />
<!--
<check> command
-->
<complexType name="checkType">
<sequence>
<element name="type" type="eppcom:minTokenType" />
</sequence>
</complexType>
<!--
server <info> result
-->
<complexType name="infDataType">
<sequence>
<element name="type" type="eppcom:minTokenType"
minOccurs="0" />
</sequence>
</complexType>
<!--
<create> command
-->
<complexType name="createType">
<sequence>
<element name="type" type="eppcom:minTokenType"
minOccurs="0" />
</sequence>
</complexType>
<!--
<update> command
-->
<complexType name="updateType">
<sequence>
<element name="chg" type="regtype:chgType" />
</sequence>
</complexType>
<complexType name="chgType">
<sequence>
<element name="type" type="eppcom:minTokenType"
minOccurs="0" />
</sequence>
</complexType>
</schema>
END</pre></div>
<a name="Security"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.4"></a><h3>4.
Security Considerations</h3>
<p>The mapping extensions described in this document do not provide any
security services beyond those described by <a class='info' href='#RFC5730'>EPP<span> (</span><span class='info'>Hollenbeck, S., “Extensible Provisioning Protocol (EPP),” August 2009.</span><span>)</span></a> [RFC5730],
the <a class='info' href='#RFC5731'>EPP domain name mapping<span> (</span><span class='info'>Hollenbeck, S., “Extensible Provisioning Protocol (EPP) Domain Name Mapping,” August 2009.</span><span>)</span></a> [RFC5731], and protocol
layers used by EPP. The security considerations described in these other
specifications apply to this specification as well.
</p>
<a name="IANA"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5"></a><h3>5.
IANA Considerations</h3>
<a name="anchor12"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.1"></a><h3>5.1.
XML Namespace</h3>
<p>This document uses URNs to describe XML namespaces and XML schemas
conforming to a registry mechanism described in <a class='info' href='#RFC3688'>[RFC3688]<span> (</span><span class='info'>Mealling, M., “The IETF XML Registry,” January 2004.</span><span>)</span></a>.
The folllowing URI assignment is requested of the IANA:
</p>
<p>URI: urn:ietf:params:xml:ns:regtype-0.2
</p>
<p>Registrant Contact: See the "Author's Address" section of this
document.
</p>
<p>XML: See the "Formal Syntax" section of this document.
</p>
<a name="anchor13"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<a name="rfc.section.5.2"></a><h3>5.2.
EPP Extension Registry</h3>
<p>The EPP extension described in this document should be registered
by the IANA in the EPP Extension Registry described in <a class='info' href='#RFC7451'>[RFC7451]<span> (</span><span class='info'>Hollenbeck, S., “Extension Registry for the Extensible Provisioning Protocol,” February 2015.</span><span>)</span></a>. The details of the registration are as follows:
</p>
<p>Name of Extension: EPP Fee Extension
</p>
<p>Document status: Experimental
</p>
<p>Reference: (insert reference to RFC version of this document)
</p>
<p>Registrant Name and Email Address: See the "Author's Address" section
of this document.
</p>
<p>TLDs: any
</p>
<p>IPR Disclosure: none
</p>
<p>Status: active
</p>
<p>Notes: none
</p>
<a name="rfc.references1"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>6. Normative References</h3>
<table width="99%" border="0">
<tr><td class="author-text" valign="top"><a name="RFC2119">[RFC2119]</a></td>
<td class="author-text">Bradner, S., “<a href="http://www.rfc-editor.org/info/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>,” BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC3688">[RFC3688]</a></td>
<td class="author-text">Mealling, M., “<a href="http://www.rfc-editor.org/info/rfc3688">The IETF XML Registry</a>,” BCP 81, RFC 3688, DOI 10.17487/RFC3688, January 2004.</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC5730">[RFC5730]</a></td>
<td class="author-text">Hollenbeck, S., “<a href="http://www.rfc-editor.org/info/rfc5730">Extensible Provisioning Protocol (EPP)</a>,” STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009.</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC5731">[RFC5731]</a></td>
<td class="author-text">Hollenbeck, S., “<a href="http://www.rfc-editor.org/info/rfc5731">Extensible Provisioning Protocol (EPP) Domain Name Mapping</a>,” STD 69, RFC 5731, DOI 10.17487/RFC5731, August 2009.</td></tr>
<tr><td class="author-text" valign="top"><a name="RFC7451">[RFC7451]</a></td>
<td class="author-text">Hollenbeck, S., “<a href="http://www.rfc-editor.org/info/rfc7451">Extension Registry for the Extensible Provisioning Protocol</a>,” RFC 7451, DOI 10.17487/RFC7451, February 2015.</td></tr>
</table>
<a name="rfc.authors"></a><br /><hr />
<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table>
<h3>Author's Address</h3>
<table width="99%" border="0" cellpadding="0" cellspacing="0">
<tr><td class="author-text"> </td>
<td class="author-text">Gavin Brown</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">CentralNic Group plc</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">35-39 Moorgate</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">London, England EC2R 6AR</td></tr>
<tr><td class="author-text"> </td>
<td class="author-text">GB</td></tr>
<tr><td class="author" align="right">Phone: </td>
<td class="author-text">+44 20 33 88 0600</td></tr>
<tr><td class="author" align="right">Email: </td>
<td class="author-text"><a href="mailto:gavin.brown@centralnic.com">gavin.brown@centralnic.com</a></td></tr>
<tr><td class="author" align="right">URI: </td>
<td class="author-text"><a href="https://www.centralnic.com">https://www.centralnic.com</a></td></tr>
</table>
</body></html>