idnits 2.17.1 draft-ietf-regext-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 seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (December 23, 2020) is 1210 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 (~~), 2 warnings (==), 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 23, 2020 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-08 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 . . . . . . . . . . . . . . . . . . . . . . . . 11 68 4.1. Registry Maintenance EPP Mapping Schema . . . . . . . . . 11 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 70 5.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 16 71 5.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 16 72 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16 73 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 17 74 7.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 17 75 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 76 8.1. Normative References . . . . . . . . . . . . . . . . . . 18 77 8.2. Informative References . . . . . . . . . . . . . . . . . 18 78 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 18 79 A.1. Change from draft-sattler-epp-poll-maintenance-response to 80 draft-sattler-epp-registry-maintenance . . . . . . . . . 18 81 A.2. Change from draft-sattler-epp-registry-maintenance to 82 draft-ietf-regext-epp-registry-maintenance . . . . . . . 18 83 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 84 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 85 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19 86 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 19 87 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 19 88 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 19 89 A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 19 90 A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 19 91 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 19 92 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 29 94 1. Introduction 96 Registries usually conduct maintenances and inform registrars in 97 different ways. Given the DNS namespace expansion, it is now 98 desirable to provide methods for EPP servers to notify EPP clients 99 and EPP clients to query EPP servers for upcoming maintenances. 101 This document describes an extension mapping for version 1.0 of the 102 Extensible Provision Protocol [RFC5730]. This mapping provides a 103 mechanism by which EPP servers may notify and EPP clients to query 104 upcoming maintenances. 106 1.1. Terminology and Definitions 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 110 "OPTIONAL" in this document are to be interpreted as described in 111 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 112 capitals shown here. 114 XML is case sensitive. Unless stated otherwise, XML specifications 115 moreover, examples provided in this document MUST be interpreted in 116 the character case presented to develop a conforming implementation. 118 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 119 maintenance-0.2". The XML namespace prefix "maint" is used, but 120 implementations MUST NOT depend on it and instead employ a proper 121 namespace-aware XML parser and serializer to interpret and output 122 the XML documents. 124 In examples, "C:" represents lines sent by a protocol client and 125 "S:" represents lines returned by a protocol server. Indentation and 126 white space in examples are provided only to illustrate element 127 relationships and are not a REQUIRED feature of this protocol. 129 2. Object Attributes 131 2.1. Internationalized Domain Names 133 Names of affected hosts MUST be provided as an A-label according to 134 [RFC5891]. 136 2.2. Dates and Times 138 All dates and times attribute values MUST be expressed in Universal 139 Coordinated Time (UTC) using the Gregorian calendar. The extended 140 date-time form using upper case "T" and "Z" characters defined in ISO 141 8601 [RFC3339] MUST be used to represent date-time values. 143 2.3. Maintenance Elements 145 The element describes a single registry maintenance 146 event during a specific period. This element is used in a maintenance 147 item EPP response and message. 149 150 The server unique identifier for the maintenance with the OPTIONAL 151 "msg" attribute that includes a human-readable description of the 152 maintenance. The server unique identifier SHALL NOT be changed if 153 the maintenance is updated or deleted. When the "msg" attribute is 154 set, the OPTIONAL "lang" attribute MAY be present to identify the 155 language if the negotiated value is something other than the 156 default value of "en" (English). 158 159 The OPTIONAL for a Registry Maintenance 160 Notification poll message; values MUST either be "create", 161 "update", or "delete". For the "create" and "update" types, the 162 server includes the state of the maintenance after the create or 163 update. For the "delete" type, the server includes the state 164 of the maintenance prior to the delete. This element MUST be 165 present only for poll messages. 167 168 One or more elements that are affected by the 169 maintenance. 171 172 The element contains the following child 173 elements: 175 176 The name of the affected system, such as "EPP", "WHOIS", 177 "DNS", "Portal", etc. 179 180 The affected maintained system contains the hostname, which 181 SHALL be an A-label according to [RFC5891]. 183 184 The impact level; the values MUST either be "full" or 185 "partial". 187 188 The type of the affected system; the attribute "type" is 189 REQUIRED and MUST either be "production", "ote", "staging", 190 "dev" or "custom". For extensibility, the 191 element includes the OPTIONAL "name" attribute that can define 192 the name of the custom environment when the 193 element "type" attribute has the "custom" value. For example, 194 for the custom "marketing" environment, the 195 element should be: 196 198 199 The date and time of the start of the maintenance. 201 202 The date and time of the end of the maintenance. The 203 element MUST be equal to or greater than the 204 element. 206 207 The reason behind the maintenance; the values MUST either be 208 "planned" or "emergency". 210 211 The OPTIONAL URI to detailed maintenance description. 213 214 The OPTIONAL free-form description of the maintenance without 215 having to create and traverse an external resource defined by 216 the element. The OPTIONAL "lang" attribute MAY 217 be present to identify the language if the negotiated value is 218 something other than the default value of "en" (English). 220 221 The OPTIONAL element contains one or more 222 child elements. 224 225 The affected top-level domain or registry zone, which SHALL 226 be an A-label according to [RFC5891]. 228 229 The OPTIONAL element contains the 230 following child elements: 232 233 The value SHALL be boolean and indicates if a client needs 234 to do something that is connection-related, such as a 235 reconnect. 237 238 The value SHALL be boolean and indicates if a client needs 239 to do something that is implementation-related, such as a 240 code change. 242 243 The date and time of the maintenance object creation. 245 246 The OPTIONAL date and time of the most recent maintenance 247 object modification. This element MUST NOT be present if the 248 maintenance object has never been modified. 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 , described in Section 3.1.3.1, to query for a specific 283 maintenance item or , described in Section 3.1.3.2, to 284 query all maintenance items. 286 3.1.3.1. Info Maintenance Item 288 The information on a specific maintenance item can be retrieved by 289 using the command with the element and the 290 child element, defined in Section 2.3. If the maintenance 291 identifier does not exist, the server MUST return an EPP error result 292 code of 2303 [RFC5730]. 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 311 element MUST contain a child element that 312 identifies the maintenance namespace. The element 313 contains the element defined in Section 2.3. 315 Example of returning a specific maintenance item in an 316 response. 318 S: 319 S: 320 S: 321 S: 322 S: Command completed successfully 323 S: 324 S: 325 S: 327 S: 328 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 329 S: 330 S: 331 S: 332 S: EPP 333 S: epp.registry.example 334 S: 335 S: full 336 S: 337 S: 338 S: 339 S: 2020-12-30T06:00:00Z 340 S: 2020-12-30T14:25:57Z 341 S: planned 342 S: 343 S: https://www.registry.example/notice?123 344 S: 345 S: free text 346 S: 347 S: 348 S: example 349 S: test 350 S: 351 S: 352 S: false 353 S: false 354 S: 355 S: 2020-09-08T22:10:00Z 356 S: 357 S: 358 S: 359 S: 360 S: ABC-12345 361 S: 54321-XYZ 362 S: 363 S: 364 S: 366 3.1.3.2. Info Maintenance List 368 The information for a list of maintenance items can be retrieved by 369 using the command with the element and the empty 370 child element. Server policy determines if previous 371 maintenances will be included in the list of maintenance items. 373 Example to retrieve the maintenance list in an command. 375 C: 376 C: 377 C: 378 C: 379 C: 381 C: 382 C: 383 C: 384 C: ABC-12345 385 C: 386 C: 388 When an command has been processed successfully, the EPP 389 element MUST contain a child element 390 that identifies the maintenance namespace. The 391 element contains the element with zero or more 392 child elements. The element 393 contains the following child elements: 395 396 The defined in Section 2.3. 398 399 The defined in Section 2.3. 401 402 The defined in Section 2.3. 404 405 The defined in Section 2.3. 407 408 The OPTIONAL defined in Section 2.3. 410 Example of returning the maintenance list in an response. 412 S: 413 S: 414 S: 415 S: 416 S: Command completed successfully 417 S: 418 S: 419 S: 421 S: 422 S: 423 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 424 S: 425 S: 2020-12-30T06:00:00Z 426 S: 2020-12-30T07:00:00Z 427 S: 2020-09-08T22:10:00Z 428 S: 429 S: 430 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 431 S: 432 S: 2021-02-15T04:30:00Z 433 S: 2021-02-15T05:30:00Z 434 S: 2020-09-08T22:11:00Z 435 S: 2020-10-17T15:00:00Z 436 S: 437 S: 438 S: 439 S: 440 S: 441 S: ABC-12345 442 S: 54321-XYZ 443 S: 444 S: 445 S: 447 3.1.4. EPP Command 449 The EPP command and response is defined in Section 2.9.2.3 of 450 [RFC5730]. The Registry Maintenance Notification is included in the 451 EPP response of [RFC5730]. 453 For the Registry Maintenance Notification, there are three types of 454 poll messages, defined by the element in Section 455 2.3. A poll message applies when a maintenance is created, updated, 456 or deleted. In the case of a Registry Maintenance specific message, 457 a element will be included within the 458 element of the standard response. The element 459 contains the element defined in Section 2.3. 461 Example command: 463 C: 464 C: 465 C: 466 C: 467 C: ABC-12345 468 C: 469 C: 471 Example response: 473 S: 474 S: 475 S: 476 S: 477 S: Command completed successfully; ack to dequeue 478 S: 479 S: 480 S: 2020-10-08T22:10:00Z 481 S: Registry Maintenance Notification 482 S: 483 S: 484 S: 486 S: 487 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 488 S: create 489 S: 490 S: 491 S: EPP 492 S: epp.registry.example 493 S: 494 S: full 495 S: 496 S: 497 S: 498 S: 2020-12-30T06:00:00Z 499 S: 2020-12-30T14:25:57Z 500 S: planned 501 S: 502 S: https://www.registry.example/notice?123 503 S: 504 S: 505 S: example 506 S: test 507 S: 508 S: 509 S: false 510 S: false 511 S: 512 S: 2020-10-08T22:10:00Z 513 S: 514 S: 515 S: 516 S: 517 S: ABC-12345 518 S: 54321-XYZ 519 S: 520 S: 521 S: 523 3.2. EPP Transform Commands 525 EPP provides five commands to transform objects: to create 526 an instance of an object, to delete an instance of an 527 object, to extend the validity period of an object, 528 to manage object sponsorship changes, and to 529 change information associated with an object. 531 3.2.1. EPP Command 533 Create semantics do not apply to maintenance objects, so there is no 534 mapping defined for the EPP command. 536 3.2.2. EPP Command 538 Delete semantics do not apply to maintenance objects, so there is no 539 mapping defined for the EPP command. 541 3.2.3. EPP Command 543 Renew semantics do not apply to maintenance objects, so there is no 544 mapping defined for the EPP command. 546 3.2.4. EPP Command 548 Transfer semantics do not apply to maintenance objects, so there is 549 no mapping defined for the EPP command. 551 3.2.5. EPP Command 553 Update semantics do not apply to maintenance objects, so there is no 554 mapping defined for the EPP command. 556 4. Formal Syntax 558 The EPP Registry Maintenance schema is presented here. 560 The formal syntax presented here is a complete schema representation 561 of the object mapping suitable for automated validation of EPP XML 562 instances. The and tags are not part of 563 the schema; they are used to note the beginning and end of the 564 schema for URI registration purposes. 566 4.1. Registry Maintenance EPP Mapping Schema 568 569 570 577 580 581 582 583 584 Extensible Provisioning Protocol v1.0 585 Registry Maintenance Mapping Schema. 586 587 588 591 592 595 596 597 598 599 600 601 602 603 606 607 608 609 610 611 612 613 614 617 618 621 622 623 624 625 626 627 630 631 632 634 635 636 639 640 641 642 643 644 645 646 647 648 651 652 653 654 655 656 657 658 659 660 661 663 664 666 667 668 669 670 673 674 675 677 678 679 682 683 684 685 686 687 688 689 692 693 694 695 696 697 698 701 702 703 704 705 706 707 708 711 712 713 714 715 716 717 718 721 722 723 724 725 726 727 728 729 730 733 734 735 736 737 738 739 740 741 744 745 746 747 748 749 750 753 754 755 757 758 759 762 763 764 765 766 767 768 771 772 774 5. IANA Considerations 776 5.1. XML Namespace 778 This document uses URNs to describe XML namespaces and XML schemas 779 conforming to a registry mechanism defined in [RFC3688]. 781 Registration request for the maintenance namespace: 783 URI: urn:ietf:params:xml:ns:epp:maintenance-0.2 785 Registrant Contact: IESG 787 XML: None. Namespace URIs do not represent an XML specification. 789 Registration request for the maintenance schema: 791 URI: urn:ietf:params:xml:schema:maintenance-0.2 793 Registrant Contact: IESG 795 XML: See the "Formal Syntax" section of this document. 797 5.2. EPP Extension Registry 799 The following registration of the EPP Extension Registry, described 800 in [RFC7451], is requested: 802 Name of Extension: "Registry Maintenance Notifications for the 803 Extensible Provisioning Protocol (EPP)" 805 Document status: Standards Track 807 Reference: (insert the reference to RFC version of this document) 809 Registrant Name and Email Address: IESG, 811 TLDs: Any 813 IPR Disclosure: None 815 Status: Active 817 Notes: None 819 6. Security Considerations 821 The mapping extensions described in this document do not provide any 822 security services beyond those specified by EPP [RFC5730] and 823 protocol layers used by EPP. The security considerations described in 824 these other specifications apply to this specification as well. 826 7. Implementation Status 828 Note to RFC Editor: Please remove this section and the reference to 829 [RFC7942] before publication. 831 This section records the status of known implementations of the 832 protocol defined by this specification at the time of posting of this 833 Internet-Draft, and is based on a proposal described in [RFC7942]. 834 The description of implementations in this section is intended to 835 assist the IETF in its decision processes in progressing drafts to 836 RFCs. Please note that the listing of any individual implementation 837 here does not imply endorsement by the IETF. Furthermore, no effort 838 has been spent to verify the information presented here that was 839 supplied by IETF contributors. This is not intended as, and must not 840 be construed to be, a catalog of available implementations or their 841 features. Readers are advised to note that other implementations may 842 exist. 844 According to [RFC7942], "this will allow reviewers and working groups 845 to assign due consideration to documents that have the benefit of 846 running code, which may serve as evidence of valuable experimentation 847 and feedback that have made the implemented protocols more mature. It 848 is up to the individual working groups to use this information as 849 they see fit". 851 7.1. GoDaddy Registry 853 Organization: GoDaddy Registry 855 Name: GoDaddy Registry 857 Description: GoDaddy Registry provides maintenance notifications to 858 their registrars. 860 Level of maturity: Production 862 Coverage: All aspects of the protocol according to the draft version 863 2 are implemented with further updates to come. 865 Licensing: Proprietary 867 Contact: quoc@registry.godaddy 869 URL: https://registry.godaddy 871 8. References 873 8.1. Normative References 875 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 876 Requirement Levels", BCP 14, RFC 2119, March 1997, 877 . 879 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 880 DOI 10.17487/RFC3688, January 2004, 881 . 883 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 884 STD 69, RFC 5730, August 2009, 885 . 887 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 888 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 889 May 2017, . 891 8.2. Informative References 893 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 894 Internet: Timestamps", RFC 3339, July 2002, 895 . 897 [RFC5891] Klensin, J., "Internationalized Domain Names in 898 Applications (IDNA): Protocol", RFC 5891, August 2010, 899 . 901 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 902 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 903 February 2015, . 905 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 906 Running Code: The Implementation Status Section", RFC 907 7942, July 2016, 908 . 910 Appendix A. Change History 912 A.1. Change from draft-sattler-epp-poll-maintenance-response to 913 draft-sattler-epp-registry-maintenance 915 Updated to be EPP based instead of JSON document. 917 A.2. Change from draft-sattler-epp-registry-maintenance to 918 draft-ietf-regext-epp-registry-maintenance 920 Adopted by the REGEXT working group. 922 A.3. Change from 00 to 01 924 Clarified maint:description and maint:environment. Changed 925 maint:description from complexType to simpleType. Fixed typo. 926 Added acknowledgment. 928 A.4. Change from 01 to 02 930 Update language from Domain Name Registry to Registry. Clarified 931 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 932 to contain hostName and hostAddr. Changed maint:tlds from MUST to 933 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 934 unique id. 936 A.5. Change from 02 to 03 938 Changed maint:connection from MUST to SHOULD. 940 A.6. Change from 03 to 04 942 A lot of clarifications and editoral changes. 944 A.7. Change from 04 to 05 946 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 947 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 948 Clarified for retrieving maintenance items and the list. 950 A.8. Change from 05 to 06 952 Changed dates in examples to more recent dates. Renamed Query 953 Maintenance Item and List to Info Maintenance Item and List. Removed 954 blackout in favor of full. Added GoDaddy Registry implementation. 956 A.9. Change from 06 to 07 958 Removed IP addresses for . Editoral changes. 960 A.10. Change from 07 to 08 962 Editoral changes. Changed XML namespace and schema from 0.1 to 0.2. 963 Added pollType to reflect create, update, or delete maintenance poll 964 messages. 966 Acknowledgments 968 The authors wish to thank the following persons for their feedback 969 and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond 970 Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig 971 Marchant, and Andreas Huber. 973 Authors' Addresses 975 Tobias Sattler 977 Email: tobias.sattler@me.com 978 URI: https://tobiassattler.com 980 Roger Carney 981 GoDaddy Inc. 982 14455 N. Hayden Rd. #219 983 Scottsdale, AZ 85260 984 US 986 Email: rcarney@godaddy.com 987 URI: http://www.godaddy.com 989 Jody Kolker 990 GoDaddy Inc. 991 14455 N. Hayden Rd. #219 992 Scottsdale, AZ 85260 993 US 995 Email: jkolker@godaddy.com 996 URI: http://www.godaddy.com