--- 1/draft-ietf-regext-epp-rdap-status-mapping-03.txt 2016-10-28 12:16:26.850130523 -0700 +++ 2/draft-ietf-regext-epp-rdap-status-mapping-04.txt 2016-10-28 12:16:26.874131114 -0700 @@ -1,19 +1,19 @@ Network Working Group J. Gould Internet-Draft VeriSign, Inc. -Intended status: Standards Track October 12, 2016 -Expires: April 15, 2017 +Intended status: Standards Track October 28, 2016 +Expires: May 1, 2017 Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping - draft-ietf-regext-epp-rdap-status-mapping-03 + draft-ietf-regext-epp-rdap-status-mapping-04 Abstract This document describes the mapping of the Extensible Provisioning Protocol (EPP) statuses with the statuses registered for use in the Registration Data Access Protocol (RDAP). This document identifies gaps in the mapping, and registers RDAP statuses to fill the gaps to ensure that all of the EPP RFC statuses are supported in RDAP. Status of This Memo @@ -24,72 +24,76 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on April 15, 2017. + This Internet-Draft will expire on May 1, 2017. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 - 1.1. Conventions Used in This Document . . . . . . . . . . . . 2 + 1.1. Conventions Used in This Document . . . . . . . . . . . . 3 2. EPP to RDAP Status Mapping . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 3.1. JSON Values Registry . . . . . . . . . . . . . . . . . . 5 - 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 - 5. Normative References . . . . . . . . . . . . . . . . . . . . 9 - Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 10 - Appendix B. Change History . . . . . . . . . . . . . . . . . . . 10 - B.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 10 - B.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 10 - B.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 10 - B.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 10 - B.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 11 - B.6. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 11 - B.7. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 11 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 11 + 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 + 5. Normative References . . . . . . . . . . . . . . . . . . . . 10 + Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 11 + Appendix B. Change History . . . . . . . . . . . . . . . . . . . 11 + B.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 11 + B.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 11 + B.3. Change from 02 to 03 . . . . . . . . . . . . . . . . . . 11 + B.4. Change from 03 to REGEXT 00 . . . . . . . . . . . . . . . 11 + B.5. Change from REGEXT 00 to REGEXT 01 . . . . . . . . . . . 12 + B.6. Change from REGEXT 01 to REGEXT 02 . . . . . . . . . . . 12 + B.7. Change from REGEXT 02 to REGEXT 03 . . . . . . . . . . . 12 + B.8. Change from REGEXT 03 to REGEXT 04 . . . . . . . . . . . 12 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 12 1. Introduction This document maps the statuses defined in the Extensible Provisioning Protocol (EPP) RFCs to the list of statuses registered for use in the Registration Data Access Protocol (RDAP), in the RDAP JSON Values Registry [rdap-json-values]. The RDAP JSON Values Registry is described in section 10.2 of [RFC7483] and is available in the RDAP JSON Values Registry [rdap-json-values]. The EPP statuses used as the source of the mapping include section - 2.3 of the EPP Domain Name Mapping [RFC5731], section 2.3 of the EPP - Host Mapping [RFC5732], section 2.2 of the EPP Contact Mapping - [RFC5733], and section 3.1 of EPP Grace Period Mapping [RFC3915]. + 2.3 of the Extensible Provisioning Protocol (EPP) Domain Name Mapping + [RFC5731], section 2.3 of the Extensible Provisioning Protocol (EPP) + Host Mapping [RFC5732], section 2.2 of the Extensible Provisioning + Protocol (EPP) Contact Mapping [RFC5733], and section 3.1 of Domain + Registry Grace Period Mapping for the Extensible Provisioning + Protocol (EPP) [RFC3915]. Each EPP status MUST map to a single RDAP status to ensure that data in the Domain Name Registries (DNRs) that use EPP can be accurately presented in RDAP. 1.1. Conventions Used in This Document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. @@ -226,111 +231,133 @@ The following values should be registered by the IANA in the RDAP JSON Values Registry described in [RFC7483]: Value: add period Type: status Description: This grace period is provided after the initial registration of the object. If the object is deleted by the client during this period, the server provides a credit to the client for - the cost of the registration. + the cost of the registration. This maps to the Domain Registry Grace + Period Mapping for the Extensible Provisioning Protocol (EPP) + [RFC3915] 'addPeriod' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: auto renew period + Type: status Description: This grace period is provided after an object registration period expires and is extended (renewed) automatically by the server. If the object is deleted by the client during this period, the server provides a credit to the client for the cost of - the auto renewal. + the auto renewal. This maps to the Domain Registry Grace Period + Mapping for the Extensible Provisioning Protocol (EPP) [RFC3915] + 'autoRenewPeriod' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: client delete prohibited Type: status Description: The client requested that requests to delete the object - MUST be rejected. + MUST be rejected. This maps to the Extensible Provisioning Protocol + (EPP) Domain Name Mapping [RFC5731], Extensible Provisioning Protocol + (EPP) Host Mapping [RFC5732], and Extensible Provisioning Protocol + (EPP) Contact Mapping [RFC5733] 'clientDeleteProhibited' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: client hold Type: status Description: The client requested that the DNS delegation information - MUST NOT be published for the object. + MUST NOT be published for the object. This maps to the Extensible + Provisioning Protocol (EPP) Domain Name Mapping [RFC5731] + 'clientHold' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: client renew prohibited Type: status Description: The client requested that requests to renew the object - MUST be rejected. + MUST be rejected. This maps to the Extensible Provisioning Protocol + (EPP) Domain Name Mapping [RFC5731] 'clientRenewProhibited' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: client transfer prohibited Type: status + Description: The client requested that requests to transfer the - object MUST be rejected. + object MUST be rejected. This maps to the Extensible Provisioning + Protocol (EPP) Domain Name Mapping [RFC5731] and Extensible + Provisioning Protocol (EPP) Contact Mapping [RFC5733] + 'clientTransferProhibited' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: client update prohibited Type: status Description: The client requested that requests to update the object - (other than to remove this status) MUST be rejected. + (other than to remove this status) MUST be rejected. This maps to + the Extensible Provisioning Protocol (EPP) Domain Name Mapping + [RFC5731], Extensible Provisioning Protocol (EPP) Host Mapping + [RFC5732], and Extensible Provisioning Protocol (EPP) Contact Mapping + [RFC5733] 'clientUpdateProhibited' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: pending restore Type: status - Description: An object is in the process of being restored after - being in the redemption period state. + being in the redemption period state. This maps to the Domain + Registry Grace Period Mapping for the Extensible Provisioning + Protocol (EPP) [RFC3915] 'pendingRestore' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: redemption period Type: status Description: A delete has been received, but the object has not yet been purged because an opportunity exists to restore the object and - abort the deletion process. + abort the deletion process. This maps to the Domain Registry Grace + Period Mapping for the Extensible Provisioning Protocol (EPP) + [RFC3915] 'redemptionPeriod' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: renew period Type: status Description: This grace period is provided after an object @@ -328,91 +355,109 @@ Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: renew period Type: status Description: This grace period is provided after an object registration period is explicitly extended (renewed) by the client. - If the object is deleted by the client during this period, the server - provides a credit to the client for the cost of the renewal. + provides a credit to the client for the cost of the renewal. This + maps to the Domain Registry Grace Period Mapping for the Extensible + Provisioning Protocol (EPP) [RFC3915] 'renewPeriod' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: server delete prohibited Type: status Description: The server set the status so that requests to delete the - object MUST be rejected. + object MUST be rejected. This maps to the Extensible Provisioning + Protocol (EPP) Domain Name Mapping [RFC5731], Extensible Provisioning + Protocol (EPP) Host Mapping [RFC5732], and Extensible Provisioning + Protocol (EPP) Contact Mapping [RFC5733] 'serverDeleteProhibited' + status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: server renew prohibited Type: status Description: The server set the status so that requests to renew the - object MUST be rejected. + object MUST be rejected. This maps to the Extensible Provisioning + Protocol (EPP) Domain Name Mapping [RFC5731] 'serverRenewProhibited' + status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: server transfer prohibited Type: status Description: The server set the status so that requests to transfer - the object MUST be rejected. + the object MUST be rejected. This maps to the Extensible + Provisioning Protocol (EPP) Domain Name Mapping [RFC5731] and + Extensible Provisioning Protocol (EPP) Contact Mapping [RFC5733] + 'serverTransferProhibited' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: server update prohibited Type: status Description: The server set the status so that requests to update the - object (other than to remove this status) MUST be rejected. + object (other than to remove this status) MUST be rejected. This + maps to the Extensible Provisioning Protocol (EPP) Domain Name + Mapping [RFC5731], Extensible Provisioning Protocol (EPP) Host + Mapping [RFC5732], and Extensible Provisioning Protocol (EPP) Contact + Mapping [RFC5733] 'serverUpdateProhibited' status. Registrant Name: IESG + Registrant Contact Information: iesg@ietf.org Value: server hold - Type: status Description: The server set the status so that DNS delegation - information MUST NOT be published for the object. + information MUST NOT be published for the object. This maps to the + Extensible Provisioning Protocol (EPP) Domain Name Mapping [RFC5731] + 'serverHold' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: transfer period Type: status Description: This grace period is provided after the successful transfer of object registration sponsorship from one client to another client. If the object is deleted by the client during this period, the server provides a credit to the client for the cost of - the transfer. + the transfer. This maps to the Domain Registry Grace Period Mapping + for the Extensible Provisioning Protocol (EPP) [RFC3915] + 'transferPeriod' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org 4. Security Considerations The status values described in this document can be subject to server-side information disclosure policies that restrict display of the values to authorized clients. Implementers may wish to review @@ -502,20 +547,26 @@ 4. Changed all references of "registrar" to "client" and "registry" to "server" in the status descriptions to be consistent. B.7. Change from REGEXT 02 to REGEXT 03 1. Updated descriptions of the add period, auto renew period, renew period, and transfer period statuses to better reflect what the status is in RFC 3915, based on feedback by Robert Sparks on the regext mailing list. +B.8. Change from REGEXT 03 to REGEXT 04 + + 1. Updated the descriptions of the JSON Values Registry entries to + include a reference back to the appropriate EPP RFC status, based + on feedback by Sabrina Tanamal from IANA. + Author's Address James Gould VeriSign, Inc. 12061 Bluemont Way Reston, VA 20190 US Email: jgould@verisign.com URI: http://www.verisigninc.com