idnits 2.17.1 draft-gould-epp-rdap-status-mapping-03.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 23, 2016) is 2896 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 23, 2016 5 Expires: November 24, 2016 7 Extensible Provisioning Protocol (EPP) and Registration Data Access 8 Protocol (RDAP) Status Mapping 9 draft-gould-epp-rdap-status-mapping-03 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 24, 2016. 36 Copyright Notice 38 Copyright (c) 2016 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 . . . . . . . . . . . . . . . . . 3 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 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 10 62 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 10 63 A.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 66 1. Introduction 68 This document maps the statuses defined in the Extensible 69 Provisioning Protocol (EPP) RFCs to the list of statuses registered 70 for use in the Registration Data Access Protocol (RDAP), in the RDAP 71 JSON Values Registry [rdap-json-values]. 73 The RDAP JSON Values Registry is described in section 10.2 of 74 [RFC7483] and is available in the RDAP JSON Values Registry 75 [rdap-json-values]. 77 The EPP statuses used as the source of the mapping include section 78 2.3 of the EPP Domain Name Mapping [RFC5731], section 2.3 of the EPP 79 Host Mapping [RFC5732], section 2.2 of the EPP Contact Mapping 80 [RFC5733], and section 3.1 of EPP Grace Period Mapping [RFC3915]. 82 Each EPP status MUST map to a single RDAP status to ensure that data 83 in the Domain Name Registries (DNRs) that use EPP can be accurately 84 presented in RDAP. 86 1.1. Conventions Used in This Document 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in RFC 2119 [RFC2119]. 92 2. EPP to RDAP Status Mapping 94 Below is an alphabetically sorted list of EPP statuses from the EPP 95 RFCs ([RFC5731], [RFC5732], [RFC5733], and [RFC3915]) mapped to the 96 RDAP statuses registered in the RDAP JSON Values Registry 97 [rdap-json-values], with the format '=' , 98 where a blank indicates a gap in the mapping. 100 addPeriod = 101 autoRenewPeriod = 102 clientDeleteProhibited = 103 clientHold = 104 clientRenewProhibited = 105 clientTransferProhibited = 106 clientUpdateProhibited = 107 inactive = inactive 108 linked = associated 109 ok = active 110 pendingCreate = pending create 111 pendingDelete = pending delete 112 pendingRenew = pending renew 113 pendingRestore = 114 pendingTransfer = pending transfer 115 pendingUpdate = pending update 116 redemptionPeriod = 117 renewPeriod = 118 serverDeleteProhibited = 119 serverRenewProhibited = 120 serverTransferProhibited = 121 serverUpdateProhibited = 122 serverHold = 123 transferPeriod = 125 The RDAP JSON Values Registry [rdap-json-values] does have a set of 126 prohibited statuses including "renew prohibited", "update 127 prohibited", "transfer prohibited", and "delete prohibited", but 128 these statuses do not directly map to the EPP prohibited statuses. 129 The EPP prohibited statuses reflect both what is prohibited ("renew", 130 "update", "transfer", "delete") and who set ("client" or "server") 131 and can clear the status. In the DNR, the client and server 132 prohibited statuses are separate and RDAP MUST support the same 133 separation. 135 Each of the EPP status values that don't map directly to an RDAP 136 status value is described below. Each EPP status value includes a 137 proposed new RDAP status value and a description of the value. The 138 RDAP status value is derived from the EPP status value by converting 139 the EPP camel case representation to lower case with a space 140 character inserted between word boundaries. 142 addPeriod = add period; For DNR that indicates if the object is 143 deleted by the registrar during this period, the registry 144 provides a credit to the registrar for the cost of the 145 registration. 146 autoRenewPeriod = auto renew period; For DNR that indicates if the 147 object is deleted by the registrar during this period, the 148 registry provides a credit to the registrar for the cost of the 149 auto renewal. 150 clientDeleteProhibited = client delete prohibited; For DNR that 151 indicates the client requested that requests to delete the object 152 MUST be rejected. 153 clientHold = client hold; For DNR that indicates the client 154 requested that the DNS delegation information MUST NOT be 155 published for the object. 156 clientRenewProhibited = client renew prohibited; For DNR that 157 indicates the client requested that requests to renew the object 158 MUST be rejected. 159 clientTransferProhibited = client transfer prohibited; For DNR that 160 indicates the client requested that requests to transfer the 161 object MUST be rejected. 162 clientUpdateProhibited = client update prohibited; For DNR that 163 indicates the client requested that requests to update the object 164 (other than to remove this status) MUST be rejected. 165 pendingRestore = pending restore; For DNR that indicates a object is 166 in the process of being restored after being in the 167 redemptionPeriod state. 168 redemptionPeriod = redemption period; For DNR that indicates a 169 delete has been received, but the object has not yet been purged 170 because an opportunity exists to restore the object and abort the 171 deletion process. 172 renewPeriod = renew period; For DNR that indicates if the object is 173 deleted by the registrar during this period, the registry 174 provides a credit to the registrar for the cost of the renewal. 175 serverDeleteProhibited = server delete prohibited; For DNR that 176 indicates the server set the status so that requests to delete 177 the object MUST be rejected. 178 serverRenewProhibited = server renew prohibited; For DNR that 179 indicates the server set the status so that requests to renew the 180 object MUST be rejected. 181 serverTransferProhibited = server transfer prohibited; For DNR that 182 indicates the server set the status so that requests to transfer 183 the object MUST be rejected. 184 serverUpdateProhibited = server update prohibited; For DNR that 185 indicates the server set the status so that requests to update 186 the object (other than to remove this status) MUST be rejected. 188 serverHold = server hold; For DNR that indicates the server set the 189 status so that DNS delegation information MUST NOT be published 190 for the object. 191 transferPeriod = transfer period; For DNR that indicates if the 192 domain name is deleted by the registrar during this period, the 193 registry provides a credit to the registrar for the cost of the 194 transfer. 196 The resulting mapping after registering the new RDAP statuses is: 198 addPeriod = add period 199 autoRenewPeriod = auto renew period 200 clientDeleteProhibited = client delete prohibited 201 clientHold = client hold 202 clientRenewProhibited = client renew prohibited 203 clientTransferProhibited = client transfer prohibited 204 clientUpdateProhibited = client update prohibited 205 inactive = inactive 206 linked = associated 207 ok = active 208 pendingCreate = pending create 209 pendingDelete = pending delete 210 pendingRenew = pending renew 211 pendingRestore = pending restore 212 pendingTransfer = pending transfer 213 pendingUpdate = pending update 214 redemptionPeriod = redemption period 215 renewPeriod = renew period 216 serverDeleteProhibited = server delete prohibited 217 serverRenewProhibited = server renew prohibited 218 serverTransferProhibited = server transfer prohibited 219 serverUpdateProhibited = server update prohibited 220 serverHold = server hold 221 transferPeriod = transfer period 223 3. IANA Considerations 225 3.1. JSON Values Registry 227 The following values should be registered by the IANA in the RDAP 228 JSON Values Registry described in [RFC7483]: 230 Value: add period 232 Type: status 233 Description: For DNR that indicates if the object is deleted by the 234 registrar during this period, the registry provides a credit to the 235 registrar for the cost of the registration. 237 Registrant Name: VeriSign Inc. 239 Registrant Contact Information: epp-registry@verisign.com 241 Value: auto renew period 243 Type: status 245 Description: For DNR that indicates if the object is deleted by the 246 registrar during this period, the registry provides a credit to the 247 registrar for the cost of the auto renewal. 249 Registrant Name: VeriSign Inc. 251 Registrant Contact Information: epp-registry@verisign.com 253 Value: client delete prohibited 255 Type: status 257 Description: For DNR that indicates the client requested that 258 requests to delete the object MUST be rejected. 260 Registrant Name: VeriSign Inc. 262 Registrant Contact Information: epp-registry@verisign.com 264 Value: client hold 266 Type: status 268 Description: For DNR that indicates the client requested that the DNS 269 delegation information MUST NOT be published for the object. 271 Registrant Name: VeriSign Inc. 273 Registrant Contact Information: epp-registry@verisign.com 275 Value: client renew prohibited 277 Type: status 279 Description: For DNR that indicates the client requested that 280 requests to renew the object MUST be rejected. 282 Registrant Name: VeriSign Inc. 284 Registrant Contact Information: epp-registry@verisign.com 286 Value: client transfer prohibited 288 Type: status 290 Description: For DNR that indicates the client requested that 291 requests to transfer the object MUST be rejected. 293 Registrant Name: VeriSign Inc. 295 Registrant Contact Information: epp-registry@verisign.com 297 Value: client update prohibited 299 Type: status 301 Description: For DNR that indicates the client requested that 302 requests to update the object (other than to remove this status) MUST 303 be rejected. 305 Registrant Name: VeriSign Inc. 307 Registrant Contact Information: epp-registry@verisign.com 309 Value: pending restore 311 Type: status 313 Description: For DNR that indicates a object is in the process of 314 being restored after being in the redemptionPeriod state. 316 Registrant Name: VeriSign Inc. 318 Registrant Contact Information: epp-registry@verisign.com 320 Value: redemption period 322 Type: status 324 Description: For DNR that indicates a delete has been received, but 325 the object has not yet been purged because an opportunity exists to 326 restore the object and abort the deletion process. 328 Registrant Name: VeriSign Inc. 330 Registrant Contact Information: epp-registry@verisign.com 332 Value: renew period 334 Type: status 336 Description: For DNR that indicates if the object is deleted by the 337 registrar during this period, the registry provides a credit to the 338 registrar for the cost of the renewal. 340 Registrant Name: VeriSign Inc. 342 Registrant Contact Information: epp-registry@verisign.com 344 Value: server delete prohibited 346 Type: status 348 Description: For DNR that indicates the server set the status so that 349 requests to delete the object MUST be rejected. 351 Registrant Name: VeriSign Inc. 353 Registrant Contact Information: epp-registry@verisign.com 355 Value: server renew prohibited 357 Type: status 359 Description: For DNR that indicates the server set the status so that 360 requests to renew the object MUST be rejected. 362 Registrant Name: VeriSign Inc. 364 Registrant Contact Information: epp-registry@verisign.com 366 Value: server transfer prohibited 368 Type: status 370 Description: For DNR that indicates the server set the status so that 371 requests to transfer the object MUST be rejected. 373 Registrant Name: VeriSign Inc. 375 Registrant Contact Information: epp-registry@verisign.com 377 Value: server update prohibited 378 Type: status 380 Description: For DNR that indicates the server set the status so that 381 requests to update the object (other than to remove this status) MUST 382 be rejected. 384 Registrant Name: VeriSign Inc. 386 Registrant Contact Information: epp-registry@verisign.com 388 Value: server hold 390 Type: status 392 Description: For DNR that indicates the server set the status so that 393 DNS delegation information MUST NOT be published for the object. 395 Registrant Name: VeriSign Inc. 397 Registrant Contact Information: epp-registry@verisign.com 399 Value: transfer period 401 Type: status 403 Description: For DNR that indicates if the domain name is deleted by 404 the registrar during this period, the registry provides a credit to 405 the registrar for the cost of the transfer. 407 Registrant Name: VeriSign Inc. 409 Registrant Contact Information: epp-registry@verisign.com 411 4. Security Considerations 413 The mapping described in this document do not provide any security 414 services beyond those described by RDAP [RFC7483]. 416 5. Normative References 418 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 419 Requirement Levels", BCP 14, RFC 2119, March 1997. 421 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 422 the Extensible Provisioning Protocol (EPP)", RFC 3915, 423 September 2004. 425 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 426 Domain Name Mapping", STD 69, RFC 5731, August 2009. 428 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 429 Host Mapping", STD 69, RFC 5732, August 2009. 431 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 432 Contact Mapping", STD 69, RFC 5733, August 2009. 434 [RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the 435 Registration Data Access Protocol (RDAP)", RFC 7483, March 436 2015. 438 [rdap-json-values] 439 "RDAP JSON Values Registry", 440 . 443 Appendix A. Change History 445 A.1. Change from 00 to 01 447 1. Changed the mapping of "linked" to "associated" and removed the 448 registration of "linked", based on feedback from Andrew Newton on 449 the weirds mailing list. 451 A.2. Change from 01 to 02 453 1. Ping update. 455 A.3. Change from 02 to 03 457 1. Ping update. 459 Author's Address 461 James Gould 462 VeriSign, Inc. 463 12061 Bluemont Way 464 Reston, VA 20190 465 US 467 Email: jgould@verisign.com 468 URI: http://www.verisigninc.com