idnits 2.17.1 draft-gould-epp-rdap-status-mapping-00.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 (May 26, 2015) is 3251 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 7483 (Obsoleted by RFC 9083) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J. Gould 3 Internet-Draft VeriSign, Inc. 4 Intended status: Informational May 26, 2015 5 Expires: November 27, 2015 7 Extensible Provisioning Protocol (EPP) and Registration Data Access 8 Protocol (RDAP) Status Mapping 9 draft-gould-epp-rdap-status-mapping-00 11 Abstract 13 This document describes the mapping of the Extensible Provisioning 14 Protocol (EPP) statuses with the statuses registered for use in the 15 Registration Data Access Protocol (RDAP). This document identifies 16 gaps in the mapping, and registers RDAP statuses to fill the gaps to 17 ensure that all of the EPP RFC statuses are supported in RDAP. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on November 27, 2015. 36 Copyright Notice 38 Copyright (c) 2015 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Conventions Used in This Document . . . . . . . . . . . . 2 55 2. EPP to RDAP Status Mapping . . . . . . . . . . . . . . . . . 2 56 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 57 3.1. JSON Values Registry . . . . . . . . . . . . . . . . . . 5 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 59 5. Normative References . . . . . . . . . . . . . . . . . . . . 9 60 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 10 61 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 63 1. Introduction 65 This document maps the statuses defined in the Extensible 66 Provisioning Protocol (EPP) RFCs to the list of statuses registered 67 for use in the Registration Data Access Protocol (RDAP), in the RDAP 68 JSON Values Registry [rdap-json-values]. 70 The RDAP JSON Values Registry is described in section 10.2 of 71 [RFC7483] and is available in the RDAP JSON Values Registry 72 [rdap-json-values]. 74 The EPP statuses used as the source of the mapping include section 75 2.3 of the EPP Domain Name Mapping [RFC5731], section 2.3 of the EPP 76 Host Mapping [RFC5732], section 2.2 of the EPP Contact Mapping 77 [RFC5733], and section 3.1 of EPP Grace Period Mapping [RFC3915]. 79 Each EPP status MUST map to a single RDAP status to ensure that data 80 in the Domain Name Registries (DNRs) that use EPP can be accurately 81 presented in RDAP. 83 1.1. Conventions Used in This Document 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 87 document are to be interpreted as described in RFC 2119 [RFC2119]. 89 2. EPP to RDAP Status Mapping 91 Below is an alphabetically sorted list of EPP statuses from the EPP 92 RFCs ([RFC5731], [RFC5732], [RFC5733], and [RFC3915]) mapped to the 93 RDAP statuses registered in the RDAP JSON Values Registry 94 [rdap-json-values], with the format '=' , 95 where a blank indicates a gap in the mapping. 97 addPeriod = 98 autoRenewPeriod = 99 clientDeleteProhibited = 100 clientHold = 101 clientRenewProhibited = 102 clientTransferProhibited = 103 clientUpdateProhibited = 104 inactive = inactive 105 linked = 106 ok = active 107 pendingCreate = pending create 108 pendingDelete = pending delete 109 pendingRenew = pending renew 110 pendingRestore = 111 pendingTransfer = pending transfer 112 pendingUpdate = pending update 113 redemptionPeriod = 114 renewPeriod = 115 serverDeleteProhibited = 116 serverRenewProhibited = 117 serverTransferProhibited = 118 serverUpdateProhibited = 119 serverHold = 120 transferPeriod = 122 The RDAP JSON Values Registry [rdap-json-values] does have a set of 123 prohibited statuses including "renew prohibited", "update 124 prohibited", "transfer prohibited", and "delete prohibited", but 125 these statuses do not directly map to the EPP prohibited statuses. 126 The EPP prohibited statuses reflect both what is prohibited ("renew", 127 "update", "transfer", "delete") and who set ("client" or "server") 128 and can clear the status. In the DNR, the client and server 129 prohibited statuses are separate and RDAP MUST support the same 130 separation. 132 Each of the EPP status values that don't map directly to an RDAP 133 status value is described below. Each EPP status value includes a 134 proposed new RDAP status value and a description of the value. The 135 RDAP status value is derived from the EPP status value by converting 136 the EPP camel case representation to lower case with a space 137 character inserted between word boundaries. 139 addPeriod = add period; For DNR that indicates if the object is 140 deleted by the registrar during this period, the registry 141 provides a credit to the registrar for the cost of the 142 registration. 143 autoRenewPeriod = auto renew period; For DNR that indicates if the 144 object is deleted by the registrar during this period, the 145 registry provides a credit to the registrar for the cost of the 146 auto renewal. 147 clientDeleteProhibited = client delete prohibited; For DNR that 148 indicates the client requested that requests to delete the object 149 MUST be rejected. 150 clientHold = client hold; For DNR that indicates the client 151 requested that the DNS delegation information MUST NOT be 152 published for the object. 153 clientRenewProhibited = client renew prohibited; For DNR that 154 indicates the client requested that requests to renew the object 155 MUST be rejected. 156 clientTransferProhibited = client transfer prohibited; For DNR that 157 indicates the client requested that requests to transfer the 158 object MUST be rejected. 159 clientUpdateProhibited = client update prohibited; For DNR that 160 indicates the client requested that requests to update the object 161 (other than to remove this status) MUST be rejected. 162 linked = linked; For DNR that indicates the object has at least one 163 active association with another object, such as a domain object. 164 pendingRestore = pending restore; For DNR that indicates a object is 165 in the process of being restored after being in the 166 redemptionPeriod state. 167 redemptionPeriod = redemption period; For DNR that indicates a 168 delete has been received, but the object has not yet been purged 169 because an opportunity exists to restore the object and abort the 170 deletion process. 171 renewPeriod = renew period; For DNR that indicates if the object is 172 deleted by the registrar during this period, the registry 173 provides a credit to the registrar for the cost of the renewal. 174 serverDeleteProhibited = server delete prohibited; For DNR that 175 indicates the server set the status so that requests to delete 176 the object MUST be rejected. 177 serverRenewProhibited = server renew prohibited; For DNR that 178 indicates the server set the status so that requests to renew the 179 object MUST be rejected. 180 serverTransferProhibited = server transfer prohibited; For DNR that 181 indicates the server set the status so that requests to transfer 182 the object MUST be rejected. 183 serverUpdateProhibited = server update prohibited; For DNR that 184 indicates the server set the status so that requests to update 185 the object (other than to remove this status) MUST be rejected. 186 serverHold = server hold; For DNR that indicates the server set the 187 status so that DNS delegation information MUST NOT be published 188 for the object. 189 transferPeriod = transfer period; For DNR that indicates if the 190 domain name is deleted by the registrar during this period, the 191 registry provides a credit to the registrar for the cost of the 192 transfer. 194 The resulting mapping after registering the new RDAP statuses is: 196 addPeriod = add period 197 autoRenewPeriod = auto renew period 198 clientDeleteProhibited = client delete prohibited 199 clientHold = client hold 200 clientRenewProhibited = client renew prohibited 201 clientTransferProhibited = client transfer prohibited 202 clientUpdateProhibited = client update prohibited 203 inactive = inactive 204 linked = linked 205 ok = active 206 pendingCreate = pending create 207 pendingDelete = pending delete 208 pendingRenew = pending renew 209 pendingRestore = pending restore 210 pendingTransfer = pending transfer 211 pendingUpdate = pending update 212 redemptionPeriod = redemption period 213 renewPeriod = renew period 214 serverDeleteProhibited = server delete prohibited 215 serverRenewProhibited = server renew prohibited 216 serverTransferProhibited = server transfer prohibited 217 serverUpdateProhibited = server update prohibited 218 serverHold = server hold 219 transferPeriod = transfer period 221 3. IANA Considerations 223 3.1. JSON Values Registry 225 The following values should be registered by the IANA in the RDAP 226 JSON Values Registry described in [RFC7483]: 228 Value: add period 230 Type: status 232 Description: For DNR that indicates if the object is deleted by the 233 registrar during this period, the registry provides a credit to the 234 registrar for the cost of the registration. 236 Registrant Name: VeriSign Inc. 238 Registrant Contact Information: epp-registry@verisign.com 240 Value: auto renew period 241 Type: status 243 Description: For DNR that indicates if the object is deleted by the 244 registrar during this period, the registry provides a credit to the 245 registrar for the cost of the auto renewal. 247 Registrant Name: VeriSign Inc. 249 Registrant Contact Information: epp-registry@verisign.com 251 Value: client delete prohibited 253 Type: status 255 Description: For DNR that indicates the client requested that 256 requests to delete the object MUST be rejected. 258 Registrant Name: VeriSign Inc. 260 Registrant Contact Information: epp-registry@verisign.com 262 Value: client hold 264 Type: status 266 Description: For DNR that indicates the client requested that the DNS 267 delegation information MUST NOT be published for the object. 269 Registrant Name: VeriSign Inc. 271 Registrant Contact Information: epp-registry@verisign.com 273 Value: client renew prohibited 275 Type: status 277 Description: For DNR that indicates the client requested that 278 requests to renew the object MUST be rejected. 280 Registrant Name: VeriSign Inc. 282 Registrant Contact Information: epp-registry@verisign.com 284 Value: client transfer prohibited 286 Type: status 287 Description: For DNR that indicates the client requested that 288 requests to transfer the object MUST be rejected. 290 Registrant Name: VeriSign Inc. 292 Registrant Contact Information: epp-registry@verisign.com 294 Value: client update prohibited 296 Type: status 298 Description: For DNR that indicates the client requested that 299 requests to update the object (other than to remove this status) MUST 300 be rejected. 302 Registrant Name: VeriSign Inc. 304 Registrant Contact Information: epp-registry@verisign.com 306 Value: linked 308 Type: status 310 Description: For DNR that indicates the object has at least one 311 active association with another object, such as a domain object. 313 Registrant Name: VeriSign Inc. 315 Registrant Contact Information: epp-registry@verisign.com 317 Value: pending restore 319 Type: status 321 Description: For DNR that indicates a object is in the process of 322 being restored after being in the redemptionPeriod state. 324 Registrant Name: VeriSign Inc. 326 Registrant Contact Information: epp-registry@verisign.com 328 Value: redemption period 330 Type: status 332 Description: For DNR that indicates a delete has been received, but 333 the object has not yet been purged because an opportunity exists to 334 restore the object and abort the deletion process. 336 Registrant Name: VeriSign Inc. 338 Registrant Contact Information: epp-registry@verisign.com 340 Value: renew period 342 Type: status 344 Description: For DNR that indicates if the object is deleted by the 345 registrar during this period, the registry provides a credit to the 346 registrar for the cost of the renewal. 348 Registrant Name: VeriSign Inc. 350 Registrant Contact Information: epp-registry@verisign.com 352 Value: server delete prohibited 354 Type: status 356 Description: For DNR that indicates the server set the status so that 357 requests to delete the object MUST be rejected. 359 Registrant Name: VeriSign Inc. 361 Registrant Contact Information: epp-registry@verisign.com 363 Value: server renew prohibited 365 Type: status 367 Description: For DNR that indicates the server set the status so that 368 requests to renew the object MUST be rejected. 370 Registrant Name: VeriSign Inc. 372 Registrant Contact Information: epp-registry@verisign.com 374 Value: server transfer prohibited 376 Type: status 378 Description: For DNR that indicates the server set the status so that 379 requests to transfer the object MUST be rejected. 381 Registrant Name: VeriSign Inc. 383 Registrant Contact Information: epp-registry@verisign.com 384 Value: server update prohibited 386 Type: status 388 Description: For DNR that indicates the server set the status so that 389 requests to update the object (other than to remove this status) MUST 390 be rejected. 392 Registrant Name: VeriSign Inc. 394 Registrant Contact Information: epp-registry@verisign.com 396 Value: server hold 398 Type: status 400 Description: For DNR that indicates the server set the status so that 401 DNS delegation information MUST NOT be published for the object. 403 Registrant Name: VeriSign Inc. 405 Registrant Contact Information: epp-registry@verisign.com 407 Value: transfer period 409 Type: status 411 Description: For DNR that indicates if the domain name is deleted by 412 the registrar during this period, the registry provides a credit to 413 the registrar for the cost of the transfer. 415 Registrant Name: VeriSign Inc. 417 Registrant Contact Information: epp-registry@verisign.com 419 4. Security Considerations 421 The mapping described in this document do not provide any security 422 services beyond those described by RDAP [RFC7483]. 424 5. Normative References 426 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 427 Requirement Levels", BCP 14, RFC 2119, March 1997. 429 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 430 the Extensible Provisioning Protocol (EPP)", RFC 3915, 431 September 2004. 433 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 434 Domain Name Mapping", STD 69, RFC 5731, August 2009. 436 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 437 Host Mapping", STD 69, RFC 5732, August 2009. 439 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 440 Contact Mapping", STD 69, RFC 5733, August 2009. 442 [RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the 443 Registration Data Access Protocol (RDAP)", RFC 7483, March 444 2015. 446 [rdap-json-values] 447 "RDAP JSON Values Registry", 448 . 451 Appendix A. Change History 453 Author's Address 455 James Gould 456 VeriSign, Inc. 457 12061 Bluemont Way 458 Reston, VA 20190 459 US 461 Email: jgould@verisign.com 462 URI: http://www.verisigninc.com