idnits 2.17.1 draft-ietf-regext-epp-registry-maintenance-07.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 11, 2020) is 1232 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 11, 2020 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-07 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 . . . . . . . . . . . . . . . . . . . . . 5 54 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 5 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 . . . . . . . . . . . . . . . . . 10 62 3.2.1. EPP Command . . . . . . . . . . . . . . . . 10 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 . . . . . . . . . . . . . . . . . . . . . . . . . 17 76 8.1. Normative References . . . . . . . . . . . . . . . . . . 17 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 . . . . . . . . . . . . . . . . . . 18 84 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 18 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 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 19 91 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 93 1. Introduction 95 Registries usually conduct maintenances and inform registrars in 96 different ways. Given the DNS namespace expansion, it is now 97 desirable to provide methods for EPP servers to notify EPP clients 98 and EPP clients to query EPP servers for upcoming 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 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 only illustrate element relationships and are 125 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 148 Server unique identifier for the maintenance with an OPTIONAL "msg" 149 attribute that includes a human-readable description of the 150 maintenance. The server unique identifier SHALL NOT be changed if 151 the maintenance is updated or deleted. When the "msg" attribute is 152 set, an OPTIONAL "lang" attribute MAY be present to identify the 153 language if the negotiated value is something other than the 154 default value of "en" (English). 156 157 Indicates one or more elements that are affected by 158 the maintenance. 160 161 The element contains the following child 162 elements: 164 165 Indicates the name of the affected system, such as "EPP", 166 "WHOIS", "DNS", "Portal", etc. 168 169 Indicates the affected maintained system contains the hostname, 170 which SHALL be A-label according [RFC5891]. 172 173 Indicates the impact level; values MUST either be "full" or 174 "partial". 176 177 Indicates the type of the affected system; the attribute type is 178 REQUIRED and SHOULD either be "production", "ote", "staging", 179 "dev" or "custom". And alternatively, the attribute name could be 180 used to define a server specific affected system, for example. In 181 that case, name MUST be set: 182 184 185 Indicates the date and time of the start of the maintenance. 187 188 Indicates the date and time of the end of the maintenance. The 189 element MUST be equal or greater than the 190 element. 192 193 Indicates the reason behind the maintenance; values SHOULD either 194 be "planned" or "emergency". 196 197 Contains URI to detailed maintenance description. 199 200 A freeform description of the maintenance without having to 201 create and traverse an external resource defined by the 202 element. An OPTIONAL "lang" attribute MAY be 203 present to identify the language if the negotiated value is 204 something other than the default value of "en" (English). 206 207 The element contains the following child element: 209 210 Contains the affected top-level domain, which SHALL be A-label 211 according [RFC5891]. 213 214 The element contains the following child 215 elements: 217 218 The value SHALL be boolean and indicates if a client needs to 219 do something that is connection-related, such as a reconnect. 221 222 The value SHALL be boolean and indicates if a client needs to 223 do something that is implementation-related, such as a code 224 change. 226 227 Indicates the date and time of the maintenance object creation. 229 230 Indicates the date and time of the most recent maintenance object 231 modification. This element MUST NOT be present if the maintenance 232 object has never been modified. 234 3. EPP Command Mapping 236 A detailed description of the EPP syntax and semantics can be found 237 in the EPP core protocol specification [RFC5730]. The command 238 mappings described here are specifically for the use to notify of 239 Registry Maintenances and Registry Maintenance object mapping. 241 3.1. EPP Query Commands 243 EPP [RFC5730] provides three commands to retrieve object information: 244 to determine if an object is known to the server, to 245 retrieve detailed information associated with an object, and 246 to retrieve object transfer status information. 248 3.1.1. EPP Command 250 Available check semantics do not apply to maintenance objects, so 251 there is no mapping defined for the EPP command. 253 3.1.2. EPP Command 255 Transfer semantics do not apply to maintenance objects, so there is 256 no mapping defined for the EPP command. 258 3.1.3. EPP Command 260 EPP provides the command that is used to retrieve registry 261 maintenance information. In addition to the standard EPP command 262 elements, the command MUST contain a 263 element that identifies the maintenance namespace. 265 The element MUST contain a child element. It is either 266 , described in Section 3.1.3.1, to query for a specific 267 maintenance item or , described in Section 3.1.3.2, to 268 query all maintenance items. 270 3.1.3.1. Info Maintenance Item 272 The information on a specific maintenance item can be retrieved by 273 using the command with the element and the 274 child element, defined in Section 2.3. If the maintenance 275 identifier does not exist, the server MUST return an EPP error result 276 code of 2303 [RFC5730]. 278 Example to retrieve a specific maintenance item in an command. 280 C: 281 C: 282 C: 283 C: 284 C: 286 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 287 C: 288 C: 289 C: ABC-12345 290 C: 291 C: 293 When an command has been processed successfully, the EPP 294 element MUST contain a child element that 295 identifies the maintenance namespace. The element 296 contains the element defined in Section 2.3. 298 Example of returning a specific maintenance item in an 299 response. 301 S: 302 S: 303 S: 304 S: 305 S: Command completed successfully 306 S: 307 S: 308 S: 310 S: 311 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 312 S: 313 S: 314 S: 315 S: EPP 316 S: epp.registry.example 317 S: 318 S: full 319 S: 320 S: 321 S: 322 S: 2020-12-30T06:00:00Z 323 S: 2020-12-30T14:25:57Z 324 S: planned 325 S: 326 S: https://www.registry.example/notice?123 327 S: 328 S: free text 329 S: 330 S: 331 S: example 332 S: test 333 S: 334 S: 335 S: false 336 S: false 337 S: 338 S: 2020-09-08T22:10:00Z 339 S: 340 S: 341 S: 342 S: 343 S: ABC-12345 344 S: 54321-XYZ 345 S: 346 S: 347 S: 349 3.1.3.2. Info Maintenance List 351 The information for a list of maintenance items can be retrieved by 352 using the command with the element and the empty 353 child element. Server policy determines if previous 354 maintenances will be included in the list of maintenance items. 356 Example to retrieve the maintenance list in an command. 358 C: 359 C: 360 C: 361 C: 362 C: 364 C: 365 C: 366 C: 367 C: ABC-12345 368 C: 369 C: 371 When an command has been processed successfully, the EPP 372 element MUST contain a child element 373 that identifies the maintenance namespace. The 374 element contains the element with zero or more 375 child elements. The element 376 contains the following child elements: 377 : defined in Section 2.3. 378 : defined in Section 2.3. 379 : defined in Section 2.3. 380 : defined in Section 2.3. 381 : OPTIONAL defined in Section 2.3. 383 Example of returning the maintenance list in an response. 385 S: 386 S: 387 S: 388 S: 389 S: Command completed successfully 390 S: 391 S: 392 S: 394 S: 395 S: 396 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 397 S: 398 S: 2020-12-30T06:00:00Z 399 S: 2020-12-30T07:00:00Z 400 S: 2020-09-08T22:10:00Z 401 S: 402 S: 403 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 404 S: 405 S: 2021-02-15T04:30:00Z 406 S: 2021-02-15T05:30:00Z 407 S: 2020-09-08T22:11:00Z 408 S: 2020-10-17T15:00:00Z 409 S: 410 S: 411 S: 412 S: 413 S: 414 S: ABC-12345 415 S: 54321-XYZ 416 S: 417 S: 418 S: 420 3.1.4. EPP Command 422 The EPP command and response is defined in Section 2.9.2.3 of 423 [RFC5730]. The Registry Maintenance Notification is included in the 424 EPP response of [RFC5730]. 426 For the Registry Maintenance Notification, there are three types of 427 poll messages. A poll message applies when a maintenance is created, 428 updated, or deleted. In the case of a Registry Maintenance specific 429 message, a element will be included within the 430 element of the standard response. The 431 element contains the element defined 432 in Section 2.3. 434 Example command: 436 C: 437 C: 438 C: 439 C: 440 C: ABC-12345 441 C: 442 C: 444 Example response with the Registry Maintenance poll message: 446 S: 447 S: 448 S: 449 S: 450 S: Command completed successfully; ack to dequeue 451 S: 452 S: 453 S: 2020-10-08T22:10:00Z 454 S: Registry Maintenance Notification 455 S: 456 S: 457 S: 459 S: 460 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 461 S: 462 S: 463 S: EPP 464 S: epp.registry.example 465 S: 466 S: full 467 S: 468 S: 469 S: 470 S: 2020-12-30T06:00:00Z 471 S: 2020-12-30T14:25:57Z 472 S: planned 473 S: 474 S: https://www.registry.example/notice?123 475 S: 476 S: 477 S: example 478 S: test 479 S: 480 S: 481 S: false 482 S: false 483 S: 484 S: 2020-10-08T22:10:00Z 485 S: 486 S: 487 S: 488 S: 489 S: ABC-12345 490 S: 54321-XYZ 491 S: 492 S: 493 S: 495 3.2. EPP Transform Commands 497 EPP provides five commands to transform objects: to create 498 an instance of an object, to delete an instance of an 499 object, to extend the validity period of an object, 500 to manage object sponsorship changes, and to 501 change information associated with an object. 503 3.2.1. EPP Command 505 Create semantics do not apply to maintenance objects, so there is no 506 mapping defined for the EPP command. 508 3.2.2. EPP Command 510 Delete semantics do not apply to maintenance objects, so there is no 511 mapping defined for the EPP command. 513 3.2.3. EPP Command 515 Renew semantics do not apply to maintenance objects, so there is no 516 mapping defined for the EPP command. 518 3.2.4. EPP Command 520 Transfer semantics do not apply to maintenance objects, so there is 521 no mapping defined for the EPP command. 523 3.2.5. EPP Command 525 Update semantics do not apply to maintenance objects, so there is no 526 mapping defined for the EPP command. 528 4. Formal Syntax 530 The EPP Registry Maintenance schema is presented here. 532 The formal syntax presented here is a complete schema representation 533 of the object mapping suitable for automated validation of EPP XML 534 instances. The and tags are not part of 535 the schema; they are used to note the beginning and end of the 536 schema for URI registration purposes. 538 4.1. Registry Maintenance EPP Mapping Schema 540 541 542 549 552 553 554 555 556 Extensible Provisioning Protocol v1.0 557 Registry Maintenance Mapping Schema. 558 559 560 563 564 567 568 569 570 571 572 573 574 575 578 579 580 581 582 583 584 585 586 589 590 593 594 595 596 597 598 599 602 603 604 606 607 608 611 612 613 614 615 616 617 618 619 620 623 624 625 626 627 628 629 630 631 632 634 635 637 638 639 640 641 644 645 646 648 649 650 653 654 655 656 657 658 659 662 663 664 665 666 667 668 669 672 673 674 675 676 677 678 679 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 702 703 704 705 706 707 708 709 710 711 714 715 716 717 718 719 720 721 722 725 726 727 728 729 730 731 734 735 736 738 739 740 743 744 745 746 747 748 749 752 753 755 5. IANA Considerations 757 5.1. XML Namespace 759 This document uses URNs to describe XML namespaces and XML schemas 760 conforming to a registry mechanism defined in [RFC3688]. 762 Registration request for the maintenance namespace: 764 URI: urn:ietf:params:xml:ns:epp:maintenance-0.1 766 Registrant Contact: IESG 768 XML: None. Namespace URIs do not represent an XML specification. 770 Registration request for the maintenance schema: 772 URI: urn:ietf:params:xml:schema:maintenance-1.0 774 Registrant Contact: IESG 776 XML: See the "Formal Syntax" section of this document. 778 5.2. EPP Extension Registry 780 The following registration of the EPP Extension Registry, described 781 in [RFC7451], is requested: 783 Name of Extension: "Registry Maintenance Notifications for the 784 Extensible Provisioning Protocol (EPP)" 786 Document status: Standards Track 788 Reference: (insert the reference to RFC version of this document) 790 Registrant Name and Email Address: IESG, 792 TLDs: Any 794 IPR Disclosure: None 796 Status: Active 798 Notes: None 800 6. Security Considerations 802 The mapping extensions described in this document do not provide any 803 security services beyond those specified by EPP [RFC5730] and 804 protocol layers used by EPP. The security considerations described in 805 these other specifications apply to this specification as well. 807 7. Implementation Status 809 Note to RFC Editor: Please remove this section and the reference to 810 [RFC7942] before publication. 812 This section records the status of known implementations of the 813 protocol defined by this specification at the time of posting of this 814 Internet-Draft, and is based on a proposal described in [RFC7942]. 815 The description of implementations in this section is intended to 816 assist the IETF in its decision processes in progressing drafts to 817 RFCs. Please note that the listing of any individual implementation 818 here does not imply endorsement by the IETF. Furthermore, no effort 819 has been spent to verify the information presented here that was 820 supplied by IETF contributors. This is not intended as, and must not 821 be construed to be, a catalog of available implementations or their 822 features. Readers are advised to note that other implementations may 823 exist. 825 According to [RFC7942], "this will allow reviewers and working groups 826 to assign due consideration to documents that have the benefit of 827 running code, which may serve as evidence of valuable experimentation 828 and feedback that have made the implemented protocols more mature. It 829 is up to the individual working groups to use this information as 830 they see fit". 832 7.1. GoDaddy Registry 834 Organization: GoDaddy Registry 836 Name: GoDaddy Registry 838 Description: GoDaddy Registry provides maintenance notifications to 839 their registrars. 841 Level of maturity: Production 843 Coverage: All aspects of the protocol according to the draft version 844 2 are implemented with further updates to come. 846 Licensing: Proprietary 848 Contact: quoc@registry.godaddy 850 URL: https://registry.godaddy 852 8. References 854 8.1. Normative References 856 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 857 Requirement Levels", BCP 14, RFC 2119, March 1997, 858 . 860 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 861 DOI 10.17487/RFC3688, January 2004, 862 . 864 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 865 STD 69, RFC 5730, August 2009, 866 . 868 8.2. Informative References 870 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 871 Internet: Timestamps", RFC 3339, July 2002, 872 . 874 [RFC5891] Klensin, J., "Internationalized Domain Names in 875 Applications (IDNA): Protocol", RFC 5891, August 2010, 876 . 878 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 879 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 880 February 2015, . 882 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 883 Running Code: The Implementation Status Section", RFC 884 7942, July 2016, 885 . 887 Appendix A. Change History 889 A.1. Change from draft-sattler-epp-poll-maintenance-response to 890 draft-sattler-epp-registry-maintenance 892 Updated to be EPP based instead of JSON document. 894 A.2. Change from draft-sattler-epp-registry-maintenance to 895 draft-ietf-regext-epp-registry-maintenance 897 Adopted by the REGEXT working group. 899 A.3. Change from 00 to 01 901 Clarified maint:description and maint:environment. Changed 902 maint:description from complexType to simpleType. Fixed typo. 903 Added acknowledgment. 905 A.4. Change from 01 to 02 907 Update language from Domain Name Registry to Registry. Clarified 908 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 909 to contain hostName and hostAddr. Changed maint:tlds from MUST to 910 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 911 unique id. 913 A.5. Change from 02 to 03 915 Changed maint:connection from MUST to SHOULD. 917 A.6. Change from 03 to 04 919 A lot of clarifications and editoral changes. 921 A.7. Change from 04 to 05 923 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 924 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 925 Clarified for retrieving maintenance items and the list. 927 A.8. Change from 05 to 06 929 Changed dates in examples to more recent dates. Renamed Query 930 Maintenance Item and List to Info Maintenance Item and List. Removed 931 blackout in favor of full. Added GoDaddy Registry implementation. 933 A.9. Change from 06 to 07 935 Removed IP addresses for . Editoral changes. 937 Acknowledgments 939 The authors wish to thank the following persons for their feedback 940 and suggestions: James Gould, Patrick Mevzek, Quoc-Anh Pham, Raymond 941 Zylstra, Christopher Martens, Anthony Eden, Neal McPherson, Craig 942 Marchant, and Andreas Huber. 944 Authors' Addresses 946 Tobias Sattler 948 Email: tobias.sattler@me.com 949 URI: https://tobiassattler.com 951 Roger Carney 952 GoDaddy Inc. 953 14455 N. Hayden Rd. #219 954 Scottsdale, AZ 85260 955 US 957 Email: rcarney@godaddy.com 958 URI: http://www.godaddy.com 960 Jody Kolker 961 GoDaddy Inc. 962 14455 N. Hayden Rd. #219 963 Scottsdale, AZ 85260 964 US 966 Email: jkolker@godaddy.com 967 URI: http://www.godaddy.com