]> Verisign Labs

12061 Bluemont Way Reston, VA 20190 United States shollenbeck@verisign.com https://www.verisignlabs.com/

Amazon Web Services, Inc.

13200 Woodland Park Road Herndon VA 20171 United States of America andy@hxr.us

Applications and Real-Time REGEXT Working Group This document describes JSON data structures representing registration information maintained by Regional Internet Registries (RIRs) and Domain Name Registries (DNRs). These data structures are used to form Registration Data Access Protocol (RDAP) query responses.

This document describes responses in the JSON format for the queries as defined by the Registration Data Access Protocol Query Format . A communication protocol for exchanging queries and responses is described in .

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in when specified in their uppercase forms. The following list describes terminology and definitions used throughout this document: Domain Name Registry or Domain Name Registrar letters, digits, hyphen data found within an object as defined by JSON a data structure as defined by JSON the definition of members that may be found in JSON objects described in this document an instantiation or specific instance of an object class Registration Data Access Protocol Regional Internet Registry

The data model for JSON responses is specified in five sections: simple data types conveyed in JSON primitive types (strings, numbers, booleans, and null) data structures specified as JSON arrays or objects that are used repeatedly when building up larger objects object classes representing structured data corresponding to a lookup of a single object arrays of objects representing structured data corresponding to a search for multiple objects the response to an error The object classes represent responses for two major categories of data: responses returned by RIRs for registration data related to IP addresses, reverse DNS names, and Autonomous System numbers and responses returned by DNRs for registration data related to forward DNS names. The following object classes are returned by both RIRs and DNRs: domains nameservers entities The information served by both RIRs and DNRs for these object classes overlap extensively and are given in this document as a unified model for both classes of service. In addition to the object classes listed above, RIRs also serve the following object classes: IP networks Autonomous System numbers Object classes defined in this document represent a minimal set of what a compliant client/server needs to understand to function correctly; however, some deployments may want to include additional object classes to suit individual needs. Anticipating this need for extension, Section 2.1 of this document defines a mechanism for extending the JSON objects that are described in this document. Positive responses take two forms. A response to a lookup of a single object in the registration system yields a JSON object, which is the subject of the lookup. A response to a search for multiple objects yields a JSON object that contains an array of JSON objects that are the subject of the search. In each type of response, other data structures are present within the topmost JSON object.

Clients of these JSON responses SHOULD ignore unrecognized JSON members in responses. Servers can insert members into the JSON responses, which are not specified in this document, but that does not constitute an error in the response. Servers that insert such unspecified members into JSON responses SHOULD have member names prefixed with a short identifier followed by an underscore followed by a meaningful name. It has been observed that these short identifiers aid software implementers with identifying the specification of the JSON member, and failure to use one could cause an implementer to assume the server is erroneously using a name from this specification. This allowance does not apply to jCard objects. The full JSON name (the prefix plus the underscore plus the meaningful name) SHOULD adhere to the character and name limitations of the prefix registry described in . Failure to use these limitations could result in slower adoption as these limitations have been observed to aid some client programming models. Consider the following JSON response with JSON members, all of which are specified in this document.

If The Registry of the Moon desires to express information not found in this specification, it might select "lunarNIC" as its identifying prefix and insert, as an example, the member named "lunarNIC_beforeOneSmallStep" to signify registrations occurring before the first moon landing and the member named "lunarNIC_harshMistressNotes" that contains other descriptive text. Consider the following JSON response with JSON names, some of which should be ignored by clients without knowledge of their meaning.

Insertion of unrecognized members ignored by clients may also be used for future revisions to this specification. Clients processing JSON responses need to be prepared for members representing registration data specified in this document to be absent from a response. In other words, servers are free to omit unrequired/optional JSON members containing registration data based on their own policies. Finally, all JSON names specified in this document are case sensitive. Both servers and clients MUST transmit and process them using the specified character case.

JSON defines the data types of a number, character string, boolean, array, object, and null. This section describes the semantics and/or syntax reference for common, JSON character strings used in this document. DNRs and RIRs have registry-unique identifiers that may be used to specifically reference an object instance. The semantics of this data type as found in this document are to be a registry-unique reference to the closest enclosing object where the value is found. The data type names "registryId", "roid", "nic-handle", "registrationNo", etc., are terms often synonymous with this data type. In this document, the term "handle" is used. The term exposed to users by clients is a presentation issue beyond the scope of this document. This value is a simple string. The representation of IPv4 addresses in this document uses the dotted-decimal notation. An example of this textual representation is "192.0.2.0". The representation of IPv6 addresses in this document follow the forms outlined in . An example of this textual representation is "2001:db8::1:0:0:1". Where the identity of a geopolitical nation or country is needed, these identities are represented with the alpha-2 or two-character country code designation as defined in . The alpha-2 representation is used because it is freely available, whereas the alpha-3 and numeric-3 standards are not. Textual representations of DNS names where the labels of the domain are all "letters, digits, hyphen" labels as described by . Trailing periods are optional. Textual representations of DNS names where one or more of the labels are U-labels as described by . Trailing periods are optional. The syntax for values denoting dates and times is defined in . The syntax for values denoting a Uniform Resource Identifier (URI) is defined by . Contact information is defined using jCards as described in . The "fn" member is required and MUST NOT be null according to , where an empty "fn" member MAY be used when the contact name does not exist or is redacted.

