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

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 2013-06-12
Replaces draft-newton-weirds-unified-json-response
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd Murray Kucherawy
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          A. Newton
Internet-Draft                                                      ARIN
Intended status: Standards Track                           S. Hollenbeck
Expires: December 14, 2013                                 Verisign Labs
                                                           June 12, 2013

    JSON Responses for the Registration Data Access Protocol (RDAP)
                   draft-ietf-weirds-json-response-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 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 December 14, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Newton & Hollenbeck     Expires December 14, 2013               [Page 1]
Internet-Draft             RDAP JSON RESPONSES                 June 2013

   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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology and Definitions . . . . . . . . . . . . . . . . .   4
   3.  Use of JSON . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Signaling . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  Naming  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Common Data Types . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Common Data Structures  . . . . . . . . . . . . . . . . . . .   7
     5.1.  RDAP Conformance  . . . . . . . . . . . . . . . . . . . .   8
     5.2.  Links . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.3.  Notices And Remarks . . . . . . . . . . . . . . . . . . .   9
     5.4.  Language Identifier . . . . . . . . . . . . . . . . . . .  11
     5.5.  Events  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     5.6.  Status  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     5.7.  Port 43 Whois Server  . . . . . . . . . . . . . . . . . .  12
     5.8.  Public IDs  . . . . . . . . . . . . . . . . . . . . . . .  12
     5.9.  An Example  . . . . . . . . . . . . . . . . . . . . . . .  13
   6.  Object Classes  . . . . . . . . . . . . . . . . . . . . . . .  14
     6.1.  The Entity Object Class . . . . . . . . . . . . . . . . .  14
     6.2.  The Nameserver Object Class . . . . . . . . . . . . . . .  20
     6.3.  The Domain Object Class . . . . . . . . . . . . . . . . .  23
     6.4.  The IP Network Object Class . . . . . . . . . . . . . . .  35
     6.5.  Autonomous System Number Entity Object Class  . . . . . .  39
   7.  Error Response Body . . . . . . . . . . . . . . . . . . . . .  42
   8.  Responding to Help Queries  . . . . . . . . . . . . . . . . .  43
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  44
     9.1.  Status  . . . . . . . . . . . . . . . . . . . . . . . . .  46
     9.2.  Event Actions . . . . . . . . . . . . . . . . . . . . . .  48
     9.3.  Roles . . . . . . . . . . . . . . . . . . . . . . . . . .  50
     9.4.  Variant Relations . . . . . . . . . . . . . . . . . . . .  53
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  54
   11. Internationalization Considerations . . . . . . . . . . . . .  54
     11.1.  Character Encoding . . . . . . . . . . . . . . . . . . .  54
     11.2.  URIs and IRIs  . . . . . . . . . . . . . . . . . . . . .  54
     11.3.  Language Tags  . . . . . . . . . . . . . . . . . . . . .  55
     11.4.  Internationalized Domain Names . . . . . . . . . . . . .  55
   12. Privacy Considerations  . . . . . . . . . . . . . . . . . . .  55
Show full document text