idnits 2.17.1 draft-ietf-regext-epp-registry-maintenance-12.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 27, 2021) is 1125 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 March 27, 2021 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-12 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 A.14. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 21 96 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 99 1. Introduction 101 Registries usually conduct maintenances and inform registrars in 102 different ways. Given the DNS namespace expansion, it is now 103 desirable to provide methods for EPP servers to notify EPP clients 104 and EPP clients to query EPP servers for upcoming maintenances. 106 This document describes an extension mapping for version 1.0 of the 107 Extensible Provision Protocol [RFC5730]. This mapping provides a 108 mechanism by which EPP servers may notify and EPP clients to query 109 upcoming maintenances. 111 1.1. Terminology and Definitions 113 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 114 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 115 "OPTIONAL" in this document are to be interpreted as described in 116 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 117 capitals, as shown here. 119 XML is case sensitive. Unless stated otherwise, XML specifications 120 moreover, examples provided in this document MUST be interpreted in 121 the character case presented to develop a conforming implementation. 123 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 124 maintenance-0.3". The XML namespace prefix "maint" is used, but 125 implementations MUST NOT depend on it and instead employ a proper 126 namespace-aware XML parser and serializer to interpret and output 127 the XML documents. 129 In examples, "C:" represents lines sent by a protocol client and 130 "S:" represents lines returned by a protocol server. Indentation and 131 white space in examples are provided only to illustrate element 132 relationships and are not a REQUIRED feature of this protocol. 134 2. Migrating to Newer Versions of This Extension 136 Servers that implement this extension SHOULD provide a way for 137 clients to progressively update their implementations when a new 138 version of the extension is deployed. 140 Servers SHOULD (for a temporary migration period up to server policy) 141 provide support for older versions of the extension in parallel to 142 the newest version and allow clients to execute their preferred 143 version of the command based on the maintenance 144 elements of the server . The version of the maintenance 145 response MUST match the version of the maintenance 146 command executed by the server. 148 Servers MUST return a Registry Maintenance Notification poll message 149 matching the newest version of the maintenance extension, based on an 150 intersection of the maintenance elements in the server 151 and the client command. If the intersection of 152 the maintenance elements of the server and the 153 client command results in an empty set, the server MUST 154 return the newest version of the Registry Maintenance Notification 155 poll message supported by the server based on section 6 "Usage with 156 Poll Message EPP Response" of 157 [draft-ietf-regext-unhandled-namespaces]. 159 3. Object Attributes 161 3.1. Internationalized Domain Names 163 Names of affected hosts MUST be provided as an A-label according to 164 [RFC5891]. 166 3.2. Dates and Times 168 All dates and times attribute values MUST be expressed in Universal 169 Coordinated Time (UTC) using the Gregorian calendar. The extended 170 date-time form using upper case "T" and "Z" characters defined in ISO 171 8601 [RFC3339] MUST be used to represent date-time values. 173 3.3. Maintenance Elements 175 The element describes a single registry maintenance 176 event during a specific period. This element is used in a maintenance 177 item EPP response and message. 179 180 The server unique identifier for the maintenance with the OPTIONAL 181 "name" attribute that includes a human-readable name of the 182 maintenance. The server unique identifier SHALL NOT be changed if 183 the maintenance is updated or deleted. When the "name" attribute 184 is set, the OPTIONAL "lang" attribute MAY be present to identify 185 the language if the negotiated value is something other than the 186 default value of "en" (English). 188 189 The OPTIONAL type of the maintenance that has the possible set of 190 values defined by server policy. 192 193 The OPTIONAL element for a Registry Maintenance 194 Notification poll message; values MUST either be "create", 195 "update", "delete", "courtesy", or "end". For the "create" and 196 "update" types, the server includes the state of the maintenance 197 after the create or update. For the "delete" type, the server 198 includes the state of the maintenance prior to the delete. The 199 "courtesy" provides a reminder of a maintenance and the "end" 200 provides a notification of the end of the maintenance without 201 updating the maintenance object and includes the latest state of 202 the maintenance. This element MUST be present only for poll 203 messages. 205 206 One or more elements that are affected by the 207 maintenance. 209 210 The element contains the following child 211 elements: 213 214 The name of the affected system, such as "EPP", "WHOIS", 215 "DNS", "Portal", etc. 217 218 The affected maintained system contains the hostname, which 219 SHALL be an A-label according to [RFC5891]. 221 222 The impact level; the values MUST either be "full" or 223 "partial". If access is intermittently unavailable, it is 224 "partial". If access is completely unavailable it, is 225 "full". 227 228 The type of the affected system; the attribute "type" is 229 REQUIRED and MUST either be "production", "ote", "staging", 230 "dev" or "custom". For extensibility, the 231 element includes the OPTIONAL "name" attribute that can define 232 the name of the custom environment when the 233 element "type" attribute has the "custom" value. For example, 234 for the custom "marketing" environment, the 235 element should be: 236 238 239 The date and time of the start of the maintenance. 241 242 The date and time of the end of the maintenance. The 243 element MUST be equal to or greater than the 244 element. 246 247 The reason behind the maintenance; the values MUST either be 248 "planned" or "emergency". 250 251 The OPTIONAL URI to detailed maintenance description. 253 254 The OPTIONAL free-form description of the maintenance without 255 having to create and traverse an external resource defined by 256 the element. The OPTIONAL "lang" attribute MAY 257 be present to identify the language if the negotiated value is 258 something other then the default value of "en" (English). The 259 OPTIONAL "type" attribute MAY be present to identify the 260 format of the description. It MUST either be "plain" for plain 261 text or "html" HTML text that is defined in [W3C-HTML5] and 262 XML-escaped, with a default value of "plain". 264 265 The OPTIONAL element contains one or more 266 child elements. If the is not present, 267 the entire system is affected. 269 270 The affected top-level domain or registry zone, which SHALL 271 be an A-label according to [RFC5891]. 273 274 The OPTIONAL element contains the 275 following child elements: 277 278 The value SHALL be boolean and indicates if a client needs 279 to do something that is connection-related, such as a 280 reconnect. 282 283 The value SHALL be boolean and indicates if a client needs 284 to do something that is implementation-related, such as a 285 code change. 287 288 The date and time of the maintenance object creation. 290 291 The OPTIONAL date and time of the most recent maintenance 292 object modification. This element MUST NOT be present if the 293 maintenance object has never been modified. 295 4. EPP Command Mapping 297 A detailed description of the EPP syntax and semantics can be found 298 in the EPP core protocol specification [RFC5730]. The command 299 mappings described here are specifically for the use to notify of 300 Registry Maintenances and Registry Maintenance object mapping. 302 4.1. EPP Query Commands 304 EPP [RFC5730] provides three commands to retrieve object information: 305 to determine if an object is known to the server, to 306 retrieve detailed information associated with an object, and 307 to retrieve object transfer status information. 309 4.1.1. EPP Command 311 Available check semantics do not apply to maintenance objects, so 312 there is no mapping defined for the EPP command. 314 4.1.2. EPP Command 316 Transfer semantics do not apply to maintenance objects, so there is 317 no mapping defined for the EPP command. 319 4.1.3. EPP Command 321 EPP provides the command that is used to retrieve registry 322 maintenance information. In addition to the standard EPP command 323 elements, the command MUST contain a 324 element that identifies the maintenance namespace. 326 The element MUST contain a child element. It is either 327 the child element, described in Section 4.1.3.1, to query 328 for a specific maintenance item or the child element, 329 described in Section 4.1.3.2, to query all maintenance items. 331 4.1.3.1. Info Maintenance Item 333 The information on a specific maintenance item can be retrieved by 334 using the command with the element and the 335 child element, defined in Section 3.3. If the maintenance 336 identifier does not exist, the server MUST return an EPP error result 337 code of 2303 [RFC5730]. 339 Example to retrieve a specific maintenance item in an command. 341 C: 342 C: 343 C: 344 C: 345 C: 347 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 348 C: 349 C: 350 C: ABC-12345 351 C: 352 C: 354 When an command has been processed successfully, the EPP 356 element MUST contain a child element that 357 identifies the maintenance namespace. The element 358 contains the element defined in Section 3.3. 360 Example of returning a specific maintenance item in an 361 response. 363 S: 364 S: 365 S: 366 S: 367 S: Command completed successfully 368 S: 369 S: 370 S: 372 S: 373 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 374 S: 375 S: 376 S: 377 S: EPP 378 S: epp.registry.example 379 S: 380 S: full 381 S: 382 S: 383 S: 384 S: 2020-12-30T06:00:00Z 385 S: 2020-12-30T14:25:57Z 386 S: planned 387 S: 388 S: https://www.registry.example/notice?123 389 S: 390 S: free text 391 S: 392 S: 393 S: example 394 S: test 395 S: 396 S: 397 S: false 398 S: false 399 S: 400 S: 2020-09-08T22:10:00Z 401 S: 402 S: 403 S: 404 S: 405 S: ABC-12345 406 S: 54321-XYZ 407 S: 408 S: 409 S: 411 4.1.3.2. Info Maintenance List 413 The information for a list of maintenance items can be retrieved by 414 using the command with the element and the empty 415 child element. Server policy determines if previous 416 maintenances will be included in the list of maintenance items. 418 Example to retrieve the maintenance list in an command. 420 C: 421 C: 422 C: 423 C: 424 C: 426 C: 427 C: 428 C: 429 C: ABC-12345 430 C: 431 C: 433 When an command has been processed successfully, the EPP 434 element MUST contain a child element 435 that identifies the maintenance namespace. The 436 element contains the element with zero or more 437 child elements. The element 438 contains the following child elements: 440 441 The element defined in Section 3.3. 443 444 The element defined in Section 3.3. 446 447 The element defined in Section 3.3. 449 450 The element defined in Section 3.3. 452 453 The OPTIONAL element defined in Section 3.3. 455 Example of returning the maintenance list in an response. 457 S: 458 S: 459 S: 460 S: 461 S: Command completed successfully 462 S: 463 S: 464 S: 466 S: 467 S: 468 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 469 S: 470 S: 2020-12-30T06:00:00Z 471 S: 2020-12-30T07:00:00Z 472 S: 2020-09-08T22:10:00Z 473 S: 474 S: 475 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 476 S: 477 S: 2021-02-15T04:30:00Z 478 S: 2021-02-15T05:30:00Z 479 S: 2020-09-08T22:11:00Z 480 S: 2020-10-17T15:00:00Z 481 S: 482 S: 483 S: 484 S: 485 S: 486 S: ABC-12345 487 S: 54321-XYZ 488 S: 489 S: 490 S: 492 4.1.4. EPP Command 494 The EPP command and response is defined in Section 2.9.2.3 of 495 [RFC5730]. The Registry Maintenance Notification is included in the 496 EPP response of [RFC5730]. 498 For the Registry Maintenance Notification, there are three types of 499 poll messages, defined by the element in Section 500 3.3. A poll message applies when a maintenance is created, updated, 501 or deleted. In the case of a Registry Maintenance specific message, 502 a element will be included within the 503 element of the standard response. The element 504 contains the element defined in Section 3.3. 506 Example command: 508 C: 509 C: 510 C: 511 C: 512 C: ABC-12345 513 C: 514 C: 516 Example response: 518 S: 519 S: 520 S: 521 S: 522 S: Command completed successfully; ack to dequeue 523 S: 524 S: 525 S: 2020-10-08T22:10:00Z 526 S: Registry Maintenance Notification 527 S: 528 S: 529 S: 531 S: 532 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 533 S: create 534 S: 535 S: 536 S: EPP 537 S: epp.registry.example 538 S: 539 S: full 540 S: 541 S: 542 S: 543 S: 2020-12-30T06:00:00Z 544 S: 2020-12-30T14:25:57Z 545 S: planned 546 S: 547 S: https://www.registry.example/notice?123 548 S: 549 S: 550 S: example 551 S: test 552 S: 553 S: 554 S: false 555 S: false 556 S: 557 S: 2020-10-08T22:10:00Z 558 S: 559 S: 560 S: 561 S: 562 S: ABC-12345 563 S: 54321-XYZ 564 S: 565 S: 566 S: 568 4.2. EPP Transform Commands 570 EPP provides five commands to transform objects: to create 571 an instance of an object, to delete an instance of an 572 object, to extend the validity period of an object, 573 to manage object sponsorship changes, and to 574 change information associated with an object. 576 4.2.1. EPP Command 578 Create semantics do not apply to maintenance objects, so there is no 579 mapping defined for the EPP command. 581 4.2.2. EPP Command 583 Delete semantics do not apply to maintenance objects, so there is no 584 mapping defined for the EPP command. 586 4.2.3. EPP Command 588 Renew semantics do not apply to maintenance objects, so there is no 589 mapping defined for the EPP command. 591 4.2.4. EPP Command 593 Transfer semantics do not apply to maintenance objects, so there is 594 no mapping defined for the EPP command. 596 4.2.5. EPP Command 598 Update semantics do not apply to maintenance objects, so there is no 599 mapping defined for the EPP command. 601 5. Formal Syntax 603 The EPP Registry Maintenance schema is presented here. 604 The formal syntax presented here is a complete schema representation 605 of the object mapping suitable for automated validation of EPP XML 606 instances. The and tags are not part of 607 the schema; they are used to note the beginning and end of the 608 schema for URI registration purposes. 610 5.1. Registry Maintenance EPP Mapping Schema 612 613 614 621 624 625 626 627 628 Extensible Provisioning Protocol v1.0 629 Registry Maintenance Mapping Schema. 630 631 632 635 636 639 640 641 642 643 644 645 646 647 650 651 652 653 654 655 656 657 658 661 662 665 666 667 668 669 670 671 674 675 676 678 679 680 683 684 685 686 687 688 689 690 691 692 695 696 697 698 699 700 701 702 703 704 705 706 708 709 711 712 713 714 715 718 719 720 722 723 724 727 728 729 730 731 732 733 734 735 736 739 740 741 742 743 744 745 748 749 750 751 752 754 755 756 757 760 761 762 763 764 765 766 769 770 771 772 773 774 775 776 779 780 781 782 783 784 785 786 789 790 791 792 793 794 795 796 797 798 801 802 803 804 805 806 807 808 809 812 813 814 815 816 817 818 821 822 823 825 826 827 830 831 832 833 834 835 836 839 840 842 6. IANA Considerations 844 6.1. XML Namespace 846 This document uses URNs to describe XML namespaces and XML schemas 847 conforming to a registry mechanism defined in [RFC3688]. 849 Registration request for the maintenance namespace: 851 URI: urn:ietf:params:xml:ns:epp:maintenance-0.3 853 Registrant Contact: IESG 855 XML: None. Namespace URIs do not represent an XML specification. 857 Registration request for the maintenance schema: 859 URI: urn:ietf:params:xml:schema:maintenance-0.3 861 Registrant Contact: IESG 863 XML: See the "Formal Syntax" section of this document. 865 6.2. EPP Extension Registry 867 The following registration of the EPP Extension Registry, described 868 in [RFC7451], is requested: 870 Name of Extension: Registry Maintenance Notifications for the 871 Extensible Provisioning Protocol (EPP) 872 Document status: Standards Track 874 Reference: (insert the reference to RFC version of this document) 876 Registrant Name and Email Address: IESG 878 TLDs: Any 880 IPR Disclosure: None 882 Status: Active 884 Notes: None 886 7. Security Considerations 888 A server MUST only provide maintenance information for clients that 889 are authorized. If a client queries for a maintenance identifier, per 890 Section 4.1.3.1 "Info Maintenance Item", that it is not authorized to 891 access, the server MUST return an EPP error result code of 2201 892 [RFC5730]. The list of top-level domains or registry zones returned 893 in the "Info Maintenance Item" response SHOULD be filtered based on 894 the top-level domains or registry zones the client is authorized. 895 Authorization of poll messages is done at the time of poll message 896 insertion and not at the time of poll message consumption. 898 8. Implementation Status 900 Note to RFC Editor: Please remove this section and the reference to 901 [RFC7942] before publication. 903 This section records the status of known implementations of the 904 protocol defined by this specification at the time of posting of this 905 Internet-Draft, and is based on a proposal described in [RFC7942]. 906 The description of implementations in this section is intended to 907 assist the IETF in its decision processes in progressing drafts to 908 RFCs. Please note that the listing of any individual implementation 909 here does not imply endorsement by the IETF. Furthermore, no effort 910 has been spent to verify the information presented here that was 911 supplied by IETF contributors. This is not intended as, and must not 912 be construed to be, a catalog of available implementations or their 913 features. Readers are advised to note that other implementations may 914 exist. 916 According to [RFC7942], "this will allow reviewers and working groups 917 to assign due consideration to documents that have the benefit of 918 running code, which may serve as evidence of valuable experimentation 919 and feedback that have made the implemented protocols more mature. It 920 is up to the individual working groups to use this information as 921 they see fit". 923 8.1. GoDaddy Registry 925 Organization: GoDaddy Registry 926 Name: GoDaddy Registry 928 Description: GoDaddy Registry provides maintenance notifications to 929 their registrars. 931 Level of maturity: Production 933 Coverage: All aspects of the protocol according to the draft version 934 2 are implemented with further updates to come. 936 Licensing: Proprietary 938 Contact: quoc@registry.godaddy 940 URL: https://registry.godaddy 942 9. References 944 9.1. Normative References 946 [I.D.draft-ietf-regext-unhandled-namespaces] 947 Gould, J. and Casanova, M., "Extensible Provisioning 948 Protocol (EPP) Unhandled Namespaces", 949 (work in progress), February 2021. 952 [W3C-HTML5] Hickson, I., Berjon, R., Faulkner, S., Leithead, T., 953 Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", 954 W3C Recommendation REC-html5-20141028, October 2014, 955 . 957 Latest version available at . 959 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 960 Requirement Levels", BCP 14, RFC 2119, 961 DOI 10.17487/RFC2119, March 1997, 962 . 964 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 965 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 966 . 968 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 969 DOI 10.17487/RFC3688, January 2004, 970 . 972 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 973 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 974 . 976 [RFC5891] Klensin, J., "Internationalized Domain Names in 977 Applications (IDNA): Protocol", RFC 5891, 978 DOI 10.17487/RFC5891, August 2010, 979 . 981 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 982 Code: The Implementation Status Section", BCP 205, 983 RFC 7942, DOI 10.17487/RFC7942, July 2016, 984 . 986 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 987 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 988 May 2017, . 990 9.2. Informative References 992 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 993 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 994 February 2015, . 996 Appendix A. Change History 998 A.1. Change from draft-sattler-epp-poll-maintenance-response to 999 draft-sattler-epp-registry-maintenance 1001 Updated to be EPP based instead of JSON document. 1003 A.2. Change from draft-sattler-epp-registry-maintenance to 1004 draft-ietf-regext-epp-registry-maintenance 1006 Adopted by the REGEXT working group. 1008 A.3. Change from 00 to 01 1010 Clarified maint:description and maint:environment. Changed 1011 maint:description from complexType to simpleType. Fixed typo. 1012 Added acknowledgment. 1014 A.4. Change from 01 to 02 1016 Update language from Domain Name Registry to Registry. Clarified 1017 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 1018 to contain hostName and hostAddr. Changed maint:tlds from MUST to 1019 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 1020 unique id. 1022 A.5. Change from 02 to 03 1024 Changed maint:connection from MUST to SHOULD. 1026 A.6. Change from 03 to 04 1028 A lot of clarifications and editoral changes. 1030 A.7. Change from 04 to 05 1032 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 1033 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 1034 Clarified for retrieving maintenance items and the list. 1036 A.8. Change from 05 to 06 1038 Changed dates in examples to more recent dates. Renamed Query 1039 Maintenance Item and List to Info Maintenance Item and List. Removed 1040 blackout in favor of full. Added GoDaddy Registry implementation. 1042 A.9. Change from 06 to 07 1044 Removed IP addresses for . Editoral changes. 1046 A.10. Change from 07 to 08 1048 Editoral changes. Changed XML namespace and schema from 0.1 to 0.2. 1049 Added pollType to reflect create, update, or delete maintenance poll 1050 messages. 1052 A.11. Change from 08 to 09 1054 Editoral changes. Added new section "Migrating to Newer Versions of 1055 This Extension". 1057 A.12. Change from 09 to 10 1059 Editoral changes. Renamed "msg" to "name". Added "courtesy" and "end" 1060 to pollType. 1062 A.13. Change from 10 to 11 1064 Editoral changes. Added mime type to description. 1066 A.14. Change from 11 to 12 1068 Editoral changes. Changed XML namespace from 0.2 to 0.3. 1070 Acknowledgments 1072 The authors wish to thank the following persons for their feedback 1073 and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond 1074 Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig 1075 Marchant, and Andreas Huber. 1077 Authors' Addresses 1079 Tobias Sattler 1081 Email: tobias.sattler@me.com 1082 URI: https://tobiassattler.com 1084 Roger Carney 1085 GoDaddy Inc. 1086 14455 N. Hayden Rd. #219 1087 Scottsdale, AZ 85260 1088 US 1090 Email: rcarney@godaddy.com 1091 URI: http://www.godaddy.com 1093 Jody Kolker 1094 GoDaddy Inc. 1095 14455 N. Hayden Rd. #219 1096 Scottsdale, AZ 85260 1097 US 1099 Email: jkolker@godaddy.com 1100 URI: http://www.godaddy.com