This section defines common data structures used in responses and object classes.

The data structure named "rdapConformance" is an array of strings, each providing a hint as to the specifications used in the construction of the response. This data structure MUST appear in the topmost JSON object of a response. An example rdapConformance data structure:

The string literal "rdap_level_0" signifies conformance with this specification. When custom JSON values are inserted into responses, conformance to those custom specifications MUST be indicated by including a unique string literal value registered in the IANA RDAP Extensions registry specified in . For example, if the fictional Registry of the Moon wants to signify that their JSON responses are conformant with their registered extensions, the string used might be "lunarNIC_level_0". These registered values aid the identification of specifications for software implementers, and failure to use them could result in slower adoption of extensions. Example rdapConformance structure with custom extensions noted:

The "links" array is found in data structures to signify links to other resources on the Internet. The relationship of these links is defined by the IANA registry described by .

The JSON name/values of "rel", "href", "hreflang", "title", "media", and "type" correspond to values found in Section 3 of . The "value" JSON value is the context URI as described by . The "value", "rel" and "href" JSON values MUST be specified. All other JSON values are OPTIONAL. A "related" link relation MUST NOT include an "href" URI that is the same as the "self" link relation "href" URI to reduce the risk of infinite client processing loops. Internationalized Domain Names (IDNs) returned in URIs SHOULD be consistently returned in LDH name format to allow clients to process these IDNs according to their capabilities. This is an example of the "links" array as it might be found in an object class:

The "notices" and "remarks" data structures take the same form. The notices structure denotes information about the service providing RDAP information and/or information about the entire response, whereas the remarks structure denotes information about the object class that contains it (see regarding object classes). Both are arrays of objects. Each object contains a "title" string representing the title of the object, a "type" string denoting a registered type of remark or notice (see ), an array of strings named "description" for the purposes of conveying any descriptive text, and a "links" array as described in . The "description" array MUST be included. All other JSON values are OPTIONAL. An example of the notices data structure:

It is the job of the clients to determine line breaks, spacing, and display issues for sentences within the character strings of the "description" array. Each string in the "description" array contains a single complete division of human-readable text indicating to clients where there are semantic breaks. An example of the remarks data structure:

Note that objects in the "remarks" array may also have a "links" array. While the "title" and "description" fields are intended primarily for human consumption, the "type" string contains a well-known value to be registered with IANA (see ) for programmatic use. An example of the remarks data structure:

While the "remarks" array will appear in many object classes in a response, the "notices" array appears only in the topmost object of a response.

This data structure consists solely of a name/value pair, where the name is "lang" and the value is a string containing a language identifier as described in .

"lang" : "mn-Cyrl-MN"

The "lang" attribute as defined in this section MAY appear anywhere in an object class or data structure, except for in jCard objects. jCard supports similar functionality by way of the LANGUAGE property parameter (see Section 5.1 of RFC 6350 ).

This data structure represents events that have occurred on an instance of an object class (see regarding object classes). This is an example of an "events" array.

The "events" array consists of objects, each with the following members: "eventAction" -- a REQUIRED string denoting the reason for the event "eventActor" -- an OPTIONAL identifier denoting the actor responsible for the event "eventDate" -- a REQUIRED string containing the time and date the event occurred "links" -- OPTIONAL; see Events can be future dated. One use case for future dating of events is to denote when an object expires from a registry. The "links" array in this data structure is provided for references to the event actor. In order to reference an RDAP entity, a "rel" of "related" and a "type" of "application/rdap+json" is used in the link reference. See for a list of values for the "eventAction" string. See Appendix B regarding the various ways events can be modeled.

This data structure, named "status", is an array of strings indicating the state of a registered object (see for a list of values).

This data structure, a member named "port43", is a simple string containing the fully qualified host name or IP address of the WHOIS server where the containing object instance may be found. Note that this is not a URI, as there is no WHOIS URI scheme.

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 REQUIRED members: type -- a string denoting the type of public identifier identifier -- a string denoting a public identifier of the type related to "type" The following is an example of a publicIds structure.

This data structure, a member named "objectClassName", gives the object class name of a particular object as a string. This identifies the type of object being processed. An objectClassName is REQUIRED in all RDAP response objects so that the type of the object can be interpreted.

This is an example response with both rdapConformance and notices embedded:

