Extensible Provisioning Protocol (EPP) Contact Mapping for Registration Data Access Protocol (RDAP) JSON Responses
draft-brown-epp-contacts-in-rdap-00

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00

Internet Engineering Task Force                                 G. Brown
Internet-Draft                                      CentralNic Group plc
Intended status: Experimental                          February 18, 2019
Expires: August 22, 2019

Extensible Provisioning Protocol (EPP) Contact Mapping for Registration
               Data Access Protocol (RDAP) JSON Responses
                  draft-brown-epp-contacts-in-rdap-00

Abstract

   This document describes how EPP contact objects can be represented in
   RDAP entities.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 https://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 August 22, 2019.

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

Brown                    Expires August 22, 2019                [Page 1]
Internet-Draft        EPP Contact Mapping for RDAP         February 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions Used in This Document . . . . . . . . . . . .   2
   2.  JSON Mapping of EPP Contact Objects . . . . . . . . . . . . .   3
     2.1.  Postal Address Information  . . . . . . . . . . . . . . .   3
     2.2.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Usage in RDAP . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   5
   4.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The Registration Data Access Protocol (RDAP, [RFC7483]) represents
   contact information pertaining to the entities associated with
   internet identifiers (such as domain names, IP address blocks, and
   autonmymous system numbers) using jCard ([RFC7095]). jCard is a JSON
   mapping of vCard ([RFC6350]) into JSON ([RFC4627]).

   vCard is a generalised specification for entries in an "address
   book", and provides a broad and extensible framework for storing
   attributes associated with an individual, group or organisation.
   However, as RDAP has been deployed by Regional Internet Registries
   (RIRs) and domain name registries (DNRs), the complexity of the jCard
   has been identified as having a negative effect on the ease of
   implementing the RDAP specifications.

   The Extensible Provisioning Protocol (EPP) is widely deployed by
   domain name registries to facilitate provisioning of domain names and
   other objects by registrars.  The EPP Contact Mapping, defined in
   [RFC5733], provides a lightweight structure to describe contact
   information such as name, organization, postal and addresses, and
   voice and fax numbers.

   This document describes a way to map the structure of contact
   information described in RFC5733 into JSON, and also how this
   representation can be used in RDAP entity objects instead of jCard.

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 [RFC2119].

Brown                    Expires August 22, 2019                [Page 2]
Internet-Draft        EPP Contact Mapping for RDAP         February 2019

2.  JSON Mapping of EPP Contact Objects

   This mapping is limited to the attributes of contact objects
   described in sections 2.3 - 2.6 of RFC 5733.  Other attributes, such
   as unique IDs, status codes, and event actions, are already
   adequately mapped to generic RDAP object attributes.

   An EPP contact object may be represented in JSON by constructing a
   JSON object with the following properties: