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