Object classes represent structures appropriate for a response from the queries specified in . Each object class contains a "links" array as specified in . For every object class instance in a response, whether the object class instance is directly representing the response to a query or is embedded in other object class instances or is an item in a search result set, servers SHOULD provide a link representing a URI for that object class instance using the "self" relationship as described in the IANA registry specified by . As explained in , this may be not always be possible for nameserver data. Clients MUST be able to process object instances without a self link. When present, clients can use the self link for caching data. Servers MAY provide more than one self link for any given object instance. Failure to provide any self link by a server may result in clients being unable to cache object class instances. Clients using self links for caching SHOULD NOT cache any object class instances where the authority of the self link is different than the authority of the server returning the data. Failing to do so might result in cache poisoning. Self links MUST contain a "type" element containing the "application/rdap+json" media type when referencing RDAP object instances as defined by this document. This is an example of the "links" array with a self link to an object class:

The entity object class appears throughout this document and is an appropriate response for the /entity/XXXX query defined in "Registration Data Access Protocol (RDAP) Query Format" . This object class represents the information of organizations, corporations, governments, non-profits, clubs, individual persons, and informal groups of people. All of these representations are so similar that it is best to represent them in JSON with one construct, the entity object class, to aid in the reuse of code by implementers. The entity object class uses jCard to represent contact information, such as postal addresses, email addresses, phone numbers and names of organizations and individuals. Many of the types of information that can be represented with jCard have no use in RDAP, such as birthdays, anniversaries, and gender. The entity object is served by both RIRs and DNRs. The following is an example of an entity that might be served by an RIR.

The entity object class can contain the following members: objectClassName -- the string "entity" handle -- a string representing a registry-unique identifier of the entity vcardArray -- a jCard with the entity's contact information roles -- an array of strings, each signifying the relationship an object would have with its closest containing object (see for a list of values) publicIds -- see entities -- an array of entity objects as defined by this section remarks -- see links -- see events -- see asEventActor -- this data structure takes the same form as the events data structure (see ), but each object in the array MUST NOT have an "eventActor" member. These objects denote that the entity is an event actor for the given events. See Appendix B regarding the various ways events can be modeled. status -- see port43 -- see networks -- an array of IP network objects as defined in autnums -- an array of autnum objects as defined in 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.

The following is an example of an entity that might be served by a DNR.

See Appendix A for use of the entity object class to model various types of entities found in both RIRs and DNRs. See Appendix C regarding structured vs. unstructured postal addresses in entities.

The nameserver object class represents information regarding DNS nameservers used in both forward and reverse DNS. RIRs and some DNRs register or expose nameserver information as an attribute of a domain name, while other DNRs model nameservers as "first class objects". The nameserver object class accommodates both models and degrees of variation in between.

Figure 18 is an example of a nameserver object with all appropriate values given. Registries using a first-class nameserver data model would embed this in domain objects as well as allowing references to it with the "/nameserver" query type (all depending on the registry operators policy). Other registries may pare back the information as needed. Figure 19 is an example of a nameserver object as would be found in RIRs and some DNRs, while Figure 20 is an example of a nameserver object as would be found in other DNRs.

The following is an example of a simple nameserver object that might be commonly used by DNRs:

As nameservers can be modeled by some registries to be first-class objects, they may also have an array of entities () 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.

The nameserver object class can contain the following members: objectClassName -- the string "nameserver" handle -- a string representing a registry-unique identifier of the nameserver ldhName -- a string containing the LDH name of the nameserver (see ) unicodeName -- a string containing a DNS Unicode name of the nameserver (see ) ipAddresses -- an object containing the following members:v6 -- an array of strings containing IPv6 addresses of the nameserver v4 -- an array of strings containing IPv4 addresses of the nameserver entities -- an array of entity objects as defined by status -- see remarks -- see links -- see port43 -- see events -- see

The domain object class represents a DNS name and point of delegation. For RIRs, these delegation points are in the reverse DNS tree, whereas for DNRs, these delegation points are in the forward DNS tree. In both cases, the high-level structure of the domain object class consists of information about the domain registration, nameserver information related to the domain name, and entities related to the domain name (e.g., registrant information, contacts, etc.). The following is an elided example of the domain object showing the high-level structure:

