idnits 2.17.1 draft-ietf-regext-validate-01.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 (June 4, 2017) is 2510 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 507, 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: December 6, 2017 June 4, 2017 7 Validate Mapping for the Extensible Provisioning Protocol (EPP) 8 draft-ietf-regext-validate-01 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 December 6, 2017. 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 . . . . . . . . . . . . 2 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 . . . . . . . . . . . . . . . . . 3 56 3.1.2. EPP Command . . . . . . . . . . . . . . . . . 7 57 3.1.3. EPP Command . . . . . . . . . . . . . . . 7 58 3.2. EPP Transform Commands . . . . . . . . . . . . . . . . . 7 59 3.2.1. EPP Command . . . . . . . . . . . . . . . . 7 60 3.2.2. EPP Command . . . . . . . . . . . . . . . . 7 61 3.2.3. EPP Command . . . . . . . . . . . . . . . . . 7 62 3.2.4. EPP Command . . . . . . . . . . . . . . . 7 63 3.2.5. EPP Command . . . . . . . . . . . . . . . . 7 64 4. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . 7 65 4.1. Validate Schema . . . . . . . . . . . . . . . . . . . . . 8 66 5. Security Considerations . . . . . . . . . . . . . . . . . . . 10 67 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 68 6.1. XML Namespace . . . . . . . . . . . . . . . . . . . . . . 11 69 7. Implemntation Status . . . . . . . . . . . . . . . . . . . . 11 70 7.1. To Be Filled In . . . . . . . . . . . . . . . . . . . . . 11 71 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11 72 9. Change History . . . . . . . . . . . . . . . . . . . . . . . 12 73 9.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 12 74 9.2. Change from carney-regext 01 to ietf-regext 00 . . . . . 12 75 10. Normative References . . . . . . . . . . . . . . . . . . . . 12 76 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 78 1. Introduction 80 This document describes a Validate mapping for version 1.0 of the 81 Extensible Provisioning Protocol (EPP) [RFC5730]. This EPP mapping 82 specifies a flexible schema by which EPP clients and servers can 83 reliably validate contact and eligibility data. 85 With the increased number of restrictions on contacts and required 86 data points (license, ids, etc.) to register a domain name, a way to 87 validate the data points prior to issuing a transform command is 88 becoming more important. 90 1.1. Conventions Used in This Document 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 94 document are to be interpreted as described in RFC 2119 [RFC2119]. 96 XML is case sensitive. Unless stated otherwise, XML specifications 97 and examples provided in this document MUST be interpreted in the 98 character case presented in order to develop a conforming 99 implementation. 101 In examples, "C:" represents lines sent by a protocol client and "S:" 102 represents lines returned by a protocol server. Indentation and 103 white space in examples are provided only to illustrate element 104 relationships and are not a REQUIRED feature of this protocol. 106 2. Object Attributes 108 A EPP validation object has attributes and associated values that can 109 be viewed by the client. This section describes each attribute type 110 in detail. 112 2.1. Key Value 114 Key Value provides a flexible mechanism to share data between the 115 client and the server. The element defines the data, 116 with two required simple attributes, key and value, and an optional 117 contactType attribute for specificity in the response, more details 118 below. 120 o An example . 121 o An example . 124 3. EPP Command Mapping 126 A detailed description of the EPP syntax and semantics can be found 127 in [RFC5730]. The command mappings described here are specifically 128 for the Validate Extension. 130 3.1. EPP Query Commands 132 EPP provides three commands to retrieve object information: 133 to determine if an object is known to the server, to retrieve 134 detailed information associated with an object, and to 135 retrieve object transfer status information. 137 3.1.1. EPP Command 139 The EPP command is used to validate a list of contact 140 information. The command MUST contain a 141 element that identifies the validate namespace. The 142 element contains the following child elements: 144 o one or more element(s) for each contact that is 145 to be validated that contains the contact type of the contact to 146 be validated. 148 The element MUST contain the following child 149 elements: 151 o one element. 152 o zero or more elements. 154 The element MUST contain the following child elements: 156 o one element. 157 o an OPTIONAL 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. 164 The following is an example command. 166 C: 167 C: 170 C: 171 C: 172 C: 173 C: 174 C: 175 C: sh8013 176 C: 177 C: John Doe 178 C: Example Inc. 179 C: 180 C: 123 Example Dr. 181 C: Suite 100 182 C: Dulles 183 C: VA 184 C: 20166-6503 185 C: US 186 C: 187 C: 188 C: +1.7035555555 189 C: +1.7035555556 190 C: jdoe@example.com 191 C: 192 C: 2fooBAR 193 C: 194 C: 195 C: 196 C: 197 C: 198 C: 199 C: 200 C: 201 C: 202 C: 203 C: sh8013 204 C: 205 C: 206 C: 207 C: 208 C: sh8014 209 C: 210 C: John Doe 211 C: Example Inc. 212 C: 213 C: 123 Example Dr. 214 C: Suite 100 215 C: Dulles 216 C: VA 217 C: 20166-6503 218 C: US 219 C: 220 C: 221 C: +1.7035555555 222 C: +1.7035555556 223 C: jdoe@example.com 224 C: 225 C: 2fooBAR 226 C: 227 C: 228 C: 229 C: 230 C: 231 C: 232 C: 233 C: 234 C: 235 C: sh8014 236 C: 237 C: 238 C: 239 C: 240 C: ABC-12345 241 C: 242 C: 244 When a command has been processed succesfully, the EPP 245 element MUST contain a child element 246 that identifies the validate namespace. The 247 element MUST contain a element for each 248 element contained in the command. The 249 element MUST contain the following child elements: 251 o one element. 252 o one element. 253 o zero or more elements. 255 The following is an example of the response. 257 S: 258 S: 259 S: 260 S: 261 S: Command completed successfully 262 S: 263 S: 264 S: 266 S: 267 S: sh8013 268 S: 1000 269 S: 270 S: 271 S: sh8014 272 S: 2306 273 S: 275 S: 277 S: 279 S: 280 S: 281 S: 282 S: 283 S: ABC-12345 284 S: 54321-ZYX 285 S: 286 S: 287 S: 289 3.1.2. EPP Command 291 Info semantics do not apply to validate objects, so there is no 292 mapping defined for the EPP command. 294 3.1.3. EPP Command 296 Transfer semantics do not apply to validate objects, so there is no 297 mapping defined for the EPP command. 299 3.2. EPP Transform Commands 301 EPP provides five commands to transform objects: to create 302 an instance of an object with a server, to remove an 303 instance of an object from a server, to extend the validity 304 period of an object, to manage changes in client 305 sponsorship of an object, and to change information. 307 3.2.1. EPP Command 309 Create semantics do not apply to validate objects, so there is no 310 mapping defined for the EPP command. 312 3.2.2. EPP Command 314 Delete semantics do not apply to validate objects, so there is no 315 mapping defined for the EPP command. 317 3.2.3. EPP Command 319 Renew semantics do not apply to validate objects, so there is no 320 mapping defined for the EPP command. 322 3.2.4. EPP Command 324 Transfer semantics do not apply to validate objects, so there is no 325 mapping defined for the EPP command. 327 3.2.5. EPP Command 329 Update semantics do not apply to validate objects, so there is no 330 mapping defined for the EPP command. 332 4. Formal Syntax 334 One schema is presented here that is the EPP Validate schema. 336 The formal syntax presented here is a complete schema representation 337 of the object mapping suitable for automated validation of EPP XML 338 instances. The BEGIN and END tags are not part of the schema; they 339 are used to note the beginning and ending of the schema for URI 340 registration purposes. 342 4.1. Validate Schema 344 BEGIN 345 346 355 356 357 Extensible Provisioning Protocol v1.0 358 Validate Object 359 360 362 363 365 367 370 373 375 376 377 380 381 383 384 385 387 390 391 393 395 397 398 399 401 404 406 408 410 413 416 417 419 420 422 424 426 428 429 430 431 433 435 436 437 438 439 441 444 446 447 448 450 451 453 454 455 457 459 462 463 465 466 END 468 5. Security Considerations 470 The mapping extensions described in this document do not provide any 471 security services beyond those described by EPP [RFC5730] and 472 protocol layers used by EPP. The security considerations described 473 in these other specifications apply to this specification as well. 475 6. IANA Considerations 476 6.1. XML Namespace 478 This document uses URNs to describe XML namespaces and XML schemas 479 conforming to a registry mechanism described in [RFC3688]. The 480 following URI assignment is requested of IANA: 482 URI: ietf:params:xml:ns:validate-1.0 484 Registrant Contact: See the "Author's Address" section of this 485 document. 487 XML: See the "Formal Syntax" section of this document. 489 7. Implemntation Status 491 Note to RFC Editor: Please remove this section and the reference to 492 [RFC6982] before publication. 494 This section records the status of known implementations of the 495 protocol defined by this specification at the time of posting of this 496 Internet-Draft, and is based on a proposal described in [RFC6982]. 497 The description of implementations in this section is intended to 498 assist the IETF in its decision processes in progressing drafts to 499 RFCs. Please note that the listing of any individual implementation 500 here does not imply endorsement by the IETF. Furthermore, no effort 501 has been spent to verify the information presented here that was 502 supplied by IETF contributors. This is not intended as, and must not 503 be construed to be, a catalog of available implementations or their 504 features. Readers are advised to note that other implementations may 505 exist. 507 According to [RFC6982], "this will allow reviewers and working groups 508 to assign due consideration to documents that have the benefit of 509 running code, which may serve as evidence of valuable experimentation 510 and feedback that have made the implemented protocols more mature. 511 It is up to the individual working groups to use this information as 512 they see fit". 514 7.1. To Be Filled In 516 Add implementation details once available. 518 8. Acknowledgements 520 The authors wish to thank the following persons for their feedback 521 and suggestions: 523 o Kevin Allendorf of GoDaddy Inc. 525 o Jody Kolker of GoDaddy Inc. 526 o James Gould of Verisign Inc 528 9. Change History 530 9.1. Change from 00 to 01 532 After review and broad feedback, extensive changes have been made 533 transforming the original document from a standalone extension 534 command to using the command and response framework. Stubbed 535 in an Implementation section for later documentation 537 9.2. Change from carney-regext 01 to ietf-regext 00 539 Updated miscellaneous verbiage to reflect the change from an 540 extension and changed to ietf naming as REGEXT WG will assume this 541 work. 543 10. Normative References 545 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 546 Requirement Levels", BCP 14, RFC 2119, 547 DOI 10.17487/RFC2119, March 1997, 548 . 550 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 551 DOI 10.17487/RFC3688, January 2004, 552 . 554 [RFC5730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", 555 STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009, 556 . 558 Authors' Addresses 560 Roger Carney 561 GoDaddy Inc. 562 14455 N. Hayden Rd. #219 563 Scottsdale, AZ 85260 564 US 566 Email: rcarney@godaddy.com 567 URI: http://www.godaddy.com 568 Joseph Snitker 569 GoDaddy Inc. 570 14455 N. Hayden Rd. #219 571 Scottsdale, AZ 85260 572 US 574 Email: jsnitker@godaddy.com 575 URI: http://www.godaddy.com