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

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 2012-09-19
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 None
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: March 23, 2013                                    Verisign Labs
                                                      September 19, 2012

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

Abstract

   This document describes responses in the JSON format to the Registry
   Data Access Protocol (RDAP) queries described in
   draft-ietf-weirds-rdap-query.

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 March 23, 2013.

Copyright Notice

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

Newton & Hollenbeck      Expires March 23, 2013                 [Page 1]
Internet-Draft             RDAP JSON RESPONSES            September 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology and Definitions  . . . . . . . . . . . . . . . . .  4
   3.  Common Data Types  . . . . . . . . . . . . . . . . . . . . . .  5
   4.  The Entity Object Class  . . . . . . . . . . . . . . . . . . .  6
     4.1.  The RIR Entity Object Class  . . . . . . . . . . . . . . .  7
     4.2.  The DNR Entity Object Class  . . . . . . . . . . . . . . .  9
   5.  The Nameserver Object Class  . . . . . . . . . . . . . . . . . 11
   6.  The Domain Object Class  . . . . . . . . . . . . . . . . . . . 13
     6.1.  The RIR Domain Object Class  . . . . . . . . . . . . . . . 13
     6.2.  The DNR Domain Object Class  . . . . . . . . . . . . . . . 16
   7.  The IP Network Object Class  . . . . . . . . . . . . . . . . . 20
   8.  Autonomous System Number Entity Object Class . . . . . . . . . 23
   9.  Contributing Authors and Acknowledgements  . . . . . . . . . . 26
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 27
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 27
     10.2. Informative References . . . . . . . . . . . . . . . . . . 28
   Appendix A.  Suggested Values  . . . . . . . . . . . . . . . . . . 29
     A.1.  Status . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     A.2.  Roles  . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     A.3.  URI Types  . . . . . . . . . . . . . . . . . . . . . . . . 30
   Appendix B.  Suggested Data Modeling with the Entity Object
                Class . . . . . . . . . . . . . . . . . . . . . . . . 31
     B.1.  Registrants and Contacts . . . . . . . . . . . . . . . . . 31
     B.2.  Registrars . . . . . . . . . . . . . . . . . . . . . . . . 32
   Appendix C.  IDN Query and Response Model  . . . . . . . . . . . . 34
   Appendix D.  Postal Addresses vs Location  . . . . . . . . . . . . 35
   Appendix E.  Changelog . . . . . . . . . . . . . . . . . . . . . . 36
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 37

Newton & Hollenbeck      Expires March 23, 2013                 [Page 2]
Internet-Draft             RDAP JSON RESPONSES            September 2012

1.  Introduction

   This document describes responses in the JSON [RFC4627] format for
   the RESTful web queries as defined by UNIFIED-RDAP-QUERY
   [I-D.ietf-weirds-rdap-query].  The signalling for JSON, JSON naming
   scheme, JSON namespace and extension mechanism and normalized
   references to other specifications are documented in RDAP-HTTP
   [I-D.ietf-weirds-using-http].

   The data model for the responses consists of two major categories:
   responses returned by Regional Internet Registries (RIRs) for
   registrations data related to IP addresses, reverse DNS names, and
Show full document text