Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping
RFC 8056

Document Type RFC - Proposed Standard (January 2017; No errata)
Last updated 2017-01-17
Replaces draft-gould-epp-rdap-status-mapping
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Apr 2016 - Submit for publicati... )
Document shepherd Ulrich Wisser
Shepherd write-up Show (last changed 2016-09-15)
IESG IESG state RFC 8056 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alexey Melnikov
Send notices to "Ulrich Wisser" <ulrich@wisser.se>
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          J. Gould
Request for Comments: 8056                                VeriSign, Inc.
Category: Standards Track                                   January 2017
ISSN: 2070-1721

                 Extensible Provisioning Protocol (EPP)
      and Registration Data Access Protocol (RDAP) Status Mapping

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 those gaps
   to ensure that all of the EPP statuses specified in RFCs are
   supported in RDAP.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8056.

Copyright Notice

   Copyright (c) 2017 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.

Gould                        Standards Track                    [Page 1]
RFC 8056                 EPP RDAP Status Mapping            January 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   2
   2.  EPP-to-RDAP Status Mapping  . . . . . . . . . . . . . . . . .   2
   3.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  JSON Values Registry  . . . . . . . . . . . . . . . . . .   6
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  Normative References  . . . . . . . . . . . . . . . . . . . .  10
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

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 Extensible Provisioning Protocol (EPP) Domain Name
   Mapping [RFC5731], Section 2.3 of "Extensible Provisioning Protocol
   (EPP) Host Mapping" [RFC5732], Section 2.2 of "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].

2.  EPP-to-RDAP Status Mapping

   Below is a list of EPP statuses from the EPP RFCs ([RFC5731],
   [RFC5732], [RFC5733], and [RFC3915]) mapped to the RDAP statuses
   registered in the "RDAP JSON Values" registry [rdap-json-values],
   with the format <EPP Status> '=' <RDAP Status>, where a blank <RDAP
   Status> indicates a gap in the mapping.

Gould                        Standards Track                    [Page 2]
Show full document text