idnits 2.17.1 draft-sattler-epp-registry-maintenance-08.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 (December 6, 2018) is 1960 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: June 5, 2019 J. Kolker 5 GoDaddy Inc. 6 December 6, 2018 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-sattler-epp-registry-maintenance-08 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 June 5, 2019. 32 Copyright Notice 33 Copyright (c) 2018 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 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 21 93 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 95 1. Introduction 97 Domain name registries usually conduct maintenances and inform domain 98 name registrars via different ways. Given the expansion of the DNS 99 namespace, it is now desirable to provide a method for EPP servers to 100 notify EPP clients as well as a method for EPP clients to query EPP 101 servers for upcoming maintenances. 103 This document describes an extension mapping for version 1.0 of the 104 Extensible Provision Protocol [RFC5730]. This mapping provides a 105 mechanism by which EPP servers may notify and EPP clients to query 106 for upcoming maintenances. 108 1.1. Terminology and Definitions 110 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 111 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 112 document are to be interpreted as described in [RFC2119] when 113 specified in their uppercase forms. 115 XML is case sensitive. Unless stated otherwise, XML specifications 116 and examples provided in this document MUST be interpreted in the 117 character case presented in order to develop a conforming 118 implementation. 120 In examples, "C:" represents lines sent by a protocol client and 121 "S:" represents lines returned by a protocol server. Indentation and 122 white space in examples are provided only to illustrate element 123 relationships and are not a REQUIRED feature of this protocol. 125 2. Object Attributes 127 2.1. Internationalized Domain Names 129 Names of affected hosts MUST be provided in Punycode according to 130 [RFC5891]. 132 2.2. Dates and Times 134 All dates and times attribute values MUST be expressed in Universal 135 Coordinated Time (UTC) using the Gregorian calendar. The extended 136 date-time form using upper case "T" and "Z" characters defined in ISO 137 8601 [RFC3339] MUST be used to represent date-time values. 139 2.3. Maintenance Elements 141 The element describes a single domain name registry 142 maintenance event during a specific time period. This element will 143 be used at EPP messages and to extend the EPP command. 145 For creating a new maintenance the attribute MUST be 146 'active', the attribute MUST be set and the attribute 147 SHALL NOT be present. 149 For updating a maintenance the attribute MUST be 150 'active', the attributes and MUST be 151 set. 153 For deleting a maintenance the attribute MUST be 154 'inactive', and the attributes and MUST 155 be set. 157 158 MUST be present and an UUID according [RFC4122] and SHALL NOT be 159 changed if maintenance got updated or deleted. A human-readable 160 description of the maintenance is identified via an OPTIONAL 161 "msg" attribute. 163 164 MUST be present and contains one or more elements. 165 The server SHOULD NOT list systems which are not affected by the 166 maintenance. 168 169 MUST be present at least once and is an element of , 170 and 172 173 MUST be present and indicates the name of the affected system, 174 such as 'EPP', 'WHOIS', 'DNS', 'Portal', etc. 176 177 MUST be present and indicates the affected maintained system 178 (host or IP address). 179 Hostname SHALL be Punycode according [RFC5891]. 180 IPv4 addresses SHALL be dotted-decimal notation. 181 An example of this textual representation is "192.0.2.0". 182 IPv6 addresses SHALL be according [RFC5952]. 183 An example of this textual representation is 184 "2001:db8::1:0:0:1". 186 187 MUST be present and contains the impact level; values SHOULD 188 either be 'blackout' or 'partial' 190 191 MUST be present and indicates the type of the affected system; 192 values SHOULD either be 'production', 'ote', 'staging' or 'dev' 194 195 MUST be present and indicates the start of the maintenance 196 according ISO 8601 [RFC3339] 197 Format: YYYY-MM-DDThh:mm:ssTZ 199 200 MUST be present and indicates the end of the maintenance 201 according ISO 8601 [RFC3339], and MUST be equal to or greater 202 than 203 Format: YYYY-MM-DDThh:mm:ssTZ 205 206 MUST be present and contains the reason behind the maintenance; 207 values SHOULD either be 'planned' or 'emergency' 209 210 MAY be present and contains URI to detailed maintenance 211 description 213 214 MAY be present and provides a freeform description of the 215 maintenance without having to create and traverse an external 216 resource. The maximum length MUST NOT exceed 1024 bit. 218 219 MUST be present and contains elements 221 222 MUST be present and contains the affected top-level domain. 223 Punycode encoded according [RFC5891] 225 226 MUST be present and contains and 227 229 230 MUST be present and indicates if a client needs to do something 231 that is connection related, such as a reconnect. The value 232 SHALL boolean. 234 235 MUST be present and indicates if a client needs to do something 236 that is implementation related, such as a code change. The 237 value SHALL be boolean. 239 240 MUST be present and indicates the status of the maintenance. 241 The value SHALL be either 'active' or 'inactive' 243 244 MUST be present and contains the creation date of the maintenance 245 according ISO 8601 [RFC3339] 246 Format: YYYY-MM-DDThh:mm:ssTZ 248 249 MAY be present and contains the updated date of the maintenance 250 according ISO 8601 [RFC3339], and if set MUST be equal to or 251 greater than 252 Format: YYYY-MM-DDThh:mm:ssTZ 254 3. EPP Command Mapping 256 A detailed description of the EPP syntax and semantics can be found 257 in the EPP core protocol specification [RFC5730]. The command 258 mappings described here are specifically for the use to notify of 259 Registry Maintenances and Registry Maintenance object mapping. 261 3.1. EPP Query Commands 263 EPP [RFC5730] provides three commands to retrieve object information: 264 to determine if an object is known to the server, to 265 retrieve detailed information associated with an object, and 266 to retrieve object transfer status information. 268 3.1.1. EPP Command 270 Available check semantics do not apply to maintenance objects, so 271 there is no mapping defined for the EPP command. 273 3.1.2. EPP Command 275 Transfer semantics do not apply to maintenance objects, so there is 276 no mapping defined for the EPP command. 278 3.1.3. EPP Command 280 EPP provides the command that is used to retrieve registry 281 maintenance information. In addition to the standard EPP command 282 elements, the command MUST contain a 283 element that identifies the maintenance namespace. The 284 element MUST contain a child element. It is either to 285 retrieve a specific maintenance notification or to 286 query all maintenance notifications. 288 Example command with to get one specific 289 maintenance: 291 C: 292 C: 293 C: 294 C: 295 C: 297 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 298 C: 299 C: 300 C: ABC-12345 301 C: 302 C: 304 Example response for one specific maintenance notification: 306 S: 307 S: 308 S: 309 S: 310 S: Command completed successfully 311 S: 312 S: 313 S: 315 S: 316 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 317 S: 318 S: 319 S: 320 S: EPP 321 S: epp.registry.example 322 S: blackout 323 S: 324 S: 325 S: 326 S: 2017-09-30T06:00:00Z 327 S: 2017-09-30T14:25:57Z 328 S: planned 329 S: 330 S: https://www.registry.example/notice?123 331 S: 332 S: free text 333 S: 334 S: example 335 S: test 336 S: 337 S: 338 S: false 339 S: false 340 S: 341 S: active 342 S: 2017-03-08T22:10:00Z 343 S: 344 S: 345 S: 346 S: 347 S: ABC-12345 348 S: 54321-XYZ 349 S: 350 S: 351 S: 353 Example command with to query all maintenances: 355 C: 356 C: 357 C: 358 C: 359 C: 361 C: 362 C: 363 C: 364 C: ABC-12345 365 C: 366 C: 368 Example response querying all maintenances: 370 S: 371 S: 372 S: 373 S: 374 S: Command completed successfully 375 S: 376 S: 377 S: 379 S: 380 S: 381 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 382 S: 383 S: 2017-04-30T06:00:00Z 384 S: 2017-04-30T07:00:00Z 385 S: 2017-02-08T22:10:00Z 386 S: 387 S: 388 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 389 S: 390 S: 2017-06-15T04:30:00Z 391 S: 2017-06-15T05:30:00Z 392 S: 2017-02-08T22:10:00Z 393 S: 2017-03-08T20:11:00Z 394 S: 395 S: 396 S: 397 S: 398 S: 399 S: ABC-12345 400 S: 54321-XYZ 401 S: 402 S: 403 S: 405 3.1.4. EPP Command 407 The EPP command and response is defined in Section 2.9.2.3 of 408 [RFC5730]. The Registry Maintenance Notification is included in the 409 EPP response of [RFC5730]. 411 For the Registry Maintenance Notification, there are three types of 412 poll messages. The poll messages apply whenever the domain name 413 registry creates, updates or deletes a maintenance. In the case of 414 a Registry Maintenance specific message, a element 415 will be included within the element of the standard 416 response. 418 The element will include a reference to the 419 Registry Maintenance namespace. EPP data contained within the 420 element is formatted according to the 421 maintenance-poll schema. 423 Example command: 425 C: 426 C: 427 C: 428 C: 429 C: ABC-12345 430 C: 431 C: 433 Example response with the Registry Maintenance poll message: 435 S: 436 S: 437 S: 438 S: 439 S: Command completed successfully; ack to dequeue 440 S: 441 S: 442 S: 2017-02-08T22:10:00Z 443 S: Registry Maintenance Notification 444 S: 445 S: 446 S: 448 S: 449 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 450 S: 451 S: 452 S: EPP 453 S: epp.registry.example 454 S: blackout 455 S: 456 S: 457 S: 458 S: 2017-10-30T06:00:00Z 459 S: 2017-10-30T14:25:57Z 460 S: planned 461 S: 462 S: https://www.registry.example/notice?123 463 S: 464 S: 465 S: example 466 S: test 467 S: 468 S: 469 S: false 470 S: false 471 S: 472 S: active 473 S: 2017-02-08T22:10:00Z 474 S: 475 S: 476 S: 477 S: 478 S: ABC-12345 479 S: 54321-XYZ 480 S: 481 S: 482 S: 484 3.2. EPP Transform Commands 486 EPP provides five commands to transform objects: to create 487 an instance of an object, to delete an instance of an 488 object, to extend the validity period of an object, 489 to manage object sponsorship changes, and to 490 change information associated with an object. 492 3.2.1. EPP Command 494 Create semantics do not apply to maintenance objects, so there is no 495 mapping defined for the EPP command. 497 3.2.2. EPP Command 499 Delete semantics do not apply to maintenance objects, so there is no 500 mapping defined for the EPP command. 502 3.2.3. EPP Command 504 Renew semantics do not apply to maintenance objects, so there is no 505 mapping defined for the EPP command. 507 3.2.4. EPP Command 509 Transfer semantics do not apply to maintenance objects, so there is 510 no mapping defined for the EPP command. 512 3.2.5. EPP Command 514 Update semantics do not apply to maintenance objects, so there is no 515 mapping defined for the EPP command. 517 4. Formal Syntax 519 One schema is presented here that is the EPP Registry Maintenance 520 schema. 522 The formal syntax presented here is a complete schema representation 523 of the object mapping suitable for automated validation of EPP XML 524 instances. The BEGIN and END tags are not part of the schema; they 525 are used to note the beginning and ending of the schema for URI 526 registration purposes. 528 4.1. Registry Maintenance EPP Mapping Schema 530 BEGIN 531 532 539 542 543 545 546 547 Extensible Provisioning Protocol v1.0 548 Maintenance Mapping Schema. 549 550 552 555 557 560 561 562 563 564 566 567 568 569 570 572 575 576 577 578 579 580 581 583 586 588 591 592 593 594 595 596 598 601 602 603 605 606 608 611 612 613 614 615 616 617 618 619 620 623 624 625 626 627 628 629 630 631 632 634 635 636 637 638 639 640 642 645 646 647 649 650 652 655 656 657 658 659 660 662 665 666 667 668 669 671 674 675 676 677 678 679 680 682 685 686 687 688 689 690 691 692 693 695 698 699 700 701 702 703 704 705 707 710 711 712 713 714 715 717 720 721 722 724 725 726 729 730 731 732 733 734 736 739 740 741 742 743 744 746 749 750 END 752 5. IANA Considerations 754 5.1. XML Namespace 756 This document uses URNs to describe XML namespaces and XML schemas 757 conforming to a registry mechanism described in [RFC3688]. 759 Registration request for the maintenance namespace: 761 URI: urn:ietf:params:xml:ns:maintenance-1.0 763 Registrant Contact: IESG 765 XML: None. Namespace URIs do not represent an XML specification. 767 Registration request for the maintenance schema: 769 URI: urn:ietf:params:xml:schema:maintenance-1.0 771 Registrant Contact: IESG 773 XML: See the "Formal Syntax" section of this document. 775 5.2. EPP Extension Registry 777 The following registration of the EPP Extension Registry, described 778 in [RFC7451], is requested: 780 Name of Extension: "Registry Maintenance Notifications for the 781 Extensible Provisioning Protocol (EPP)" 783 Document status: Standards Track 785 Reference: (insert reference to RFC version of this document) 787 Registrant Name and Email Address: IESG, 789 TLDs: Any 791 IPR Disclosure: None 793 Status: Active 795 Notes: None 797 6. Security Considerations 799 The mapping extensions described in this document do not provide any 800 security services beyond those described by EPP [RFC5730] and 801 protocol layers used by EPP. The security considerations described in 802 these other specifications apply to this specification as well. 804 7. Implementation Status 806 Note to RFC Editor: Please remove this section and the reference to 807 [RFC7942] before publication. 809 This section records the status of known implementations of the 810 protocol defined by this specification at the time of posting of this 811 Internet-Draft, and is based on a proposal described in [RFC7942]. 812 The description of implementations in this section is intended to 813 assist the IETF in its decision processes in progressing drafts to 814 RFCs. Please note that the listing of any individual implementation 815 here does not imply endorsement by the IETF. Furthermore, no effort 816 has been spent to verify the information presented here that was 817 supplied by IETF contributors. This is not intended as, and must not 818 be construed to be, a catalog of available implementations or their 819 features. Readers are advised to note that other implementations may 820 exist. 822 According to [RFC7942], "this will allow reviewers and working groups 823 to assign due consideration to documents that have the benefit of 824 running code, which may serve as evidence of valuable experimentation 825 and feedback that have made the implemented protocols more mature. It 826 is up to the individual working groups to use this information as 827 they see fit". 829 Add implementation details once available. 831 8. References 833 8.1. Normative References 835 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 836 Requirement Levels", BCP 14, RFC 2119, March 1997, 837 . 839 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 840 DOI 10.17487/RFC3688, January 2004, 841 . 843 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 844 STD 69, RFC 5730, August 2009, 845 . 847 8.2. Informative References 849 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 850 Internet: Timestamps", RFC 3339, July 2002, 851 . 853 [RFC5891] Klensin, J., "Internationalized Domain Names in 854 Applications (IDNA): Protocol", RFC 5891, August 2010, 855 . 857 [RFC4122] Leach, P., Mealling, M. and Salz, R., "A Universally 858 Unique IDentifier (UUID) URN Namespace", RFC 4122, July 859 2015, 860 . 862 [RFC5952] Kawamura, S. and Kawashima, M., "A Recommendation for IPv6 863 Address Text Representation", RFC 5952, August 2010, 864 . 866 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 867 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 868 February 2015, . 870 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 871 Running Code: The Implementation Status Section", RFC 872 7942, July 2016, 873 . 875 Appendix A. Change History 877 A.1. Change from 00 to 01 879 Removed JSON Schema. Clarified unique id with UUID. Added Common Data 880 Structures for better explanation. Fixed EPP poll response example. 881 Added und fixed References. 883 A.2. Change from 01 to 02 885 Clarified host field. Added TLDs to Common Data Structure. Added 886 Internationalization Considerations. Changed authors address and 887 contact details. 889 A.3. Change from 02 to 03 891 Added date-time Values to Internationalization Considerations. Sorted 892 Terminology and Definitions alphabetically. Changed start and end 893 date-time. Changed Reference URI to HTTPS. 895 A.4. Change from 03 to 04 897 Added Acknowledgements. Clarified UUID field to be not changed at all 898 Clarified environment field with production, ote, staging and dev. 899 Clarified connection and implementation fields. Fixed writing of 900 systems field. Removed author's private address. Moved this draft 901 from Experimental to Standard Track. 903 A.5. Change from 04 to 05 905 Changed title of this draft to be more specific. Added Change Log. 906 Split References into Normative and Informative References. Clarified 907 Common Data Types. Rephrased Abstract and Introduction. Added 908 Implementation Status Section. 910 A.6. Change from 05 to 06 912 Added IANA Considerations. Changed URIs from http to https. Added 913 new main Section 4. EPP Command Mapping. Added new JSON field purpose 914 for announce, change or cancel of a maintenance notification. 916 A.7. Change from 06 to 07 918 Fixed typo in Section 3.4. and added missing comma in the example of 919 Section 4.1. Added the field specification to help facilitate the 920 adoption of this document. Changed possible purposes to create, 921 update and delete to be closer to the EPP syntax. Cleaned 922 whitespaces. Updated Acknowledgements. 924 A.8. Change from 07 to EPPMAINT 00 926 Removed JSON payload in message and switched to specific 927 EPP message. Extended EPP command to provide details 928 on specific maintenance or list all maintenances. 930 A.9. Change from EPPMAINT 00 to EPPMAINT 01 932 Fixed typos and added missing change log text for EPPMAINT 00. 933 Added BEGIN and END flag to XML schema. Removed Character Encoding 934 Section. Fixed indentation in Section 2.3. 936 A.10. Change from EPPMAINT 01 to EPPMAINT 02 938 Changed the element to . Fixed 939 indentation in Section 4.1. Cleaned up whitespaces. 941 A.11. Change from EPPMAINT 02 to EPPMAINT 03 943 Changed reference from RFC3492 to RFC5891. Fixed minor typos. 944 Added for a freeform maintenance description 945 with a maximum length of 1024. Added optional "msg" attribute to 946 and . 948 A.12. Change from EPPMAINT 03 to EPPMAINT 04 950 Fixed minor typos and added one acknowledgement. 952 A.13. Change from EPPMAINT 04 to EPPMAINT 05 954 Added missing whitespace. Fixed dates in examples. Added 955 clarification that must be equal to or greater than 956 , same applies for and if 957 set. 959 A.14. Change from EPPMAINT 05 to EPPMAINT 06 961 Added Roger Carney and Jody Kolker as Co-Authors to this draft. 963 A.15. Change from EPPMAINT 06 to EPPMAINT 07 965 Changed Acknowledgements. 967 A.16. Change from EPPMAINT 07 to EPPMAINT 08 969 Added IANA consideration section 5.1. and 5.2. Added editor flag 970 to author. Changed abstract and introduction. Minor formatting 971 changes. 973 Appendix B. Acknowledgements 975 The authors wish to thank the following persons for their feedback 976 and suggestions (sorted alphabetically by company): 978 o Patrick Mevzek 979 o Neal McPherson, 1&1 IONOS 980 o Anthony Eden, DNSimple 981 o Christopher Martens, Donuts 982 o Raymond Zylstra, Neustar 983 o Andreas Huber, united-domains 984 o Craig Marchant, VentraIP 985 o James Gould, Verisign 987 Authors' Addresses 989 Tobias Sattler 991 Email: tobias.sattler@me.com 992 URI: https://tobiassattler.com 994 Roger Carney 995 GoDaddy Inc. 996 14455 N. Hayden Rd. #219 997 Scottsdale, AZ 85260 998 US 1000 Email: rcarney@godaddy.com 1001 URI: http://www.godaddy.com 1003 Jody Kolker 1004 GoDaddy Inc. 1005 14455 N. Hayden Rd. #219 1006 Scottsdale, AZ 85260 1007 US 1009 Email: jkolker@godaddy.com 1010 URI: http://www.godaddy.com