idnits 2.17.1 draft-icann-registrar-interfaces-03.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 (September 23, 2019) is 1675 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'RFC3688' is defined on line 852, but no explicit reference was found in the text == Outdated reference: A later version (-21) exists of draft-lozano-icann-registry-interfaces-10 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: March 26, 2020 September 23, 2019 7 ICANN Registrar Interfaces 8 draft-icann-registrar-interfaces-03 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 March 26, 2020. 34 Copyright Notice 36 Copyright (c) 2019 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 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 22 73 8.1. Normative References . . . . . . . . . . . . . . . . . . 22 74 8.2. Informative References . . . . . . . . . . . . . . . . . 23 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 77 1. Introduction 79 This document describes the technical details of the interfaces 80 provided by the Internet Corporation for Assigned Names and Numbers 81 (ICANN) to Registrars and Data Escrow Agents in order to fulfill the 82 data escrow requirements of the Registrar Accreditation Agreement 83 [ICANN-RAA-2013] and the Registrar Data Escrow Specifications 84 [ICANN-RDE-SPEC]. 86 1.1. Terminology 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in RFC 2119 [RFC2119]. 92 XML is case sensitive. Unless stated otherwise, XML specifications 93 and examples provided in this document MUST be interpreted in the 94 character case presented in order to develop a conforming 95 implementation. 97 1.2. Date and Time 99 Numerous fields indicate "date and time", such as the creation and 100 receipt dates for data escrow deposits. These fields SHALL contain 101 timestamps indicating the date and time in UTC as specified in 102 [RFC3339], with no offset from the zero meridian. 104 1.3. Common elements used in this specification 106 Common elements used in this specification are explained in this 107 section. 109 o : The base URL used in the reporting interfaces examples 110 must be replaced with the URL indicated by ICANN. 112 o This document uses the term of "Differential" deposit as defined 113 in the Registry Data Escrow Specification (see, 114 [I-D.arias-noguchi-registry-data-escrow]), while the Registrar 115 Data Escrow Specifications [ICANN-RDE-SPEC] refers to the same 116 concept as "Incremental" deposit. 118 2. Interfaces for Registrar Data Escrow Notifications 120 This section describes the interfaces provided by ICANN to the 121 Registrars and Data Escrow Agents in order to fulfill their reporting 122 requirements related to Registrar Data Escrow Specifications 123 [ICANN-RDE-SPEC]. 125 2.1. Registrar Reporting 127 To notify that a data escrow deposit has been submitted to a Data 128 Escrow Agent, the ICANN-accredited Registrar sends a 129 object (see, 130 [I-D.lozano-icann-registry-interfaces]) to ICANN. 132 The following considerations apply for a object 133 corresponding to a data escrow deposit for a Registrar repository: 135 o The element in the object 136 (see, [I-D.arias-noguchi-dnrd-objects-mapping]) MUST be present 137 and have a value corresponding to the IANA Registrar ID assigned 138 by ICANN. 140 o A element MUST be included with the 141 corresponding "rcdn" attribute in the object to 142 indicate the total domains in the Registrar repository for each 143 Registry Class Domain Name (e.g. example) with at least one domain 144 name allocation at a specific point in time (watermark), 145 regardless of the type of deposit: full or differential. 147 * If the "https://www.icann.org/en/system/files/files/rde-specs- 148 09nov07-en.pdf" specification is being used as the 149 , then the "uri" attribute in the 150 elements for domain names MUST have a value 151 of "urn:ietf:params:xml:ns:rdeDomain-1.0". 153 o To indicate that a Registrar repository has no domain names, one 154 element MUST be included with the "uri" 155 attribute value of "urn:ietf:params:xml:ns:rdeDomain-1.0", no 156 "rcdn" attribute, and a value of 0 (zero). 158 The object for each deposit successfully sent to 159 the Data Escrow Agent is sent using the PUT HTTP verb in the 160 interface provided by ICANN at: 162 /report/registrar-escrow-report// 164 Where: 166 * MUST be substituted with the IANA Registrar ID 167 assigned by ICANN for which the report is being provided. 169 * MUST be substituted with the identifier assigned to this 170 report, which MUST be the same as the "id" attribute from the 171 . 173 Note: The interface supports overwriting the information of a 174 particular report to support asynchronous interfaces between 175 Registrars and Data Escrow Agents. 177 Example of a object for a data escrow deposit 178 corresponding to a Registrar repository: 180 181 184 20170801001 185 1 186 187 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 188 189 0 190 2017-08-01T00:15:00.0Z 191 FULL 192 2017-08-01T00:00:00Z 193 194 9999 195 2 197 8 199 3 201 202 204 Example of a object for an empty data escrow 205 deposit corresponding to a Registrar repository: 207 208 211 20170801001 212 1 213 214 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 215 216 0 217 2017-08-01T00:15:00.0Z 218 FULL 219 2017-08-01T00:00:00Z 220 221 9999 222 223 0 224 225 227 2.2. Data Escrow Agent Reporting 229 The Registrar Data Escrow Specification requires that Registrar Data 230 Escrow Agents deliver to ICANN a notification every time a 231 successfully processed deposit is received from the Registrar 232 regardless of the final status of the verification process, in 233 addition to a failure notification if a scheduled deposit is not 234 received from a Registrar. 236 In order to satisfy this requirement, the Data Escrow Agent sends to 237 ICANN a object as defined in Section 2 238 of [I-D.lozano-icann-registry-interfaces], to ICANN using the POST 239 HTTP verb in the interface provided by ICANN at: 241 /report/registrar-escrow-agent-notification/ 243 Where: 245 * MUST be substituted with the IANA Registrar ID 246 assigned by ICANN for which the notification is being provided. 248 A with DRFN (Deposit Receipt Failure 249 Notice) status is used to notify that a data escrow deposit has not 250 been processed for verification for a past date where a deposit was 251 scheduled to be received from the Registrar. 253 In addition to the considerations listed in Section 2.1 for the 254 object of the notification, if the data escrow 255 deposit does not include an , a unique value MUST be generated by 256 the Data Escrow Agent to reference the deposit and it MUST be 257 provided in the element. 259 In the case of a with DVFN (Deposit 260 Verification Failure Notice) status, the 261 element MUST be present and include a object for each 262 deposit verification error condition and specify in the corresponding 263 "domainCount" attribute the number of domain names with such error 264 conditions. 266 Note: an error condition may be present several times in the the same 267 domain escrow record (e.g. the administrative, technical and billing 268 contact contain invalid email syntax). In this case only one domain 269 name is affected by the error condition, therefore the "domainCount" 270 attribute value must be increased by one in the corresponding 271 object. 273 The following table defines the result codes and messages that a Data 274 Escrow Agent could use to report verification issues found in a 275 Registrar data escrow deposit. When using result codes 2102, 2103, 276 2104, 2105, 2106, 2107, 2108, 2109, or 2110, the "domainCount" 277 attribute MUST be present. 279 +-----------+-------------------------------------------------------+ 280 | Result | Message | 281 | Code | | 282 +-----------+-------------------------------------------------------+ 283 | 2001 | No corresponding hash file found for deposit file. | 284 | 2002 | Hash does not match corresponding deposit file. | 285 | 2003 | Invalid hash file format. | 286 | 2004 | Data escrow deposit PGP signature verification error. | 287 | 2005 | Archive includes unrecognized files. | 288 | 2006 | Invalid encoding for data escrow deposit file. | 289 | 2007 | Data escrow deposit file size exceeds maximum allowed | 290 | | size. | 291 | 2008 | Data escrow deposit file exceeds maximum allowed | 292 | | number of lines. | 293 | 2101 | Unrecognized data escrow deposit file CSV header. | 294 | 2102 | Escrow Record structure does not conform with CSV | 295 | | header definition. | 296 | 2103 | Escrow Record found missing data in required | 297 | | field(s). | 298 | 2104 | Invalid domain name syntax in Escrow Record. | 299 | 2105 | Invalid email syntax in Escrow Record. | 300 | 2106 | Invalid hostname syntax in Escrow Record. | 301 | 2107 | Invalid date syntax in Escrow Record. | 302 | 2108 | Invalid phone syntax in Escrow Record. | 303 | 2109 | Duplicate domain or handle Escrow Record found in | 304 | | deposit. | 305 | 2110 | Handle reference by Escrow Record not found. | 306 | 2201 | "Full" data escrow deposit expected but received | 307 | | "Differential" instead. | 308 | 2202 | Data Escrow deposit date is in the future. | 309 | 2203 | A data escrow deposit has been already successfully | 310 | | verified for that date. | 311 +-----------+-------------------------------------------------------+ 313 Registrar Data Escrow Deposit Verification Result Codes 315 Example of a object of a Data Escrow 316 Agent notification corresponding to a Registrar Data Escrow deposit 317 that was not received or could not be processed for verification: 319 320 322 Escrow Agent Inc. 323 1 324 2017-06-17 325 DRFN 326 2017-06-10 327 328 330 Example of a object of a Data Escrow 331 Agent notification corresponding to a Registrar repository Data 332 Escrow deposit that has passed the verification process: 334 335 339 Escrow Agent Inc. 340 1 341 342 2017-06-17 343 DVPN 344 345 2017-06-17T03:15:00.0Z 346 347 2017-06-17T05:15:00.0Z 348 349 2017-06-17 350 351 20170617001 352 1 353 354 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 355 356 0 357 2017-06-17T00:15:00.0Z 358 FULL 359 2017-06-17T00:00:00Z 360 361 9999 362 2 364 6 366 1 368 369 370 372 Example of a object of a Data Escrow 373 Agent notification corresponding to a Registrar repository Data 374 Escrow deposit that has failed the verification process: 376 377 382 Escrow Agent Inc. 383 1 384 2017-06-17 385 DVFN 386 387 388 389 Invalid domain name syntax in Escrow Record. 390 391 392 393 394 Handle reference by Escrow Record not found. 395 396 397 398 399 2017-06-17T03:15:00.0Z 400 401 402 2017-06-17T05:15:00.0Z 403 404 405 2017-06-14 406 407 408 20170617001 409 1 410 411 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 412 413 0 414 2017-06-17T00:15:00.0Z 415 FULL 416 2017-06-17T00:00:00Z 417 418 9999 419 2 421 8 423 3 425 426 427 429 3. Technical details of the interfaces 431 Content-type value in the HTTP header: 433 o The client MUST set "text/xml" in the HTTP header Content-type 434 when using the Data Escrow Agent Reporting and Registrar Reporting 435 interfaces described in Section 2. 437 After successfully receiving and processing an input, the interfaces 438 return any of the HTTP status codes described in Section 4 of 439 [I-D.lozano-icann-registry-interfaces]. 441 The following sections provide the IIRDEA Result Codes that can be 442 expected in the object from each interface: 444 3.1. Registrar Reporting 446 The following table lists the result codes of the interface: 448 +---------+---------------------------------------------------------+ 449 | Result | Message | 450 | Code | | 451 +---------+---------------------------------------------------------+ 452 | 1000 | No ERRORs were found and the report has been accepted | 453 | | by ICANN. | 454 | 2001 | The request did not validate against the schema. | 455 | 2004 | Report for a date in the future. The and | 456 | | date should not be in the future. | 457 | 2005 | Version is not supported. | 458 | 2006 | The in the element and the in the | 459 | | URL path do not match. | 460 | 2301 | Interface is disabled for this Registrar. | 461 | 2302 | The and date should not be before | 462 | | the creation date of the Registrar in the system. | 463 | 2303 | The in the
and the in | 464 | | the URL path do not match. | 465 | 2304 | Report regarding an differential deposit received when | 466 | | a full deposit was expected (). | 467 | 2305 | attribute missing in count element provided in | 468 | | the
. | 469 | 2306 | Multiple count elements with the same and | 470 | | attribute values provided in the
. | 471 | 2307 | Missing required element in the
. | 472 | 2312 | An invalid NR-LDH label or A-label was found or the | 473 | | domain name syntax is invalid in the attribute. | 474 | 2313 | INCR is not supported. | 475 +---------+---------------------------------------------------------+ 477 Registrar Data Escrow Reporting Result Codes 479 3.2. Data Escrow Agent Reporting 481 The following table lists the result codes of the interface: 483 +--------+----------------------------------------------------------+ 484 | Result | Message | 485 | Code | | 486 +--------+----------------------------------------------------------+ 487 | 1000 | No ERRORs were found and the notification has been | 488 | | accepted by ICANN. | 489 | 2001 | The request did not validate against the schema. | 490 | 2002 | A DVPN notification exists for that date (). | 491 | 2004 | Notification for a date in the future. The , | 492 | | , and date should | 493 | | not be in the future. | 494 | 2005 | Version is not supported. | 495 | 2201 | The and in the notification do not | 496 | | match. | 497 | 2203 | A Deposit Verification Pass Notice (DVPN) notification | 498 | | was received, but the Domain Name count is missing in | 499 | | the
. | 500 | 2204 | The notification for the report "id" already exists. | 501 | 2207 | A DVPN or DVFN was received, but the element is | 502 | | missing in the notification. | 503 | 2208 | A DRFN was received, but a element exists in | 504 | | the notification. | 505 | 2209 | and elements must not be present in a | 506 | | DRFN. | 507 | 2301 | Interface is disabled for this Registrar. | 508 | 2302 | The and and date should | 509 | | not be before the creation date of the Registrar in the | 510 | | system. | 511 | 2303 | The in the
and the in | 512 | | the URL path do not match. | 513 | 2304 | Notification regarding an differential deposit received | 514 | | when a full deposit was expected (). | 515 | 2305 | attribute missing in count element provided in | 516 | | the
. | 517 | 2306 | Multiple count elements with the same and | 518 | | attribute values provided in the
. | 519 | 2307 | Missing required element in the
. | 520 | 2309 | A DVFN was received, but the element is | 521 | | missing in the notification. | 522 | 2310 | The specified result code in the element | 523 | | requires the "domainCount" attribute to be present. | 524 | 2311 | Unrecognized value in the "code" attribute of the | 525 | | element. | 526 | 2312 | An invalid NR-LDH label or A-label was found or the | 527 | | domain name syntax is invalid in the attribute. | 528 | 2313 | INCR is not supported. | 529 +--------+----------------------------------------------------------+ 531 Data Escrow Agent Reporting Result Codes 533 4. Monitoring Registrar reporting 535 Registrars MAY monitor the status of the data escrow reporting 536 notifications requirement using the following interfaces that support 537 the GET HTTP verb. 539 4.1. Monitoring the reporting status of a Registrar 541 Registrars MAY monitor the general reporting status and obtain a list 542 of any outstanding issues using the following interface: 544 /info/status/registrar/ 546 Where: 548 * MUST be substituted with the IANA ID assigned by 549 ICANN to the Registrar being queried. 551 This interface provides a element as defined 552 in Section 2 of [I-D.lozano-icann-registry-interfaces] that uses the 553 element and includes the following 554 values: 556 o "Registrar_Escrow_Report" : For Registrar Data Escrow Reporting as 557 defined in Section 2.1. The "date" attribute for any reporting 558 issue is provided in "YYYY-MM-DD" format. 560 o "DEA_Notification" : For Data Escrow Agent Notifications as 561 defined in Section 2.2. The "date" attribute for any reporting 562 issue is provided in "YYYY-MM-DD" format. 564 Example of response for a Registrar status check with no reporting 565 issues: 567 HTTP/1.1 200 OK 568 Content-Type: application/xml 569 Content-Length: 1125 571 572 575 9999 576 577 2017-06-10T12:00:30.101Z 578 Daily 579 2017-10-15 580 581 582 Registrar_Escrow_Report 583 false 584 ok 585 586 587 DEA_Notification 588 true 589 ok 590 591 592 593 2017-10-20T02:22:14.148Z 594 596 Example of response for a Registrar status check with reporting 597 issues: 599 HTTP/1.1 200 OK 600 Content-Type: application/xml 601 Content-Length: 1604 603 604 607 9999 608 609 2017-06-10T12:00:30.101Z 610 Daily 611 2017-10-08 612 613 614 Registrar_Escrow_Report 615 true 616 ok 617 618 619 DEA_Notification 620 true 621 unsatisfactory 622 623 625 627 629 631 632 633 634 635 2017-10-20T02:22:14.148Z 636 638 4.2. Monitoring Registrar Data Escrow Reports 640 Registrars MAY monitor the status of their Data Escrow reports using 641 the following interface: 643 /info/report/registrar-escrow-report// 645 Where: 647 * MUST be substituted with the IANA ID assigned by 648 ICANN to the Registrar being queried. 650 * MUST be substituted with the date being queried in 651 "YYYY-MM-DD" format. For example: 2017-08-01 653 Possible results are: 655 o The interface provides a HTTP/200 status code with a 656 element in the response content as defined in 657 Section 2 of [I-D.lozano-icann-registry-interfaces], listing each 658 successfully received with watermark value that 659 matches the queried date. 661 Example of response for a Registrar Data Escrow Reporting status 662 check: 664 HTTP/1.1 200 OK 665 Content-Type: application/xml 666 Content-Length: 1194 668 669 673 674 2017-10-13T00:30:13.741Z 675 676 20171013001 677 1 678 679 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 680 681 0 682 2017-10-13T00:01:11.000Z 683 FULL 684 2017-10-13T00:00:00.00Z 685 686 9999 687 10 689 1 691 692 693 694 696 4.3. Monitoring Registrar Data Escrow Agent Notifications 698 Registrars and Data Escrow Agents MAY monitor the status of Data 699 Escrow Agent Notifications using the following interface: 701 /info/report/registrar-escrow-agent-notification// 704 Where: 706 * MUST be substituted with the IANA ID assigned by 707 ICANN to the Registrar being queried. 709 * MUST be substituted with the date being queried in 710 "YYYY-MM-DD" format. For example: 2017-08-01 712 Possible results are: 714 o The interface provides a HTTP/200 status code with a 715 element in the response content 716 as defined in Section 2 of [I-D.lozano-icann-registry-interfaces], 717 listing each successfully received 718 with a watermark value that matches the queried date. 720 Example of a response of a Registrar Data Escrow Agent Notification 721 status check for a date with 2 received notifications: 723 HTTP/1.1 200 OK 724 Content-Type: application/xml 725 Content-Length: 2578 727 728 734 735 736 2017-10-17T23:59:59.0Z 737 738 739 Escrow Agent Inc. 740 1 741 2017-10-17 742 DRFN 743 744 2017-10-14 745 746 747 748 749 2017-10-18T06:00:00.0Z 750 751 752 Escrow Agent Inc. 753 1 754 2017-10-17 755 DVPN 756 757 2017-10-18T03:15:00.0Z 758 759 2017-10-18T05:15:00.0Z 761 762 2017-10-17 763 764 20171017001 765 1 766 767 https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf 768 769 0 770 2017-10-17T00:15:00.0Z 771 FULL 772 2017-10-17T00:00:00Z 773 774 9999 775 10 777 1 779 780 781 782 783 785 5. IANA Considerations 787 TODO 789 6. Security Considerations 791 TODO 793 7. Change History 795 [[RFC Editor: Please remove this section.]] 797 7.1. Version 00 799 Initial version. 801 7.2. Version 01 803 o Added clarifications, list of result codes that require the 804 "domainCount" attribute to be present, and additional examples of 805 objects in Section 2.2. 807 o Removed HTTP/404 from the possible results of interfaces to 808 monitor data escrow notifications and registrar reports. 810 7.3. Version 02 812 1. Ping update. 814 7.4. Version 03 816 1. Ping update. 818 8. References 820 8.1. Normative References 822 [I-D.arias-noguchi-dnrd-objects-mapping] 823 Lozano, G., Gould, J., and C. Thippeswamy, "Domain Name 824 Registration Data (DNRD) Objects Mapping", draft-arias- 825 noguchi-dnrd-objects-mapping-10 (work in progress), 826 January 2019. 828 [I-D.arias-noguchi-registry-data-escrow] 829 Lozano, G., "Registry Data Escrow Specification", draft- 830 arias-noguchi-registry-data-escrow-11 (work in progress), 831 January 2019. 833 [I-D.lozano-icann-registry-interfaces] 834 Lozano, G. and E. Alvarez, "ICANN Registry Interfaces", 835 draft-lozano-icann-registry-interfaces-10 (work in 836 progress), March 2019. 838 [ICANN-RDE-SPEC] 839 ICANN, "Registrar Data Escrow specifications", Nov 2007, 840 . 843 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 844 Requirement Levels", BCP 14, RFC 2119, 845 DOI 10.17487/RFC2119, March 1997, 846 . 848 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 849 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 850 . 852 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 853 DOI 10.17487/RFC3688, January 2004, 854 . 856 8.2. Informative References 858 [ICANN-RAA-2013] 859 ICANN, "2013 Registrar Accreditation Agreement", Jun 2013, 860 . 863 Authors' Addresses 865 Gustavo Lozano 866 ICANN 867 12025 Waterfront Drive, Suite 300 868 Los Angeles 90292 869 US 871 Phone: +1.3103015800 872 Email: gustavo.lozano@icann.org 874 Eduardo Alvarez 875 ICANN 876 12025 Waterfront Drive, Suite 300 877 Los Angeles 90292 878 US 880 Phone: +1.3103015800 881 Email: eduardo.alvarez@icann.org