JSON Responses for the Registration Data Access Protocol (RDAP)
draft-ietf-weirds-json-response-11

The information below is for an old version of the document
Document Type Active Internet-Draft (weirds WG)
Authors Andrew Newton  , Scott Hollenbeck 
Last updated 2014-10-30 (latest revision 2014-10-28)
Replaces draft-newton-weirds-unified-json-response
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Murray Kucherawy
Shepherd write-up Show (last changed 2014-09-23)
IESG IESG state IESG Evaluation::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Needs a YES. Needs 8 more YES or NO OBJECTION positions to pass.
Responsible AD Pete Resnick
Send notices to weirds-chairs@tools.ietf.org, draft-ietf-weirds-json-response@tools.ietf.org, weirds@ietf.org
IANA IANA review state IANA OK - Actions Needed
Network Working Group                                          A. Newton
Internet-Draft                                                      ARIN
Intended status: Standards Track                           S. Hollenbeck
Expires: April 30, 2015                                    Verisign Labs
                                                        October 27, 2014

    JSON Responses for the Registration Data Access Protocol (RDAP)
                   draft-ietf-weirds-json-response-11

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 http://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 April 30, 2015.

Copyright Notice

   Copyright (c) 2014 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
   (http://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

Newton & Hollenbeck      Expires April 30, 2015                 [Page 1]
Internet-Draft             RDAP JSON RESPONSES              October 2014

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

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  . . . . . . . . . . . . . . . . . . .   9
     4.1.  RDAP Conformance  . . . . . . . . . . . . . . . . . . . .   9
     4.2.  Links . . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Notices And Remarks . . . . . . . . . . . . . . . . . . .  10
     4.4.  Language Identifier . . . . . . . . . . . . . . . . . . .  12
     4.5.  Events  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     4.6.  Status  . . . . . . . . . . . . . . . . . . . . . . . . .  14
     4.7.  Port 43 WHOIS Server  . . . . . . . . . . . . . . . . . .  14
     4.8.  Public IDs  . . . . . . . . . . . . . . . . . . . . . . .  14
     4.9.  Object Class Name . . . . . . . . . . . . . . . . . . . .  14
     4.10. An Example  . . . . . . . . . . . . . . . . . . . . . . .  15
   5.  Object Classes  . . . . . . . . . . . . . . . . . . . . . . .  17
     5.1.  The Entity Object Class . . . . . . . . . . . . . . . . .  17
     5.2.  The Nameserver Object Class . . . . . . . . . . . . . . .  24
     5.3.  The Domain Object Class . . . . . . . . . . . . . . . . .  28
     5.4.  The IP Network Object Class . . . . . . . . . . . . . . .  40
     5.5.  Autonomous System Number Entity Object Class  . . . . . .  44
   6.  Error Response Body . . . . . . . . . . . . . . . . . . . . .  47
   7.  Responding to Help Queries  . . . . . . . . . . . . . . . . .  49
   8.  Responding To Searches  . . . . . . . . . . . . . . . . . . .  50
   9.  Indicating Truncated Responses  . . . . . . . . . . . . . . .  51
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  54
     10.1.  RDAP JSON Media Type Registration  . . . . . . . . . . .  54
     10.2.  JSON Values Registry . . . . . . . . . . . . . . . . . .  55
       10.2.1.  Notice and Remark Types  . . . . . . . . . . . . . .  56
       10.2.2.  Status . . . . . . . . . . . . . . . . . . . . . . .  58
       10.2.3.  Event Actions  . . . . . . . . . . . . . . . . . . .  63
       10.2.4.  Roles  . . . . . . . . . . . . . . . . . . . . . . .  66
       10.2.5.  Variant Relations  . . . . . . . . . . . . . . . . .  69
Show full document text