RDAP jCard Profile
draft-harrison-regext-rdap-jcard-profile-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-07
Replaces draft-rdap-jcard-profile
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                              T. Harrison
Internet-Draft                                             G. Michaelson
Updates: 7483 (if approved)                                        APNIC
Intended status: Standards Track                            July 7, 2019
Expires: January 8, 2020

                           RDAP jCard Profile
              draft-harrison-regext-rdap-jcard-profile-00

Abstract

   The Registration Data Access Protocol (RDAP) is used by Regional
   Internet Registries (RIRs) and Domain Name Registries (DNRs) to
   provide access to their resource registration information.  RDAP uses
   jCard to convey information about individuals and other entities: for
   example, for the technical contact for a domain name.  In practice,
   server operators are only using a small subset of jCard's
   functionality, so in an effort to simplify the requirements on the
   client side, this document defines a jCard profile for use with RDAP.

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 January 8, 2020.

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

Harrison & Michaelson    Expires January 8, 2020                [Page 1]
Internet-Draft             RDAP jCard Profile                  July 2019

   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.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Profile Definition  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Operational Considerations  . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The Registration Data Access Protocol (RDAP) [RFC7480] is used by
   Regional Internet Registries (RIRs) and Domain Name Registries (DNRs)
   to provide access to their resource registration information.  RDAP
   uses jCard ([RFC7095]) to convey information about individuals and
   other entities (e.g.  organisations and groups).  jCard is in turn a
   way of representing vCard ([RFC6350]) information in JSON.

   The core vCard specification defines 36 properties, 11 parameters, 12
   data types, and 31 parameter values.  More of each are defined in
   subsequent specifications (see the IANA vCard Elements registry).
   Due to the lack of supporting libraries for jCard, RDAP client
   developers often have to implement jCard support themselves, and
   handling the entire specification is a substantial burden.

   This document defines a jCard profile for use with RDAP that will
   reduce the implementation complexity for client developers.  The
   profile is primarily based on response data from the implementations
   that are currently included in the IANA RDAP bootstrap files.

1.1.  Requirements Language

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

Harrison & Michaelson    Expires January 8, 2020                [Page 2]
Internet-Draft             RDAP jCard Profile                  July 2019

2.  Profile Definition

   The following properties may be used in jCards included in RDAP
   responses:

      kind;

      fn;

      n;

      adr;

      tel;

      email;
Show full document text