draft-ietf-weirds-json-response-02.txt   draft-ietf-weirds-json-response-03.txt 
Network Working Group A. Newton Network Working Group A.L. Newton
Internet-Draft ARIN Internet-Draft ARIN
Intended status: Standards Track S. Hollenbeck Intended status: Standards Track S. Hollenbeck
Expires: July 7, 2013 Verisign Labs Expires: October 11, 2013 Verisign Labs
January 3, 2013 April 09, 2013
JSON Responses for the Registration Data Access Protocol (RDAP) JSON Responses for the Registration Data Access Protocol (RDAP)
draft-ietf-weirds-json-response-02 draft-ietf-weirds-json-response-03
Abstract Abstract
This document describes JSON data structures representing This document describes JSON data structures representing
registration information maintained by Regional Internet Registries registration information maintained by Regional Internet Registries
(RIRs) and Domain Name Registries (DNRs). These data structures are (RIRs) and Domain Name Registries (DNRs). These data structures are
used to form Registration Data Access Protocol (RDAP) query used to form Registration Data Access Protocol (RDAP) query
responses. responses.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 7, 2013. This Internet-Draft will expire on October 11, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology and Definitions . . . . . . . . . . . . . . . . . 5
3. Common Data Types . . . . . . . . . . . . . . . . . . . . . . 6
4. Use of JSON . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.1. Signaling . . . . . . . . . . . . . . . . . . . . . . . . 8
4.2. Naming . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5. Common Data Structures . . . . . . . . . . . . . . . . . . . . 10
5.1. RDAP Conformance . . . . . . . . . . . . . . . . . . . . . 10
5.2. Notices . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.3. Language Identifier . . . . . . . . . . . . . . . . . . . 11
5.4. An Example . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Object Class Links . . . . . . . . . . . . . . . . . . . . . . 13
7. The Entity Object Class . . . . . . . . . . . . . . . . . . . 14
7.1. The RIR Entity Object Class . . . . . . . . . . . . . . . 15
7.2. The DNR Entity Object Class . . . . . . . . . . . . . . . 16
8. The Nameserver Object Class . . . . . . . . . . . . . . . . . 19
9. The Domain Object Class . . . . . . . . . . . . . . . . . . . 21
9.1. The RIR Domain Object Class . . . . . . . . . . . . . . . 21
9.2. The DNR Domain Object Class . . . . . . . . . . . . . . . 24
10. The IP Network Object Class . . . . . . . . . . . . . . . . . 29
11. Autonomous System Number Entity Object Class . . . . . . . . . 32
12. Error Response Body . . . . . . . . . . . . . . . . . . . . . 35
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
14. Internationalization Considerations . . . . . . . . . . . . . 37
14.1. Character Encoding . . . . . . . . . . . . . . . . . . . . 37
14.2. URIs and IRIs . . . . . . . . . . . . . . . . . . . . . . 37
14.3. Language Tags . . . . . . . . . . . . . . . . . . . . . . 37
14.4. Internationalized Domain Names . . . . . . . . . . . . . . 37
15. Contributing Authors and Acknowledgements . . . . . . . . . . 38
16. References . . . . . . . . . . . . . . . . . . . . . . . . . . 39
16.1. Normative References . . . . . . . . . . . . . . . . . . . 39
16.2. Informative References . . . . . . . . . . . . . . . . . . 40
Appendix A. Suggested Values . . . . . . . . . . . . . . . . . . 41
A.1. Status . . . . . . . . . . . . . . . . . . . . . . . . . . 41
A.2. Roles . . . . . . . . . . . . . . . . . . . . . . . . . . 41
A.3. Variant Relations . . . . . . . . . . . . . . . . . . . . 42
Appendix B. Suggested Data Modeling with the Entity Object
Class . . . . . . . . . . . . . . . . . . . . . . . . 43
B.1. Registrants and Contacts . . . . . . . . . . . . . . . . . 43
B.2. Registrars . . . . . . . . . . . . . . . . . . . . . . . . 44
Appendix C. IDN Query and Response Model . . . . . . . . . . . . 46
Appendix D. Postal Addresses vs Location . . . . . . . . . . . . 47
Appendix E. Motivations for Using JSON . . . . . . . . . . . . . 48
Appendix F. Changelog . . . . . . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 51
1. Introduction 1. Introduction
This document describes responses in the JSON [RFC4627] format for This document describes responses in the JSON [RFC4627] format for
the RESTful web queries as defined by UNIFIED-RDAP-QUERY the RESTful web queries as defined by the Registration Data Access
[I-D.ietf-weirds-rdap-query]. Protocol Lookup Format [I-D.ietf-weirds-rdap-query].
The data model for the responses consists of two major categories: The data model for JSON responses is specified in four sections:
responses returned by Regional Internet Registries (RIRs) for
1. simple data types conveyed in JSON strings
2. data structures specified as JSON arrays or objects that are used
repeatedly when building up larger objects
3. object classes representing structured data corresponding to a
given query
4. the response to an error
The object classes represent responses for two major categories of
data: responses returned by Regional Internet Registries (RIRs) for
registrations data related to IP addresses, reverse DNS names, and registrations data related to IP addresses, reverse DNS names, and
Autonomous System numbers; and responses returned by Domain Name Autonomous System numbers; and responses returned by Domain Name
Registries (DNRs) for registration data related to forward DNS names. Registries (DNRs) for registration data related to forward DNS names.
The RIR object classes are a proper subset of the DNR object classes. The following object classes are served by both RIRs and DNRs:
The current division between RIR and DNR object classes is given to
illustrate an expectation of what data may be expected from an RIR vs
a DNR. However, implementers should be aware that RIRs are not
limited to the data in the RIR object classes (as an example, some
RIRs have a notion of "status" for entities as defined in the DNR
entity object class and may at some point start publishing that
data).
Object classes defined in the document represent a minimal set of 1. domains
2. nameservers
3. entities
The information served by both RIRs and DNRs for these object classes
overlap extensively and are given in this document as a unified model
for both classes of service.
In addition to the object classes listed above, RIRs also serve the
following object classes:
1. IP networks
2. Autonomous System numbers
Object classes defined in this document represent a minimal set of
what a compliant client/server MUST understand to function correctly, what a compliant client/server MUST understand to function correctly,
however some deployments may want to include additional object however some deployments may want to include additional object
classes to suit individual needs. Anticipating this need for classes to suit individual needs. Anticipating this need for
extension, Section 4.2 of this document defines a mechanism for extension, Section 3.2 of this document defines a mechanism for
extending the JSON (objects) that are described in this document. extending the JSON objects that are described in this document.
2. Terminology and Definitions 2. Terminology and Definitions
The following list describes terminology and definitions used The following list describes terminology and definitions used
throughout this document: throughout this document:
DNR: "Domain Name Registry". DNR: "Domain Name Registry".
LDH: "Letters, Digits, Hyphen".
member: data found with in an object as defined by JSON member: data found with in an object as defined by JSON
[RFC4627]. [RFC4627].
object: a data structure as defined by JSON [RFC4627]. object: a data structure as defined by JSON [RFC4627].
object class: the definition of members that may be found in JSON object class: the definition of members that may be found in JSON
objects described in this document. objects described in this document.
object instance: an instantiation or specific instance of an object object instance: an instantiation or specific instance of an object
class. class.
RDAP: "Registration Data Access Protocol". RDAP: "Registration Data Access Protocol".
RIR: "Regional Internet Registry". RIR: "Regional Internet Registry".
3. Common Data Types 3. Use of JSON
JSON [RFC4627] defines the data types of a number, character string,
boolean, array, object and null. This section describes the
semantics and/or syntax reference for data types used in this
document derived from the JSON character string.
'handle': DNRs and RIRs have registry-unique identifiers that may
be used to specifically reference an object instance. The
semantics of this data type as found in this document is to be a
registry-unique reference to the closest enclosing object where
the value is found. The data type names 'registryId', 'roid',
'nic-handle', 'registrationNo', etc... are terms often synonymous
with this data type. In this document, the term 'handle' is used.
The term exposed to users by clients is a presentation issue
beyond the scope of this document.
IPv4 addresses: The representation of IPv4 addresses in this
document uses the dotted-decimal notation described in [RFC1166].
An example of this textual representation is '192.0.2.0'.
IPv6 addresses: The representation of IPv6 addresses in this
document follow the forms outlined in [RFC5952]. An example of
this textual representation is '2001:db8::1:0:0:1'.
country codes: Where the identity of a geopolitical nation or
country is needed, these identities are represented with the
alpha-2 or 2 character country code designation as defined in
[ISO.3166.1988]. The alpha-2 representation is used because it is
freely available whereas the alpha-3 and numeric-3 standards are
not.
domain names: Textual representations of DNS names follow the rules
set forth in [RFC4343], specifically the case insensitivity and
character escaping rules. Trailing periods are optional for both
input and output.
email addresses: Textual representations of email addresses follow
the syntax defined in [RFC5322].
dates and times: The syntax for values denoting dates and times is
defined in [RFC3339].
URIs: The syntax for values denoting a Uniform Resource Identifier
(URI) is defined by [RFC3986].
Many of the object classes defined in this document contain values
representing telephone numbers. Servers are encouraged to provide
those telephone numbers in [E164] format, however clients MUST be
prepared for telephone numbers that do not adhere to the [E164]
standard.
Postal addresses also appear in some of the object classes. This
document specifies no standard for postal addresses as many
registries would have to undergo severe data cleanup efforts to meet
such standards.
4. Use of JSON
4.1. Signaling 3.1. Signaling
Clients may signal their desire for JSON using the "application/json" Media type signaling for the JSON data specified in this document is
media type or the more specific media type "application/rdap" as specified in [I-D.ietf-weirds-using-http].
specified in Section 13.
4.2. Naming 3.2. Naming
Clients processing JSON [RFC4627] responses SHOULD ignore values Clients processing JSON [RFC4627] responses are under no obligation
associated with unrecognized names. Servers MAY insert values to process unrecognized JSON attributes but SHOULD NOT treat them as
signified by names into the JSON responses which are not specified in an error. Servers MAY insert values signified by names into the JSON
this document. Insertion of unspecified values into JSON responses responses which are not specified in this document. Insertion of
SHOULD have names prefixed with a short identifier followed by an unspecified values into JSON responses SHOULD have names prefixed
underscore followed by a meaningful name. The full JSON name, the with a short identifier followed by an underscore followed by a
prefix plus the underscore plus the meaningful name, SHOULD adhere to meaningful name. The full JSON name, the prefix plus the underscore
the character and name limitations of the prefix registry described plus the meaningful name, SHOULD adhere to the character and name
in [I-D.ietf-weirds-using-http]. limitations of the prefix registry described in
[I-D.ietf-weirds-using-http].
Consider the following JSON response with JSON names. "handle" and Consider the following JSON response with JSON names. some of which
"remarks" are JSON names specified in this document. are not specified in this document.
{ {
"handle" : "ABC123", "handle" : "ABC123",
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
] [
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
]
} }
Figure 1 Figure 1
If The Registry of the Moon desires to express information not found If The Registry of the Moon desires to express information not found
in this specification, it might select "lunarNic" as its identifying in this specification, it might select "lunarNic" as its identifying
prefix and insert, as an example, the name prefix and insert, as an example, the name
"lunarNic_beforeOneSmallStep" to signify registrations occuring "lunarNic_beforeOneSmallStep" to signify registrations occurring
before the first moon landing and the name before the first moon landing and the name
"lunarNic_harshMistressNotes" containing other descriptive text. "lunarNic_harshMistressNotes" containing other descriptive text.
Consider the following JSON response with JSON names, some of which Consider the following JSON response with JSON names, some of which
should be ignored by clients without knowledge of their meaning. should be ignored by clients without knowledge of their meaning.
{ {
"handle" : "ABC123", "handle" : "ABC123",
"lunarNic_beforeOneSmallStep" : "TRUE THAT!", "lunarNic_beforeOneSmallStep" : "TRUE THAT!",
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"lunarNic_harshMistressNotes" : "lunarNic_harshMistressNotes" :
[ [
"In space,", "In space,",
"nobody can hear you scream." "nobody can hear you scream."
] ]
} }
Figure 2 Figure 2
skipping to change at page 9, line 36 skipping to change at page 5, line 38
for future revisions to this specification. for future revisions to this specification.
Clients processing JSON responses MUST be prepared for values Clients processing JSON responses MUST be prepared for values
specified in this document to be absent from a response as no JSON specified in this document to be absent from a response as no JSON
value listed is required to appear in a response. In other words, value listed is required to appear in a response. In other words,
servers MAY remove values as is needed by the policies of the server servers MAY remove values as is needed by the policies of the server
operator. operator.
Finally, all JSON names specified in this document are case Finally, all JSON names specified in this document are case
sensitive. Both servers and clients MUST transmit and process them sensitive. Both servers and clients MUST transmit and process them
according to the character casing specified. using the specified character case.
4. Common Data Types
JSON [RFC4627] defines the data types of a number, character string,
boolean, array, object and null. This section describes the
semantics and/or syntax reference for data types used in this
document derived from the JSON character string.
'handle': DNRs and RIRs have registry-unique identifiers that
may be used to specifically reference an object
instance. The semantics of this data type as found
in this document is to be a registry-unique
reference to the closest enclosing object where the
value is found. The data type names 'registryId',
'roid', 'nic-handle', 'registrationNo', etc. are
terms often synonymous with this data type. In
this document, the term 'handle' is used. The term
exposed to users by clients is a presentation issue
beyond the scope of this document.
IPv4 addresses: The representation of IPv4 addresses in this
document uses the dotted-decimal notation described
in [RFC1166]. An example of this textual
representation is '192.0.2.0'.
IPv6 addresses: The representation of IPv6 addresses in this
document follow the forms outlined in [RFC5952].
An example of this textual representation is
'2001:db8::1:0:0:1'.
country codes: Where the identity of a geopolitical nation or
country is needed, these identities are represented
with the alpha-2 or 2 character country code
designation as defined in [ISO.3166.1988]. The
alpha-2 representation is used because it is freely
available whereas the alpha-3 and numeric-3
standards are not.
LDH names: Textual representations of DNS names where the
labels of the domain are all "letters, digits,
hyphen" labels as described by [RFC5890]. Trailing
periods are optional.
Unicode names: Textual representations of DNS names were one or
more of the labels are u-labels as described by
[RFC5890]. Trailing periods are optional.
dates and times: The syntax for values denoting dates and times is
defined in [RFC3339].
URIs: The syntax for values denoting a Uniform Resource
Identifier (URI) is defined by [RFC3986].
Contact information is defined using JSON vCards as described in
[I-D.kewisch-vcard-in-json]
5. Common Data Structures 5. Common Data Structures
This section defines three common data structures to be used in This section defines common data structures to be used in response.
respones. Each of these datatypes MAY appear within any object class Each of these structures MAY appear within any object class of a
of a response, but the intended purpose is that they will be mostly response.
used in the top-most object class of a response.
5.1. RDAP Conformance 5.1. RDAP Conformance
The first data structure is named "rdapConformance" and is simply an The first data structure is named "rdapConformance" and is simply an
array of strings, each providing a hint as to the specifications used array of strings, each providing a hint as to the specifications used
in the construction of the response. in the construction of the response. This data structure appears
only in the top most object of a response.
An example rdapConformance data structure. An example rdapConformance data structure:
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
] ]
Figure 3 Figure 3
The string literal "rdap_level_0" signifies conformance with this The string literal "rdap_level_0" signifies conformance with this
specification. When custom JSON values are inserted into responses, specification. When custom JSON values are inserted into responses,
conformance to those custom specifications should use a string conformance to those custom specifications should use a string
prefixed with the appropriate identifier from the IANA prefix prefixed with the appropriate identifier from the IANA prefix
identifier registry specified in [I-D.ietf-weirds-using-http]. For identifier registry specified in [I-D.ietf-weirds-using-http]. For
example, if the fictional Registry of the Moon want to signify that example, if the fictional Registry of the Moon wants to signify that
their JSON responses are conformant with their registered extensions, their JSON responses are conformant with their registered extensions,
the string used might be "lunarNIC_level_0". the string used might be "lunarNIC_level_0".
Example rdapConformance structure with custom extensions noted. Example rdapConformance structure with custom extensions noted:
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0", "rdap_level_0",
"lunarNic_level_0" "lunarNic_level_0"
] ]
Figure 4 Figure 4
5.2. Notices 5.2. Links
The second data structure is named "notices" and is an array of The "links" array is found in data structures to signify links to
objects. Each object contains a "title" string representing the other resources on the Internet. The relationship of these links is
title of the notice object, an array of strings named "description" defined by the IANA registry described by [RFC5988].
for the purposes of conveying any descriptive text about the notice,
and an optional "links" object as described in Section 6.
An exmaple of the notices data structure. The following is an example of the link structure:
{
"value" : "http://example.com/context_uri",
"rel" : "self",
"href" : "http://example.com/target_uri",
"hreflang" : [ "en", "ch" ],
"title" : [ "title1", "title2" ],
"media" : "screen",
"type" : "application/json"
}
Figure 5
The JSON name/values of "rel", "href", "hreflang", "title", "media",
and "type" correspond to values found in Section 5 of [RFC5988]. The
"value" JSON value is the context URI as described by [RFC5988]. The
"value", "rel", and "href" JSON values MUST be specified. All other
JSON values are optional.
This is an example of the "links" array as it might be found in an
object class:
"links" :
[
{
"value" : "http://example.com/ip/2001:db8::123",
"rel" : "self",
"href" : "http://example.com/ip/2001:db8::123"
},
{
"value" : "http://example.com/ip/2001:db8::123",
"rel" : "up",
"href" : "http://example.com/ip/2001:db8::/48"
}
]
5.3. Notices And Remarks
The "notices" and "remarks" data structures take the same form. The
"notices" structure denotes information about the service providing
RDAP information, whereas the "remarks" structure denotes information
about the object class it is contained within (see Section 6
regarding object classes).
Both are an array of objects. Each object contains an optional
"title" string representing the title of the object, an array of
strings named "description" for the purposes of conveying any
descriptive text, and an optional "links" array as described in
Section 5.2.
An example of the notices data structure:
"notices" : "notices" :
[ [
{ {
"title" : "Terms of Use", "title" : "Terms of Use",
"description" : "description" :
[ [
"This service is subject to The Registry of the Moons", "Service subject to The Registry of the Moon's TOS.",
"terms of service." "Copyright (c) 2020 LunarNIC"
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/entity/XXXX", "value" : "http://example.net/entity/XXXX",
"rel" : "alternate", "rel" : "alternate",
"type" : "text/html", "type" : "text/html",
"href" : "http://www.example.com/terms_of_use.html" "href" : "http://www.example.com/terms_of_use.html"
} }
] ]
} }
] ]
Figure 5 Figure 6
5.3. Language Identifier It is the job of the clients to determine line breaks, spacing and
display issues for sentences within the character strings of the
"description" array. Servers SHOULD NOT split sentences across
multiple strings of this array. Each string is to represent a
semantic division in the descriptive text.
The third data structure is a simple JSON name/value of "lang" with a An example of the remarks data structure:
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
]
Figure 7
Note that objects in the "remarks" array may also have a "links"
array.
While the "remarks" array will appear in many object classes in a
response, the "notices" array appears only in the top most object of
a response.
5.4. Language Identifier
This data structure is a simple JSON name/value of "lang" with a
string containing a language identifier as described by [RFC5646]. string containing a language identifier as described by [RFC5646].
"lang" : "mn-Cyrl-MN" "lang" : "mn-Cyrl-MN"
Figure 6 Figure 8
5.4. An Example The 'lang' attribute may appear anywhere in an object class or data
structure.
5.5. Events
This data structure represents events that have occurred on an
instance of an object class (see Section 6 regarding object classes).
This is an example of an "events" array.
"events" :
[
{
"eventAction" : "registration",
"eventActor" : "SOMEID-LUNARNIC",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventActor" : "OTHERID-LUNARNIC",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
Figure 9
The "events" array consists of objects, each with the following
members:
o 'eventAction' -- a string denoting the reason for the event
o 'eventActor' -- an optional identifier denoting the actor
responsible for the event
o 'eventDate' -- a string containing the time and date the event
occurred.
Events can be future dated. One use case for future dating of events
is to denote when an object expires from a registry.
See Appendix A.2 for a list of suggested values for the 'eventAction'
string. See Appendix C regarding the various ways events can be
modeled.
5.6. Status
This data structure, named 'status', is an array of strings
indicating the state of a registered object (see Appendix A.1 for
suggested values).
5.7. Port 43 Whois Server
This data stricture, named 'port43', is a simple string containing
the fully-qualified host name of the WHOIS [RFC3912] server where the
containing object instance may be found. Note that this is not a
URI, as there is not Whois URI scheme.
5.8. An Example
This is an example response with both rdapConformance and notices This is an example response with both rdapConformance and notices
embedded. embedded:
{ {
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
], ],
"notices" : "notices" :
[ [
{ {
"title" : "Content Redacted", "title" : "Content Redacted",
skipping to change at page 12, line 39 skipping to change at page 12, line 34
"type" : "text/html", "type" : "text/html",
"href" : "http://www.example.com/redaction_policy.html" "href" : "http://www.example.com/redaction_policy.html"
} }
] ]
} }
], ],
"lang" : "en", "lang" : "en",
"startAddress" : "192.0.2.0", "startAddress" : "192.0.2.0",
"endAddress" : "192.0.2.255", "endAddress" : "192.0.2.255",
"handle" : "XXXX-RIR", "handle" : "XXXX-RIR",
"ipVersion" : 4, "ipVersion" : "v4",
"name": "NET-RTR-1", "name": "NET-RTR-1",
"description" : [ "A network used for example documentation" ], "description" : [ "A network used for example documentation" ],
"parentHandle" : "YYYY-RIR", "parentHandle" : "YYYY-RIR",
"remarks" : "remarks" :
[ [
"she sells seas shells",
"down by the seashore"
]
}
Figure 7
6. Object Class Links
Each object class defined in this document may have links to other
resources on the Internet. The relationship of these links is
defined by the IANA registry described by [RFC5988].
The following is an example of the link structure of object classes
{ {
"value" : "http://example.com/context_uri", "description" :
"rel" : "self", [
"href" : "http://example.com/target_uri", "She sells sea shells down by the sea shore.",
"hreflang" : [ "en", "ch" ], "Originally written by Terry Sullivan."
"title" : [ "title1", "title2" ], ]
"media" : "screen",
"type" : "application/json"
} }
]
}
Figure 8 Figure 10
The JSON name/values of "rel", "href", "hreflang", "title", "media", 6. Object Classes
and "type" correspond to values found in Section 5 of [RFC5988]. The
"value" JSON value is the context URI as described by [RFC5988]. The
"value", "rel", and "href" JSON values MUST be specified. All other
JSON values are optional.
Within an object class, these structures are to be in an array named Object classes represent structures appropriate for a response from
"links". the queries specified in [I-D.ietf-weirds-rdap-query].
This is an example of the "links" array as it might be found in an Each object class contains a "links" array as specified in
object class. Section 5.2. For every object class in a response, whether the
object class is directly representing the response to a query or is
embedded in other object classes, servers SHOULD provide a link
representing a URI for that object class using the "self"
relationship as specified in the IANA registry specified by
[RFC5988]. As explained in Section 6.2, this may be not always be
possible for name server data. Clients MUST be able to process
object instances without a "self" link. When present, clients MAY
use the self link for caching data. Servers MAY provide more than
one "self" link for any given object instance.
"links" : This is an example of the "links" array with a self link to an object
[ class:
{
"value" : "http://example.com/ip/2001:db8::123",
"rel" : "self",
"href" : "http://example.com/ip/2001:db8::123"
},
{
"value" : "http://example.com/ip/2001:db8::123",
"rel" : "up",
"href" : "http://example.com/ip/2001:db8::/48"
}
] "links" :
[
{
"value" : "http://example.com/ip/2001:db8::123",
"rel" : "self",
"href" : "http://example.com/ip/2001:db8::123"
}
]
7. The Entity Object Class 6.1. The Entity Object Class
The entity object class appears throughout this document and is an The entity object class appears throughout this document and is an
appropriate response for the /entity/XXXX query defined in UNIFIED- appropriate response for the /entity/XXXX query defined in
RDAP-QUERY [I-D.ietf-weirds-rdap-query]. This object class Registration Data Access Protocol Lookup Format
represents the information of organizations, corporations, [I-D.ietf-weirds-rdap-query]. This object class represents the
governments, non-profits, clubs, individual persons, and informal information of organizations, corporations, governments, non-profits,
groups of people. All of these representations are so similar that clubs, individual persons, and informal groups of people. All of
it is best to represent them in JSON [RFC4627] with one construct, these representations are so similar that it is best to represent
the entity object class, to aid in the re-use of code by them in JSON [RFC4627] with one construct, the entity object class,
implementers. to aid in the re-use of code by implementers.
Many of the members of the entity object class are repeated in other Some of the members of the entity object class are repeated in other
object classes described later in this document. object classes described later in this document.
7.1. The RIR Entity Object Class The entity object is served by both RIRs and DNRs. The following is
an example of an entity that might be served by an RIR:
The following is an example of an RIR entity:
{ {
"handle" : "XXXX", "handle" : "XXXX",
"entityNames": [ "Joe Bob, Inc.", "Bobby Joe Shopping" ], "vCard" :
"roles" : [ "registrant" ],
"postalAddress" :
[ [
"123 Maple Ave", [ "version", {}, "text", "4.0" ],
"Suite 90001", [ "fn", {}, "text", "Joe Bob, Inc." ],
"Vancouver", [ "fn", {}, "text", "Bobby Joe Shopping" ],
"BC", [ "label", {}, "text", "123 Maple Ave\n",
"12393" "Suite 90001\n",
"Vancouver\n",
"BC\n",
"1239\n" ],
[ "email", {}, "text", "joe at bob.com" ],
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
], ],
"emails" : [ "joe@bob.com", "bob@joe.com" ], "roles" : [ "registrant" ],
"phones" :
{
"office" : [ "1-958-555-4321", "1-958-555-4322" ],
"fax" : [ "1-958-555-4323" ],
"mobile" : [ "1-958-555-4324" ]
},
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.com/entity/XXXX", "value" : "http://example.com/entity/XXXX",
"rel" : "self", "rel" : "self",
"href" : "http://example.com/entity/XXXX" "href" : "http://example.com/entity/XXXX"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"lastChangedDate" : "1990-12-31T23:59:60Z", [
"lastChangedBy" : "joe@bob.com" {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
}
],
"asEventActor" :
[
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
} }
This object as the following members. This object has the following members:
o handle -- a string representing an registry unique identifier of o handle -- a string representing an registry unique identifier of
the entity the entity
o entityNames -- an array of strings, each signifying the name of o vCard -- a JSON vCard with the entity's contact information
the entity
o roles -- an array of strings, each signifying the relationship an o roles -- an array of strings, each signifying the relationship an
object would have with its closest containing object. object would have with its closest containing object (see
Appendix A.3 for suggested values)
o postalAddress -- an array of string, each representing a line in a
postal address.
o emails -- an array of strings, each containing an email address
for the entity
o phones -- an object containing telephone information associated
with the entity, with the following members:
* office -- an array of strings, each being a telephone number
* fax -- an array of strings, each being a telephone number
* mobile -- an array of strings, each being a telephone number
o remarks -- an array of strings, each containing comments about the
entity
o links -- see Section 6
o registrationDate -- a string containing the date the entity was
registered
o lastChangedDate -- a string containing the date of last change
made to the entity
o lastChangedBy -- a string containing an identifier of the party
responsible for the last change made to the entity registration
7.2. The DNR Entity Object Class
The DNR entity object class is a superset of the RIR entity object o remarks -- see Section 5.3
class (Section 7.1). It has the following additional members:
o registrationBy -- a string containing an identifier of the party o links -- see Section 5.2
responsible for the registration of the entity
o sponsoredBy -- a string containing an identifier of the party o events -- see Section 5.5
through which the registration was made, such as an IANA approved
registrar
o resoldBy -- a string containing an identifier of the party o asEventActor -- this data structure takes the same form as the
originating the registration of the entity. 'events' data structure (see Section 5.5), but each object in the
array MUST NOT have an 'eventActor' member. These objects denote
that the entity is an event actor for the given events. See
Appendix C regarding the various ways events can be modeled.
o status -- an array of strings indicating the state of the entity o status -- see Section 5.6
o port43 -- a string containing the fully-qualified host name of the o port43 -- see Section 5.7
WHOIS [RFC3912] server where the object instance may be found.
The following is an example of a DNR entity: The following is an example of a entity that might be served by a
DNR:
{ {
"handle" : "XXXX", "handle" : "XXXX",
"entityNames": [ "Joe Bob, Inc.", "Bobby Joe Shopping" ], "vCard" :
"status" : [ "validated", "locked" ],
"postalAddress" :
[ [
"123 Maple Ave", [ "version", {}, "text", "4.0" ],
"Suite 90001", [ "fn", {}, "text", "Joe Bob, Inc." ],
"Vancouver", [ "fn", {}, "text", "Bobby Joe Shopping" ],
"BC", [ "label", {}, "text", "123 Maple Ave\n",
"12393" "Suite 90001\n",
"Vancouver\n",
"BC\n",
"1239\n" ],
[ "email", {}, "text", "joe at bob.com" ],
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
], ],
"emails" : [ "joe@bob.com", "bob@joe.com" ], "status" : [ "validated", "locked" ],
"phones" :
{
"office" : [ "1-958-555-4321", "1-958-555-4322" ],
"fax" : [ "1-958-555-4323" ],
"mobile" : [ "1-958-555-4324" ]
},
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.com/entity/XXXX", "value" : "http://example.com/entity/XXXX",
"rel" : "self", "rel" : "self",
"href" : "http://example.com/entity/XXXX" "href" : "http://example.com/entity/XXXX"
} }
], ],
"port43" : "whois.example.net", "port43" : "whois.example.net",
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"registrationBy" : "ABC123", [
"lastChangedDate" : "1990-12-31T23:59:60Z", {
"lastChangedBy" : "ABC123", "eventAction" : "registration",
"sponsoredBy" : "SponsorXYZ", "eventDate" : "1990-12-31T23:59:60Z"
"resoldBy" : "ResellerPDQ" },
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
}
]
} }
8. The Nameserver Object Class 6.2. The Nameserver Object Class
The nameserver object class represents information regarding DNS name
The nameserver object class is used by both RIRs and DNRs. Unlike servers used in both forward and reverse DNS. RIRs and some DNRs
other object classes used by both registries where the RIR object
class is a subset of the DNR object class, a clear delineation is not
made with the nameserver object class because some DNRs have the same
or a similar registration model as the RIRs. RIRs and some DNRs
register or expose nameserver information as an attribute of a domain register or expose nameserver information as an attribute of a domain
name, while other DNRs model nameservers as "first class objects". name, while other DNRs model nameservers as "first class objects".
The nameserver object class accommodates both models and degrees of The nameserver object class accommodates both models and degrees of
variation in between. variation in between.
The following is an example of a nameserver object. The following is an example of a nameserver object.
{ {
"handle" : "XXXX", "handle" : "XXXX",
"name" : "ns1.example.com", "ldhName" : "ns1.xn--fo-5ja.example",
"unicodeName" : "foo.example",
"status" : [ "active" ], "status" : [ "active" ],
"ipAddresses" : [ "192.0.2.1", "192.0.2.2" ], "ipAddresses" :
{
"v4": [ "192.0.2.1", "192.0.2.2" ],
"v6": [ "2001:db8::123" ]
},
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/nameserver/xxxx", "value" : "http://example.net/nameserver/xxxx",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/nameserver/xxxx" "href" : "http://example.net/nameserver/xxxx"
} }
], ],
"port43" : "whois.example.net", "port43" : "whois.example.net",
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"registrationBy" : "ABC123", [
"lastChangedDate" : "1990-12-31T23:59:60Z", {
"lastChangedBy" : "ABC123", "eventAction" : "registration",
"sponsoredBy" : "SponsorXYZ", "eventDate" : "1990-12-31T23:59:60Z"
"resoldBy" : "ResellerPDQ" },
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
}
]
} }
Figure 9 Figure 11
Figure 9 is an example of a nameserver object with all values given. Figure 11 is an example of a nameserver object with all values given.
Registries using a first-class nameserver data model would embed this Registries using a first-class nameserver data model would embed this
in domain objects as well as allowing references to it with the in domain objects as well as allowing references to it with the "/
/nameserver query type (all depending on the registry operators nameserver" query type (all depending on the registry operators
policy). Other registries may pare back the information as needed. policy). Other registries may pare back the information as needed.
Figure 10 is an example of a nameserver object as would be found in Figure 12 is an example of a nameserver object as would be found in
RIRs and some DNRs, while Figure 11 is an example of a nameserver RIRs and some DNRs, while Figure 13 is an example of a nameserver
object as would be found in other DNRs. object as would be found in other DNRs.
The following is an example of the simplest nameserver object. The following is an example of the simplest nameserver object:
{ {
"name" : "ns1.example.com" "ldhName" : "ns1.example.com"
} }
Figure 10 Figure 12
The following is an example of a simple nameserver object that might The following is an example of a simple nameserver object that might
be commonly used by DNRs. be commonly used by DNRs:
{ {
"name" : "ns1.example.com", "ldhName" : "ns1.example.com",
"ipAddresses" : [ "2001:db8::123", "2001:db8::124" ] "ipAddresses" : { "v6" : [ "2001:db8::123", "2001:db8::124" ] }
} }
Figure 11 Figure 13
The nameserver object class has the following members: The nameserver object class has the following members:
o handle -- a string representing an registry unique identifier of o handle -- a string representing an registry unique identifier of
the nameserver the nameserver
o name -- a string containing the DNS name of the nameserver o ldhName -- a string containing the LDH name of the nameserver (see
Section 4)
o ipAddresses -- an array of strings containing IPv4 and/or IPv6 o unicodeName -- a string containing a DNS unicode name of the
addresses of the nameserver nameserver (see Section 4)
The members "status", "remarks", "links", "port43", "sponsoredBy", o ipAddresses -- an object containing the following members:
"resoldBy", "registrationBy", "registrationDate", "lastChangedDate",
and "lastChangedBy" take the same form of the members of the same
name of the entity object (Section 7).
9. The Domain Object Class * v6 -- an array of strings containing IPv6 addresses of the
nameserver
* v4 -- an array of strings containing IPv4 addresses of the
nameserver
o status - see Section 5.6
o remarks - see Section 5.3
o links - see Section 5.2
o port43 - see Section 5.7
o events - see Section 5.5
6.3. The Domain Object Class
The domain object class represents a DNS name and point of The domain object class represents a DNS name and point of
delegation. For RIRs these delegation points are in the reverse DNS delegation. For RIRs these delegation points are in the reverse DNS
tree, whereas for DNRs these delegation points are in the forward DNS tree, whereas for DNRs these delegation points are in the forward DNS
tree. The RIR domain object class is a subset of the DNR object tree.
class.
In both cases, the high level structure of the domain object class In both cases, the high level structure of the domain object class
consists of information about the domain registration, nameserver consists of information about the domain registration, nameserver
information related to the domain name, and entities related to the information related to the domain name, and entities related to the
domain name (e.g. registrant information, contacts, etc...). domain name (e.g. registrant information, contacts, etc.).
The following is an elided example of the domain object showing the The following is an elided example of the domain object showing the
high level structure. high level structure:
{ {
"handle" : "XXX", "handle" : "XXX",
"name" : "blah.example.com", "ldhName" : "blah.example.com",
... ...
"nameServers" : "nameServers" :
[ [
... ...
], ],
... ...
"entities" : "entities" :
[ [
... ...
] ]
} }
9.1. The RIR Domain Object Class The following is a description of the members of this object:
The following is an example of a JSON object representing a reverse o handle -- a string representing a registry unique identifier of
DNS delegation point or the RIR domain object class. the domain object instance
o ldhName -- a string describing an domain name in LDH form as
described in Section 4
o unicodeName -- a string containing a domain name with u-labels as
described in Section 4
o variants -- an array of objects, each containing the following
values:
* relation -- an array of strings, with each string denoting the
relationship between the variants and the containing domain
object (see Appendix A.4 for a list of suggested variant
relations).
* variantNames -- an array of objects, with each object
containing an "ldhName" member and a "unicodeName" member (see
Section 4).
o nameservers -- an array of nameserver objects as defined by
Section 6.2
o delegationKeys -- an array of objects, each with the following
members:
* algorithm -- an integer as specified by the algorithm field of
a DNS DS record as specified by RFC 4034 [RFC4034] in
presentation format
* digest -- an string as specified by the digest field of a DNS
DS record as specified by RFC 4034 in presentation format
* digestType -- an integer as specified by the digest type field
of a DNS DS record as specified by RFC 4034 in presentation
format
* keyTag -- an integer as specified by the key tag field of a DNS
DS record as specified by RFC 4034 in presentation format
o entities -- an array of entity objects as defined by Section 6.1.
o status - see Section 5.6
o remarks - see Section 5.3
o links - see Section 5.2
o port43 - see Section 5.7
o events - see Section 5.5
The following is an example of a JSON domain object representing a
reverse DNS delegation point that might be served by an RIR:
{ {
"handle" : "XXXX", "handle" : "XXXX",
"name" : "192.in-addr.arpa", "ldhName" : "192.in-addr.arpa",
"nameServers" : "nameServers" :
[ [
{ "name" : "ns1.rir.net" }, { "ldhName" : "ns1.rir.example" },
{ "name" : "ns2.rir.net" } { "ldhName" : "ns2.rir.example" }
], ],
"delegationKeys" : "delegationKeys" :
[ [
{ {
"algorithm": 7, "algorithm": 7,
"digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C", "digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C",
"digestType" : 1, "digestType" : 1,
"keyTag" : 53814 "keyTag" : 53814
} }
], ],
"remarks" : "remarks" :
[ [
skipping to change at page 22, line 15 skipping to change at page 22, line 28
[ [
{ {
"algorithm": 7, "algorithm": 7,
"digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C", "digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C",
"digestType" : 1, "digestType" : 1,
"keyTag" : 53814 "keyTag" : 53814
} }
], ],
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value": "http://example.net/domain/XXXX", "value": "http://example.net/domain/XXXX",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/domain/XXXXX" "href" : "http://example.net/domain/XXXXX"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"lastChangedDate" : "1990-12-31T23:59:60Z", [
"lastChangedBy" : "joe@bob.com", {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
}
],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"entityNames": [ "Joe Bob, Inc.", "Bobby Joe Shopping" ], "vCard" :
"roles" : [ "registrant" ],
"postalAddress" :
[ [
"123 Maple Ave", [ "version", {}, "text", "4.0" ],
"Suite 90001", [ "fn", {}, "text", "Joe Bob, Inc." ],
"Vancouver", [ "fn", {}, "text", "Bobby Joe Shopping" ],
"BC", [ "label", {}, "text", "123 Maple Ave\n",
"12393" "Suite 90001\n",
], "Vancouver\n",
"emails" : [ "joe@bob.com", "bob@joe.com" ], "BC\n",
"phones" : "1239\n" ],
{ [ "email", {}, "text", "joe at bob.com" ],
"office" : [ "1-958-555-4321", "1-958-555-4322" ], [ "email", {}, "text", "bob at joe.com" ],
"fax" : [ "1-958-555-4323" ], [ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
"mobile" : [ "1-958-555-4324" ] [ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
}, [ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
],
"roles" : [ "registrant" ],
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value": "http://example.net/entity/xxxx", "value": "http://example.net/entity/xxxx",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/entity/xxxx" "href" : "http://example.net/entity/xxxx"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"lastChangedDate" : "1990-12-31T23:59:60Z", [
"lastChangedBy" : "joe@bob.com" {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
}
]
} }
] ]
} }
The following is a description of the members of this object: The following is an example of a JSON domain object representing a
forward DNS delegation point that might be served by a DNR:
o handle -- a string representing a registry unique identifier of
the domain object instance
o name -- a string denoting the DNS zone name, which is a domain
name
o nameservers -- an array of nameserver objects as defined by
Section 8
o delegationKeys -- an array of objects, each with the following
members:
* algorithm -- an integer as specified by the algorithm field of
a DNS DS record as specified by RFC 4034 [RFC4034] in
presentation format
* digest -- an string as specified by the digest field of a DNS
DS record as specified by RFC 4034 in presentation format
* digestType -- an integer as specified by the digest type field
of a DNS DS record as specified by RFC 4034 in presentation
format
* keyTag -- an integer as specified by the key tag field of a DNS
DS record as specified by RFC 4034 in presentation format
o entities -- an array of entity objects as defined by Section 7.1.
The members "remarks", "links", "registrationDate",
"lastChangedDate", and "lastChangedBy" take the same form of the
members of the same name of the entity object (Section 7).
9.2. The DNR Domain Object Class
The DNR domain object class is a superset of the RIR domain object
class (Section 9.1) and has the following additional members.
o variants -- an array of objects, each containing the following
values:
* relation -- an array of strings, with each string denoting the
relationship between the variants and the containing domain
object.
* variantNames -- an array of strings, each being a variant
domain of the containing domain object.
o expirationDate -- a string containing the date and time this
domain name registration will expire
o registrationBy -- a string containing an identifier of the party
responsible for the registration of the domain name
o sponsoredBy -- a string containing an identifier of the party
through which the registration was made, such as an IANA approved
registrar
o resoldBy -- a string containing an identifier of the party
originating the registration of the domain name
o status -- an array of strings indicating the state of the domain
name
o transferDate -- a string containing the date and time this domain
name was transferred
o port43 -- a string containing the fully-qualified host name of the
WHOIS [RFC3912] server where the object instance may be found.
The following is an example of a JSON object representing a forward
DNS delegation point or the DNR domain object class.
{ {
"handle" : "XXXX", "handle" : "XXXX",
"name" : "blah.example.com", "ldhName" : "xn--fo-5ja.example",
"unicodeName" : "foo.example",
"variants" : "variants" :
[ [
{ {
"relation" : [ "registered", "conjoined" ], "relation" : [ "registered", "conjoined" ],
"variantNames" : [ "blah2.example.com", "blah3.example.com" ] "variantNames" :
[
{
"ldhName" : "xn--fo-cka.example",
"unicodeName" : "foo.example"
},
{
"ldhName" : "xn--fo-fka.example",
"unicodeName" : "foeo.example"
}
]
}, },
{ {
"relation" : [ "unregistered", "restrictedRegistration" ], "relation" : [ "unregistered", "restricted registration" ],
"variantNames" : [ "blah3.example.com", "blah4.example.com" ] "variantNames" :
[
{
"ldhName": "xn--fo-8ja.example",
"unicodeName" : "foo.example"
}
]
} }
], ],
"status" : [ "locked", "transferProhibited" ], "status" : [ "locked", "transferProhibited" ],
"nameServers" : "nameServers" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"name" : "ns1.example.com", "ldhName" : "ns1.example.com",
"status" : [ "active" ], "status" : [ "active" ],
"ipAddresses" : "ipAddresses" :
[ {
"2001:db8::123", "2001:db8::124", "v6": [ "2001:db8::123", "2001:db8::124" ],
"192.0.2.1", "192.0.2.2" "v4": [ "192.0.2.1", "192.0.2.2" ]
], },
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/nameserver/XXXX". "value" : "http://example.net/nameserver/XXXX",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/nameserver/XXXX" "href" : "http://example.net/nameserver/XXXX"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"registrationBy" : "ABC123", [
"lastChangedDate" : "1990-12-31T23:59:60Z", {
"lastChangedBy" : "ABC123", "eventAction" : "registration",
"sponsoredBy" : "SponsorXYZ", "eventDate" : "1990-12-31T23:59:60Z"
"resoldBy" : "ResellerPDQ" },
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
}, },
{ {
"handle" : "XXXX", "handle" : "XXXX",
"name" : "ns2.example.com", "ldhName" : "ns2.example.com",
"status" : [ "active" ], "status" : [ "active" ],
"ipAddresses" : "ipAddresses" :
[ {
"2001:db8::125", "2001:db8::126", "v6" : [ "2001:db8::125", "2001:db8::126" ],
"192.0.2.3", "192.0.2.4" "v4" : [ "192.0.2.3", "192.0.2.4" ]
], },
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/nameserver/XXXX", "value" : "http://example.net/nameserver/XXXX",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/nameserver/XXXX" "href" : "http://example.net/nameserver/XXXX"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"registrationBy" : "ABC123", [
"lastChangedDate" : "1990-12-31T23:59:60Z", {
"lastChangedBy" : "ABC123", "eventAction" : "registration",
"sponsoredBy" : "SponsorXYZ", "eventDate" : "1990-12-31T23:59:60Z"
"resoldBy" : "ResellerPDQ" },
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
} }
], ],
"delegationKeys" : "delegationKeys" :
[ [
{ {
"algorithm": 7, "algorithm": 7,
"digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C", "digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C",
"digestType" : 1, "digestType" : 1,
"keyTag" : 53814 "keyTag" : 53814
} }
], ],
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value": "http://example.net/domain/XXXX", "value": "http://example.net/domain/XXXX",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/domain/XXXX" "href" : "http://example.net/domain/XXXX"
} }
], ],
"port43" : "whois.example.net", "port43" : "whois.example.net",
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"registrationBy" : "ABC123", [
"lastChangedDate" : "1990-12-31T23:59:60Z", {
"lastChangedBy" : "ABC123", "eventAction" : "registration",
"sponsoredBy" : "SponsorXYZ", "eventDate" : "1990-12-31T23:59:60Z"
"resoldBy" : "ResellerPDQ", },
"expirationDate" : "2016-12-31T23:59:60Z", {
"transferDate" : "1990-12-31T23:59:60Z", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
},
{
"eventAction" : "transfer",
"eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
},
{
"eventAction" : "expiration",
"eventDate" : "2016-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
}
],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"entityNames": [ "Joe Bob, Inc.", "Bobby Joe Shopping" ], "vCard" :
"status" : [ "validated", "locked" ],
"postalAddress" :
[ [
"123 Maple Ave", [ "version", {}, "text", "4.0" ],
"Suite 90001", [ "fn", {}, "text", "Joe Bob, Inc." ],
"Vancouver", [ "fn", {}, "text", "Bobby Joe Shopping" ],
"BC", [ "label", {}, "text", "123 Maple Ave\n",
"12393" "Suite 90001\n",
"Vancouver\n",
"BC\n",
"1239\n" ],
[ "email", {}, "text", "joe at bob.com" ],
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
], ],
"emails" : [ "joe@bob.com", "bob@joe.com" ], "status" : [ "validated", "locked" ],
"phones" : "roles" : [ "registrant" ],
{
"office" : [ "1-958-555-4321", "1-958-555-4322" ],
"fax" : [ "1-958-555-4323" ],
"mobile" : [ "1-958-555-4324" ]
},
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/entity/xxxx", "value" : "http://example.net/entity/xxxx",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/entity/xxxx" "href" : "http://example.net/entity/xxxx"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"registrationBy" : "ABC123", [
"lastChangedDate" : "1990-12-31T23:59:60Z", {
"lastChangedBy" : "ABC123", "eventAction" : "registration",
"sponsoredBy" : "SponsorXYZ", "eventDate" : "1990-12-31T23:59:60Z"
"resoldBy" : "ResellerPDQ" },
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
} }
] ]
} }
10. The IP Network Object Class 6.4. The IP Network Object Class
The IP Network object class models IP network registrations found in The IP Network object class models IP network registrations found in
RIRs and is the expected response for the /ip query as defined by RIRs and is the expected response for the "/ip" query as defined by
[I-D.ietf-weirds-rdap-query]. There is no equivalent object class [I-D.ietf-weirds-rdap-query]. There is no equivalent object class
for DNRs. The high level structure of the IP network object class for DNRs. The high level structure of the IP network object class
consists of information about the network registration and entities consists of information about the network registration and entities
related to the IP network (e.g. registrant information, contacts, related to the IP network (e.g. registrant information, contacts,
etc...). etc...).
The following is an elided example of the IP network object type The following is an elided example of the IP network object type
showing the high level structure. showing the high level structure:
{ {
"handle" : "XXX", "handle" : "XXX",
... ...
"entities" : "entities" :
[ [
... ...
] ]
} }
The following is an example of the JSON object for the network The following is an example of the JSON object for the network
registration information registration information
{ {
"handle" : "XXXX-RIR", "handle" : "XXXX-RIR",
"startAddress" : "2001:db8::0", "startAddress" : "2001:db8::0",
"endAddress" : "2001:db8::0:FFFF:FFFF:FFFF:FFFF:FFFF", "endAddress" : "2001:db8::0:FFFF:FFFF:FFFF:FFFF:FFFF",
"ipVersion" : 6, "ipVersion" : "v6",
"name": "NET-RTR-1", "name": "NET-RTR-1",
"description" : [ "A network used for routing" ], "description" : [ "A network used for routing" ],
"type" : "DIRECT ALLOCATION", "type" : "DIRECT ALLOCATION",
"country" : "AU", "country" : "AU",
"parentHandle" : "YYYY-RIR", "parentHandle" : "YYYY-RIR",
"status" : [ "allocated" ], "status" : [ "allocated" ],
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.ent/ip/2001:db8::/48", "value" : "http://example.ent/ip/2001:db8::/48",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/ip/2001:db8::/48" "href" : "http://example.net/ip/2001:db8::/48"
}, },
{ {
"value" : "http://example.net/ip/2001:db8::/48", "value" : "http://example.net/ip/2001:db8::/48",
"rel" : "up", "rel" : "up",
"href" : "http://example.net/ip/2001:C00::/23" "href" : "http://example.net/ip/2001:C00::/23"
} }
], ],
"registrationDate" : "20110509", "events" :
"lastChangedDate" : "20110509", [
"lastChangedBy" : "joe@bob.com", {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"entityNames": [ "Joe Bob, Inc.", "Bobby Joe Shopping" ], "vCard" :
"roles" : [ "registrant" ],
"postalAddress" :
[ [
"123 Maple Ave", [ "version", {}, "text", "4.0" ],
"Suite 90001", [ "fn", {}, "text", "Joe Bob, Inc." ],
"Vancouver", [ "fn", {}, "text", "Bobby Joe Shopping" ],
"BC", [ "label", {}, "text", "123 Maple Ave\n",
"12393" "Suite 90001\n",
"Vancouver\n",
"BC\n",
"1239\n" ],
[ "email", {}, "text", "joe at bob.com" ],
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
], ],
"emails" : [ "joe@bob.com", "bob@joe.com" ], "roles" : [ "registrant" ],
"phones" :
{
"office" : [ "1-958-555-4321", "1-958-555-4322" ],
"fax" : [ "1-958-555-4323" ],
"mobile" : [ "1-958-555-4324" ]
},
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/entity/xxxx", "value" : "http://example.net/entity/xxxx",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/entity/xxxx" "href" : "http://example.net/entity/xxxx"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"lastChangedDate" : "1990-12-31T23:59:60Z", [
"lastChangedBy" : "joe@bob.com" {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
} }
] ]
} }
The following is a description of the members of this object: The following is a description of the members of this object:
o handle -- a string representing an RIR unique identifier of the o handle -- a string representing an RIR unique identifier of the
network registration network registration
o startAddress -- the starting IP address of the network, either o startAddress -- the starting IP address of the network, either
IPv4 or IPv6 IPv4 or IPv6
o endAddress -- the ending IP address of the network, either IPv4 or o endAddress -- the ending IP address of the network, either IPv4 or
IPv6 IPv6
o ipVersion -- an integer signifying the IP protocol version of the o ipVersion -- an string signifying the IP protocol version of the
network: 4 signifying an IPv4 network, 6 signifying an IPv6 network: "v4" signifying an IPv4 network, "v6" signifying an IPv6
network network
o name -- an identifier assigned to the network registration by the o name -- an identifier assigned to the network registration by the
registration holder registration holder
o description -- an array of strings containing descriptive text o description -- an array of strings containing descriptive text
about the network registration about the network registration
o type -- a string containing an RIR specific classification of the o type -- a string containing an RIR-specific classification of the
network network
o country -- a string containing the name of the 2 character country o country -- a string containing the name of the 2 character country
code of the network code of the network
o parentHandle -- a string containing an RIR unique identifier of o parentHandle -- a string containing an RIR-unique identifier of
the parent network of this network registration the parent network of this network registration
o status -- an array of strings indicating the state of the IP o status -- an array of strings indicating the state of the IP
network network
o entities -- an array of entity objects as defined by Section 7.1. o entities -- an array of entity objects as defined by Section 6.1.
The members "remarks", "links", "registrationDate", o remarks - see Section 5.3
"lastChangedDate", and "lastChangedBy" take the same form of the
members of the same name of the entity object (Section 7.1).
11. Autonomous System Number Entity Object Class o links - see Section 5.2
o events - see Section 5.5
6.5. Autonomous System Number Entity Object Class
The Autonomous System Number (autnum) object class models Autonomous The Autonomous System Number (autnum) object class models Autonomous
System Number registrations found in RIRs and represents the expected System Number registrations found in RIRs and represents the expected
response to an /autnum query as defined by response to an "/autnum" query as defined by
[I-D.ietf-weirds-rdap-query]. There is no equivalent object class [I-D.ietf-weirds-rdap-query]. There is no equivalent object class
for DNRs. The high level structure of the autnum object class for DNRs. The high level structure of the autnum object class
consists of information about the network registration and entities consists of information about the network registration and entities
related to the autnum registration (e.g. registrant information, related to the autnum registration (e.g. registrant information,
contacts, etc...), and is similar to the IP Network entity object contacts, etc.), and is similar to the IP Network entity object
class. class.
The following is an example of a JSON object representing an autnum. The following is an example of a JSON object representing an autnum.
{ {
"handle" : "XXXX-RIR", "handle" : "XXXX-RIR",
"startAutnum" : "10", "startAutnum" : "10",
"endAutnum" : "15", "endAutnum" : "15",
"name": "AS-RTR-1", "name": "AS-RTR-1",
"description" : [ "AS for Exchange" ], "description" : [ "AS for Exchange" ],
"type" : "DIRECT ALLOCATION", "type" : "DIRECT ALLOCATION",
"country": "AU", "country": "AU",
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/autnum/xxxx", "value" : "http://example.net/autnum/xxxx",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/autnum/xxxx" "href" : "http://example.net/autnum/xxxx"
} }
], ],
"registrationDate" : "20110509", "events" :
"lastChangedDate" : "20110509", [
"lastChangedBy" : "joe@bob.com", {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"entityNames": [ "Joe Bob, Inc.", "Bobby Joe Shopping" ], "vCard" :
"roles" : [ "registrant" ],
"postalAddress" :
[ [
"123 Maple Ave", [ "version", {}, "text", "4.0" ],
"Suite 90001", [ "fn", {}, "text", "Joe Bob, Inc." ],
"Vancouver", [ "fn", {}, "text", "Bobby Joe Shopping" ],
"BC", [ "label", {}, "text", "123 Maple Ave\n",
"12393" "Suite 90001\n",
"Vancouver\n",
"BC\n",
"1239\n" ],
[ "email", {}, "text", "joe at bob.com" ],
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
], ],
"emails" : [ "joe@bob.com", "bob@joe.com" ], "roles" : [ "registrant" ],
"phones" :
{
"office" : [ "1-958-555-4321", "1-958-555-4322" ],
"fax" : [ "1-958-555-4323" ],
"mobile" : [ "1-958-555-4324" ]
},
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/entity/XXXX", "value" : "http://example.net/entity/XXXX",
"rel" : "self", "rel" : "self",
"href" : "http://example.net/entity/XXXX" "href" : "http://example.net/entity/XXXX"
} }
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"lastChangedDate" : "1990-12-31T23:59:60Z", [
"lastChangedBy" : "joe@bob.com" {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
} }
] ]
} }
The following is a description of the members of this object: The following is a description of the members of this object:
o handle -- a string representing an RIR unique identifier of the o handle -- a string representing an RIR-unique identifier of the
autnum registration autnum registration
o startAutnum -- the starting number [RFC5396] in the block of o startAutnum -- the starting number [RFC5396] in the block of
autonomous system numbers autonomous system numbers
o endAutnum -- the ending number [RFC5396] in the block of o endAutnum -- the ending number [RFC5396] in the block of
autonomous system numbers autonomous system numbers
o name -- an identifier assigned to the autnum registration by the o name -- an identifier assigned to the autnum registration by the
registration holder registration holder
o description -- an array of strings containing descriptive text o description -- an array of strings containing descriptive text
about the autnum registration about the autnum registration
o type -- a string containing an RIR specific classification of the o type -- a string containing an RIR-specific classification of the
autnum autnum
o country -- a string containing the name of the 2 character country o country -- a string containing the name of the 2 character country
code of the autnum code of the autnum
The members "remarks", "links", "registrationDate", o remarks - see Section 5.3
"lastChangedDate", and "lastChangedBy" take the same form of the
members of the same name of the entity object (Section 7.1).
12. Error Response Body o links - see Section 5.2
o events - see Section 5.5
7. Error Response Body
Some non-answer responses may return entity bodies with information Some non-answer responses may return entity bodies with information
that could be more descriptive. that could be more descriptive.
The basic structure of that response is an object class containing an The basic structure of that response is an object class containing an
error code number (corresponding to the HTTP response code) followed error code number (corresponding to the HTTP response code) followed
by a string named "title" followed by an array of strings named by a string named "title" followed by an array of strings named
"description". "description".
This is an example of the JSON version of the common response body. This is an example of the JSON version of the common response body:
{ {
"errorCode": 418, "errorCode": 418,
"title": "Your beverage choice is not available", "title": "Your beverage choice is not available",
"description": "description":
[ [
"I know coffee has more ummppphhh.", "I know coffee has more ummppphhh.",
"But I cannot provide." "But I cannot provide."
] ]
} }
Figure 12 Figure 14
A client MAY simply use the HTTP response code as the server is not A client MAY simply use the HTTP response code as the server is not
required to include error data in the response body. However, if a required to include error data in the response body. However, if a
client wishes to parse the error data, it SHOULD first check that the client wishes to parse the error data, it SHOULD first check that the
Content-Type header contains the appropriate media type. Content-Type header contains the appropriate media type.
13. IANA Considerations 8. IANA Considerations
This specification registers the "application/rdap" media type.
Type name: application
Subtype name: rdap
Required parameters: n/a
Encoding considerations: n/a
Security considerations: n/a
Interoperability considerations: n/a
Published specification: [[ this document ]]
Applications that use this media type: RDAP
Additional information: n/a
Person & email address to contact for further information: Andy
Newton &andy@hxr.us&
Intended usage: COMMON
Restrictions on usage: none None.
Author: Andy Newton 9. Security Considerations
Change controller: IETF This specification models information serialized in JSON format. As
JSON is a subset of Javascript, implementations are advised to follow
the security considerations outlined in Section 6 of [RFC4627] to
prevent code injection.
14. Internationalization Considerations 10. Internationalization Considerations
14.1. Character Encoding 10.1. Character Encoding
The default text encoding for JSON and XML responses in RDAP is The default text encoding for JSON and XML responses in RDAP is
UTF-8, and all servers and clients MUST support UTF-8. Servers and UTF-8, and all servers and clients MUST support UTF-8. Servers and
clients MAY optionally support other character encodings. clients MAY optionally support other character encodings.
14.2. URIs and IRIs 10.2. URIs and IRIs
[I-D.ietf-weirds-using-http] defines the use of URIs and IRIs in [I-D.ietf-weirds-using-http] defines the use of URIs and IRIs in
RDAP. RDAP.
14.3. Language Tags 10.3. Language Tags
Section 5.3 defines the use of language tags in the JSON responses Section 5.4 defines the use of language tags in the JSON responses
defined in this document. defined in this document.
14.4. Internationalized Domain Names 10.4. Internationalized Domain Names
Appendix C illustrates the model for query and response regarding Internationalized Domain Names (IDNs) are denoted in this
internationalized domain names (IDNs). specification by the separation of DNS names in LDH form and Unicode
form (see Section 4). Representation of IDNs in registries is
described by the "variants" object in Section 6.3 and the suggested
values listed in Appendix A.4.
15. Contributing Authors and Acknowledgements 11. Privacy Considerations
This specification suggests status values to denote contact and
registrant information that has been marked as private and/or has
been redacted or obscured. See Appendix A.1 for the list of status
values. See Appendix B.1 on guidance to apply those values to
contacts and registrants.
This document is derived from original work on RIR response in JSON 12. Contributing Authors and Acknowledgements
by Byron J. Ellacott of APNIC, Arturo L. Servin of LACNIC, Kaveh
Ranjbar of the RIPE NCC, and Andrew L. Newton of ARIN. Additionally, This document is derived from original work on RIR responses in JSON
this document incorporates word on DNR responses in JSON by Ning by Byron J. Ellacott, Arturo L. Servin, Kaveh Ranjbar, and Andrew
Kong, Linlin Zhou, Jiagui Xie, and Sean Shen of CNNIC. L. Newton. Additionally, this document incorporates word on DNR
responses in JSON by Ning Kong, Linlin Zhou, Jiagui Xie, and Sean
Shen.
The components of the DNR object classes are derived from a The components of the DNR object classes are derived from a
categorization of WHOIS response formats created by Ning Kong, Linlin categorization of WHOIS response formats created by Ning Kong, Linlin
Zhou, and Guangqing Deng of CNNIC, Steve Sheng and Francisco Arias of Zhou, and Guangqing Deng, Steve Sheng and Francisco Arias, Ray
ICANN, Ray Bellis of Nominet, and Frederico Neves of NIC.BR. Bellis, and Frederico Neves.
Ed Lewis of Neustar contributed significant review comments and Ed Lewis contributed significant review comments and provided
provided clarifying text. clarifying text. James Mitchel provided text regarding the
processing of unknown JSON attributes and identified issues leading
to the remodeling of events. Ernie Dainow and Francisco Obispo
provided concrete suggestions that led to a better variant model for
domain names.
16. References The switch to and incorporation of JSON vCard was performed by Simon
Perreault.
16.1. Normative References 13. References
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 13.1. Normative References
September 1981.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981.
[RFC1166] Kirkpatrick, S., Stahl, M., and M. Recker, "Internet [RFC1166] Kirkpatrick, S., Stahl, M., and M. Recker, "Internet
numbers", RFC 1166, July 1990. numbers", RFC 1166, July 1990.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the [RFC3339] Klyne, G., Ed. and C. Newman, "Date and Time on the
Internet: Timestamps", RFC 3339, July 2002. Internet: Timestamps", RFC 3339, July 2002.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66, RFC
RFC 3986, January 2005. 3986, January 2005.
[RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S. [RFC4034] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Resource Records for the DNS Security Extensions", Rose, "Resource Records for the DNS Security Extensions",
RFC 4034, March 2005. RFC 4034, March 2005.
[RFC4343] Eastlake, D., "Domain Name System (DNS) Case Insensitivity [RFC4343] Eastlake, D., "Domain Name System (DNS) Case Insensitivity
Clarification", RFC 4343, January 2006. Clarification", RFC 4343, January 2006.
[RFC4627] Crockford, D., "The application/json Media Type for [RFC4627] Crockford, D., "The application/json Media Type for
JavaScript Object Notation (JSON)", RFC 4627, July 2006. JavaScript Object Notation (JSON)", RFC 4627, July 2006.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
October 2008. October 2008.
[RFC5396] Huston, G. and G. Michaelson, "Textual Representation of [RFC5396] Huston, G. and G. Michaelson, "Textual Representation of
Autonomous System (AS) Numbers", RFC 5396, December 2008. Autonomous System (AS) Numbers", RFC 5396, December 2008.
[RFC5646] Phillips, A. and M. Davis, "Tags for Identifying [RFC5646] Phillips, A. and M. Davis, "Tags for Identifying
Languages", BCP 47, RFC 5646, September 2009. Languages", BCP 47, RFC 5646, September 2009.
[RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework",
RFC 5890, August 2010.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952, August 2010. Address Text Representation", RFC 5952, August 2010.
[RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010. [RFC5988] Nottingham, M., "Web Linking", RFC 5988, October 2010.
[I-D.kewisch-vcard-in-json]
Kewisch, P., "jCard: The JSON format for vCard", draft-
kewisch-vcard-in-json-01 (work in progress), March 2013.
[ISO.3166.1988] [ISO.3166.1988]
International Organization for Standardization, "Codes for International Organization for Standardization, "Codes for
the representation of names of countries, 3rd edition", the representation of names of countries, 3rd edition",
ISO Standard 3166, August 1988. ISO Standard 3166, August 1988.
[I-D.ietf-weirds-rdap-query] [I-D.ietf-weirds-rdap-query]
Newton, A. and S. Hollenbeck, "RDAP Query Format", Newton, A. and S. Hollenbeck, "RDAP Query Format", draft-
draft-ietf-weirds-rdap-query-00 (work in progress), ietf-weirds-rdap-query-00 (work in progress), September
September 2011. 2011.
[I-D.ietf-weirds-using-http] [I-D.ietf-weirds-using-http]
Newton, A., Ellacott, B., and N. Kong, "Using HTTP for Newton, A., Ellacott, B., and N. Kong, "Using HTTP for
RESTful Whois Services by Internet Registries", RESTful Whois Services by Internet Registries", draft-
draft-ietf-weirds-using-http-01 (work in progress), ietf-weirds-using-http-01 (work in progress), May 2012.
May 2012.
[E164] ITU-T, "The International Public Telecommunication Number
Plan", Recommendation E.164, May 1997.
16.2. Informative References 13.2. Informative References
[RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912, [RFC3912] Daigle, L., "WHOIS Protocol Specification", RFC 3912,
September 2004. September 2004.
[RFC3730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)", [RFC3730] Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
RFC 3730, March 2004. RFC 3730, March 2004.
[JSON_acendancy] [JSON_acendancy]
MacVittie, "The Stealthy Ascendancy of JSON", 04 2011. MacVittie, , "The Stealthy Ascendancy of JSON", 04 2011.
[JSON_performance_study] [JSON_performance_study]
Montana State University - Bozeman, Montana State Montana State University - Bozeman, Montana State
University - Bozeman, Montana State University - Bozeman, University - Bozeman, Montana State University - Bozeman,
and Montana State University - Bozeman, "Comparison of Montana State University - Bozeman, "Comparison of JSON
JSON and XML Data Interchange Formats: A Case Study", and XML Data Interchange Formats: A Case Study", 2009.
2009.
Appendix A. Suggested Values Appendix A. Suggested Values
Due to the wide variation between the hundreds of registry operators Due to the wide variation between the hundreds of registry operators
and the on-going policy refinement by registry communities, values of and the on-going policy refinement by registry communities, values of
some data cannot be formally standardized. This section lists some data cannot be formally standardized. This section lists
suggested values for such data but is not nor will ever be a complete suggested values for such data but is not nor will ever be a complete
list of values and their meanings. list of values and their meanings.
A.1. Status A.1. Status
skipping to change at page 41, line 36 skipping to change at page 40, line 9
forbidden. forbidden.
o 'transfer prohibited' -- Transfers of the registration from one o 'transfer prohibited' -- Transfers of the registration from one
registrar to another are forbidden. This type of status normally registrar to another are forbidden. This type of status normally
applies to DNR domain names. applies to DNR domain names.
o 'delete prohibited' -- Deletion of the registration of the object o 'delete prohibited' -- Deletion of the registration of the object
instance is forbidden. This type of status normally applies to instance is forbidden. This type of status normally applies to
DNR domain names. DNR domain names.
A.2. Roles o 'proxy' -- The registration of the object instance has been
performed by a third party. This is most commonly applied to
entities.
o 'private' -- The information of the object instance is not
designated for public consumption. This is most commonly applied
to entities.
o 'redacted' -- Some of the information of the object instance has
not been made available. This is most commonly applied to
entities.
o 'obscured' -- Some of the information of the object instance has
been altered for the purposes of not readily revealing the actual
information of the object instance. This is most commonly applied
to entities.
A.2. Event Actions
Section 5.5 describes a data structure for denoting events against
object classes. Each event can have an event action, which is a
string. The following is a list of suggested values to use for event
actions:
o 'registration' -- the object instance was initially registered
o 'reregistration' -- the object instance was registered
subsequently to initial registration
o 'last changed' -- when the information in the object instance was
last changed
o 'expiration' -- the object instance has been removed or will be
removed at a pre-determined date and time from the registry
o 'deletion' -- the object instance was removed from the registry at
a point in time that was not pre-determined
o 'reinstantation' -- the object instance was reregistered after
having been removed from the registry
o 'transfer' -- the object instance was transfered from one
registrant to another
A.3. Roles
Entity object classes have a member named 'roles'. This member is an Entity object classes have a member named 'roles'. This member is an
array of strings, with each string indicating the role or array of strings, with each string indicating the role or
relationship the entity object instance has with a containing object, relationship the entity object instance has with a containing object,
such as a domain name or IP network. An entity object instance can such as a domain name or IP network. An entity object instance can
have more than one type of relationship with a containing object. have more than one type of relationship with a containing object.
The following is a list of suggested values to use in the 'roles' The following is a list of suggested values to use in the 'roles'
array: array:
o 'registrant' -- The entity object instance is the registrant of o 'registrant' -- The entity object instance is the registrant of
skipping to change at page 42, line 17 skipping to change at page 41, line 33
o 'abuse' -- The entity object instance handles network abuse issues o 'abuse' -- The entity object instance handles network abuse issues
on behalf of the registrant of the registration. on behalf of the registrant of the registration.
o 'billing' -- The entity object instance handles payment and o 'billing' -- The entity object instance handles payment and
billing issues on behalf of the registrant of the registration. billing issues on behalf of the registrant of the registration.
o 'registrar' -- The entity object instance represents the authority o 'registrar' -- The entity object instance represents the authority
responsible for the registration in the registry. responsible for the registration in the registry.
A.3. Variant Relations o 'reseller' -- The entity object instance represents a third party
through which the registration was conducted (i.e. not the
registry or registrar).
Section 9.2 describes a structure for noting variants of domain names o 'sponsor' -- The entity object instance represents a domain policy
sponsor, such as an ICANN approved sponsor
A.4. Variant Relations
Section 6.3 describes a structure for noting variants of domain names
and the relationship those variants have with a registered domain and the relationship those variants have with a registered domain
name. The following is a list of suggested values to use as the name. The following is a list of suggested values to use as the
variant relation values: variant relation values:
o 'registered' -- the variant names are registered in the registry. o 'registered' -- the variant names are registered in the registry.
o 'unregistered' -- the variant names are not found in the registry. o 'unregistered' -- the variant names are not found in the registry.
o 'restrictedRegistration' -- registration of the variant names is o 'restricted registration' -- registration of the variant names is
restricted to certain parties or within certain rules. restricted to certain parties or within certain rules.
o 'openRegistration' -- registration of the variant names is o 'open registration' -- registration of the variant names is
available to generally qualified registrants. available to generally qualified registrants.
o 'conjoined' -- registration of the variant names is conjoined with o 'conjoined' -- registration of the variant names is occurs
the registration of the containing domain registration. automatically with the registration of the containing domain
registration.
Appendix B. Suggested Data Modeling with the Entity Object Class Appendix B. Suggested Data Modeling with the Entity Object Class
B.1. Registrants and Contacts B.1. Registrants and Contacts
This document does not provide specific object classes for This document does not provide specific object classes for
registrants and contacts. Instead the entity object class may be registrants and contacts. Instead the entity object class may be
used to represent a registrant or contact. When the entity object is used to represent a registrant or contact. When the entity object is
embedded inside a containing object such as a domain name or IP embedded inside a containing object such as a domain name or IP
network, the 'roles' string array can be used to signify the network, the 'roles' string array can be used to signify the
relationship. It is recommended that the values from Appendix A.2 be relationship. It is recommended that the values from Appendix A.3 be
used. used.
The following is an example of an elided containing object with an The following is an example of an elided containing object with an
embedded entity that is both a registrant and admin contact: embedded entity that is both a registrant and admin contact:
{ {
... ...
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"entityNames": [ "Joe Bob, Inc.", "Bobby Joe Shopping" ], "vCard" :
"roles" : [ "registrant", "admin" ],
"postalAddress" :
[ [
"123 Maple Ave", [ "version", {}, "text", "4.0" ],
"Suite 90001", [ "fn", {}, "text", "Joe Bob, Inc." ],
"Vancouver", [ "fn", {}, "text", "Bobby Joe Shopping" ],
"BC", [ "label", {}, "text", "123 Maple Ave\n",
"12393" "Suite 90001\n",
"Vancouver\n",
"BC\n",
"1239\n" ],
[ "email", {}, "text", "joe at bob.com" ],
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
], ],
"emails" : [ "joe@bob.com", "bob@joe.com" ], "roles" : [ "registrant", "admin" ],
"phones" :
{
"office" : [ "1-958-555-4321", "1-958-555-4322" ],
"fax" : [ "1-958-555-4323" ],
"mobile" : [ "1-958-555-4324" ]
},
"remarks" : "remarks" :
[ [
"she sells seas shells", {
"down by the seashore" "description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"registrationDate" : "1990-12-31T23:59:60Z", "events" :
"lastChangedDate" : "1990-12-31T23:59:60Z", [
"lastChangedBy" : "joe@bob.com" {
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z"
}
]
} }
]
}
In many use cases, it is necessary to hide or obscure the information
of a registrant or contact due to policy or other operational
matters. Registries can denote these situations with 'status' values
(see Appendix A.1).
The following is an elided example of a registrant with information
changed to reflect that of a third party.
{
...
"entities" :
[
{
"handle" : "XXXX",
...
"roles" : [ "registrant", "admin" ],
"status" : [ "proxy", "private", "obscured" ]
}
] ]
} }
B.2. Registrars B.2. Registrars
This document does not provide a specific object class for This document does not provide a specific object class for
registrars, but like registrants and contacts (see Appendix B.1) the registrars, but like registrants and contacts (see Appendix B.1) the
'roles' string array maybe used. 'roles' string array maybe used.
The following is an example of an elided containing object with an The following is an example of an elided containing object with an
embedded entity that is a registrar: embedded entity that is a registrar:
{ {
... ...
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"names": [ "RegistrarsRUS" ], "vCard" :
"roles" : [ "registrar" ],
"postalAddress" :
[ [
"1212 Tulip Ave", [ "version", {}, "text", "4.0" ],
"Suite 1", [ "fn", {}, "text", "RegistrarsRUS" ],
"Marina Del Rey", [ "label", {}, "text", "1212 Tulip Ave\n",
"CA", "Suite 1\n",
"12393-2193" "Marina Del Rey\n",
"CA\n",
"12393-2193" ],
[ "email", {}, "text", "joe at bob.com" ],
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ],
], ],
"emails" : [ "joe@bob.com", "bob@joe.com" ], "roles" : [ "registrar" ],
"phones" :
{
"office" : [ "1-958-555-4321", "1-958-555-4322" ],
"fax" : [ "1-958-555-4323" ],
"mobile" : [ "1-958-555-4324" ]
},
"remarks" : "remarks" :
[ [
"we registrar for less!" {
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : "links" :
[ [
{ {
"value" : "http://example.net/entity/XXXX", "value" : "http://example.net/entity/XXXX",
"rel" : "alternate", "rel" : "alternate",
"type" : "text/html", "type" : "text/html",
"href" : "http://www.example.com" "href" : "http://www.example.com"
} }
] ]
} }
] ]
} }
Appendix C. IDN Query and Response Model Appendix C. Modeling Events
Internationalized Domain Names (IDNs) differ from other types of Events represent actions that have taken place against a registered
domain names because multiple domain names as would be represented by object at a certain date and time. Events have three properties: the
a name in Master File format (see [RFC4343]) may be registered by a action, the actor, and the date and time of the event (which is
single IDN. IDNs are based on Unicode, and Unicode can have multiple sometimes in the future). In some cases the identity of the actor is
means for encoding the same word depending on the character set and not captured.
language being used. And the rules for determining which IDN
encoding maps to a "wire-format" domain name vary from DNR to DNR.
When an IDN maps to multiple domain names, the various mappings are Events can be modeled in three ways:
called variants. The DNR Domain object class (Section 9.2)
represents the variants using a string array.
The following is an example of an elided DNR domain object with 1. events with no designated actor
variants.
{ 2. events where the actor is only designated by an identifier
"handle" : "XXXX",
"name" : "blah.example.com",
"variants" : [ "blah2.example.com", "blah3.example.com" ],
...
}
Because IDNs can have multiple targets in a mapping and due to the 3. events where the actor can be modeled as an entity
variance in DNR mapping rules, it is up to the client to reduce an
IDN to a domain name in Master File format so as to narrow the lookup
of the domain name to the proper subset. A query of a DNR using the
IDN itself might map across multiple registrations depending on the
mapping rules of the DNR.
Appendix D. Postal Addresses vs Location For the first use case, the 'events' data structure (Section 5.5) is
used without the 'eventActor' object member.
The postal address data listed in the entity object class (Section 7) This is an example of an "events" array without the 'eventActor'.
does not necessarily represent location. The intent of this
information is to provide a means to send postal mail to an entity.
While in some cases it may also be the location of the entity, there
is no guarantee that the two are the same.
Additionally, the postal address data represented in this document "events" :
does not follow any specific standard for postal addresses because [
many registries do not keep postal address data in an {
internationalized standard form. Publication of such data in a "eventAction" : "registration",
format that suggests an internationalized standard form when such "eventDate" : "1990-12-31T23:59:60Z"
data is not known to be well-formed for that purpose would be }
misleading. ]
Appendix E. Motivations for Using JSON Figure 15
For the second use case, the 'events' data structure (Section 5.5) is
used with the 'eventActor' object member.
This is an example of an "events" array with the 'eventActor'.
"events" :
[
{
"eventAction" : "registration",
"eventActor" : "XYZ-NIC",
"eventDate" : "1990-12-31T23:59:60Z"
}
]
Figure 16
For the third use case, the 'asEventActor' array is used when an
entity (Section 6.1) is embedded into another object class. The
'asEventActor' array follows the same structure as the 'events' array
but does not have 'eventActor' attributes.
The following is an elided example of a domain object with an entity
as an event actor.
{
"handle" : "XXXX",
"ldhName" : "foo.example",
"status" : [ "locked", "transfer Prohibited" ],
...
"entities" :
[
{
"handle" : "XXXX",
...
"asEventActor" :
[
{
"eventAction" : "last changed",
"eventDate" : "1990-12-31T23:59:60Z"
}
]
}
]
}
Appendix D. Motivations for Using JSON
This section addresses a common question regarding the use of JSON This section addresses a common question regarding the use of JSON
over other data formats, most notably XML. over other data formats, most notably XML.
It is often pointed out that many DNRs and one RIR support the EPP It is often pointed out that many DNRs and one RIR support the EPP
[RFC3730] standard, which is an XML serialized protocol. The logic [RFC3730] standard, which is an XML serialized protocol. The logic
is that since EPP is a common protocol in the industry it follows is that since EPP is a common protocol in the industry it follows
that XML would be a more natural choice. While EPP does enfluence that XML would be a more natural choice. While EPP does influence
this specification quite a bit, EPP serves a different purpose which this specification quite a bit, EPP serves a different purpose which
is the provisioning of Internet resources between registries and is the provisioning of Internet resources between registries and
accredited registrars and serves a much narrower audience than that accredited registrars and serves a much narrower audience than that
envisioned for RDAP. envisioned for RDAP.
By contrast, RDAP has a broader audience and is designed for public By contrast, RDAP has a broader audience and is designed for public
consumption of data. Experience from RIRs with first generation consumption of data. Experience from RIRs with first generation
RESTful web services for Whois indicate a large percentage of clients RESTful web services for Whois indicate a large percentage of clients
operate within browsers and other platforms where full-blown XML operate within browsers and other platforms where full-blown XML
stacks are not readily available and where JSON is a better fit. stacks are not readily available and where JSON is a better fit.
Additionally, while EPP is used in much of the DNR community it is Additionally, while EPP is used in much of the DNR community it is
not a unversial constant in that industry. And finally, EPP's use of not a universal constant in that industry. And finally, EPP's use of
XML predates the specification of JSON. If EPP had been defined XML predates the specification of JSON. If EPP had been defined
today, it may very well have used JSON instead of XML. today, it may very well have used JSON instead of XML.
Beyond the specific DNR and RIR communities, the trend in the broader Beyond the specific DNR and RIR communities, the trend in the broader
Internet industry is also switching to JSON over XML, especially in Internet industry is also switching to JSON over XML, especially in
the area of RESTful web services (see [JSON_acendancy]). Studies the area of RESTful web services (see [JSON_acendancy]). Studies
have also found that JSON is generally less bulky and consequently have also found that JSON is generally less bulky and consequently
faster to parse (see [JSON_performance_study]). faster to parse (see [JSON_performance_study]).
Appendix F. Changelog Appendix E. Changelog
Initial -00 Adopted as working group document 2012-September-18. Initial -00 Adopted as working group document 2012-September-18.
-01 -01
Minor spelling corrections. Changed "Registry Data" to Minor spelling corrections. Changed "Registry Data" to
"Registration Data" for the sake of consistency. "Registration Data" for the sake of consistency.
Transitioned to RFC 5988 links and relationshipt types from our Transitioned to RFC 5988 links and relationship types from our
own custom "uris" structure. own custom "uris" structure.
Some examples had 'status' as a string. Those have been Some examples had 'status' as a string. Those have been
corrected as 'status' is always an array of strings. corrected as 'status' is always an array of strings.
Domain variants can now have a multi-valued relationship with Domain variants can now have a multi-valued relationship with
domain registrations. domain registrations.
"names" in the entity object class was changed to "names" in the entity object class was changed to
"entityNames". "entityNames".
skipping to change at page 50, line 5 skipping to change at page 49, line 18
Added 'lang' name/value. Added 'lang' name/value.
Added internationalization considerations section. Added internationalization considerations section.
-02 -02
Removed level from media type registration. Removed level from media type registration.
Textual changes as given by Ed Lewis. Textual changes as given by Ed Lewis.
Fixed objectclass linking example noted by Francisco Obispo Fixed object class linking example noted by Francisco Obispo
Fixed a lot of other examples called out by Alex Sergeyev Fixed a lot of other examples called out by Alex Sergeyev
Added a note that JSON names are case sensitive Added a note that JSON names are case sensitive
Added 'status' to IP networks as suggested by Alex Sergeyev Added 'status' to IP networks as suggested by Alex Sergeyev
-03
Added jCard verbiage and examples and deleted overlapping
contact information and the appendix on postal addresses
Removed the IANA considerations as they have been moved to
another document
Changed the remarks structure to be like notices
Reordering and rewording some of the sections so they flow
better
Added note about object class "self" links
Changed ipAddresses in nameserver object class to separate out
v6 from v4
Changed IP network version identifier from integer to string to
be more consistent with ipAddresses identifier in nameserver
object classes
Changed DNS names to LDH names and Unicode names
Modified the definition of 'conjoined' variant relationship so
it was circular
Added 'proxy', 'private', 'redacted', and 'obscured' status
values (most useful for entities).
Added a privacy considerations section
Added a security considerations section
Added 'reseller' and 'sponsor' to the list of entity roles
Added the 'events' common data structure
Added 'asEventActor' to entities
Added appendix on event modeling
Removed the subclasses/superclassing between RIRs/DNRs for
entity and domain object classes
Change suggested status/relation/etc values to be case/spacing
consistent
Normalized some of the definitions of object class members
Modifying the JSON signaling section to reference the guidance
in draft-ietf-weirds-using-http
Changed the text regarding the process of unknown JSON
attributes
Authors' Addresses Authors' Addresses
Andrew Lee Newton Andrew Lee Newton
American Registry for Internet Numbers American Registry for Internet Numbers
3635 Concorde Parkway 3635 Concorde Parkway
Chantilly, VA 20151 Chantilly, VA 20151
US US
Email: andy@arin.net Email: andy@arin.net
URI: http://www.arin.net URI: http://www.arin.net
 End of changes. 220 change blocks. 
770 lines changed or deleted 1208 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/