The domain object class can contain the following members: objectClassName -- the string "domain" handle -- a string representing a registry-unique identifier of the domain object instance ldhName -- a string describing a domain name in LDH form as described in unicodeName -- a string containing a domain name with U-labels as described in variants -- an array of objects, each containing the following values:relation -- an array of strings, with each string denoting the relationship between the variants and the containing domain object (see for a list of suggested variant relations). idnTable -- the name of the Internationalized Domain Name (IDN) table of codepoints, such as one listed with the IANA (see IDN tables ). variantNames -- an array of objects, with each object containing an "ldhName" member and a "unicodeName" member (see ). nameservers -- an array of nameserver objects as defined by secureDNS -- an object with the following members:zoneSigned -- boolean true if the zone has been signed, false otherwise. delegationSigned -- boolean true if there are DS records in the parent, false otherwise. maxSigLife -- an integer representing the signature lifetime in seconds to be used when creating the RRSIG DS record in the parent zone . dsData -- an array of objects, each with the following members:keyTag -- an integer as specified by the key tag field of a DNS DS record as specified by in presentation format algorithm -- an integer as specified by the algorithm field of a DNS DS record as described 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 links -- see keyData -- an array of objects, each with the following members:flags -- an integer representing the flags field value in the DNSKEY record in presentation format protocol -- an integer representation of the protocol field value of the DNSKEY record in presentation format publicKey -- a string representation of the public key in the DNSKEY record in presentation format algorithm -- an integer as specified by the algorithm field of a DNSKEY record as specified by in presentation format events -- see links -- see entities -- an array of entity objects as defined by status -- see publicIds -- see remarks -- see links -- see port43 -- see events -- see network -- represents the IP network for which a reverse DNS domain is referenced; see The following is an example of a JSON domain object representing a reverse DNS delegation point that might be served by an RIR.

The following is an example of a JSON domain object representing a forward DNS delegation point that might be served by a DNR.

The IP network object class models IP network registrations found in RIRs and is the expected response for the "/ip" query as defined by . There is no equivalent object class for DNRs. The high- level structure of the IP network object class consists of information about the network registration and entities related to the IP network (e.g., registrant information, contacts, etc.). The following is an elided example of the IP network object type showing the high-level structure:

The following is an example of the JSON object for the network registration information.

The IP network object class can contain the following members: objectClassName -- the string "ip network" handle -- a string representing the RIR-unique identifier of the network registration startAddress -- a string representing the starting IP address of the network, either IPv4 or IPv6 endAddress -- a string representing the ending IP address of the network, either IPv4 or IPv6 ipVersion -- a string signifying the IP protocol version of the network: "v4" signifies an IPv4 network, and "v6" signifies an IPv6 network name -- a string representing an identifier assigned to the network registration by the registration holder type -- a string containing an RIR-specific classification of the network country -- a string containing the two-character country code of the network parentHandle -- a string containing an RIR-unique identifier of the parent network of this network registration status -- an array of strings indicating the state of the IP network as defined by entities -- an array of entity objects as defined by remarks -- see links -- see port43 -- see events -- see

The Autonomous System number (autnum) object class models Autonomous System number registrations found in RIRs and represents the expected response to an "/autnum" query as defined by . There is no equivalent object class for DNRs. The high-level structure of the autnum object class consists of information about the autonomous system number registration and entities related to the autnum registration (e.g., registrant information, contacts, etc.) and is similar to the IP network object class. The following is an example of a JSON object representing an autnum.

The Autonomous System number object class can contain the following members: objectClassName -- the string "autnum" handle -- a string representing the RIR-unique identifier of the autnum registration startAutnum -- an unsigned 32-bit integer representing the starting number in the block of Autonomous System numbers endAutnum -- an unsigned 32-bit integer representing the ending number in the block of Autonomous System numbers name -- a string representing an identifier assigned to the autnum registration by the registration holder type -- a string containing an RIR-specific classification of the autnum status -- an array of strings indicating the state of the autnum as defined by country -- a string containing the two-character country code of the autnum entities -- an array of entity objects as defined by remarks -- see links -- see port43 -- see events -- see

Some non-answer responses MAY return entity bodies with information that could be more descriptive. The basic structure of that response is an object class containing a REQUIRED error code number (corresponding to the HTTP response code) followed by an OPTIONAL string named "title" and an OPTIONAL array of strings named "description". This is an example of the common response body.

This is an example of the common response body with an rdapConformance and notices data structures:

The appropriate response to /help queries as defined by is to use the notices structure as defined in . This is an example of a response to a /help query including the rdapConformance data structure.

specifies three types of searches: domains, nameservers, and entities. Responses to these searches take the form of an array of object instances where each instance is an appropriate object class for the search (i.e., a search for /domains yields an array of domain object instances). These arrays are contained within the response object. The names of the arrays are as follows: for /domains searches, the array is "domainSearchResults" for /nameservers searches, the array is "nameserverSearchResults" for /entities searches, the array is "entitySearchResults" The following is an elided example of a response to a /domains search.

In cases where the data of a response needs to be limited or parts of the data need to be omitted, the response is considered "truncated". A truncated response is still valid JSON, but some of the results in a search set or some of the data in an object are not provided by the server. A server may indicate this by including a typed notice in the response object. The following is an elided example of a search response that has been truncated.

A similar technique can be used with a typed remark where a single object has been returned and data in that object has been truncated. Such an example might be an entity object with only a partial set of the IP networks associated with it. The following is an elided example of an entity truncated data.

IANA is requested to update the description of the "transfer" event action as described in .

