idnits 2.17.1 draft-ietf-regext-epp-registry-maintenance-11.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 (February 19, 2021) is 1159 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: June 30, 2021 J. Kolker 5 GoDaddy Inc. 6 February 19, 2021 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-11 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 June 30, 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 . . . . . . . . . . . . . . . . . 11 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 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 77 9.1. Normative References . . . . . . . . . . . . . . . . . . 19 78 9.2. Informative References . . . . . . . . . . . . . . . . . 20 79 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 20 80 A.1. Change from draft-sattler-epp-poll-maintenance-response to 81 draft-sattler-epp-registry-maintenance . . . . . . . . . 20 82 A.2. Change from draft-sattler-epp-registry-maintenance to 83 draft-ietf-regext-epp-registry-maintenance . . . . . . . 20 84 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 20 85 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20 86 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20 87 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20 88 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20 89 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20 90 A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 21 91 A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 21 92 A.11. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 21 93 A.12. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 21 94 A.13. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 21 95 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22 96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 98 1. Introduction 100 Registries usually conduct maintenances and inform registrars in 101 different ways. Given the DNS namespace expansion, it is now 102 desirable to provide methods for EPP servers to notify EPP clients 103 and EPP clients to query EPP servers for upcoming maintenances. 105 This document describes an extension mapping for version 1.0 of the 106 Extensible Provision Protocol [RFC5730]. This mapping provides a 107 mechanism by which EPP servers may notify and EPP clients to query 108 upcoming maintenances. 110 1.1. Terminology and Definitions 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 114 "OPTIONAL" in this document are to be interpreted as described in 115 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 116 capitals, as shown here. 118 XML is case sensitive. Unless stated otherwise, XML specifications 119 moreover, examples provided in this document MUST be interpreted in 120 the character case presented to develop a conforming implementation. 122 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 123 maintenance-0.2". The XML namespace prefix "maint" is used, but 124 implementations MUST NOT depend on it and instead employ a proper 125 namespace-aware XML parser and serializer to interpret and output 126 the XML documents. 128 In examples, "C:" represents lines sent by a protocol client and 129 "S:" represents lines returned by a protocol server. Indentation and 130 white space in examples are provided only to illustrate element 131 relationships and are not a REQUIRED feature of this protocol. 133 2. Migrating to Newer Versions of This Extension 135 Servers that implement this extension SHOULD provide a way for 136 clients to progressively update their implementations when a new 137 version of the extension is deployed. 139 Servers SHOULD (for a temporary migration period up to server policy) 140 provide support for older versions of the extension in parallel to 141 the newest version and allow clients to execute their preferred 142 version of the command based on the maintenance 143 elements of the server . The version of the maintenance 144 response MUST match the version of the maintenance 145 command executed by the server. 147 Servers MUST return a Registry Maintenance Notification poll message 148 matching the newest version of the maintenance extension, based on an 149 intersection of the maintenance elements in the server 150 and the client command. If the intersection of 151 the maintenance elements of the server and the 152 client command results in an empty set, the server MUST 153 return the newest version of the Registry Maintenance Notification 154 poll message supported by the server based on section 6 "Usage with 155 Poll Message EPP Response" of 156 [draft-ietf-regext-unhandled-namespaces]. 158 3. Object Attributes 160 3.1. Internationalized Domain Names 162 Names of affected hosts MUST be provided as an A-label according to 163 [RFC5891]. 165 3.2. Dates and Times 167 All dates and times attribute values MUST be expressed in Universal 168 Coordinated Time (UTC) using the Gregorian calendar. The extended 169 date-time form using upper case "T" and "Z" characters defined in ISO 170 8601 [RFC3339] MUST be used to represent date-time values. 172 3.3. Maintenance Elements 174 The element describes a single registry maintenance 175 event during a specific period. This element is used in a maintenance 176 item EPP response and message. 178 179 The server unique identifier for the maintenance with the OPTIONAL 180 "name" attribute that includes a human-readable name of the 181 maintenance. The server unique identifier SHALL NOT be changed if 182 the maintenance is updated or deleted. When the "name" attribute 183 is set, the OPTIONAL "lang" attribute MAY be present to identify 184 the language if the negotiated value is something other than the 185 default value of "en" (English). 187 188 The OPTIONAL type of the maintenance that has the possible set of 189 values defined by server policy. 191 192 The OPTIONAL element for a Registry Maintenance 193 Notification poll message; values MUST either be "create", 194 "update", "delete", "courtesy", or "end". For the "create" and 195 "update" types, the server includes the state of the maintenance 196 after the create or update. For the "delete" type, the server 197 includes the state of the maintenance prior to the delete. The 198 "courtesy" provides a reminder of a maintenance and the "end" 199 provides a notification of the end of the maintenance without 200 updating the maintenance object and includes the latest state of 201 the maintenance. This element MUST be present only for poll 202 messages. 204 205 One or more elements that are affected by the 206 maintenance. 208 209 The element contains the following child 210 elements: 212 213 The name of the affected system, such as "EPP", "WHOIS", 214 "DNS", "Portal", etc. 216 217 The affected maintained system contains the hostname, which 218 SHALL be an A-label according to [RFC5891]. 220 221 The impact level; the values MUST either be "full" or 222 "partial". If access is intermittently unavailable, it is 223 "partial". If access is completely unavailable it, is 224 "full". 226 227 The type of the affected system; the attribute "type" is 228 REQUIRED and MUST either be "production", "ote", "staging", 229 "dev" or "custom". For extensibility, the 230 element includes the OPTIONAL "name" attribute that can define 231 the name of the custom environment when the 232 element "type" attribute has the "custom" value. For example, 233 for the custom "marketing" environment, the 234 element should be: 235 237 238 The date and time of the start of the maintenance. 240 241 The date and time of the end of the maintenance. The 242 element MUST be equal to or greater than the 243 element. 245 246 The reason behind the maintenance; the values MUST either be 247 "planned" or "emergency". 249 250 The OPTIONAL URI to detailed maintenance description. 252 253 The OPTIONAL free-form description of the maintenance without 254 having to create and traverse an external resource defined by 255 the element. The OPTIONAL "lang" attribute MAY 256 be present to identify the language if the negotiated value is 257 something other then the default value of "en" (English). The 258 OPTIONAL "type" attribute MAY be present to identify the 259 format of the description. It MUST either be "plain" for plain 260 text or "html" HTML text that is defined in [W3C-HTML5] and 261 XML-escaped, with a default value of "plain". 263 264 The OPTIONAL element contains one or more 265 child elements. If the is not present, 266 the entire system is affected. 268 269 The affected top-level domain or registry zone, which SHALL 270 be an A-label according to [RFC5891]. 272 273 The OPTIONAL element contains the 274 following child elements: 276 277 The value SHALL be boolean and indicates if a client needs 278 to do something that is connection-related, such as a 279 reconnect. 281 282 The value SHALL be boolean and indicates if a client needs 283 to do something that is implementation-related, such as a 284 code change. 286 287 The date and time of the maintenance object creation. 289 290 The OPTIONAL date and time of the most recent maintenance 291 object modification. This element MUST NOT be present if the 292 maintenance object has never been modified. 294 4. EPP Command Mapping 296 A detailed description of the EPP syntax and semantics can be found 297 in the EPP core protocol specification [RFC5730]. The command 298 mappings described here are specifically for the use to notify of 299 Registry Maintenances and Registry Maintenance object mapping. 301 4.1. EPP Query Commands 303 EPP [RFC5730] provides three commands to retrieve object information: 304 to determine if an object is known to the server, to 305 retrieve detailed information associated with an object, and 306 to retrieve object transfer status information. 308 4.1.1. EPP Command 310 Available check semantics do not apply to maintenance objects, so 311 there is no mapping defined for the EPP command. 313 4.1.2. EPP Command 315 Transfer semantics do not apply to maintenance objects, so there is 316 no mapping defined for the EPP command. 318 4.1.3. EPP Command 320 EPP provides the command that is used to retrieve registry 321 maintenance information. In addition to the standard EPP command 322 elements, the command MUST contain a 323 element that identifies the maintenance namespace. 325 The element MUST contain a child element. It is either 326 the child element, described in Section 4.1.3.1, to query 327 for a specific maintenance item or the child element, 328 described in Section 4.1.3.2, to query all maintenance items. 330 4.1.3.1. Info Maintenance Item 332 The information on a specific maintenance item can be retrieved by 333 using the command with the element and the 334 child element, defined in Section 3.3. If the maintenance 335 identifier does not exist, the server MUST return an EPP error result 336 code of 2303 [RFC5730]. 338 Example to retrieve a specific maintenance item in an command. 340 C: 341 C: 342 C: 343 C: 344 C: 346 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 347 C: 348 C: 349 C: ABC-12345 350 C: 351 C: 353 When an command has been processed successfully, the EPP 355 element MUST contain a child element that 356 identifies the maintenance namespace. The element 357 contains the element defined in Section 3.3. 359 Example of returning a specific maintenance item in an 360 response. 362 S: 363 S: 364 S: 365 S: 366 S: Command completed successfully 367 S: 368 S: 369 S: 371 S: 372 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 373 S: 374 S: 375 S: 376 S: EPP 377 S: epp.registry.example 378 S: 379 S: full 380 S: 381 S: 382 S: 383 S: 2020-12-30T06:00:00Z 384 S: 2020-12-30T14:25:57Z 385 S: planned 386 S: 387 S: https://www.registry.example/notice?123 388 S: 389 S: free text 390 S: 391 S: 392 S: example 393 S: test 394 S: 395 S: 396 S: false 397 S: false 398 S: 399 S: 2020-09-08T22:10:00Z 400 S: 401 S: 402 S: 403 S: 404 S: ABC-12345 405 S: 54321-XYZ 406 S: 407 S: 408 S: 410 4.1.3.2. Info Maintenance List 412 The information for a list of maintenance items can be retrieved by 413 using the command with the element and the empty 414 child element. Server policy determines if previous 415 maintenances will be included in the list of maintenance items. 417 Example to retrieve the maintenance list in an command. 419 C: 420 C: 421 C: 422 C: 423 C: 425 C: 426 C: 427 C: 428 C: ABC-12345 429 C: 430 C: 432 When an command has been processed successfully, the EPP 433 element MUST contain a child element 434 that identifies the maintenance namespace. The 435 element contains the element with zero or more 436 child elements. The element 437 contains the following child elements: 439 440 The element defined in Section 3.3. 442 443 The element defined in Section 3.3. 445 446 The element defined in Section 3.3. 448 449 The element defined in Section 3.3. 451 452 The OPTIONAL element defined in Section 3.3. 454 Example of returning the maintenance list in an response. 456 S: 457 S: 458 S: 459 S: 460 S: Command completed successfully 461 S: 462 S: 463 S: 465 S: 466 S: 467 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 468 S: 469 S: 2020-12-30T06:00:00Z 470 S: 2020-12-30T07:00:00Z 471 S: 2020-09-08T22:10:00Z 472 S: 473 S: 474 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 475 S: 476 S: 2021-02-15T04:30:00Z 477 S: 2021-02-15T05:30:00Z 478 S: 2020-09-08T22:11:00Z 479 S: 2020-10-17T15:00:00Z 480 S: 481 S: 482 S: 483 S: 484 S: 485 S: ABC-12345 486 S: 54321-XYZ 487 S: 488 S: 489 S: 491 4.1.4. EPP Command 493 The EPP command and response is defined in Section 2.9.2.3 of 494 [RFC5730]. The Registry Maintenance Notification is included in the 495 EPP response of [RFC5730]. 497 For the Registry Maintenance Notification, there are three types of 498 poll messages, defined by the element in Section 499 3.3. A poll message applies when a maintenance is created, updated, 500 or deleted. In the case of a Registry Maintenance specific message, 501 a element will be included within the 502 element of the standard response. The element 503 contains the element defined in Section 3.3. 505 Example command: 507 C: 508 C: 509 C: 510 C: 511 C: ABC-12345 512 C: 513 C: 515 Example response: 517 S: 518 S: 519 S: 520 S: 521 S: Command completed successfully; ack to dequeue 522 S: 523 S: 524 S: 2020-10-08T22:10:00Z 525 S: Registry Maintenance Notification 526 S: 527 S: 528 S: 530 S: 531 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 532 S: create 533 S: 534 S: 535 S: EPP 536 S: epp.registry.example 537 S: 538 S: full 539 S: 540 S: 541 S: 542 S: 2020-12-30T06:00:00Z 543 S: 2020-12-30T14:25:57Z 544 S: planned 545 S: 546 S: https://www.registry.example/notice?123 547 S: 548 S: 549 S: example 550 S: test 551 S: 552 S: 553 S: false 554 S: false 555 S: 556 S: 2020-10-08T22:10:00Z 557 S: 558 S: 559 S: 560 S: 561 S: ABC-12345 562 S: 54321-XYZ 563 S: 564 S: 565 S: 567 4.2. EPP Transform Commands 569 EPP provides five commands to transform objects: to create 570 an instance of an object, to delete an instance of an 571 object, to extend the validity period of an object, 572 to manage object sponsorship changes, and to 573 change information associated with an object. 575 4.2.1. EPP Command 577 Create semantics do not apply to maintenance objects, so there is no 578 mapping defined for the EPP command. 580 4.2.2. EPP Command 582 Delete semantics do not apply to maintenance objects, so there is no 583 mapping defined for the EPP command. 585 4.2.3. EPP Command 587 Renew semantics do not apply to maintenance objects, so there is no 588 mapping defined for the EPP command. 590 4.2.4. EPP Command 592 Transfer semantics do not apply to maintenance objects, so there is 593 no mapping defined for the EPP command. 595 4.2.5. EPP Command 597 Update semantics do not apply to maintenance objects, so there is no 598 mapping defined for the EPP command. 600 5. Formal Syntax 602 The EPP Registry Maintenance schema is presented here. 603 The formal syntax presented here is a complete schema representation 604 of the object mapping suitable for automated validation of EPP XML 605 instances. The and tags are not part of 606 the schema; they are used to note the beginning and end of the 607 schema for URI registration purposes. 609 5.1. Registry Maintenance EPP Mapping Schema 611 612 613 620 623 624 625 626 627 Extensible Provisioning Protocol v1.0 628 Registry Maintenance Mapping Schema. 629 630 631 634 635 638 639 640 641 642 643 644 645 646 649 650 651 652 653 654 655 656 657 660 661 664 665 666 667 668 669 670 673 674 675 677 678 679 682 683 684 685 686 687 688 689 690 691 694 695 696 697 698 699 700 701 702 703 704 705 707 708 710 711 712 713 714 717 718 719 721 722 723 726 727 728 729 730 731 732 733 734 735 738 739 740 741 742 743 744 747 748 749 750 751 753 754 755 756 759 760 761 762 763 764 765 768 769 770 771 772 773 774 775 778 779 780 781 782 783 784 785 788 789 790 791 792 793 794 795 796 797 800 801 802 803 804 805 806 807 808 811 812 813 814 815 816 817 820 821 822 824 825 826 829 830 831 832 833 834 835 838 839 841 6. IANA Considerations 843 6.1. XML Namespace 845 This document uses URNs to describe XML namespaces and XML schemas 846 conforming to a registry mechanism defined in [RFC3688]. 848 Registration request for the maintenance namespace: 850 URI: urn:ietf:params:xml:ns:epp:maintenance-0.3 852 Registrant Contact: IESG 854 XML: None. Namespace URIs do not represent an XML specification. 856 Registration request for the maintenance schema: 858 URI: urn:ietf:params:xml:schema:maintenance-0.3 860 Registrant Contact: IESG 862 XML: See the "Formal Syntax" section of this document. 864 6.2. EPP Extension Registry 866 The following registration of the EPP Extension Registry, described 867 in [RFC7451], is requested: 869 Name of Extension: Registry Maintenance Notifications for the 870 Extensible Provisioning Protocol (EPP) 871 Document status: Standards Track 873 Reference: (insert the reference to RFC version of this document) 875 Registrant Name and Email Address: IESG 877 TLDs: Any 879 IPR Disclosure: None 881 Status: Active 883 Notes: None 885 7. Security Considerations 887 A server MUST only provide maintenance information for clients that 888 are authorized. If a client queries for a maintenance identifier, per 889 Section 4.1.3.1 "Info Maintenance Item", that it is not authorized to 890 access, the server MUST return an EPP error result code of 2201 891 [RFC5730]. The list of top-level domains or registry zones returned 892 in the "Info Maintenance Item" response SHOULD be filtered based on 893 the top-level domains or registry zones the client is authorized. 894 Authorization of poll messages is done at the time of poll message 895 insertion and not at the time of poll message consumption. 897 8. Implementation Status 899 Note to RFC Editor: Please remove this section and the reference to 900 [RFC7942] before publication. 902 This section records the status of known implementations of the 903 protocol defined by this specification at the time of posting of this 904 Internet-Draft, and is based on a proposal described in [RFC7942]. 905 The description of implementations in this section is intended to 906 assist the IETF in its decision processes in progressing drafts to 907 RFCs. Please note that the listing of any individual implementation 908 here does not imply endorsement by the IETF. Furthermore, no effort 909 has been spent to verify the information presented here that was 910 supplied by IETF contributors. This is not intended as, and must not 911 be construed to be, a catalog of available implementations or their 912 features. Readers are advised to note that other implementations may 913 exist. 915 According to [RFC7942], "this will allow reviewers and working groups 916 to assign due consideration to documents that have the benefit of 917 running code, which may serve as evidence of valuable experimentation 918 and feedback that have made the implemented protocols more mature. It 919 is up to the individual working groups to use this information as 920 they see fit". 922 8.1. GoDaddy Registry 924 Organization: GoDaddy Registry 925 Name: GoDaddy Registry 927 Description: GoDaddy Registry provides maintenance notifications to 928 their registrars. 930 Level of maturity: Production 932 Coverage: All aspects of the protocol according to the draft version 933 2 are implemented with further updates to come. 935 Licensing: Proprietary 937 Contact: quoc@registry.godaddy 939 URL: https://registry.godaddy 941 9. References 943 9.1. Normative References 945 [I.D.draft-ietf-regext-unhandled-namespaces] 946 Gould, J. and Casanova, M., "Extensible Provisioning 947 Protocol (EPP) Unhandled Namespaces", 948 (work in progress), December 2020. 951 [W3C-HTML5] Hickson, I., Berjon, R., Faulkner, S., Leithead, T., 952 Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", 953 W3C Recommendation REC-html5-20141028, October 2014, 954 . 956 Latest version available at . 958 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 959 Requirement Levels", BCP 14, RFC 2119, 960 DOI 10.17487/RFC2119, March 1997, 961 . 963 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 964 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 965 . 967 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 968 DOI 10.17487/RFC3688, January 2004, 969 . 971 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 972 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 973 . 975 [RFC5891] Klensin, J., "Internationalized Domain Names in 976 Applications (IDNA): Protocol", RFC 5891, 977 DOI 10.17487/RFC5891, August 2010, 978 . 980 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 981 Code: The Implementation Status Section", BCP 205, 982 RFC 7942, DOI 10.17487/RFC7942, July 2016, 983 . 985 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 986 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 987 May 2017, . 989 9.2. Informative References 991 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 992 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 993 February 2015, . 995 Appendix A. Change History 997 A.1. Change from draft-sattler-epp-poll-maintenance-response to 998 draft-sattler-epp-registry-maintenance 1000 Updated to be EPP based instead of JSON document. 1002 A.2. Change from draft-sattler-epp-registry-maintenance to 1003 draft-ietf-regext-epp-registry-maintenance 1005 Adopted by the REGEXT working group. 1007 A.3. Change from 00 to 01 1009 Clarified maint:description and maint:environment. Changed 1010 maint:description from complexType to simpleType. Fixed typo. 1011 Added acknowledgment. 1013 A.4. Change from 01 to 02 1015 Update language from Domain Name Registry to Registry. Clarified 1016 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 1017 to contain hostName and hostAddr. Changed maint:tlds from MUST to 1018 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 1019 unique id. 1021 A.5. Change from 02 to 03 1023 Changed maint:connection from MUST to SHOULD. 1025 A.6. Change from 03 to 04 1027 A lot of clarifications and editoral changes. 1029 A.7. Change from 04 to 05 1031 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 1032 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 1033 Clarified for retrieving maintenance items and the list. 1035 A.8. Change from 05 to 06 1037 Changed dates in examples to more recent dates. Renamed Query 1038 Maintenance Item and List to Info Maintenance Item and List. Removed 1039 blackout in favor of full. Added GoDaddy Registry implementation. 1041 A.9. Change from 06 to 07 1043 Removed IP addresses for . Editoral changes. 1045 A.10. Change from 07 to 08 1047 Editoral changes. Changed XML namespace and schema from 0.1 to 0.2. 1048 Added pollType to reflect create, update, or delete maintenance poll 1049 messages. 1051 A.11. Change from 08 to 09 1053 Editoral changes. Added new section "Migrating to Newer Versions of 1054 This Extension". 1056 A.12. Change from 09 to 10 1058 Editoral changes. Renamed "msg" to "name". Added "courtesy" and "end" 1059 to pollType. 1061 A.13. Change from 10 to 11 1063 Editoral changes. Added mime type to description. 1065 Acknowledgments 1067 The authors wish to thank the following persons for their feedback 1068 and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond 1069 Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig 1070 Marchant, and Andreas Huber. 1072 Authors' Addresses 1074 Tobias Sattler 1076 Email: tobias.sattler@me.com 1077 URI: https://tobiassattler.com 1079 Roger Carney 1080 GoDaddy Inc. 1081 14455 N. Hayden Rd. #219 1082 Scottsdale, AZ 85260 1083 US 1085 Email: rcarney@godaddy.com 1086 URI: http://www.godaddy.com 1088 Jody Kolker 1089 GoDaddy Inc. 1090 14455 N. Hayden Rd. #219 1091 Scottsdale, AZ 85260 1092 US 1094 Email: jkolker@godaddy.com 1095 URI: http://www.godaddy.com