idnits 2.17.1 draft-ietf-regext-epp-registry-maintenance-13.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 15, 2021) is 1108 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 15, 2021 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-13 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 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 101 1. Introduction 103 Registries usually conduct maintenances and inform registrars in 104 different ways. Given the DNS namespace expansion, it is now 105 desirable to provide methods for EPP servers to notify EPP clients 106 and EPP clients can query EPP servers for upcoming maintenances. 108 This document describes an extension mapping for version 1.0 of the 109 Extensible Provision Protocol [RFC5730]. This mapping provides a 110 mechanism by which EPP servers may notify and EPP clients to query 111 upcoming maintenances. 113 1.1. Terminology and Definitions 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 117 "OPTIONAL" in this document are to be interpreted as described in 118 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 119 capitals, as shown here. 121 XML is case sensitive. Unless stated otherwise, XML specifications 122 moreover, examples provided in this document MUST be interpreted in 123 the character case presented to develop a conforming implementation. 125 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 126 maintenance-0.3". The XML namespace prefix "maint" is used, but 127 implementations MUST NOT depend on it and instead employ a proper 128 namespace-aware XML parser and serializer to interpret and output 129 the XML documents. 131 In examples, "C:" represents lines sent by a protocol client and 132 "S:" represents lines returned by a protocol server. Indentation and 133 white space in examples are provided only to illustrate element 134 relationships and are not a REQUIRED feature of this protocol. 136 2. Migrating to Newer Versions of This Extension 138 Servers that implement this extension SHOULD provide a way for 139 clients to progressively update their implementations when a new 140 version of the extension is deployed. 142 Servers SHOULD (for a temporary migration period up to server policy) 143 provide support for older versions of the extension in parallel to 144 the newest version and allow clients to execute their preferred 145 version of the command based on the maintenance 146 elements of the server . The version of the maintenance 147 response MUST match the version of the maintenance 148 command executed by the server. 150 Servers MUST return a Registry Maintenance Notification poll message 151 matching the newest version of the maintenance extension, based on an 152 intersection of the maintenance elements in the server 153 and the client command. If the intersection of 154 the maintenance elements of the server and the 155 client command results in an empty set, the server MUST 156 return the newest version of the Registry Maintenance Notification 157 poll message supported by the server based on section 6 "Usage with 158 Poll Message EPP Response" of 159 [draft-ietf-regext-unhandled-namespaces]. 161 3. Object Attributes 163 3.1. Internationalized Domain Names 165 Names of affected hosts MUST be provided as an A-label according to 166 [RFC5891]. 168 3.2. Dates and Times 170 All dates and times attribute values MUST be expressed in Universal 171 Coordinated Time (UTC) using the Gregorian calendar. The extended 172 date-time form using upper case "T" and "Z" characters defined in ISO 173 8601 [RFC3339] MUST be used to represent date-time values. 175 3.3. Maintenance Elements 177 The element describes a single registry maintenance 178 event during a specific period. This element is used in a maintenance 179 item EPP response and message. 181 182 The server unique identifier for the maintenance with the OPTIONAL 183 "name" attribute that includes a human-readable name of the 184 maintenance. The server unique identifier SHALL NOT be changed if 185 the maintenance is updated or deleted. When the "name" attribute 186 is set, the OPTIONAL "lang" attribute MAY be present to identify 187 the language if the negotiated value is something other than the 188 default value of "en" (English). 190 191 Zero or more OPTIONAL types of the maintenance that has the 192 possible set of values defined by server policy, such as 193 "Routine Maintenance", "Software Update", "Software Upgrade", or 194 "Extended Outage". 196 197 The OPTIONAL element for a Registry Maintenance 198 Notification poll message; values MUST either be "create", 199 "update", "delete", "courtesy", or "end". For the "create" and 200 "update" types, the server includes the state of the maintenance 201 after the create or update. For the "delete" type, the server 202 includes the state of the maintenance prior to the delete. The 203 "courtesy" provides a reminder of a maintenance and the "end" 204 provides a notification of the end of the maintenance without 205 updating the maintenance object and includes the latest state of 206 the maintenance. This element MUST be present only for poll 207 messages. 209 210 One or more elements that are affected by the 211 maintenance. 213 214 The element contains the following child 215 elements: 217 218 The name of the affected system, such as "EPP", "WHOIS", 219 "DNS", "Portal", etc. 221 222 The OPTIONAL affected maintained system's hostname, which 223 SHALL be an A-label according to [RFC5891]. 225 226 The impact level; the values MUST either be "full", 227 "partial", or "none". If access is intermittently 228 unavailable, it is "partial". If access is completely 229 unavailable, it is "full". If access is not affected, it is 230 "none". 232 233 The type of the affected system; the attribute "type" is 234 REQUIRED and MUST either be "production", "ote", "staging", 235 "dev" or "custom". For extensibility, the 236 element includes the OPTIONAL "name" attribute that can define 237 the name of the custom environment when the 238 element "type" attribute has the "custom" value. For example, 239 for the custom "marketing" environment, the 240 element should be: 241 243 244 The date and time of the start of the maintenance. 246 247 The date and time of the end of the maintenance. The 248 element MUST be equal to or greater than the 249 element. 251 252 The reason behind the maintenance; the values MUST either be 253 "planned" or "emergency". 255 256 The OPTIONAL URI to detailed maintenance description, formatted 257 according to [RFC8820]. 259 260 Zero or more OPTIONAL free-form descriptions of the maintenance 261 without having to create and traverse an external resource 262 defined by the element. The OPTIONAL "lang" 263 attribute MAY be present to identify the language if the 264 negotiated value is something other then the default value of 265 "en" (English). The OPTIONAL "type" attribute MAY be present to 266 identify the format of the description. It MUST either be 267 "plain" for plain text or "html" HTML text that is defined in 268 [W3C-HTML5] and XML-escaped, with a default value of "plain". 270 271 The OPTIONAL element contains one or more 272 child elements. If the is not present, 273 the entire system is affected. 275 276 The affected top-level domain or registry zone, which SHALL 277 be an A-label according to [RFC5891]. 279 280 The OPTIONAL element contains the 281 following child elements: 283 284 The value SHALL be boolean and indicates if a client needs 285 to do something that is connection-related, such as a 286 reconnect. 288 289 The value SHALL be boolean and indicates if a client needs 290 to do something that is implementation-related, such as a 291 code change. 293 294 The date and time of the maintenance object creation. 296 297 The OPTIONAL date and time of the most recent maintenance 298 object modification. This element MUST NOT be present if the 299 maintenance object has never been modified. 301 4. EPP Command Mapping 303 A detailed description of the EPP syntax and semantics can be found 304 in the EPP core protocol specification [RFC5730]. The command 305 mappings described here are specifically for the use to notify of 306 Registry Maintenances and Registry Maintenance object mapping. 308 4.1. EPP Query Commands 310 EPP [RFC5730] provides three commands to retrieve object information: 311 to determine if an object is known to the server, to 312 retrieve detailed information associated with an object, and 313 to retrieve object transfer status information. 315 4.1.1. EPP Command 317 Available check semantics do not apply to maintenance objects, so 318 there is no mapping defined for the EPP command. 320 4.1.2. EPP Command 322 Transfer semantics do not apply to maintenance objects, so there is 323 no mapping defined for the EPP command. 325 4.1.3. EPP Command 327 EPP provides the command that is used to retrieve registry 328 maintenance information. In addition to the standard EPP command 329 elements, the command MUST contain a 330 element that identifies the maintenance namespace. 332 The element MUST contain a child element. It is either 333 the child element, described in Section 4.1.3.1, to query 334 for a specific maintenance item or the child element, 335 described in Section 4.1.3.2, to query all maintenance items. 337 4.1.3.1. Info Maintenance Item 339 The information on a specific maintenance item can be retrieved by 340 using the command with the element and the 341 child element, defined in Section 3.3. If the maintenance 342 identifier does not exist, the server MUST return an EPP error result 343 code of 2303 [RFC5730]. 345 Example to retrieve a specific maintenance item in an command. 347 C: 348 C: 349 C: 350 C: 351 C: 353 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 354 C: 355 C: 356 C: ABC-12345 357 C: 358 C: 360 When an command has been processed successfully, the EPP 361 element MUST contain a child element that 362 identifies the maintenance namespace. The element 363 contains the element defined in Section 3.3. 365 Example of returning a specific maintenance item in an 366 response. 368 S: 369 S: 370 S: 371 S: 372 S: Command completed successfully 373 S: 374 S: 375 S: 377 S: 378 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 379 S: 380 S: Routine Maintenance 381 S: 382 S: 383 S: EPP 384 S: epp.registry.example 385 S: 386 S: full 387 S: 388 S: 389 S: 390 S: 2021-12-30T06:00:00Z 391 S: 2021-12-30T14:25:57Z 392 S: planned 393 S: 394 S: https://www.registry.example/notice?123 395 S: 396 S: free-text 397 S: 398 S: Freitext 399 S: 400 S: 401 S: example 402 S: test 403 S: 404 S: 405 S: false 406 S: false 407 S: 408 S: 2021-09-08T22:10:00Z 409 S: 410 S: 411 S: 412 S: 413 S: ABC-12345 414 S: 54321-XYZ 415 S: 416 S: 417 S: 419 4.1.3.2. Info Maintenance List 421 The information for a list of maintenance items can be retrieved by 422 using the command with the element and the empty 423 child element. Server policy determines if previous 424 maintenances will be included in the list of maintenance items. 426 Example to retrieve the maintenance list in an command. 428 C: 429 C: 430 C: 431 C: 432 C: 434 C: 435 C: 436 C: 437 C: ABC-12345 438 C: 439 C: 441 When an command has been processed successfully, the EPP 442 element MUST contain a child element 443 that identifies the maintenance namespace. The 444 element contains the element with zero or more 445 child elements. The element 446 contains the following child elements: 448 449 The element defined in Section 3.3. 451 452 The element defined in Section 3.3. 454 455 The element defined in Section 3.3. 457 458 The element defined in Section 3.3. 460 461 The OPTIONAL element defined in Section 3.3. 463 Example of returning the maintenance list in an response. 465 S: 466 S: 467 S: 468 S: 469 S: Command completed successfully 470 S: 471 S: 472 S: 474 S: 475 S: 476 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 477 S: 478 S: 2021-12-30T06:00:00Z 479 S: 2021-12-30T07:00:00Z 480 S: 2021-09-08T22:10:00Z 481 S: 482 S: 483 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 484 S: 485 S: 2021-12-15T04:30:00Z 486 S: 2021-12-15T05:30:00Z 487 S: 2021-09-08T22:11:00Z 488 S: 2021-10-17T15:00:00Z 489 S: 490 S: 491 S: 492 S: 493 S: 494 S: ABC-12345 495 S: 54321-XYZ 496 S: 497 S: 498 S: 500 4.1.4. EPP Command 502 The EPP command and response is defined in Section 2.9.2.3 of 503 [RFC5730]. The Registry Maintenance Notification is included in the 504 EPP response of [RFC5730]. 506 For the Registry Maintenance Notification, there are five types of 507 poll messages, defined by the element in Section 508 3.3. A poll message applies when a maintenance is created, updated or 509 deleted. A courtesy poll message can be sent as a reminder of 510 an impending maintenance. An end poll message can be sent when the 511 maintenance is completed. In the case of a Registry Maintenance 512 specific message, a element will be included within 513 the element of the standard response. The 514 element contains the element defined in 515 Section 3.3. 517 Example command: 519 C: 520 C: 521 C: 522 C: 523 C: ABC-12345 524 C: 525 C: 526 Example response: 528 S: 529 S: 530 S: 531 S: 532 S: Command completed successfully; ack to dequeue 533 S: 534 S: 535 S: 2021-10-08T22:10:00Z 536 S: Registry Maintenance Notification 537 S: 538 S: 539 S: 541 S: 542 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 543 S: create 544 S: 545 S: 546 S: EPP 547 S: epp.registry.example 548 S: 549 S: full 550 S: 551 S: 552 S: 553 S: 2021-12-30T06:00:00Z 554 S: 2021-12-30T14:25:57Z 555 S: planned 556 S: 557 S: https://www.registry.example/notice?123 558 S: 559 S: 560 S: example 561 S: test 562 S: 563 S: 564 S: false 565 S: false 566 S: 567 S: 2021-10-08T22:10:00Z 568 S: 569 S: 570 S: 571 S: 572 S: ABC-12345 573 S: 54321-XYZ 574 S: 575 S: 576 S: 578 4.2. EPP Transform Commands 580 EPP provides five commands to transform objects: to create 581 an instance of an object, to delete an instance of an 582 object, to extend the validity period of an object, 583 to manage object sponsorship changes, and to 584 change information associated with an object. 586 4.2.1. EPP Command 588 Create semantics do not apply to maintenance objects, so there is no 589 mapping defined for the EPP command. 591 4.2.2. EPP Command 593 Delete semantics do not apply to maintenance objects, so there is no 594 mapping defined for the EPP command. 596 4.2.3. EPP Command 598 Renew semantics do not apply to maintenance objects, so there is no 599 mapping defined for the EPP command. 601 4.2.4. EPP Command 603 Transfer semantics do not apply to maintenance objects, so there is 604 no mapping defined for the EPP command. 606 4.2.5. EPP Command 608 Update semantics do not apply to maintenance objects, so there is no 609 mapping defined for the EPP command. 611 5. Formal Syntax 613 The EPP Registry Maintenance schema is presented here. 614 The formal syntax presented here is a complete schema representation 615 of the object mapping suitable for automated validation of EPP XML 616 instances. The and tags are not part of 617 the schema; they are used to note the beginning and end of the 618 schema for URI registration purposes. 620 5.1. Registry Maintenance EPP Mapping Schema 622 623 624 632 635 636 637 638 639 Extensible Provisioning Protocol v1.0 640 Registry Maintenance Mapping Schema. 641 642 643 646 647 650 651 652 653 654 655 656 657 658 661 662 663 664 665 666 667 668 669 672 673 676 677 678 679 680 681 682 685 686 687 689 690 691 694 695 696 697 698 699 700 701 702 703 706 707 708 709 711 712 713 714 715 716 717 718 720 721 723 724 725 726 727 730 731 732 734 735 736 739 740 741 742 743 744 745 746 747 748 751 752 753 754 755 756 757 758 761 762 763 764 765 767 768 769 770 773 774 775 776 777 778 779 782 783 784 785 786 787 788 789 792 793 794 795 796 797 798 799 802 803 804 805 806 807 808 809 810 811 814 815 816 817 818 819 820 821 822 825 826 827 828 829 830 831 834 835 836 838 839 840 843 844 845 846 847 848 849 852 853 855 6. IANA Considerations 857 6.1. XML Namespace 859 This document uses URNs to describe XML namespaces and XML schemas 860 conforming to a registry mechanism defined in [RFC3688]. 862 Registration request for the maintenance namespace: 864 URI: urn:ietf:params:xml:ns:epp:maintenance-0.3 866 Registrant Contact: IESG 868 XML: None. Namespace URIs do not represent an XML specification. 870 Registration request for the maintenance schema: 872 URI: urn:ietf:params:xml:schema:maintenance-0.3 874 Registrant Contact: IESG 876 XML: See the "Formal Syntax" section of this document. 878 6.2. EPP Extension Registry 880 The following registration of the EPP Extension Registry, described 881 in [RFC7451], is requested: 883 Name of Extension: Registry Maintenance Notifications for the 884 Extensible Provisioning Protocol (EPP) 885 Document status: Standards Track 887 Reference: (insert the reference to RFC version of this document) 889 Registrant Name and Email Address: IESG 891 TLDs: Any 893 IPR Disclosure: None 895 Status: Active 897 Notes: None 899 7. Security Considerations 901 A server MUST only provide maintenance information for clients that 902 are authorized. If a client queries for a maintenance identifier, per 903 Section 4.1.3.1 "Info Maintenance Item", that it is not authorized to 904 access, the server MUST return an EPP error result code of 2201 905 [RFC5730]. The list of top-level domains or registry zones returned 906 in the "Info Maintenance Item" response SHOULD be filtered based on 907 the top-level domains or registry zones the client is authorized. 908 Authorization of poll messages is done at the time of poll message 909 insertion and not at the time of poll message consumption. 911 8. Implementation Status 913 Note to RFC Editor: Please remove this section and the reference to 914 [RFC7942] before publication. 916 This section records the status of known implementations of the 917 protocol defined by this specification at the time of posting of this 918 Internet-Draft, and is based on a proposal described in [RFC7942]. 919 The description of implementations in this section is intended to 920 assist the IETF in its decision processes in progressing drafts to 921 RFCs. Please note that the listing of any individual implementation 922 here does not imply endorsement by the IETF. Furthermore, no effort 923 has been spent to verify the information presented here that was 924 supplied by IETF contributors. This is not intended as, and must not 925 be construed to be, a catalog of available implementations or their 926 features. Readers are advised to note that other implementations may 927 exist. 929 According to [RFC7942], "this will allow reviewers and working groups 930 to assign due consideration to documents that have the benefit of 931 running code, which may serve as evidence of valuable experimentation 932 and feedback that have made the implemented protocols more mature. It 933 is up to the individual working groups to use this information as 934 they see fit". 936 8.1. GoDaddy Registry 938 Organization: GoDaddy Registry 939 Name: GoDaddy Registry 941 Description: GoDaddy Registry provides maintenance notifications to 942 their registrars. 944 Level of maturity: Production 946 Coverage: All aspects of the protocol according to the draft version 947 2 are implemented with further updates to come. 949 Licensing: Proprietary 951 Contact: quoc@registry.godaddy 953 URL: https://registry.godaddy 955 8.2. TANGO Registry Services 957 Name: TANGO Registry Services 959 Description: TANGO Registry Services provides maintenance 960 notifications to their registrars. 962 Level of maturity: Beta 964 Coverage: All aspects of the protocol according to the draft version 965 12 are implemented with further updates to come. 967 Licensing: Proprietary 969 Contact: Michael.Bauland@knipp.de 971 URL: https://tango-rs.com 973 9. References 975 9.1. Normative References 977 [I.D.draft-ietf-regext-unhandled-namespaces] 978 Gould, J. and Casanova, M., "Extensible Provisioning 979 Protocol (EPP) Unhandled Namespaces", 980 (work in progress), February 2021. 983 [W3C-HTML5] Hickson, I., Berjon, R., Faulkner, S., Leithead, T., 984 Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", 985 W3C Recommendation REC-html5-20141028, October 2014, 986 . 988 Latest version available at . 990 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 991 Requirement Levels", BCP 14, RFC 2119, 992 DOI 10.17487/RFC2119, March 1997, 993 . 995 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 996 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 997 . 999 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1000 DOI 10.17487/RFC3688, January 2004, 1001 . 1003 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1004 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1005 . 1007 [RFC5891] Klensin, J., "Internationalized Domain Names in 1008 Applications (IDNA): Protocol", RFC 5891, 1009 DOI 10.17487/RFC5891, August 2010, 1010 . 1012 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1013 Code: The Implementation Status Section", BCP 205, 1014 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1015 . 1017 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1018 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1019 May 2017, . 1021 [RFC8820] Nottingham, M., "URI Design and Ownership", BCP 190, RFC 1022 8820, DOI 10.17487/RFC8820, June 2020, 1023 . 1025 9.2. Informative References 1027 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1028 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1029 February 2015, . 1031 Appendix A. Change History 1033 A.1. Change from draft-sattler-epp-poll-maintenance-response to 1034 draft-sattler-epp-registry-maintenance 1036 Updated to be EPP based instead of JSON document. 1038 A.2. Change from draft-sattler-epp-registry-maintenance to 1039 draft-ietf-regext-epp-registry-maintenance 1041 Adopted by the REGEXT working group. 1043 A.3. Change from 00 to 01 1045 Clarified maint:description and maint:environment. Changed 1046 maint:description from complexType to simpleType. Fixed typo. 1047 Added acknowledgment. 1049 A.4. Change from 01 to 02 1051 Update language from Domain Name Registry to Registry. Clarified 1052 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 1053 to contain hostName and hostAddr. Changed maint:tlds from MUST to 1054 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 1055 unique id. 1057 A.5. Change from 02 to 03 1059 Changed maint:connection from MUST to SHOULD. 1061 A.6. Change from 03 to 04 1063 A lot of clarifications and editoral changes. 1065 A.7. Change from 04 to 05 1067 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 1068 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 1069 Clarified for retrieving maintenance items and the list. 1071 A.8. Change from 05 to 06 1073 Changed dates in examples to more recent dates. Renamed Query 1074 Maintenance Item and List to Info Maintenance Item and List. Removed 1075 blackout in favor of full. Added GoDaddy Registry implementation. 1077 A.9. Change from 06 to 07 1079 Removed IP addresses for . Editoral changes. 1081 A.10. Change from 07 to 08 1083 Editoral changes. Changed XML namespace and schema from 0.1 to 0.2. 1084 Added pollType to reflect create, update, or delete maintenance poll 1085 messages. 1087 A.11. Change from 08 to 09 1089 Editoral changes. Added new section "Migrating to Newer Versions of 1090 This Extension". 1092 A.12. Change from 09 to 10 1094 Editoral changes. Renamed "msg" to "name". Added "courtesy" and "end" 1095 to pollType. 1097 A.13. Change from 10 to 11 1099 Editoral changes. Added mime type to description. 1101 A.14. Change from 11 to 12 1103 Editoral changes. Changed XML namespace from 0.2 to 0.3. 1105 A.15. Change from 12 to 13 1107 Editoral changes. Added TANGO Registry Services to Section 8. Added 1108 Michael Bauland to acknowledgments. Added "none" to . 1110 Acknowledgments 1112 The authors wish to thank the following persons for their feedback 1113 and suggestions: James Gould, Michael Bauland, Patrick Mevzek, 1114 Quoc-Anh Pham, Raymond Zylstra, Christopher Martens, Anthony Eden, 1115 Neal McPherson, Craig Marchant, and Andreas Huber. 1117 Authors' Addresses 1119 Tobias Sattler 1121 Email: tobias.sattler@me.com 1122 URI: https://tobiassattler.com 1124 Roger Carney 1125 GoDaddy Inc. 1126 14455 N. Hayden Rd. #219 1127 Scottsdale, AZ 85260 1128 US 1130 Email: rcarney@godaddy.com 1131 URI: http://www.godaddy.com 1133 Jody Kolker 1134 GoDaddy Inc. 1135 14455 N. Hayden Rd. #219 1136 Scottsdale, AZ 85260 1137 US 1139 Email: jkolker@godaddy.com 1140 URI: http://www.godaddy.com