Type name: application Subtype name: rdap+json Required parameters: n/a Encoding considerations: See Section 3.1 of . Security considerations: The media represented by this identifier does not have security considerations beyond that found in Section 12 of . Interoperability considerations: There are no known interoperability problems regarding this media format. Published specification: RFC 7483 Applications that use this media type: Implementations of the Registration Data Access Protocol (RDAP). Additional information: This media type is a product of the IETF WEIRDS working group. The WEIRDS charter, information on the WEIRDS mailing list, and other documents produced by the WEIRDS working group can be found at . Person & email address to contact for further information: IESG <iesg@ietf.org> Intended usage: COMMON Restrictions on usage: none Author: Andy Newton Change controller: IETF Provisional Registration: No (upon publication of this RFC)

IANA has created a category in the protocol registries labeled "Registration Data Access Protocol (RDAP)", and within that category, IANA has established a URL-referenceable, stand-alone registry labeled "RDAP JSON Values". This new registry is for use in the notices and remarks (), status (), role (), event action (), and domain variant relation () fields specified in RDAP. Each entry in the registry contains the following fields: Value -- the string value being registered. Type -- the type of value being registered. It should be one of the following:"notice or remark type" -- denotes a type of notice or remark. "status" -- denotes a value for the "status" object member as defined by . "role" -- denotes a value for the "role" array as defined in . "event action" -- denotes a value for an event action as defined in . "domain variant relation" -- denotes a relationship between a domain and a domain variant as defined in . 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. Registrant Name -- the name of the person registering the value. Registrant Contact Information -- an email address, postal address, or some other information to be used to contact the registrant. This registry is operated under the "Expert Review" policy defined in . Review of registrations into this registry by the designated expert(s) should be narrowly judged on the following criteria: Values in need of being placed into multiple types must be assigned a separate registration for each type. Values must be strings. They should 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. 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. 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. The following sections provide initial registrations into this registry.

The following values have been registered in the "RDAP JSON Values" registry: Value: result set truncated due to authorization Type: notice and remark type Description: The list of results does not contain all results due to lack of authorization. This may indicate to some clients that proper authorization will yield a longer result set. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: result set truncated due to excessive load Type: notice and remark type Description: The list of results does not contain all results due to excessively heavy load on the server. This may indicate to some clients that requerying at a later time will yield a longer result set. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: result set truncated due to unexplainable reasons Type: notice and remark type Description: The list of results does not contain all results for an unexplainable reason. This may indicate to some clients that requerying for any reason will not yield a longer result set. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: object truncated due to authorization Type: notice and remark type Description: The object does not contain all data due to lack of authorization. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: object truncated due to excessive load Type: notice and remark type Description: The object does not contain all data due to excessively heavy load on the server. This may indicate to some clients that requerying at a later time will yield all data of the object. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: object truncated due to unexplainable reasons Type: notice and remark type Description: The object does not contain all data for an unexplainable reason. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org

The following values have been registered in the "RDAP JSON Values" registry: 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: IESG Registrant Contact Information: iesg@ietf.org Value: renew prohibited Type: status Description: Renewal or reregistration of the object instance is forbidden. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: update prohibited Type: status Description: Updates to the object instance are forbidden. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org Value: removed Type: status Description: Some of the information of the object instance has not been made available and has been removed. This is most commonly applied to entities. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org Value: associated Type: status Description: The object instance is associated with other object instances in the registry. This is most commonly used to signify that a nameserver is associated with a domain or that an entity is associated with a network resource or domain. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: active Type: status Description: The object instance is in use. For domain names, it signifies that the domain name is published in DNS. For network and autnum registrations it signifies that they are allocated or assigned for use in operational networks. This maps to the Extensible Provisioning Protocol (EPP) 'OK' status. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: inactive Type: status Description: The object instance is not in use. See 'active'. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: locked Type: status Description: Changes to the object instance cannot be made, including the association of other object instances. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: pending create Type: status Description: A request has been received for the creation of the object instance but this action is not yet complete. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: pending renew Type: status Description: A request has been received for the renewal of the object instance but this action is not yet complete. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: pending transfer Type: status Description: A request has been received for the transfer of the object instance but this action is not yet complete. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: pending update Type: status Description: A request has been received for the update or modification of the object instance but this action is not yet complete. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: pending delete Type: status Description: A request has been received for the deletion or removal of the object instance but this action is not yet complete. For domains, this might mean that the name is no longer published in DNS but has not yet been purged from the registry database. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org

The following values have been registered in the "RDAP JSON Values" registry: Value: registration Type: event action Description: The object instance was initially registered. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: reregistration Type: event action Description: The object instance was registered subsequently to initial registration. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: last changed Type: event action Description: An action noting when the information in the object instance was last changed. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org Value: reinstantiation Type: event action Description: The object instance was reregistered after having been removed from the registry. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: transfer Type: event action Description: The object instance was transferred from one registrar to another. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: locked Type: event action Description: The object instance was locked (see the 'locked' status). Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: unlocked Type: event action Description: The object instance was unlocked (see the 'locked' status). Registrant Name: IESG Registrant Contact Information: iesg@ietf.org

