Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses
draft-loffredo-regext-rdap-jcard-deprecation-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-23
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)
Registration Protocols Extensions                            M. Loffredo
Internet-Draft                                       IIT-CNR/Registro.it
Intended status: Best Current Practice                          G. Brown
Expires: September 24, 2020                         CentralNic Group plc
                                                          March 23, 2020

    Using JSContact in Registration Data Access Protocol (RDAP) JSON
                               Responses
            draft-loffredo-regext-rdap-jcard-deprecation-00

Abstract

   This document describes how RDAP servers can represent entity contact
   information in JSON responses using JSContact.

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 September 24, 2020.

Copyright Notice

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

Loffredo & Brown       Expires September 24, 2020               [Page 1]
Internet-Draft           Using JSContact in RDAP              March 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Rationale . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Conventions Used in This Document . . . . . . . . . . . .   3
   2.  JSContact . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Using JSCard objects in RDAP Responses  . . . . . . . . . . .   4
   4.  Migration from JCard to JSCard  . . . . . . . . . . . . . . .   4
     4.1.  Best Practices for deprecating a REST API features  . . .   5
     4.2.  RDAP Features Supporting a Deprecation Process  . . . . .   5
     4.3.  jCard Deprecation Procedure . . . . . . . . . . . . . . .   6
       4.3.1.  Stages  . . . . . . . . . . . . . . . . . . . . . . .   6
       4.3.2.  Length  . . . . . . . . . . . . . . . . . . . . . . .   9
       4.3.3.  Goals . . . . . . . . . . . . . . . . . . . . . . . .   9
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .  10
     5.1.  IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . .  10
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   This document specifies how RDAP servers can use JSContact
   ([draft-ietf-jmap-jscontact]) to represent the contact information
   associated with entities in RDAP responses, instead of jCard
   ([RFC7095]).  It also describes the process by which an RDAP server
   can migrate from jCard to JSContact.

1.1.  Rationale

   According to the feedback from RDAP Pilot Working Group
   ([RDAP-PILOT-WG], a group of RDAP server implementers representing
   registries and registrars of generic TLDs), the most commonly raised
   implementation concern, for both servers and clients related to the
   use of jCard ([RFC7095]) to represent the contact information
   associated with entities.  Working Group members reported jCard to be
   unintuitive, complicated to implement for both clients and servers,
   and incompatible with best practices for RESTful APIs.

   JSContact ([draft-ietf-jmap-jscontact]) provides a simpler and more
   efficient representation for contact information.  In addition, it
   provides a means to represent internationalised and unstructured
   contact information which cannot currently be represented using
   jCard.  Support for internationalised contact information has been

Loffredo & Brown       Expires September 24, 2020               [Page 2]
Show full document text