idnits 2.17.00 (12 Aug 2021) /tmp/idnits19959/draft-ietf-regext-epp-registry-maintenance-19.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 (October 11, 2021) is 215 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: December 17, 2021 J. Kolker 5 GoDaddy Inc. 6 October 11, 2021 8 Registry Maintenance Notification for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-19 12 Abstract 13 This document describes an Extensible Provisioning Protocol (EPP) 14 extension called "Registry Maintenance Notification", used by EPP 15 servers to notify EPP clients and allow EPP clients to query EPP 16 servers regarding maintenance events. 18 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at https://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress". 32 This Internet-Draft will expire on December 17, 2021. 34 Copyright Notice 35 Copyright (c) 2021 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 50 1.1. Terminology and Definitions . . . . . . . . . . . . . . . 3 51 2. Migrating to Newer Versions of This Extension . . . . . . . . 4 52 3. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 4 53 3.1. Internationalized Domain Names . . . . . . . . . . . . . 4 54 3.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 4 55 3.3. Maintenance Elements . . . . . . . . . . . . . . . . . . 4 56 4. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 7 57 4.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 7 58 4.1.1. EPP Command . . . . . . . . . . . . . . . . . 7 59 4.1.1.1. Info Maintenance Item . . . . . . . . . . . . . . . 7 60 4.1.1.2. Info Maintenance List . . . . . . . . . . . . . . . 9 61 4.1.2. EPP Command . . . . . . . . . . . . . . . . . 10 62 4.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 12 63 5. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 12 64 5.1. Registry Maintenance Notification EPP Mapping Schema . . 12 65 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 66 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 17 67 6.2. EPP Extension Registry . . . . . . . . . . . . . . . . . 17 68 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 69 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 18 70 8.1. GoDaddy Registry . . . . . . . . . . . . . . . . . . . . 18 71 8.2. TANGO Registry Services . . . . . . . . . . . . . . . . . 19 72 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 73 9.1. Normative References . . . . . . . . . . . . . . . . . . 19 74 9.2. Informative References . . . . . . . . . . . . . . . . . 20 75 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 20 76 A.1. Change from draft-sattler-epp-poll-maintenance-response to 77 draft-sattler-epp-registry-maintenance . . . . . . . . . 20 78 A.2. Change from draft-sattler-epp-registry-maintenance to 79 draft-ietf-regext-epp-registry-maintenance . . . . . . . 20 80 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 21 81 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 21 82 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 21 83 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 21 84 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 21 85 A.8. Change from 05 to 06 . . . . . . . . . . . . . . . . . . 21 86 A.9. Change from 06 to 07 . . . . . . . . . . . . . . . . . . 21 87 A.10. Change from 07 to 08 . . . . . . . . . . . . . . . . . . 21 88 A.11. Change from 08 to 09 . . . . . . . . . . . . . . . . . . 21 89 A.12. Change from 09 to 10 . . . . . . . . . . . . . . . . . . 21 90 A.13. Change from 10 to 11 . . . . . . . . . . . . . . . . . . 22 91 A.14. Change from 11 to 12 . . . . . . . . . . . . . . . . . . 22 92 A.15. Change from 12 to 13 . . . . . . . . . . . . . . . . . . 22 93 A.16. Change from 13 to 14 . . . . . . . . . . . . . . . . . . 22 94 A.17. Change from 14 to 15 . . . . . . . . . . . . . . . . . . 22 95 A.18. Change from 15 to 16 . . . . . . . . . . . . . . . . . . 22 96 A.19. Change from 16 to 17 . . . . . . . . . . . . . . . . . . 22 97 A.20. Change from 17 to 18 . . . . . . . . . . . . . . . . . . 22 98 A.21. Change from 18 to 19 . . . . . . . . . . . . . . . . . . 22 99 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 22 100 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23 102 1. Introduction 104 The Extensible Provisioning Protocol (EPP), as defined in [RFC5730], 105 is a protocol whose original motivation is to provide a standard 106 Internet domain name registration protocol for use between registries 107 and registrars. 109 Registries routinely update systems to ensure a higher quality of 110 service, implement new services, or upgrade protocols to the latest 111 standards. These updates are pushed to various registry environments 112 during time frames communicated to registrars as "maintenance 113 events". Maintenance events may require making services unavailable 114 for some limited time while the upgrade happens. Registries usually 115 inform registrars about maintenance events in various formats, none 116 of which are standardized between registries. 118 The DNS namespace expansion has led to many additional registries 119 that registrars must interact with, adding more maintenance events 120 and formats. It is now desirable to provide an efficient approach to 121 notify registrars. 123 This document describes an extension mapping for version 1.0 of the 124 EPP to provide a mechanism by which EPP servers may notify EPP 125 clients of and allow EPP clients to query EPP servers on upcoming 126 maintenance events. 128 1.1. Terminology and Definitions 130 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 131 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 132 "OPTIONAL" in this document are to be interpreted as described in 133 BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all 134 capitals, as shown here. 136 XML [W3C.REC-xml11-20060816] is case-sensitive. Unless stated 137 otherwise, XML specification and examples provided in this document 138 MUST be interpreted in the character case presented in order to 139 develop a conforming implementation. 141 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 142 maintenance-1.0". The XML namespace prefix "maint" is used, but 143 implementations MUST NOT depend on it. Instead, they are to employ a 144 proper namespace-aware XML parser and serializer to interpret and 145 output the XML documents. 147 "ote" is an abbreviation for "Operational Test and Evaluation". 149 In examples, "C:" represents lines sent by a protocol client, and 150 "S:" represents lines returned by a protocol server. Indentation and 151 white space in examples are provided only to illustrate element 152 relationships and are not a required feature of this protocol. 154 2. Migrating to Newer Versions of This Extension 156 Servers that implement this extension SHOULD provide a way for 157 clients to progressively update their implementations when a new 158 version of the extension is deployed. A newer version of the 159 extension is expected to use an XML namespace with a higher version 160 number than the prior versions. 162 Servers SHOULD (for a temporary migration period up to server policy) 163 provide support for older versions of the extension in parallel to 164 the newest version and allow clients to execute their preferred 165 version of the command based on the maintenance 166 elements of the server . The version of the maintenance 167 response MUST match the version of the maintenance 168 command executed by the server. 170 Servers MUST return a Registry Maintenance Notification poll message 171 matching the newest negotiated version of the maintenance extension, 172 based on an intersection of the maintenance elements in the 173 server and the client command. If the intersection 174 of the maintenance elements of the server and the 175 client command results in an empty set, the server MUST 176 return the newest version of the Registry Maintenance Notification 177 poll message supported by the server based on "Usage with 178 Poll-Message EPP Responses" in Section 6 of [RFC9038]. 180 3. Object Attributes 182 3.1. Internationalized Domain Names 184 Names of affected hosts MUST be provided in A-label form, according 185 to [RFC5891]. 187 3.2. Dates and Times 189 All date and time attribute values MUST be expressed in Universal 190 Coordinated Time (UTC) using the Gregorian calendar. The date-time 191 format defined as "date-time" in [RFC3339], with time-offset="Z", 192 MUST be used. 194 3.3. Maintenance Elements 196 The element describes a single registry maintenance 197 event during a specific period. This element is used in a maintenance 198 item EPP command and response, and response. 200 If an element is not marked as optional, it is mandatory. 202 203 The server unique identifier for the maintenance event with the 204 OPTIONAL "name" attribute that includes a human-readable name of 205 the event. The server unique identifier SHALL NOT be changed if 206 the event is updated or deleted. When the "name" attribute is set, 207 the OPTIONAL "lang" attribute MAY be present to identify the 208 language if the negotiated value is something other than the 209 default value of "en" (English). 211 212 Zero or more OPTIONAL types of the maintenance event, with the 213 possible set of values defined by server policy, such as 214 "Routine Maintenance", "Software Update", "Software Upgrade", or 215 "Extended Outage". The OPTIONAL "lang" attribute MAY be present to 216 identify the language if the negotiated value is something other 217 than the default value of "en" (English). 219 220 The OPTIONAL element for a Registry Maintenance 221 Notification poll message; values MUST either be "create", 222 "update", "delete", "courtesy", or "end". For the "create" and 223 "update" types, the server includes the state of the maintenance 224 event after the creation or update. For the "delete" type, the 225 server includes the state of the event before the delete. The 226 "courtesy" provides a reminder of an event, and the "end" provides 227 a notification of the end of the event without updating the 228 maintenance object and includes the latest state of the event. 229 This element MUST be present only for poll messages. 231 232 One or more elements that are affected by the 233 maintenance event. 235 236 The element contains the following child 237 elements: 239 240 The name of the affected system, such as "EPP", "WHOIS", 241 "DNS", "Portal", "RDAP", etc. 243 244 The OPTIONAL affected maintained system's hostname, which 245 SHALL be in A-label form, according to [RFC5891]. 247 248 The impact level; the values MUST either be "full", 249 "partial", or "none". If access is expected to be 250 intermittently unavailable, it is "partial". If access is 251 expected to be completely unavailable, it is "full". If 252 access is not affected, it is "none". 254 255 The type of the affected system; the attribute "type" is REQUIRED 256 and MUST either be "production", "ote", "staging", "dev" or 257 "custom". For extensibility, the element 258 includes the OPTIONAL "name" attribute that can define the name of 259 the custom environment when the element "type" 260 attribute has the "custom" value. For example, for the custom 261 "marketing" environment, the element should 262 be: 264 265 The date and time of the start of the maintenance event. 267 268 The date and time of the end of the maintenance event. The 269 element MUST be greater than the 270 element. 272 273 The reason behind the maintenance event; the values MUST either be 274 "planned" or "emergency". 276 277 The OPTIONAL URI to the detailed maintenance event description, 278 formatted according to [RFC3986]. 280 281 Zero or more OPTIONAL free-form descriptions of the maintenance 282 event, usable without creating and traversing an external resource 283 as defined by the element. The OPTIONAL "lang" 284 attribute MAY be present to identify the language if the 285 negotiated value is something other than the default value of "en" 286 (English). The OPTIONAL "type" attribute MAY be present to 287 identify the format of the description. It MUST either be "plain" 288 for plain text or "html" for HTML text that is defined in 289 [W3C.REC-html5-20141028] and XML-escaped, with a default value of 290 "plain". 292 293 The OPTIONAL element contains one or more 294 child elements. If the is not present, the entire 295 system is affected. 297 298 The affected top-level domain or registry zone, which SHALL be 299 in A-label form, according to [RFC5891]. 301 302 The OPTIONAL element contains the following 303 child elements: 305 306 The value SHALL be boolean and indicates if a client needs to 307 perform a connection-related action, such as a reconnect. The 308 attribute should only be used as a flag to indicate connections 309 will be affected. Servers SHOULD include a description of how 310 the connections are affected in the element 311 or use the element above. 313 314 The value SHALL be boolean and indicates if a client needs to 315 perform an implementation-related action, such as a code 316 change. The attribute should only be used as a flag to indicate 317 implementation will be affected. Servers SHOULD include a 318 description of how the implementation is affected in the 319 element or use the element 320 above. 322 323 The date and time of the maintenance object creation. 325 326 The OPTIONAL date and time of the most recent maintenance object 327 modification. This element MUST NOT be present if the maintenance 328 object has never been modified. 330 4. EPP Command Mapping 332 A detailed description of the EPP syntax and semantics can be found 333 in the EPP core protocol specification [RFC5730]. The command 334 mappings described here are specifically used to notify registrars of 335 registry maintenance events and object mapping. 337 4.1. EPP Query Commands 339 EPP [RFC5730] provides three commands to retrieve object information: 340 to determine if an object is known to the server, to 341 retrieve detailed information associated with an object, and 342 to retrieve object transfer status information. 344 This extension does not add any elements to EPP and 345 commands or responses. 347 4.1.1. EPP Command 349 EPP provides the command that is used to retrieve registry 350 maintenance information. In addition to the standard EPP command 351 elements, the command MUST contain a 352 element that identifies the maintenance namespace. 354 The element MUST contain a child element. It is either 355 the child element, described in Section 4.1.1.1, to query 356 for a specific maintenance item or the child element, 357 described in Section 4.1.1.2, to query all maintenance items. 359 4.1.1.1. Info Maintenance Item 361 The information regarding a specific maintenance item can be 362 retrieved by using the command with the element 363 and the child element, defined in Section 3.3. If the 364 maintenance identifier does not exist, the server MUST return an EPP 365 error result code of 2303 ("Object does not exist") [RFC5730]. 367 Example to retrieve a specific maintenance item in an command. 369 C: 370 C: 371 C: 372 C: 373 C: 375 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 376 C: 377 C: 378 C: ABC-12345 379 C: 380 C: 382 When an command has been processed successfully, the EPP 383 element MUST contain a child element that 384 identifies the maintenance namespace. The element 385 contains the element defined in Section 3.3. 387 Example of returning a specific maintenance item in an 388 response. 390 S: 391 S: 392 S: 393 S: 394 S: Command completed successfully 395 S: 396 S: 397 S: 399 S: 400 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 401 S: 402 S: Routine Maintenance 403 S: 404 S: 405 S: EPP 406 S: epp.registry.example 407 S: 408 S: full 409 S: 410 S: 411 S: 412 S: 2021-12-30T06:00:00Z 413 S: 2021-12-30T07:00:00Z 414 S: planned 415 S: 416 S: https://www.registry.example/notice?123 417 S: 418 S: free-text 419 S: 420 S: Freitext 421 S: 422 S: 423 S: example 424 S: test 425 S: 426 S: 427 S: false 428 S: false 429 S: 430 S: 2021-11-08T22:10:00Z 431 S: 432 S: 433 S: 434 S: 435 S: ABC-12345 436 S: 54321-XYZ 437 S: 438 S: 439 S: 441 4.1.1.2. Info Maintenance List 443 The information for a list of maintenance items can be retrieved by 444 using the command with the element and the empty 445 child element. Server policy determines if completed 446 maintenance events will be included in the list of maintenance items. 448 Example to retrieve the list of maintenance items in an 449 command. 451 C: 452 C: 453 C: 454 C: 455 C: 457 C: 458 C: 459 C: 460 C: ABC-12345 461 C: 462 C: 464 When an command has been processed successfully, the EPP 465 element MUST contain a child element 466 that identifies the maintenance namespace. The 467 element contains the element with zero or more 468 child elements. The element 469 contains the following child elements: 471 472 The element defined in Section 3.3. 474 475 The element defined in Section 3.3. 477 478 The element defined in Section 3.3. 480 481 The element defined in Section 3.3. 483 484 The OPTIONAL element defined in Section 3.3. 486 Example of returning the list of maintenance items in an 487 response. 489 S: 490 S: 491 S: 492 S: 493 S: Command completed successfully 494 S: 495 S: 496 S: 498 S: 499 S: 500 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 501 S: 502 S: 2021-12-30T06:00:00Z 503 S: 2021-12-30T07:00:00Z 504 S: 2021-11-08T22:10:00Z 505 S: 506 S: 507 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 508 S: 509 S: 2021-12-15T04:30:00Z 510 S: 2021-12-15T05:30:00Z 511 S: 2021-11-08T22:11:00Z 512 S: 2021-11-17T15:00:00Z 513 S: 514 S: 515 S: 516 S: 517 S: 518 S: ABC-12345 519 S: 54321-XYZ 520 S: 521 S: 522 S: 524 4.1.2. EPP Command 526 The EPP command and response are defined in Section 2.9.2.3 of 527 [RFC5730]. The Registry Maintenance Notification is included in the 528 EPP response of [RFC5730]. 530 There are five types of poll messages for the Registry Maintenance 531 Notification, defined by the element in Section 3.3. 532 A poll message might be generated when a maintenance event is 533 created, updated, or deleted. A courtesy poll message can be sent as 534 a reminder of an upcoming maintenance event. An end poll message can 535 be sent when the maintenance event is completed. In the case of a 536 Registry Maintenance specific message, a element, 537 that identifies the maintenance namespace will be included within 538 the element of the standard response. The 539 element contains the element defined in 540 Section 3.3. 542 Example command: 544 C: 545 C: 546 C: 547 C: 548 C: ABC-12345 549 C: 550 C: 552 Example response: 554 S: 555 S: 556 S: 557 S: 558 S: Command completed successfully; ack to dequeue 559 S: 560 S: 561 S: 2021-11-08T22:10:00Z 562 S: Registry Maintenance Notification 563 S: 564 S: 565 S: 567 S: 568 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 569 S: create 570 S: 571 S: 572 S: EPP 573 S: epp.registry.example 574 S: 575 S: full 576 S: 577 S: 578 S: 579 S: 2021-12-30T06:00:00Z 580 S: 2021-12-30T07:00:00Z 581 S: planned 582 S: 583 S: https://www.registry.example/notice?123 584 S: 585 S: 586 S: example 587 S: test 588 S: 589 S: 590 S: false 591 S: false 592 S: 593 S: 2021-11-08T22:10:00Z 594 S: 595 S: 596 S: 597 S: 598 S: ABC-12345 599 S: 54321-XYZ 600 S: 601 S: 602 S: 604 4.2. EPP Transform Commands 606 EPP provides five commands to transform objects: to create 607 an instance of an object, to delete an instance of an 608 object, to extend the validity period of an object, 609 to manage object sponsorship changes, and to 610 change information associated with an object. 612 This extension does not add any elements to the EPP , 613 , , , and . 615 5. Formal Syntax 617 The EPP Registry Maintenance Notification schema is presented here. 619 The formal syntax presented here is a complete schema representation 620 of the object mapping suitable for automated validation of EPP XML 621 instances. The and tags are not part of 622 the schema; they are used to note the beginning and end of the 623 schema for URI registration purposes. 625 5.1. Registry Maintenance Notification EPP Mapping Schema 627 628 629 637 640 641 642 643 644 Extensible Provisioning Protocol v1.0 645 Registry Maintenance Notification Mapping Schema. 646 647 648 651 652 655 656 657 658 659 660 661 662 663 666 667 668 669 670 671 672 673 674 677 678 681 682 683 684 685 686 687 690 691 692 694 695 696 699 700 701 702 703 704 705 706 707 708 711 712 713 714 716 717 718 719 720 721 722 723 725 726 728 729 730 731 732 735 736 737 739 740 741 744 745 746 747 748 749 750 751 752 753 756 757 758 759 760 761 762 763 766 767 768 769 770 772 773 774 775 778 779 780 781 782 783 784 787 788 789 790 791 792 793 794 797 798 799 800 801 802 803 804 807 808 809 810 811 812 813 814 815 816 819 820 821 822 823 824 825 826 827 830 831 832 833 834 835 836 839 840 841 843 844 845 848 849 850 851 852 853 854 857 858 860 6. IANA Considerations 862 6.1. XML Namespace 864 This document uses URNs to describe XML namespaces and XML schemas 865 conforming to a registry mechanism defined in [RFC3688]. 867 Registration request for the maintenance namespace: 869 URI: urn:ietf:params:xml:ns:epp:maintenance-1.0 871 Registrant Contact: IESG 873 XML: None. Namespace URIs do not represent an XML specification. 875 Registration request for the maintenance schema: 877 URI: urn:ietf:params:xml:schema:epp:maintenance-1.0 879 Registrant Contact: IESG 881 XML: See the "Formal Syntax" section of this document. 883 6.2. EPP Extension Registry 885 The following registration of the EPP Extension Registry, described 886 in [RFC7451], is requested: 888 Name of Extension: Registry Maintenance Notification for the 889 Extensible Provisioning Protocol (EPP) 891 Document status: Standards Track 893 Reference: (insert the reference to RFC version of this document) 895 Registrant Name and Email Address: IESG 897 TLDs: Any 899 IPR Disclosure: None 901 Status: Active 903 Notes: None 905 7. Security Considerations 907 The security considerations of [RFC5730] apply in this document. 908 Additionally, a server MUST only provide maintenance information to 909 clients that are authorized. Suppose a client queries a maintenance 910 identifier that it is not authorized to access per Section 4.1.1.1 911 "Info Maintenance Item". In that case, the server SHOULD return an 912 EPP error result code of 2201 ("Authorization error") or 2303 913 ("Object does not exist") [RFC5730]. The list of top-level domains or 914 registry zones returned in the "Info Maintenance Item" response 915 SHOULD be filtered based on the top-level domains or registry zones 916 for which the client is authorized. Authorization of poll messages is 917 done at the time of poll message insertion and not at the time of 918 poll message consumption. 920 8. Implementation Status 922 Note to RFC Editor: Please remove this section and the reference to 923 [RFC7942] before publication. 925 This section records the status of known implementations of the 926 protocol defined by this specification at the time of posting of this 927 Internet-Draft, and is based on a proposal described in [RFC7942]. 928 The description of implementations in this section is intended to 929 assist the IETF in its decision processes in progressing drafts to 930 RFCs. Please note that the listing of any individual implementation 931 here does not imply endorsement by the IETF. Furthermore, no effort 932 has been spent to verify the information presented here that was 933 supplied by IETF contributors. This is not intended as, and must not 934 be construed to be, a catalog of available implementations or their 935 features. Readers are advised to note that other implementations may 936 exist. 938 According to [RFC7942], "this will allow reviewers and working groups 939 to assign due consideration to documents that have the benefit of 940 running code, which may serve as evidence of valuable experimentation 941 and feedback that have made the implemented protocols more mature. It 942 is up to the individual working groups to use this information as 943 they see fit". 945 8.1. GoDaddy Registry 947 Organization: GoDaddy Registry 949 Name: GoDaddy Registry 951 Description: GoDaddy Registry provides maintenance notifications to 952 their registrars. 954 Level of maturity: Production 956 Coverage: All aspects of the protocol according to the draft version 957 2 are implemented with further updates to come. 959 Licensing: Proprietary 961 Contact: quoc@registry.godaddy 963 URL: https://registry.godaddy 965 8.2. TANGO Registry Services 967 Name: TANGO Registry Services 969 Description: TANGO Registry Services provides maintenance 970 notifications to their registrars. 972 Level of maturity: Beta 974 Coverage: All aspects of the protocol according to the draft version 975 12 are implemented with further updates to come. 977 Licensing: Proprietary 979 Contact: Michael.Bauland@knipp.de 981 URL: https://tango-rs.com 983 9. References 985 9.1. Normative References 987 [W3C.REC-html5-20141028] 988 Hickson, I., Berjon, R., Faulkner, S., Leithead, T., 989 Doyle Navara, E., O'Connor, E., and S. Pfeiffer, "HTML5", 990 W3C Recommendation REC-html5-20141028, October 2014, 991 . 993 Latest version available at . 995 [W3C.REC-xml11-20060816] 996 Bray, T., Paoli, J., Sperberg-McQueen, M., Maler, E., 997 Yergeau, F., and J. Cowan, "Extensible Markup Language 998 (XML) 1.1 (Second Edition)", World Wide Web Consortium 999 Recommendation REC-xml11-20060816, 16 August 2006, 1000 . 1002 Latest version available at 1003 . 1005 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1006 Requirement Levels", BCP 14, RFC 2119, 1007 DOI 10.17487/RFC2119, March 1997, 1008 . 1010 [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: 1011 Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, 1012 . 1014 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, 1015 "Uniform Resource Identifier (URI): Generic Syntax", 1016 STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, 1017 . 1019 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 1020 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 1021 . 1023 [RFC5891] Klensin, J., "Internationalized Domain Names in 1024 Applications (IDNA): Protocol", RFC 5891, 1025 DOI 10.17487/RFC5891, August 2010, 1026 . 1028 [RFC7942] Sheffer, Y. and A. Farrel, "Improving Awareness of Running 1029 Code: The Implementation Status Section", BCP 205, 1030 RFC 7942, DOI 10.17487/RFC7942, July 2016, 1031 . 1033 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1034 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1035 May 2017, . 1037 [RFC9038] Gould, J. and M. Casanova, "Extensible Provisioning 1038 Protocol (EPP) Unhandled Namespaces", RFC 9038, 1039 DOI 10.17487/RFC9038, May 2021, 1040 . 1042 9.2. Informative References 1044 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 1045 DOI 10.17487/RFC3688, January 2004, 1046 . 1048 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 1049 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 1050 February 2015, . 1052 Appendix A. Change History 1054 A.1. Change from draft-sattler-epp-poll-maintenance-response to 1055 draft-sattler-epp-registry-maintenance 1057 Updated to be EPP based instead of JSON document. 1059 A.2. Change from draft-sattler-epp-registry-maintenance to 1060 draft-ietf-regext-epp-registry-maintenance 1062 Adopted by the REGEXT working group. 1064 A.3. Change from 00 to 01 1066 Clarified maint:description and maint:environment. Changed 1067 maint:description from complexType to simpleType. Fixed typo. 1068 Added acknowledgment. 1070 A.4. Change from 01 to 02 1072 Update language from Domain Name Registry to Registry. Clarified 1073 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 1074 to contain hostName and hostAddr. Changed maint:tlds from MUST to 1075 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 1076 unique id. 1078 A.5. Change from 02 to 03 1080 Changed maint:connection from MUST to SHOULD. 1082 A.6. Change from 03 to 04 1084 A lot of clarifications and editorial changes. 1086 A.7. Change from 04 to 05 1088 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 1089 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 1090 Clarified for retrieving maintenance items and the list. 1092 A.8. Change from 05 to 06 1094 Changed dates in examples to more recent dates. Renamed Query 1095 Maintenance Item and List to Info Maintenance Item and List. Removed 1096 blackout in favor of full. Added GoDaddy Registry implementation. 1098 A.9. Change from 06 to 07 1100 Removed IP addresses for . Editorial changes. 1102 A.10. Change from 07 to 08 1104 Editorial changes. Changed XML namespace and schema from 0.1 to 0.2. 1105 Added pollType to reflect create, update, or delete maintenance poll 1106 messages. 1108 A.11. Change from 08 to 09 1110 Editorial changes. Added new section "Migrating to Newer Versions of 1111 This Extension". 1113 A.12. Change from 09 to 10 1115 Editorial changes. Renamed "msg" to "name". Added "courtesy" and 1116 "end" to pollType. 1118 A.13. Change from 10 to 11 1120 Editorial changes. Added mime type to description. 1122 A.14. Change from 11 to 12 1124 Editorial changes. Changed XML namespace from 0.2 to 0.3. 1126 A.15. Change from 12 to 13 1128 Editorial changes. Added TANGO Registry Services to Section 8. Added 1129 Michael Bauland to acknowledgments. Added "none" to . 1131 A.16. Change from 13 to 14 1133 Accepted in WGLC. Changed XML namespace from 0.3 to 1.0. 1135 A.17. Change from 14 to 15 1137 Editorial changes, added feedback from the document shepherd. 1139 A.18. Change from 15 to 16 1141 Editorial changes, added feedback from area director. 1143 A.19. Change from 16 to 17 1145 Editorial changes, added last call feedback. Changed schema URI 1146 to urn:ietf:params:xml:schema:epp:maintenance-1.0. Changed dates in 1147 examples to more recent dates. 1149 A.20. Change from 17 to 18 1151 Editorial changes. 1153 A.21. Change from 18 to 19 1155 Editorial changes. 1157 Acknowledgments 1159 The authors wish to thank the following persons for their feedback 1160 and suggestions: James Gould, Michael Bauland, Patrick Mevzek, 1161 Quoc-Anh Pham, Raymond Zylstra, Christopher Martens, Anthony Eden, 1162 Neal McPherson, Craig Marchant, and Andreas Huber. 1164 Authors' Addresses 1166 Tobias Sattler 1168 Email: mail@tobiassattler.com 1169 URI: https://tobiassattler.com 1171 Roger Carney 1172 GoDaddy Inc. 1173 14455 N. Hayden Rd. #219 1174 Scottsdale, AZ 85260 1175 US 1177 Email: rcarney@godaddy.com 1178 URI: https://www.godaddy.com 1180 Jody Kolker 1181 GoDaddy Inc. 1182 14455 N. Hayden Rd. #219 1183 Scottsdale, AZ 85260 1184 US 1186 Email: jkolker@godaddy.com 1187 URI: https://www.godaddy.com