The following values have been registered in the "RDAP JSON Values" registry: 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: IESG Registrant Contact Information: iesg@ietf.org Value: technical Type: role Description: The entity object instance is a technical contact for the registration. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: administrative Type: role Description: The entity object instance is an administrative contact for the registration. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: abuse Type: role Description: The entity object instance handles network abuse issues on behalf of the registrant of the registration. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: billing Type: role Description: The entity object instance handles payment and billing issues on behalf of the registrant of the registration. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: registrar Type: role Description: The entity object instance represents the authority responsible for the registration in the registry. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org 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: IESG Registrant Contact Information: iesg@ietf.org Value: sponsor Type: role Description: The entity object instance represents a domain policy sponsor, such as an ICANN approved sponsor. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: proxy Type: role Description: The entity object instance represents a proxy for another entity object, such as a registrant. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: notifications Type: role Description: An entity object instance designated to receive notifications about association object instances. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: noc Type: role Description: The entity object instance handles communications related to a network operations center (NOC). Registrant Name: IESG Registrant Contact Information: iesg@ietf.org

The following values have been registered in the "RDAP JSON Values" registry: Value: registered Type: domain variant relation Description: The variant names are registered in the registry. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: unregistered Type: domain variant relation Description: The variant names are not found in the registry. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: registration restricted Type: domain variant relation Description: Registration of the variant names is restricted to certain parties or within certain rules. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: open registration Type: domain variant relation Description: Registration of the variant names is available to generally qualified registrants. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org Value: conjoined Type: domain variant relation Description: Registration of the variant names occurs automatically with the registration of the containing domain registration. Registrant Name: IESG Registrant Contact Information: iesg@ietf.org

NOTE: Please remove this section and the reference to RFC 7942 prior to publication as an RFC. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in RFC 7942 . The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to RFC 7942, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit".

Responsible Organization: NIC Mexico Location: https://reddog.mx/ Description: RedDog implements all the functionality of an RDAP Server defined in RFCs 7480,7481,7482 and 7483. RedDog is highly configurable and extensible to fit the needs of the developers and operators. Level of Maturity: Production. Coverage: RedDog supports all lookups, searches and responses for all object classes described in RFC 7482 and RFC 7483. Version Compatibility: RFC 7482 and RFC 7483 Licensing: Apache License 2.0 Contact Information: reddog-dev@nic.mx Information last updated: November 22, 2019

Responsible Organization: Verisign Location: https://rdap.verisign.com/com/v1/, https://rdap.verisign.com/net/v1/ Description: Verisign's production RDAP service for the .com and .net gTLDs. Level of Maturity: Production. Coverage: Lookup of domain names, name servers, entities; name server search by IP address; help. Version Compatibility: RFC 7483 Contact Information: info@verisign-grs.com

Responsible Organization: Verisign Labs Location: https://rdap.verisignlabs.com/rdap/v1/ Description: Verisign's experimental RDAP service for the .cc and .tv ccTLDs. Level of Maturity: Experimental. Coverage: Lookup of domain names, name servers, entities; name server search by IP address; basic search; regular expression search; federated authentication; help. Version Compatibility: RFC 7483 Contact Information: Scott Hollenbeck, shollenbeck@verisign.com

Responsible Organization: Asia-Pacific Network Information Centre (APNIC) Location: https://rdap.apnic.net/, https://github.com/APNIC-net/rdapd Description: APNIC's production RDAP service for Internet number resouces. Level of Maturity: Production. Coverage: Lookup of IP networks, AS numbers, domains, and entities. Also domain search by name, entity search by handle or full name, and help responses. Version Compatibility: RFC 7483 Contact Information: helpdesk@apnic.net

This specification models information serialized in JSON format. As JSON is a subset of JavaScript, implementations are advised to follow the security considerations outlined in Section 12 of to prevent code injection. Though not specific to JSON, RDAP implementers should be aware of the security considerations specified in and the security requirements and considerations in . Clients caching data, especially clients using RDAP-specific caches (instead of HTTP-layer caches), should have safeguards to prevent cache poisoning. See for advice on using the self links for caching. Finally, service operators should be aware of the privacy mechanisms noted in .

The default text encoding for JSON responses in RDAP is UTF-8 , and all servers and clients MUST support UTF-8.

defines the use of URIs and IRIs in RDAP.

defines the use of language tags in the JSON responses defined in this document.

IDNs are denoted in this specification by the separation of DNS names in LDH form and Unicode form (see ). Representation of IDNs in registries is described by the "variants" object in and the suggested values listed in .

