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
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
|
<pre>Network Working Group A. Newton
Request for Comments: 5144 American Registry for Internet Numbers
Category: Standards Track M. Sanz
DENIC eG
February 2008
<span class="h1">A Domain Availability Check (DCHK) Registry Type for</span>
<span class="h1">the Internet Registry Information Service (IRIS)</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Abstract
This document describes a lightweight domain availability service
using the Internet Registry Information Service (IRIS) framework and
the data model of the IRIS Domain Registry (DREG) service.
<span class="grey">Newton & Sanz Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-2">2</a>. Document Terminology . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Domain Availability Check Registry . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. Schema Description . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.1.1">3.1.1</a>. The <domain> Result . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-3.1.2">3.1.2</a>. Support for <iris:lookupEntity> . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-3.2">3.2</a>. DCHK Formal XML Syntax . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
3.3. Blocks Extensible Exchange Protocol (BEEP) Transport
Compliance . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-3.3.1">3.3.1</a>. Message Pattern . . . . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-3.3.2">3.3.2</a>. Server Authentication . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-3.4">3.4</a>. URI Resolution . . . . . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-3.4.1">3.4.1</a>. Application Service Label . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-3.4.2">3.4.2</a>. Bottom-Up Resolution . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-3.4.3">3.4.3</a>. Top-Down Resolution . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-4">4</a>. Internationalization Considerations . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-5.1">5.1</a>. XML Namespace Registration . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-5.2">5.2</a>. XML Schema Registration . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-5.3">5.3</a>. S-NAPTR Registration . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-5.4">5.4</a>. BEEP Registration . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-6">6</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<span class="grey">Newton & Sanz Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
This document describes a lightweight service for checking the
availability of domain names. This service is based on the IRIS
framework and uses the data model defined by <a href="./rfc3982">RFC 3982</a> [<a href="#ref-7" title=""IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)"">7</a>]. By doing
this, the domain availability service has the advantages provided by
IRIS and DREG, such as well-known methods for server navigation,
structured queries and results, and layered extensibility.
The use of IRIS for this service also allows seamless integration
between the domain availability service and the service provided by
DREG. This allows a user to find the availability status of a domain
and reference the full registration information in DREG.
The data model in this service (called a registry schema in IRIS
terms) is a strict subset of the DREG data model. This enables
implementors to directly reuse DREG code paths and allows operators
to deploy the service in either the same server processes as a DREG
service (same host and port) or in a different server process
(different port) or machine (different host).
As an example, an operator may wish to deploy both types of service
on the same set of machines. As time goes on, the operator may then
decide to segregate the services, placing the domain availability
service on one set of machines and the DREG service on a separate set
of machines with a stricter set of controls. Either deployment
scenario is transparent to the end user and always appears to be
seamlessly complementary.
When coupled with [<a href="#ref-9" title=""A Lightweight UDP Transfer Protocol for the Internet Registry Information Service"">9</a>], this domain availability service is
lightweight and extremely efficient for high-volume, public-facing
service.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Document Terminology</span>
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 href="./rfc2119">RFC 2119</a> [<a href="#ref-2" title=""Key words for use in RFCs to Indicate Requirement Levels"">2</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Domain Availability Check Registry</span>
The data model used for the domain availability check (DCHK) service
is a strict subset of the DREG data model. This section describes
the DCHK registry type.
<span class="grey">Newton & Sanz Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Schema Description</span>
References to XML elements with no namespace qualifier are from the
schema defined in <a href="#section-3.2">Section 3.2</a>. References to elements and attributes
with the "iris" XML namespace qualifier are from the schema defined
in IRIS [<a href="#ref-6" title=""IRIS: The Internet Registry Information Service (IRIS) Core Protocol"">6</a>].
The schema present in this document is tied to the protocol version
associated with the XML namespace URI defined in <a href="#section-5.2">Section 5.2</a>.
Extensions to the present DCHK schema are allowed, though not
recommended, but would require a new version. Please refer to <a href="./rfc3981">RFC</a>
<a href="./rfc3981">3981</a> [<a href="#ref-6" title=""IRIS: The Internet Registry Information Service (IRIS) Core Protocol"">6</a>] for more details about versioning the IRIS protocol.
The descriptions contained within this section refer to XML elements
and attributes and their relation to the exchange of data within the
protocol. These descriptions also contain specifications outside the
scope of the formal XML syntax. Therefore, this section will use
terms defined by <a href="./rfc2119">RFC 2119</a> [<a href="#ref-2" title=""Key words for use in RFCs to Indicate Requirement Levels"">2</a>] to describe the specification outside
the scope of the formal XML syntax. While reading this section,
please reference <a href="#section-3.2">Section 3.2</a> for needed details on the formal XML
syntax.
<span class="h4"><a class="selflink" id="section-3.1.1" href="#section-3.1.1">3.1.1</a>. The <domain> Result</span>
An example of a <domain> result:
<domain
authority="iana.org" registryType="dchk1"
entityClass="domain-name" entityName="example.com">
<domainName>example.com</domainName>
<status><active/></status>
</domain>
<domain> Example
The <domain> result represents an instance of a domain assignment.
The children of the <domain> element are as follows:
o <domainName> - the full name of the domain as it is in DNS. The
contents of this element MUST be a domain name as specified by <a href="./rfc1035">RFC</a>
<a href="./rfc1035">1035</a> [<a href="#ref-1" title=""Domain names - implementation and specification"">1</a>].
o <idn> - the name of the domain in nameprep form, if applicable.
See <a href="./rfc3491">RFC 3491</a> [<a href="#ref-3" title=""Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)"">3</a>].
o <status> - this element may contain child elements representing
domain status information. It defines the following status types:
<span class="grey">Newton & Sanz Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
* <active> - available via DNS (either via delegation or direct
publication).
* <inactive> - unavailable via DNS.
* <dispute> - registrant assignment is in dispute.
* <addPeriod> - the domain is in the grace period after creation
or activation (see <a href="./rfc3915">RFC 3915</a> [<a href="#ref-5" title=""Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)"">5</a>]).
* <renewPeriod> - the domain is in the grace period after renewal
(see <a href="./rfc3915">RFC 3915</a> [<a href="#ref-5" title=""Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)"">5</a>]).
* <autoRenewPeriod> - the domain is in the grace period after
automatic renewal (see <a href="./rfc3915">RFC 3915</a> [<a href="#ref-5" title=""Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)"">5</a>]).
* <transferPeriod> - the domain is in the grace period after
transfer (see <a href="./rfc3915">RFC 3915</a> [<a href="#ref-5" title=""Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)"">5</a>]).
* <redemptionPeriod> - the domain is in the grace period after
deletion (see <a href="./rfc3915">RFC 3915</a> [<a href="#ref-5" title=""Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)"">5</a>]).
* <policyCompliant> - the domain is considered compliant
according to a given policy specified by the substatus
identifier.
* <policyNoncompliant> - the domain is not considered compliant
according to a given policy specified by the substatus
identifier.
* <reserved> - the domain is reserved and is not available for
registration under normal registration procedures.
* <create> - specifies the creation of the domain in the
registration system. This status is usually further refined by
the disposition attribute.
* <delete> - specifies the deletion of the domain in the
registration system. This status is usually further refined by
the disposition attribute.
* <renew> - specifies the renewal of domain registration. This
status is usually further refined by the disposition attribute.
* <restore> - specifies the restoration to the previous state of
the domain before it was deleted. This status is usually
further refined by the disposition attribute.
<span class="grey">Newton & Sanz Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
* <transfer> - specifies the transfer of the domain from one
responsible or owning entity in the registration system to
another. This status is usually further refined by the
disposition attribute.
* <update> - specifies a general modification of the domain
information. This status is usually be further refined by the
disposition attribute.
* <other> - specifies a registration system specific status of
the domain.
o <registrationReference> - an element containing an entity
reference, the referent of which MUST be either a <domain>
(<a href="#section-3.1.1">Section 3.1.1</a>) or a <domain> as defined by <a href="./rfc3982">RFC 3982</a> [<a href="#ref-7" title=""IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)"">7</a>]. The
intent of this element is to point to the downstream registration
reference. Therefore, if this is a result given back by a domain
registry, it should point to the domain in the domain registrar or
registrant service.
o <createdDateTime> - an element containing the date and time of the
creation of this domain.
o <initialDelegationDateTime> - an element containing the date and
time of the initial delegation of this domain.
o <expirationDateTime> - an element containing the date and time of
the expiration of this domain.
o <lastDatabaseUpdateDateTime> - an element containing the date and
time of the last actualization of the database that is the source
for this result.
o <iris:seeAlso> - an element containing an entity reference
specifying a referent that is indirectly associated with this
domain.
<span class="h5"><a class="selflink" id="section-3.1.1.1" href="#section-3.1.1.1">3.1.1.1</a>. Domain Status Type</span>
Each element of type 'domainStatusType' has the following
composition:
o <appliedDate> - an optional child element containing the date
applicable to creation of the status.
o <ticket> - an optional child element containing a service ticket
identifier relevant to the status.
<span class="grey">Newton & Sanz Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
o <description> - zero or more child elements with text to describe
the status in natural language. Each of these elements MUST have
a 'language' attribute describing the language of the description
element.
o <subStatus> - a child element indicating further status
information. Values for this element are not defined by this
specification. This child element has a required 'authority'
attribute to indicate the origin of the specification of the value
of this element.
o 'actor' - an optional attribute indicating the acting entity for
which this status is applied. The values may be "registry",
"registrar", or "registrationServiceProvider".
o 'disposition' - an optional attribute indicating the nature of
this status. The values may be "pending" or "prohibited".
o 'scope' - an optional attribute indicating the context or origin
of the status value.
<span class="h4"><a class="selflink" id="section-3.1.2" href="#section-3.1.2">3.1.2</a>. Support for <iris:lookupEntity></span>
The following types of entity classes are recognized by the
<lookupEntity> query of IRIS for this registry:
o domain-name - the fully qualified name of a domain. This is a
domain name as specified by <a href="./rfc1035">RFC 1035</a> [<a href="#ref-1" title=""Domain names - implementation and specification"">1</a>]. Yields a <domain>
(<a href="#section-3.1.1">Section 3.1.1</a>) in the response.
o idn - the fully qualified name of a domain in nameprep form (see
<a href="./rfc3491">RFC 3491</a> [<a href="#ref-3" title=""Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)"">3</a>]). Yields a <domain> (<a href="#section-3.1.1">Section 3.1.1</a>) in the response.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. DCHK Formal XML Syntax</span>
This registry schema is specified in the XML Schema notation (see
[<a href="#ref-10" title=""XML Schema Part 2: Datatypes"">10</a>] and [<a href="#ref-11" title=""XML Schema Part 1: Structures"">11</a>]). The formal syntax presented here is a complete
schema representation of an XML instance when combined with the
formal schema syntax of IRIS.
<?xml version="1.0"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:dchk="urn:ietf:params:xml:ns:dchk1"
xmlns:iris="urn:ietf:params:xml:ns:iris1"
targetNamespace="urn:ietf:params:xml:ns:dchk1"
elementFormDefault="qualified" >
<span class="grey">Newton & Sanz Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
<import namespace="urn:ietf:params:xml:ns:iris1" />
<annotation>
<documentation>
Domain availability check schema
derived from IRIS schema
</documentation>
</annotation>
<!-- ========================================= -->
<!-- -->
<!-- Result Types -->
<!-- -->
<!-- ========================================= -->
<!-- -->
<!-- Domain -->
<!-- -->
<complexType
name="domainType">
<complexContent>
<extension
base="iris:resultType">
<sequence>
<element
name="domainName"
type="token" />
<element
name="idn"
type="token"
minOccurs="0"
maxOccurs="1" />
<element name="status"
minOccurs="0"
maxOccurs="1">
<complexType>
<choice minOccurs="0" maxOccurs="unbounded">
<element
name="active"
type="dchk:domainStatusType" />
<element
name="inactive"
type="dchk:domainStatusType" />
<element
name="dispute"
type="dchk:domainStatusType" />
<element
<span class="grey">Newton & Sanz Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
name="renew"
type="dchk:domainStatusType" />
<element
name="addPeriod"
type="dchk:domainStatusType" />
<element
name="renewPeriod"
type="dchk:domainStatusType" />
<element
name="autoRenewPeriod"
type="dchk:domainStatusType" />
<element
name="transferPeriod"
type="dchk:domainStatusType" />
<element
name="redemptionPeriod"
type="dchk:domainStatusType" />
<element
name="restore"
type="dchk:domainStatusType" />
<element
name="policyCompliant"
type="dchk:domainStatusType" />
<element
name="policyNoncompliant"
type="dchk:domainStatusType" />
<element
name="reserved"
type="dchk:domainStatusType" />
<element
name="create"
type="dchk:domainStatusType" />
<element
name="delete"
type="dchk:domainStatusType" />
<element
name="transfer"
type="dchk:domainStatusType" />
<element
name="update"
type="dchk:domainStatusType" />
<element
name="other"
type="dchk:domainStatusType" />
</choice>
</complexType>
</element>
<element
<span class="grey">Newton & Sanz Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
name="registrationReference"
type="iris:entityType"
minOccurs="0"
maxOccurs="1" />
<element
name="createdDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="initialDelegationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="expirationDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="lastDatabaseUpdateDateTime"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
ref="iris:seeAlso"
minOccurs="0"
maxOccurs="unbounded" />
</sequence>
</extension>
</complexContent>
</complexType>
<element
name="domain"
type="dchk:domainType"
substitutionGroup="iris:result" />
<complexType
name="domainStatusType">
<sequence>
<element
name="appliedDate"
type="dateTime"
minOccurs="0"
maxOccurs="1" />
<element
name="ticket"
<span class="grey">Newton & Sanz Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
type="token"
minOccurs="0"
maxOccurs="unbounded" />
<element
name="description"
minOccurs="0"
maxOccurs="unbounded">
<complexType>
<simpleContent>
<extension
base="string">
<attribute
name="language"
type="language"
use="required" />
</extension>
</simpleContent>
</complexType>
</element>
<element
name="subStatus"
minOccurs="0"
maxOccurs="1">
<complexType>
<simpleContent>
<extension
base="token">
<attribute
type="token"
use="required"
name="authority"/>
</extension>
</simpleContent>
</complexType>
</element>
</sequence>
<attribute
name="actor">
<simpleType>
<restriction
base="string">
<enumeration
value="registry"/>
<enumeration
value="registrar"/>
<enumeration
value="registrationServiceProvider"/>
</restriction>
<span class="grey">Newton & Sanz Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
</simpleType>
</attribute>
<attribute
name="disposition">
<simpleType>
<restriction
base="string">
<enumeration
value="prohibited"/>
<enumeration
value="pending"/>
</restriction>
</simpleType>
</attribute>
<attribute
name="scope"
type="token" />
</complexType>
</schema>
Figure 1: dchk.xsd
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Blocks Extensible Exchange Protocol (BEEP) Transport Compliance</span>
All DCHK clients and servers MUST implement the Lightweight UDP
Transport Protocol (IRIS-LWZ) [<a href="#ref-9" title=""A Lightweight UDP Transfer Protocol for the Internet Registry Information Service"">9</a>]. The use of other transports like
the XML Pipelining with Chunks (IRIS-XPC) transport [<a href="#ref-12" title=""XML Pipelining with Chunks for the Internet Registry Information Service"">12</a>] or the BEEP
transport [<a href="#ref-8" title=""Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)"">8</a>] is optional and completely at the discretion of the
server operator. The XPC transport is in any case preferable to the
BEEP transport.
IRIS allows several extensions of the core capabilities. This
section outlines those extensions allowable by IRIS-BEEP [<a href="#ref-8" title=""Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)"">8</a>].
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a>. Message Pattern</span>
This registry type uses the default message pattern as described in
IRIS-BEEP [<a href="#ref-8" title=""Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)"">8</a>].
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a>. Server Authentication</span>
This registry type uses the default server authentication method as
described in IRIS-BEEP [<a href="#ref-8" title=""Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)"">8</a>].
<span class="grey">Newton & Sanz Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. URI Resolution</span>
<span class="h4"><a class="selflink" id="section-3.4.1" href="#section-3.4.1">3.4.1</a>. Application Service Label</span>
The application service label associated with this registry type MUST
be "DCHK1". This is the abbreviated form of the URN for this
registry type, urn:ietf:params:xml:ns:dchk1.
<span class="h4"><a class="selflink" id="section-3.4.2" href="#section-3.4.2">3.4.2</a>. Bottom-Up Resolution</span>
The bottom-up alternative resolution method MUST be identified as
'bottom' in IRIS URI's. Its process is identical to the 'bottom'
process described by <a href="./rfc3982">RFC 3982</a> [<a href="#ref-7" title=""IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)"">7</a>].
<span class="h4"><a class="selflink" id="section-3.4.3" href="#section-3.4.3">3.4.3</a>. Top-Down Resolution</span>
The top-down alternative resolution method MUST be identified as
'top' in IRIS URI's. Its process is identical to the 'top' process
described by <a href="./rfc3982">RFC 3982</a> [<a href="#ref-7" title=""IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)"">7</a>].
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Internationalization Considerations</span>
Implementors should be aware of considerations for
internationalization in IRIS [<a href="#ref-6" title=""IRIS: The Internet Registry Information Service (IRIS) Core Protocol"">6</a>].
Clients needing to localize the data tags in this protocol should
take note that localization is only needed on the names of XML
elements and attributes, with the exception of elements containing
date and time information. The schema for this registry has been
designed so that clients need not interpret the content of elements
or attributes for localization, other than those elements containing
date and time information.
Clients should also make use of the <language> elements provided in
many of the results. Results containing internationalized data can
be accompanied by these elements in order to aid better localization
of the data by the user.
All date and time elements make use of the XML Schema [<a href="#ref-10" title=""XML Schema Part 2: Datatypes"">10</a>] data type
"dateTime". If their contents are Coordinated Universal Time (UTC)
timestamps, they MUST be specified by using the capitalized 'Z'
indicator (instead of 'z').
<span class="grey">Newton & Sanz Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. XML Namespace Registration</span>
This document makes use of the XML registry specified in <a href="./rfc3688">RFC 3688</a>
[<a href="#ref-4" title=""The IETF XML Registry"">4</a>]. Accordingly, IANA has made the following registration:
o XML Namespace URN/URI:
* urn:ietf:params:xml:ns:dchk1
o Contact:
* Andrew Newton <andy@hxr.us>
* Marcos Sanz <sanz@denic.de>
o XML:
* None.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. XML Schema Registration</span>
This document makes use of the XML registry specified in <a href="./rfc3688">RFC 3688</a>
[<a href="#ref-4" title=""The IETF XML Registry"">4</a>]. Accordingly, IANA has made the following registration:
o XML Schema URN/URI:
* urn:ietf:params:xml:schema:dchk1
o Contact:
* Andrew Newton <andy@hxr.us>
* Marcos Sanz <sanz@denic.de>
o XML:
* The XML Schema specified in <a href="#section-3.2">Section 3.2</a>
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. S-NAPTR Registration</span>
The following Sraightforwarad-NAPTR (S-NAPTR) application service
label has been registered with IANA according to the IANA
considerations defined in IRIS [<a href="#ref-6" title=""IRIS: The Internet Registry Information Service (IRIS) Core Protocol"">6</a>]:
DCHK1
<span class="grey">Newton & Sanz Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
<span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a>. BEEP Registration</span>
The following BEEP Profile URI has been registered with IANA, in
addition to the registration provided in IRIS-BEEP [<a href="#ref-8" title=""Using the Internet Registry Information Service (IRIS) over the Blocks Extensible Exchange Protocol (BEEP)"">8</a>].
<a href="http://iana.org/beep/iris1/dchk1">http://iana.org/beep/iris1/dchk1</a>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
Being a proper subset of <a href="./rfc3982">RFC 3982</a> [<a href="#ref-7" title=""IRIS: A Domain Registry (dreg) Type for the Internet Registry Information Service (IRIS)"">7</a>], the registry described in this
document introduces no security considerations beyond those
documented in <a href="./rfc3981">RFC 3981</a> [<a href="#ref-6" title=""IRIS: The Internet Registry Information Service (IRIS) Core Protocol"">6</a>].
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
[<a id="ref-1">1</a>] Mockapetris, P., "Domain names - implementation and
specification", STD 13, <a href="./rfc1035">RFC 1035</a>, November 1987.
[<a id="ref-2">2</a>] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-3">3</a>] Hoffman, P. and M. Blanchet, "Nameprep: A Stringprep Profile
for Internationalized Domain Names (IDN)", <a href="./rfc3491">RFC 3491</a>,
March 2003.
[<a id="ref-4">4</a>] Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
January 2004.
[<a id="ref-5">5</a>] Hollenbeck, S., "Domain Registry Grace Period Mapping for the
Extensible Provisioning Protocol (EPP)", <a href="./rfc3915">RFC 3915</a>,
September 2004.
[<a id="ref-6">6</a>] Newton, A. and M. Sanz, "IRIS: The Internet Registry
Information Service (IRIS) Core Protocol", <a href="./rfc3981">RFC 3981</a>,
January 2005.
[<a id="ref-7">7</a>] Newton, A. and M. Sanz, "IRIS: A Domain Registry (dreg) Type
for the Internet Registry Information Service (IRIS)",
<a href="./rfc3982">RFC 3982</a>, January 2005.
[<a id="ref-8">8</a>] Newton, A. and M. Sanz, "Using the Internet Registry
Information Service (IRIS) over the Blocks Extensible Exchange
Protocol (BEEP)", <a href="./rfc3983">RFC 3983</a>, January 2005.
[<a id="ref-9">9</a>] Newton, A., "A Lightweight UDP Transfer Protocol for the
Internet Registry Information Service", <a href="./rfc4993">RFC 4993</a>, August 2007.
<span class="grey">Newton & Sanz Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
[<a id="ref-10">10</a>] World Wide Web Consortium, "XML Schema Part 2: Datatypes",
W3C XML Schema, October 2004,
<<a href="http://www.w3.org/TR/xmlschema-2/">http://www.w3.org/TR/xmlschema-2/</a>>.
[<a id="ref-11">11</a>] World Wide Web Consortium, "XML Schema Part 1: Structures",
W3C XML Schema, October 2004,
<<a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>>.
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
[<a id="ref-12">12</a>] Newton, A., "XML Pipelining with Chunks for the Internet
Registry Information Service", <a href="./rfc4992">RFC 4992</a>, August 2007.
Authors' Addresses
Andrew L. Newton
American Registry for Internet Numbers
3635 Concorde Parkway, Suite 200
Chantilly, VA 20151
USA
Phone: +1 703 227 9884
EMail: andy@arin.net
URI: <a href="http://www.arin.net/">http://www.arin.net/</a>
Marcos Sanz
DENIC eG
Kaiserstrasse 75-77
D-60329 Frankfurt
Germany
EMail: sanz@denic.de
URI: <a href="http://www.denic.de/">http://www.denic.de/</a>
<span class="grey">Newton & Sanz Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc5144">RFC 5144</a> IRIS-DCHK February 2008</span>
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Newton & Sanz Standards Track [Page 17]
</pre>
|
