JSON Responses for the Registration Data Access Protocol (RDAP)
draft-ietf-regext-rfc7483bis-04

Document Type Active Internet-Draft (regext WG)
Authors Scott Hollenbeck  , Andrew Newton 
Last updated 2020-11-30 (latest revision 2020-10-21)
Replaces draft-hollenbeck-regext-rfc7483bis
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Stream WG state Submitted to IESG for Publication (wg milestone: Aug 2020 - Submit for publicati... )
Document shepherd Jasdip Singh
Shepherd write-up Show (last changed 2020-11-09)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Barry Leiba
Send notices to Jasdip Singh <jasdips@arin.net>
REGEXT Working Group                                       S. Hollenbeck
Internet-Draft                                             Verisign Labs
Intended status: Standards Track                               A. Newton
Expires: 24 April 2021                                               AWS
                                                         21 October 2020

    JSON Responses for the Registration Data Access Protocol (RDAP)
                    draft-ietf-regext-rfc7483bis-04

Abstract

   This document describes JSON data structures representing
   registration information maintained by Regional Internet Registries
   (RIRs) and Domain Name Registries (DNRs).  These data structures are
   used to form Registration Data Access Protocol (RDAP) query
   responses.

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 24 April 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.

Hollenbeck & Newton       Expires 24 April 2021                 [Page 1]
Internet-Draft             RDAP JSON Responses              October 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology and Definitions . . . . . . . . . . . . . . .   3
     1.2.  Data Model  . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Use of JSON . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Naming  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Common Data Types . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Common Data Structures  . . . . . . . . . . . . . . . . . . .   8
     4.1.  RDAP Conformance  . . . . . . . . . . . . . . . . . . . .   8
     4.2.  Links . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Notices and Remarks . . . . . . . . . . . . . . . . . . .  10
     4.4.  Language Identifier . . . . . . . . . . . . . . . . . . .  12
     4.5.  Events  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     4.6.  Status  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.7.  Port 43 WHOIS Server  . . . . . . . . . . . . . . . . . .  14
     4.8.  Public IDs  . . . . . . . . . . . . . . . . . . . . . . .  14
     4.9.  Object Class Name . . . . . . . . . . . . . . . . . . . .  14
     4.10. An Example  . . . . . . . . . . . . . . . . . . . . . . .  14
   5.  Object Classes  . . . . . . . . . . . . . . . . . . . . . . .  16
     5.1.  The Entity Object Class . . . . . . . . . . . . . . . . .  17
     5.2.  The Nameserver Object Class . . . . . . . . . . . . . . .  23
     5.3.  The Domain Object Class . . . . . . . . . . . . . . . . .  26
     5.4.  The IP Network Object Class . . . . . . . . . . . . . . .  38
     5.5.  The Autonomous System Number Object Class . . . . . . . .  43
   6.  Error Response Body . . . . . . . . . . . . . . . . . . . . .  46
   7.  Responding to Help Queries  . . . . . . . . . . . . . . . . .  48
   8.  Responding To Searches  . . . . . . . . . . . . . . . . . . .  48
   9.  Indicating Truncated Responses  . . . . . . . . . . . . . . .  49
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  51
     10.1.  RDAP JSON Media Type Registration  . . . . . . . . . . .  52
     10.2.  JSON Values Registry . . . . . . . . . . . . . . . . . .  53
       10.2.1.  Notice and Remark Types  . . . . . . . . . . . . . .  54
       10.2.2.  Status . . . . . . . . . . . . . . . . . . . . . . .  56
       10.2.3.  Event Actions  . . . . . . . . . . . . . . . . . . .  60
       10.2.4.  Roles  . . . . . . . . . . . . . . . . . . . . . . .  62
       10.2.5.  Variant Relations  . . . . . . . . . . . . . . . . .  65
   11. Implementation Status . . . . . . . . . . . . . . . . . . . .  66
     11.1.  RedDog . . . . . . . . . . . . . . . . . . . . . . . . .  67
Show full document text