Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses
draft-loffredo-regext-rdap-jcard-deprecation-03
Registration Protocols Extensions M. Loffredo
Internet-Draft IIT-CNR/Registro.it
Intended status: Standards Track G. Brown
Expires: February 1, 2021 CentralNic Group plc
July 31, 2020
Using JSContact in Registration Data Access Protocol (RDAP) JSON
Responses
draft-loffredo-regext-rdap-jcard-deprecation-03
Abstract
This document describes an RDAP extension which represents 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 February 1, 2021.
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 February 1, 2021 [Page 1]
Internet-Draft Using JSContact in RDAP July 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Rationale . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. Conventions Used in This Document . . . . . . . . . . . . 3
2. JSContact . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Using JSCard objects in RDAP Responses . . . . . . . . . . . 4
3.1. RDAP Query Parameters . . . . . . . . . . . . . . . . . . 6
4. Transition Considerations . . . . . . . . . . . . . . . . . . 7
4.1. RDAP Features Supporting a Transition Process . . . . . . 7
4.1.1. Notices and Link Relationships . . . . . . . . . . . 7
4.1.2. rdapConformance Property . . . . . . . . . . . . . . 7
4.1.3. Query Parameters . . . . . . . . . . . . . . . . . . 7
4.2. Transition Procedure . . . . . . . . . . . . . . . . . . 7
4.2.1. Transition Stages . . . . . . . . . . . . . . . . . . 8
4.2.1.1. Stage 1: only jCard provided . . . . . . . . . . 8
4.2.1.2. Stage 2: jCard sunset . . . . . . . . . . . . . . 8
4.2.1.3. Stage 3: jCard deprecation . . . . . . . . . . . 9
4.2.1.4. Stage 4: jCard deprecated . . . . . . . . . . . . 11
4.2.1.5. Length . . . . . . . . . . . . . . . . . . . . . 11
4.2.1.6. Goals . . . . . . . . . . . . . . . . . . . . . . 11
5. Implementation Status . . . . . . . . . . . . . . . . . . . . 12
5.1. IIT-CNR/Registro.it . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 14
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 15
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 15
A.3. Change from 02 to 023 . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
This document specifies an extension to the Registration Data Access
Protocol (RDAP) that allows RDAP servers to 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 transition from jCard to JSContact. RDAP query and response
extensions are defined to facilitate the transition process.
Show full document text