This specification suggests status values to denote contact and registrant information that has been marked as private and/or has been removed or obscured. See for the complete list of status values. A few of the status values indicate that there are privacy concerns associated with the object instance. The following status codes SHOULD be used to describe data elements of a response when appropriate: private -- The object is not be shared in query responses, unless the user is authorized to view this information. removed -- Data elements within the object have been collected but have been omitted from the response. This option can be used to prevent unauthorized access to associated object instances without the need to mark them as private. obscured -- Data elements within the object have been collected, but the response value has been altered so that values are not easily discernible. A value changed from "1212" to "XXXX" is an example of obscured data. This option may reveal privacy sensitive information and should only be used when data sensitivity does not require a more protective option like "private" or "removed". See Appendix A.1 for an example of applying those values to contacts and registrants.

International Organization for Standardization &RFC2119; &RFC3339; &RFC3629; &RFC3986; &RFC4034; &RFC5396; &RFC5646; &RFC5890; &RFC5952; &RFC7095; &RFC7480; &RFC7481; &RFC8126; &RFC8259; &RFC8288; &I-D.ietf-regext-rfc7482bis; IANA &RFC3912; &RFC5730; &RFC5910; &RFC6350; &RFC6839; &RFC7942;

This document does not provide specific object classes for registrants and contacts. Instead, the entity object class may be used to represent a registrant or contact. When the entity object is embedded inside a containing object such as a domain name or IP network, the "roles" string array can be used to signify the relationship. It is recommended that the values from be used. The following is an example of an elided containing object with an embedded entity that is both a registrant and administrative contact:

In many use cases, it is necessary to hide or obscure the information of a registrant or contact due to policy or other operational matters. Registries can denote these situations with "status" values (see ). The following is an elided example of a registrant with information changed to reflect that of a third party.

This document does not provide a specific object class for registrars, but like registrants and contacts (see Appendix A.1), the "roles" string array maybe used. Additionally, many registrars have publicly assigned identifiers. The publicIds structure () represents that information. The following is an example of an elided containing object with an embedded entity that is a registrar:

Events represent actions that have taken place against a registered 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 sometimes in the future). In some cases, the identity of the actor is not captured. Events can be modeled in three ways: events with no designated actor events where the actor is only designated by an identifier events where the actor can be modeled as an entity For the first use case, the events data structure () is used without the "eventActor" object member. This is an example of an "events" array without the "eventActor".

For the second use case, the events data structure () is used with the "eventActor" object member. This is an example of an "events" array with the "eventActor".

For the third use case, the "asEventActor" array is used when an entity () is embedded into another object class. The "asEventActor" array follows the same structure as the "events" array but does not have "eventActor" attributes. The following is an elided example of a domain object with an entity as an event actor.

The entity () object class uses jCard 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.

The arrays in Figure 40 with the first member of "adr" represent postal addresses. In the first example, the postal address is given as 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 . In this example, the following data corresponds to the following positional meanings: post office box -- not applicable; empty string extended address (e.g., apartment or suite number) -- Suite 1234 street address -- 4321 Rue Somewhere locality (e.g., city) -- Quebec region (e.g., state or province) -- QC postal code -- G1V 2M2 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.

defines the "secureDNS" member to represent secure DNS information about domain names. DNSSEC provides data integrity for DNS through the digital signing of resource records. To enable DNSSEC, the zone is signed by one or more private keys and the signatures are 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 DS records, and signed by the parent's private key (RRSIG DS record), as indicated in "Resource Records for the DNS Security Extensions" . 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)" . 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 () 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.

This section addresses a common question regarding the use of JSON over other data formats, most notably XML. It is often pointed out that many DNRs and one RIR support the EPP standard, which is an XML serialized protocol. The logic 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 this specification quite a bit, EPP serves a different purpose, which is the provisioning of Internet resources between registries and accredited registrars and serving a much narrower audience than that envisioned for RDAP. By contrast, RDAP has a broader audience and is designed for public consumption of data. Experience from RIRs with first generation RESTful web services for WHOIS indicate that a large percentage of clients operate within browsers and other platforms where full-blown XML stacks are not readily available and where JSON is a better fit. Additionally, while EPP is used in much of the DNR community it is not a universal constant in that industry. And finally, EPP's use of XML predates the specification of JSON. If EPP had been defined today, it may very well have used JSON instead of XML. Beyond the specific DNR and RIR communities, the trend in the broader Internet industry is also switching to JSON over XML, especially in the area of RESTful web services (see ). Studies have also found that JSON is generally less bulky and consequently faster to parse (see ).

