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