idnits 2.17.1 draft-ietf-regext-epp-registry-maintenance-14.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 (April 19, 2021) is 1103 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'W3C-HTML5' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force (IETF) T. Sattler 2 Internet-Draft 3 Intended status: Standards Track R. Carney 4 Expires: October 14, 2021 J. Kolker 5 GoDaddy Inc. 6 April 19, 2021 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-14 12 Abstract 13 This document describes an Extensible Provision Protocol (EPP) 14 mapping for registry's maintenance notifications. 16 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at https://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress". 30 This Internet-Draft will expire on October 14, 2021. 32 Copyright Notice 33 Copyright (c) 2021 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (https://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 47 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 48 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 49 2. Migrating to Newer Versions of This Extension . . . . . . . . 3 50 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 51 3.1. Internationalized Domain Names . . . . . . . . . . . . . 4 52 3.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 4 53 3.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4 54 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 55 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 56 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 57 4.1.2. EPP Command . . . . . . . . . . . . . . . 7 58 4.1.3. EPP Command . . . . . . . . . . . . . . . . . 7 59 4.1.3.1. Info Maintenance Item . . . . . . . . . . . . . . . 7 60 4.1.3.2. Info Maintenance List . . . . . . . . . . . . . . . 8 61 4.1.4. EPP Command . . . . . . . . . . . . . . . . . 10 62 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 12 63 4.2.1. EPP Command . . . . . . . . . . . . . . . . 12 64 4.2.2. EPP Command . . . . . . . . . . . . . . . . 12 65 4.2.3. EPP Command . . . . . . . . . . . . . . . . . 12 66 4.2.4. EPP Command . . . . . . . . . . . . . . . 12 67 4.2.5. EPP Command . . . . . . . . . . . . . . . . 12 68 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12 69 5.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 71 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 72 6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 73 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 74 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 75 8.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 18 76 8.2. TANGO Registry Services . . . . . . . . . . . . . . . . . 18 77 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 78 9.1. Normative References . . . . . . . . . . . . . . . . . . 19 79 9.2. Informative References . . . . . . . . . . . . . . . . . 20 80 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 20 81 A.1. Change from draft-sattler-epp-poll-maintenance-response to 82 draft-sattler-epp-registry-maintenance . . . . . . . . . 20 83 A.2. Change from draft-sattler-epp-registry-maintenance to 84 draft-ietf-regext-epp-registry-maintenance . . . . . . . 20 85 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 21 86 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 21 87 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 21 88 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 21 89 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 21 90 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 21 91 A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 21 92 A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 21 93 A.11. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 21 94 A.12. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 21 95 A.13. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 22 96 A.14. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 22 97 A.15. Change from 12 to 13 . . . . . . . . . . . . . . . . . . 22 98 A.16. Change from 13 to 14 . . . . . . . . . . . . . . . . . . 22 99 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22 100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 102 1. Introduction 104 Registries usually conduct maintenances and inform registrars in 105 different ways. Given the DNS namespace expansion, it is now 106 desirable to provide methods for EPP servers to notify EPP clients 107 and EPP clients can query EPP servers for upcoming maintenances. 109 This document describes an extension mapping for version 1.0 of the 110 Extensible Provision Protocol [RFC5730]. This mapping provides a 111 mechanism by which EPP servers may notify and EPP clients to query 112 upcoming maintenances. 114 1.1. Terminology and Definitions 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 118 "OPTIONAL" in this document are to be interpreted as described in 119 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 120 capitals, as shown here. 122 XML is case sensitive. Unless stated otherwise, XML specifications 123 moreover, examples provided in this document MUST be interpreted in 124 the character case presented to develop a conforming implementation. 126 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 127 maintenance-1.0". The XML namespace prefix "maint" is used, but 128 implementations MUST NOT depend on it and instead employ a proper 129 namespace-aware XML parser and serializer to interpret and output 130 the XML documents. 132 In examples, "C:" represents lines sent by a protocol client and 133 "S:" represents lines returned by a protocol server. Indentation and 134 white space in examples are provided only to illustrate element 135 relationships and are not a REQUIRED feature of this protocol. 137 2. Migrating to Newer Versions of This Extension 139 Servers that implement this extension SHOULD provide a way for 140 clients to progressively update their implementations when a new 141 version of the extension is deployed. 143 Servers SHOULD (for a temporary migration period up to server policy) 144 provide support for older versions of the extension in parallel to 145 the newest version and allow clients to execute their preferred 146 version of the command based on the maintenance 147 elements of the server . The version of the maintenance 148 response MUST match the version of the maintenance 149 command executed by the server. 151 Servers MUST return a Registry Maintenance Notification poll message 152 matching the newest version of the maintenance extension, based on an 153 intersection of the maintenance elements in the server 154 and the client command. If the intersection of 155 the maintenance elements of the server and the 156 client command results in an empty set, the server MUST 157 return the newest version of the Registry Maintenance Notification 158 poll message supported by the server based on section 6 "Usage with 159 Poll Message EPP Response" of 160 [draft-ietf-regext-unhandled-namespaces]. 162 3. Object Attributes 164 3.1. Internationalized Domain Names 166 Names of affected hosts MUST be provided as an A-label according to 167 [RFC5891]. 169 3.2. Dates and Times 171 All dates and times attribute values MUST be expressed in Universal 172 Coordinated Time (UTC) using the Gregorian calendar. The extended 173 date-time form using upper case "T" and "Z" characters defined in ISO 174 8601 [RFC3339] MUST be used to represent date-time values. 176 3.3. Maintenance Elements 178 The element describes a single registry maintenance 179 event during a specific period. This element is used in a maintenance 180 item EPP response and message. 182 183 The server unique identifier for the maintenance with the OPTIONAL 184 "name" attribute that includes a human-readable name of the 185 maintenance. The server unique identifier SHALL NOT be changed if 186 the maintenance is updated or deleted. When the "name" attribute 187 is set, the OPTIONAL "lang" attribute MAY be present to identify 188 the language if the negotiated value is something other than the 189 default value of "en" (English). 191 192 Zero or more OPTIONAL types of the maintenance that has the 193 possible set of values defined by server policy, such as 194 "Routine Maintenance", "Software Update", "Software Upgrade", or 195 "Extended Outage". 197 198 The OPTIONAL element for a Registry Maintenance 199 Notification poll message; values MUST either be "create", 200 "update", "delete", "courtesy", or "end". For the "create" and 201 "update" types, the server includes the state of the maintenance 202 after the create or update. For the "delete" type, the server 203 includes the state of the maintenance prior to the delete. The 204 "courtesy" provides a reminder of a maintenance and the "end" 205 provides a notification of the end of the maintenance without 206 updating the maintenance object and includes the latest state of 207 the maintenance. This element MUST be present only for poll 208 messages. 210 211 One or more elements that are affected by the 212 maintenance. 214 215 The element contains the following child 216 elements: 218 219 The name of the affected system, such as "EPP", "WHOIS", 220 "DNS", "Portal", etc. 222 223 The OPTIONAL affected maintained system's hostname, which 224 SHALL be an A-label according to [RFC5891]. 226 227 The impact level; the values MUST either be "full", 228 "partial", or "none". If access is intermittently 229 unavailable, it is "partial". If access is completely 230 unavailable, it is "full". If access is not affected, it is 231 "none". 233 234 The type of the affected system; the attribute "type" is 235 REQUIRED and MUST either be "production", "ote", "staging", 236 "dev" or "custom". For extensibility, the 237 element includes the OPTIONAL "name" attribute that can define 238 the name of the custom environment when the 239 element "type" attribute has the "custom" value. For example, 240 for the custom "marketing" environment, the 241 element should be: 242 244 245 The date and time of the start of the maintenance. 247 248 The date and time of the end of the maintenance. The 249 element MUST be equal to or greater than the 250 element. 252 253 The reason behind the maintenance; the values MUST either be 254 "planned" or "emergency". 256 257 The OPTIONAL URI to detailed maintenance description, formatted 258 according to [RFC8820]. 260 261 Zero or more OPTIONAL free-form descriptions of the maintenance 262 without having to create and traverse an external resource 263 defined by the element. The OPTIONAL "lang" 264 attribute MAY be present to identify the language if the 265 negotiated value is something other then the default value of 266 "en" (English). The OPTIONAL "type" attribute MAY be present to 267 identify the format of the description. It MUST either be 268 "plain" for plain text or "html" HTML text that is defined in 269 [W3C-HTML5] and XML-escaped, with a default value of "plain". 271 272 The OPTIONAL element contains one or more 273 child elements. If the is not present, 274 the entire system is affected. 276 277 The affected top-level domain or registry zone, which SHALL 278 be an A-label according to [RFC5891]. 280 281 The OPTIONAL element contains the 282 following child elements: 284 285 The value SHALL be boolean and indicates if a client needs 286 to do something that is connection-related, such as a 287 reconnect. 289 290 The value SHALL be boolean and indicates if a client needs 291 to do something that is implementation-related, such as a 292 code change. 294 295 The date and time of the maintenance object creation. 297 298 The OPTIONAL date and time of the most recent maintenance 299 object modification. This element MUST NOT be present if the 300 maintenance object has never been modified. 302 4. EPP Command Mapping 304 A detailed description of the EPP syntax and semantics can be found 305 in the EPP core protocol specification [RFC5730]. The command 306 mappings described here are specifically for the use to notify of 307 Registry Maintenances and Registry Maintenance object mapping. 309 4.1. EPP Query Commands 311 EPP [RFC5730] provides three commands to retrieve object information: 312 to determine if an object is known to the server, to 313 retrieve detailed information associated with an object, and 314 to retrieve object transfer status information. 316 4.1.1. EPP Command 318 Available check semantics do not apply to maintenance objects, so 319 there is no mapping defined for the EPP command. 321 4.1.2. EPP Command 323 Transfer semantics do not apply to maintenance objects, so there is 324 no mapping defined for the EPP command. 326 4.1.3. EPP Command 328 EPP provides the command that is used to retrieve registry 329 maintenance information. In addition to the standard EPP command 330 elements, the command MUST contain a 331 element that identifies the maintenance namespace. 333 The element MUST contain a child element. It is either 334 the child element, described in Section 4.1.3.1, to query 335 for a specific maintenance item or the child element, 336 described in Section 4.1.3.2, to query all maintenance items. 338 4.1.3.1. Info Maintenance Item 340 The information on a specific maintenance item can be retrieved by 341 using the command with the element and the 342 child element, defined in Section 3.3. If the maintenance 343 identifier does not exist, the server MUST return an EPP error result 344 code of 2303 [RFC5730]. 346 Example to retrieve a specific maintenance item in an command. 348 C: 349 C: 350 C: 351 C: 352 C: 354 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 355 C: 356 C: 357 C: ABC-12345 358 C: 359 C: 361 When an command has been processed successfully, the EPP 362 element MUST contain a child element that 363 identifies the maintenance namespace. The element 364 contains the element defined in Section 3.3. 366 Example of returning a specific maintenance item in an 367 response. 369 S: 370 S: 371 S: 372 S: 373 S: Command completed successfully 374 S: 375 S: 376 S: 378 S: 379 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 380 S: 381 S: Routine Maintenance 382 S: 383 S: 384 S: EPP 385 S: epp.registry.example 386 S: 387 S: full 388 S: 389 S: 390 S: 391 S: 2021-12-30T06:00:00Z 392 S: 2021-12-30T14:25:57Z 393 S: planned 394 S: 395 S: https://www.registry.example/notice?123 396 S: 397 S: free-text 398 S: 399 S: Freitext 400 S: 401 S: 402 S: example 403 S: test 404 S: 405 S: 406 S: false 407 S: false 408 S: 409 S: 2021-09-08T22:10:00Z 410 S: 411 S: 412 S: 413 S: 414 S: ABC-12345 415 S: 54321-XYZ 416 S: 417 S: 418 S: 420 4.1.3.2. Info Maintenance List 422 The information for a list of maintenance items can be retrieved by 423 using the command with the element and the empty 424 child element. Server policy determines if previous 425 maintenances will be included in the list of maintenance items. 427 Example to retrieve the maintenance list in an command. 429 C: 430 C: 431 C: 432 C: 433 C: 435 C: 436 C: 437 C: 438 C: ABC-12345 439 C: 440 C: 442 When an command has been processed successfully, the EPP 443 element MUST contain a child element 444 that identifies the maintenance namespace. The 445 element contains the element with zero or more 446 child elements. The element 447 contains the following child elements: 449 450 The element defined in Section 3.3. 452 453 The element defined in Section 3.3. 455 456 The element defined in Section 3.3. 458 459 The element defined in Section 3.3. 461 462 The OPTIONAL element defined in Section 3.3. 464 Example of returning the maintenance list in an response. 466 S: 467 S: 468 S: 469 S: 470 S: Command completed successfully 471 S: 472 S: 473 S: 475 S: 476 S: 477 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 478 S: 479 S: 2021-12-30T06:00:00Z 480 S: 2021-12-30T07:00:00Z 481 S: 2021-09-08T22:10:00Z 482 S: 483 S: 484 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 485 S: 486 S: 2021-12-15T04:30:00Z 487 S: 2021-12-15T05:30:00Z 488 S: 2021-09-08T22:11:00Z 489 S: 2021-10-17T15:00:00Z 490 S: 491 S: 492 S: 493 S: 494 S: 495 S: ABC-12345 496 S: 54321-XYZ 497 S: 498 S: 499 S: 501 4.1.4. EPP Command 503 The EPP command and response is defined in Section 2.9.2.3 of 504 [RFC5730]. The Registry Maintenance Notification is included in the 505 EPP response of [RFC5730]. 507 For the Registry Maintenance Notification, there are five types of 508 poll messages, defined by the element in Section 509 3.3. A poll message applies when a maintenance is created, updated or 510 deleted. A courtesy poll message can be sent as a reminder of 511 an impending maintenance. An end poll message can be sent when the 512 maintenance is completed. In the case of a Registry Maintenance 513 specific message, a element will be included within 514 the element of the standard response. The 515 element contains the element defined in 516 Section 3.3. 518 Example command: 520 C: 521 C: 522 C: 523 C: 524 C: ABC-12345 525 C: 526 C: 527 Example response: 529 S: 530 S: 531 S: 532 S: 533 S: Command completed successfully; ack to dequeue 534 S: 535 S: 536 S: 2021-10-08T22:10:00Z 537 S: Registry Maintenance Notification 538 S: 539 S: 540 S: 542 S: 543 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 544 S: create 545 S: 546 S: 547 S: EPP 548 S: epp.registry.example 549 S: 550 S: full 551 S: 552 S: 553 S: 554 S: 2021-12-30T06:00:00Z 555 S: 2021-12-30T14:25:57Z 556 S: planned 557 S: 558 S: https://www.registry.example/notice?123 559 S: 560 S: 561 S: example 562 S: test 563 S: 564 S: 565 S: false 566 S: false 567 S: 568 S: 2021-10-08T22:10:00Z 569 S: 570 S: 571 S: 572 S: 573 S: ABC-12345 574 S: 54321-XYZ 575 S: 576 S: 577 S: 579 4.2. EPP Transform Commands 581 EPP provides five commands to transform objects: to create 582 an instance of an object, to delete an instance of an 583 object, to extend the validity period of an object, 584 to manage object sponsorship changes, and to 585 change information associated with an object. 587 4.2.1. EPP Command 589 Create semantics do not apply to maintenance objects, so there is no 590 mapping defined for the EPP command. 592 4.2.2. EPP Command 594 Delete semantics do not apply to maintenance objects, so there is no 595 mapping defined for the EPP command. 597 4.2.3. EPP Command 599 Renew semantics do not apply to maintenance objects, so there is no 600 mapping defined for the EPP command. 602 4.2.4. EPP Command 604 Transfer semantics do not apply to maintenance objects, so there is 605 no mapping defined for the EPP command. 607 4.2.5. EPP Command 609 Update semantics do not apply to maintenance objects, so there is no 610 mapping defined for the EPP command. 612 5. Formal Syntax 614 The EPP Registry Maintenance schema is presented here. 615 The formal syntax presented here is a complete schema representation 616 of the object mapping suitable for automated validation of EPP XML 617 instances. The and tags are not part of 618 the schema; they are used to note the beginning and end of the 619 schema for URI registration purposes. 621 5.1. Registry Maintenance EPP Mapping Schema 623 624 625 633 636 637 638 639 640 Extensible Provisioning Protocol v1.0 641 Registry Maintenance Mapping Schema. 642 643 644 647 648 651 652 653 654 655 656 657 658 659 662 663 664 665 666 667 668 669 670 673 674 677 678 679 680 681 682 683 686 687 688 690 691 692 695 696 697 698 699 700 701 702 703 704 707 708 709 710 712 713 714 715 716 717 718 719 721 722 724 725 726 727 728 731 732 733 735 736 737 740 741 742 743 744 745 746 747 748 749 752 753 754 755 756 757 758 759 762 763 764 765 766 768 769 770 771 774 775 776 777 778 779 780 783 784 785 786 787 788 789 790 793 794 795 796 797 798 799 800 803 804 805 806 807 808 809 810 811 812 815 816 817 818 819 820 821 822 823 826 827 828 829 830 831 832 835 836 837 839 840 841 844 845 846 847 848 849 850 853 854 856 6. IANA Considerations 858 6.1. XML Namespace 860 This document uses URNs to describe XML namespaces and XML schemas 861 conforming to a registry mechanism defined in [RFC3688]. 863 Registration request for the maintenance namespace: 865 URI: urn:ietf:params:xml:ns:epp:maintenance-1.0 867 Registrant Contact: IESG 869 XML: None. Namespace URIs do not represent an XML specification. 871 Registration request for the maintenance schema: 873 URI: urn:ietf:params:xml:schema:maintenance-1.0 875 Registrant Contact: IESG 877 XML: See the "Formal Syntax" section of this document. 879 6.2. EPP Extension Registry 881 The following registration of the EPP Extension Registry, described 882 in [RFC7451], is requested: 884 Name of Extension: Registry Maintenance Notifications for the 885 Extensible Provisioning Protocol (EPP) 886 Document status: Standards Track 888 Reference: (insert the reference to RFC version of this document) 890 Registrant Name and Email Address: IESG 892 TLDs: Any 894 IPR Disclosure: None 896 Status: Active 898 Notes: None 900 7. Security Considerations 902 A server MUST only provide maintenance information for clients that 903 are authorized. If a client queries for a maintenance identifier, per 904 Section 4.1.3.1 "Info Maintenance Item", that it is not authorized to 905 access, the server MUST return an EPP error result code of 2201 906 [RFC5730]. The list of top-level domains or registry zones returned 907 in the "Info Maintenance Item" response SHOULD be filtered based on 908 the top-level domains or registry zones the client is authorized. 909 Authorization of poll messages is done at the time of poll message 910 insertion and not at the time of poll message consumption. 912 8. Implementation Status 914 Note to RFC Editor: Please remove this section and the reference to 915 [RFC7942] before publication. 917 This section records the status of known implementations of the 918 protocol defined by this specification at the time of posting of this 919 Internet-Draft, and is based on a proposal described in [RFC7942]. 920 The description of implementations in this section is intended to 921 assist the IETF in its decision processes in progressing drafts to 922 RFCs. Please note that the listing of any individual implementation 923 here does not imply endorsement by the IETF. Furthermore, no effort 924 has been spent to verify the information presented here that was 925 supplied by IETF contributors. This is not intended as, and must not 926 be construed to be, a catalog of available implementations or their 927 features. Readers are advised to note that other implementations may 928 exist. 930 According to [RFC7942], "this will allow reviewers and working groups 931 to assign due consideration to documents that have the benefit of 932 running code, which may serve as evidence of valuable experimentation 933 and feedback that have made the implemented protocols more mature. It 934 is up to the individual working groups to use this information as 935 they see fit". 937 8.1. GoDaddy Registry 939 Organization: GoDaddy Registry 940 Name: GoDaddy Registry 942 Description: GoDaddy Registry provides maintenance notifications to 943 their registrars. 945 Level of maturity: Production 947 Coverage: All aspects of the protocol according to the draft version 948 2 are implemented with further updates to come. 950 Licensing: Proprietary 952 Contact: quoc@registry.godaddy 954 URL: https://registry.godaddy 956 8.2. TANGO Registry Services 958 Name: TANGO Registry Services 960 Description: TANGO Registry Services provides maintenance 961 notifications to their registrars. 963 Level of maturity: Beta 965 Coverage: All aspects of the protocol according to the draft version 966 12 are implemented with further updates to come. 968 Licensing: Proprietary 970 Contact: Michael.Bauland@knipp.de 972 URL: https://tango-rs.com 974 9. References 976 9.1. Normative References 978 [I.D.draft-ietf-regext-unhandled-namespaces] 979 Gould, J. and Casanova, M., "Extensible Provisioning 980 Protocol (EPP) Unhandled Namespaces", 981 (work in progress), February 2021. 984 [W3C-HTML5] Hickson, I., Berjon, R., Faulkner, S., Leithead, T., 985 Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", 986 W3C Recommendation REC-html5-20141028, October 2014, 987 . 989 Latest version available at . 991 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 992 Requirement Levels", BCP 14, RFC 2119, 993 DOI 10.17487/RFC2119, March 1997, 994 . 996 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 997 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 998 . 1000 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1001 DOI 10.17487/RFC3688, January 2004, 1002 . 1004 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1005 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1006 . 1008 [RFC5891] Klensin, J., "Internationalized Domain Names in 1009 Applications (IDNA): Protocol", RFC 5891, 1010 DOI 10.17487/RFC5891, August 2010, 1011 . 1013 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1014 Code: The Implementation Status Section", BCP 205, 1015 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1016 . 1018 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1019 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1020 May 2017, . 1022 [RFC8820] Nottingham, M., "URI Design and Ownership", BCP 190, RFC 1023 8820, DOI 10.17487/RFC8820, June 2020, 1024 . 1026 9.2. Informative References 1028 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1029 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1030 February 2015, . 1032 Appendix A. Change History 1034 A.1. Change from draft-sattler-epp-poll-maintenance-response to 1035 draft-sattler-epp-registry-maintenance 1037 Updated to be EPP based instead of JSON document. 1039 A.2. Change from draft-sattler-epp-registry-maintenance to 1040 draft-ietf-regext-epp-registry-maintenance 1042 Adopted by the REGEXT working group. 1044 A.3. Change from 00 to 01 1046 Clarified maint:description and maint:environment. Changed 1047 maint:description from complexType to simpleType. Fixed typo. 1048 Added acknowledgment. 1050 A.4. Change from 01 to 02 1052 Update language from Domain Name Registry to Registry. Clarified 1053 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 1054 to contain hostName and hostAddr. Changed maint:tlds from MUST to 1055 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 1056 unique id. 1058 A.5. Change from 02 to 03 1060 Changed maint:connection from MUST to SHOULD. 1062 A.6. Change from 03 to 04 1064 A lot of clarifications and editoral changes. 1066 A.7. Change from 04 to 05 1068 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 1069 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 1070 Clarified for retrieving maintenance items and the list. 1072 A.8. Change from 05 to 06 1074 Changed dates in examples to more recent dates. Renamed Query 1075 Maintenance Item and List to Info Maintenance Item and List. Removed 1076 blackout in favor of full. Added GoDaddy Registry implementation. 1078 A.9. Change from 06 to 07 1080 Removed IP addresses for . Editoral changes. 1082 A.10. Change from 07 to 08 1084 Editoral changes. Changed XML namespace and schema from 0.1 to 0.2. 1085 Added pollType to reflect create, update, or delete maintenance poll 1086 messages. 1088 A.11. Change from 08 to 09 1090 Editoral changes. Added new section "Migrating to Newer Versions of 1091 This Extension". 1093 A.12. Change from 09 to 10 1095 Editoral changes. Renamed "msg" to "name". Added "courtesy" and "end" 1096 to pollType. 1098 A.13. Change from 10 to 11 1100 Editoral changes. Added mime type to description. 1102 A.14. Change from 11 to 12 1104 Editoral changes. Changed XML namespace from 0.2 to 0.3. 1106 A.15. Change from 12 to 13 1108 Editoral changes. Added TANGO Registry Services to Section 8. Added 1109 Michael Bauland to acknowledgments. Added "none" to . 1111 A.16. Change from 13 to 14 1113 Accepted in WGLC. Changed XML namespace from 0.3 to 1.0. 1115 Acknowledgments 1117 The authors wish to thank the following persons for their feedback 1118 and suggestions: James Gould, Michael Bauland, Patrick Mevzek, 1119 Quoc-Anh Pham, Raymond Zylstra, Christopher Martens, Anthony Eden, 1120 Neal McPherson, Craig Marchant, and Andreas Huber. 1122 Authors' Addresses 1124 Tobias Sattler 1126 Email: tobias.sattler@me.com 1127 URI: https://tobiassattler.com 1129 Roger Carney 1130 GoDaddy Inc. 1131 14455 N. Hayden Rd. #219 1132 Scottsdale, AZ 85260 1133 US 1135 Email: rcarney@godaddy.com 1136 URI: http://www.godaddy.com 1138 Jody Kolker 1139 GoDaddy Inc. 1140 14455 N. Hayden Rd. #219 1141 Scottsdale, AZ 85260 1142 US 1144 Email: jkolker@godaddy.com 1145 URI: http://www.godaddy.com