This document is derived from original work on RIR responses in JSON by Byron J. Ellacott, Arturo L. Servin, Kaveh Ranjbar, and Andrew L. Newton. Additionally, this document incorporates work on DNR responses in JSON by Ning Kong, Linlin Zhou, Jiagui Xie, and Sean Shen. The components of the DNR object classes are derived from a categorization of WHOIS response formats created by Ning Kong, Linlin Zhou, Guangqing Deng, Steve Sheng, Francisco Arias, Ray Bellis, and Frederico Neves. Tom Harrison, Murray Kucherawy, Ed Lewis, Audric Schiltknecht, Naoki Kambe, Maarten Bosteels, Mario Loffredo, and Jasdip Singh contributed significant review comments and provided clarifying text. James Mitchell provided text regarding the processing of unknown JSON attributes and identified issues leading to the remodeling of events. Ernie Dainow and Francisco Obispo provided concrete suggestions that led to a better variant model for domain names. Ernie Dainow provided the background information on the secure DNS attributes and objects for domains, informative text on DNSSEC, and many other attributes that appear throughout the object classes of this document. The switch to and incorporation of jCard was performed by Simon Perreault. Olaf Kolkman and Murray Kucherawy chaired the IETF's WEIRDS working group from which this document was originally created. James Galvin and Antoin Verschuren chaired the REGEXT working group that worked on the -bis version.

Initial version ported from RFC 7483. Addressed known errata. Added Implementation Status section. Updated references to 7482 to 7482bis Internet-Draft. Updated "Change Log" to "Changes from RFC 7483". Added APNIC implementation status. Adjusted case of "xxxx" used in examples where "XXXX" was previously used, and removed an "X" from "XXXXX". Changed IPv6 address example using "C00" to "c00". Added "a string representing" to the definitions of startAddress and endAddress. Removed "entity" from "Autonomous System Number Entity Object Class". Added "an unsigned 32-bit integer" to the definition of startAutnum and endAutnum. Added "a string representing" to the definition of name in the IP network and ASN object classes. Clarified rdapConformance identifier registration expectations in Section 4.1. Changed "lunarNic_level_0" to "lunarNIC_level_0". Clarified that the "value", "rel" and "href" JSON values MUST be specified in the "links" array. Clarified that the "description" array is required in the Notices and Remarks data structures and other values are OPTIONAL. Noted that all members of the "events" and "Public IDs" arrays are REQUIRED. Fix "self" link values in examples. Changed "http" to "https" link values in examples. Noted that Figure 18 is an example of a nameserver object with all "appropriate" values given. In appendix C, quoted the word "label" in "label attribute". Added reference to "status" definition in the descriptions for IP networks and autnums. Fixed a 404 for the informative reference to "The Stealthy Ascendancy of JSON". Added "boolean" to the definition of zoneSigned. Clarified REQUIRED and OPTIONAL members of the "events" array. Changed "SHOULD not" to "SHOULD NOT" in . Updated normative references (5226-8126, 5988-8288, 7159-8259). Changed examples using "ns1.xn--fo-5ja.example" to split URLs to avoid long lines. Initial working group version. Added acknowledgments. Changed "The "lang" attribute may appear anywhere in an object class or data structure except for in jCard objects" to "The "lang" attribute as defined in this section MAY appear anywhere in an object class or data structure, except for in jCard objects. jCard supports similar functionality by way of the LANGUAGE property parameter (see Section 5.1 of RFC 6350 [RFC6350]". Changed "simple data types conveyed in JSON strings" to "simple data types conveyed in JSON primitive types (strings, numbers, booleans, and null)". Changed "In other words, servers are free to not include JSON members containing registration data based on their own policies" to "In other words, servers are free to omit unrequired/optional JSON members containing registration data based on their own policies". Changed "This data structure appears only in the topmost JSON object of a response" to "This data structure MUST appear in the topmost JSON object of a response". Changed "Some non-answer responses may return entity bodies with information that could be more descriptive" to "Some non-answer responses MAY return entity bodies with information that could be more descriptive". Changed "The basic structure of that response is an object class containing an error code number (corresponding to the HTTP response code) followed by a string named "title" and an array of strings named "description"" to "The basic structure of that response is an object class containing a REQUIRED error code number (corresponding to the HTTP response code) followed by an OPTIONAL string named "title" and an OPTIONAL array of strings named "description"". Changed the "Autonomous System Number Object Class" section title to "The Autonomous System Number Object Class" for consistency with other section titles. Removed trailing periods in the "Terminology and Definitions" section for consistency. Changed instances of "lunarNic" to "lunarNIC" for consistency. Removed an extraneous trailing period after the eventDate description. Changed a "." to ";" in the description of the "network" member of the domain object class. Changed "The high-level structure of the autnum object class consists of information about the network registration" to "The high-level structure of the autnum object class consists of information about the autonomous system number registration". Changed "registry unique" to "registry-unique". Changed "registrant" to "registrar" in the description of the "transfer" event action to address erratum 6158. Added IANA instructions to correct the description of the value in the registry. Added text to to note that "self" and "related" "href" URIs MUST NOT be the same. Added text to to describe return of IDNs in LDH name format. Added text to note that the "fn" member of a contact object MAY be empty in .