idnits 2.17.1 draft-ietf-regext-validate-02.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 (August 3, 2017) is 2430 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) == Missing Reference: 'RFC6982' is mentioned on line 509, but not defined ** Obsolete undefined reference: RFC 6982 (Obsoleted by RFC 7942) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Registration Protocols Extensions R. Carney 3 Internet-Draft J. Snitker 4 Intended status: Standards Track GoDaddy Inc. 5 Expires: February 4, 2018 August 3, 2017 7 Validate Mapping for the Extensible Provisioning Protocol (EPP) 8 draft-ietf-regext-validate-02 10 Abstract 12 This document describes an Extensible Provisioning Protocol (EPP) 13 mapping for the validation of contact and eligibility data. 15 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 http://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 February 4, 2018. 32 Copyright Notice 34 Copyright (c) 2017 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 51 2. Object Attributes . . . . . . . . . . . . . . . . . . . . . . 3 52 2.1. Key Value . . . . . . . . . . . . . . . . . . . . . . . . 3 53 3. EPP Command Mapping . . . . . . . . . . . . . . . . . . . . . 3 54 3.1. EPP Query Commands . . . . . . . . . . . . . . . . . . . 3 55 3.1.1. EPP Command . . . . . . . . . . . . . . . . . 4 56 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 7 57 3.1.3. EPP Command . . . . . . . . . . . . . . . 7 58 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 8 59 3.2.1. EPP Command . . . . . . . . . . . . . . . . 8 60 3.2.2. EPP Command . . . . . . . . . . . . . . . . 8 61 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 8 62 3.2.4. EPP Command . . . . . . . . . . . . . . . 8 63 3.2.5. EPP Command . . . . . . . . . . . . . . . . 8 64 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 8 65 4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 11 67 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 68 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11 69 7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 12 70 7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 12 71 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 72 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12 73 9.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 12 74 9.2. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 13 75 9.3. Change from carney-regext 01 to ietf-regext 00 . . . . . 13 76 10. Normative References . . . . . . . . . . . . . . . . . . . . 13 77 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13 79 1. Introduction 81 This document describes a Validate mapping for version 1.0 of the 82 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 83 specifies a flexible schema by which EPP clients and servers can 84 reliably validate contact and eligibility data. 86 With the increased number of restrictions on contacts and required 87 data points (license, ids, etc.) to register a domain name, a way to 88 validate the data points prior to issuing a transform command is 89 becoming more important. 91 1.1. Conventions Used in This Document 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in RFC 2119 [RFC2119]. 97 XML is case sensitive. Unless stated otherwise, XML specifications 98 and examples provided in this document MUST be interpreted in the 99 character case presented in order to develop a conforming 100 implementation. 102 In examples, "C:" represents lines sent by a protocol client and "S:" 103 represents lines returned by a protocol server. Indentation and 104 white space in examples are provided only to illustrate element 105 relationships and are not a REQUIRED feature of this protocol. 107 2. Object Attributes 109 A EPP validation object has attributes and associated values that can 110 be viewed by the client. This section describes each attribute type 111 in detail. 113 2.1. Key Value 115 Key Value provides a flexible mechanism to share data between the 116 client and the server. The element defines the data, 117 with two required simple attributes, key and value, and an optional 118 contactType attribute for specificity in the response, more details 119 below. 121 o An example . 122 o An example . 125 3. EPP Command Mapping 127 A detailed description of the EPP syntax and semantics can be found 128 in [RFC5730]. The command mappings described here are specifically 129 for the Validate Extension. 131 3.1. EPP Query Commands 133 EPP provides three commands to retrieve object information: 134 to determine if an object is known to the server, to retrieve 135 detailed information associated with an object, and to 136 retrieve object transfer status information. 138 3.1.1. EPP Command 140 The EPP command is used to validate a list of contact 141 information. The command MUST contain a 142 element that identifies the validate namespace. The 143 element contains the following child elements: 145 o one or more element(s) for each contact that is 146 to be validated that contains the contact type of the contact to 147 be validated. 149 The element MUST contain the following child 150 elements: 152 o one element. 153 o zero or more elements. 155 The element MUST contain the following child elements: 157 o one element. 158 o an OPTIONAL element. 159 o an OPTIONAL element. 160 o an OPTIONAL element. 161 o an OPTIONAL element. 162 o an OPTIONAL element. 163 o an OPTIONAL element. 165 The following is an example command. 167 C: 168 C: 171 C: 172 C: 173 C: 174 C: 175 C: 176 C: sh8013 177 C: 178 C: John Doe 179 C: Example Inc. 180 C: 181 C: 123 Example Dr. 182 C: Suite 100 183 C: Dulles 184 C: VA 185 C: 20166-6503 186 C: US 187 C: 188 C: 189 C: +1.7035555555 190 C: +1.7035555556 191 C: jdoe@example.com 192 C: 193 C: 2fooBAR 194 C: 195 C: 196 C: 197 C: 198 C: 199 C: 200 C: 201 C: 202 C: 203 C: 204 C: sh8013 205 C: 206 C: 207 C: 208 C: 209 C: sh8014 210 C: 211 C: John Doe 212 C: Example Inc. 213 C: 214 C: 123 Example Dr. 215 C: Suite 100 216 C: Dulles 217 C: VA 218 C: 20166-6503 219 C: US 220 C: 221 C: 222 C: +1.7035555555 223 C: +1.7035555556 224 C: jdoe@example.com 225 C: 226 C: 2fooBAR 227 C: 228 C: 229 C: 230 C: 231 C: 232 C: 233 C: 234 C: 235 C: 236 C: sh8014 237 C: 238 C: 239 C: 240 C: 241 C: ABC-12345 242 C: 243 C: 245 When a command has been processed succesfully, the EPP 246 element MUST contain a child element 247 that identifies the validate namespace. The 248 element MUST contain a element for each 249 element contained in the command. The 250 element MUST contain the following child elements: 252 o one element. 253 o one element. 254 o zero or more elements. 256 The following is an example of the response. 258 S: 259 S: 260 S: 261 S: 262 S: Command completed successfully 263 S: 264 S: 265 S: 267 S: 268 S: sh8013 269 S: 1000 270 S: 271 S: 272 S: sh8014 273 S: 2306 274 S: 276 S: 278 S: 280 S: 281 S: 282 S: 283 S: 284 S: ABC-12345 285 S: 54321-ZYX 286 S: 287 S: 288 S: 290 3.1.2. EPP Command 292 Info semantics do not apply to validate objects, so there is no 293 mapping defined for the EPP command. 295 3.1.3. EPP Command 297 Transfer semantics do not apply to validate objects, so there is no 298 mapping defined for the EPP command. 300 3.2. EPP Transform Commands 302 EPP provides five commands to transform objects: to create 303 an instance of an object with a server, to remove an 304 instance of an object from a server, to extend the validity 305 period of an object, to manage changes in client 306 sponsorship of an object, and to change information. 308 3.2.1. EPP Command 310 Create semantics do not apply to validate objects, so there is no 311 mapping defined for the EPP command. 313 3.2.2. EPP Command 315 Delete semantics do not apply to validate objects, so there is no 316 mapping defined for the EPP command. 318 3.2.3. EPP Command 320 Renew semantics do not apply to validate objects, so there is no 321 mapping defined for the EPP command. 323 3.2.4. EPP Command 325 Transfer semantics do not apply to validate objects, so there is no 326 mapping defined for the EPP command. 328 3.2.5. EPP Command 330 Update semantics do not apply to validate objects, so there is no 331 mapping defined for the EPP command. 333 4. Formal Syntax 335 One schema is presented here that is the EPP Validate schema. 337 The formal syntax presented here is a complete schema representation 338 of the object mapping suitable for automated validation of EPP XML 339 instances. The BEGIN and END tags are not part of the schema; they 340 are used to note the beginning and ending of the schema for URI 341 registration purposes. 343 4.1. Validate Schema 345 BEGIN 346 347 356 357 358 Extensible Provisioning Protocol v1.0 359 Validate Object 360 361 363 364 366 368 371 374 376 377 378 381 382 384 385 386 388 391 392 394 397 399 400 401 403 406 408 410 412 415 418 419 421 422 424 426 428 430 431 432 433 434 436 437 438 439 440 442 445 447 448 449 451 452 454 455 456 458 460 463 464 466 467 END 469 5. Security Considerations 471 The mapping extensions described in this document do not provide any 472 security services beyond those described by EPP [RFC5730] and 473 protocol layers used by EPP. The security considerations described 474 in these other specifications apply to this specification as well. 476 6. IANA Considerations 478 6.1. XML Namespace 480 This document uses URNs to describe XML namespaces and XML schemas 481 conforming to a registry mechanism described in [RFC3688]. The 482 following URI assignment is requested of IANA: 484 URI: ietf:params:xml:ns:validate-1.0 486 Registrant Contact: See the "Author's Address" section of this 487 document. 489 XML: See the "Formal Syntax" section of this document. 491 7. Implemntation Status 493 Note to RFC Editor: Please remove this section and the reference to 494 [RFC6982] before publication. 496 This section records the status of known implementations of the 497 protocol defined by this specification at the time of posting of this 498 Internet-Draft, and is based on a proposal described in [RFC6982]. 499 The description of implementations in this section is intended to 500 assist the IETF in its decision processes in progressing drafts to 501 RFCs. Please note that the listing of any individual implementation 502 here does not imply endorsement by the IETF. Furthermore, no effort 503 has been spent to verify the information presented here that was 504 supplied by IETF contributors. This is not intended as, and must not 505 be construed to be, a catalog of available implementations or their 506 features. Readers are advised to note that other implementations may 507 exist. 509 According to [RFC6982], "this will allow reviewers and working groups 510 to assign due consideration to documents that have the benefit of 511 running code, which may serve as evidence of valuable experimentation 512 and feedback that have made the implemented protocols more mature. 513 It is up to the individual working groups to use this information as 514 they see fit". 516 7.1. To Be Filled In 518 Add implementation details once available. 520 8. Acknowledgements 522 The authors wish to thank the following persons for their feedback 523 and suggestions: 525 o Kevin Allendorf of GoDaddy Inc. 526 o Jody Kolker of GoDaddy Inc. 527 o James Gould of Verisign Inc 529 9. Change History 531 9.1. Change from 00 to 01 533 Corrected some formatting issues 535 9.2. Change from 00 to 01 537 After review and broad feedback, extensive changes have been made 538 transforming the original document from a standalone extension 539 command to using the command and response framework. Stubbed 540 in an Implementation section for later documentation. 542 9.3. Change from carney-regext 01 to ietf-regext 00 544 Updated miscellaneous verbiage to reflect the change from an 545 extension and changed to ietf naming as REGEXT WG will assume this 546 work. 548 10. Normative References 550 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 551 Requirement Levels", BCP 14, RFC 2119, 552 DOI 10.17487/RFC2119, March 1997, 553 . 555 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 556 DOI 10.17487/RFC3688, January 2004, 557 . 559 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 560 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 561 . 563 Authors' Addresses 565 Roger Carney 566 GoDaddy Inc. 567 14455 N. Hayden Rd. #219 568 Scottsdale, AZ 85260 569 US 571 Email: rcarney@godaddy.com 572 URI: http://www.godaddy.com 574 Joseph Snitker 575 GoDaddy Inc. 576 14455 N. Hayden Rd. #219 577 Scottsdale, AZ 85260 578 US 580 Email: jsnitker@godaddy.com 581 URI: http://www.godaddy.com