idnits 2.17.1 draft-ietf-regext-epp-registry-maintenance-05.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 1, 2020) is 1243 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 1, 2020 8 Registry Maintenance Notifications for the 9 Extensible Provisioning Protocol (EPP) 10 draft-ietf-regext-epp-registry-maintenance-05 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. Query Maintenance Item . . . . . . . . . . . . . . 7 59 3.1.3.2. Query 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 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 75 8.1. Normative References . . . . . . . . . . . . . . . . . . 18 76 8.2. Informative References . . . . . . . . . . . . . . . . . 19 77 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 19 78 A.1. Change from draft-sattler-epp-poll-maintenance-response to 79 draft-sattler-epp-registry-maintenance . . . . . . . . . 19 80 A.2. Change from draft-sattler-epp-registry-maintenance to 81 draft-ietf-regext-epp-registry-maintenance . . . . . . . 19 82 A.3. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 19 83 A.4. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 19 84 A.5. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 19 85 A.6. Change from 03 to 04 . . . . . . . . . . . . . . . . . . 20 86 A.7. Change from 04 to 05 . . . . . . . . . . . . . . . . . . 20 87 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 20 88 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 90 1. Introduction 92 Registries usually conduct maintenances and inform registrars in 93 different ways. Given the expansion of the DNS namespace, it is now 94 desirable to provide a method for EPP servers to notify EPP clients 95 as well as a method for EPP clients to query EPP servers for upcoming 96 maintenances. 98 This document describes an extension mapping for version 1.0 of the 99 Extensible Provision Protocol [RFC5730]. This mapping provides a 100 mechanism by which EPP servers may notify and EPP clients to query 101 for upcoming maintenances. 103 1.1. Terminology and Definitions 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in [RFC2119] when 108 specified in their uppercase forms. 110 XML is case sensitive. Unless stated otherwise, XML specifications 111 moreover, examples provided in this document MUST be interpreted in 112 the character case presented to develop a conforming implementation. 114 "maint" is used as an abbreviation for "urn:ietf:params:xml:ns:epp: 115 maintenance-0.1". The XML namespace prefix "maint" is used, but 116 implementations MUST NOT depend on it and instead employ a proper 117 namespace-aware XML parser and serializer to interpret and output 118 the XML documents. 120 In examples, "C:" represents lines sent by a protocol client and 121 "S:" represents lines returned by a protocol server. Indentation and 122 white space in examples are provided only to illustrate element 123 relationships and are not a REQUIRED feature of this protocol. 125 2. Object Attributes 127 2.1. Internationalized Domain Names 129 Names of affected hosts MUST be provided as A-label according to 130 [RFC5891]. 132 2.2. Dates and Times 134 All dates and times attribute values MUST be expressed in Universal 135 Coordinated Time (UTC) using the Gregorian calendar. The extended 136 date-time form using upper case "T" and "Z" characters defined in ISO 137 8601 [RFC3339] MUST be used to represent date-time values. 139 2.3. Maintenance Elements 141 The element describes a single registry maintenance 142 event during a specific period. This element will be used at EPP 143 messages and to extend the EPP command. 145 For creating a new maintenance the attribute MUST be 146 set and the attribute SHALL NOT be present. 148 For updating a maintenance the attributes and 149 MUST be set. 151 152 MUST be present and a server unique id and SHALL NOT be 153 changed if maintenance is updated or deleted. A human-readable 154 description of the maintenance is identified via an OPTIONAL 155 "msg" attribute. 157 158 MUST be present and contains one or more elements. 159 The server SHOULD NOT list systems which are not affected by the 160 maintenance. 162 163 MUST be present at least once and has an element of , 164 and . 166 167 MUST be present and indicates the name of the affected system, 168 such as "EPP", "WHOIS", "DNS", "Portal", etc. 170 171 MUST be present and indicates the affected maintained system 172 contains the hostname and OPTIONAL an IP address. 173 Hostname SHALL be A-label according [RFC5891]. 174 IPv4 addresses SHALL be dotted-decimal notation. 175 An example of this textual representation is "192.0.2.0". 176 IPv6 addresses SHALL be according [RFC5952]. 177 An example of this textual representation is 178 "2001:db8::1:0:0:1". 180 181 MUST be present and contains the impact level; values MUST 182 either be "full" or "partial". 184 185 MUST be present and indicates the type of the affected system; 186 the attribute type is REQUIRED and SHOULD either be "production", 187 "ote", "staging", "dev" or "custom". And alternatively the 188 attribute name could be used to define a server specific affected 189 system for example. In that case name MUST be set: 190 192 193 SHOULD be present and indicates the start of the maintenance 194 according ISO 8601 [RFC3339]. 195 Format: YYYY-MM-DDThh:mm:ssTZ 197 198 SHOULD be present and indicates the end of the maintenance 199 according to ISO 8601 [RFC3339], and MUST be equal to or greater 200 than . 201 Format: YYYY-MM-DDThh:mm:ssTZ 203 204 MUST be present and contains the reason behind the maintenance; 205 values SHOULD either be "planned" or "emergency". 207 208 MAY be present and contains URI to detailed maintenance 209 description. 211 212 MAY be present and provides a freeform description of the 213 maintenance without having to create and traverse an external 214 resource. 216 217 SHOULD be present and contains elements. 219 220 MUST be present and contains the affected top-level domain. 221 A-label format according to [RFC5891]. 223 224 SHOULD be present and contains and 225 . 227 228 MUST be present and indicates if a client needs to do 229 something that is connection-related, such as a reconnect. The 230 value SHALL be boolean. 232 233 MUST be present and indicates if a client needs to do something 234 that is implementation-related, such as a code change. The 235 value SHALL be boolean. 237 238 MUST be present and contains the creation date of the maintenance 239 according ISO 8601 [RFC3339]. 240 Format: YYYY-MM-DDThh:mm:ssTZ 242 243 MAY be present and contains the updated date of the maintenance 244 according to ISO 8601 [RFC3339], and if set MUST be equal to or 245 greater than . 246 Format: YYYY-MM-DDThh:mm:ssTZ 248 3. EPP Command Mapping 250 A detailed description of the EPP syntax and semantics can be found 251 in the EPP core protocol specification [RFC5730]. The command 252 mappings described here are specifically for the use to notify of 253 Registry Maintenances and Registry Maintenance object mapping. 255 3.1. EPP Query Commands 257 EPP [RFC5730] provides three commands to retrieve object information: 258 to determine if an object is known to the server, to 259 retrieve detailed information associated with an object, and 260 to retrieve object transfer status information. 262 3.1.1. EPP Command 264 Available check semantics do not apply to maintenance objects, so 265 there is no mapping defined for the EPP command. 267 3.1.2. EPP Command 269 Transfer semantics do not apply to maintenance objects, so there is 270 no mapping defined for the EPP command. 272 3.1.3. EPP Command 274 EPP provides the command that is used to retrieve registry 275 maintenance information. In addition to the standard EPP command 276 elements, the command MUST contain a 277 element that identifies the maintenance namespace. 279 The element MUST contain a child element. It is either 280 to retrieve a specific maintenance notification or 281 to query all maintenance notifications. 283 3.1.3.1. Query one maintenance item 285 If a is send with a that does not exist on 286 the server side, then the result code 2303 MUST be responded. 288 Please see the defintion of elements in Section 2.3. 290 Example command with explicit to get one specific 291 maintenance: 293 C: 294 C: 295 C: 296 C: 297 C: 299 C: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 300 C: 301 C: 302 C: ABC-12345 303 C: 304 C: 306 Example response for one specific maintenance notification, 307 which was requested with a explicit . In this case, it 308 provides the all "required" elements and additional elements 309 , , , , 310 , . 312 S: 313 S: 314 S: 315 S: 316 S: Command completed successfully 317 S: 318 S: 319 S: 321 S: 322 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 323 S: 324 S: 325 S: 326 S: EPP 327 S: epp.registry.example 328 S: 329 S: blackout 330 S: 331 S: 332 S: 333 S: 2017-09-30T06:00:00Z 334 S: 2017-09-30T14:25:57Z 335 S: planned 336 S: 337 S: https://www.registry.example/notice?123 338 S: 339 S: free text 340 S: 341 S: 342 S: example 343 S: test 344 S: 345 S: 346 S: false 347 S: false 348 S: 349 S: 2017-03-08T22:10:00Z 350 S: 351 S: 352 S: 353 S: 354 S: ABC-12345 355 S: 54321-XYZ 356 S: 357 S: 358 S: 360 3.1.3.2. Query maintenance list 362 Example command with to query all maintenances 363 subject to server policy: 365 C: 366 C: 367 C: 368 C: 369 C: 371 C: 372 C: 373 C: 374 C: ABC-12345 375 C: 376 C: 378 Example response querying all maintenances subject to server 379 policy. In this case, all the "required" elements will be returned 380 and additional . 382 S: 383 S: 384 S: 385 S: 386 S: Command completed successfully 387 S: 388 S: 389 S: 391 S: 392 S: 393 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 394 S: 395 S: 2017-04-30T06:00:00Z 396 S: 2017-04-30T07:00:00Z 397 S: 2017-02-08T22:10:00Z 398 S: 399 S: 400 S: 91e9dabf-c4e9-4c19-a56c-78e3e89c2e2f 401 S: 402 S: 2017-06-15T04:30:00Z 403 S: 2017-06-15T05:30:00Z 404 S: 2017-02-08T22:10:00Z 405 S: 2017-03-08T20:11:00Z 406 S: 407 S: 408 S: 409 S: 410 S: 411 S: ABC-12345 412 S: 54321-XYZ 413 S: 414 S: 415 S: 417 3.1.4. EPP Command 419 The EPP command and response is defined in Section 2.9.2.3 of 420 [RFC5730]. The Registry Maintenance Notification is included in the 421 EPP response of [RFC5730]. 423 For the Registry Maintenance Notification, there are three types of 424 poll messages. The poll message applies whenever the domain name 425 registry creates, updates, or deletes maintenance. In the case of 426 a Registry Maintenance specific message, a element 427 will be included within the element of the standard 428 response. 430 The element will include a reference to the 431 Registry Maintenance namespace. EPP data contained within the 432 element is formatted according to the 433 maintenance-poll schema. 435 Please see the defintion of elements in Section 2.3. 437 Example command: 439 C: 440 C: 441 C: 442 C: 443 C: ABC-12345 444 C: 445 C: 447 Example response with the Registry Maintenance poll message: 449 S: 450 S: 451 S: 452 S: 453 S: Command completed successfully; ack to dequeue 454 S: 455 S: 456 S: 2017-02-08T22:10:00Z 457 S: Registry Maintenance Notification 458 S: 459 S: 460 S: 462 S: 463 S: 2e6df9b0-4092-4491-bcc8-9fb2166dcee6 464 S: 465 S: 466 S: EPP 467 S: epp.registry.example 468 S: 469 S: blackout 470 S: 471 S: 472 S: 473 S: 2017-10-30T06:00:00Z 474 S: 2017-10-30T14:25:57Z 475 S: planned 476 S: 477 S: https://www.registry.example/notice?123 478 S: 479 S: 480 S: example 481 S: test 482 S: 483 S: 484 S: false 485 S: false 486 S: 487 S: 2017-02-08T22:10:00Z 488 S: 489 S: 490 S: 491 S: 492 S: ABC-12345 493 S: 54321-XYZ 494 S: 495 S: 496 S: 498 3.2. EPP Transform Commands 500 EPP provides five commands to transform objects: to create 501 an instance of an object, to delete an instance of an 502 object, to extend the validity period of an object, 503 to manage object sponsorship changes, and to 504 change information associated with an object. 506 3.2.1. EPP Command 508 Create semantics do not apply to maintenance objects, so there is no 509 mapping defined for the EPP command. 511 3.2.2. EPP Command 513 Delete semantics do not apply to maintenance objects, so there is no 514 mapping defined for the EPP command. 516 3.2.3. EPP Command 518 Renew semantics do not apply to maintenance objects, so there is no 519 mapping defined for the EPP command. 521 3.2.4. EPP Command 523 Transfer semantics do not apply to maintenance objects, so there is 524 no mapping defined for the EPP command. 526 3.2.5. EPP Command 528 Update semantics do not apply to maintenance objects, so there is no 529 mapping defined for the EPP command. 531 4. Formal Syntax 533 One schema is presented here that is the EPP Registry Maintenance 534 schema. 536 The formal syntax presented here is a complete schema representation 537 of the object mapping suitable for automated validation of EPP XML 538 instances. The BEGIN and END tags are not part of the schema; they 539 are used to note the beginning and end of the schema for URI 540 registration purposes. 542 4.1. Registry Maintenance EPP Mapping Schema 544 BEGIN 545 546 554 557 558 560 561 562 Extensible Provisioning Protocol v1.0 563 Maintenance Mapping Schema. 564 565 567 570 572 575 576 577 578 579 580 581 582 583 586 587 588 589 590 591 592 593 595 598 600 603 604 605 606 607 608 610 613 614 615 617 618 620 623 624 625 626 627 628 629 630 631 632 635 636 637 638 639 640 641 642 643 644 646 647 649 650 651 652 654 657 658 659 661 662 664 667 668 669 670 671 672 674 677 678 679 680 681 682 683 684 687 688 689 690 691 692 693 695 698 699 700 701 702 703 704 706 707 708 709 710 711 713 714 715 716 717 718 720 723 724 725 726 727 728 729 730 731 732 735 736 737 738 739 740 741 742 744 747 748 749 750 751 752 754 757 758 759 761 762 764 767 768 769 770 771 772 773 776 777 END 779 5. IANA Considerations 781 5.1. XML Namespace 783 This document uses URNs to describe XML namespaces and XML schemas 784 conforming to a registry mechanism defined in [RFC3688]. 786 Registration request for the maintenance namespace: 788 URI: urn:ietf:params:xml:ns:epp:maintenance-0.1 790 Registrant Contact: IESG 792 XML: None. Namespace URIs do not represent an XML specification. 794 Registration request for the maintenance schema: 796 URI: urn:ietf:params:xml:schema:maintenance-1.0 798 Registrant Contact: IESG 800 XML: See the "Formal Syntax" section of this document. 802 5.2. EPP Extension Registry 804 The following registration of the EPP Extension Registry, described 805 in [RFC7451], is requested: 807 Name of Extension: "Registry Maintenance Notifications for the 808 Extensible Provisioning Protocol (EPP)" 810 Document status: Standards Track 812 Reference: (insert the reference to RFC version of this document) 814 Registrant Name and Email Address: IESG, 816 TLDs: Any 818 IPR Disclosure: None 820 Status: Active 822 Notes: None 824 6. Security Considerations 826 The mapping extensions described in this document do not provide any 827 security services beyond those specified by EPP [RFC5730] and 828 protocol layers used by EPP. The security considerations described in 829 these other specifications apply to this specification as well. 831 7. Implementation Status 833 Note to RFC Editor: Please remove this section and the reference to 834 [RFC7942] before publication. 836 This section records the status of known implementations of the 837 protocol defined by this specification at the time of posting of this 838 Internet-Draft, and is based on a proposal described in [RFC7942]. 839 The description of implementations in this section is intended to 840 assist the IETF in its decision processes in progressing drafts to 841 RFCs. Please note that the listing of any individual implementation 842 here does not imply endorsement by the IETF. Furthermore, no effort 843 has been spent to verify the information presented here that was 844 supplied by IETF contributors. This is not intended as, and must not 845 be construed to be, a catalog of available implementations or their 846 features. Readers are advised to note that other implementations may 847 exist. 849 According to [RFC7942], "this will allow reviewers and working groups 850 to assign due consideration to documents that have the benefit of 851 running code, which may serve as evidence of valuable experimentation 852 and feedback that have made the implemented protocols more mature. It 853 is up to the individual working groups to use this information as 854 they see fit". 856 Add implementation details once available. 858 8. References 860 8.1. Normative References 862 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 863 Requirement Levels", BCP 14, RFC 2119, March 1997, 864 . 866 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 867 DOI 10.17487/RFC3688, January 2004, 868 . 870 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 871 STD 69, RFC 5730, August 2009, 872 . 874 8.2. Informative References 876 [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the 877 Internet: Timestamps", RFC 3339, July 2002, 878 . 880 [RFC5891] Klensin, J., "Internationalized Domain Names in 881 Applications (IDNA): Protocol", RFC 5891, August 2010, 882 . 884 [RFC5952] Kawamura, S. and Kawashima, M., "A Recommendation for IPv6 885 Address Text Representation", RFC 5952, August 2010, 886 . 888 [RFC7451] Hollenbeck, S., "Extension Registry for the Extensible 889 Provisioning Protocol", RFC 7451, DOI 10.17487/RFC7451, 890 February 2015, . 892 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 893 Running Code: The Implementation Status Section", RFC 894 7942, July 2016, 895 . 897 Appendix A. Change History 899 A.1. Change from draft-sattler-epp-poll-maintenance-response to 900 draft-sattler-epp-registry-maintenance 902 Updated to be EPP based instead of JSON document. 904 A.2. Change from draft-sattler-epp-registry-maintenance to 905 draft-ietf-regext-epp-registry-maintenance 907 Adopted by the REGEXT working group. 909 A.3. Change from 00 to 01 911 Clarified maint:description and maint:environment. Changed 912 maint:description from complexType to simpleType. Fixed typo. 913 Added acknowledgment. 915 A.4. Change from 01 to 02 917 Update language from Domain Name Registry to Registry. Clarified 918 XML namespace urn:ietf:params:xml:ns:maintenance-1.0. Changed host 919 to contain hostName and hostAddr. Changed maint:tlds from MUST to 920 SHOULD. Fixed maint:status in Schema. Changed UUID to a server 921 unique id. 923 A.5. Change from 02 to 03 925 Changed maint:connection from MUST to SHOULD. 927 A.6. Change from 03 to 04 929 A lot of clarifications and editoral changes. 931 A.7. Change from 04 to 05 933 Changed XML namespace from urn:ietf:params:xml:ns:maintenance-1.0 to 934 urn:ietf:params:xml:ns:epp:maintenance-0.1. Removed . 935 Clarified for retrieving maintenance items and the list. 937 Acknowledgments 939 The authors wish to thank the following individuals for their 940 feedback and suggestions (sorted alphabetically by company): 942 o Patrick Mevzek 943 o Neal McPherson, 1&1 IONOS 944 o Anthony Eden, DNSimple 945 o Christopher Martens, Donuts 946 o Quoc-Anh Pham, Neustar 947 o Raymond Zylstra, Neustar 948 o Andreas Huber, united-domains 949 o Craig Marchant, VentraIP 950 o James Gould, Verisign 952 Authors' Addresses 954 Tobias Sattler 956 Email: tobias.sattler@me.com 957 URI: https://tobiassattler.com 959 Roger Carney 960 GoDaddy Inc. 961 14455 N. Hayden Rd. #219 962 Scottsdale, AZ 85260 963 US 965 Email: rcarney@godaddy.com 966 URI: http://www.godaddy.com 968 Jody Kolker 969 GoDaddy Inc. 970 14455 N. Hayden Rd. #219 971 Scottsdale, AZ 85260 972 US 974 Email: jkolker@godaddy.com 975 URI: http://www.godaddy.com