idnits 2.17.1 draft-ietf-regext-epp-registry-maintenance-06.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 8, 2020) is 1234 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 (IETF) T. Sattler 2 Internet-Draft 3 Intended status: Standards Track R. Carney 4 Expires: June 30, 2021 J. Kolker 5 GoDaddy Inc. 6 December 8, 2020 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-06 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) 2020 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.3.1. Info Maintenance Item . . . . . . . . . . . . . . . 6 59 3.1.3.2. Info Maintenance List . . . . . . . . . . . . . . . 8 60 3.1.4. EPP Command . . . . . . . . . . . . . . . . . 9 61 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 11 62 3.2.1. EPP Command . . . . . . . . . . . . . . . . 11 63 3.2.2. EPP Command . . . . . . . . . . . . . . . . 11 64 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 11 65 3.2.4. EPP Command . . . . . . . . . . . . . . . 11 66 3.2.5. EPP Command . . . . . . . . . . . . . . . . 11 67 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12 68 4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 12 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 70 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 71 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 72 6. Security Considerations . . . . . . . . . . . . . . . . . . . 18 73 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 74 7.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 18 75 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 76 8.1. Normative References . . . . . . . . . . . . . . . . . . 19 77 8.2. Informative References . . . . . . . . . . . . . . . . . 19 78 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 79 A.1. Change from draft-sattler-epp-poll-maintenance-response to 80 draft-sattler-epp-registry-maintenance . . . . . . . . . 19 81 A.2. Change from draft-sattler-epp-registry-maintenance to 82 draft-ietf-regext-epp-registry-maintenance . . . . . . . 19 83 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 84 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 20 85 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 20 86 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20 87 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20 88 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 20 89 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 21 90 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 92 1. Introduction 94 Registries usually conduct maintenances and inform registrars in 95 different ways. Given the expansion of the DNS namespace, it is now 96 desirable to provide a method for EPP servers to notify EPP clients 97 as well as a method for EPP clients to query EPP servers for upcoming 98 maintenances. 100 This document describes an extension mapping for version 1.0 of the 101 Extensible Provision Protocol [RFC5730]. This mapping provides a 102 mechanism by which EPP servers may notify and EPP clients to query 103 for upcoming maintenances. 105 1.1. Terminology and Definitions 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in [RFC2119] when 110 specified in their uppercase forms. 112 XML is case sensitive. Unless stated otherwise, XML specifications 113 moreover, examples provided in this document MUST be interpreted in 114 the character case presented to develop a conforming implementation. 116 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 117 maintenance-0.1". The XML namespace prefix "maint" is used, but 118 implementations MUST NOT depend on it and instead employ a proper 119 namespace-aware XML parser and serializer to interpret and output 120 the XML documents. 122 In examples, "C:" represents lines sent by a protocol client and 123 "S:" represents lines returned by a protocol server. Indentation and 124 white space in examples are provided only to illustrate element 125 relationships and are not a REQUIRED feature of this protocol. 127 2. Object Attributes 129 2.1. Internationalized Domain Names 131 Names of affected hosts MUST be provided as A-label according to 132 [RFC5891]. 134 2.2. Dates and Times 136 All dates and times attribute values MUST be expressed in Universal 137 Coordinated Time (UTC) using the Gregorian calendar. The extended 138 date-time form using upper case "T" and "Z" characters defined in ISO 139 8601 [RFC3339] MUST be used to represent date-time values. 141 2.3. Maintenance Elements 143 The element describes a single registry maintenance 144 event during a specific period. This element is used in a maintenance 145 item EPP response and message. 147 For creating a new maintenance the attribute MUST be 148 set and the attribute SHALL NOT be present. 150 For updating a maintenance the attributes and 151 MUST be set. 153 154 MUST be present and a server unique id and SHALL NOT be 155 changed if maintenance is updated or deleted. A human-readable 156 description of the maintenance is identified via an OPTIONAL 157 "msg" attribute. 159 160 MUST be present and contains one or more elements. 161 The server SHOULD NOT list systems which are not affected by the 162 maintenance. 164 165 MUST be present at least once and has an element of , 166 and . 168 169 MUST be present and indicates the name of the affected system, 170 such as "EPP", "WHOIS", "DNS", "Portal", etc. 172 173 MUST be present and indicates the affected maintained system 174 contains the hostname and OPTIONAL an IP address. 175 Hostname SHALL be A-label according [RFC5891]. 176 IPv4 addresses SHALL be dotted-decimal notation. 177 An example of this textual representation is "192.0.2.0". 178 IPv6 addresses SHALL be according [RFC5952]. 179 An example of this textual representation is 180 "2001:db8::1:0:0:1". 182 183 MUST be present and contains the impact level; values MUST 184 either be "full" or "partial". 186 187 MUST be present and indicates the type of the affected system; 188 the attribute type is REQUIRED and SHOULD either be "production", 189 "ote", "staging", "dev" or "custom". And alternatively the 190 attribute name could be used to define a server specific affected 191 system for example. In that case name MUST be set: 192 194 195 SHOULD be present and indicates the start of the maintenance 196 according ISO 8601 [RFC3339]. 197 Format: YYYY-MM-DDThh:mm:ssTZ 199 200 SHOULD be present and indicates the end of the maintenance 201 according to 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. 218 219 SHOULD be present and contains elements. 221 222 MUST be present and contains the affected top-level domain. 223 A-label format according to [RFC5891]. 225 226 SHOULD be present and contains and 227 . 229 230 MUST be present and indicates if a client needs to do 231 something that is connection-related, such as a reconnect. The 232 value SHALL be 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 contains the creation date of the maintenance 241 according ISO 8601 [RFC3339]. 242 Format: YYYY-MM-DDThh:mm:ssTZ 244 245 MAY be present and contains the updated date of the maintenance 246 according to ISO 8601 [RFC3339], and if set MUST be equal to or 247 greater than . 248 Format: YYYY-MM-DDThh:mm:ssTZ 250 3. EPP Command Mapping 252 A detailed description of the EPP syntax and semantics can be found 253 in the EPP core protocol specification [RFC5730]. The command 254 mappings described here are specifically for the use to notify of 255 Registry Maintenances and Registry Maintenance object mapping. 257 3.1. EPP Query Commands 259 EPP [RFC5730] provides three commands to retrieve object information: 260 to determine if an object is known to the server, to 261 retrieve detailed information associated with an object, and 262 to retrieve object transfer status information. 264 3.1.1. EPP Command 266 Available check semantics do not apply to maintenance objects, so 267 there is no mapping defined for the EPP command. 269 3.1.2. EPP Command 271 Transfer semantics do not apply to maintenance objects, so there is 272 no mapping defined for the EPP command. 274 3.1.3. EPP Command 276 EPP provides the command that is used to retrieve registry 277 maintenance information. In addition to the standard EPP command 278 elements, the command MUST contain a 279 element that identifies the maintenance namespace. 281 The element MUST contain a child element. It is either 282 to retrieve a specific maintenance item or 283 to query all maintenance items. 285 3.1.3.1. Info Maintenance Item 287 The information on a specific Maintenance Item can be retrieved by 288 using command with the element and the child 289 element . 291 If a is sent with a that does not exist on 292 the server side, then the result code 2303 MUST be responded. 294 Example to retrieve a specific maintenance item in an command. 296 C: 297 C: 298 C: 299 C: 300 C: 302 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 303 C: 304 C: 305 C: ABC-12345 306 C: 307 C: 309 When an command has been processed successfully, the EPP 310 element MUST contain a child element that 311 identifies the maintenance namespace. The element 312 contains the element defined in Section 2.3. 314 Example of returning a specific maintenance item in an 315 response. 317 S: 318 S: 319 S: 320 S: 321 S: Command completed successfully 322 S: 323 S: 324 S: 326 S: 327 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 328 S: 329 S: 330 S: 331 S: EPP 332 S: epp.registry.example 333 S: 334 S: full 335 S: 336 S: 337 S: 338 S: 2020-09-30T06:00:00Z 339 S: 2020-09-30T14:25:57Z 340 S: planned 341 S: 342 S: https://www.registry.example/notice?123 343 S: 344 S: free text 345 S: 346 S: 347 S: example 348 S: test 349 S: 350 S: 351 S: false 352 S: false 353 S: 354 S: 2020-03-08T22:10:00Z 355 S: 356 S: 357 S: 358 S: 359 S: ABC-12345 360 S: 54321-XYZ 361 S: 362 S: 363 S: 365 3.1.3.2. Info Maintenance List 367 The Info Maintenance List can be retrieved by using the 368 command and the element with the child element 369 . Server policy determines if previous maintenances will 370 be listed in the . 372 Example to retrieve the maintenance list in an command. 374 C: 375 C: 376 C: 377 C: 378 C: 380 C: 381 C: 382 C: 383 C: ABC-12345 384 C: 385 C: 386 When an command has been processed successfully, the EPP 387 element MUST contain a child element 388 that identifies the maintenance namespace. The 389 element contains the element a list of 390 elements. The element contains the following child 391 elements: 392 : defined in Section 2.3. 393 : defined in Section 2.3. 394 : defined in Section 2.3. 395 : defined in Section 2.3. 396 : OPTIONAL defined in Section 2.3. 398 Example of returning the maintenance list in an response. 400 S: 401 S: 402 S: 403 S: 404 S: Command completed successfully 405 S: 406 S: 407 S: 409 S: 410 S: 411 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 412 S: 413 S: 2020-04-30T06:00:00Z 414 S: 2020-04-30T07:00:00Z 415 S: 2020-02-08T22:10:00Z 416 S: 417 S: 418 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 419 S: 420 S: 2020-06-15T04:30:00Z 421 S: 2020-06-15T05:30:00Z 422 S: 2020-02-08T22:10:00Z 423 S: 2020-03-08T20:11:00Z 424 S: 425 S: 426 S: 427 S: 428 S: 429 S: ABC-12345 430 S: 54321-XYZ 431 S: 432 S: 433 S: 435 3.1.4. EPP Command 437 The EPP command and response is defined in Section 2.9.2.3 of 438 [RFC5730]. The Registry Maintenance Notification is included in the 439 EPP response of [RFC5730]. 441 For the Registry Maintenance Notification, there are three types of 442 poll messages. The poll message applies whenever the domain name 443 registry creates, updates, or deletes maintenance. In the case of 444 a Registry Maintenance specific message, a element 445 will be included within the element of the standard 446 response. 448 The element will include a reference to the 449 Registry Maintenance namespace. EPP data contained within the 450 element is formatted according to the 451 maintenance-poll schema. 453 Please see the defintion of elements in Section 2.3. 455 Example command: 457 C: 458 C: 459 C: 460 C: 461 C: ABC-12345 462 C: 463 C: 465 Example response with the Registry Maintenance poll message: 467 S: 468 S: 469 S: 470 S: 471 S: Command completed successfully; ack to dequeue 472 S: 473 S: 474 S: 2020-10-08T22:10:00Z 475 S: Registry Maintenance Notification 476 S: 477 S: 478 S: 480 S: 481 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 482 S: 483 S: 484 S: EPP 485 S: epp.registry.example 486 S: 487 S: full 488 S: 489 S: 490 S: 491 S: 2020-10-30T06:00:00Z 492 S: 2020-10-30T14:25:57Z 493 S: planned 494 S: 495 S: https://www.registry.example/notice?123 496 S: 497 S: 498 S: example 499 S: test 500 S: 501 S: 502 S: false 503 S: false 504 S: 505 S: 2020-02-08T22:10:00Z 506 S: 507 S: 508 S: 509 S: 510 S: ABC-12345 511 S: 54321-XYZ 512 S: 513 S: 514 S: 516 3.2. EPP Transform Commands 518 EPP provides five commands to transform objects: to create 519 an instance of an object, to delete an instance of an 520 object, to extend the validity period of an object, 521 to manage object sponsorship changes, and to 522 change information associated with an object. 524 3.2.1. EPP Command 526 Create semantics do not apply to maintenance objects, so there is no 527 mapping defined for the EPP command. 529 3.2.2. EPP Command 531 Delete semantics do not apply to maintenance objects, so there is no 532 mapping defined for the EPP command. 534 3.2.3. EPP Command 536 Renew semantics do not apply to maintenance objects, so there is no 537 mapping defined for the EPP command. 539 3.2.4. EPP Command 541 Transfer semantics do not apply to maintenance objects, so there is 542 no mapping defined for the EPP command. 544 3.2.5. EPP Command 546 Update semantics do not apply to maintenance objects, so there is no 547 mapping defined for the EPP command. 549 4. Formal Syntax 551 One schema is presented here that is the EPP Registry Maintenance 552 schema. 554 The formal syntax presented here is a complete schema representation 555 of the object mapping suitable for automated validation of EPP XML 556 instances. The BEGIN and END tags are not part of the schema; they 557 are used to note the beginning and end of the schema for URI 558 registration purposes. 560 4.1. Registry Maintenance EPP Mapping Schema 562 BEGIN 563 564 572 575 576 578 579 580 Extensible Provisioning Protocol v1.0 581 Maintenance Mapping Schema. 582 583 585 588 590 593 594 595 596 597 598 599 600 601 604 605 606 607 608 609 610 611 613 616 618 621 622 623 624 625 626 628 631 632 633 635 636 638 641 642 643 644 645 646 647 648 649 650 653 654 655 656 657 658 659 660 661 662 664 665 667 668 669 670 672 675 676 677 679 680 682 685 686 687 688 689 690 692 695 696 697 698 699 700 701 702 705 706 707 708 709 710 711 713 716 717 718 719 720 721 722 724 725 726 727 728 729 731 732 733 734 735 736 738 741 742 743 744 745 746 747 748 749 750 753 754 755 756 757 758 759 760 762 765 766 767 768 769 770 772 775 776 777 779 780 782 785 786 787 788 789 790 791 794 795 END 797 5. IANA Considerations 799 5.1. XML Namespace 801 This document uses URNs to describe XML namespaces and XML schemas 802 conforming to a registry mechanism defined in [RFC3688]. 804 Registration request for the maintenance namespace: 806 URI: urn:ietf:params:xml:ns:epp:maintenance-0.1 808 Registrant Contact: IESG 810 XML: None. Namespace URIs do not represent an XML specification. 812 Registration request for the maintenance schema: 814 URI: urn:ietf:params:xml:schema:maintenance-1.0 816 Registrant Contact: IESG 818 XML: See the "Formal Syntax" section of this document. 820 5.2. EPP Extension Registry 822 The following registration of the EPP Extension Registry, described 823 in [RFC7451], is requested: 825 Name of Extension: "Registry Maintenance Notifications for the 826 Extensible Provisioning Protocol (EPP)" 828 Document status: Standards Track 830 Reference: (insert the reference to RFC version of this document) 832 Registrant Name and Email Address: IESG, 834 TLDs: Any 836 IPR Disclosure: None 838 Status: Active 840 Notes: None 842 6. Security Considerations 844 The mapping extensions described in this document do not provide any 845 security services beyond those specified by EPP [RFC5730] and 846 protocol layers used by EPP. The security considerations described in 847 these other specifications apply to this specification as well. 849 7. Implementation Status 851 Note to RFC Editor: Please remove this section and the reference to 852 [RFC7942] before publication. 854 This section records the status of known implementations of the 855 protocol defined by this specification at the time of posting of this 856 Internet-Draft, and is based on a proposal described in [RFC7942]. 857 The description of implementations in this section is intended to 858 assist the IETF in its decision processes in progressing drafts to 859 RFCs. Please note that the listing of any individual implementation 860 here does not imply endorsement by the IETF. Furthermore, no effort 861 has been spent to verify the information presented here that was 862 supplied by IETF contributors. This is not intended as, and must not 863 be construed to be, a catalog of available implementations or their 864 features. Readers are advised to note that other implementations may 865 exist. 867 According to [RFC7942], "this will allow reviewers and working groups 868 to assign due consideration to documents that have the benefit of 869 running code, which may serve as evidence of valuable experimentation 870 and feedback that have made the implemented protocols more mature. It 871 is up to the individual working groups to use this information as 872 they see fit". 874 7.1. GoDaddy Registry 876 Organization: GoDaddy Registry 878 Name: GoDaddy Registry 880 Description: GoDaddy Registry provides maintenance notifications to 881 their registrars. 883 Level of maturity: Production 885 Coverage: All aspects of the protocol according to the draft version 886 2 are implemented with further updates to come. 888 Licensing: Proprietary 890 Contact: quoc@registry.godaddy 892 URL: https://registry.godaddy 894 8. References 896 8.1. Normative References 898 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 899 Requirement Levels", BCP 14, RFC 2119, March 1997, 900 . 902 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 903 DOI 10.17487/RFC3688, January 2004, 904 . 906 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 907 STD 69, RFC 5730, August 2009, 908 . 910 8.2. Informative References 912 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 913 Internet: Timestamps", RFC 3339, July 2002, 914 . 916 [RFC5891] Klensin, J., "Internationalized Domain Names in 917 Applications (IDNA): Protocol", RFC 5891, August 2010, 918 . 920 [RFC5952] Kawamura, S. and Kawashima, M., "A Recommendation for IPv6 921 Address Text Representation", RFC 5952, August 2010, 922 . 924 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 925 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 926 February 2015, . 928 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 929 Running Code: The Implementation Status Section", RFC 930 7942, July 2016, 931 . 933 Appendix A. Change History 935 A.1. Change from draft-sattler-epp-poll-maintenance-response to 936 draft-sattler-epp-registry-maintenance 938 Updated to be EPP based instead of JSON document. 940 A.2. Change from draft-sattler-epp-registry-maintenance to 941 draft-ietf-regext-epp-registry-maintenance 943 Adopted by the REGEXT working group. 945 A.3. Change from 00 to 01 947 Clarified maint:description and maint:environment. Changed 948 maint:description from complexType to simpleType. Fixed typo. 949 Added acknowledgment. 951 A.4. Change from 01 to 02 953 Update language from Domain Name Registry to Registry. Clarified 954 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 955 to contain hostName and hostAddr. Changed maint:tlds from MUST to 956 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 957 unique id. 959 A.5. Change from 02 to 03 961 Changed maint:connection from MUST to SHOULD. 963 A.6. Change from 03 to 04 965 A lot of clarifications and editoral changes. 967 A.7. Change from 04 to 05 969 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 970 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 971 Clarified for retrieving maintenance items and the list. 973 A.8. Change from 05 to 06 975 Changed dates in examples to more recent dates. Renamed Query 976 Maintenance Item and List to Info Maintenance Item and List. Removed 977 blackout in favor of full. Added GoDaddy Registry implementation. 979 Acknowledgments 981 The authors wish to thank the following individuals for their 982 feedback and suggestions (sorted alphabetically by company): 984 o Patrick Mevzek 985 o Anthony Eden, DNSimple 986 o Christopher Martens, Donuts 987 o Quoc-Anh Pham, GoDaddy Registry 988 o Raymond Zylstra, GoDaddy Registry 989 o Neal McPherson, IONOS 990 o Andreas Huber, united-domains 991 o Craig Marchant, VentraIP 992 o James Gould, Verisign 994 Authors' Addresses 996 Tobias Sattler 998 Email: tobias.sattler@me.com 999 URI: https://tobiassattler.com 1001 Roger Carney 1002 GoDaddy Inc. 1003 14455 N. Hayden Rd. #219 1004 Scottsdale, AZ 85260 1005 US 1007 Email: rcarney@godaddy.com 1008 URI: http://www.godaddy.com 1010 Jody Kolker 1011 GoDaddy Inc. 1012 14455 N. Hayden Rd. #219 1013 Scottsdale, AZ 85260 1014 US 1016 Email: jkolker@godaddy.com 1017 URI: http://www.godaddy.com