idnits 2.17.1 draft-sattler-epp-registry-maintenance-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 26, 2019) is 1672 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force T. Sattler, Editor 2 Internet-Draft 3 Intended status: Standard Track R. Carney 4 Expires: March 25, 2020 J. Kolker 5 GoDaddy Inc. 6 September 26, 2019 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-sattler-epp-registry-maintenance-10 12 Abstract 13 This document describes an Extensible Provision Protocol (EPP) 14 mapping for domain name 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 March 25, 2020. 32 Copyright Notice 33 Copyright (c) 2019 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. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 50 2.1. Internationalized Domain Names . . . . . . . . . . . . . 3 51 2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3 52 2.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4 53 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 6 54 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 6 55 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 6 56 3.1.2. EPP Command . . . . . . . . . . . . . . . 6 57 3.1.3. EPP Command . . . . . . . . . . . . . . . . . 6 58 3.1.4. EPP Command . . . . . . . . . . . . . . . . . 9 59 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11 60 3.2.1. EPP Command . . . . . . . . . . . . . . . . 11 61 3.2.2. EPP Command . . . . . . . . . . . . . . . . 11 62 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 11 63 3.2.4. EPP Command . . . . . . . . . . . . . . . 11 64 3.2.5. EPP Command . . . . . . . . . . . . . . . . 11 65 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12 66 4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12 67 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 68 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16 69 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 70 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 71 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 72 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 73 8.1. Normative References . . . . . . . . . . . . . . . . . . 18 74 8.2. Informative References . . . . . . . . . . . . . . . . . 18 75 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 76 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 77 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 78 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19 79 A.4. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 19 80 A.5. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 19 81 A.6. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20 82 A.7. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 20 83 A.8. Change from 07 to EPPMAINT 00 . . . . . . . . . . . . . . 20 84 A.9. Change from EPPMAINT 00 to EPPMAINT 01 . . . . . . . . . 20 85 A.10. Change from EPPMAINT 01 to EPPMAINT 02 . . . . . . . . . 20 86 A.11. Change from EPPMAINT 02 to EPPMAINT 03 . . . . . . . . . 20 87 A.12. Change from EPPMAINT 03 to EPPMAINT 04 . . . . . . . . . 20 88 A.13. Change from EPPMAINT 04 to EPPMAINT 05 . . . . . . . . . 20 89 A.14. Change from EPPMAINT 05 to EPPMAINT 06 . . . . . . . . . 20 90 A.15. Change from EPPMAINT 06 to EPPMAINT 07 . . . . . . . . . 21 91 A.16. Change from EPPMAINT 07 to EPPMAINT 08 . . . . . . . . . 21 92 A.17. Change from EPPMAINT 08 to EPPMAINT 09 . . . . . . . . . 21 93 A.18. Change from EPPMAINT 09 to EPPMAINT 10 . . . . . . . . . 21 94 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 22 95 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 97 1. Introduction 99 Domain name registries usually conduct maintenances and inform domain 100 name registrars in different ways. Given the expansion of the DNS 101 namespace, it is now desirable to provide a method for EPP servers to 102 notify EPP clients as well as a method for EPP clients to query EPP 103 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 for upcoming maintenances. 110 1.1. Terminology and Definitions 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 114 document are to be interpreted as described in [RFC2119] when 115 specified in their uppercase forms. 117 XML is case sensitive. Unless stated otherwise, XML specifications 118 moreover, examples provided in this document MUST be interpreted in 119 the character case presented to develop a conforming implementation. 121 In examples, "C:" represents lines sent by a protocol client and 122 "S:" represents lines returned by a protocol server. Indentation and 123 white space in examples are provided only to illustrate element 124 relationships and are not a REQUIRED feature of this protocol. 126 2. Object Attributes 128 2.1. Internationalized Domain Names 130 Names of affected hosts MUST be provided in Punycode according to 131 [RFC5891]. 133 2.2. Dates and Times 135 All dates and times attribute values MUST be expressed in Universal 136 Coordinated Time (UTC) using the Gregorian calendar. The extended 137 date-time form using upper case "T" and "Z" characters defined in ISO 138 8601 [RFC3339] MUST be used to represent date-time values. 140 2.3. Maintenance Elements 142 The element describes a single registry maintenance 143 event during a specific period. This element will be used at EPP 144 messages and to extend the EPP command. 146 For creating a new maintenance the attribute MUST be 147 'active', the attribute MUST be set and the attribute 148 SHALL NOT be present. 150 For updating a maintenance the attribute MUST be 151 'active', the attributes and MUST be 152 set. 154 For deleting a maintenance the attribute MUST be 155 'inactive', and the attributes and MUST 156 be set. 158 159 MUST be present and a UUID according [RFC4122] and SHALL NOT be 160 changed if maintenance got updated or deleted. A human-readable 161 description of the maintenance is identified via an OPTIONAL 162 "msg" attribute. 164 165 MUST be present and contains one or more elements. 166 The server SHOULD NOT list systems which are not affected by the 167 maintenance. 169 170 MUST be present at least once and is an element of , 171 and . 173 174 MUST be present and indicates the name of the affected system, 175 such as 'EPP', 'WHOIS', 'DNS', 'Portal', etc. 177 178 MUST be present and indicates the affected maintained system 179 (host or IP address). 180 Hostname SHALL be Punycode according [RFC5891]. 181 IPv4 addresses SHALL be dotted-decimal notation. 182 An example of this textual representation is "192.0.2.0". 183 IPv6 addresses SHALL be according [RFC5952]. 184 An example of this textual representation is 185 "2001:db8::1:0:0:1". 187 188 MUST be present and contains the impact level; values SHOULD 189 either be 'blackout' or 'partial'. 191 192 MUST be present and indicates the type of the affected system; 193 values SHOULD either be 'production', 'ote', 'staging' or 'dev'. 195 196 MUST be present and indicates the start of the maintenance 197 according ISO 8601 [RFC3339]. 198 Format: YYYY-MM-DDThh:mm:ssTZ 200 201 MUST be present and indicates the end of the maintenance 202 according to ISO 8601 [RFC3339], and MUST be equal to or greater 203 than . 204 Format: YYYY-MM-DDThh:mm:ssTZ 206 207 MUST be present and contains the reason behind the maintenance; 208 values SHOULD either be 'planned' or 'emergency'. 210 211 MAY be present and contains URI to detailed maintenance 212 description. 214 215 MAY be present and provides a freeform description of the 216 maintenance without having to create and traverse an external 217 resource. The maximum length MUST NOT exceed 1024 bit. 219 220 MUST be present and contains elements. 222 223 MUST be present and contains the affected top-level domain. 224 Punycode encoded according to [RFC5891]. 226 227 MUST be present and contains and 228 . 230 231 MUST be present and indicates if a client needs to do something 232 that is connection-related, such as a reconnect. The value 233 SHALL be boolean. 235 236 MUST be present and indicates if a client needs to do something 237 that is implementation-related, such as a code change. The 238 value SHALL be boolean. 240 241 MUST be present and indicates the status of the maintenance. 242 The value SHALL be either 'active' or 'inactive'. 244 245 MUST be present and contains the creation date of the maintenance 246 according ISO 8601 [RFC3339]. 247 Format: YYYY-MM-DDThh:mm:ssTZ 249 250 MAY be present and contains the updated date of the maintenance 251 according to ISO 8601 [RFC3339], and if set MUST be equal to or 252 greater than . 253 Format: YYYY-MM-DDThh:mm:ssTZ 255 3. EPP Command Mapping 257 A detailed description of the EPP syntax and semantics can be found 258 in the EPP core protocol specification [RFC5730]. The command 259 mappings described here are specifically for the use to notify of 260 Registry Maintenances and Registry Maintenance object mapping. 262 3.1. EPP Query Commands 264 EPP [RFC5730] provides three commands to retrieve object information: 265 to determine if an object is known to the server, to 266 retrieve detailed information associated with an object, and 267 to retrieve object transfer status information. 269 3.1.1. EPP Command 271 Available check semantics do not apply to maintenance objects, so 272 there is no mapping defined for the EPP command. 274 3.1.2. EPP Command 276 Transfer semantics do not apply to maintenance objects, so there is 277 no mapping defined for the EPP command. 279 3.1.3. EPP Command 281 EPP provides the command that is used to retrieve registry 282 maintenance information. In addition to the standard EPP command 283 elements, the command MUST contain a 284 element that identifies the maintenance namespace. The 285 element MUST contain a child element. It is either to 286 retrieve a specific maintenance notification or to 287 query all maintenance notifications. 289 Example command with to get one specific 290 maintenance: 292 C: 293 C: 294 C: 295 C: 296 C: 298 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 299 C: 300 C: 301 C: ABC-12345 302 C: 303 C: 305 Example response for one specific maintenance notification: 307 S: 308 S: 309 S: 310 S: 311 S: Command completed successfully 312 S: 313 S: 314 S: 316 S: 317 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 318 S: 319 S: 320 S: 321 S: EPP 322 S: epp.registry.example 323 S: blackout 324 S: 325 S: 326 S: 327 S: 2017-09-30T06:00:00Z 328 S: 2017-09-30T14:25:57Z 329 S: planned 330 S: 331 S: https://www.registry.example/notice?123 332 S: 333 S: free text 334 S: 335 S: example 336 S: test 337 S: 338 S: 339 S: false 340 S: false 341 S: 342 S: active 343 S: 2017-03-08T22:10:00Z 344 S: 345 S: 346 S: 347 S: 348 S: ABC-12345 349 S: 54321-XYZ 350 S: 351 S: 352 S: 354 Example command with to query all maintenances: 356 C: 357 C: 358 C: 359 C: 360 C: 362 C: 363 C: 364 C: 365 C: ABC-12345 366 C: 367 C: 369 Example response querying all maintenances: 371 S: 372 S: 373 S: 374 S: 375 S: Command completed successfully 376 S: 377 S: 378 S: 380 S: 381 S: 382 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 383 S: 384 S: 2017-04-30T06:00:00Z 385 S: 2017-04-30T07:00:00Z 386 S: 2017-02-08T22:10:00Z 387 S: 388 S: 389 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 390 S: 391 S: 2017-06-15T04:30:00Z 392 S: 2017-06-15T05:30:00Z 393 S: 2017-02-08T22:10:00Z 394 S: 2017-03-08T20:11:00Z 395 S: 396 S: 397 S: 398 S: 399 S: 400 S: ABC-12345 401 S: 54321-XYZ 402 S: 403 S: 404 S: 406 3.1.4. EPP Command 408 The EPP command and response is defined in Section 2.9.2.3 of 409 [RFC5730]. The Registry Maintenance Notification is included in the 410 EPP response of [RFC5730]. 412 For the Registry Maintenance Notification, there are three types of 413 poll messages. The poll messages apply whenever the domain name 414 registry creates, updates or deletes maintenance. In the case of 415 a Registry Maintenance specific message, a element 416 will be included within the element of the standard 417 response. 419 The element will include a reference to the 420 Registry Maintenance namespace. EPP data contained within the 421 element is formatted according to the 422 maintenance-poll schema. 424 Example command: 426 C: 427 C: 428 C: 429 C: 430 C: ABC-12345 431 C: 432 C: 434 Example response with the Registry Maintenance poll message: 436 S: 437 S: 438 S: 439 S: 440 S: Command completed successfully; ack to dequeue 441 S: 442 S: 443 S: 2017-02-08T22:10:00Z 444 S: Registry Maintenance Notification 445 S: 446 S: 447 S: 449 S: 450 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 451 S: 452 S: 453 S: EPP 454 S: epp.registry.example 455 S: blackout 456 S: 457 S: 458 S: 459 S: 2017-10-30T06:00:00Z 460 S: 2017-10-30T14:25:57Z 461 S: planned 462 S: 463 S: https://www.registry.example/notice?123 464 S: 465 S: 466 S: example 467 S: test 468 S: 469 S: 470 S: false 471 S: false 472 S: 473 S: active 474 S: 2017-02-08T22:10:00Z 475 S: 476 S: 477 S: 478 S: 479 S: ABC-12345 480 S: 54321-XYZ 481 S: 482 S: 483 S: 485 3.2. EPP Transform Commands 487 EPP provides five commands to transform objects: to create 488 an instance of an object, to delete an instance of an 489 object, to extend the validity period of an object, 490 to manage object sponsorship changes, and to 491 change information associated with an object. 493 3.2.1. EPP Command 495 Create semantics do not apply to maintenance objects, so there is no 496 mapping defined for the EPP command. 498 3.2.2. EPP Command 500 Delete semantics do not apply to maintenance objects, so there is no 501 mapping defined for the EPP command. 503 3.2.3. EPP Command 505 Renew semantics do not apply to maintenance objects, so there is no 506 mapping defined for the EPP command. 508 3.2.4. EPP Command 510 Transfer semantics do not apply to maintenance objects, so there is 511 no mapping defined for the EPP command. 513 3.2.5. EPP Command 515 Update semantics do not apply to maintenance objects, so there is no 516 mapping defined for the EPP command. 518 4. Formal Syntax 520 One schema is presented here that is the EPP Registry Maintenance 521 schema. 523 The formal syntax presented here is a complete schema representation 524 of the object mapping suitable for automated validation of EPP XML 525 instances. The BEGIN and END tags are not part of the schema; they 526 are used to note the beginning and end of the schema for URI 527 registration purposes. 529 4.1. Registry Maintenance EPP Mapping Schema 531 BEGIN 532 533 540 543 544 546 547 548 Extensible Provisioning Protocol v1.0 549 Maintenance Mapping Schema. 550 551 553 556 558 561 562 563 564 565 567 568 569 570 571 573 576 577 578 579 580 581 582 584 587 589 592 593 594 595 596 597 599 602 603 604 606 607 609 612 613 614 615 616 617 618 619 620 621 624 625 626 627 628 629 630 631 632 633 635 636 637 638 639 640 641 643 646 647 648 650 651 653 656 657 658 659 660 661 663 666 667 668 669 670 672 675 676 677 678 679 680 681 683 686 687 688 689 690 691 692 693 694 696 699 700 701 702 703 704 705 706 708 711 712 713 714 715 716 718 721 722 723 725 726 727 730 731 732 733 734 735 737 740 741 742 743 744 745 747 750 751 END 753 5. IANA Considerations 755 5.1. XML Namespace 757 This document uses URNs to describe XML namespaces and XML schemas 758 conforming to a registry mechanism defined in [RFC3688]. 760 Registration request for the maintenance namespace: 762 URI: urn:ietf:params:xml:ns:maintenance-1.0 764 Registrant Contact: IESG 766 XML: None. Namespace URIs do not represent an XML specification. 768 Registration request for the maintenance schema: 770 URI: urn:ietf:params:xml:schema:maintenance-1.0 772 Registrant Contact: IESG 774 XML: See the "Formal Syntax" section of this document. 776 5.2. EPP Extension Registry 778 The following registration of the EPP Extension Registry, described 779 in [RFC7451], is requested: 781 Name of Extension: "Registry Maintenance Notifications for the 782 Extensible Provisioning Protocol (EPP)" 784 Document status: Standards Track 786 Reference: (insert the reference to RFC version of this document) 788 Registrant Name and Email Address: IESG, 790 TLDs: Any 792 IPR Disclosure: None 794 Status: Active 796 Notes: None 798 6. Security Considerations 800 The mapping extensions described in this document do not provide any 801 security services beyond those specified by EPP [RFC5730] and 802 protocol layers used by EPP. The security considerations described in 803 these other specifications apply to this specification as well. 805 7. Implementation Status 807 Note to RFC Editor: Please remove this section and the reference to 808 [RFC7942] before publication. 810 This section records the status of known implementations of the 811 protocol defined by this specification at the time of posting of this 812 Internet-Draft, and is based on a proposal described in [RFC7942]. 813 The description of implementations in this section is intended to 814 assist the IETF in its decision processes in progressing drafts to 815 RFCs. Please note that the listing of any individual implementation 816 here does not imply endorsement by the IETF. Furthermore, no effort 817 has been spent to verify the information presented here that was 818 supplied by IETF contributors. This is not intended as, and must not 819 be construed to be, a catalog of available implementations or their 820 features. Readers are advised to note that other implementations may 821 exist. 823 According to [RFC7942], "this will allow reviewers and working groups 824 to assign due consideration to documents that have the benefit of 825 running code, which may serve as evidence of valuable experimentation 826 and feedback that have made the implemented protocols more mature. It 827 is up to the individual working groups to use this information as 828 they see fit". 830 Add implementation details once available. 832 8. References 834 8.1. Normative References 836 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 837 Requirement Levels", BCP 14, RFC 2119, March 1997, 838 . 840 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 841 DOI 10.17487/RFC3688, January 2004, 842 . 844 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 845 STD 69, RFC 5730, August 2009, 846 . 848 8.2. Informative References 850 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 851 Internet: Timestamps", RFC 3339, July 2002, 852 . 854 [RFC5891] Klensin, J., "Internationalized Domain Names in 855 Applications (IDNA): Protocol", RFC 5891, August 2010, 856 . 858 [RFC4122] Leach, P., Mealling, M. and Salz, R., "A Universally 859 Unique IDentifier (UUID) URN Namespace", RFC 4122, July 860 2015, 861 . 863 [RFC5952] Kawamura, S. and Kawashima, M., "A Recommendation for IPv6 864 Address Text Representation", RFC 5952, August 2010, 865 . 867 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 868 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 869 February 2015, . 871 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 872 Running Code: The Implementation Status Section", RFC 873 7942, July 2016, 874 . 876 Appendix A. Change History 878 A.1. Change from 00 to 01 880 Removed JSON Schema. Clarified unique id with UUID. Added Common Data 881 Structures for a better explanation. Fixed EPP poll response example. 882 Added und fixed References. 884 A.2. Change from 01 to 02 886 Clarified host field. Added TLDs to Common Data Structure. Added 887 Internationalization Considerations. Changed authors address and 888 contact details. 890 A.3. Change from 02 to 03 892 Added date-time Values to Internationalization Considerations. Sorted 893 Terminology and Definitions alphabetically. Changed start and end 894 date-time. Changed Reference URI to HTTPS. 896 A.4. Change from 03 to 04 898 Added Acknowledgements. Clarified UUID field to be not changed at all 899 Clarified environment field with production, ote, staging and dev. 900 Clarified connection and implementation fields. Fixed writing of 901 systems field. Removed author's private address. Moved this draft 902 from Experimental to Standard Track. 904 A.5. Change from 04 to 05 906 Changed title of this draft to be more specific. Added changelog. 907 Split References into Normative and Informative References. Clarified 908 Common Data Types. Rephrased Abstract and Introduction. Added 909 Implementation Status Section. 911 A.6. Change from 05 to 06 913 Added IANA Considerations. Changed URIs from HTTP to HTTPS. Added 914 new main Section 4. EPP Command Mapping. Added new JSON field 915 'purpose' for announce, change or cancel of a maintenance 916 notification. 918 A.7. Change from 06 to 07 920 Fixed typo in Section 3.4. and added missing comma in the example of 921 Section 4.1. Added the field specification to help facilitate the 922 adoption of this document. Changed possible purposes to create, 923 update and delete to be closer to the EPP syntax. Cleaned 924 whitespaces. Updated Acknowledgements. 926 A.8. Change from 07 to EPPMAINT 00 928 Removed JSON payload in message and switched to specific 929 EPP message. Extended EPP command to provide details 930 on specific maintenance or list all maintenances. 932 A.9. Change from EPPMAINT 00 to EPPMAINT 01 934 Fixed typos and added missing changelog text for EPPMAINT 00. 935 Added BEGIN and END flag to the XML schema. Removed Character 936 Encoding Section. Fixed indentation in Section 2.3. 938 A.10. Change from EPPMAINT 01 to EPPMAINT 02 940 Changed the element to . Fixed 941 indentation in Section 4.1. Cleaned up whitespaces. 943 A.11. Change from EPPMAINT 02 to EPPMAINT 03 945 Changed reference from RFC3492 to RFC5891. Fixed minor typos. 946 Added for a freeform maintenance description 947 with a maximum length of 1024. Added optional "msg" attribute to 948 and . 950 A.12. Change from EPPMAINT 03 to EPPMAINT 04 952 Fixed minor typos and added one acknowledgment. 954 A.13. Change from EPPMAINT 04 to EPPMAINT 05 956 Added missing whitespace. Fixed dates in examples. Added 957 clarification that must be equal to or greater than 958 , same applies for and if 959 set. 961 A.14. Change from EPPMAINT 05 to EPPMAINT 06 963 Added Roger Carney and Jody Kolker as Co-Authors to this draft. 965 A.15. Change from EPPMAINT 06 to EPPMAINT 07 967 Changed Acknowledgements. 969 A.16. Change from EPPMAINT 07 to EPPMAINT 08 971 Added IANA consideration section 5.1. and 5.2. Added editor flag 972 to author. Changed abstract and introduction. Minor formatting 973 changes. 975 A.17. Change from EPPMAINT 08 to EPPMAINT 09 977 Editorial changes. 979 A.18. Change from EPPMAINT 09 to EPPMAINT 10 981 Editorial changes. 983 Appendix B. Acknowledgements 985 The authors wish to thank the following persons for their feedback 986 and suggestions (sorted alphabetically by company): 988 o Patrick Mevzek 989 o Neal McPherson, 1&1 IONOS 990 o Anthony Eden, DNSimple 991 o Christopher Martens, Donuts 992 o Raymond Zylstra, Neustar 993 o Andreas Huber, united-domains 994 o Craig Marchant, VentraIP 995 o James Gould, Verisign 997 Authors' Addresses 999 Tobias Sattler 1001 Email: tobias.sattler@me.com 1002 URI: https://tobiassattler.com 1004 Roger Carney 1005 GoDaddy Inc. 1006 14455 N. Hayden Rd. #219 1007 Scottsdale, AZ 85260 1008 US 1010 Email: rcarney@godaddy.com 1011 URI: http://www.godaddy.com 1013 Jody Kolker 1014 GoDaddy Inc. 1015 14455 N. Hayden Rd. #219 1016 Scottsdale, AZ 85260 1017 US 1019 Email: jkolker@godaddy.com 1020 URI: http://www.godaddy.com