idnits 2.17.1 draft-icann-registrar-interfaces-05.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 (June 24, 2020) is 1402 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-11) exists of draft-ietf-regext-dnrd-objects-mapping-08 == Outdated reference: A later version (-21) exists of draft-lozano-icann-registry-interfaces-13 -- Obsolete informational reference (is this intentional?): RFC 7525 (Obsoleted by RFC 9325) Summary: 0 errors (**), 0 flaws (~~), 3 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: December 26, 2020 June 24, 2020 7 ICANN Registrar Interfaces 8 draft-icann-registrar-interfaces-05 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 December 26, 2020. 34 Copyright Notice 36 Copyright (c) 2020 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 . . . . . . . . . . . . . . . . . . . 3 57 2.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 6 58 3. Technical details of the interfaces . . . . . . . . . . . . . 11 59 3.1. Registrar Reporting . . . . . . . . . . . . . . . . . . . 12 60 3.2. Data Escrow Agent Reporting . . . . . . . . . . . . . . . 13 61 4. Monitoring Registrar reporting . . . . . . . . . . . . . . . 15 62 4.1. Monitoring the reporting status of a Registrar . . . . . 15 63 4.2. Monitoring Registrar Data Escrow Reports . . . . . . . . 17 64 4.3. Monitoring Registrar Data Escrow Agent Notifications . . 19 65 5. Internationalization Considerations . . . . . . . . . . . . . 21 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 67 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 21 68 7.1. Implementation in the gTLD space . . . . . . . . . . . . 22 69 8. Security Considerations . . . . . . . . . . . . . . . . . . . 22 70 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 22 71 9.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 23 72 9.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 23 73 9.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 23 74 9.4. Version 03 . . . . . . . . . . . . . . . . . . . . . . . 23 75 9.5. Version 04 . . . . . . . . . . . . . . . . . . . . . . . 23 76 9.6. Version 05 . . . . . . . . . . . . . . . . . . . . . . . 23 77 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 23 78 10.1. Normative References . . . . . . . . . . . . . . . . . . 23 79 10.2. Informative References . . . . . . . . . . . . . . . . . 24 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 82 1. Introduction 84 This document describes the technical details of the interfaces 85 provided by the Internet Corporation for Assigned Names and Numbers 86 (ICANN) to Registrars and Data Escrow Agents to fulfill the data 87 escrow requirements of the Registrar Accreditation Agreement 88 [ICANN-RAA-2013] and the Registrar Data Escrow Specifications 89 [ICANN-RDE-SPEC]. 91 Extensible Markup Language (XML) 1.0 as described in 92 [W3C.REC-xml-20081126] is used in this specification. 94 The provisioning of credentials and authentication methods used in 95 the interfaces is outside of this document's scope. 97 1.1. Terminology 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 101 "OPTIONAL" in this document are to be interpreted as described in BCP 102 14 [RFC2119] [RFC8174] when, and only when, they appear in all 103 capitals, as shown here. 105 XML is case sensitive. Unless stated otherwise, XML specifications 106 and examples provided in this document MUST be interpreted in the 107 character case presented to develop a conforming implementation. 109 1.2. Date and Time 111 Numerous fields indicate "date and time", such as the creation and 112 receipt dates for data escrow deposits. These fields SHALL contain 113 timestamps indicating the date and time in UTC as specified in 114 [RFC3339], with no offset from the zero meridian. 116 1.3. Common elements used in this specification 118 Common elements used in this specification are explained in this 119 section. 121 o : The base URL used in the reporting interfaces examples 122 must be replaced with the URL indicated by ICANN. 124 o This document uses the term of "Differential" deposit as defined 125 in the Registry Data Escrow Specification (see, 126 [I-D.ietf-regext-data-escrow]), while the Registrar Data Escrow 127 Specifications [ICANN-RDE-SPEC] refers to the same concept as 128 "Incremental" deposit. 130 o A-label and NR-LDH, as defined in [RFC5890]. 132 2. Interfaces for Registrar Data Escrow Notifications 134 This section describes the interfaces provided by ICANN to the 135 Registrars and Data Escrow Agents to fulfill their reporting 136 requirements related to Registrar Data Escrow Specifications 137 [ICANN-RDE-SPEC]. 139 2.1. Registrar Reporting 141 To notify that a data escrow deposit has been submitted to a Data 142 Escrow Agent, the ICANN-accredited Registrar sends a 143 object (see, 144 [I-D.lozano-icann-registry-interfaces]) to ICANN. 146 The following considerations apply for a object 147 corresponding to a data escrow deposit for a Registrar repository: 149 o The element in the object 150 (see, [I-D.ietf-regext-dnrd-objects-mapping]) MUST be present and 151 have a value corresponding to the IANA Registrar ID assigned by 152 ICANN. 154 o A element MUST be included with the 155 corresponding "rcdn" attribute in the object to 156 indicate the total domains in the Registrar repository for each 157 Registry Class Domain Name (e.g., example) with at least one 158 domain name allocation at a specific point in time (watermark), 159 regardless of the type of deposit: full or differential. 161 * If the "https://www.icann.org/en/system/files/files/rde-specs- 162 09nov07-en.pdf" specification is being used as the 163 , then the "uri" attribute in the 164 elements for domain names MUST have a value 165 of "urn:ietf:params:xml:ns:rdeDomain-1.0". 167 o To indicate that a Registrar repository has no domain names, one 168 element MUST be included with the "uri" 169 attribute value of "urn:ietf:params:xml:ns:rdeDomain-1.0", no 170 "rcdn" attribute, and a value of 0 (zero). 172 The object for each deposit successfully sent to 173 the Data Escrow Agent is sent using the PUT HTTP verb in the 174 interface provided by ICANN at: 176 /report/registrar-escrow-report// 178 Where: 180 * MUST be substituted with the IANA Registrar ID 181 assigned by ICANN for which the report is being provided. 183 * MUST be substituted with the identifier assigned to the 184 report, which MUST be the same as the "id" attribute from the 185 . 187 Note: The interface supports overwriting the information of a 188 particular report to support asynchronous interfaces between 189 Registrars and Data Escrow Agents. 191 Example of a object for a data escrow deposit 192 corresponding to a Registrar repository: 194 195 198 20170801001 199 1 200 201 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 202 203 0 204 2017-08-01T00:15:00.0Z 205 FULL 206 2017-08-01T00:00:00Z 207 208 9999 209 2 211 8 213 3 215 216 218 Example of a object for an empty data escrow 219 deposit corresponding to a Registrar repository: 221 222 225 20170801001 226 1 227 228 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 229 230 0 231 2017-08-01T00:15:00.0Z 232 FULL 233 2017-08-01T00:00:00Z 234 235 9999 236 237 0 238 239 241 2.2. Data Escrow Agent Reporting 243 The Registrar Data Escrow Specification requires that Registrar Data 244 Escrow Agents deliver to ICANN a notification every time a 245 successfully processed deposit is received from the Registrar 246 regardless of the final status of the verification process, in 247 addition to a failure notification if a scheduled deposit is not 248 received from a Registrar. 250 In order to satisfy this requirement, the Data Escrow Agent sends to 251 ICANN a object as defined in Section 2 252 of [I-D.lozano-icann-registry-interfaces], to ICANN using the POST 253 HTTP verb in the interface provided by ICANN at: 255 /report/registrar-escrow-agent-notification/ 257 Where: 259 * MUST be substituted with the IANA Registrar ID 260 assigned by ICANN for which the notification is being provided. 262 A with DRFN (Deposit Receipt Failure 263 Notice) status is used to notify that a data escrow deposit has not 264 been processed for verification for a past date where a deposit was 265 scheduled to be received from the Registrar. 267 In addition to the considerations listed in Section 2.1 for the 268 object of the notification, if the data escrow 269 deposit does not include an , a unique value MUST be generated by 270 the Data Escrow Agent to reference the deposit and it MUST be 271 provided in the element. 273 In the case of a with DVFN (Deposit 274 Verification Failure Notice) status, the 275 element MUST be present and include a object for each 276 deposit verification error condition and specify in the corresponding 277 "domainCount" attribute the number of domain names with such error 278 conditions. 280 Note: an error condition may be present several times in the same 281 domain escrow record (e.g., the administrative, technical and billing 282 contact contains invalid email syntax). In this case only one domain 283 name is affected by the error condition, therefore the "domainCount" 284 attribute value must be increased by one in the corresponding 285 object. 287 The following table defines the result codes and messages that a Data 288 Escrow Agent could use to report verification issues found in a 289 Registrar data escrow deposit. When using result codes 2102, 2103, 290 2104, 2105, 2106, 2107, 2108, 2109, or 2110, the "domainCount" 291 attribute MUST be present. 293 +-----------+-------------------------------------------------------+ 294 | Result | Message | 295 | Code | | 296 +-----------+-------------------------------------------------------+ 297 | 2001 | No corresponding hash file found for deposit file. | 298 | 2002 | Hash does not match the corresponding deposit file. | 299 | 2003 | Invalid hash file format. | 300 | 2004 | Data escrow deposit PGP signature verification error. | 301 | 2005 | Archive includes unrecognized files. | 302 | 2006 | Invalid encoding for data escrow deposit file. | 303 | 2007 | Data escrow deposit file size exceeds the maximum | 304 | | allowed size. | 305 | 2008 | Data escrow deposit file exceeds the maximum allowed | 306 | | number of lines. | 307 | 2101 | Unrecognized data escrow deposit file CSV header. | 308 | 2102 | Escrow Record structure does not conform with CSV | 309 | | header definition. | 310 | 2103 | Escrow Record found missing data in required | 311 | | field(s). | 312 | 2104 | Invalid domain name syntax in Escrow Record. | 313 | 2105 | Invalid email syntax in Escrow Record. | 314 | 2106 | Invalid hostname syntax in Escrow Record. | 315 | 2107 | Invalid date syntax in Escrow Record. | 316 | 2108 | Invalid phone syntax in Escrow Record. | 317 | 2109 | Duplicate domain or handle Escrow Record found in | 318 | | deposit. | 319 | 2110 | Handle reference by Escrow Record not found. | 320 | 2201 | "Full" data escrow deposit expected but received | 321 | | "Differential" instead. | 322 | 2202 | Data Escrow deposit date is in the future. | 323 | 2203 | A data escrow deposit has been already successfully | 324 | | verified for that date. | 325 +-----------+-------------------------------------------------------+ 327 Registrar Data Escrow Deposit Verification Result Codes 329 Example of a object of a Data Escrow 330 Agent notification corresponding to a Registrar Data Escrow deposit 331 that was not received or could not be processed for verification: 333 334 336 Escrow Agent Inc. 337 1 338 2017-06-17 339 DRFN 340 2017-06-10 341 342 344 Example of a object of a Data Escrow 345 Agent notification corresponding to a Registrar repository Data 346 Escrow deposit that has passed the verification process: 348 349 353 Escrow Agent Inc. 354 1 355 356 2017-06-17 357 DVPN 358 359 2017-06-17T03:15:00.0Z 360 361 2017-06-17T05:15:00.0Z 362 363 2017-06-17 364 365 20170617001 366 1 367 368 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 369 370 0 371 2017-06-17T00:15:00.0Z 372 FULL 373 2017-06-17T00:00:00Z 374 375 9999 376 2 378 6 380 1 382 383 384 386 Example of a object of a Data Escrow 387 Agent notification corresponding to a Registrar repository Data 388 Escrow deposit that has failed the verification process: 390 391 396 Escrow Agent Inc. 397 1 398 2017-06-17 399 DVFN 400 401 402 403 Invalid domain name syntax in Escrow Record. 404 405 406 407 408 Handle reference by Escrow Record not found. 409 410 411 412 413 2017-06-17T03:15:00.0Z 414 415 416 2017-06-17T05:15:00.0Z 417 418 419 2017-06-14 420 421 422 20170617001 423 1 424 425 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 426 427 0 428 2017-06-17T00:15:00.0Z 429 FULL 430 2017-06-17T00:00:00Z 431 432 9999 433 2 435 8 437 3 439 440 441 443 3. Technical details of the interfaces 445 Content-type value in the HTTP header: 447 o The client MUST set "text/xml" in the HTTP header Content-type 448 when using the Data Escrow Agent Reporting and Registrar Reporting 449 interfaces described in Section 2. 451 After successfully receiving and processing an input, the interfaces 452 return any of the HTTP status codes described in Section 4 of 453 [I-D.lozano-icann-registry-interfaces]. 455 The following sections provide the IIRDEA Result Codes that can be 456 expected in the object from each interface: 458 3.1. Registrar Reporting 460 The following table lists the result codes of the interface: 462 +---------+---------------------------------------------------------+ 463 | Result | Message | 464 | Code | | 465 +---------+---------------------------------------------------------+ 466 | 1000 | No ERRORs were found and the report has been accepted | 467 | | by ICANN. | 468 | 2001 | The request did not validate against the schema. | 469 | 2004 | Report for a date in the future. The and | 470 | | date should not be in the future. | 471 | 2005 | Version is not supported. | 472 | 2006 | The in the element and the in the | 473 | | URL path do not match. | 474 | 2301 | Interface is disabled for this Registrar. | 475 | 2302 | The and date should not be before | 476 | | the creation date of the Registrar in the system. | 477 | 2303 | The in the
and the in | 478 | | the URL path do not match. | 479 | 2304 | Report regarding an differential deposit received when | 480 | | a full deposit was expected (). | 481 | 2305 | attribute missing in count element provided in | 482 | | the
. | 483 | 2306 | Multiple count elements with the same and | 484 | | attribute values provided in the
. | 485 | 2307 | Missing required element in the
. | 486 | 2312 | An invalid NR-LDH label or A-label was found or the | 487 | | domain name syntax is invalid in the attribute. | 488 | 2313 | INCR is not supported. | 489 +---------+---------------------------------------------------------+ 491 Registrar Data Escrow Reporting Result Codes 493 3.2. Data Escrow Agent Reporting 495 The following table lists the result codes of the interface: 497 +--------+----------------------------------------------------------+ 498 | Result | Message | 499 | Code | | 500 +--------+----------------------------------------------------------+ 501 | 1000 | No ERRORs were found and the notification has been | 502 | | accepted by ICANN. | 503 | 2001 | The request did not validate against the schema. | 504 | 2002 | A DVPN notification exists for that date (). | 505 | 2004 | Notification for a date in the future. The , | 506 | | , and date should | 507 | | not be in the future. | 508 | 2005 | Version is not supported. | 509 | 2201 | The and in the notification do not | 510 | | match. | 511 | 2203 | A Deposit Verification Pass Notice (DVPN) notification | 512 | | was received, but the Domain Name count is missing in | 513 | | the
. | 514 | 2204 | The notification for the report "id" already exists. | 515 | 2207 | A DVPN or DVFN was received, but the element is | 516 | | missing in the notification. | 517 | 2208 | A DRFN was received, but a element exists in | 518 | | the notification. | 519 | 2209 | and elements must not be present in a | 520 | | DRFN. | 521 | 2301 | Interface is disabled for this Registrar. | 522 | 2302 | The and and date should | 523 | | not be before the creation date of the Registrar in the | 524 | | system. | 525 | 2303 | The in the
and the in | 526 | | the URL path do not match. | 527 | 2304 | Notification regarding an differential deposit received | 528 | | when a full deposit was expected (). | 529 | 2305 | attribute missing in count element provided in | 530 | | the
. | 531 | 2306 | Multiple count elements with the same and | 532 | | attribute values provided in the
. | 533 | 2307 | Missing required element in the
. | 534 | 2309 | A DVFN was received, but the element is | 535 | | missing in the notification. | 536 | 2310 | The specified result code in the element | 537 | | requires the "domainCount" attribute to be present. | 538 | 2311 | Unrecognized value in the "code" attribute of the | 539 | | element. | 540 | 2312 | An invalid NR-LDH label or A-label was found or the | 541 | | domain name syntax is invalid in the attribute. | 542 | 2313 | INCR is not supported. | 543 +--------+----------------------------------------------------------+ 545 Data Escrow Agent Reporting Result Codes 547 4. Monitoring Registrar reporting 549 Registrars MAY monitor the status of the data escrow reporting 550 notifications requirement using the following interfaces that support 551 the GET HTTP verb. 553 4.1. Monitoring the reporting status of a Registrar 555 Registrars MAY monitor the general reporting status and obtain a list 556 of any outstanding issues using the following interface: 558 /info/status/registrar/ 560 Where: 562 * MUST be substituted with the IANA ID assigned by 563 ICANN to the Registrar being queried. 565 This interface provides a element as defined 566 in Section 2 of [I-D.lozano-icann-registry-interfaces] that uses the 567 element and includes the following 568 values: 570 o "Registrar_Escrow_Report" : For Registrar Data Escrow Reporting as 571 defined in Section 2.1. The "date" attribute for any reporting 572 issue is provided in "YYYY-MM-DD" format. 574 o "DEA_Notification" : For Data Escrow Agent Notifications as 575 defined in Section 2.2. The "date" attribute for any reporting 576 issue is provided in "YYYY-MM-DD" format. 578 Example of response for a Registrar status check with no reporting 579 issues: 581 HTTP/1.1 200 OK 582 Content-Type: application/xml 583 Content-Length: 1125 585 586 589 9999 590 591 2017-06-10T12:00:30.101Z 592 Daily 593 2017-10-15 594 595 596 Registrar_Escrow_Report 597 false 598 ok 599 600 601 DEA_Notification 602 true 603 ok 604 605 606 607 2017-10-20T02:22:14.148Z 608 610 Example of response for a Registrar status check with reporting 611 issues: 613 HTTP/1.1 200 OK 614 Content-Type: application/xml 615 Content-Length: 1604 617 618 621 9999 622 623 2017-06-10T12:00:30.101Z 624 Daily 625 2017-10-08 626 627 628 Registrar_Escrow_Report 629 true 630 ok 631 632 633 DEA_Notification 634 true 635 unsatisfactory 636 637 639 641 643 645 646 647 648 649 2017-10-20T02:22:14.148Z 650 652 4.2. Monitoring Registrar Data Escrow Reports 654 Registrars MAY monitor the status of their Data Escrow reports using 655 the following interface: 657 /info/report/registrar-escrow-report// 659 Where: 661 * MUST be substituted with the IANA ID assigned by 662 ICANN to the Registrar being queried. 664 * MUST be substituted with the date being queried in 665 "YYYY-MM-DD" format. For example: 2017-08-01. 667 Possible results are: 669 o The interface provides a HTTP/200 status code with a 670 element in the response content as defined in 671 Section 2 of [I-D.lozano-icann-registry-interfaces], listing each 672 successfully received with watermark value that 673 matches the queried date. 675 Example of response for a Registrar Data Escrow Reporting status 676 check: 678 HTTP/1.1 200 OK 679 Content-Type: application/xml 680 Content-Length: 1194 682 683 687 688 2017-10-13T00:30:13.741Z 689 690 20171013001 691 1 692 693 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 694 695 0 696 2017-10-13T00:01:11.000Z 697 FULL 698 2017-10-13T00:00:00.00Z 699 700 9999 701 10 703 1 705 706 707 708 710 4.3. Monitoring Registrar Data Escrow Agent Notifications 712 Registrars and Data Escrow Agents MAY monitor the status of Data 713 Escrow Agent Notifications using the following interface: 715 /info/report/registrar-escrow-agent-notification// 718 Where: 720 * MUST be substituted with the IANA ID assigned by 721 ICANN to the Registrar being queried. 723 * MUST be substituted with the date being queried in 724 "YYYY-MM-DD" format. For example: 2017-08-01. 726 Possible results are: 728 o The interface provides a HTTP/200 status code with a 729 element in the response content 730 as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], 731 listing each successfully received 732 with a watermark value that matches the queried date. 734 Example of a response of a Registrar Data Escrow Agent Notification 735 status check for a date with two received notifications: 737 HTTP/1.1 200 OK 738 Content-Type: application/xml 739 Content-Length: 2578 741 742 748 749 750 2017-10-17T23:59:59.0Z 751 752 753 Escrow Agent Inc. 754 1 755 2017-10-17 756 DRFN 757 758 2017-10-14 759 760 761 762 763 2017-10-18T06:00:00.0Z 764 765 766 Escrow Agent Inc. 767 1 768 2017-10-17 769 DVPN 770 771 2017-10-18T03:15:00.0Z 772 773 2017-10-18T05:15:00.0Z 775 776 2017-10-17 777 778 20171017001 779 1 780 781 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 782 783 0 784 2017-10-17T00:15:00.0Z 785 FULL 786 2017-10-17T00:00:00Z 787 788 9999 789 10 791 1 793 794 795 796 797 799 5. Internationalization Considerations 801 The interfaces described in this document use XML, which provides 802 native support for encoding information using the Unicode character 803 set and its more compact representations including UTF-8. Conformant 804 XML processors recognize both UTF-8 and UTF-16. Though XML includes 805 provisions to identify and use other character encodings through use 806 of an "encoding" attribute in an declaration, use of UTF-8 is 807 RECOMMENDED. 809 6. IANA Considerations 811 No actions are required from IANA. 813 7. Implementation Status 815 Note to RFC Editor: Please remove this section and the reference to 816 RFC 7942 [RFC7942] before publication. 818 This section records the status of known implementations of the 819 protocol defined by this specification at the time of posting of this 820 Internet-Draft, and is based on a proposal described in RFC 7942 821 [RFC7942]. The description of implementations in this section is 822 intended to assist the IETF in its decision processes in progressing 823 drafts to RFCs. Please note that the listing of any individual 824 implementation here does not imply endorsement by the IETF. 825 Furthermore, no effort has been spent to verify the information 826 presented here that was supplied by IETF contributors. This is not 827 intended as, and must not be construed to be, a catalog of available 828 implementations or their features. Readers are advised to note that 829 other implementations may exist. 831 According to RFC 7942 [RFC7942], "this will allow reviewers and 832 working groups to assign due consideration to documents that have the 833 benefit of running code, which may serve as evidence of valuable 834 experimentation and feedback that have made the implemented protocols 835 more mature. It is up to the individual working groups to use this 836 information as they see fit". 838 7.1. Implementation in the gTLD space 840 Organization: ICANN 842 Name: Registrar Data Escrow Specifications 844 Description: Data Escrow Agents, and ICANN implement this 845 specification. ICANN receives daily notifications from Data Escrow 846 Agents using this specification. 848 Level of maturity: production. 850 Coverage: all aspects of this specification are implemented. 852 Version compatibility: versions 00 - 04 are known to be implemented. 854 Contact: gustavo.lozano@icann.org 856 URL: https://www.icann.org/en/system/files/files/rde-specs- 857 09nov07-en.pdf 859 8. Security Considerations 861 The interfaces described in this document MUST be provided using 862 HTTPS. The recommendations in [RFC7525] MUST be implemented. 864 9. Change History 866 [[RFC Editor: Please remove this section.]] 868 9.1. Version 00 870 Initial version. 872 9.2. Version 01 874 o Added clarifications, list of result codes that require the 875 "domainCount" attribute to be present, and additional examples of 876 objects in Section 2.2. 878 o Removed HTTP/404 from the possible results of interfaces to 879 monitor data escrow notifications and registrar reports. 881 9.3. Version 02 883 1. Ping update. 885 9.4. Version 03 887 1. Ping update. 889 9.5. Version 04 891 1. Ping update. 893 9.6. Version 05 895 1. IANA Considerations section added. 897 2. Implementation section added. 899 3. Internationalization Considerations status section added. 901 4. Security section added. 903 5. Editorial updates. 905 10. References 907 10.1. Normative References 909 [I-D.ietf-regext-data-escrow] 910 Lozano, G., "Registry Data Escrow Specification", draft- 911 ietf-regext-data-escrow-10 (work in progress), June 2020. 913 [I-D.ietf-regext-dnrd-objects-mapping] 914 Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name 915 Registration Data (DNRD) Objects Mapping", draft-ietf- 916 regext-dnrd-objects-mapping-08 (work in progress), June 917 2020. 919 [I-D.lozano-icann-registry-interfaces] 920 Lozano, G. and E. Alvarez, "ICANN Registry Interfaces", 921 draft-lozano-icann-registry-interfaces-13 (work in 922 progress), June 2020. 924 [ICANN-RDE-SPEC] 925 ICANN, "Registrar Data Escrow specifications", Nov 2007, 926 . 929 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 930 Requirement Levels", BCP 14, RFC 2119, 931 DOI 10.17487/RFC2119, March 1997, 932 . 934 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 935 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 936 . 938 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 939 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 940 May 2017, . 942 [W3C.REC-xml-20081126] 943 Bray, T., Paoli, J., Sperberg-McQueen, C., Maler, E., and 944 F. Yergeau, "Extensible Markup Language (XML) 1.0 (Fifth 945 Edition) REC-xml-20081126", November 2008, 946 . 948 10.2. Informative References 950 [ICANN-RAA-2013] 951 ICANN, "2013 Registrar Accreditation Agreement", Jun 2013, 952 . 955 [RFC5890] Klensin, J., "Internationalized Domain Names for 956 Applications (IDNA): Definitions and Document Framework", 957 RFC 5890, DOI 10.17487/RFC5890, August 2010, 958 . 960 [RFC7525] Sheffer, Y., Holz, R., and P. Saint-Andre, 961 "Recommendations for Secure Use of Transport Layer 962 Security (TLS) and Datagram Transport Layer Security 963 (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May 964 2015, . 966 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 967 Code: The Implementation Status Section", BCP 205, 968 RFC 7942, DOI 10.17487/RFC7942, July 2016, 969 . 971 Authors' Addresses 973 Gustavo Lozano 974 ICANN 975 12025 Waterfront Drive, Suite 300 976 Los Angeles 90292 977 US 979 Phone: +1.3103015800 980 Email: gustavo.lozano@icann.org 982 Eduardo Alvarez 983 ICANN 984 12025 Waterfront Drive, Suite 300 985 Los Angeles 90292 986 US 988 Phone: +1.3103015800 989 Email: eduardo.alvarez@icann.org