idnits 2.17.1 draft-icann-registrar-interfaces-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (Mar 20, 2022) is 761 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-21) exists of draft-lozano-icann-registry-interfaces-15 -- Obsolete informational reference (is this intentional?): RFC 7525 (Obsoleted by RFC 9325) Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Lozano 3 Internet-Draft E. Alvarez 4 Intended status: Informational ICANN 5 Expires: September 21, 2022 Mar 20, 2022 7 ICANN Registrar Interfaces 8 draft-icann-registrar-interfaces-08 10 Abstract 12 This document describes the interfaces provided by ICANN to 13 Registrars and Data Escrow Agents to fulfill the data escrow 14 requirements of the Registrar Accreditation Agreement and the 15 Registrar Data Escrow Specifications. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on September 21, 2022. 34 Copyright Notice 36 Copyright (c) 2022 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (https://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 53 1.2. Date and Time . . . . . . . . . . . . . . . . . . . . . . 3 54 1.3. Common elements used in this specification . . . . . . . 3 55 2. Interfaces for Registrar Data Escrow Notifications . . . . . 3 56 2.1. Registrar Reporting . . . . . . . . . . . . . . . . . . . 4 57 2.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 6 58 3. Technical details of the interfaces . . . . . . . . . . . . . 12 59 3.1. Registrar Reporting . . . . . . . . . . . . . . . . . . . 13 60 3.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 14 61 4. Monitoring Registrar reporting . . . . . . . . . . . . . . . 16 62 4.1. Monitoring the reporting status of a Registrar . . . . . 16 63 4.2. Monitoring Registrar Data Escrow Reports . . . . . . . . 18 64 4.3. Monitoring Registrar Data Escrow Agent Notifications . . 20 65 5. Internationalization Considerations . . . . . . . . . . . . . 22 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 22 67 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 22 68 7.1. Implementation in the gTLD space . . . . . . . . . . . . 23 69 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 70 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 23 71 9.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 24 72 9.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 24 73 9.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 24 74 9.4. Version 03 . . . . . . . . . . . . . . . . . . . . . . . 24 75 9.5. Version 04 . . . . . . . . . . . . . . . . . . . . . . . 24 76 9.6. Version 05 . . . . . . . . . . . . . . . . . . . . . . . 24 77 9.7. Version 06 . . . . . . . . . . . . . . . . . . . . . . . 24 78 9.8. Version 07 . . . . . . . . . . . . . . . . . . . . . . . 24 79 9.9. Version 08 . . . . . . . . . . . . . . . . . . . . . . . 25 80 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 25 81 10.1. Normative References . . . . . . . . . . . . . . . . . . 25 82 10.2. Informative References . . . . . . . . . . . . . . . . . 26 83 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26 85 1. Introduction 87 This document describes the technical details of the interfaces 88 provided by the Internet Corporation for Assigned Names and Numbers 89 (ICANN) to Registrars and Data Escrow Agents to fulfill the data 90 escrow requirements of the Registrar Accreditation Agreement 91 [ICANN-RAA-2013] and the Registrar Data Escrow Specifications 92 [ICANN-RDE-SPEC]. 94 Extensible Markup Language (XML) 1.0 as described in 95 [W3C.REC-xml-20081126] is used in this specification. 97 The provisioning of credentials and authentication methods used in 98 the interfaces is outside of this document's scope. 100 1.1. Terminology 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 104 "OPTIONAL" in this document are to be interpreted as described in BCP 105 14 [RFC2119] [RFC8174] when, and only when, they appear in all 106 capitals, as shown here. 108 XML is case sensitive. Unless stated otherwise, XML specifications 109 and examples provided in this document MUST be interpreted in the 110 character case presented to develop a conforming implementation. 112 1.2. Date and Time 114 Numerous fields indicate "date and time", such as the creation and 115 receipt dates for data escrow deposits. These fields SHALL contain 116 timestamps indicating the date and time in UTC as specified in 117 [RFC3339], with no offset from the zero meridian. 119 1.3. Common elements used in this specification 121 Common elements used in this specification are explained in this 122 section. 124 o : The base URL used in the reporting interfaces examples 125 must be replaced with the URL indicated by ICANN. 127 o This document uses the term of "Differential" deposit as defined 128 in the Registry Data Escrow Specification (see, [RFC8909]), while 129 the Registrar Data Escrow Specifications [ICANN-RDE-SPEC] refers 130 to the same concept as "Incremental" deposit. 132 o A-label and NR-LDH, as defined in [RFC5890]. 134 2. Interfaces for Registrar Data Escrow Notifications 136 This section describes the interfaces provided by ICANN to the 137 Registrars and Data Escrow Agents to fulfill their reporting 138 requirements related to Registrar Data Escrow Specifications 139 [ICANN-RDE-SPEC]. 141 2.1. Registrar Reporting 143 To notify that a data escrow deposit has been submitted to a Data 144 Escrow Agent, the ICANN-accredited Registrar sends a 145 object (see, 146 [I-D.lozano-icann-registry-interfaces]) to ICANN. 148 The following considerations apply for a object 149 corresponding to a data escrow deposit for a Registrar repository: 151 o The element in the object 152 (see, [RFC9022]) MUST be present and have a value corresponding to 153 the IANA Registrar ID assigned by ICANN. 155 o A element MUST be included with the 156 corresponding "rcdn" attribute in the object to 157 indicate the total domains in the Registrar repository for each 158 Registry Class Domain Name (e.g., example) with at least one 159 domain name allocation at a specific point in time (watermark), 160 regardless of the type of deposit: full or differential. 162 * If the "https://www.icann.org/en/system/files/files/rde-specs- 163 09nov07-en.pdf" specification is being used as the 164 , then the "uri" attribute in the 165 elements for domain names MUST have a value 166 of "urn:ietf:params:xml:ns:rdeDomain-1.0". 168 o To indicate that a Registrar repository has no domain names, one 169 element MUST be included with the "uri" 170 attribute value of "urn:ietf:params:xml:ns:rdeDomain-1.0", no 171 "rcdn" attribute, and a value of 0 (zero). 173 The object for each deposit successfully sent to 174 the Data Escrow Agent is sent using the PUT HTTP verb in the 175 interface provided by ICANN at: 177 /report/registrar-escrow-report// 179 Where: 181 * MUST be substituted with the IANA Registrar ID 182 assigned by ICANN for which the report is being provided. 184 * MUST be substituted with the identifier assigned to the 185 report, which MUST be the same as the "id" attribute from the 186 . 188 Note: The interface supports overwriting the information of a 189 particular report to support asynchronous interfaces between 190 Registrars and Data Escrow Agents. 192 Example of a object for a data escrow deposit 193 corresponding to a Registrar repository: 195 196 199 20170801001 200 1 201 202 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 203 204 0 205 2017-08-01T00:15:00.0Z 206 FULL 207 2017-08-01T00:00:00Z 208 209 9999 210 2 212 8 214 3 216 217 219 Example of a object for an empty data escrow 220 deposit corresponding to a Registrar repository: 222 223 226 20170801001 227 1 228 229 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 230 231 0 232 2017-08-01T00:15:00.0Z 233 FULL 234 2017-08-01T00:00:00Z 235 236 9999 237 238 0 239 240 242 2.2. Data Escrow Agent Reporting 244 The Registrar Data Escrow Specification requires that Registrar Data 245 Escrow Agents deliver to ICANN a notification every time a 246 successfully processed deposit is received from the Registrar 247 regardless of the final status of the verification process, in 248 addition to a failure notification if a scheduled deposit is not 249 received from a Registrar. 251 In order to satisfy this requirement, the Data Escrow Agent sends to 252 ICANN a object as defined in Section 2 253 of [I-D.lozano-icann-registry-interfaces], to ICANN using the POST 254 HTTP verb in the interface provided by ICANN at: 256 /report/registrar-escrow-agent-notification/ 258 Where: 260 * MUST be substituted with the IANA Registrar ID 261 assigned by ICANN for which the notification is being provided. 263 A with DRFN (Deposit Receipt Failure 264 Notice) status is used to notify that a data escrow deposit has not 265 been processed for verification for a past date where a deposit was 266 scheduled to be received from the Registrar. 268 In addition to the considerations listed in Section 2.1 for the 269 object of the notification, if the data escrow 270 deposit does not include an , a unique value MUST be generated by 271 the Data Escrow Agent to reference the deposit and it MUST be 272 provided in the element. 274 In the case of a with DVFN (Deposit 275 Verification Failure Notice) status, the 276 element MUST be present and include a object for each 277 deposit verification error condition and specify in the corresponding 278 "domainCount" attribute the number of domain names with such error 279 conditions. 281 Note: an error condition may be present several times in the same 282 domain escrow record (e.g., the administrative, technical and billing 283 contact contains invalid email syntax). In this case only one domain 284 name is affected by the error condition, therefore the "domainCount" 285 attribute value must be increased by one in the corresponding 286 object. 288 The following table defines the result codes and messages that a Data 289 Escrow Agent could use to report verification issues found in a 290 Registrar data escrow deposit. When using result codes 2102, 2103, 291 2104, 2105, 2106, 2107, 2108, 2109, or 2110, the "domainCount" 292 attribute MUST be present. 294 +-----------+-------------------------------------------------------+ 295 | Result | Message | 296 | Code | | 297 +-----------+-------------------------------------------------------+ 298 | 2001 | No corresponding hash file found for deposit file. | 299 | 2002 | Hash does not match the corresponding deposit file. | 300 | 2003 | Invalid hash file format. | 301 | 2004 | Data escrow deposit PGP signature verification error. | 302 | 2005 | Archive includes unrecognized files. | 303 | 2006 | Invalid encoding for data escrow deposit file. | 304 | 2007 | Data escrow deposit file size exceeds the maximum | 305 | | allowed size. | 306 | 2008 | Data escrow deposit file exceeds the maximum allowed | 307 | | number of lines. | 308 | 2101 | Unrecognized data escrow deposit file CSV header. | 309 | 2102 | Escrow Record structure does not conform with CSV | 310 | | header definition. | 311 | 2103 | Escrow Record found missing data in required | 312 | | field(s). | 313 | 2104 | Invalid domain name syntax in Escrow Record. | 314 | 2105 | Invalid email syntax in Escrow Record. | 315 | 2106 | Invalid hostname syntax in Escrow Record. | 316 | 2107 | Invalid date syntax in Escrow Record. | 317 | 2108 | Invalid phone syntax in Escrow Record. | 318 | 2109 | Duplicate domain or handle Escrow Record found in | 319 | | deposit. | 320 | 2110 | Handle reference by Escrow Record not found. | 321 | 2201 | "Full" data escrow deposit expected but received | 322 | | "Differential" instead. | 323 | 2202 | Data Escrow deposit date is in the future. | 324 | 2203 | A data escrow deposit has been already successfully | 325 | | verified for that date. | 326 +-----------+-------------------------------------------------------+ 328 Registrar Data Escrow Deposit Verification Result Codes 330 Example of a object of a Data Escrow 331 Agent notification corresponding to a Registrar Data Escrow deposit 332 that was not received or could not be processed for verification: 334 335 337 Escrow Agent Inc. 338 1 339 2017-06-17 340 DRFN 341 2017-06-10 342 343 345 Example of a object of a Data Escrow 346 Agent notification corresponding to a Registrar repository Data 347 Escrow deposit that has passed the verification process: 349 350 354 Escrow Agent Inc. 355 1 356 357 2017-06-17 358 DVPN 359 360 2017-06-17T03:15:00.0Z 361 362 2017-06-17T05:15:00.0Z 363 364 2017-06-17 365 366 20170617001 367 1 368 369 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 370 371 0 372 2017-06-17T00:15:00.0Z 373 FULL 374 2017-06-17T00:00:00Z 375 376 9999 377 2 379 6 381 1 383 384 385 387 Example of a object of a Data Escrow 388 Agent notification corresponding to a Registrar repository Data 389 Escrow deposit that has failed the verification process: 391 392 397 Escrow Agent Inc. 398 1 399 2017-06-17 400 DVFN 401 402 403 404 Invalid domain name syntax in Escrow Record. 405 406 407 408 409 Handle reference by Escrow Record not found. 410 411 412 413 414 2017-06-17T03:15:00.0Z 415 416 417 2017-06-17T05:15:00.0Z 418 419 420 2017-06-14 421 422 423 20170617001 424 1 425 426 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 427 428 0 429 2017-06-17T00:15:00.0Z 430 FULL 431 2017-06-17T00:00:00Z 432 433 9999 434 2 436 8 438 3 440 441 442 444 3. Technical details of the interfaces 446 Content-type value in the HTTP header: 448 o The client MUST set "text/xml" in the HTTP header Content-type 449 when using the Data Escrow Agent Reporting and Registrar Reporting 450 interfaces described in Section 2. 452 After successfully receiving and processing an input, the interfaces 453 return any of the HTTP status codes described in Section 4 of 454 [I-D.lozano-icann-registry-interfaces]. 456 The following sections provide the IIRDEA Result Codes that can be 457 expected in the object from each interface: 459 3.1. Registrar Reporting 461 The following table lists the result codes of the interface: 463 +---------+---------------------------------------------------------+ 464 | Result | Message | 465 | Code | | 466 +---------+---------------------------------------------------------+ 467 | 1000 | No ERRORs were found and the report has been accepted | 468 | | by ICANN. | 469 | 2001 | The request did not validate against the schema. | 470 | 2004 | Report for a date in the future. The and | 471 | | date should not be in the future. | 472 | 2005 | Version is not supported. | 473 | 2006 | The in the element and the in the | 474 | | URL path do not match. | 475 | 2301 | Interface is disabled for this Registrar. | 476 | 2302 | The and date should not be before | 477 | | the creation date of the Registrar in the system. | 478 | 2303 | The in the
and the in | 479 | | the URL path do not match. | 480 | 2304 | Report regarding an differential deposit received when | 481 | | a full deposit was expected (). | 482 | 2305 | attribute missing in count element provided in | 483 | | the
. | 484 | 2306 | Multiple count elements with the same and | 485 | | attribute values provided in the
. | 486 | 2307 | Missing required element in the
. | 487 | 2312 | An invalid NR-LDH label or A-label was found or the | 488 | | domain name syntax is invalid in the attribute. | 489 | 2313 | INCR is not supported. | 490 +---------+---------------------------------------------------------+ 492 Registrar Data Escrow Reporting Result Codes 494 3.2. Data Escrow Agent Reporting 496 The following table lists the result codes of the interface: 498 +--------+----------------------------------------------------------+ 499 | Result | Message | 500 | Code | | 501 +--------+----------------------------------------------------------+ 502 | 1000 | No ERRORs were found and the notification has been | 503 | | accepted by ICANN. | 504 | 2001 | The request did not validate against the schema. | 505 | 2002 | A DVPN notification exists for that date (). | 506 | 2004 | Notification for a date in the future. The , | 507 | | , and date should | 508 | | not be in the future. | 509 | 2005 | Version is not supported. | 510 | 2201 | The and in the notification do not | 511 | | match. | 512 | 2203 | A Deposit Verification Pass Notice (DVPN) notification | 513 | | was received, but the Domain Name count is missing in | 514 | | the
. | 515 | 2204 | The notification for the report "id" already exists. | 516 | 2207 | A DVPN or DVFN was received, but the element is | 517 | | missing in the notification. | 518 | 2208 | A DRFN was received, but a element exists in | 519 | | the notification. | 520 | 2209 | and elements must not be present in a | 521 | | DRFN. | 522 | 2301 | Interface is disabled for this Registrar. | 523 | 2302 | The and and date should | 524 | | not be before the creation date of the Registrar in the | 525 | | system. | 526 | 2303 | The in the
and the in | 527 | | the URL path do not match. | 528 | 2304 | Notification regarding an differential deposit received | 529 | | when a full deposit was expected (). | 530 | 2305 | attribute missing in count element provided in | 531 | | the
. | 532 | 2306 | Multiple count elements with the same and | 533 | | attribute values provided in the
. | 534 | 2307 | Missing required element in the
. | 535 | 2309 | A DVFN was received, but the element is | 536 | | missing in the notification. | 537 | 2310 | The specified result code in the element | 538 | | requires the "domainCount" attribute to be present. | 539 | 2311 | Unrecognized value in the "code" attribute of the | 540 | | element. | 541 | 2312 | An invalid NR-LDH label or A-label was found or the | 542 | | domain name syntax is invalid in the attribute. | 543 | 2313 | INCR is not supported. | 544 +--------+----------------------------------------------------------+ 546 Data Escrow Agent Reporting Result Codes 548 4. Monitoring Registrar reporting 550 Registrars MAY monitor the status of the data escrow reporting 551 notifications requirement using the following interfaces that support 552 the GET HTTP verb. 554 4.1. Monitoring the reporting status of a Registrar 556 Registrars MAY monitor the general reporting status and obtain a list 557 of any outstanding issues using the following interface: 559 /info/status/registrar/ 561 Where: 563 * MUST be substituted with the IANA ID assigned by 564 ICANN to the Registrar being queried. 566 This interface provides a element as defined 567 in Section 2 of [I-D.lozano-icann-registry-interfaces] that uses the 568 element and includes the following 569 values: 571 o "Registrar_Escrow_Report" : For Registrar Data Escrow Reporting as 572 defined in Section 2.1. The "date" attribute for any reporting 573 issue is provided in "YYYY-MM-DD" format. 575 o "DEA_Notification" : For Data Escrow Agent Notifications as 576 defined in Section 2.2. The "date" attribute for any reporting 577 issue is provided in "YYYY-MM-DD" format. 579 Example of response for a Registrar status check with no reporting 580 issues: 582 HTTP/1.1 200 OK 583 Content-Type: application/xml 584 Content-Length: 1125 586 587 590 9999 591 592 2017-06-10T12:00:30.101Z 593 Daily 594 2017-10-15 595 596 597 Registrar_Escrow_Report 598 false 599 ok 600 601 602 DEA_Notification 603 true 604 ok 605 606 607 608 2017-10-20T02:22:14.148Z 609 611 Example of response for a Registrar status check with reporting 612 issues: 614 HTTP/1.1 200 OK 615 Content-Type: application/xml 616 Content-Length: 1604 618 619 622 9999 623 624 2017-06-10T12:00:30.101Z 625 Daily 626 2017-10-08 627 628 629 Registrar_Escrow_Report 630 true 631 ok 632 633 634 DEA_Notification 635 true 636 unsatisfactory 637 638 640 642 644 646 647 648 649 650 2017-10-20T02:22:14.148Z 651 653 4.2. Monitoring Registrar Data Escrow Reports 655 Registrars MAY monitor the status of their Data Escrow reports using 656 the following interface: 658 /info/report/registrar-escrow-report// 660 Where: 662 * MUST be substituted with the IANA ID assigned by 663 ICANN to the Registrar being queried. 665 * MUST be substituted with the date being queried in 666 "YYYY-MM-DD" format. For example: 2017-08-01. 668 Possible results are: 670 o The interface provides a HTTP/200 status code with a 671 element in the response content as defined in 672 Section 2 of [I-D.lozano-icann-registry-interfaces], listing each 673 successfully received with watermark value that 674 matches the queried date. 676 Example of response for a Registrar Data Escrow Reporting status 677 check: 679 HTTP/1.1 200 OK 680 Content-Type: application/xml 681 Content-Length: 1194 683 684 688 689 2017-10-13T00:30:13.741Z 690 691 20171013001 692 1 693 694 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 695 696 0 697 2017-10-13T00:01:11.000Z 698 FULL 699 2017-10-13T00:00:00.00Z 700 701 9999 702 10 704 1 706 707 708 709 711 4.3. Monitoring Registrar Data Escrow Agent Notifications 713 Registrars and Data Escrow Agents MAY monitor the status of Data 714 Escrow Agent Notifications using the following interface: 716 /info/report/registrar-escrow-agent-notification// 719 Where: 721 * MUST be substituted with the IANA ID assigned by 722 ICANN to the Registrar being queried. 724 * MUST be substituted with the date being queried in 725 "YYYY-MM-DD" format. For example: 2017-08-01. 727 Possible results are: 729 o The interface provides a HTTP/200 status code with a 730 element in the response content 731 as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], 732 listing each successfully received 733 with a watermark value that matches the queried date. 735 Example of a response of a Registrar Data Escrow Agent Notification 736 status check for a date with two received notifications: 738 HTTP/1.1 200 OK 739 Content-Type: application/xml 740 Content-Length: 2578 742 743 749 750 751 2017-10-17T23:59:59.0Z 752 753 754 Escrow Agent Inc. 755 1 756 2017-10-17 757 DRFN 758 759 2017-10-14 760 761 762 763 764 2017-10-18T06:00:00.0Z 765 766 767 Escrow Agent Inc. 768 1 769 2017-10-17 770 DVPN 771 772 2017-10-18T03:15:00.0Z 773 774 2017-10-18T05:15:00.0Z 776 777 2017-10-17 778 779 20171017001 780 1 781 782 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 783 784 0 785 2017-10-17T00:15:00.0Z 786 FULL 787 2017-10-17T00:00:00Z 788 789 9999 790 10 792 1 794 795 796 797 798 800 5. Internationalization Considerations 802 The interfaces described in this document use XML, which provides 803 native support for encoding information using the Unicode character 804 set and its more compact representations including UTF-8. Conformant 805 XML processors recognize both UTF-8 and UTF-16. Though XML includes 806 provisions to identify and use other character encodings through use 807 of an "encoding" attribute in an declaration, use of UTF-8 is 808 RECOMMENDED. 810 6. IANA Considerations 812 No actions are required from IANA. 814 7. Implementation Status 816 Note to RFC Editor: Please remove this section and the reference to 817 RFC 7942 [RFC7942] before publication. 819 This section records the status of known implementations of the 820 protocol defined by this specification at the time of posting of this 821 Internet-Draft, and is based on a proposal described in RFC 7942 822 [RFC7942]. The description of implementations in this section is 823 intended to assist the IETF in its decision processes in progressing 824 drafts to RFCs. Please note that the listing of any individual 825 implementation here does not imply endorsement by the IETF. 826 Furthermore, no effort has been spent to verify the information 827 presented here that was supplied by IETF contributors. This is not 828 intended as, and must not be construed to be, a catalog of available 829 implementations or their features. Readers are advised to note that 830 other implementations may exist. 832 According to RFC 7942 [RFC7942], "this will allow reviewers and 833 working groups to assign due consideration to documents that have the 834 benefit of running code, which may serve as evidence of valuable 835 experimentation and feedback that have made the implemented protocols 836 more mature. It is up to the individual working groups to use this 837 information as they see fit". 839 7.1. Implementation in the gTLD space 841 Organization: ICANN 843 Name: Registrar Data Escrow Specifications 845 Description: Data Escrow Agents, and ICANN implement this 846 specification. ICANN receives daily notifications from Data Escrow 847 Agents using this specification. 849 Level of maturity: production. 851 Coverage: all aspects of this specification are implemented. 853 Version compatibility: versions 00 - 04 are known to be implemented. 855 Contact: gustavo.lozano@icann.org 857 URL: https://www.icann.org/en/system/files/files/rde-specs- 858 09nov07-en.pdf 860 8. Security Considerations 862 The interfaces described in this document MUST be provided using 863 HTTPS. The recommendations in [RFC7525] MUST be implemented. 865 9. Change History 867 [[RFC Editor: Please remove this section.]] 869 9.1. Version 00 871 Initial version. 873 9.2. Version 01 875 o Added clarifications, list of result codes that require the 876 "domainCount" attribute to be present, and additional examples of 877 objects in Section 2.2. 879 o Removed HTTP/404 from the possible results of interfaces to 880 monitor data escrow notifications and registrar reports. 882 9.3. Version 02 884 1. Ping update. 886 9.4. Version 03 888 1. Ping update. 890 9.5. Version 04 892 1. Ping update. 894 9.6. Version 05 896 1. IANA Considerations section added. 898 2. Implementation section added. 900 3. Internationalization Considerations status section added. 902 4. Security section added. 904 5. Editorial updates. 906 9.7. Version 06 908 1. Ping update. 910 9.8. Version 07 912 1. Citations for RFCs that were recently published. 914 9.9. Version 08 916 1. Ping update. 918 10. References 920 10.1. Normative References 922 [I-D.lozano-icann-registry-interfaces] 923 Ibarra, G. and E. Alvarez, "ICANN Registry Interfaces", 924 draft-lozano-icann-registry-interfaces-15 (work in 925 progress), July 2021. 927 [ICANN-RDE-SPEC] 928 ICANN, "Registrar Data Escrow specifications", Nov 2007, 929 . 932 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 933 Requirement Levels", BCP 14, RFC 2119, 934 DOI 10.17487/RFC2119, March 1997, 935 . 937 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 938 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 939 . 941 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 942 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 943 May 2017, . 945 [RFC8909] Lozano, G., "Registry Data Escrow Specification", 946 RFC 8909, DOI 10.17487/RFC8909, November 2020, 947 . 949 [RFC9022] Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name 950 Registration Data (DNRD) Objects Mapping", RFC 9022, 951 DOI 10.17487/RFC9022, May 2021, 952 . 954 [W3C.REC-xml-20081126] 955 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 956 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 957 Edition) REC-xml-20081126", November 2008, 958 . 960 10.2. Informative References 962 [ICANN-RAA-2013] 963 ICANN, "2013 Registrar Accreditation Agreement", Jun 2013, 964 . 967 [RFC5890] Klensin, J., "Internationalized Domain Names for 968 Applications (IDNA): Definitions and Document Framework", 969 RFC 5890, DOI 10.17487/RFC5890, August 2010, 970 . 972 [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, 973 "Recommendations for Secure Use of Transport Layer 974 Security (TLS) and Datagram Transport Layer Security 975 (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 976 2015, . 978 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 979 Code: The Implementation Status Section", BCP 205, 980 RFC 7942, DOI 10.17487/RFC7942, July 2016, 981 . 983 Authors' Addresses 985 Gustavo Lozano 986 ICANN 987 12025 Waterfront Drive, Suite 300 988 Los Angeles 90292 989 US 991 Phone: +1.3103015800 992 Email: gustavo.lozano@icann.org 994 Eduardo Alvarez 995 ICANN 996 12025 Waterfront Drive, Suite 300 997 Los Angeles 90292 998 US 1000 Phone: +1.3103015800 1001 Email: eduardo.alvarez@icann.org