idnits 2.17.1 draft-icann-registrar-interfaces-04.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 (March 26, 2020) is 1492 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3688' is defined on line 857, but no explicit reference was found in the text == Outdated reference: A later version (-21) exists of draft-lozano-icann-registry-interfaces-11 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). 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 27, 2020 March 26, 2020 7 ICANN Registrar Interfaces 8 draft-icann-registrar-interfaces-04 10 Abstract 12 This document describes the interfaces provided by ICANN to 13 Registrars and Data Escrow Agents in order 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 27, 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 . . . . . . . . . . . . . . . . . . . . . . . 2 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. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 21 66 6. Security Considerations . . . . . . . . . . . . . . . . . . . 21 67 7. Change History . . . . . . . . . . . . . . . . . . . . . . . 21 68 7.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 21 69 7.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 21 70 7.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 22 71 7.4. Version 03 . . . . . . . . . . . . . . . . . . . . . . . 22 72 7.5. Version 04 . . . . . . . . . . . . . . . . . . . . . . . 22 73 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 74 8.1. Normative References . . . . . . . . . . . . . . . . . . 22 75 8.2. Informative References . . . . . . . . . . . . . . . . . 23 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 78 1. Introduction 80 This document describes the technical details of the interfaces 81 provided by the Internet Corporation for Assigned Names and Numbers 82 (ICANN) to Registrars and Data Escrow Agents in order to fulfill the 83 data escrow requirements of the Registrar Accreditation Agreement 84 [ICANN-RAA-2013] and the Registrar Data Escrow Specifications 85 [ICANN-RDE-SPEC]. 87 1.1. Terminology 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 91 document are to be interpreted as described in RFC 2119 [RFC2119]. 93 XML is case sensitive. Unless stated otherwise, XML specifications 94 and examples provided in this document MUST be interpreted in the 95 character case presented in order to develop a conforming 96 implementation. 98 1.2. Date and Time 100 Numerous fields indicate "date and time", such as the creation and 101 receipt dates for data escrow deposits. These fields SHALL contain 102 timestamps indicating the date and time in UTC as specified in 103 [RFC3339], with no offset from the zero meridian. 105 1.3. Common elements used in this specification 107 Common elements used in this specification are explained in this 108 section. 110 o : The base URL used in the reporting interfaces examples 111 must be replaced with the URL indicated by ICANN. 113 o This document uses the term of "Differential" deposit as defined 114 in the Registry Data Escrow Specification (see, 115 [I-D.arias-noguchi-registry-data-escrow]), while the Registrar 116 Data Escrow Specifications [ICANN-RDE-SPEC] refers to the same 117 concept as "Incremental" deposit. 119 2. Interfaces for Registrar Data Escrow Notifications 121 This section describes the interfaces provided by ICANN to the 122 Registrars and Data Escrow Agents in order to fulfill their reporting 123 requirements related to Registrar Data Escrow Specifications 124 [ICANN-RDE-SPEC]. 126 2.1. Registrar Reporting 128 To notify that a data escrow deposit has been submitted to a Data 129 Escrow Agent, the ICANN-accredited Registrar sends a 130 object (see, 131 [I-D.lozano-icann-registry-interfaces]) to ICANN. 133 The following considerations apply for a object 134 corresponding to a data escrow deposit for a Registrar repository: 136 o The element in the object 137 (see, [I-D.arias-noguchi-dnrd-objects-mapping]) MUST be present 138 and have a value corresponding to the IANA Registrar ID assigned 139 by ICANN. 141 o A element MUST be included with the 142 corresponding "rcdn" attribute in the object to 143 indicate the total domains in the Registrar repository for each 144 Registry Class Domain Name (e.g. example) with at least one domain 145 name allocation at a specific point in time (watermark), 146 regardless of the type of deposit: full or differential. 148 * If the "https://www.icann.org/en/system/files/files/rde-specs- 149 09nov07-en.pdf" specification is being used as the 150 , then the "uri" attribute in the 151 elements for domain names MUST have a value 152 of "urn:ietf:params:xml:ns:rdeDomain-1.0". 154 o To indicate that a Registrar repository has no domain names, one 155 element MUST be included with the "uri" 156 attribute value of "urn:ietf:params:xml:ns:rdeDomain-1.0", no 157 "rcdn" attribute, and a value of 0 (zero). 159 The object for each deposit successfully sent to 160 the Data Escrow Agent is sent using the PUT HTTP verb in the 161 interface provided by ICANN at: 163 /report/registrar-escrow-report// 165 Where: 167 * MUST be substituted with the IANA Registrar ID 168 assigned by ICANN for which the report is being provided. 170 * MUST be substituted with the identifier assigned to this 171 report, which MUST be the same as the "id" attribute from the 172 . 174 Note: The interface supports overwriting the information of a 175 particular report to support asynchronous interfaces between 176 Registrars and Data Escrow Agents. 178 Example of a object for a data escrow deposit 179 corresponding to a Registrar repository: 181 182 185 20170801001 186 1 187 188 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 189 190 0 191 2017-08-01T00:15:00.0Z 192 FULL 193 2017-08-01T00:00:00Z 194 195 9999 196 2 198 8 200 3 202 203 205 Example of a object for an empty data escrow 206 deposit corresponding to a Registrar repository: 208 209 212 20170801001 213 1 214 215 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 216 217 0 218 2017-08-01T00:15:00.0Z 219 FULL 220 2017-08-01T00:00:00Z 221 222 9999 223 224 0 225 226 228 2.2. Data Escrow Agent Reporting 230 The Registrar Data Escrow Specification requires that Registrar Data 231 Escrow Agents deliver to ICANN a notification every time a 232 successfully processed deposit is received from the Registrar 233 regardless of the final status of the verification process, in 234 addition to a failure notification if a scheduled deposit is not 235 received from a Registrar. 237 In order to satisfy this requirement, the Data Escrow Agent sends to 238 ICANN a object as defined in Section 2 239 of [I-D.lozano-icann-registry-interfaces], to ICANN using the POST 240 HTTP verb in the interface provided by ICANN at: 242 /report/registrar-escrow-agent-notification/ 244 Where: 246 * MUST be substituted with the IANA Registrar ID 247 assigned by ICANN for which the notification is being provided. 249 A with DRFN (Deposit Receipt Failure 250 Notice) status is used to notify that a data escrow deposit has not 251 been processed for verification for a past date where a deposit was 252 scheduled to be received from the Registrar. 254 In addition to the considerations listed in Section 2.1 for the 255 object of the notification, if the data escrow 256 deposit does not include an , a unique value MUST be generated by 257 the Data Escrow Agent to reference the deposit and it MUST be 258 provided in the element. 260 In the case of a with DVFN (Deposit 261 Verification Failure Notice) status, the 262 element MUST be present and include a object for each 263 deposit verification error condition and specify in the corresponding 264 "domainCount" attribute the number of domain names with such error 265 conditions. 267 Note: an error condition may be present several times in the the same 268 domain escrow record (e.g. the administrative, technical and billing 269 contact contain invalid email syntax). In this case only one domain 270 name is affected by the error condition, therefore the "domainCount" 271 attribute value must be increased by one in the corresponding 272 object. 274 The following table defines the result codes and messages that a Data 275 Escrow Agent could use to report verification issues found in a 276 Registrar data escrow deposit. When using result codes 2102, 2103, 277 2104, 2105, 2106, 2107, 2108, 2109, or 2110, the "domainCount" 278 attribute MUST be present. 280 +-----------+-------------------------------------------------------+ 281 | Result | Message | 282 | Code | | 283 +-----------+-------------------------------------------------------+ 284 | 2001 | No corresponding hash file found for deposit file. | 285 | 2002 | Hash does not match corresponding deposit file. | 286 | 2003 | Invalid hash file format. | 287 | 2004 | Data escrow deposit PGP signature verification error. | 288 | 2005 | Archive includes unrecognized files. | 289 | 2006 | Invalid encoding for data escrow deposit file. | 290 | 2007 | Data escrow deposit file size exceeds maximum allowed | 291 | | size. | 292 | 2008 | Data escrow deposit file exceeds maximum allowed | 293 | | number of lines. | 294 | 2101 | Unrecognized data escrow deposit file CSV header. | 295 | 2102 | Escrow Record structure does not conform with CSV | 296 | | header definition. | 297 | 2103 | Escrow Record found missing data in required | 298 | | field(s). | 299 | 2104 | Invalid domain name syntax in Escrow Record. | 300 | 2105 | Invalid email syntax in Escrow Record. | 301 | 2106 | Invalid hostname syntax in Escrow Record. | 302 | 2107 | Invalid date syntax in Escrow Record. | 303 | 2108 | Invalid phone syntax in Escrow Record. | 304 | 2109 | Duplicate domain or handle Escrow Record found in | 305 | | deposit. | 306 | 2110 | Handle reference by Escrow Record not found. | 307 | 2201 | "Full" data escrow deposit expected but received | 308 | | "Differential" instead. | 309 | 2202 | Data Escrow deposit date is in the future. | 310 | 2203 | A data escrow deposit has been already successfully | 311 | | verified for that date. | 312 +-----------+-------------------------------------------------------+ 314 Registrar Data Escrow Deposit Verification Result Codes 316 Example of a object of a Data Escrow 317 Agent notification corresponding to a Registrar Data Escrow deposit 318 that was not received or could not be processed for verification: 320 321 323 Escrow Agent Inc. 324 1 325 2017-06-17 326 DRFN 327 2017-06-10 328 329 331 Example of a object of a Data Escrow 332 Agent notification corresponding to a Registrar repository Data 333 Escrow deposit that has passed the verification process: 335 336 340 Escrow Agent Inc. 341 1 342 343 2017-06-17 344 DVPN 345 346 2017-06-17T03:15:00.0Z 347 348 2017-06-17T05:15:00.0Z 349 350 2017-06-17 351 352 20170617001 353 1 354 355 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 356 357 0 358 2017-06-17T00:15:00.0Z 359 FULL 360 2017-06-17T00:00:00Z 361 362 9999 363 2 365 6 367 1 369 370 371 373 Example of a object of a Data Escrow 374 Agent notification corresponding to a Registrar repository Data 375 Escrow deposit that has failed the verification process: 377 378 383 Escrow Agent Inc. 384 1 385 2017-06-17 386 DVFN 387 388 389 390 Invalid domain name syntax in Escrow Record. 391 392 393 394 395 Handle reference by Escrow Record not found. 396 397 398 399 400 2017-06-17T03:15:00.0Z 401 402 403 2017-06-17T05:15:00.0Z 404 405 406 2017-06-14 407 408 409 20170617001 410 1 411 412 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 413 414 0 415 2017-06-17T00:15:00.0Z 416 FULL 417 2017-06-17T00:00:00Z 418 419 9999 420 2 422 8 424 3 426 427 428 430 3. Technical details of the interfaces 432 Content-type value in the HTTP header: 434 o The client MUST set "text/xml" in the HTTP header Content-type 435 when using the Data Escrow Agent Reporting and Registrar Reporting 436 interfaces described in Section 2. 438 After successfully receiving and processing an input, the interfaces 439 return any of the HTTP status codes described in Section 4 of 440 [I-D.lozano-icann-registry-interfaces]. 442 The following sections provide the IIRDEA Result Codes that can be 443 expected in the object from each interface: 445 3.1. Registrar Reporting 447 The following table lists the result codes of the interface: 449 +---------+---------------------------------------------------------+ 450 | Result | Message | 451 | Code | | 452 +---------+---------------------------------------------------------+ 453 | 1000 | No ERRORs were found and the report has been accepted | 454 | | by ICANN. | 455 | 2001 | The request did not validate against the schema. | 456 | 2004 | Report for a date in the future. The and | 457 | | date should not be in the future. | 458 | 2005 | Version is not supported. | 459 | 2006 | The in the element and the in the | 460 | | URL path do not match. | 461 | 2301 | Interface is disabled for this Registrar. | 462 | 2302 | The and date should not be before | 463 | | the creation date of the Registrar in the system. | 464 | 2303 | The in the
and the in | 465 | | the URL path do not match. | 466 | 2304 | Report regarding an differential deposit received when | 467 | | a full deposit was expected (). | 468 | 2305 | attribute missing in count element provided in | 469 | | the
. | 470 | 2306 | Multiple count elements with the same and | 471 | | attribute values provided in the
. | 472 | 2307 | Missing required element in the
. | 473 | 2312 | An invalid NR-LDH label or A-label was found or the | 474 | | domain name syntax is invalid in the attribute. | 475 | 2313 | INCR is not supported. | 476 +---------+---------------------------------------------------------+ 478 Registrar Data Escrow Reporting Result Codes 480 3.2. Data Escrow Agent Reporting 482 The following table lists the result codes of the interface: 484 +--------+----------------------------------------------------------+ 485 | Result | Message | 486 | Code | | 487 +--------+----------------------------------------------------------+ 488 | 1000 | No ERRORs were found and the notification has been | 489 | | accepted by ICANN. | 490 | 2001 | The request did not validate against the schema. | 491 | 2002 | A DVPN notification exists for that date (). | 492 | 2004 | Notification for a date in the future. The , | 493 | | , and date should | 494 | | not be in the future. | 495 | 2005 | Version is not supported. | 496 | 2201 | The and in the notification do not | 497 | | match. | 498 | 2203 | A Deposit Verification Pass Notice (DVPN) notification | 499 | | was received, but the Domain Name count is missing in | 500 | | the
. | 501 | 2204 | The notification for the report "id" already exists. | 502 | 2207 | A DVPN or DVFN was received, but the element is | 503 | | missing in the notification. | 504 | 2208 | A DRFN was received, but a element exists in | 505 | | the notification. | 506 | 2209 | and elements must not be present in a | 507 | | DRFN. | 508 | 2301 | Interface is disabled for this Registrar. | 509 | 2302 | The and and date should | 510 | | not be before the creation date of the Registrar in the | 511 | | system. | 512 | 2303 | The in the
and the in | 513 | | the URL path do not match. | 514 | 2304 | Notification regarding an differential deposit received | 515 | | when a full deposit was expected (). | 516 | 2305 | attribute missing in count element provided in | 517 | | the
. | 518 | 2306 | Multiple count elements with the same and | 519 | | attribute values provided in the
. | 520 | 2307 | Missing required element in the
. | 521 | 2309 | A DVFN was received, but the element is | 522 | | missing in the notification. | 523 | 2310 | The specified result code in the element | 524 | | requires the "domainCount" attribute to be present. | 525 | 2311 | Unrecognized value in the "code" attribute of the | 526 | | element. | 527 | 2312 | An invalid NR-LDH label or A-label was found or the | 528 | | domain name syntax is invalid in the attribute. | 529 | 2313 | INCR is not supported. | 530 +--------+----------------------------------------------------------+ 532 Data Escrow Agent Reporting Result Codes 534 4. Monitoring Registrar reporting 536 Registrars MAY monitor the status of the data escrow reporting 537 notifications requirement using the following interfaces that support 538 the GET HTTP verb. 540 4.1. Monitoring the reporting status of a Registrar 542 Registrars MAY monitor the general reporting status and obtain a list 543 of any outstanding issues using the following interface: 545 /info/status/registrar/ 547 Where: 549 * MUST be substituted with the IANA ID assigned by 550 ICANN to the Registrar being queried. 552 This interface provides a element as defined 553 in Section 2 of [I-D.lozano-icann-registry-interfaces] that uses the 554 element and includes the following 555 values: 557 o "Registrar_Escrow_Report" : For Registrar Data Escrow Reporting as 558 defined in Section 2.1. The "date" attribute for any reporting 559 issue is provided in "YYYY-MM-DD" format. 561 o "DEA_Notification" : For Data Escrow Agent Notifications as 562 defined in Section 2.2. The "date" attribute for any reporting 563 issue is provided in "YYYY-MM-DD" format. 565 Example of response for a Registrar status check with no reporting 566 issues: 568 HTTP/1.1 200 OK 569 Content-Type: application/xml 570 Content-Length: 1125 572 573 576 9999 577 578 2017-06-10T12:00:30.101Z 579 Daily 580 2017-10-15 581 582 583 Registrar_Escrow_Report 584 false 585 ok 586 587 588 DEA_Notification 589 true 590 ok 591 592 593 594 2017-10-20T02:22:14.148Z 595 597 Example of response for a Registrar status check with reporting 598 issues: 600 HTTP/1.1 200 OK 601 Content-Type: application/xml 602 Content-Length: 1604 604 605 608 9999 609 610 2017-06-10T12:00:30.101Z 611 Daily 612 2017-10-08 613 614 615 Registrar_Escrow_Report 616 true 617 ok 618 619 620 DEA_Notification 621 true 622 unsatisfactory 623 624 626 628 630 632 633 634 635 636 2017-10-20T02:22:14.148Z 637 639 4.2. Monitoring Registrar Data Escrow Reports 641 Registrars MAY monitor the status of their Data Escrow reports using 642 the following interface: 644 /info/report/registrar-escrow-report// 646 Where: 648 * MUST be substituted with the IANA ID assigned by 649 ICANN to the Registrar being queried. 651 * MUST be substituted with the date being queried in 652 "YYYY-MM-DD" format. For example: 2017-08-01 654 Possible results are: 656 o The interface provides a HTTP/200 status code with a 657 element in the response content as defined in 658 Section 2 of [I-D.lozano-icann-registry-interfaces], listing each 659 successfully received with watermark value that 660 matches the queried date. 662 Example of response for a Registrar Data Escrow Reporting status 663 check: 665 HTTP/1.1 200 OK 666 Content-Type: application/xml 667 Content-Length: 1194 669 670 674 675 2017-10-13T00:30:13.741Z 676 677 20171013001 678 1 679 680 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 681 682 0 683 2017-10-13T00:01:11.000Z 684 FULL 685 2017-10-13T00:00:00.00Z 686 687 9999 688 10 690 1 692 693 694 695 697 4.3. Monitoring Registrar Data Escrow Agent Notifications 699 Registrars and Data Escrow Agents MAY monitor the status of Data 700 Escrow Agent Notifications using the following interface: 702 /info/report/registrar-escrow-agent-notification// 705 Where: 707 * MUST be substituted with the IANA ID assigned by 708 ICANN to the Registrar being queried. 710 * MUST be substituted with the date being queried in 711 "YYYY-MM-DD" format. For example: 2017-08-01 713 Possible results are: 715 o The interface provides a HTTP/200 status code with a 716 element in the response content 717 as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], 718 listing each successfully received 719 with a watermark value that matches the queried date. 721 Example of a response of a Registrar Data Escrow Agent Notification 722 status check for a date with 2 received notifications: 724 HTTP/1.1 200 OK 725 Content-Type: application/xml 726 Content-Length: 2578 728 729 735 736 737 2017-10-17T23:59:59.0Z 738 739 740 Escrow Agent Inc. 741 1 742 2017-10-17 743 DRFN 744 745 2017-10-14 746 747 748 749 750 2017-10-18T06:00:00.0Z 751 752 753 Escrow Agent Inc. 754 1 755 2017-10-17 756 DVPN 757 758 2017-10-18T03:15:00.0Z 759 760 2017-10-18T05:15:00.0Z 762 763 2017-10-17 764 765 20171017001 766 1 767 768 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 769 770 0 771 2017-10-17T00:15:00.0Z 772 FULL 773 2017-10-17T00:00:00Z 774 775 9999 776 10 778 1 780 781 782 783 784 786 5. IANA Considerations 788 TODO 790 6. Security Considerations 792 TODO 794 7. Change History 796 [[RFC Editor: Please remove this section.]] 798 7.1. Version 00 800 Initial version. 802 7.2. Version 01 804 o Added clarifications, list of result codes that require the 805 "domainCount" attribute to be present, and additional examples of 806 objects in Section 2.2. 808 o Removed HTTP/404 from the possible results of interfaces to 809 monitor data escrow notifications and registrar reports. 811 7.3. Version 02 813 1. Ping update. 815 7.4. Version 03 817 1. Ping update. 819 7.5. Version 04 821 1. Ping update. 823 8. References 825 8.1. Normative References 827 [I-D.arias-noguchi-dnrd-objects-mapping] 828 Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name 829 Registration Data (DNRD) Objects Mapping", draft-arias- 830 noguchi-dnrd-objects-mapping-10 (work in progress), 831 January 2019. 833 [I-D.arias-noguchi-registry-data-escrow] 834 Lozano, G., "Registry Data Escrow Specification", draft- 835 arias-noguchi-registry-data-escrow-11 (work in progress), 836 January 2019. 838 [I-D.lozano-icann-registry-interfaces] 839 Lozano, G. and E. Alvarez, "ICANN Registry Interfaces", 840 draft-lozano-icann-registry-interfaces-11 (work in 841 progress), September 2019. 843 [ICANN-RDE-SPEC] 844 ICANN, "Registrar Data Escrow specifications", Nov 2007, 845 . 848 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 849 Requirement Levels", BCP 14, RFC 2119, 850 DOI 10.17487/RFC2119, March 1997, 851 . 853 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 854 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 855 . 857 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 858 DOI 10.17487/RFC3688, January 2004, 859 . 861 8.2. Informative References 863 [ICANN-RAA-2013] 864 ICANN, "2013 Registrar Accreditation Agreement", Jun 2013, 865 . 868 Authors' Addresses 870 Gustavo Lozano 871 ICANN 872 12025 Waterfront Drive, Suite 300 873 Los Angeles 90292 874 US 876 Phone: +1.3103015800 877 Email: gustavo.lozano@icann.org 879 Eduardo Alvarez 880 ICANN 881 12025 Waterfront Drive, Suite 300 882 Los Angeles 90292 883 US 885 Phone: +1.3103015800 886 Email: eduardo.alvarez@icann.org