idnits 2.17.1 draft-gould-epp-rdap-status-mapping-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 (November 23, 2015) is 3067 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 November 23, 2015 5 Expires: May 26, 2016 7 Extensible Provisioning Protocol (EPP) and Registration Data Access 8 Protocol (RDAP) Status Mapping 9 draft-gould-epp-rdap-status-mapping-02 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 May 26, 2016. 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 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 10 62 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 10 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 65 1. Introduction 67 This document maps the statuses defined in the Extensible 68 Provisioning Protocol (EPP) RFCs to the list of statuses registered 69 for use in the Registration Data Access Protocol (RDAP), in the RDAP 70 JSON Values Registry [rdap-json-values]. 72 The RDAP JSON Values Registry is described in section 10.2 of 73 [RFC7483] and is available in the RDAP JSON Values Registry 74 [rdap-json-values]. 76 The EPP statuses used as the source of the mapping include section 77 2.3 of the EPP Domain Name Mapping [RFC5731], section 2.3 of the EPP 78 Host Mapping [RFC5732], section 2.2 of the EPP Contact Mapping 79 [RFC5733], and section 3.1 of EPP Grace Period Mapping [RFC3915]. 81 Each EPP status MUST map to a single RDAP status to ensure that data 82 in the Domain Name Registries (DNRs) that use EPP can be accurately 83 presented in RDAP. 85 1.1. Conventions Used in This Document 87 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 88 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 89 document are to be interpreted as described in RFC 2119 [RFC2119]. 91 2. EPP to RDAP Status Mapping 93 Below is an alphabetically sorted list of EPP statuses from the EPP 94 RFCs ([RFC5731], [RFC5732], [RFC5733], and [RFC3915]) mapped to the 95 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. 187 serverHold = server hold; For DNR that indicates the server set the 188 status so that DNS delegation information MUST NOT be published 189 for the object. 190 transferPeriod = transfer period; For DNR that indicates if the 191 domain name is deleted by the registrar during this period, the 192 registry provides a credit to the registrar for the cost of the 193 transfer. 195 The resulting mapping after registering the new RDAP statuses is: 197 addPeriod = add period 198 autoRenewPeriod = auto renew period 199 clientDeleteProhibited = client delete prohibited 200 clientHold = client hold 201 clientRenewProhibited = client renew prohibited 202 clientTransferProhibited = client transfer prohibited 203 clientUpdateProhibited = client update prohibited 204 inactive = inactive 205 linked = associated 206 ok = active 207 pendingCreate = pending create 208 pendingDelete = pending delete 209 pendingRenew = pending renew 210 pendingRestore = pending restore 211 pendingTransfer = pending transfer 212 pendingUpdate = pending update 213 redemptionPeriod = redemption period 214 renewPeriod = renew period 215 serverDeleteProhibited = server delete prohibited 216 serverRenewProhibited = server renew prohibited 217 serverTransferProhibited = server transfer prohibited 218 serverUpdateProhibited = server update prohibited 219 serverHold = server hold 220 transferPeriod = transfer period 222 3. IANA Considerations 224 3.1. JSON Values Registry 226 The following values should be registered by the IANA in the RDAP 227 JSON Values Registry described in [RFC7483]: 229 Value: add period 231 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 240 Value: auto renew period 242 Type: status 244 Description: For DNR that indicates if the object is deleted by the 245 registrar during this period, the registry provides a credit to the 246 registrar for the cost of the auto renewal. 248 Registrant Name: VeriSign Inc. 250 Registrant Contact Information: epp-registry@verisign.com 252 Value: client delete prohibited 254 Type: status 256 Description: For DNR that indicates the client requested that 257 requests to delete the object MUST be rejected. 259 Registrant Name: VeriSign Inc. 261 Registrant Contact Information: epp-registry@verisign.com 263 Value: client hold 265 Type: status 267 Description: For DNR that indicates the client requested that the DNS 268 delegation information MUST NOT be published for the object. 270 Registrant Name: VeriSign Inc. 272 Registrant Contact Information: epp-registry@verisign.com 274 Value: client renew prohibited 276 Type: status 278 Description: For DNR that indicates the client requested that 279 requests to renew the object MUST be rejected. 281 Registrant Name: VeriSign Inc. 283 Registrant Contact Information: epp-registry@verisign.com 285 Value: client transfer prohibited 287 Type: status 288 Description: For DNR that indicates the client requested that 289 requests to transfer the object MUST be rejected. 291 Registrant Name: VeriSign Inc. 293 Registrant Contact Information: epp-registry@verisign.com 295 Value: client update prohibited 297 Type: status 299 Description: For DNR that indicates the client requested that 300 requests to update the object (other than to remove this status) MUST 301 be rejected. 303 Registrant Name: VeriSign Inc. 305 Registrant Contact Information: epp-registry@verisign.com 307 Value: pending restore 309 Type: status 311 Description: For DNR that indicates a object is in the process of 312 being restored after being in the redemptionPeriod state. 314 Registrant Name: VeriSign Inc. 316 Registrant Contact Information: epp-registry@verisign.com 318 Value: redemption period 320 Type: status 322 Description: For DNR that indicates a delete has been received, but 323 the object has not yet been purged because an opportunity exists to 324 restore the object and abort the deletion process. 326 Registrant Name: VeriSign Inc. 328 Registrant Contact Information: epp-registry@verisign.com 330 Value: renew period 332 Type: status 333 Description: For DNR that indicates if the object is deleted by the 334 registrar during this period, the registry provides a credit to the 335 registrar for the cost of the renewal. 337 Registrant Name: VeriSign Inc. 339 Registrant Contact Information: epp-registry@verisign.com 341 Value: server delete prohibited 343 Type: status 345 Description: For DNR that indicates the server set the status so that 346 requests to delete the object MUST be rejected. 348 Registrant Name: VeriSign Inc. 350 Registrant Contact Information: epp-registry@verisign.com 352 Value: server renew prohibited 354 Type: status 356 Description: For DNR that indicates the server set the status so that 357 requests to renew the object MUST be rejected. 359 Registrant Name: VeriSign Inc. 361 Registrant Contact Information: epp-registry@verisign.com 363 Value: server transfer prohibited 365 Type: status 367 Description: For DNR that indicates the server set the status so that 368 requests to transfer the object MUST be rejected. 370 Registrant Name: VeriSign Inc. 372 Registrant Contact Information: epp-registry@verisign.com 374 Value: server update prohibited 376 Type: status 378 Description: For DNR that indicates the server set the status so that 379 requests to update the object (other than to remove this status) MUST 380 be rejected. 382 Registrant Name: VeriSign Inc. 384 Registrant Contact Information: epp-registry@verisign.com 386 Value: server hold 388 Type: status 390 Description: For DNR that indicates the server set the status so that 391 DNS delegation information MUST NOT be published for the object. 393 Registrant Name: VeriSign Inc. 395 Registrant Contact Information: epp-registry@verisign.com 397 Value: transfer period 399 Type: status 401 Description: For DNR that indicates if the domain name is deleted by 402 the registrar during this period, the registry provides a credit to 403 the registrar for the cost of the transfer. 405 Registrant Name: VeriSign Inc. 407 Registrant Contact Information: epp-registry@verisign.com 409 4. Security Considerations 411 The mapping described in this document do not provide any security 412 services beyond those described by RDAP [RFC7483]. 414 5. Normative References 416 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 417 Requirement Levels", BCP 14, RFC 2119, March 1997. 419 [RFC3915] Hollenbeck, S., "Domain Registry Grace Period Mapping for 420 the Extensible Provisioning Protocol (EPP)", RFC 3915, 421 September 2004. 423 [RFC5731] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 424 Domain Name Mapping", STD 69, RFC 5731, August 2009. 426 [RFC5732] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 427 Host Mapping", STD 69, RFC 5732, August 2009. 429 [RFC5733] Hollenbeck, S., "Extensible Provisioning Protocol (EPP) 430 Contact Mapping", STD 69, RFC 5733, August 2009. 432 [RFC7483] Newton, A. and S. Hollenbeck, "JSON Responses for the 433 Registration Data Access Protocol (RDAP)", RFC 7483, March 434 2015. 436 [rdap-json-values] 437 "RDAP JSON Values Registry", 438 . 441 Appendix A. Change History 443 A.1. Change from 00 to 01 445 1. Changed the mapping of "linked" to "associated" and removed the 446 registration of "linked", based on feedback from Andrew Newton on 447 the weirds mailing list. 449 A.2. Change from 01 to 02 451 1. Ping update. 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