draft-ietf-weirds-json-response-03.txt   draft-ietf-weirds-json-response-04.txt 
Network Working Group A.L. Newton Network Working Group A. Newton
Internet-Draft ARIN Internet-Draft ARIN
Intended status: Standards Track S. Hollenbeck Intended status: Standards Track S. Hollenbeck
Expires: October 11, 2013 Verisign Labs Expires: December 14, 2013 Verisign Labs
April 09, 2013 June 12, 2013
JSON Responses for the Registration Data Access Protocol (RDAP) JSON Responses for the Registration Data Access Protocol (RDAP)
draft-ietf-weirds-json-response-03 draft-ietf-weirds-json-response-04
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
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 October 11, 2013. This Internet-Draft will expire on December 14, 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 . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Definitions . . . . . . . . . . . . . . . . . 4
3. Use of JSON . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Signaling . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Naming . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Common Data Types . . . . . . . . . . . . . . . . . . . . . . 6
5. Common Data Structures . . . . . . . . . . . . . . . . . . . 7
5.1. RDAP Conformance . . . . . . . . . . . . . . . . . . . . 8
5.2. Links . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.3. Notices And Remarks . . . . . . . . . . . . . . . . . . . 9
5.4. Language Identifier . . . . . . . . . . . . . . . . . . . 11
5.5. Events . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.6. Status . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.7. Port 43 Whois Server . . . . . . . . . . . . . . . . . . 12
5.8. Public IDs . . . . . . . . . . . . . . . . . . . . . . . 12
5.9. An Example . . . . . . . . . . . . . . . . . . . . . . . 13
6. Object Classes . . . . . . . . . . . . . . . . . . . . . . . 14
6.1. The Entity Object Class . . . . . . . . . . . . . . . . . 14
6.2. The Nameserver Object Class . . . . . . . . . . . . . . . 20
6.3. The Domain Object Class . . . . . . . . . . . . . . . . . 23
6.4. The IP Network Object Class . . . . . . . . . . . . . . . 35
6.5. Autonomous System Number Entity Object Class . . . . . . 39
7. Error Response Body . . . . . . . . . . . . . . . . . . . . . 42
8. Responding to Help Queries . . . . . . . . . . . . . . . . . 43
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44
9.1. Status . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.2. Event Actions . . . . . . . . . . . . . . . . . . . . . . 48
9.3. Roles . . . . . . . . . . . . . . . . . . . . . . . . . . 50
9.4. Variant Relations . . . . . . . . . . . . . . . . . . . . 53
10. Security Considerations . . . . . . . . . . . . . . . . . . . 54
11. Internationalization Considerations . . . . . . . . . . . . . 54
11.1. Character Encoding . . . . . . . . . . . . . . . . . . . 54
11.2. URIs and IRIs . . . . . . . . . . . . . . . . . . . . . 54
11.3. Language Tags . . . . . . . . . . . . . . . . . . . . . 55
11.4. Internationalized Domain Names . . . . . . . . . . . . . 55
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 55
13. Contributing Authors and Acknowledgements . . . . . . . . . . 55
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 56
14.1. Normative References . . . . . . . . . . . . . . . . . . 56
14.2. Informative References . . . . . . . . . . . . . . . . . 57
Appendix A. Suggested Data Modeling with the Entity Object Class 58
A.1. Registrants and Contacts . . . . . . . . . . . . . . . . 58
A.2. Registrars . . . . . . . . . . . . . . . . . . . . . . . 60
Appendix B. Modeling Events . . . . . . . . . . . . . . . . . . 62
Appendix C. Structured vs Unstructured Addresses . . . . . . . . 64
Appendix D. Secure DNS . . . . . . . . . . . . . . . . . . . . . 66
Appendix E. Motivations for Using JSON . . . . . . . . . . . . . 67
Appendix F. Changelog . . . . . . . . . . . . . . . . . . . . . 67
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 70
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 the Registration Data Access the RESTful web queries as defined by the Registration Data Access
Protocol Lookup Format [I-D.ietf-weirds-rdap-query]. Protocol Lookup Format [I-D.ietf-weirds-rdap-query].
The data model for JSON responses is specified in four sections: The data model for JSON responses is specified in four sections:
1. simple data types conveyed in JSON strings 1. simple data types conveyed in JSON strings
skipping to change at page 3, line 48 skipping to change at page 5, line 4
RIR: "Regional Internet Registry". RIR: "Regional Internet Registry".
3. Use of JSON 3. Use of JSON
3.1. Signaling 3.1. Signaling
Media type signaling for the JSON data specified in this document is Media type signaling for the JSON data specified in this document is
specified in [I-D.ietf-weirds-using-http]. specified in [I-D.ietf-weirds-using-http].
3.2. Naming 3.2. Naming
Clients processing JSON [RFC4627] responses are under no obligation Clients processing JSON [RFC4627] responses are under no obligation
to process unrecognized JSON attributes but SHOULD NOT treat them as to process unrecognized JSON attributes but SHOULD NOT treat them as
an error. Servers MAY insert values signified by names into the JSON an error. Servers MAY insert values signified by names into the JSON
responses which are not specified in this document. Insertion of responses which are not specified in this document. Insertion of
unspecified values into JSON responses SHOULD have names prefixed unspecified values into JSON responses SHOULD have names prefixed
with a short identifier followed by an underscore followed by a with a short identifier followed by an underscore followed by a
meaningful name. The full JSON name, the prefix plus the underscore meaningful name. The full JSON name (the prefix plus the underscore
plus the meaningful name, SHOULD adhere to the character and name plus the meaningful name) SHOULD adhere to the character and name
limitations of the prefix registry described in limitations of the prefix registry described in
[I-D.ietf-weirds-using-http]. [I-D.ietf-weirds-using-http].
Consider the following JSON response with JSON names. some of which Consider the following JSON response with JSON names, all of which
are not specified in this document. are specified in this document.
{ {
"handle" : "ABC123", "handle" : "ABC123",
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
skipping to change at page 6, line 4 skipping to change at page 7, line 4
boolean, array, object and null. This section describes the boolean, array, object and null. This section describes the
semantics and/or syntax reference for data types used in this semantics and/or syntax reference for data types used in this
document derived from the JSON character string. document derived from the JSON character string.
'handle': DNRs and RIRs have registry-unique identifiers that 'handle': DNRs and RIRs have registry-unique identifiers that
may be used to specifically reference an object may be used to specifically reference an object
instance. The semantics of this data type as found instance. The semantics of this data type as found
in this document is to be a registry-unique in this document is to be a registry-unique
reference to the closest enclosing object where the reference to the closest enclosing object where the
value is found. The data type names 'registryId', value is found. The data type names 'registryId',
'roid', 'nic-handle', 'registrationNo', etc. are 'roid', 'nic-handle', 'registrationNo', etc. are
terms often synonymous with this data type. In terms often synonymous with this data type. In
this document, the term 'handle' is used. The term this document, the term 'handle' is used. The term
exposed to users by clients is a presentation issue exposed to users by clients is a presentation issue
beyond the scope of this document. beyond the scope of this document.
IPv4 addresses: The representation of IPv4 addresses in this IPv4 addresses: The representation of IPv4 addresses in this
document uses the dotted-decimal notation described document uses the dotted-decimal notation described
in [RFC1166]. An example of this textual in [RFC1166]. An example of this textual
representation is '192.0.2.0'. representation is '192.0.2.0'.
skipping to change at page 6, line 33 skipping to change at page 7, line 33
designation as defined in [ISO.3166.1988]. The designation as defined in [ISO.3166.1988]. The
alpha-2 representation is used because it is freely alpha-2 representation is used because it is freely
available whereas the alpha-3 and numeric-3 available whereas the alpha-3 and numeric-3
standards are not. standards are not.
LDH names: Textual representations of DNS names where the LDH names: Textual representations of DNS names where the
labels of the domain are all "letters, digits, labels of the domain are all "letters, digits,
hyphen" labels as described by [RFC5890]. Trailing hyphen" labels as described by [RFC5890]. Trailing
periods are optional. periods are optional.
Unicode names: Textual representations of DNS names were one or Unicode names: Textual representations of DNS names where one or
more of the labels are u-labels as described by more of the labels are U-labels as described by
[RFC5890]. Trailing periods are optional. [RFC5890]. Trailing periods are optional.
dates and times: The syntax for values denoting dates and times is dates and times: The syntax for values denoting dates and times is
defined in [RFC3339]. defined in [RFC3339].
URIs: The syntax for values denoting a Uniform Resource URIs: The syntax for values denoting a Uniform Resource
Identifier (URI) is defined by [RFC3986]. Identifier (URI) is defined by [RFC3986].
Contact information is defined using JSON vCards as described in Contact information is defined using JSON vCards as described in
[I-D.kewisch-vcard-in-json] [I-D.kewisch-vcard-in-json]
5. Common Data Structures 5. Common Data Structures
This section defines common data structures to be used in response. This section defines common data structures used commonly in object
Each of these structures MAY appear within any object class of a classes.
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. This data structure appears in the construction of the response. This data structure appears
only in the top most object of a response. only in the top most object of a response.
An example rdapConformance data structure: An example rdapConformance data structure:
skipping to change at page 11, line 13 skipping to change at page 12, line 13
o 'eventAction' -- a string denoting the reason for the event o 'eventAction' -- a string denoting the reason for the event
o 'eventActor' -- an optional identifier denoting the actor o 'eventActor' -- an optional identifier denoting the actor
responsible for the event responsible for the event
o 'eventDate' -- a string containing the time and date the event o 'eventDate' -- a string containing the time and date the event
occurred. occurred.
Events can be future dated. One use case for future dating of events Events can be future dated. One use case for future dating of events
is to denote when an object expires from a registry. is to denote when an object expires from a registry.
See Appendix A.2 for a list of suggested values for the 'eventAction' See Section 9.2 for a list of values for the 'eventAction' string.
string. See Appendix C regarding the various ways events can be See Appendix B regarding the various ways events can be modeled.
modeled.
5.6. Status 5.6. Status
This data structure, named 'status', is an array of strings This data structure, named 'status', is an array of strings
indicating the state of a registered object (see Appendix A.1 for indicating the state of a registered object (see Section 9.1 for a
suggested values). list of values).
5.7. Port 43 Whois Server 5.7. Port 43 Whois Server
This data stricture, named 'port43', is a simple string containing This data structure, named 'port43', is a simple string containing
the fully-qualified host name of the WHOIS [RFC3912] server where the the fully-qualified host name of the WHOIS [RFC3912] server where the
containing object instance may be found. Note that this is not a containing object instance may be found. Note that this is not a
URI, as there is not Whois URI scheme. URI, as there is no WHOIS URI scheme.
5.8. An Example 5.8. Public IDs
This data structure maps a public identifier to an object class. It
is named 'publicIds' and is an array of objects, with each object
containing the following members:
o type - a string denoting the type of public identifier
o identifier - a public identifier of the type denoted by 'type'
The following is an example of a 'publicIds' structure.
"publicIds":
[
{
"type":"IANA Registrar ID",
"identifier":"1"
}
]
Figure 10
5.9. 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" :
skipping to change at page 12, line 36 skipping to change at page 13, line 41
} }
] ]
} }
], ],
"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" : "v4", "ipVersion" : "v4",
"name": "NET-RTR-1", "name": "NET-RTR-1",
"description" : [ "A network used for example documentation" ],
"parentHandle" : "YYYY-RIR", "parentHandle" : "YYYY-RIR",
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
] ]
} }
Figure 11
Figure 10
6. Object Classes 6. Object Classes
Object classes represent structures appropriate for a response from Object classes represent structures appropriate for a response from
the queries specified in [I-D.ietf-weirds-rdap-query]. the queries specified in [I-D.ietf-weirds-rdap-query].
Each object class contains a "links" array as specified in Each object class contains a "links" array as specified in
Section 5.2. For every object class in a response, whether the Section 5.2. For every object class in a response, whether the
object class is directly representing the response to a query or is object class is directly representing the response to a query or is
embedded in other object classes, servers SHOULD provide a link embedded in other object classes, servers SHOULD provide a link
skipping to change at page 13, line 46 skipping to change at page 14, line 47
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 appropriate response for the /entity/XXXX query defined in
Registration Data Access Protocol Lookup Format Registration Data Access Protocol Lookup Format
[I-D.ietf-weirds-rdap-query]. This object class represents the [I-D.ietf-weirds-rdap-query]. This object class represents the
information of organizations, corporations, governments, non-profits, information of organizations, corporations, governments, non-profits,
clubs, individual persons, and informal groups of people. All of clubs, individual persons, and informal groups of people. All of
these representations are so similar that it is best to represent these representations are so similar that it is best to represent
them in JSON [RFC4627] with one construct, the entity object class, them in JSON [RFC4627] with one construct, the entity object class,
to aid in the re-use of code by implementers. to aid in the re-use of code by implementers.
Some of the members of the entity object class are repeated in other
object classes described later in this document.
The entity object is served by both RIRs and DNRs. The following is 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: an example of an entity that might be served by an RIR. For
illustrative purposes, it does not include rdapConformance or notices
data structures.
{ {
"handle" : "XXXX", "handle":"XXXX",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "Joe Bob, Inc." ], ["version", {}, "text", "4.0"],
[ "fn", {}, "text", "Bobby Joe Shopping" ], ["fn", {}, "text", "Joe User"],
[ "label", {}, "text", "123 Maple Ave\n", ["n", {}, "text",
"Suite 90001\n", ["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
"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" ],
], ],
"roles" : [ "registrant" ], ["bday", {}, "date-and-or-time", "--02-03"],
"remarks" : ["anniversary",
[ {}, "date-and-or-time", "2009-08-08T14:30:00-05:00"
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : ["gender", {}, "text", "M"],
[ ["kind", {}, "text", "individual"],
{ ["lang", {
"value" : "http://example.com/entity/XXXX", "pref":"1"
"rel" : "self", }, "language-tag", "fr"],
"href" : "http://example.com/entity/XXXX" ["lang", {
} "pref":"2"
}, "language-tag", "en"],
["org", {
"type":"work"
}, "text", "Example"],
["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
], ],
"events" : ["adr",
[
{ {
"eventAction" : "registration", "type":"home",
"eventDate" : "1990-12-31T23:59:60Z" "label":"123 Maple Ave\nSuite 90001\nVancouver\nBC\n1239\n"
} },
"text",
[
"", "", "", "", "", "", ""
]
], ],
"asEventActor" : ["tel",
[
{ {
"eventAction" : "last changed", "type":["work", "voice"],
"eventDate" : "1991-12-31T23:59:60Z" "pref":"1"
} },
"uri",
"tel:+1-555-555-1234;ext=102"
],
["tel",
{ "type":["work", "cell", "voice", "video", "text"] },
"uri",
"tel:+1-555-555-4321"
],
["email",
{ "type":"work" },
"text",
"joe.user@example.com"
],
["geo", {
"type":"work"
}, "uri", "geo:46.772673,-71.282945"],
["key",
{ "type":"work" },
"uri",
"http://www.example.com/joe.user/joe.asc"
],
["tz", {},
"utc-offset", "-05:00"],
["url", { "type":"home" },
"uri", "http://example.org"]
]
],
"roles":[ "registrar" ],
"publicIds":[
{
"type":"IANA Registrar ID",
"identifier":"1"
}
],
"remarks":[
{
"description":[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
] ]
} }
],
"links":[
{
"value":"http://example.com/entity/XXXX",
"rel":"self",
"href":"http://example.com/entity/XXXX"
}
],
"events":[
{
"eventAction":"registration",
"eventDate":"1990-12-31T23:59:60Z"
}
],
"asEventActor":[
{
"eventAction":"last changed",
"eventDate":"1991-12-31T23:59:60Z"
}
]
}
Entities may also have other entities embedded with them in an array.
This can be used to model an organization with specific individuals
fulfilling designated roles of responsibility.
The following is an elided example of an entity with embedded
entities.
{
"handle" : "ANENTITY",
"roles" : [ "registrar" ],
...
"entities" :
[
{
"handle": "ANEMBEDDEDENTITY",
"roles" : [ "technical" ],
...
},
...
],
...
}
Figure 12
This object has 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 vCard -- a JSON vCard with the entity's contact information o vcardArray -- a JSON vCard with the entity's contact information
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 (see object would have with its closest containing object (see
Appendix A.3 for suggested values) Section 9.3 for a list of values)
o publicIds - see Section 5.8
o entities - an array of entity objects as defined by this section.
o remarks -- see Section 5.3 o remarks -- see Section 5.3
o links -- see Section 5.2 o links -- see Section 5.2
o events -- see Section 5.5 o events -- see Section 5.5
o asEventActor -- this data structure takes the same form as the o asEventActor -- this data structure takes the same form as the
'events' data structure (see Section 5.5), but each object in the 'events' data structure (see Section 5.5), but each object in the
array MUST NOT have an 'eventActor' member. These objects denote array MUST NOT have an 'eventActor' member. These objects denote
that the entity is an event actor for the given events. See that the entity is an event actor for the given events. See
Appendix C regarding the various ways events can be modeled. Appendix B regarding the various ways events can be modeled.
o status -- see Section 5.6 o status -- see Section 5.6
o port43 -- see Section 5.7 o port43 -- see Section 5.7
The following is an example of a entity that might be served by a The following is an example of a entity that might be served by a
DNR: DNR. For illustrative purposes, it does not include rdapConformance
or notices data structures.
{ {
"handle" : "XXXX", "handle":"XXXX",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "Joe Bob, Inc." ], ["version", {}, "text", "4.0"],
[ "fn", {}, "text", "Bobby Joe Shopping" ], ["fn", {}, "text", "Joe User"],
[ "label", {}, "text", "123 Maple Ave\n", ["kind", {}, "text", "individual"],
"Suite 90001\n", ["lang", {
"Vancouver\n", "pref":"1"
"BC\n",
"1239\n" ], }, "language-tag", "fr"],
[ "email", {}, "text", "joe at bob.com" ], ["lang", {
[ "email", {}, "text", "bob at joe.com" ], "pref":"2"
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ], }, "language-tag", "en"],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ], ["org", {
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ], "type":"work"
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ], }, "text", "Example"],
["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
], ],
"status" : [ "validated", "locked" ], ["tel",
"remarks" : { "type":["work", "voice"], "pref":"1" },
[ "uri", "tel:+1-555-555-1234;ext=102"
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
], ],
"links" : ["email",
[ { "type":"work" },
{ "text", "joe.user@example.com"
"value" : "http://example.com/entity/XXXX",
"rel" : "self",
"href" : "http://example.com/entity/XXXX"
}
], ],
"port43" : "whois.example.net", ]
"events" : ],
[ "status":[ "validated", "locked" ],
{ "remarks":[
"eventAction" : "registration", {
"eventDate" : "1990-12-31T23:59:60Z" "description":[
}, "She sells sea shells down by the sea shore.",
{ "Originally written by Terry Sullivan."
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com"
}
] ]
} }
],
"links":[
{
"value":"http://example.com/entity/XXXX",
"rel":"self",
"href":"http://example.com/entity/XXXX"
}
],
"port43":"whois.example.net",
"events":[
{
"eventAction":"registration",
"eventDate":"1990-12-31T23:59:60Z"
},
{
"eventAction":"last changed",
"eventDate":"1991-12-31T23:59:60Z",
"eventActor":"joe@example.com"
}
]
}
6.2. The Nameserver Object Class 6.2. The Nameserver Object Class
The nameserver object class represents information regarding DNS name The nameserver object class represents information regarding DNS name
servers used in both forward and reverse DNS. RIRs and some DNRs servers used in both forward and reverse DNS. 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. For illustrative
purposes, it does not include rdapConformance or notices data
structures.
{ {
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "ns1.xn--fo-5ja.example", "ldhName" : "ns1.xn--fo-5ja.example",
"unicodeName" : "foo.example", "unicodeName" : "foo.example",
"status" : [ "active" ], "status" : [ "active" ],
"ipAddresses" : "ipAddresses" :
{ {
"v4": [ "192.0.2.1", "192.0.2.2" ], "v4": [ "192.0.2.1", "192.0.2.2" ],
"v6": [ "2001:db8::123" ] "v6": [ "2001:db8::123" ]
skipping to change at page 18, line 43 skipping to change at page 21, line 43
"port43" : "whois.example.net", "port43" : "whois.example.net",
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z", "eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com" "eventActor" : "joe@example.com"
} }
] ]
} }
Figure 11 Figure 13
Figure 11 is an example of a nameserver object with all values given. Figure 13 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 12 is an example of a nameserver object as would be found in Figure 14 is an example of a nameserver object as would be found in
RIRs and some DNRs, while Figure 13 is an example of a nameserver RIRs and some DNRs, while Figure 15 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:
{ {
"ldhName" : "ns1.example.com" "ldhName" : "ns1.example.com"
} }
Figure 12 Figure 14
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:
{ {
"ldhName" : "ns1.example.com", "ldhName" : "ns1.example.com",
"ipAddresses" : { "v6" : [ "2001:db8::123", "2001:db8::124" ] } "ipAddresses" : { "v6" : [ "2001:db8::123", "2001:db8::124" ] }
} }
Figure 13 Figure 15
As nameservers can be modeled by some registries to be first-class
objects, they may also have an array of entities (Section 6.1)
embedded to signify parties responsible for the maintenance,
registrations, etc. of the nameservers.
The following is an elided example of a nameserver with embedded
entities.
{
"handle" : "XXXX",
"ldhName" : "ns1.xn--fo-5ja.example",
...
"entities" :
[
...
],
...
}
Figure 16
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 ldhName -- a string containing the LDH name of the nameserver (see o ldhName -- a string containing the LDH name of the nameserver (see
Section 4) Section 4)
o unicodeName -- a string containing a DNS unicode name of the o unicodeName -- a string containing a DNS Unicode name of the
nameserver (see Section 4) nameserver (see Section 4)
o ipAddresses -- an object containing the following members: o ipAddresses -- an object containing the following members:
* v6 -- an array of strings containing IPv6 addresses of the * v6 -- an array of strings containing IPv6 addresses of the
nameserver nameserver
* v4 -- an array of strings containing IPv4 addresses of the * v4 -- an array of strings containing IPv4 addresses of the
nameserver nameserver
o entities -- an array of entity objects as defined by Section 6.1.
o status - see Section 5.6 o status - see Section 5.6
o remarks - see Section 5.3 o remarks - see Section 5.3
o links - see Section 5.2 o links - see Section 5.2
o port43 - see Section 5.7 o port43 - see Section 5.7
o events - see Section 5.5 o events - see Section 5.5
skipping to change at page 20, line 16 skipping to change at page 24, line 4
o remarks - see Section 5.3 o remarks - see Section 5.3
o links - see Section 5.2 o links - see Section 5.2
o port43 - see Section 5.7 o port43 - see Section 5.7
o events - see Section 5.5 o events - see Section 5.5
6.3. The Domain Object Class 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. tree.
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",
"ldhName" : "blah.example.com", "ldhName" : "blah.example.com",
... ...
"nameServers" : "nameServers" :
[ [
skipping to change at page 21, line 5 skipping to change at page 24, line 37
[ [
... ...
] ]
} }
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 a registry unique identifier of o handle -- a string representing a registry unique identifier of
the domain object instance the domain object instance
o ldhName -- a string describing an domain name in LDH form as o ldhName -- a string describing a domain name in LDH form as
described in Section 4 described in Section 4
o unicodeName -- a string containing a domain name with u-labels as o unicodeName -- a string containing a domain name with U-labels as
described in Section 4 described in Section 4
o variants -- an array of objects, each containing the following o variants -- an array of objects, each containing the following
values: values:
* relation -- an array of strings, with each string denoting the * relation -- an array of strings, with each string denoting the
relationship between the variants and the containing domain relationship between the variants and the containing domain
object (see Appendix A.4 for a list of suggested variant object (see Section 9.4 for a list of suggested variant
relations). relations).
* idnTable -- the name of the IDN table of codepoints, such as
one listed with the IANA (see IDN tables [1]).
* variantNames -- an array of objects, with each object * variantNames -- an array of objects, with each object
containing an "ldhName" member and a "unicodeName" member (see containing an "ldhName" member and a "unicodeName" member (see
Section 4). Section 4).
o nameservers -- an array of nameserver objects as defined by o nameservers -- an array of nameserver objects as defined by
Section 6.2 Section 6.2
o delegationKeys -- an array of objects, each with the following o secureDNS -- an object with the following members:
members:
* algorithm -- an integer as specified by the algorithm field of * zoneSigned -- boolean true if the zone has been signed, false
a DNS DS record as specified by RFC 4034 [RFC4034] in otherwise.
presentation format
* digest -- an string as specified by the digest field of a DNS * delegationSigned -- boolean true if there are DS records in the
DS record as specified by RFC 4034 in presentation format parent, false otherwise.
* digestType -- an integer as specified by the digest type field * maxSigLife -- an integer representing the signature life time
of a DNS DS record as specified by RFC 4034 in presentation in seconds to be used when creating the RRSIG DS record in the
format parent zone [RFC5910].
* keyTag -- an integer as specified by the key tag field of a DNS * dsData - an array of objects, each with the following members:
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 RFC 4034 [RFC4034] in
presentation format
+ algorithm -- an integer as specified by the algorithm field
of a DNS DS record as specified by RFC 4034 in presentation
format
+ digest -- a 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
+ events - see Section 5.5
* keyData - an array of objects, each with the following members:
+ flags -- a string representing the flags field value in the
DNSKEY record [RFC4034] in presentation format.
+ protocol - a string representation of the protocol field
value of the DNSKEY record [RFC4034] in presentation format.
+ publicKey - a string representation of the public key in the
DNSKEY record [RFC4034] in presentation format.
+ algorithm -- an integer as specified by the algorithm field
of a DNSKEY record as specified by RFC 4034 [RFC4034] in
presentation format
+ events - see Section 5.5
See Appendix D for background information on these objects.
o entities -- an array of entity objects as defined by Section 6.1. o entities -- an array of entity objects as defined by Section 6.1.
o status - see Section 5.6 o status - see Section 5.6
o publicIds - see Section 5.8
o remarks - see Section 5.3 o remarks - see Section 5.3
o links - see Section 5.2 o links - see Section 5.2
o port43 - see Section 5.7 o port43 - see Section 5.7
o events - see Section 5.5 o events - see Section 5.5
The following is an example of a JSON domain object representing a The following is an example of a JSON domain object representing a
reverse DNS delegation point that might be served by an RIR: reverse DNS delegation point that might be served by an RIR. For
illustrative purposes, it does not include rdapConformance or notices
data structures.
{ {
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "192.in-addr.arpa", "ldhName" : "192.in-addr.arpa",
"nameServers" : "nameServers" :
[ [
{ "ldhName" : "ns1.rir.example" }, { "ldhName" : "ns1.rir.example" },
{ "ldhName" : "ns2.rir.example" } { "ldhName" : "ns2.rir.example" }
], ],
"delegationKeys" : "secureDNS":
[ {
{ "delegationSigned": true,
"algorithm": 7, "dsData":
"digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C", [
"digestType" : 1, {
"keyTag" : 53814 "keyTag": 12345,
} "algorithm": 3,
], "digestType": 1,
"digest": "49FD46E6C4B45C55D4AC",
}
]
},
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
], ],
skipping to change at page 23, line 6 skipping to change at page 27, line 41
], ],
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z", "eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com" "eventActor" : "joe@example.com"
} }
], ],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "Joe Bob, Inc." ], ["version", {}, "text", "4.0"],
[ "fn", {}, "text", "Bobby Joe Shopping" ],
[ "label", {}, "text", "123 Maple Ave\n", ["fn", {}, "text", "Joe User"],
"Suite 90001\n", ["kind", {}, "text", "individual"],
"Vancouver\n", ["lang", {
"BC\n", "pref":"1"
"1239\n" ], }, "language-tag", "fr"],
[ "email", {}, "text", "joe at bob.com" ], ["lang", {
[ "email", {}, "text", "bob at joe.com" ], "pref":"2"
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ], }, "language-tag", "en"],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ], ["org", {
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ], "type":"work"
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ], }, "text", "Example"],
["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
],
]
], ],
"roles" : [ "registrant" ], "roles" : [ "registrant" ],
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
skipping to change at page 24, line 10 skipping to change at page 29, line 21
], ],
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z", "eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com" "eventActor" : "joe@example.com"
} }
] ]
} }
] ]
} }
The following is an example of a JSON domain object representing a The following is an example of a JSON domain object representing a
forward DNS delegation point that might be served by a DNR: forward DNS delegation point that might be served by a DNR. For
illustrative purposes, it does not include rdapConformance or notices
data structures.
{ {
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "xn--fo-5ja.example", "ldhName" : "xn--fo-5ja.example",
"unicodeName" : "foo.example", "unicodeName" : "foo.example",
"variants" : "variants" :
[ [
{ {
"relation" : [ "registered", "conjoined" ], "relation" : [ "registered", "conjoined" ],
"variantNames" : "variantNames" :
skipping to change at page 24, line 37 skipping to change at page 30, line 4
"relation" : [ "registered", "conjoined" ], "relation" : [ "registered", "conjoined" ],
"variantNames" : "variantNames" :
[ [
{ {
"ldhName" : "xn--fo-cka.example", "ldhName" : "xn--fo-cka.example",
"unicodeName" : "foo.example" "unicodeName" : "foo.example"
}, },
{ {
"ldhName" : "xn--fo-fka.example", "ldhName" : "xn--fo-fka.example",
"unicodeName" : "foeo.example" "unicodeName" : "foeo.example"
} }
] ]
}, },
{ {
"relation" : [ "unregistered", "restricted registration" ], "relation" : [ "unregistered", "restricted registration" ],
"idnTable": ".EXAMPLE Swedish",
"variantNames" : "variantNames" :
[ [
{ {
"ldhName": "xn--fo-8ja.example", "ldhName": "xn--fo-8ja.example",
"unicodeName" : "foo.example" "unicodeName" : "foo.example"
} }
] ]
} }
], ],
"status" : [ "locked", "transferProhibited" ], "status" : [ "locked", "transferProhibited" ],
"publicIds":[
{
"type":"ENS_Auth ID",
"identifier":"1234567890"
}
],
"nameServers" : "nameServers" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "ns1.example.com", "ldhName" : "ns1.example.com",
"status" : [ "active" ], "status" : [ "active" ],
"ipAddresses" : "ipAddresses" :
{ {
"v6": [ "2001:db8::123", "2001:db8::124" ], "v6": [ "2001:db8::123", "2001:db8::124" ],
"v4": [ "192.0.2.1", "192.0.2.2" ] "v4": [ "192.0.2.1", "192.0.2.2" ]
skipping to change at page 26, line 40 skipping to change at page 32, line 11
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z" "eventDate" : "1991-12-31T23:59:60Z"
} }
] ]
} }
], ],
"delegationKeys" : "secureDNS":
[ [
{ "zoneSigned": true,
"algorithm": 7, "delegationSigned": true,
"digest" : "E68C017BD813B9AE2F4DD28E61AD014F859ED44C", "maxSigLife": 604800,
"digestType" : 1, "keyData":
"keyTag" : 53814 [
} {
"flags": 257,
"protocol": 3,
"algorithm": 1,
"publicKey": "AQPJ////4Q==",
"events":
[
{
"eventAction": "last changed",
"eventDate": "2012-07-23T05:15:47Z"
}
]
}
]
], ],
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
skipping to change at page 27, line 29 skipping to change at page 33, line 13
"port43" : "whois.example.net", "port43" : "whois.example.net",
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z", "eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com" "eventActor" : "joe@example.com"
}, },
{ {
"eventAction" : "transfer", "eventAction" : "transfer",
"eventDate" : "1991-12-31T23:59:60Z", "eventDate" : "1991-12-31T23:59:60Z",
"eventActor" : "joe@bob.com" "eventActor" : "joe@example.com"
}, },
{ {
"eventAction" : "expiration", "eventAction" : "expiration",
"eventDate" : "2016-12-31T23:59:60Z", "eventDate" : "2016-12-31T23:59:60Z",
"eventActor" : "joe@bob.com" "eventActor" : "joe@example.com"
} }
], ],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "Joe Bob, Inc." ], ["version", {}, "text", "4.0"],
[ "fn", {}, "text", "Bobby Joe Shopping" ], ["fn", {}, "text", "Joe User"],
[ "label", {}, "text", "123 Maple Ave\n", ["kind", {}, "text", "individual"],
"Suite 90001\n", ["lang", {
"Vancouver\n", "pref":"1"
"BC\n", }, "language-tag", "fr"],
"1239\n" ], ["lang", {
[ "email", {}, "text", "joe at bob.com" ], "pref":"2"
[ "email", {}, "text", "bob at joe.com" ], }, "language-tag", "en"],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ], ["org", {
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ], "type":"work"
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ], }, "text", "Example"],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ], ["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
],
]
], ],
"status" : [ "validated", "locked" ], "status" : [ "validated", "locked" ],
"roles" : [ "registrant" ], "roles" : [ "registrant" ],
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
skipping to change at page 29, line 12 skipping to change at page 35, line 17
] ]
} }
6.4. 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. For illustrative purposes, it does not
include rdapConformance or notices data structures.
{ {
"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" : "v6", "ipVersion" : "v6",
"name": "NET-RTR-1", "name": "NET-RTR-1",
"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" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "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"
}, },
{ {
skipping to change at page 30, line 35 skipping to change at page 36, line 42
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z" "eventDate" : "1991-12-31T23:59:60Z"
} }
], ],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "Joe Bob, Inc." ], ["version", {}, "text", "4.0"],
[ "fn", {}, "text", "Bobby Joe Shopping" ], ["fn", {}, "text", "Joe User"],
[ "label", {}, "text", "123 Maple Ave\n", ["kind", {}, "text", "individual"],
"Suite 90001\n", ["lang", {
"Vancouver\n", "pref":"1"
"BC\n", }, "language-tag", "fr"],
"1239\n" ], ["lang", {
[ "email", {}, "text", "joe at bob.com" ], "pref":"2"
[ "email", {}, "text", "bob at joe.com" ],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ], }, "language-tag", "en"],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ], ["org", {
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ], "type":"work"
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ], }, "text", "Example"],
["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
],
]
], ],
"roles" : [ "registrant" ], "roles" : [ "registrant" ],
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
skipping to change at page 32, line 5 skipping to change at page 38, line 30
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 string signifying the IP protocol version of the o ipVersion -- a string signifying the IP protocol version of the
network: "v4" signifying an IPv4 network, "v6" 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
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
skipping to change at page 32, line 43 skipping to change at page 39, line 19
o events - see Section 5.5 o events - see Section 5.5
6.5. Autonomous System Number Entity Object Class 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.
For illustrative purposes, it does not include rdapConformance or
notices data structures.
{ {
"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" ],
"type" : "DIRECT ALLOCATION", "type" : "DIRECT ALLOCATION",
"status" : [ "allocated" ],
"country": "AU", "country": "AU",
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
skipping to change at page 33, line 42 skipping to change at page 40, line 21
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:60Z" "eventDate" : "1991-12-31T23:59:60Z"
} }
], ],
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "Joe Bob, Inc." ], ["version", {}, "text", "4.0"],
[ "fn", {}, "text", "Bobby Joe Shopping" ], ["fn", {}, "text", "Joe User"],
[ "label", {}, "text", "123 Maple Ave\n", ["kind", {}, "text", "individual"],
"Suite 90001\n", ["lang", {
"Vancouver\n", "pref":"1"
"BC\n", }, "language-tag", "fr"],
"1239\n" ], ["lang", {
"pref":"2"
[ "email", {}, "text", "joe at bob.com" ], }, "language-tag", "en"],
[ "email", {}, "text", "bob at joe.com" ], ["org", {
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ], "type":"work"
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ], }, "text", "Example"],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ], ["title", {}, "text", "Research Scientist"],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ], ["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
],
]
], ],
"roles" : [ "registrant" ], "roles" : [ "registrant" ],
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
skipping to change at page 35, line 5 skipping to change at page 42, line 5
] ]
} }
] ]
} }
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 -- a number representing the starting number [RFC5396]
autonomous system numbers in the block of autonomous system numbers
o endAutnum -- the ending number [RFC5396] in the block of o endAutnum -- a number representing the ending number [RFC5396] in
autonomous system numbers the block of 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
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 status -- an array of strings indicating the state of the 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
o remarks - see Section 5.3 o remarks - see Section 5.3
o links - see Section 5.2 o links - see Section 5.2
o events - see Section 5.5 o events - see Section 5.5
7. Error Response Body 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 common response body. For illustrative
purposes, it does not include rdapConformance or notices data
structures.
{ {
"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." "Sorry, dude!"
] ]
} }
Figure 14 Figure 17
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.
8. IANA Considerations This is an example of the common response body with and
rdapConformance and notices data structures:
None. {
"rdapConformance" :
[
"rdap_level_0"
],
"notices" :
[
{
"title" : "Beverage policy",
"description" :
[
"Beverages with caffeine for keeping horses awake."
],
"links" :
[
{
"value" : "http://example.net/ip/192.0.2.0/24",
"rel" : "alternate",
"type" : "text/html",
"href" : "http://www.example.com/redaction_policy.html"
}
]
}
],
"lang" : "en",
"errorCode": 418,
"title": "Your beverage choice is not available",
"description":
[
"I know coffee has more ummppphhh.",
"Sorry, dude!"
]
}
9. Security Considerations Figure 18
8. Responding to Help Queries
The appropriate response to /help queries as defined by
[I-D.ietf-weirds-rdap-query] is to use the notices structure as
defined in Section 5.3.
This is an example of a response to a /help query including the
rdapConformance data structure.
{
"rdapConformance" :
[
"rdap_level_0"
],
"notices" :
[
{
"title" : "Authentication Policy",
"description" :
[
"Access to sensitive data for users with proper credentials."
],
"links" :
[
{
"value" : "http://example.net/help",
"rel" : "alternate",
"type" : "text/html",
"href" : "http://www.example.com/auth_policy.html"
}
]
}
]
}
Figure 19
9. IANA Considerations
This section requests that the IANA establish an RDAP JSON Values
Registry for use in the status (Section 5.6), role (Section 6.1),
event action (Section 5.5), and domain variant relation (Section 6.3)
fields specified in RDAP.
Each entry in the registry should contain the following fields:
1. Value - the string value being registered.
2. Type - the type of value being registered. It should be one of
the following:
* 'status' - denotes a value for the 'status' object member as
defined by Section 5.6.
* 'role' - denotes a value for the 'role' array as defined in
Section 6.1.
* 'event action' - denotes a value for an event action as
defined in Section 5.5.
* 'domain variant relation' - denotes a relationship between a
domain and a domain variant as defined in Section 6.3.
3. Description - a one or two sentence description regarding the
meaning of the value, how it might be used, and/or how it should
be interpreted by clients.
4. Registrant Name - the name of the person registering the value.
5. Registrant Contact Information - an email address, postal
address, or some other information to be used to contact the
registrant.
This registry should be governed by a designated expert or multiple
designated experts. Registration of values into this registry should
be accomplished by providing the information above to the designated
expert(s).
Review of registrations into this registry by the designated
expert(s) should be narrowly judged on the following criteria:
1. Values in need of being placed into multiple types must be
assigned a separate registration for each type.
2. Values must be strings. They can be multiple words separated by
single space characters. Every character should be lowercased.
If possible, every word should be given in English and each
character should be US ASCII.
3. Registrations should not duplicate the meaning of any existing
registration. That is, if a request for a registration is
significantly similar in nature to an existing registration, the
request should be denied. For example, the terms 'maintainer'
and 'registrant' are significantly similar in nature as they both
denote a holder of a domain name or Internet number resource. In
cases where it may be reasonably argued that machine
interpretation of two similar values may alter the operation of
client software, designated experts should not judge the values
to be of significant similarity.
4. Registrations should be relevant to the common usages of RDAP.
Designated experts may rely upon the serving of the value by a
DNR or RIR to make this determination.
9.1. Status
This section registers the following values into the RDAP JSON Values
Registry:
1.
* Value: validated
* Type: status
* Description: Signifies that the data of the object instance
has been found to be accurate. This type of status is usually
found on entity object instances to note the validity of
identifying contact information.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
2.
* Value: update prohibited
* Type: status
* Description: Updates to the object instance are forbidden.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
3.
* Value: transfer prohibited
* Type: status
* Description: Transfers of the registration from one registrar
to another are forbidden. This type of status normally
applies to DNR domain names.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
4.
* Value: delete prohibited
* Type: status
* Description: Deletion of the registration of the object
instance is forbidden. This type of status normally applies
to DNR domain names.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
5.
* Value: proxy
* Type: status
* Description: The registration of the object instance has been
performed by a third party. This is most commonly applied to
entities.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
6.
* Value: private
* Type: status
* Description: The information of the object instance is not
designated for public consumption. This is most commonly
applied to entities.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
7.
* Value: redacted
* Type: status
* Description: Some of the information of the object instance
has not been made available. This is most commonly applied to
entities.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
8.
* Value: obscured
* Type: status
* Description: 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.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
9.2. Event Actions
This section registers the following values into the RDAP JSON Values
Registry:
1.
* Value: registration
* Type: event action
* Description: The object instance was initially registered.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
2.
* Value: reregistration
* Type: event action
* Description: The object instance was registered subsequently
to initial registration.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
3.
* Value: last changed
* Type: event action
* Description: An action noting when the information in the
object instance was last changed.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
4.
* Value: expiration
* Type: event action
* Description: The object instance has been removed or will be
removed at a pre-determined date and time from the registry.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
5.
* Value: deletion
* Type: event action
* Description: The object instance was removed from the registry
at a point in time that was not pre-determined.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
6.
* Value: reinstantiation
* Type: event action
* Description: The object instance was reregistered after having
been removed from the registry.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
7.
* Value: transfer
* Type: event action
* Description: The object instance was transferred from one
registrant to another.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
9.3. Roles
This section registers the following values into the RDAP JSON Values
Registry:
1.
* Value: registrant
* Type: role
* Description: The entity object instance is the registrant of
the registration. In some registries, this is known as a
maintainer.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
2.
* Value: tech
* Type: role
* Description: The entity object instance is a technical contact
for the registration.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
3.
* Value: administrative
* Type: role
* Description: The entity object instance is an administrative
contact for the registration.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
4.
* Value: abuse
* Type: role
* Description: The entity object instance handles network abuse
issues on behalf of the registrant of the registration.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
5.
* Value: billing
* Type: role
* Description: The entity object instance handles payment and
billing issues on behalf of the registrant of the
registration.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
6.
* Value: registrar
* Type: role
* Description: The entity object instance represents the
authority responsible for the registration in the registry.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
7.
* Value: reseller
* Type: role
* Description: The entity object instance represents a third
party through which the registration was conducted (i.e. not
the registry or registrar).
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
8.
* Value: sponsor
* Type: role
* Description: The entity object instance represents a domain
policy sponsor, such as an ICANN approved sponsor.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
9.
* Value: proxy
* Type: role
* Description: The entity object instance represents a proxy for
another entity object, such as a registrant.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
9.4. Variant Relations
This section registers the following values into the RDAP JSON Values
Registry:
1.
* Value: registered
* Type: domain variant relation
* Description: The variant names are registered in the registry.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
2.
* Value: unregistered
* Type: domain variant relation
* Description: The variant names are not found in the registry.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
3.
* Value: registration restricted
* Type: domain variant relation
* Description: Registration of the variant names is restricted
to certain parties or within certain rules.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
4.
* Value: open registration
* Type: domain variant relation
* Description: Registration of the variant names is available to
generally qualified registrants.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
5.
* Value: conjoined
* Type: domain variant relation
* Description: Registration of the variant names occurs
automatically with the registration of the containing domain
registration.
* Registrant Name: Andrew Newton
* Registrant Contact Information: andy@hxr.us
10. Security Considerations
This specification models information serialized in JSON format. As This specification models information serialized in JSON format. As
JSON is a subset of Javascript, implementations are advised to follow JSON is a subset of Javascript, implementations are advised to follow
the security considerations outlined in Section 6 of [RFC4627] to the security considerations outlined in Section 6 of [RFC4627] to
prevent code injection. prevent code injection.
10. Internationalization Considerations 11. Internationalization Considerations
10.1. Character Encoding 11.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
UTF-8, and all servers and clients MUST support UTF-8. Servers and [RFC3629], and all servers and clients MUST support UTF-8. Servers
clients MAY optionally support other character encodings. and clients MAY optionally support other character encodings.
10.2. URIs and IRIs 11.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.
10.3. Language Tags 11.3. Language Tags
Section 5.4 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.
10.4. Internationalized Domain Names 11.4. Internationalized Domain Names
Internationalized Domain Names (IDNs) are denoted in this Internationalized Domain Names (IDNs) are denoted in this
specification by the separation of DNS names in LDH form and Unicode specification by the separation of DNS names in LDH form and Unicode
form (see Section 4). Representation of IDNs in registries is form (see Section 4). Representation of IDNs in registries is
described by the "variants" object in Section 6.3 and the suggested described by the "variants" object in Section 6.3 and the suggested
values listed in Appendix A.4. values listed in Section 9.4.
12. Privacy Considerations
11. Privacy Considerations
This specification suggests status values to denote contact and This specification suggests status values to denote contact and
registrant information that has been marked as private and/or has registrant information that has been marked as private and/or has
been redacted or obscured. See Appendix A.1 for the list of status been redacted or obscured. See Section 9.1 for the list of status
values. See Appendix B.1 on guidance to apply those values to values. See Appendix A.1 on guidance to apply those values to
contacts and registrants. contacts and registrants.
12. Contributing Authors and Acknowledgements 13. Contributing Authors and Acknowledgements
This document is derived from original work on RIR responses in JSON This document is derived from original work on RIR responses in JSON
by Byron J. Ellacott, Arturo L. Servin, Kaveh Ranjbar, and Andrew by Byron J. Ellacott, Arturo L. Servin, Kaveh Ranjbar, and Andrew L.
L. Newton. Additionally, this document incorporates word on DNR Newton. Additionally, this document incorporates word on DNR
responses in JSON by Ning Kong, Linlin Zhou, Jiagui Xie, and Sean responses in JSON by Ning Kong, Linlin Zhou, Jiagui Xie, and Sean
Shen. 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, Steve Sheng and Francisco Arias, Ray Zhou, and Guangqing Deng, Steve Sheng and Francisco Arias, Ray
Bellis, and Frederico Neves. Bellis, and Frederico Neves.
Ed Lewis contributed significant review comments and provided Ed Lewis contributed significant review comments and provided
clarifying text. James Mitchel provided text regarding the clarifying text. James Mitchell provided text regarding the
processing of unknown JSON attributes and identified issues leading processing of unknown JSON attributes and identified issues leading
to the remodeling of events. Ernie Dainow and Francisco Obispo to the remodeling of events. Ernie Dainow and Francisco Obispo
provided concrete suggestions that led to a better variant model for provided concrete suggestions that led to a better variant model for
domain names. domain names.
Ernie Dainow provided the background information on the secure DNSSEC
attributes and objects for domains, informative text on DNSSEC, and
many other attributes that appear throughout the object classes of
this draft.
The switch to and incorporation of JSON vCard was performed by Simon The switch to and incorporation of JSON vCard was performed by Simon
Perreault. Perreault.
13. References 14. References
13.1. Normative References 14.1. Normative References
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, September
1981. 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.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, November 2003.
[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, RFC Resource Identifier (URI): Generic Syntax", STD 66, 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.
skipping to change at page 38, line 41 skipping to change at page 57, line 14
[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] [I-D.kewisch-vcard-in-json]
Kewisch, P., "jCard: The JSON format for vCard", draft- Kewisch, P., "jCard: The JSON format for vCard", draft-
kewisch-vcard-in-json-01 (work in progress), March 2013. kewisch-vcard-in-json-01 (work in progress), March 2013.
[I-D.ietf-weirds-using-http]
Newton, A., Ellacott, B., and N. Kong, "HTTP usage in the
Registration Data Access Protocol (RDAP)", draft-ietf-
weirds-using-http-05 (work in progress), May 2013.
[I-D.ietf-weirds-rdap-query]
Newton, A. and S. Hollenbeck, "Registration Data Access
Protocol Lookup Format", draft-ietf-weirds-rdap-query-05
(work in progress), June 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] 14.2. Informative References
Newton, A. and S. Hollenbeck, "RDAP Query Format", draft-
ietf-weirds-rdap-query-00 (work in progress), September
2011.
[I-D.ietf-weirds-using-http]
Newton, A., Ellacott, B., and N. Kong, "Using HTTP for
RESTful Whois Services by Internet Registries", draft-
ietf-weirds-using-http-01 (work in progress), May 2012.
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.
[RFC5910] Gould, J. and S. Hollenbeck, "Domain Name System (DNS)
Security Extensions Mapping for the Extensible
Provisioning Protocol (EPP)", RFC 5910, May 2010.
[RFC6530] Klensin, J. and Y. Ko, "Overview and Framework for
Internationalized Email", RFC 6530, February 2012.
[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,
Montana State University - Bozeman, "Comparison of JSON Montana State University - Bozeman, "Comparison of JSON
and XML Data Interchange Formats: A Case Study", 2009. and XML Data Interchange Formats: A Case Study", 2009.
Appendix A. Suggested Values Appendix A. Suggested Data Modeling with the Entity Object Class
Due to the wide variation between the hundreds of registry operators
and the on-going policy refinement by registry communities, values of
some data cannot be formally standardized. This section lists
suggested values for such data but is not nor will ever be a complete
list of values and their meanings.
A.1. Status
Many of the object classes have a member named 'status'. This member
is an array of strings, with each string denoting a status associated
with the containing object. The following is a list of suggested
values to use in the 'status' array:
o 'validated' -- Signifies that the data of the object instance has
been found to be accurate. This type of status is usually found
on entity object instances to note the validity of identifying
contact information.
o 'update prohibited' -- Updates to the object instance are
forbidden.
o 'transfer prohibited' -- Transfers of the registration from one
registrar to another are forbidden. This type of status normally
applies to DNR domain names.
o 'delete prohibited' -- Deletion of the registration of the object
instance is forbidden. This type of status normally applies to
DNR domain names.
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
array of strings, with each string indicating the role or
relationship the entity object instance has with a containing object,
such as a domain name or IP network. An entity object instance can
have more than one type of relationship with a containing object.
The following is a list of suggested values to use in the 'roles'
array:
o 'registrant' -- The entity object instance is the registrant of
the registration.
o 'tech' -- The entity object instance is a technical contact for
the registration.
o 'admin' -- The entity object instance is an administrative contact
for the registration.
o 'abuse' -- The entity object instance handles network abuse issues
on behalf of the registrant of the registration.
o 'billing' -- The entity object instance handles payment and
billing issues on behalf of the registrant of the registration.
o 'registrar' -- The entity object instance represents the authority
responsible for the registration in the registry.
o 'reseller' -- The entity object instance represents a third party
through which the registration was conducted (i.e. not the
registry or registrar).
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
name. The following is a list of suggested values to use as the
variant relation values:
o 'registered' -- the variant names are registered in the registry.
o 'unregistered' -- the variant names are not found in the registry.
o 'restricted registration' -- registration of the variant names is
restricted to certain parties or within certain rules.
o 'open registration' -- registration of the variant names is
available to generally qualified registrants.
o 'conjoined' -- registration of the variant names is occurs
automatically with the registration of the containing domain
registration.
Appendix B. Suggested Data Modeling with the Entity Object Class
B.1. Registrants and Contacts A.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.3 be relationship. It is recommended that the values from Section 9.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",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "Joe Bob, Inc." ], ["version", {}, "text", "4.0"],
[ "fn", {}, "text", "Bobby Joe Shopping" ], ["fn", {}, "text", "Joe User"],
[ "label", {}, "text", "123 Maple Ave\n", ["kind", {}, "text", "individual"],
"Suite 90001\n", ["lang", {
"Vancouver\n", "pref":"1"
"BC\n", }, "language-tag", "fr"],
"1239\n" ], ["lang", {
[ "email", {}, "text", "joe at bob.com" ], "pref":"2"
[ "email", {}, "text", "bob at joe.com" ], }, "language-tag", "en"],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ], ["org", {
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ], "type":"work"
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ], }, "text", "Example"],
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ], ["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
],
]
], ],
"roles" : [ "registrant", "admin" ], "roles" : [ "registrant", "admin" ],
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
], ],
"events" : "events" :
skipping to change at page 43, line 32 skipping to change at page 59, line 47
"eventDate" : "1991-12-31T23:59:60Z" "eventDate" : "1991-12-31T23:59:60Z"
} }
] ]
} }
] ]
} }
In many use cases, it is necessary to hide or obscure the information In many use cases, it is necessary to hide or obscure the information
of a registrant or contact due to policy or other operational of a registrant or contact due to policy or other operational
matters. Registries can denote these situations with 'status' values matters. Registries can denote these situations with 'status' values
(see Appendix A.1). (see Section 9.1).
The following is an elided example of a registrant with information The following is an elided example of a registrant with information
changed to reflect that of a third party. changed to reflect that of a third party.
{ {
... ...
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
... ...
"roles" : [ "registrant", "admin" ], "roles" : [ "registrant", "admin" ],
"status" : [ "proxy", "private", "obscured" ] "status" : [ "proxy", "private", "obscured" ]
} }
] ]
} }
B.2. Registrars A.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 A.1) the
'roles' string array maybe used. 'roles' string array maybe used. Additionally, many registrars have
publicly assigned identifiers. The 'publicIds' structure
(Section 5.8) represents that information.
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",
"vCard" : "vcardArray":[
[ "vcard",
[ "version", {}, "text", "4.0" ], [
[ "fn", {}, "text", "RegistrarsRUS" ], ["version", {}, "text", "4.0"],
[ "label", {}, "text", "1212 Tulip Ave\n", ["fn", {}, "text", "Joe User"],
"Suite 1\n", ["kind", {}, "text", "individual"],
"Marina Del Rey\n", ["lang", {
"CA\n", "pref":"1"
"12393-2193" ], }, "language-tag", "fr"],
[ "email", {}, "text", "joe at bob.com" ], ["lang", {
[ "email", {}, "text", "bob at joe.com" ], "pref":"2"
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4321" ], }, "language-tag", "en"],
[ "tel", { "type": "work" }, "uri", "tel:+1-958-555-4322" ],
[ "tel", { "type": "fax" }, "uri", "tel:+1-958-555-4323" ], ["org", {
[ "tel", { "type": "cell" }, "uri", "tel:+1-958-555-4324" ], "type":"work"
}, "text", "Example"],
["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
],
["tel",
{
"type":["work", "voice"],
"pref":"1"
},
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
],
]
], ],
"roles" : [ "registrar" ], "roles":[ "registrar" ],
"remarks" : "publicIds":[
[
{ {
"description" : "type":"IANA Registrar ID",
[ "identifier":"1"
}
],
"remarks":[
{
"description":[
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "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. Modeling Events Appendix B. Modeling Events
Events represent actions that have taken place against a registered Events represent actions that have taken place against a registered
object at a certain date and time. Events have three properties: the object at a certain date and time. Events have three properties: the
action, the actor, and the date and time of the event (which is action, the actor, and the date and time of the event (which is
sometimes in the future). In some cases the identity of the actor is sometimes in the future). In some cases the identity of the actor is
not captured. not captured.
Events can be modeled in three ways: Events can be modeled in three ways:
1. events with no designated actor 1. events with no designated actor
skipping to change at page 46, line 34 skipping to change at page 62, line 43
This is an example of an "events" array without the 'eventActor'. This is an example of an "events" array without the 'eventActor'.
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
} }
] ]
Figure 15 Figure 20
For the second use case, the 'events' data structure (Section 5.5) is For the second use case, the 'events' data structure (Section 5.5) is
used with the 'eventActor' object member. used with the 'eventActor' object member.
This is an example of an "events" array with the 'eventActor'. This is an example of an "events" array with the 'eventActor'.
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventActor" : "XYZ-NIC", "eventActor" : "XYZ-NIC",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
} }
] ]
Figure 16 Figure 21
For the third use case, the 'asEventActor' array is used when an For the third use case, the 'asEventActor' array is used when an
entity (Section 6.1) is embedded into another object class. The entity (Section 6.1) is embedded into another object class. The
'asEventActor' array follows the same structure as the 'events' array 'asEventActor' array follows the same structure as the 'events' array
but does not have 'eventActor' attributes. but does not have 'eventActor' attributes.
The following is an elided example of a domain object with an entity The following is an elided example of a domain object with an entity
as an event actor. as an event actor.
{ {
skipping to change at page 47, line 34 skipping to change at page 64, line 5
[ [
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1990-12-31T23:59:60Z" "eventDate" : "1990-12-31T23:59:60Z"
} }
] ]
} }
] ]
} }
Appendix D. Motivations for Using JSON Appendix C. Structured vs Unstructured Addresses
The entity (Section 6.1) object class uses jCard
[I-D.kewisch-vcard-in-json] to represent contact information,
including postal addresses. jCard has the ability to represent
multiple language preferences, multiple email address and phone
numbers, and multiple postal addresses in both a structured and
unstructured format. This section describes the use of jCard for
representing structured and unstructured addresses.
The following is an example of a jCard.
{
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["n", {}, "text",
["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
],
["bday", {}, "date-and-or-time", "--02-03"],
["anniversary",
{}, "date-and-or-time", "2009-08-08T14:30:00-05:00"
],
["gender", {}, "text", "M"],
["kind", {}, "text", "individual"],
["lang", {
"pref":"1"
}, "language-tag", "fr"],
["lang", {
"pref":"2"
}, "language-tag", "en"],
["org", {
"type":"work"
}, "text", "Example"],
["title", {}, "text", "Research Scientist"],
["role", {}, "text", "Project Lead"],
["adr",
{ "type":"work" },
"text",
[
"",
"Suite 1234",
"4321 Rue Somewhere",
"Quebec",
"QC",
"G1V 2M2",
"Canada"
]
],
["adr",
{
"type":"home",
"label":"123 Maple Ave\nSuite 90001\nVancouver\nBC\n1239\n"
},
"text",
[
"", "", "", "", "", "", ""
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["tel",
{
"type":["work", "cell", "voice", "video", "text"]
},
"uri",
"tel:+1-555-555-1234"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
],
["geo", {
"type":"work"
}, "uri", "geo:46.772673,-71.282945"],
["key",
{ "type":"work" },
"uri", "http://www.example.com/joe.user/joe.asc"
],
["tz", {},
"utc-offset", "-05:00"],
["url", { "type":"home" },
"uri", "http://example.org"]
]
]
}
Figure 22
The arrays in Figure 22 with the first member of "adr" represent
postal addresses. In the first example, the postal address is given
as a an array of strings and constitutes a structured address. For
components of the structured address that are not applicable, an
empty string is given. Each member of that array aligns with the
positions of a vCard as given in [RFC6530]. In this example, the
following data corresponds to the following positional meanings:
1. post office box - not applicable, empty string
2. extended address (e.g., apartment or suite number) - Suite 1234
3. street address - 4321 Rue Somewhere
4. locality (e.g., city) - Quebec
5. region (e.g., state or province) - QC
6. postal code - G1V 2M2
7. country name (full name) - Canada
The second example is an unstructured address. It uses the label
attribute, which is a string containing a newline (\n) character to
separate address components in an unordered, unspecified manner.
Note that in this example the structured address array is still given
but that each string is an empty string.
Appendix D. Secure DNS
Section 6.3 defines the "secureDNS" member to represent secure DNS
information about domain names.
DNSSEC provides data integrity for DNS through digital signing of
resource records. To enable DNSSEC, the zone is signed by one or
more private keys and the signatures stored as RRSIG records. To
complete the chain of trust in the DNS zone hierarchy, a digest of
each DNSKEY record (which contains the public key) must be loaded
into the parent zone, stored as Delegation Signer (DS) records and
signed by the parent's private key (RRSIG DS record), "Resource
Records for the DNS Security Extensions" [RFC4034]. Creating the DS
records in the parent zone can be done by the registration authority,
"Domain Name System (DNS) Security Extensions Mapping for the
Extensible Provisioning Protocol (EPP)" [RFC5910].
Only DS related information is provided by RDAP, since other
information is not generally stored in the registration database.
Other DNSSEC related information can be retrieved with other DNS
tools such as dig.
The domain object class (Section 6.3) can represent this information
using either the 'dsData' or 'keyData' object arrays. Client
implementers should be aware that some registries do not collect or
do not publish all of the secure DNS meta-information.
Appendix E. 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 influence 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
skipping to change at page 48, line 19 skipping to change at page 67, line 46
not a universal 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 E. Changelog Appendix F. 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 relationship 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
skipping to change at page 50, line 24 skipping to change at page 70, line 4
Added 'asEventActor' to entities Added 'asEventActor' to entities
Added appendix on event modeling Added appendix on event modeling
Removed the subclasses/superclassing between RIRs/DNRs for Removed the subclasses/superclassing between RIRs/DNRs for
entity and domain object classes entity and domain object classes
Change suggested status/relation/etc values to be case/spacing Change suggested status/relation/etc values to be case/spacing
consistent consistent
Normalized some of the definitions of object class members Normalized some of the definitions of object class members
Modifying the JSON signaling section to reference the guidance Modifying the JSON signaling section to reference the guidance
in draft-ietf-weirds-using-http in draft-ietf-weirds-using-http
Changed the text regarding the process of unknown JSON Changed the text regarding the process of unknown JSON
attributes attributes
Authors' Addresses -04
'description' removed from IP network and autnum because it is
redundant with the remarks structure.
Added 'entities' array to nameservers.
Added 'status' to autnum.
Added 'publicIds' to entity and domain.
Added embedded entities to the entity object class.
Added 'idnTable' to variants objects in domain object class.
Changed the numbers for startNum and endNum in autnum to
numbers instead of strings.
Added an example for error response with full rdapConformance
and notices.
Added a section discussing help.
Changed entities to use vcardArray and changed the examples to
be current with jCard.
Added a section on structured vs unstructured addresses.
Added associated to the list of status values.
Added a secure DNS section changed the 'delegationKey' object
into the 'secureDNS' object.
Changed the suggested values to an IANA registry.
Added 'proxy' to the list of entity roles.
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
Scott Hollenbeck Scott Hollenbeck
Verisign Labs Verisign Labs
12061 Bluemont Way 12061 Bluemont Way
Reston, VA 20190 Reston, VA 20190
US US
Email: shollenbeck@verisign.com Email: shollenbeck@verisign.com
URI: http://www.verisignlabs.com/ URI: http://www.verisignlabs.com/
 End of changes. 144 change blocks. 
489 lines changed or deleted 1517 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/