<?xml<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC3339 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml">
<!ENTITY RFC3629 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3629.xml">
<!ENTITY RFC3912 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3912.xml">
<!ENTITY RFC3986 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml">
<!ENTITY RFC4034 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4034.xml">
<!ENTITY RFC5396 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5396.xml">
<!ENTITY RFC5646 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5646.xml">
<!ENTITY RFC5730 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5730.xml">
<!ENTITY RFC5890 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5890.xml">
<!ENTITY RFC5910 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5910.xml">
<!ENTITY RFC5952 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5952.xml">
<!ENTITY RFC6350 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6350.xml">
<!ENTITY RFC6839 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6839.xml">
<!ENTITY RFC7095 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7095.xml">
<!ENTITY RFC7480 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7480.xml">
<!ENTITY RFC7481 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7481.xml">
<!ENTITY RFC7942 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7942.xml">
<!ENTITY RFC8126 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8126.xml">
<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml">
<!ENTITY RFC8288 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8288.xml">
<!ENTITY RFC8259 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml">
<!ENTITY I-D.ietf-regext-rfc7482bis SYSTEM 'https://xml2rfc.tools.ietf.org/public/rfc/bibxml3/reference.I-D.ietf-regext-rfc7482bis.xml'>
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" consensus="true" docName="draft-ietf-regext-rfc7483bis-05" indexInclude="true" ipr="trust200902" obsoletes="7483">
<!-- Generated by id2xml 1.5.0 on 2019-12-20T13:25:29Z -->
<?rfc compact="yes"?>
<?rfc text-list-symbols="o*+-"?>
<?rfc subcompact="no"?>
<?rfc sortrefs="yes"?>
<?rfc symrefs="yes"?>
<?rfc strict="yes"?>
<?rfc toc="yes"?> number="9083" obsoletes="7483" prepTime="2021-06-11T16:35:08" scripts="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="3" tocInclude="true" xml:lang="en">
<link href="https://datatracker.ietf.org/doc/draft-ietf-regext-rfc7483bis-05" rel="prev"/>
<link href="https://dx.doi.org/10.17487/rfc9083" rel="alternate"/>
<link href="urn:issn:2070-1721" rel="alternate"/>
<front>
<title abbrev="RDAP JSON Responses">JSON Responses for the Registration Data Access Protocol (RDAP)</title>
<seriesInfo name="RFC" value="9083" stream="IETF"/>
<seriesInfo name="STD" value="95" stream="IETF"/>
<author fullname="Scott Hollenbeck" initials="S." surname="Hollenbeck">
<organization>Verisign
<organization showOnFrontPage="true">Verisign Labs</organization>
<address><postal><street>12061
<address>
<postal>
<street>12061 Bluemont Way</street>
<street>Reston, VA 20190</street>
<street>United States</street>
<city>Reston</city>
<region>VA</region>
<code>20190</code>
<country>United States of America</country>
</postal>
<email>shollenbeck@verisign.com</email>
<uri>https://www.verisignlabs.com/</uri>
</address>
</author>
<author fullname="Andy Newton" initials="A." surname="Newton">
<organization abbrev="AWS">Amazon abbrev="AWS" showOnFrontPage="true">Amazon Web Services, Inc.</organization>
<address><postal><street>13200
<address>
<postal>
<street>13200 Woodland Park Road</street>
<city>Herndon</city>
<region>VA</region>
<code>20171</code>
<country>United States of America</country>
</postal>
<email>andy@hxr.us</email>
</address>
</author>
<date/>
<date month="06" year="2021"/>
<area>Applications and Real-Time</area>
<workgroup>REGEXT Working Group</workgroup>
<abstract><t>
<abstract pn="section-abstract">
<t indent="0" pn="section-abstract-1">
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. If approved, this This document obsoletes RFC 7483.</t>
</abstract>
<boilerplate>
<section anchor="status-of-memo" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.1">
<name slugifiedName="name-status-of-this-memo">Status of This Memo</name>
<t indent="0" pn="section-boilerplate.1-1">
This is an Internet Standards Track document.
</t>
<t indent="0" pn="section-boilerplate.1-2">
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by
the Internet Engineering Steering Group (IESG). Further
information on Internet Standards is available in Section 2 of
RFC 7841.
</t>
<t indent="0" pn="section-boilerplate.1-3">
Information about the current status of this document, any
errata, and how to provide feedback on it may be obtained at
<eref target="https://www.rfc-editor.org/info/rfc9083" brackets="none"/>.
</t>
</section>
<section anchor="copyright" numbered="false" removeInRFC="false" toc="exclude" pn="section-boilerplate.2">
<name slugifiedName="name-copyright-notice">Copyright Notice</name>
<t indent="0" pn="section-boilerplate.2-1">
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
</t>
<t indent="0" pn="section-boilerplate.2-2">
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<eref target="https://trustee.ietf.org/license-info" brackets="none"/>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License.
</t>
</section>
</boilerplate>
<toc>
<section anchor="toc" numbered="false" removeInRFC="false" toc="exclude" pn="section-toc.1">
<name slugifiedName="name-table-of-contents">Table of Contents</name>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1">
<li pn="section-toc.1-1.1">
<t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref derivedContent="1" format="counter" sectionFormat="of" target="section-1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-introduction">Introduction</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.1.2">
<li pn="section-toc.1-1.1.2.1">
<t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.1.1"><xref derivedContent="1.1" format="counter" sectionFormat="of" target="section-1.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-terminology-and-definitions">Terminology and Definitions</xref></t>
</li>
<li pn="section-toc.1-1.1.2.2">
<t indent="0" keepWithNext="true" pn="section-toc.1-1.1.2.2.1"><xref derivedContent="1.2" format="counter" sectionFormat="of" target="section-1.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-data-model">Data Model</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.2">
<t indent="0" pn="section-toc.1-1.2.1"><xref derivedContent="2" format="counter" sectionFormat="of" target="section-2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-use-of-json">Use of JSON</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.2.2">
<li pn="section-toc.1-1.2.2.1">
<t indent="0" pn="section-toc.1-1.2.2.1.1"><xref derivedContent="2.1" format="counter" sectionFormat="of" target="section-2.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-naming">Naming</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.3">
<t indent="0" pn="section-toc.1-1.3.1"><xref derivedContent="3" format="counter" sectionFormat="of" target="section-3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-common-data-types">Common Data Types</xref></t>
</li>
<li pn="section-toc.1-1.4">
<t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" format="counter" sectionFormat="of" target="section-4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-common-data-structures">Common Data Structures</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.4.2">
<li pn="section-toc.1-1.4.2.1">
<t indent="0" pn="section-toc.1-1.4.2.1.1"><xref derivedContent="4.1" format="counter" sectionFormat="of" target="section-4.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rdap-conformance">RDAP Conformance</xref></t>
</li>
<li pn="section-toc.1-1.4.2.2">
<t indent="0" pn="section-toc.1-1.4.2.2.1"><xref derivedContent="4.2" format="counter" sectionFormat="of" target="section-4.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-links">Links</xref></t>
</li>
<li pn="section-toc.1-1.4.2.3">
<t indent="0" pn="section-toc.1-1.4.2.3.1"><xref derivedContent="4.3" format="counter" sectionFormat="of" target="section-4.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-notices-and-remarks">Notices and Remarks</xref></t>
</li>
<li pn="section-toc.1-1.4.2.4">
<t indent="0" pn="section-toc.1-1.4.2.4.1"><xref derivedContent="4.4" format="counter" sectionFormat="of" target="section-4.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-language-identifier">Language Identifier</xref></t>
</li>
<li pn="section-toc.1-1.4.2.5">
<t indent="0" pn="section-toc.1-1.4.2.5.1"><xref derivedContent="4.5" format="counter" sectionFormat="of" target="section-4.5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-events">Events</xref></t>
</li>
<li pn="section-toc.1-1.4.2.6">
<t indent="0" pn="section-toc.1-1.4.2.6.1"><xref derivedContent="4.6" format="counter" sectionFormat="of" target="section-4.6"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-status">Status</xref></t>
</li>
<li pn="section-toc.1-1.4.2.7">
<t indent="0" pn="section-toc.1-1.4.2.7.1"><xref derivedContent="4.7" format="counter" sectionFormat="of" target="section-4.7"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-port-43-whois-server">Port 43 WHOIS Server</xref></t>
</li>
<li pn="section-toc.1-1.4.2.8">
<t indent="0" pn="section-toc.1-1.4.2.8.1"><xref derivedContent="4.8" format="counter" sectionFormat="of" target="section-4.8"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-public-ids">Public IDs</xref></t>
</li>
<li pn="section-toc.1-1.4.2.9">
<t indent="0" pn="section-toc.1-1.4.2.9.1"><xref derivedContent="4.9" format="counter" sectionFormat="of" target="section-4.9"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-object-class-name">Object Class Name</xref></t>
</li>
<li pn="section-toc.1-1.4.2.10">
<t indent="0" pn="section-toc.1-1.4.2.10.1"><xref derivedContent="4.10" format="counter" sectionFormat="of" target="section-4.10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-an-example">An Example</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.5">
<t indent="0" pn="section-toc.1-1.5.1"><xref derivedContent="5" format="counter" sectionFormat="of" target="section-5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-object-classes">Object Classes</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.5.2">
<li pn="section-toc.1-1.5.2.1">
<t indent="0" pn="section-toc.1-1.5.2.1.1"><xref derivedContent="5.1" format="counter" sectionFormat="of" target="section-5.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-entity-object-class">The Entity Object Class</xref></t>
</li>
<li pn="section-toc.1-1.5.2.2">
<t indent="0" pn="section-toc.1-1.5.2.2.1"><xref derivedContent="5.2" format="counter" sectionFormat="of" target="section-5.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-nameserver-object-class">The Nameserver Object Class</xref></t>
</li>
<li pn="section-toc.1-1.5.2.3">
<t indent="0" pn="section-toc.1-1.5.2.3.1"><xref derivedContent="5.3" format="counter" sectionFormat="of" target="section-5.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-domain-object-class">The Domain Object Class</xref></t>
</li>
<li pn="section-toc.1-1.5.2.4">
<t indent="0" pn="section-toc.1-1.5.2.4.1"><xref derivedContent="5.4" format="counter" sectionFormat="of" target="section-5.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-ip-network-object-class">The IP Network Object Class</xref></t>
</li>
<li pn="section-toc.1-1.5.2.5">
<t indent="0" pn="section-toc.1-1.5.2.5.1"><xref derivedContent="5.5" format="counter" sectionFormat="of" target="section-5.5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-the-autonomous-system-numbe">The Autonomous System Number Object Class</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.6">
<t indent="0" pn="section-toc.1-1.6.1"><xref derivedContent="6" format="counter" sectionFormat="of" target="section-6"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-error-response-body">Error Response Body</xref></t>
</li>
<li pn="section-toc.1-1.7">
<t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" format="counter" sectionFormat="of" target="section-7"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-responding-to-help-queries">Responding to Help Queries</xref></t>
</li>
<li pn="section-toc.1-1.8">
<t indent="0" pn="section-toc.1-1.8.1"><xref derivedContent="8" format="counter" sectionFormat="of" target="section-8"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-responding-to-searches">Responding To Searches</xref></t>
</li>
<li pn="section-toc.1-1.9">
<t indent="0" pn="section-toc.1-1.9.1"><xref derivedContent="9" format="counter" sectionFormat="of" target="section-9"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-indicating-truncated-respon">Indicating Truncated Responses</xref></t>
</li>
<li pn="section-toc.1-1.10">
<t indent="0" pn="section-toc.1-1.10.1"><xref derivedContent="10" format="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-iana-considerations">IANA Considerations</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.10.2">
<li pn="section-toc.1-1.10.2.1">
<t indent="0" pn="section-toc.1-1.10.2.1.1"><xref derivedContent="10.1" format="counter" sectionFormat="of" target="section-10.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-rdap-json-media-type-regist">RDAP JSON Media Type Registration</xref></t>
</li>
<li pn="section-toc.1-1.10.2.2">
<t indent="0" pn="section-toc.1-1.10.2.2.1"><xref derivedContent="10.2" format="counter" sectionFormat="of" target="section-10.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-json-values-registry">JSON Values Registry</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.10.2.2.2">
<li pn="section-toc.1-1.10.2.2.2.1">
<t indent="0" pn="section-toc.1-1.10.2.2.2.1.1"><xref derivedContent="10.2.1" format="counter" sectionFormat="of" target="section-10.2.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-notice-and-remark-types">Notice and Remark Types</xref></t>
</li>
<li pn="section-toc.1-1.10.2.2.2.2">
<t indent="0" pn="section-toc.1-1.10.2.2.2.2.1"><xref derivedContent="10.2.2" format="counter" sectionFormat="of" target="section-10.2.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-status-2">Status</xref></t>
</li>
<li pn="section-toc.1-1.10.2.2.2.3">
<t indent="0" pn="section-toc.1-1.10.2.2.2.3.1"><xref derivedContent="10.2.3" format="counter" sectionFormat="of" target="section-10.2.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-event-actions">Event Actions</xref></t>
</li>
<li pn="section-toc.1-1.10.2.2.2.4">
<t indent="0" pn="section-toc.1-1.10.2.2.2.4.1"><xref derivedContent="10.2.4" format="counter" sectionFormat="of" target="section-10.2.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-roles">Roles</xref></t>
</li>
<li pn="section-toc.1-1.10.2.2.2.5">
<t indent="0" pn="section-toc.1-1.10.2.2.2.5.1"><xref derivedContent="10.2.5" format="counter" sectionFormat="of" target="section-10.2.5"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-variant-relations">Variant Relations</xref></t>
</li>
</ul>
</li>
</ul>
</li>
<li pn="section-toc.1-1.11">
<t indent="0" pn="section-toc.1-1.11.1"><xref derivedContent="11" format="counter" sectionFormat="of" target="section-11"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-security-considerations">Security Considerations</xref></t>
</li>
<li pn="section-toc.1-1.12">
<t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="12" format="counter" sectionFormat="of" target="section-12"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-internationalization-consid">Internationalization Considerations</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.12.2">
<li pn="section-toc.1-1.12.2.1">
<t indent="0" pn="section-toc.1-1.12.2.1.1"><xref derivedContent="12.1" format="counter" sectionFormat="of" target="section-12.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-character-encoding">Character Encoding</xref></t>
</li>
<li pn="section-toc.1-1.12.2.2">
<t indent="0" pn="section-toc.1-1.12.2.2.1"><xref derivedContent="12.2" format="counter" sectionFormat="of" target="section-12.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-uris-and-iris">URIs and IRIs</xref></t>
</li>
<li pn="section-toc.1-1.12.2.3">
<t indent="0" pn="section-toc.1-1.12.2.3.1"><xref derivedContent="12.3" format="counter" sectionFormat="of" target="section-12.3"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-language-tags">Language Tags</xref></t>
</li>
<li pn="section-toc.1-1.12.2.4">
<t indent="0" pn="section-toc.1-1.12.2.4.1"><xref derivedContent="12.4" format="counter" sectionFormat="of" target="section-12.4"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-internationalized-domain-na">Internationalized Domain Names</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.13">
<t indent="0" pn="section-toc.1-1.13.1"><xref derivedContent="13" format="counter" sectionFormat="of" target="section-13"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-privacy-considerations">Privacy Considerations</xref></t>
</li>
<li pn="section-toc.1-1.14">
<t indent="0" pn="section-toc.1-1.14.1"><xref derivedContent="14" format="counter" sectionFormat="of" target="section-14"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-references">References</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.14.2">
<li pn="section-toc.1-1.14.2.1">
<t indent="0" pn="section-toc.1-1.14.2.1.1"><xref derivedContent="14.1" format="counter" sectionFormat="of" target="section-14.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-normative-references">Normative References</xref></t>
</li>
<li pn="section-toc.1-1.14.2.2">
<t indent="0" pn="section-toc.1-1.14.2.2.1"><xref derivedContent="14.2" format="counter" sectionFormat="of" target="section-14.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-informative-references">Informative References</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.15">
<t indent="0" pn="section-toc.1-1.15.1"><xref derivedContent="Appendix A" format="default" sectionFormat="of" target="section-appendix.a"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-suggested-data-modeling-wit">Suggested Data Modeling with the Entity Object Class</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-toc.1-1.15.2">
<li pn="section-toc.1-1.15.2.1">
<t indent="0" pn="section-toc.1-1.15.2.1.1"><xref derivedContent="A.1" format="counter" sectionFormat="of" target="section-a.1"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-registrants-and-contacts">Registrants and Contacts</xref></t>
</li>
<li pn="section-toc.1-1.15.2.2">
<t indent="0" pn="section-toc.1-1.15.2.2.1"><xref derivedContent="A.2" format="counter" sectionFormat="of" target="section-a.2"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-registrars">Registrars</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.16">
<t indent="0" pn="section-toc.1-1.16.1"><xref derivedContent="Appendix B" format="default" sectionFormat="of" target="section-appendix.b"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-modeling-events">Modeling Events</xref></t>
</li>
<li pn="section-toc.1-1.17">
<t indent="0" pn="section-toc.1-1.17.1"><xref derivedContent="Appendix C" format="default" sectionFormat="of" target="section-appendix.c"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-structured-vs-unstructured-">Structured vs. Unstructured Addresses</xref></t>
</li>
<li pn="section-toc.1-1.18">
<t indent="0" pn="section-toc.1-1.18.1"><xref derivedContent="Appendix D" format="default" sectionFormat="of" target="section-appendix.d"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-secure-dns">Secure DNS</xref></t>
</li>
<li pn="section-toc.1-1.19">
<t indent="0" pn="section-toc.1-1.19.1"><xref derivedContent="Appendix E" format="default" sectionFormat="of" target="section-appendix.e"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-motivations-for-using-json">Motivations for Using JSON</xref></t>
</li>
<li pn="section-toc.1-1.20">
<t indent="0" pn="section-toc.1-1.20.1"><xref derivedContent="Appendix F" format="default" sectionFormat="of" target="section-appendix.f"/>. <xref derivedContent="" format="title" sectionFormat="of" target="name-changes-from-rfc-7483">Changes from RFC 7483</xref></t>
</li>
<li pn="section-toc.1-1.21">
<t indent="0" pn="section-toc.1-1.21.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.g"/><xref derivedContent="" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgments</xref></t>
</li>
<li pn="section-toc.1-1.22">
<t indent="0" pn="section-toc.1-1.22.1"><xref derivedContent="" format="none" sectionFormat="of" target="section-appendix.h"/><xref derivedContent="" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Addresses</xref></t>
</li>
</ul>
</section>
</toc>
</front>
<middle>
<section title="Introduction" anchor="sect-1"><t> anchor="sect-1" numbered="true" toc="include" removeInRFC="false" pn="section-1">
<name slugifiedName="name-introduction">Introduction</name>
<t indent="0" pn="section-1-1">
This document describes responses in the JSON <xref target="RFC8259"/> target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/> format for
the queries as defined by the Registration Data Access Protocol Query
Format <xref target="I-D.ietf-regext-rfc7482bis"/>. target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>. A communication protocol for exchanging queries
and responses is described in <xref target="RFC7480"/>. If approved, this target="RFC7480" format="default" sectionFormat="of" derivedContent="RFC7480"/>. This document obsoletes RFC 7483.</t>
<section title="Terminology anchor="sect-1.1" numbered="true" toc="include" removeInRFC="false" pn="section-1.1">
<name slugifiedName="name-terminology-and-definitions">Terminology and Definitions" anchor="sect-1.1"><t> Definitions</name>
<t indent="0" pn="section-1.1-1">
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "OPTIONAL" "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> target="RFC2119" format="default" sectionFormat="of" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionFormat="of" derivedContent="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>
<t>
<t indent="0" pn="section-1.1-2">
The following list describes terminology and definitions used
throughout this document:</t>
<t><list style="hanging" hangIndent="1"><t hangText="DNR:">
<dl newline="false" spacing="normal" indent="1" pn="section-1.1-3">
<dt pn="section-1.1-3.1">DNR:</dt>
<dd pn="section-1.1-3.2">
Domain Name Registry or Domain Name Registrar
<vspace blankLines="0"/>
</t>
<t hangText="LDH:">
</dd>
<dt pn="section-1.1-3.3">LDH:</dt>
<dd pn="section-1.1-3.4">
letters, digits, hyphen
<vspace blankLines="0"/>
</t>
<t hangText="member:">
</dd>
<dt pn="section-1.1-3.5">member:</dt>
<dd pn="section-1.1-3.6">
data found within an object as defined by JSON <xref target="RFC8259"/>
</t>
<t hangText="object:"> target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/>
</dd>
<dt pn="section-1.1-3.7">object:</dt>
<dd pn="section-1.1-3.8">
a data structure as defined by JSON <xref target="RFC8259"/>
<vspace blankLines="0"/>
</t>
<t hangText="object class:"> target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/>
</dd>
<dt pn="section-1.1-3.9">object class:</dt>
<dd pn="section-1.1-3.10">
the definition of members that may be found in JSON
objects described in this document
</t>
<t hangText="object instance:">
</dd>
<dt pn="section-1.1-3.11">object instance:</dt>
<dd pn="section-1.1-3.12">
an instantiation or specific instance of an object
class
</t>
<t hangText="RDAP:">
</dd>
<dt pn="section-1.1-3.13">RDAP:</dt>
<dd pn="section-1.1-3.14">
Registration Data Access Protocol
<vspace blankLines="0"/>
</t>
<t hangText="RIR:">
</dd>
<dt pn="section-1.1-3.15">RIR:</dt>
<dd pn="section-1.1-3.16">
Regional Internet Registry
<vspace blankLines="0"/>
</t>
</list>
</t>
</dd>
</dl>
</section>
<section title="Data Model" anchor="sect-1.2"><t> anchor="sect-1.2" numbered="true" toc="include" removeInRFC="false" pn="section-1.2">
<name slugifiedName="name-data-model">Data Model</name>
<t indent="0" pn="section-1.2-1">
The data model for JSON responses is specified in five sections:</t>
<t><list style="numbers"><t>simple
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-1.2-2"><li pn="section-1.2-2.1" derivedCounter="1.">simple data types conveyed in JSON
primitive types (strings, numbers, booleans, and null)</t>
<t>data null)</li>
<li pn="section-1.2-2.2" derivedCounter="2.">data structures specified as JSON arrays or objects that are used
repeatedly when building up larger objects</t>
<t>object objects</li>
<li pn="section-1.2-2.3" derivedCounter="3.">object classes representing structured data corresponding to a
lookup of a single object</t>
<t>arrays object</li>
<li pn="section-1.2-2.4" derivedCounter="4.">arrays of objects representing structured data corresponding to a
search for multiple objects</t>
<t>the objects</li>
<li pn="section-1.2-2.5" derivedCounter="5.">the response to an error</t>
</list>
</t>
<t> error</li>
</ol>
<t indent="0" pn="section-1.2-3">
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:</t>
<t><list style="numbers"><t>domains</t>
<t>nameservers</t>
<t>entities</t>
</list>
</t>
<t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-1.2-4"><li pn="section-1.2-4.1" derivedCounter="1.">domains</li>
<li pn="section-1.2-4.2" derivedCounter="2.">nameservers</li>
<li pn="section-1.2-4.3" derivedCounter="3.">entities</li>
</ol>
<t indent="0" pn="section-1.2-5">
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.</t>
<t>
<t indent="0" pn="section-1.2-6">
In addition to the object classes listed above, RIRs also serve the
following object classes:</t>
<t><list style="numbers"><t>IP networks</t>
<t>Autonomous
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-1.2-7"><li pn="section-1.2-7.1" derivedCounter="1.">IP networks</li>
<li pn="section-1.2-7.2" derivedCounter="2.">Autonomous System numbers</t>
</list>
</t>
<t> numbers</li>
</ol>
<t indent="0" pn="section-1.2-8">
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 <xref target="sect-2.1" format="default" sectionFormat="of" derivedContent="Section 2.1"/> of this document defines a mechanism for
extending the JSON objects that are described in this document.</t>
<t>
<t indent="0" pn="section-1.2-9">
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.</t>
</section>
</section>
<section title="Use anchor="sect-2" numbered="true" toc="include" removeInRFC="false" pn="section-2">
<name slugifiedName="name-use-of-json">Use of JSON" anchor="sect-2"><section title="Naming" anchor="sect-2.1"><t> JSON</name>
<section anchor="sect-2.1" numbered="true" toc="include" removeInRFC="false" pn="section-2.1">
<name slugifiedName="name-naming">Naming</name>
<t indent="0" pn="section-2.1-1">
Clients of these JSON responses SHOULD <bcp14>SHOULD</bcp14> 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 <bcp14>SHOULD</bcp14> 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 <xref target="RFC7095"/> target="RFC7095" format="default" sectionFormat="of" derivedContent="RFC7095"/>
objects. The full JSON name (the prefix plus the underscore plus the
meaningful name) SHOULD <bcp14>SHOULD</bcp14> adhere to the character and name limitations
of the prefix registry described in <xref target="RFC7480"/>. target="RFC7480" format="default" sectionFormat="of" derivedContent="RFC7480"/>. Failure to use these
limitations could result in slower adoption as these limitations have
been observed to aid some client programming models.</t>
<t>
<t indent="0" pn="section-2.1-2">
Consider the following JSON response with JSON members, all of which
are specified in this document.</t>
<figure anchor="ure-1"><artwork><![CDATA[ anchor="ure-1" align="left" suppress-title="false" pn="figure-1">
<sourcecode type="json" markers="false" pn="section-2.1-3.1">
{
"handle" : "ABC123",
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-2.1-4">
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.</t>
<t>
<t indent="0" pn="section-2.1-5">
Consider the following JSON response with JSON names, some of which
should be ignored by clients without knowledge of their meaning.</t>
<figure anchor="ure-2"><artwork><![CDATA[ anchor="ure-2" align="left" suppress-title="false" pn="figure-2">
<sourcecode type="json" markers="false" pn="section-2.1-6.1">
{
"handle" : "ABC123",
"lunarNIC_beforeOneSmallStep" : "TRUE THAT!",
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"lunarNIC_harshMistressNotes" :
[
"In space,",
"nobody can hear you scream."
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-2.1-7">
Insertion of unrecognized members ignored by clients may also be used
for future revisions to this specification.</t>
<t>
<t indent="0" pn="section-2.1-8">
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.</t>
<t>
<t indent="0" pn="section-2.1-9">
Finally, all JSON names specified in this document are case
sensitive. Both servers and clients MUST <bcp14>MUST</bcp14> transmit and process them
using the specified character case.</t>
</section>
</section>
<section title="Common anchor="sect-3" numbered="true" toc="include" removeInRFC="false" pn="section-3">
<name slugifiedName="name-common-data-types">Common Data Types" anchor="sect-3"><t> Types</name>
<t indent="0" pn="section-3-1">
JSON <xref target="RFC8259"/> target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/> 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.</t>
<t><list style="hanging" hangIndent="18"><t hangText="handle:">
<dl newline="false" spacing="normal" indent="18" pn="section-3-2">
<dt pn="section-3-2.1">handle:</dt>
<dd pn="section-3-2.2">
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 character string.
</t>
<t hangText="IPv4 addresses:">
</dd>
<dt pn="section-3-2.3">IPv4 addresses:</dt>
<dd pn="section-3-2.4">
The representation of IPv4 addresses in this
document uses the dotted-decimal notation. An
example of this textual representation is
"192.0.2.0".
</t>
<t hangText="IPv6 addresses:">
</dd>
<dt pn="section-3-2.5">IPv6 addresses:</dt>
<dd pn="section-3-2.6">
The representation of IPv6 addresses in this
document follow the forms outlined in <xref target="RFC5952"/>. target="RFC5952" format="default" sectionFormat="of" derivedContent="RFC5952"/>.
An example of this textual representation is
"2001:db8::1:0:0:1".
</t>
<t hangText="country codes:">
</dd>
<dt pn="section-3-2.7">country codes:</dt>
<dd pn="section-3-2.8">
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 <xref target="ISO.3166.1988"/>. target="ISO.3166.2020" format="default" sectionFormat="of" derivedContent="ISO.3166.2020"/>. The
alpha-2 representation is used because it is freely
available, whereas the alpha-3 and numeric-3
standards are not.
</t>
<t hangText="LDH names:">
</dd>
<dt pn="section-3-2.9">LDH names:</dt>
<dd pn="section-3-2.10">
Textual representations of DNS names where the
labels of the domain are all "letters, digits, hyphen" labels as described by <xref target="RFC5890"/>. target="RFC5890" format="default" sectionFormat="of" derivedContent="RFC5890"/>. Trailing
periods are optional.
</t>
<t hangText="Unicode names:">
</dd>
<dt pn="section-3-2.11">Unicode names:</dt>
<dd pn="section-3-2.12">
Textual representations of DNS names where one or
more of the labels are U-labels as described by
<xref target="RFC5890"/>. target="RFC5890" format="default" sectionFormat="of" derivedContent="RFC5890"/>. Trailing periods are optional.
</t>
<t hangText="dates and times:">
</dd>
<dt pn="section-3-2.13">dates and times:</dt>
<dd pn="section-3-2.14">
The syntax for values denoting dates and times is
defined in <xref target="RFC3339"/>.
</t>
<t hangText="URIs:"> target="RFC3339" format="default" sectionFormat="of" derivedContent="RFC3339"/>.
</dd>
<dt pn="section-3-2.15">URIs:</dt>
<dd pn="section-3-2.16">
The syntax for values denoting a Uniform Resource
Identifier (URI) is defined by <xref target="RFC3986"/>.
</t>
</list>
</t>
<t> target="RFC3986" format="default" sectionFormat="of" derivedContent="RFC3986"/>.
</dd>
</dl>
<t indent="0" pn="section-3-3">
Contact information is defined using jCards as described in
<xref target="RFC7095"/>. target="RFC7095" format="default" sectionFormat="of" derivedContent="RFC7095"/>. The "fn" member is required and MUST
NOT <bcp14>MUST NOT</bcp14> be null according to <xref target="RFC6350"/>. target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350"/>. An empty
"fn" member MAY <bcp14>MAY</bcp14> be used when the contact name does not exist
or is redacted.</t>
</section>
<section title="Common anchor="sect-4" numbered="true" toc="include" removeInRFC="false" pn="section-4">
<name slugifiedName="name-common-data-structures">Common Data Structures" anchor="sect-4"><t> Structures</name>
<t indent="0" pn="section-4-1">
This section defines common data structures used in responses and
object classes.</t>
<section title="RDAP Conformance" anchor="sect-4.1"><t> anchor="sect-4.1" numbered="true" toc="include" removeInRFC="false" pn="section-4.1">
<name slugifiedName="name-rdap-conformance">RDAP Conformance</name>
<t indent="0" pn="section-4.1-1">
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 <bcp14>MUST</bcp14> appear
in the topmost JSON object of a response and MUST NOT <bcp14>MUST NOT</bcp14> appear
anywhere else. A response to a "help"
request will include identifiers for all of the specifications
supported by the server. A response to any other request will
include only identifiers for the specifications used in the
construction of the response. The set of returned identifiers
MAY
<bcp14>MAY</bcp14> vary depending on the authorization level of the client.</t>
<t>
<t indent="0" pn="section-4.1-2">
An example rdapConformance data structure:</t>
<figure anchor="ure-3"><artwork><![CDATA[ anchor="ure-3" align="left" suppress-title="false" pn="figure-3">
<sourcecode type="json" markers="false" pn="section-4.1-3.1">
"rdapConformance" :
[
"rdap_level_0"
]
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-4.1-4">
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 <bcp14>MUST</bcp14> be indicated by including
a unique string literal value registered in the IANA RDAP Extensions
registry specified in <xref target="RFC7480"/>. target="RFC7480" format="default" sectionFormat="of" derivedContent="RFC7480"/>. 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.</t>
<t>
<t indent="0" pn="section-4.1-5">
Example rdapConformance structure with custom extensions noted:</t>
<figure anchor="ure-4"><artwork><![CDATA[ anchor="ure-4" align="left" suppress-title="false" pn="figure-4">
<sourcecode type="json" markers="false" pn="section-4.1-6.1">
"rdapConformance" :
[
"rdap_level_0",
"lunarNIC_level_0"
]
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Links" anchor="sect-4.2"><t> anchor="sect-4.2" numbered="true" toc="include" removeInRFC="false" pn="section-4.2">
<name slugifiedName="name-links">Links</name>
<t indent="0" pn="section-4.2-1">
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 <xref target="RFC8288"/>.</t>
<t><list style="hanging" hangIndent="1"><t hangText="The target="RFC8288" format="default" sectionFormat="of" derivedContent="RFC8288"/>.</t>
<t indent="0" pn="section-4.2-2">The following is an example of the link structure:">
<vspace blankLines="0"/>
</t>
</list>
</t> structure:</t>
<figure anchor="ure-5"><artwork><![CDATA[ anchor="ure-5" align="left" suppress-title="false" pn="figure-5">
<sourcecode type="json" markers="false" pn="section-4.2-3.1">
{
"value" : "https://example.com/context_uri",
"rel" : "self",
"href" : "https://example.com/target_uri",
"hreflang" : [ "en", "ch" ],
"title" : "title",
"media" : "screen",
"type" : "application/json"
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-4.2-4">
The JSON name/values of "rel", "href", "hreflang", "title", "media",
and "type" correspond to values found in Section 3 of <xref target="RFC8288"/>. target="RFC8288" section="3" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8288#section-3" derivedContent="RFC8288"/>. The
"value" JSON value is the context URI as described by <xref target="RFC8288"/>. target="RFC8288" format="default" sectionFormat="of" derivedContent="RFC8288"/>. The
"value", "rel" "rel", and "href" JSON values MUST <bcp14>MUST</bcp14> be specified. All other JSON values are
OPTIONAL.
<bcp14>OPTIONAL</bcp14>. A "related" link relation MUST NOT <bcp14>MUST NOT</bcp14> 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 <bcp14>SHOULD</bcp14>
be consistently returned in LDH name format to allow clients to process these IDNs
according to their capabilities.</t>
<t>
<t indent="0" pn="section-4.2-5">
This is an example of the "links" array as it might be found in an
object class:</t>
<figure anchor="ure-6"><artwork><![CDATA[ anchor="ure-6" align="left" suppress-title="false" pn="figure-6">
<sourcecode type="json" markers="false" pn="section-4.2-6.1">
"links" :
[
{
"value" : "https://example.com/ip/2001:db8::123",
"rel" : "self",
"href" : "https://example.com/ip/2001:db8::123",
"type" : "application/rdap+json"
},
{
"value" : "https://example.com/ip/2001:db8::123",
"rel" : "up",
"href" : "https://example.com/ip/2001:db8::/48",
"type" : "application/rdap+json"
}
]
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Notices anchor="sect-4.3" numbered="true" toc="include" removeInRFC="false" pn="section-4.3">
<name slugifiedName="name-notices-and-remarks">Notices and Remarks" anchor="sect-4.3"><t> Remarks</name>
<t indent="0" pn="section-4.3-1">
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 <xref target="sect-5"/> target="sect-5" format="default" sectionFormat="of" derivedContent="Section 5"/> regarding object classes).</t>
<t>Both
<t indent="0" pn="section-4.3-2">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 <xref target="sect-10.2.1"/>), target="sect-10.2.1" format="default" sectionFormat="of" derivedContent="Section 10.2.1"/>), an
array of strings named "description" for the purposes of conveying any
descriptive text, and a "links" array as described in <xref target="sect-4.2"/>. target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>. The
"description" array MUST <bcp14>MUST</bcp14> be included. All other JSON values are OPTIONAL.</t>
<t> <bcp14>OPTIONAL</bcp14>.</t>
<t indent="0" pn="section-4.3-3">
An example of the notices data structure:</t>
<figure anchor="ure-7"><artwork><![CDATA[ anchor="ure-7" align="left" suppress-title="false" pn="figure-7">
<sourcecode type="json" markers="false" pn="section-4.3-4.1">
"notices" :
[
{
"title" : "Terms of Use",
"description" :
[
"Service subject to The Registry of the Moon's TOS.",
"Copyright (c) 2020 LunarNIC"
],
"links" :
[
{
"value" : "https://example.net/entity/XXXX",
"rel" : "alternate",
"type" : "text/html",
"href" : "https://www.example.com/terms_of_use.html"
}
]
}
]
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-4.3-5">
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.</t>
<t>
<t indent="0" pn="section-4.3-6">
An example of the remarks data structure:</t>
<figure anchor="ure-8"><artwork><![CDATA[ anchor="ure-8" align="left" suppress-title="false" pn="figure-8">
<sourcecode type="json" markers="false" pn="section-4.3-7.1">
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
]
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-4.3-8">
Note that objects in the "remarks" array may also have a "links"
array.</t>
<t>
<t indent="0" pn="section-4.3-9">
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 <xref target="sect-10.2.1"/>) target="sect-10.2.1" format="default" sectionFormat="of" derivedContent="Section 10.2.1"/>) for programmatic use.</t>
<t>
<t indent="0" pn="section-4.3-10">
An example of the remarks data structure:</t>
<figure anchor="ure-9"><artwork><![CDATA[ anchor="ure-9" align="left" suppress-title="false" pn="figure-9">
<sourcecode type="json" markers="false" pn="section-4.3-11.1">
"remarks" :
[
{
"type" : "object truncated due to authorization",
"description" :
[
"Some registration data may not have been given.",
"Use proper authorization credentials to see all of it."
]
}
]
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-4.3-12">
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.</t>
</section>
<section title="Language Identifier" anchor="sect-4.4"><t> anchor="sect-4.4" numbered="true" toc="include" removeInRFC="false" pn="section-4.4">
<name slugifiedName="name-language-identifier">Language Identifier</name>
<t indent="0" pn="section-4.4-1">
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 <xref target="RFC5646"/>.</t>
<t><figure anchor="ure-10"><artwork>"lang" target="RFC5646" format="default" sectionFormat="of" derivedContent="RFC5646"/>.</t>
<figure anchor="ure-10" align="left" suppress-title="false" pn="figure-10">
<sourcecode type="json" markers="false" pn="section-4.4-2.1">"lang" : "mn-Cyrl-MN"</artwork></figure>
</t>
<t>The "mn-Cyrl-MN"</sourcecode>
</figure>
<t indent="0" pn="section-4.4-3">The "lang" attribute as defined in this section MAY <bcp14>MAY</bcp14> appear anywhere
in an object class or data structure, except for in jCard objects. vCard
supports similar functionality by way of the LANGUAGE property parameter
(see Section 5.1 <xref target="RFC6350" section="5.1" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6350#section-5.1" derivedContent="RFC6350"/> of RFC 6350 <xref target="RFC6350"/>).</t> target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350"/>).</t>
</section>
<section title="Events" anchor="sect-4.5"><t> anchor="sect-4.5" numbered="true" toc="include" removeInRFC="false" pn="section-4.5">
<name slugifiedName="name-events">Events</name>
<t indent="0" pn="section-4.5-1">
This data structure represents events that have occurred on an
instance of an object class (see <xref target="sect-5"/> target="sect-5" format="default" sectionFormat="of" derivedContent="Section 5"/> regarding object classes).</t>
<t>
<t indent="0" pn="section-4.5-2">
This is an example of an "events" array.</t>
<figure anchor="ure-11"><artwork><![CDATA[ anchor="ure-11" align="left" suppress-title="false" pn="figure-11">
<sourcecode type="json" markers="false" pn="section-4.5-3.1">
"events" :
[
{
"eventAction" : "registration",
"eventActor" : "SOMEID-LUNARNIC",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventActor" : "OTHERID-LUNARNIC",
"eventDate" : "1991-12-31T23:59:59Z"
}
]
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-4.5-4">
The "events" array consists of objects, each with the following members:</t>
<t><list style="symbols"><t>"eventAction"
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.5-5">
<li pn="section-4.5-5.1">"eventAction" -- a REQUIRED <bcp14>REQUIRED</bcp14> string denoting the reason for the event</t>
<t>"eventActor" event</li>
<li pn="section-4.5-5.2">"eventActor" -- an OPTIONAL <bcp14>OPTIONAL</bcp14> identifier denoting the actor
responsible for the event</t>
<t>"eventDate" event</li>
<li pn="section-4.5-5.3">"eventDate" -- a REQUIRED <bcp14>REQUIRED</bcp14> string containing the time and date the event
occurred</t>
<t>"links"
occurred</li>
<li pn="section-4.5-5.4">"links" -- OPTIONAL; <bcp14>OPTIONAL</bcp14>; see <xref target="sect-4.2"/>
</t>
</list>
</t>
<t> target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
</ul>
<t indent="0" pn="section-4.5-6">
Events can be future dated. One use case for future dating of events
is to denote when an object expires from a registry.</t>
<t>
<t indent="0" pn="section-4.5-7">
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.</t>
<t>
<t indent="0" pn="section-4.5-8">
See <xref target="sect-10.2.3"/> target="sect-10.2.3" format="default" sectionFormat="of" derivedContent="Section 10.2.3"/> for a list of values for the "eventAction" string.
See Appendix B <xref target="sect-b" format="default" sectionFormat="of" derivedContent="Appendix B"/> regarding the various ways events can be modeled.</t>
</section>
<section title="Status" anchor="sect-4.6"><t> anchor="sect-4.6" numbered="true" toc="include" removeInRFC="false" pn="section-4.6">
<name slugifiedName="name-status">Status</name>
<t indent="0" pn="section-4.6-1">
This data structure, named "status", is an array of strings
indicating the state of a registered object (see <xref target="sect-10.2.2"/> target="sect-10.2.2" format="default" sectionFormat="of" derivedContent="Section 10.2.2"/> for a
list of values).</t>
</section>
<section title="Port anchor="sect-4.7" numbered="true" toc="include" removeInRFC="false" pn="section-4.7">
<name slugifiedName="name-port-43-whois-server">Port 43 WHOIS Server" anchor="sect-4.7"><t> Server</name>
<t indent="0" pn="section-4.7-1">
This data structure, a member named "port43", is a simple character string
containing the fully qualified host name or IP address of the WHOIS
<xref target="RFC3912"/> target="RFC3912" format="default" sectionFormat="of" derivedContent="RFC3912"/> server where the containing object instance may be found.
Note that this is not a URI, as there is no WHOIS URI scheme.</t>
</section>
<section title="Public IDs" anchor="sect-4.8"><t> anchor="sect-4.8" numbered="true" toc="include" removeInRFC="false" pn="section-4.8">
<name slugifiedName="name-public-ids">Public IDs</name>
<t indent="0" pn="section-4.8-1">
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 <bcp14>REQUIRED</bcp14> members:</t>
<t><list style="symbols"><t>type
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4.8-2">
<li pn="section-4.8-2.1">type -- a string denoting the type of public identifier</t>
<t>identifier identifier</li>
<li pn="section-4.8-2.2">identifier -- a string denoting a public identifier of the type related to "type"</t>
</list>
</t>
<t> "type"</li>
</ul>
<t indent="0" pn="section-4.8-3">
The following is an example of a publicIds structure.</t>
<figure anchor="ure-12"><artwork><![CDATA[ anchor="ure-12" align="left" suppress-title="false" pn="figure-12">
<sourcecode type="json" markers="false" pn="section-4.8-4.1">
"publicIds":
[
{
"type":"IANA Registrar ID",
"identifier":"1"
}
]
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Object anchor="sect-4.9" numbered="true" toc="include" removeInRFC="false" pn="section-4.9">
<name slugifiedName="name-object-class-name">Object Class Name" anchor="sect-4.9"><t> Name</name>
<t indent="0" pn="section-4.9-1">
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
<bcp14>REQUIRED</bcp14> in all RDAP response objects so that the type of the object
can be interpreted.</t>
</section>
<section title="An Example" anchor="sect-4.10"><t> anchor="sect-4.10" numbered="true" toc="include" removeInRFC="false" pn="section-4.10">
<name slugifiedName="name-an-example">An Example</name>
<t indent="0" pn="section-4.10-1">
This is an example response with both rdapConformance and notices
embedded:</t>
<figure anchor="ure-13"><artwork><![CDATA[ anchor="ure-13" align="left" suppress-title="false" pn="figure-13">
<sourcecode type="json" markers="false" pn="section-4.10-2.1">
{
"rdapConformance" :
[
"rdap_level_0"
],
"notices" :
[
{
"title" : "Content Removed",
"description" :
[
"Without full authorization, content has been removed.",
"Sorry, dude!"
],
"links" :
[
{
"value" : "https://example.net/ip/192.0.2.0/24",
"rel" : "alternate",
"type" : "text/html",
"href" : "https://www.example.com/redaction_policy.html"
}
]
}
],
"lang" : "en",
"objectClassName" : "ip network",
"startAddress" : "192.0.2.0",
"endAddress" : "192.0.2.255",
"handle" : "XXXX-RIR",
"ipVersion" : "v4",
"name": "NET-RTR-1",
"parentHandle" : "YYYY-RIR",
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
</section>
<section title="Object Classes" anchor="sect-5"><t> anchor="sect-5" numbered="true" toc="include" removeInRFC="false" pn="section-5">
<name slugifiedName="name-object-classes">Object Classes</name>
<t indent="0" pn="section-5-1">
Object classes represent structures appropriate for a response from
the queries specified in <xref target="I-D.ietf-regext-rfc7482bis"/>.</t>
<t> target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>.</t>
<t indent="0" pn="section-5-2">
Each object class contains a "links" array as specified in
<xref target="sect-4.2"/>. target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>. 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 <bcp14>SHOULD</bcp14> provide a link representing a URI
for that object class instance using the "self" relationship as
described in the IANA registry specified by <xref target="RFC8288"/>. target="RFC8288" format="default" sectionFormat="of" derivedContent="RFC8288"/>. As explained
in <xref target="sect-5.2"/>, target="sect-5.2" format="default" sectionFormat="of" derivedContent="Section 5.2"/>, this may be not always be possible for nameserver
data. Clients MUST <bcp14>MUST</bcp14> be able to process object instances without a
self link. When present, clients can use the self link for caching
data. Servers MAY <bcp14>MAY</bcp14> 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.</t>
<t>
<t indent="0" pn="section-5-3">
Clients using self links for caching SHOULD NOT <bcp14>SHOULD NOT</bcp14> 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.</t>
<t>
<t indent="0" pn="section-5-4">
Self links MUST <bcp14>MUST</bcp14> contain a "type" element containing the "application/rdap+json" media type when referencing RDAP object instances as
defined by this document.</t>
<t>
<t indent="0" pn="section-5-5">
This is an example of the "links" array with a self link to an object
class:</t>
<figure anchor="ure-14"><artwork><![CDATA[ anchor="ure-14" align="left" suppress-title="false" pn="figure-14">
<sourcecode type="json" markers="false" pn="section-5-6.1">
"links" :
[
{
"value" : "https://example.com/ip/2001:db8::123",
"rel" : "self",
"href" : "https://example.com/ip/2001:db8::123",
"type" : "application/rdap+json"
}
]
]]></artwork>
</sourcecode>
</figure>
<section title="The anchor="sect-5.1" numbered="true" toc="include" removeInRFC="false" pn="section-5.1">
<name slugifiedName="name-the-entity-object-class">The Entity Object Class" anchor="sect-5.1"><t> Class</name>
<t indent="0" pn="section-5.1-1">
The entity object class appears throughout this document and is an
appropriate response for the /entity/XXXX query defined in
"Registration
"<xref target="RFC9082" format="title" sectionFormat="of" derivedContent="Registration Data Access Protocol (RDAP) Query Format" Format"/>" <xref target="I-D.ietf-regext-rfc7482bis"/>. target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>.
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 <xref target="RFC8259"/> target="RFC8259" format="default" sectionFormat="of" derivedContent="RFC8259"/> with one
construct, the entity object class, to aid in the reuse of code by
implementers.</t>
<t>
<t indent="0" pn="section-5.1-2">
The entity object class uses jCard <xref target="RFC7095"/> target="RFC7095" format="default" sectionFormat="of" derivedContent="RFC7095"/> 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 little or no use in RDAP,
such as birthdays, anniversaries, and gender.</t>
<t>
<t indent="0" pn="section-5.1-3">
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.</t>
<figure anchor="ure-15"><artwork><![CDATA[ anchor="ure-15" align="left" suppress-title="false" pn="figure-15">
<sourcecode type="json" markers="false" pn="section-5.1-4.1">
{
"objectClassName" : "entity",
"handle":"XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["n", {}, "text",
["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
],
["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-4321"
],
["email",
{ "type":"work" },
"text",
"joe.user@example.com"
],
["geo", {
"type":"work"
}, "uri", "geo:46.772673,-71.282945"],
["key",
{ "type":"work" },
"uri",
"https://www.example.com/joe.user/joe.asc"
],
["tz", {},
"utc-offset", "-05:00"],
["url", { "type":"home" },
"uri", "https://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":"https://example.com/entity/XXXX",
"rel":"self",
"href":"https://example.com/entity/XXXX",
"type" : "application/rdap+json"
}
],
"events":[
{
"eventAction":"registration",
"eventDate":"1990-12-31T23:59:59Z"
}
],
"asEventActor":[
{
"eventAction":"last changed",
"eventDate":"1991-12-31T23:59:59Z"
}
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.1-5">
The entity object class can contain the following members:</t>
<t><list style="symbols"><t>objectClassName
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.1-6">
<li pn="section-5.1-6.1">objectClassName -- the string "entity"</t>
<t>handle "entity"</li>
<li pn="section-5.1-6.2">handle -- a string representing a registry-unique identifier of
the entity</t>
<t>vcardArray entity</li>
<li pn="section-5.1-6.3">vcardArray -- a jCard with the entity's contact information</t>
<t>roles information</li>
<li pn="section-5.1-6.4">roles -- an array of strings, each signifying the relationship an
object would have with its closest containing object (see
<xref target="sect-10.2.4"/> target="sect-10.2.4" format="default" sectionFormat="of" derivedContent="Section 10.2.4"/> for a list of values)</t>
<t>publicIds values)</li>
<li pn="section-5.1-6.5">publicIds -- see <xref target="sect-4.8"/>
</t>
<t>entities target="sect-4.8" format="default" sectionFormat="of" derivedContent="Section 4.8"/>
</li>
<li pn="section-5.1-6.6">entities -- an array of entity objects as defined by this section</t>
<t>remarks section</li>
<li pn="section-5.1-6.7">remarks -- see <xref target="sect-4.3"/>
</t>
<t>links target="sect-4.3" format="default" sectionFormat="of" derivedContent="Section 4.3"/>
</li>
<li pn="section-5.1-6.8">links -- see <xref target="sect-4.2"/>
</t>
<t>events target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
<li pn="section-5.1-6.9">events -- see <xref target="sect-4.5"/>
</t>
<t>asEventActor target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
<li pn="section-5.1-6.10">asEventActor -- this data structure takes the same form as the
events data structure (see <xref target="sect-4.5"/>), target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>), but each object in the
array MUST NOT <bcp14>MUST NOT</bcp14> have an "eventActor" member. These objects denote
that the entity is an event actor for the given events. See
Appendix B
<xref target="sect-b" format="default" sectionFormat="of" derivedContent="Appendix B"/> regarding the various ways events can be modeled.</t>
<t>status modeled.</li>
<li pn="section-5.1-6.11">status -- see <xref target="sect-4.6"/>
</t>
<t>port43 target="sect-4.6" format="default" sectionFormat="of" derivedContent="Section 4.6"/>
</li>
<li pn="section-5.1-6.12">port43 -- see <xref target="sect-4.7"/>
</t>
<t>networks target="sect-4.7" format="default" sectionFormat="of" derivedContent="Section 4.7"/>
</li>
<li pn="section-5.1-6.13">networks -- an array of IP network objects as defined in
<xref target="sect-5.4"/>
</t>
<t>autnums target="sect-5.4" format="default" sectionFormat="of" derivedContent="Section 5.4"/>
</li>
<li pn="section-5.1-6.14">autnums -- an array of autnum objects as defined in <xref target="sect-5.5"/>
</t>
</list>
</t>
<t> target="sect-5.5" format="default" sectionFormat="of" derivedContent="Section 5.5"/>
</li>
</ul>
<t indent="0" pn="section-5.1-7">
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.</t>
<t>
<t indent="0" pn="section-5.1-8">
The following is an elided example of an entity with embedded
entities.</t>
<figure anchor="ure-16"><artwork><![CDATA[ anchor="ure-16" align="left" suppress-title="false" pn="figure-16">
<sourcecode type="json" markers="false" pn="section-5.1-9.1">
{
"objectClassName" : "entity",
"handle" : "ANENTITY",
"roles" : [ "registrar" ],
...
"entities" :
[
{
"objectClassName" : "entity",
"handle": "ANEMBEDDEDENTITY",
"roles" : [ "technical" ],
...
},
...
],
...
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.1-10">
The following is an example of an entity that might be served by a
DNR.</t>
<figure anchor="ure-17"><artwork><![CDATA[ anchor="ure-17" align="left" suppress-title="false" pn="figure-17">
<sourcecode type="json" markers="false" pn="section-5.1-11.1">
{
"objectClassName" : "entity",
"handle":"XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["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"
]
],
["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" ],
"remarks":[
{
"description":[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links":[
{
"value":"https://example.com/entity/XXXX",
"rel":"self",
"href":"https://example.com/entity/XXXX",
"type":"application/rdap+json"
}
],
"port43":"whois.example.net",
"events":[
{
"eventAction":"registration",
"eventDate":"1990-12-31T23:59:59Z"
},
{
"eventAction":"last changed",
"eventDate":"1991-12-31T23:59:59Z",
"eventActor":"joe@example.com"
}
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.1-12">
See Appendix A <xref target="sect-a" format="default" sectionFormat="of" derivedContent="Appendix A"/> for use of the entity object class to model various
types of entities found in both RIRs and DNRs. See Appendix C <xref target="sect-c" format="default" sectionFormat="of" derivedContent="Appendix C"/>
regarding structured vs. unstructured postal addresses in entities.</t>
</section>
<section title="The anchor="sect-5.2" numbered="true" toc="include" removeInRFC="false" pn="section-5.2">
<name slugifiedName="name-the-nameserver-object-class">The Nameserver Object Class" anchor="sect-5.2"><t> Class</name>
<t indent="0" pn="section-5.2-1">
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".
Please note that some of the examples in this section include lines
that have been wrapped for reading clarity.</t>
<t>
<t indent="0" pn="section-5.2-2">
The nameserver object class accommodates both models and degrees of
variation in between.</t>
<t><list style="hanging" hangIndent="1"><t hangText="The
<t indent="0" pn="section-5.2-3">The following is an example of a nameserver object.">
<vspace blankLines="0"/>
</t>
</list>
</t> object.</t>
<figure anchor="ure-18"><artwork><![CDATA[ anchor="ure-18" align="left" suppress-title="false" pn="figure-18">
<sourcecode type="json" markers="false" pn="section-5.2-4.1">
{
"objectClassName" : "nameserver",
"handle" : "XXXX",
"ldhName" : "ns1.xn--fo-5ja.example",
"unicodeName" : "ns.fóo.example",
"status" : [ "active" ],
"ipAddresses" :
{
"v4": [ "192.0.2.1", "192.0.2.2" ],
"v6": [ "2001:db8::123" ]
},
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/nameserver/
ns1.xn--fo-5ja.example",
"rel" : "self",
"href" : "https://example.net/nameserver/
ns1.xn--fo-5ja.example",
"type" : "application/rdap+json"
}
],
"port43" : "whois.example.net",
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z",
"eventActor" : "joe@example.com"
}
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
Figure 18
<t indent="0" pn="section-5.2-5">
<xref target="ure-18" format="default" sectionFormat="of" derivedContent="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
<xref target="ure-19" format="default" sectionFormat="of" derivedContent="Figure 19"/> is an example of a nameserver object as would be found in
RIRs and some DNRs, while Figure 20 <xref target="ure-20" format="default" sectionFormat="of" derivedContent="Figure 20"/> is an example of a nameserver
object as would be found in other DNRs.</t>
<t><list style="hanging" hangIndent="1"><t hangText="The
<t indent="0" pn="section-5.2-6">The following is an example of the simplest nameserver object:">
<vspace blankLines="0"/>
</t>
</list>
</t> object:</t>
<figure anchor="ure-19"><artwork><![CDATA[ anchor="ure-19" align="left" suppress-title="false" pn="figure-19">
<sourcecode type="json" markers="false" pn="section-5.2-7.1">
{
"objectClassName" : "nameserver",
"ldhName" : "ns1.example.com"
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.2-8">
The following is an example of a simple nameserver object that might
be commonly used by DNRs:</t>
<figure anchor="ure-20"><artwork><![CDATA[ anchor="ure-20" align="left" suppress-title="false" pn="figure-20">
<sourcecode type="json" markers="false" pn="section-5.2-9.1">
{
"objectClassName" : "nameserver",
"ldhName" : "ns1.example.com",
"ipAddresses" : { "v6" : [ "2001:db8::123", "2001:db8::124" ] }
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.2-10">
As nameservers can be modeled by some registries to be first-class
objects, they may also have an array of entities (<xref target="sect-5.1"/>) target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>)
embedded to signify parties responsible for the maintenance,
registrations, etc., of the nameservers.</t>
<t>
<t indent="0" pn="section-5.2-11">
The following is an elided example of a nameserver with embedded
entities.</t>
<figure anchor="ure-21"><artwork><![CDATA[ anchor="ure-21" align="left" suppress-title="false" pn="figure-21">
<sourcecode type="json" markers="false" pn="section-5.2-12.1">
{
"objectClassName" : "nameserver",
"handle" : "XXXX",
"ldhName" : "ns.xn--fo-5ja.example",
...
"entities" :
[
...
],
...
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.2-13">
The nameserver object class can contain the following members:</t>
<t><list style="symbols"><t>objectClassName
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.2-14">
<li pn="section-5.2-14.1">objectClassName -- the string "nameserver"</t>
<t>handle "nameserver"</li>
<li pn="section-5.2-14.2">handle -- a string representing a registry-unique identifier of
the nameserver</t>
<t>ldhName nameserver</li>
<li pn="section-5.2-14.3">ldhName -- a string containing the LDH name of the nameserver (see
<xref target="sect-3"/>)</t>
<t>unicodeName target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>)</li>
<li pn="section-5.2-14.4">unicodeName -- a string containing a DNS Unicode name of the
nameserver (see <xref target="sect-3"/>)</t>
<t>ipAddresses target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>)</li>
<li pn="section-5.2-14.5">
<t indent="0" pn="section-5.2-14.5.1">ipAddresses -- an object containing the following members:<list style="symbols"><t>v6 members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.2-14.5.2">
<li pn="section-5.2-14.5.2.1">v6 -- an array of strings containing IPv6 addresses of the
nameserver</t>
<t>v4
nameserver</li>
<li pn="section-5.2-14.5.2.2">v4 -- an array of strings containing IPv4 addresses of the
nameserver</t>
</list>
</t>
<t>entities
nameserver</li>
</ul>
</li>
<li pn="section-5.2-14.6">entities -- an array of entity objects as defined by <xref target="sect-5.1"/>
</t>
<t>status target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>
</li>
<li pn="section-5.2-14.7">status -- see <xref target="sect-4.6"/>
</t>
<t>remarks target="sect-4.6" format="default" sectionFormat="of" derivedContent="Section 4.6"/>
</li>
<li pn="section-5.2-14.8">remarks -- see <xref target="sect-4.3"/>
</t>
<t>links target="sect-4.3" format="default" sectionFormat="of" derivedContent="Section 4.3"/>
</li>
<li pn="section-5.2-14.9">links -- see <xref target="sect-4.2"/>
</t>
<t>port43 target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
<li pn="section-5.2-14.10">port43 -- see <xref target="sect-4.7"/>
</t>
<t>events target="sect-4.7" format="default" sectionFormat="of" derivedContent="Section 4.7"/>
</li>
<li pn="section-5.2-14.11">events -- see <xref target="sect-4.5"/>
</t>
</list>
</t> target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
</ul>
</section>
<section title="The anchor="sect-5.3" numbered="true" toc="include" removeInRFC="false" pn="section-5.3">
<name slugifiedName="name-the-domain-object-class">The Domain Object Class" anchor="sect-5.3"><t> Class</name>
<t indent="0" pn="section-5.3-1">
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.</t>
<t>
<t indent="0" pn="section-5.3-2">
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.).</t>
<t>
<t indent="0" pn="section-5.3-3">
The following is an elided example of the domain object showing the
high-level structure:</t>
<figure anchor="ure-22"><artwork><![CDATA[ anchor="ure-22" align="left" suppress-title="false" pn="figure-22">
<sourcecode type="json" markers="false" pn="section-5.3-4.1">
{
"objectClassName" : "domain",
"handle" : "XXX",
"ldhName" : "blah.example.com",
...
"nameservers" :
[
...
],
...
"entities" :
[
...
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.3-5">
The domain object class can contain the following members:</t>
<t><!--
rfc7483.xml.txt(1543): Warning: Found unexpected inentation change: worked on '
+ links - see Section 4.2', found ' See Appendix D for background
information on these objects.'
--><list style="symbols"><t>objectClassName
<t indent="0" pn="section-5.3-6">
</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.3-7">
<li pn="section-5.3-7.1">objectClassName -- the string "domain"</t>
<t>handle "domain"</li>
<li pn="section-5.3-7.2">handle -- a string representing a registry-unique identifier of
the domain object instance</t>
<t>ldhName instance</li>
<li pn="section-5.3-7.3">ldhName -- a string describing a domain name in LDH form as
described in <xref target="sect-3"/>
</t>
<t>unicodeName target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>
</li>
<li pn="section-5.3-7.4">unicodeName -- a string containing a domain name with U-labels as
described in <xref target="sect-3"/>
</t>
<t>variants target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>
</li>
<li pn="section-5.3-7.5">
<t indent="0" pn="section-5.3-7.5.1">variants -- an array of objects, each containing the following
values:<list style="symbols"><t>relation
values:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.3-7.5.2">
<li pn="section-5.3-7.5.2.1">relation -- an array of strings, with each string denoting the
relationship between the variants and the containing domain
object (see <xref target="sect-10.2.5"/> target="sect-10.2.5" format="default" sectionFormat="of" derivedContent="Section 10.2.5"/> for a list of suggested variant
relations).</t>
<t>idnTable
relations).</li>
<li pn="section-5.3-7.5.2.2">idnTable -- the character string literal that represents the Internationalized
Domain Name (IDN) table that has been registered in the IANA Repository of IDN
Practices <xref target="IANA_IDNTABLES"/>.</t>
<t>variantNames target="IANA_IDNTABLES" format="default" sectionFormat="of" derivedContent="IANA_IDNTABLES"/>.</li>
<li pn="section-5.3-7.5.2.3">variantNames -- an array of objects, with each object
containing an "ldhName" member and a "unicodeName" member (see
<xref target="sect-3"/>).</t>
</list>
</t>
<t>nameservers target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>).</li>
</ul>
</li>
<li pn="section-5.3-7.6">nameservers -- an array of nameserver objects as defined by
<xref target="sect-5.2"/>
</t>
<t>secureDNS target="sect-5.2" format="default" sectionFormat="of" derivedContent="Section 5.2"/>
</li>
<li pn="section-5.3-7.7">
<t indent="0" pn="section-5.3-7.7.1">secureDNS -- an object with the following members:<list style="symbols"><t>zoneSigned members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.3-7.7.2">
<li pn="section-5.3-7.7.2.1">zoneSigned -- boolean true if the zone has been signed, false
otherwise.</t>
<t>delegationSigned
otherwise.</li>
<li pn="section-5.3-7.7.2.2">delegationSigned -- boolean true if there are DS records in the
parent, false otherwise.</t>
<t>maxSigLife otherwise.</li>
<li pn="section-5.3-7.7.2.3">maxSigLife -- an integer representing the signature lifetime in
seconds to be used when creating the RRSIG DS record in the
parent zone <xref target="RFC5910"/>.</t>
<t>dsData target="RFC5910" format="default" sectionFormat="of" derivedContent="RFC5910"/>.</li>
<li pn="section-5.3-7.7.2.4">
<t indent="0" pn="section-5.3-7.7.2.4.1">dsData -- an array of objects, each with the following members:<list style="symbols"><t>keyTag members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.3-7.7.2.4.2">
<li pn="section-5.3-7.7.2.4.2.1">keyTag -- an integer as specified by the key tag field of a
DNS DS record as specified by <xref target="RFC4034"/> target="RFC4034" format="default" sectionFormat="of" derivedContent="RFC4034"/> in presentation
format</t>
<t>algorithm
format</li>
<li pn="section-5.3-7.7.2.4.2.2">algorithm -- an integer as specified by the algorithm field
of a DNS DS record as described by RFC 4034 in presentation
format</t>
<t>digest
format</li>
<li pn="section-5.3-7.7.2.4.2.3">digest -- a string as specified by the digest field of a DNS
DS record as specified by RFC 4034 in presentation format</t>
<t>digestType format</li>
<li pn="section-5.3-7.7.2.4.2.4">digestType -- an integer as specified by the digest type
field of a DNS DS record as specified by RFC 4034 in
presentation format</t>
<t>events format</li>
<li pn="section-5.3-7.7.2.4.2.5">events -- see <xref target="sect-4.5"/>
</t>
<t>links target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
<li pn="section-5.3-7.7.2.4.2.6">links -- see <xref target="sect-4.2"/>
</t>
</list>
</t>
<t>keyData target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
</ul>
</li>
<li pn="section-5.3-7.7.2.5">
<t indent="0" pn="section-5.3-7.7.2.5.1">keyData -- an array of objects, each with the following
members:<list style="symbols"><t>flags
members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.3-7.7.2.5.2">
<li pn="section-5.3-7.7.2.5.2.1">flags -- an integer representing the flags field value in
the DNSKEY record <xref target="RFC4034"/> target="RFC4034" format="default" sectionFormat="of" derivedContent="RFC4034"/> in presentation format</t>
<t>protocol format</li>
<li pn="section-5.3-7.7.2.5.2.2">protocol -- an integer representation of the protocol field
value of the DNSKEY record <xref target="RFC4034"/> target="RFC4034" format="default" sectionFormat="of" derivedContent="RFC4034"/> in presentation format</t>
<t>publicKey format</li>
<li pn="section-5.3-7.7.2.5.2.3">publicKey -- a string representation of the public key in
the DNSKEY record <xref target="RFC4034"/> target="RFC4034" format="default" sectionFormat="of" derivedContent="RFC4034"/> in presentation format</t>
<t>algorithm format</li>
<li pn="section-5.3-7.7.2.5.2.4">algorithm -- an integer as specified by the algorithm field
of a DNSKEY record as specified by <xref target="RFC4034"/> target="RFC4034" format="default" sectionFormat="of" derivedContent="RFC4034"/> in presentation
format</t>
<t>events
format</li>
<li pn="section-5.3-7.7.2.5.2.5">events -- see <xref target="sect-4.5"/>
</t>
<t>links target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
<li pn="section-5.3-7.7.2.5.2.6">
<t indent="0" pn="section-5.3-7.7.2.5.2.6.1">links -- see <xref target="sect-4.2"/>
<list style="hanging" hangIndent="1"><t hangText="See Appendix D target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</t>
<t indent="0" pn="section-5.3-7.7.2.5.2.6.2">See <xref target="sect-d" format="default" sectionFormat="of" derivedContent="Appendix D"/> for background information on these objects.">
<vspace blankLines="0"/>
</t>
</list>
</t>
</list>
</t>
</list>
</t>
<t>entities objects.</t>
</li>
</ul>
</li>
</ul>
</li>
<li pn="section-5.3-7.8">entities -- an array of entity objects as defined by <xref target="sect-5.1"/>
</t>
<t>status target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>
</li>
<li pn="section-5.3-7.9">status -- see <xref target="sect-4.6"/>
</t>
<t>publicIds target="sect-4.6" format="default" sectionFormat="of" derivedContent="Section 4.6"/>
</li>
<li pn="section-5.3-7.10">publicIds -- see <xref target="sect-4.8"/>
</t>
<t>remarks target="sect-4.8" format="default" sectionFormat="of" derivedContent="Section 4.8"/>
</li>
<li pn="section-5.3-7.11">remarks -- see <xref target="sect-4.3"/>
</t>
<t>links target="sect-4.3" format="default" sectionFormat="of" derivedContent="Section 4.3"/>
</li>
<li pn="section-5.3-7.12">links -- see <xref target="sect-4.2"/>
</t>
<t>port43 target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
<li pn="section-5.3-7.13">port43 -- see <xref target="sect-4.7"/>
</t>
<t>events target="sect-4.7" format="default" sectionFormat="of" derivedContent="Section 4.7"/>
</li>
<li pn="section-5.3-7.14">events -- see <xref target="sect-4.5"/>
</t>
<t>network target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
<li pn="section-5.3-7.15">network -- represents the IP network for which a reverse DNS
domain is referenced; see <xref target="sect-5.4"/>
</t>
</list>
</t>
<t> target="sect-5.4" format="default" sectionFormat="of" derivedContent="Section 5.4"/>
</li>
</ul>
<t indent="0" pn="section-5.3-8">
The following is an example of a JSON domain object representing a
reverse DNS delegation point that might be served by an RIR (note
that the dsData digest value has been modified to fit on one line).</t>
<figure anchor="ure-23"><artwork><![CDATA[ anchor="ure-23" align="left" suppress-title="false" pn="figure-23">
<sourcecode type="json" markers="false" pn="section-5.3-9.1">
{
"objectClassName" : "domain",
"handle" : "XXXX",
"ldhName" : "0.2.192.in-addr.arpa",
"nameservers" :
[
{
"objectClassName" : "nameserver",
"ldhName" : "ns1.rir.example"
},
{
"objectClassName" : "nameserver",
"ldhName" : "ns2.rir.example"
}
],
"secureDNS":
{
"delegationSigned": true,
"dsData":
[
{
"keyTag": 25345,
"algorithm": 8,
"digestType": 2,
"digest": "2788970E18EA14...C890C85B8205B94"
}
]
},
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value": "https://example.net/domain/0.2.192.in-addr.arpa",
"rel" : "self",
"href" : "https://example.net/domain/0.2.192.in-addr.arpa",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z",
"eventActor" : "joe@example.com"
}
],
"entities" :
[
{
"objectClassName" : "entity",
"handle" : "XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["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"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
]
]
],
"roles" : [ "registrant" ],
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value": "https://example.net/entity/XXXX",
"rel" : "self",
"href" : "https://example.net/entity/XXXX",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z",
"eventActor" : "joe@example.com"
}
]
}
],
"network" :
{
"objectClassName" : "ip network",
"handle" : "XXXX-RIR",
"startAddress" : "192.0.2.0",
"endAddress" : "192.0.2.255",
"ipVersion" : "v4",
"name": "NET-RTR-1",
"type" : "DIRECT ALLOCATION",
"country" : "AU",
"parentHandle" : "YYYY-RIR",
"status" : [ "active" ]
}
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.3-10">
The following is an example of a JSON domain object representing a
forward DNS delegation point that might be served by a DNR. Note that
the secureDNS keyData publicKey value has been modified to fit on a
single line.</t>
<figure anchor="ure-24"><artwork><![CDATA[ anchor="ure-24" align="left" suppress-title="false" pn="figure-24">
<sourcecode type="json" markers="false" pn="section-5.3-11.1">
{
"objectClassName" : "domain",
"handle" : "XXXX",
"ldhName" : "xn--fo-5ja.example",
"unicodeName" : "fóo.example",
"variants" :
[
{
"relation" : [ "registered", "conjoined" ],
"variantNames" :
[
{
"ldhName" : "xn--fo-cka.example",
"unicodeName" : "fõo.example"
},
{
"ldhName" : "xn--fo-fka.example",
"unicodeName" : "föo.example"
}
]
},
{
"relation" : [ "unregistered", "registration restricted" ],
"idnTable": ".EXAMPLE Swedish",
"variantNames" :
[
{
"ldhName": "xn--fo-8ja.example",
"unicodeName" : "fôo.example"
}
]
}
],
"status" : [ "locked", "transfer prohibited" ],
"publicIds":[
{
"type":"ENS_Auth ID",
"identifier":"1234567890"
}
],
"nameservers" :
[
{
"objectClassName" : "nameserver",
"handle" : "XXXX",
"ldhName" : "ns1.example.com",
"status" : [ "active" ],
"ipAddresses" :
{
"v6": [ "2001:db8::123", "2001:db8::124" ],
"v4": [ "192.0.2.1", "192.0.2.2" ]
},
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/nameserver/ns1.example.com",
"rel" : "self",
"href" : "https://example.net/nameserver/ns1.example.com",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
]
},
{
"objectClassName" : "nameserver",
"handle" : "XXXX",
"ldhName" : "ns2.example.com",
"status" : [ "active" ],
"ipAddresses" :
{
"v6" : [ "2001:db8::125", "2001:db8::126" ],
"v4" : [ "192.0.2.3", "192.0.2.4" ]
},
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/nameserver/ns2.example.com",
"rel" : "self",
"href" : "https://example.net/nameserver/ns2.example.com",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
]
}
],
"secureDNS":
{
"zoneSigned": true,
"delegationSigned": true,
"maxSigLife": 604800,
"keyData":
[
{
"flags": 257,
"protocol": 3,
"algorithm": 8,
"publicKey": "AwEAAa6eDzronzjEDbT...Jg1M5N rBSPkuXpdFE=",
"events":
[
{
"eventAction": "last changed",
"eventDate": "2012-07-23T05:15:47Z"
}
]
}
]
},
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value": "https://example.net/domain/xn--fo-5ja.example",
"rel" : "self",
"href" : "https://example.net/domain/xn--fo-5ja.example",
"type" : "application/rdap+json"
}
],
"port43" : "whois.example.net",
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z",
"eventActor" : "joe@example.com"
},
{
"eventAction" : "transfer",
"eventDate" : "1991-12-31T23:59:59Z",
"eventActor" : "joe@example.com"
},
{
"eventAction" : "expiration",
"eventDate" : "2016-12-31T23:59:59Z",
"eventActor" : "joe@example.com"
}
],
"entities" :
[
{
"objectClassName" : "entity",
"handle" : "XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["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"
]
],
["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" ],
"roles" : [ "registrant" ],
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/entity/XXXX",
"rel" : "self",
"href" : "https://example.net/entity/XXXX",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="The anchor="sect-5.4" numbered="true" toc="include" removeInRFC="false" pn="section-5.4">
<name slugifiedName="name-the-ip-network-object-class">The IP Network Object Class" anchor="sect-5.4"><t> Class</name>
<t indent="0" pn="section-5.4-1">
The IP network object class models IP network registrations found in
RIRs and is the expected response for the "/ip" query as defined by
<xref target="I-D.ietf-regext-rfc7482bis"/>. target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>. 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.).</t>
<t>
<t indent="0" pn="section-5.4-2">
The following is an elided example of the IP network object type
showing the high-level structure:</t>
<figure anchor="ure-25"><artwork><![CDATA[ anchor="ure-25" align="left" suppress-title="false" pn="figure-25">
<sourcecode type="json" markers="false" pn="section-5.4-3.1">
{
"objectClassName" : "ip network",
"handle" : "XXX",
...
"entities" :
[
...
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.4-4">
The following is an example of the JSON object for the network
registration information.</t>
<figure anchor="ure-26"><artwork><![CDATA[ anchor="ure-26" align="left" suppress-title="false" pn="figure-26">
<sourcecode type="json" markers="false" pn="section-5.4-5.1">
{
"objectClassName" : "ip network",
"handle" : "XXXX-RIR",
"startAddress" : "2001:db8::",
"endAddress" : "2001:db8:0:ffff:ffff:ffff:ffff:ffff",
"ipVersion" : "v6",
"name": "NET-RTR-1",
"type" : "DIRECT ALLOCATION",
"country" : "AU",
"parentHandle" : "YYYY-RIR",
"status" : [ "active" ],
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/ip/2001:db8::/48",
"rel" : "self",
"href" : "https://example.net/ip/2001:db8::/48",
"type" : "application/rdap+json"
},
{
"value" : "https://example.net/ip/2001:db8::/48",
"rel" : "up",
"href" : "https://example.net/ip/2001:db8::/32",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
],
"entities" :
[
{
"objectClassName" : "entity",
"handle" : "XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["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"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
]
]
],
"roles" : [ "registrant" ],
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/entity/xxxx",
"rel" : "self",
"href" : "https://example.net/entity/xxxx",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.4-6">
The IP network object class can contain the following members:</t>
<t><list style="symbols"><t>objectClassName
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.4-7">
<li pn="section-5.4-7.1">objectClassName -- the string "ip network"</t>
<t>handle network"</li>
<li pn="section-5.4-7.2">handle -- a string representing the RIR-unique identifier of the
network registration</t>
<t>startAddress registration</li>
<li pn="section-5.4-7.3">startAddress -- a string representing the starting IP address of the network, either
IPv4 or IPv6</t>
<t>endAddress IPv6</li>
<li pn="section-5.4-7.4">endAddress -- a string representing the ending IP address of the network, either IPv4 or
IPv6</t>
<t>ipVersion
IPv6</li>
<li pn="section-5.4-7.5">ipVersion -- a string signifying the IP protocol version of the
network: "v4" signifies an IPv4 network, and "v6" signifies an
IPv6 network</t>
<t>name network</li>
<li pn="section-5.4-7.6">name -- a string representing an identifier assigned to the network registration by the
registration holder</t>
<t>type holder</li>
<li pn="section-5.4-7.7">type -- a string containing an RIR-specific classification of the
network as per that RIR's registration model
</t>
<t>country
</li>
<li pn="section-5.4-7.8">country -- a string containing the two-character country code of
the network</t>
<t>parentHandle network</li>
<li pn="section-5.4-7.9">parentHandle -- a string containing an RIR-unique identifier of
the parent network of this network registration</t>
<t>status registration</li>
<li pn="section-5.4-7.10">status -- an array of strings indicating the state of the IP
network as defined by <xref target="sect-4.6"/></t>
<t>entities target="sect-4.6" format="default" sectionFormat="of" derivedContent="Section 4.6"/></li>
<li pn="section-5.4-7.11">entities -- an array of entity objects as defined by <xref target="sect-5.1"/>
</t>
<t>remarks target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>
</li>
<li pn="section-5.4-7.12">remarks -- see <xref target="sect-4.3"/>
</t>
<t>links target="sect-4.3" format="default" sectionFormat="of" derivedContent="Section 4.3"/>
</li>
<li pn="section-5.4-7.13">links -- see <xref target="sect-4.2"/>
</t>
<t>port43 target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
<li pn="section-5.4-7.14">port43 -- see <xref target="sect-4.7"/>
</t>
<t>events target="sect-4.7" format="default" sectionFormat="of" derivedContent="Section 4.7"/>
</li>
<li pn="section-5.4-7.15">events -- see <xref target="sect-4.5"/>
</t>
</list>
</t> target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
</ul>
</section>
<section title="The anchor="sect-5.5" numbered="true" toc="include" removeInRFC="false" pn="section-5.5">
<name slugifiedName="name-the-autonomous-system-numbe">The Autonomous System Number Object Class" anchor="sect-5.5"><t> Class</name>
<t indent="0" pn="section-5.5-1">
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 <xref target="I-D.ietf-regext-rfc7482bis"/>. target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/>. There is no
equivalent object class for DNRs. The high-level structure of the
autnum object class consists of information about the autonomous system 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.</t>
<t>
<t indent="0" pn="section-5.5-2">
The following is an example of a JSON object representing an autnum.</t>
<figure anchor="ure-27"><artwork><![CDATA[ anchor="ure-27" align="left" suppress-title="false" pn="figure-27">
<sourcecode type="json" markers="false" pn="section-5.5-3.1">
{
"objectClassName" : "autnum",
"handle" : "XXXX-RIR",
"startAutnum" : 65536,
"endAutnum" : 65541,
"name": "AS-RTR-1",
"type" : "DIRECT ALLOCATION",
"status" : [ "active" ],
"country": "AU",
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/autnum/65537",
"rel" : "self",
"href" : "https://example.net/autnum/65537",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
],
"entities" :
[
{
"objectClassName" : "entity",
"handle" : "XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["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"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
]
]
],
"roles" : [ "registrant" ],
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"links" :
[
{
"value" : "https://example.net/entity/XXXX",
"rel" : "self",
"href" : "https://example.net/entity/XXXX",
"type" : "application/rdap+json"
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-5.5-4">
The Autonomous System number object class can contain the following
members:</t>
<t><list style="symbols"><t>objectClassName
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5.5-5">
<li pn="section-5.5-5.1">objectClassName -- the string "autnum"</t>
<t>handle "autnum"</li>
<li pn="section-5.5-5.2">handle -- a string representing the RIR-unique identifier of the
autnum registration</t>
<t>startAutnum registration</li>
<li pn="section-5.5-5.3">startAutnum -- an unsigned 32-bit integer representing the starting number <xref target="RFC5396"/> target="RFC5396" format="default" sectionFormat="of" derivedContent="RFC5396"/>
in the block of Autonomous System numbers</t>
<t>endAutnum numbers</li>
<li pn="section-5.5-5.4">endAutnum -- an unsigned 32-bit integer representing the ending number <xref target="RFC5396"/> target="RFC5396" format="default" sectionFormat="of" derivedContent="RFC5396"/> in
the block of Autonomous System numbers</t>
<t>name numbers</li>
<li pn="section-5.5-5.5">name -- a string representing an identifier assigned to the autnum registration by the
registration holder</t>
<t>type holder</li>
<li pn="section-5.5-5.6">type -- a string containing an RIR-specific classification of the
autnum as per that RIR's registration model</t>
<t>status model</li>
<li pn="section-5.5-5.7">status -- an array of strings indicating the state of the autnum as defined by <xref target="sect-4.6"/></t>
<t>country target="sect-4.6" format="default" sectionFormat="of" derivedContent="Section 4.6"/></li>
<li pn="section-5.5-5.8">country -- a string containing the two-character country
code of the autnum</t>
<t>entities autnum</li>
<li pn="section-5.5-5.9">entities -- an array of entity objects as defined by <xref target="sect-5.1"/>
</t>
<t>remarks target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>
</li>
<li pn="section-5.5-5.10">remarks -- see <xref target="sect-4.3"/>
</t>
<t>links target="sect-4.3" format="default" sectionFormat="of" derivedContent="Section 4.3"/>
</li>
<li pn="section-5.5-5.11">links -- see <xref target="sect-4.2"/>
</t>
<t>port43 target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
<li pn="section-5.5-5.12">port43 -- see <xref target="sect-4.7"/>
</t>
<t>events target="sect-4.7" format="default" sectionFormat="of" derivedContent="Section 4.7"/>
</li>
<li pn="section-5.5-5.13">events -- see <xref target="sect-4.5"/>
</t>
</list>
</t> target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
</ul>
</section>
</section>
<section title="Error anchor="sect-6" numbered="true" toc="include" removeInRFC="false" pn="section-6">
<name slugifiedName="name-error-response-body">Error Response Body" anchor="sect-6"><t> Body</name>
<t indent="0" pn="section-6-1">
Some non-answer responses MAY <bcp14>MAY</bcp14> return entity bodies with information
that could be more descriptive.</t>
<t>
<t indent="0" pn="section-6-2">
The basic structure of that response is an object class containing a
REQUIRED
<bcp14>REQUIRED</bcp14> error code number (corresponding to the HTTP response code) followed
by an OPTIONAL <bcp14>OPTIONAL</bcp14> string named "title" and an OPTIONAL <bcp14>OPTIONAL</bcp14> array of strings named
"description".</t>
<t>
<t indent="0" pn="section-6-3">
This is an example of the common response body.</t>
<figure anchor="ure-28"><artwork><![CDATA[ anchor="ure-28" align="left" suppress-title="false" pn="figure-28">
<sourcecode type="json" markers="false" pn="section-6-4.1">
{
"errorCode": 418,
"title": "Your Beverage Choice is Not Available",
"description":
[
"I know coffee has more ummppphhh.",
"Sorry, dude!"
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-6-5">
This is an example of the common response body with an
rdapConformance and notices data structures:</t>
<figure anchor="ure-29"><artwork><![CDATA[ anchor="ure-29" align="left" suppress-title="false" pn="figure-29">
<sourcecode type="json" markers="false" pn="section-6-6.1">
{
"rdapConformance" :
[
"rdap_level_0"
],
"notices" :
[
{
"title" : "Beverage Policy",
"description" :
[
"Beverages with caffeine for keeping horses awake."
],
"links" :
[
{
"value" : "https://example.net/ip/192.0.2.0/24",
"rel" : "alternate",
"type" : "text/html",
"href" : "https://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!"
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Responding anchor="sect-7" numbered="true" toc="include" removeInRFC="false" pn="section-7">
<name slugifiedName="name-responding-to-help-queries">Responding to Help Queries" anchor="sect-7"><t> Queries</name>
<t indent="0" pn="section-7-1">
The appropriate response to /help queries as defined by <xref target="I-D.ietf-regext-rfc7482bis"/> target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/> is
to use the notices structure as defined in <xref target="sect-4.3"/>.</t>
<t> target="sect-4.3" format="default" sectionFormat="of" derivedContent="Section 4.3"/>.</t>
<t indent="0" pn="section-7-2">
This is an example of a response to a /help query including the
rdapConformance data structure.</t>
<figure anchor="ure-30"><artwork><![CDATA[ anchor="ure-30" align="left" suppress-title="false" pn="figure-30">
<sourcecode type="json" markers="false" pn="section-7-3.1">
{
"rdapConformance" :
[
"rdap_level_0"
],
"notices" :
[
{
"title" : "Authentication Policy",
"description" :
[
"Access to sensitive data for users with proper credentials."
],
"links" :
[
{
"value" : "https://example.net/help",
"rel" : "alternate",
"type" : "text/html",
"href" : "https://www.example.com/auth_policy.html"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Responding anchor="sect-8" numbered="true" toc="include" removeInRFC="false" pn="section-8">
<name slugifiedName="name-responding-to-searches">Responding To Searches" anchor="sect-8"><t> Searches</name>
<t indent="0" pn="section-8-1">
<xref target="I-D.ietf-regext-rfc7482bis"/> target="RFC9082" format="default" sectionFormat="of" derivedContent="RFC9082"/> 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.</t>
<t>
<t indent="0" pn="section-8-2">
The names of the arrays are as follows:</t>
<t><list style="symbols"><t>for
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-8-3">
<li pn="section-8-3.1">for /domains searches, the array is "domainSearchResults"</t>
<t>for "domainSearchResults"</li>
<li pn="section-8-3.2">for /nameservers searches, the array is "nameserverSearchResults"</t>
<t>for "nameserverSearchResults"</li>
<li pn="section-8-3.3">for /entities searches, the array is "entitySearchResults"</t>
</list>
</t>
<t> "entitySearchResults"</li>
</ul>
<t indent="0" pn="section-8-4">
The following is an elided example of a response to a /domains
search.</t>
<figure anchor="ure-31"><artwork><![CDATA[ anchor="ure-31" align="left" suppress-title="false" pn="figure-31">
<sourcecode type="json" markers="false" pn="section-8-5.1">
{
"rdapConformance" :
[
"rdap_level_0"
],
...
"domainSearchResults" :
[
{
"objectClassName" : "domain",
"handle" : "1-XXXX",
"ldhName" : "1.example.com",
...
},
{
"objectClassName" : "domain",
"handle" : "2-XXXX",
"ldhName" : "2.example.com",
...
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Indicating anchor="sect-9" numbered="true" toc="include" removeInRFC="false" pn="section-9">
<name slugifiedName="name-indicating-truncated-respon">Indicating Truncated Responses" anchor="sect-9"><t> Responses</name>
<t indent="0" pn="section-9-1">
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.</t>
<t>
<t indent="0" pn="section-9-2">
The following is an elided example of a search response that has been
truncated.</t>
<figure anchor="ure-32"><artwork><![CDATA[ anchor="ure-32" align="left" suppress-title="false" pn="figure-32">
<sourcecode type="json" markers="false" pn="section-9-3.1">
{
"rdapConformance" :
[
"rdap_level_0"
],
"notices" :
[
{
"title" : "Search Policy",
"type" : "result set truncated due to authorization",
"description" :
[
"Search results are limited to 25 per day per querying IP."
],
"links" :
[
{
"value" : "https://example.net/help",
"rel" : "alternate",
"type" : "text/html",
"href" : "https://www.example.com/search_policy.html"
}
]
}
],
"domainSearchResults" :
[
...
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-9-4">
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.</t>
<t>
<t indent="0" pn="section-9-5">
The following is an elided example of an entity truncated data.</t>
<figure anchor="ure-33"><artwork><![CDATA[ anchor="ure-33" align="left" suppress-title="false" pn="figure-33">
<sourcecode type="json" markers="false" pn="section-9-6.1">
{
"objectClassName" : "entity",
"handle" : "ANENTITY",
"roles" : [ "registrant" ],
...
"entities" :
[
{
"objectClassName" : "entity",
"handle": "ANEMBEDDEDENTITY",
"roles" : [ "technical" ],
...
},
...
],
"networks" :
[
...
],
...
"remarks" :
[
{
"title" : "Data Policy",
"type" : "object truncated due to unexplainable reason",
"description" :
[
"Some of the data in this object has been removed."
],
"links" :
[
{
"value" : "https://example.net/help",
"rel" : "alternate",
"type" : "text/html",
"href" : "https://www.example.com/data_policy.html"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="IANA Considerations" anchor="sect-10">
<t>IANA is requested to update anchor="sect-10" numbered="true" toc="include" removeInRFC="false" pn="section-10">
<name slugifiedName="name-iana-considerations">IANA Considerations</name>
<t indent="0" pn="section-10-1">IANA has updated the description of the "transfer" event action as described in <xref target="sect-10.2.3"/>.</t> target="sect-10.2.3" format="default" sectionFormat="of" derivedContent="Section 10.2.3"/>.</t>
<section title="RDAP anchor="sect-10.1" numbered="true" toc="include" removeInRFC="false" pn="section-10.1">
<name slugifiedName="name-rdap-json-media-type-regist">RDAP JSON Media Type Registration" anchor="sect-10.1">
<t>IANA is requested to update Registration</name>
<t indent="0" pn="section-10.1-1">IANA has updated the media type registration as described below.</t>
<t><list style="hanging" hangIndent="3"><t hangText="This
<t indent="0" pn="section-10.1-2">This specification registers the "application/rdap+json" "application/rdap+json" media type.">
<vspace blankLines="1"/> type.</t>
<dl indent="3" newline="false" spacing="normal" pn="section-10.1-3">
<dt pn="section-10.1-3.1">
Type name: name:</dt>
<dd pn="section-10.1-3.2"> application
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.3">
Subtype name: name:</dt>
<dd pn="section-10.1-3.4"> rdap+json
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.5">
Required parameters: parameters:</dt>
<dd pn="section-10.1-3.6"> n/a
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.7">
Encoding considerations: considerations:</dt>
<dd pn="section-10.1-3.8"> See Section 3.1 of <xref target="RFC6839"/>.
<vspace blankLines="1"/> target="RFC6839" section="3.1" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6839#section-3.1" derivedContent="RFC6839"/>.
</dd>
<dt pn="section-10.1-3.9">
Security considerations: The considerations:</dt>
<dd pn="section-10.1-3.10">The media represented by this identifier
does not have security considerations beyond that found in
Section 12 of
<xref target="RFC8259"/>.
<vspace blankLines="1"/> target="RFC8259" section="12" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-12" derivedContent="RFC8259"/>.
</dd>
<dt pn="section-10.1-3.11">
Interoperability considerations: considerations:</dt>
<dd pn="section-10.1-3.12"> There are no known
interoperability problems regarding this media format.
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.13">
Published specification: RFC <this new specification:</dt>
<dd pn="section-10.1-3.14"> RFC number>
<vspace blankLines="1"/> 9083
</dd>
<dt pn="section-10.1-3.15">
Applications that use this media type: type:</dt>
<dd pn="section-10.1-3.16"> Implementations of the
Registration Data Access Protocol (RDAP).
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.17">
Additional information: information:</dt>
<dd pn="section-10.1-3.18"> This media type is a product of the IETF
REGEXT working group. Working Group. The REGEXT charter, information on the
REGEXT mailing list, and other documents produced by the REGEXT
working group
Working Group can be found at
<eref target="https://datatracker.ietf.org/wg/regext/"/>.
<vspace blankLines="1"/> target="https://datatracker.ietf.org/wg/regext/" brackets="none"/>.
</dd>
<dt pn="section-10.1-3.19">
Person & email address to contact for further information: IESG information:</dt>
<dd pn="section-10.1-3.20">
<br/>IESG
<iesg@ietf.org>
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.21">
Intended usage: usage:</dt>
<dd pn="section-10.1-3.22"> COMMON
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.23">
Restrictions on usage: usage:</dt>
<dd pn="section-10.1-3.24"> none
<vspace blankLines="1"/>
Author:
</dd>
<dt pn="section-10.1-3.25">
Author:</dt>
<dd pn="section-10.1-3.26"> Andy Newton
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.27">
Change controller: controller:</dt>
<dd pn="section-10.1-3.28"> IETF
<vspace blankLines="1"/>
</dd>
<dt pn="section-10.1-3.29">
Provisional Registration: Registration:</dt>
<dd pn="section-10.1-3.30"> No (upon publication of this RFC)
</t>
</list>
</t>
</dd>
</dl>
</section>
<section title="JSON anchor="sect-10.2" numbered="true" toc="include" removeInRFC="false" pn="section-10.2">
<name slugifiedName="name-json-values-registry">JSON Values Registry" anchor="sect-10.2"><t> Registry</name>
<t indent="0" pn="section-10.2-1">
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 (<xref target="sect-4.3"/>), target="sect-4.3" format="default" sectionFormat="of" derivedContent="Section 4.3"/>), status (<xref target="sect-4.6"/>), target="sect-4.6" format="default" sectionFormat="of" derivedContent="Section 4.6"/>), role
(<xref target="sect-5.1"/>), target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>), event action (<xref target="sect-4.5"/>), target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>), and domain variant
relation (<xref target="sect-5.3"/>) target="sect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.3"/>) fields specified in RDAP.</t>
<t>
<t indent="0" pn="section-10.2-2">
Each entry in the registry contains the following fields:</t>
<t><list style="numbers"><t>Value
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-10.2-3"><li pn="section-10.2-3.1" derivedCounter="1.">Value -- the string value being registered.</t>
<t>Type registered.</li>
<li pn="section-10.2-3.2" derivedCounter="2.">
<t indent="0" pn="section-10.2-3.2.1">Type -- the type of value being registered. It should be one of
the following:<list style="symbols"><t>"notice following:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-10.2-3.2.2">
<li pn="section-10.2-3.2.2.1">"notice or remark type" -- denotes a type of notice or remark.</t>
<t>"status" remark.</li>
<li pn="section-10.2-3.2.2.2">"status" -- denotes a value for the "status" object member as
defined by <xref target="sect-4.6"/>.</t>
<t>"role" target="sect-4.6" format="default" sectionFormat="of" derivedContent="Section 4.6"/>.</li>
<li pn="section-10.2-3.2.2.3">"role" -- denotes a value for the "role" array as defined in
<xref target="sect-5.1"/>.</t>
<t>"event target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>.</li>
<li pn="section-10.2-3.2.2.4">"event action" -- denotes a value for an event action as
defined in <xref target="sect-4.5"/>.</t>
<t>"domain target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>.</li>
<li pn="section-10.2-3.2.2.5">"domain variant relation" -- denotes a relationship between a
domain and a domain variant as defined in <xref target="sect-5.3"/>.</t>
</list>
</t>
<t>Description target="sect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.3"/>.</li>
</ul>
</li>
<li pn="section-10.2-3.3" derivedCounter="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.</t>
<t>Registrant clients.</li>
<li pn="section-10.2-3.4" derivedCounter="4.">Registrant Name -- the name of the person registering the value.</t>
<t>Registrant value.</li>
<li pn="section-10.2-3.5" derivedCounter="5.">Registrant Contact Information -- an email address, postal
address, or some other information to be used to contact the
registrant.</t>
</list>
</t>
<t>
registrant.</li>
</ol>
<t indent="0" pn="section-10.2-4">
This registry is operated under the "Expert Review" policy defined in
<xref target="RFC8126"/>.</t>
<t> target="RFC8126" format="default" sectionFormat="of" derivedContent="RFC8126"/>.</t>
<t indent="0" pn="section-10.2-5">
Review of registrations into this registry by the designated
expert(s) should be narrowly judged on the following criteria:</t>
<t><list style="numbers"><t>Values
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-10.2-6"><li pn="section-10.2-6.1" derivedCounter="1.">Values in need of being placed into multiple types must be
assigned a separate registration for each type.</t>
<t>Values type.</li>
<li pn="section-10.2-6.2" derivedCounter="2.">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.</t>
<t>Registrations US-ASCII.</li>
<li pn="section-10.2-6.3" derivedCounter="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.</t>
<t>Registrations similarity.</li>
<li pn="section-10.2-6.4" derivedCounter="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.</t>
</list>
</t>
<t> determination.</li>
</ol>
<t indent="0" pn="section-10.2-7">
The following sections provide initial registrations into this
registry.</t>
<section title="Notice anchor="sect-10.2.1" numbered="true" toc="include" removeInRFC="false" pn="section-10.2.1">
<name slugifiedName="name-notice-and-remark-types">Notice and Remark Types" anchor="sect-10.2.1"><t> Types</name>
<t indent="0" pn="section-10.2.1-1">
The following values have been registered in the "RDAP JSON Values"
registry:</t>
<t>
<list style="none">
<t>Value: result
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-2">
<dt pn="section-10.2.1-2.1">Value:</dt>
<dd pn="section-10.2.1-2.2">result set truncated due to authorization<vspace blankLines="0"/>
Type: notice authorization</dd>
<dt pn="section-10.2.1-2.3">Type:</dt>
<dd pn="section-10.2.1-2.4">notice and remark type<vspace blankLines="0"/>
Description: The type</dd>
<dt pn="section-10.2.1-2.5">Description:</dt>
<dd pn="section-10.2.1-2.6">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.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: result
set.</dd>
<dt pn="section-10.2.1-2.7">Registrant Name:</dt>
<dd pn="section-10.2.1-2.8">IESG</dd>
<dt pn="section-10.2.1-2.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.1-2.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-3">
<dt pn="section-10.2.1-3.1">Value:</dt>
<dd pn="section-10.2.1-3.2">result set truncated due to excessive load<vspace blankLines="0"/>
Type: notice load</dd>
<dt pn="section-10.2.1-3.3">Type:</dt>
<dd pn="section-10.2.1-3.4">notice and remark type<vspace blankLines="0"/>
Description: The type</dd>
<dt pn="section-10.2.1-3.5">Description:</dt>
<dd pn="section-10.2.1-3.6">The list of results does not contain all results due to an excessively heavy load on the server.
This may indicate to some clients that requerying at a later time will yield a longer result
set.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: result
set.</dd>
<dt pn="section-10.2.1-3.7">Registrant Name:</dt>
<dd pn="section-10.2.1-3.8">IESG</dd>
<dt pn="section-10.2.1-3.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.1-3.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-4">
<dt pn="section-10.2.1-4.1">Value:</dt>
<dd pn="section-10.2.1-4.2">result set truncated due to unexplainable reasons<vspace blankLines="0"/>
Type: notice reasons</dd>
<dt pn="section-10.2.1-4.3">Type:</dt>
<dd pn="section-10.2.1-4.4">notice and remark type<vspace blankLines="0"/>
Description: The type</dd>
<dt pn="section-10.2.1-4.5">Description:</dt>
<dd pn="section-10.2.1-4.6">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.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: object set.</dd>
<dt pn="section-10.2.1-4.7">Registrant Name:</dt>
<dd pn="section-10.2.1-4.8">IESG</dd>
<dt pn="section-10.2.1-4.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.1-4.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-5">
<dt pn="section-10.2.1-5.1">Value:</dt>
<dd pn="section-10.2.1-5.2">object truncated due to authorization<vspace blankLines="0"/>
Type: notice authorization</dd>
<dt pn="section-10.2.1-5.3">Type:</dt>
<dd pn="section-10.2.1-5.4">notice and remark type<vspace blankLines="0"/>
Description: The type</dd>
<dt pn="section-10.2.1-5.5">Description:</dt>
<dd pn="section-10.2.1-5.6">The object does not contain all data due to lack of authorization.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: object authorization.</dd>
<dt pn="section-10.2.1-5.7">Registrant Name:</dt>
<dd pn="section-10.2.1-5.8">IESG</dd>
<dt pn="section-10.2.1-5.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.1-5.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-6">
<dt pn="section-10.2.1-6.1">Value:</dt>
<dd pn="section-10.2.1-6.2">object truncated due to excessive load<vspace blankLines="0"/>
Type: notice load</dd>
<dt pn="section-10.2.1-6.3">Type:</dt>
<dd pn="section-10.2.1-6.4">notice and remark type<vspace blankLines="0"/>
Description: The type</dd>
<dt pn="section-10.2.1-6.5">Description:</dt>
<dd pn="section-10.2.1-6.6">The object does not contain all data due to an 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.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: object object.</dd>
<dt pn="section-10.2.1-6.7">Registrant Name:</dt>
<dd pn="section-10.2.1-6.8">IESG</dd>
<dt pn="section-10.2.1-6.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.1-6.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-7">
<dt pn="section-10.2.1-7.1">Value:</dt>
<dd pn="section-10.2.1-7.2">object truncated due to unexplainable reasons<vspace blankLines="0"/>
Type: notice reasons</dd>
<dt pn="section-10.2.1-7.3">Type:</dt>
<dd pn="section-10.2.1-7.4">notice and remark type<vspace blankLines="0"/>
Description: The type</dd>
<dt pn="section-10.2.1-7.5">Description:</dt>
<dd pn="section-10.2.1-7.6">The object does not contain all data for an unexplainable reason.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t> reason.</dd>
<dt pn="section-10.2.1-7.7">Registrant Name:</dt>
<dd pn="section-10.2.1-7.8">IESG</dd>
<dt pn="section-10.2.1-7.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.1-7.10">iesg@ietf.org</dd>
</dl>
</section>
<section title="Status" anchor="sect-10.2.2">
<t>The anchor="sect-10.2.2" numbered="true" toc="include" removeInRFC="false" pn="section-10.2.2">
<name slugifiedName="name-status-2">Status</name>
<t indent="0" pn="section-10.2.2-1">The following values have been registered in the "RDAP JSON Values" registry:</t>
<t>
<list style="none">
<t>Value: validated<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Signifies
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-2">
<dt pn="section-10.2.2-2.1">Value:</dt>
<dd pn="section-10.2.2-2.2">validated</dd>
<dt pn="section-10.2.2-2.3">Type:</dt>
<dd pn="section-10.2.2-2.4">status</dd>
<dt pn="section-10.2.2-2.5">Description:</dt>
<dd pn="section-10.2.2-2.6">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.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: renew prohibited<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Renewal
information.</dd>
<dt pn="section-10.2.2-2.7">Registrant Name:</dt>
<dd pn="section-10.2.2-2.8">IESG</dd>
<dt pn="section-10.2.2-2.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-2.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-3">
<dt pn="section-10.2.2-3.1">Value:</dt>
<dd pn="section-10.2.2-3.2">renew prohibited</dd>
<dt pn="section-10.2.2-3.3">Type:</dt>
<dd pn="section-10.2.2-3.4">status</dd>
<dt pn="section-10.2.2-3.5">Description:</dt>
<dd pn="section-10.2.2-3.6">Renewal or reregistration of the object instance is forbidden.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: update prohibited<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Updates forbidden.</dd>
<dt pn="section-10.2.2-3.7">Registrant Name:</dt>
<dd pn="section-10.2.2-3.8">IESG</dd>
<dt pn="section-10.2.2-3.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-3.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-4">
<dt pn="section-10.2.2-4.1">Value:</dt>
<dd pn="section-10.2.2-4.2">update prohibited</dd>
<dt pn="section-10.2.2-4.3">Type:</dt>
<dd pn="section-10.2.2-4.4">status</dd>
<dt pn="section-10.2.2-4.5">Description:</dt>
<dd pn="section-10.2.2-4.6">Updates to the object instance are forbidden.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: transfer prohibited<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Transfers forbidden.</dd>
<dt pn="section-10.2.2-4.7">Registrant Name:</dt>
<dd pn="section-10.2.2-4.8">IESG</dd>
<dt pn="section-10.2.2-4.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-4.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-5">
<dt pn="section-10.2.2-5.1">Value:</dt>
<dd pn="section-10.2.2-5.2">transfer prohibited</dd>
<dt pn="section-10.2.2-5.3">Type:</dt>
<dd pn="section-10.2.2-5.4">status</dd>
<dt pn="section-10.2.2-5.5">Description:</dt>
<dd pn="section-10.2.2-5.6">Transfers of the registration from one registrar
to another are forbidden. This type of status normally applies to DNR
domain names.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: delete prohibited<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Deletion names.</dd>
<dt pn="section-10.2.2-5.7">Registrant Name:</dt>
<dd pn="section-10.2.2-5.8">IESG</dd>
<dt pn="section-10.2.2-5.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-5.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-6">
<dt pn="section-10.2.2-6.1">Value:</dt>
<dd pn="section-10.2.2-6.2">delete prohibited</dd>
<dt pn="section-10.2.2-6.3">Type:</dt>
<dd pn="section-10.2.2-6.4">status</dd>
<dt pn="section-10.2.2-6.5">Description:</dt>
<dd pn="section-10.2.2-6.6">Deletion of the registration of the object
instance is forbidden. This type of status normally applies to DNR
domain names.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: proxy<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: The names.</dd>
<dt pn="section-10.2.2-6.7">Registrant Name:</dt>
<dd pn="section-10.2.2-6.8">IESG</dd>
<dt pn="section-10.2.2-6.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-6.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-7">
<dt pn="section-10.2.2-7.1">Value:</dt>
<dd pn="section-10.2.2-7.2">proxy</dd>
<dt pn="section-10.2.2-7.3">Type:</dt>
<dd pn="section-10.2.2-7.4">status</dd>
<dt pn="section-10.2.2-7.5">Description:</dt>
<dd pn="section-10.2.2-7.6">The registration of the object instance has been performed
by a third party. This is most commonly applied to entities.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: private<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: The entities.</dd>
<dt pn="section-10.2.2-7.7">Registrant Name:</dt>
<dd pn="section-10.2.2-7.8">IESG</dd>
<dt pn="section-10.2.2-7.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-7.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-8">
<dt pn="section-10.2.2-8.1">Value:</dt>
<dd pn="section-10.2.2-8.2">private</dd>
<dt pn="section-10.2.2-8.3">Type:</dt>
<dd pn="section-10.2.2-8.4">status</dd>
<dt pn="section-10.2.2-8.5">Description:</dt>
<dd pn="section-10.2.2-8.6">The information of the object instance is not designated
for public consumption. This is most commonly applied to entities.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: removed<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Some entities.</dd>
<dt pn="section-10.2.2-8.7">Registrant Name:</dt>
<dd pn="section-10.2.2-8.8">IESG</dd>
<dt pn="section-10.2.2-8.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-8.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-9">
<dt pn="section-10.2.2-9.1">Value:</dt>
<dd pn="section-10.2.2-9.2">removed</dd>
<dt pn="section-10.2.2-9.3">Type:</dt>
<dd pn="section-10.2.2-9.4">status</dd>
<dt pn="section-10.2.2-9.5">Description:</dt>
<dd pn="section-10.2.2-9.6">Some of the information of the object instance has not
been made available and has been removed. This is most commonly applied to entities.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: obscured<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Some entities.</dd>
<dt pn="section-10.2.2-9.7">Registrant Name:</dt>
<dd pn="section-10.2.2-9.8">IESG</dd>
<dt pn="section-10.2.2-9.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-9.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-10">
<dt pn="section-10.2.2-10.1">Value:</dt>
<dd pn="section-10.2.2-10.2">obscured</dd>
<dt pn="section-10.2.2-10.3">Type:</dt>
<dd pn="section-10.2.2-10.4">status</dd>
<dt pn="section-10.2.2-10.5">Description:</dt>
<dd pn="section-10.2.2-10.6">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.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: associated<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: The entities.</dd>
<dt pn="section-10.2.2-10.7">Registrant Name:</dt>
<dd pn="section-10.2.2-10.8">IESG</dd>
<dt pn="section-10.2.2-10.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-10.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-11">
<dt pn="section-10.2.2-11.1">Value:</dt>
<dd pn="section-10.2.2-11.2">associated</dd>
<dt pn="section-10.2.2-11.3">Type:</dt>
<dd pn="section-10.2.2-11.4">status</dd>
<dt pn="section-10.2.2-11.5">Description:</dt>
<dd pn="section-10.2.2-11.6">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.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: active<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: The domain.</dd>
<dt pn="section-10.2.2-11.7">Registrant Name:</dt>
<dd pn="section-10.2.2-11.8">IESG</dd>
<dt pn="section-10.2.2-11.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-11.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-12">
<dt pn="section-10.2.2-12.1">Value:</dt>
<dd pn="section-10.2.2-12.2">active</dd>
<dt pn="section-10.2.2-12.3">Type:</dt>
<dd pn="section-10.2.2-12.4">status</dd>
<dt pn="section-10.2.2-12.5">Description:</dt>
<dd pn="section-10.2.2-12.6">The object instance is in use. For domain names, it signifies
that the domain name is published in DNS. For network and autnum registrations registrations,
it signifies that they are allocated or assigned for use in operational networks.
This maps to the "OK" status of the Extensible Provisioning Protocol (EPP) <xref target="RFC5730"></xref> 'OK' status.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: inactive<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: The target="RFC5730" format="default" sectionFormat="of" derivedContent="RFC5730"/>.</dd>
<dt pn="section-10.2.2-12.7">Registrant Name:</dt>
<dd pn="section-10.2.2-12.8">IESG</dd>
<dt pn="section-10.2.2-12.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-12.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-13">
<dt pn="section-10.2.2-13.1">Value:</dt>
<dd pn="section-10.2.2-13.2">inactive</dd>
<dt pn="section-10.2.2-13.3">Type:</dt>
<dd pn="section-10.2.2-13.4">status</dd>
<dt pn="section-10.2.2-13.5">Description:</dt>
<dd pn="section-10.2.2-13.6">The object instance is not in use. See 'active'.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: locked<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: Changes "active".</dd>
<dt pn="section-10.2.2-13.7">Registrant Name:</dt>
<dd pn="section-10.2.2-13.8">IESG</dd>
<dt pn="section-10.2.2-13.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-13.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-14">
<dt pn="section-10.2.2-14.1">Value:</dt>
<dd pn="section-10.2.2-14.2">locked</dd>
<dt pn="section-10.2.2-14.3">Type:</dt>
<dd pn="section-10.2.2-14.4">status</dd>
<dt pn="section-10.2.2-14.5">Description:</dt>
<dd pn="section-10.2.2-14.6">Changes to the object instance cannot be made, including the association of other
object instances.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: pending create<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: A instances.</dd>
<dt pn="section-10.2.2-14.7">Registrant Name:</dt>
<dd pn="section-10.2.2-14.8">IESG</dd>
<dt pn="section-10.2.2-14.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-14.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-15">
<dt pn="section-10.2.2-15.1">Value:</dt>
<dd pn="section-10.2.2-15.2">pending create</dd>
<dt pn="section-10.2.2-15.3">Type:</dt>
<dd pn="section-10.2.2-15.4">status</dd>
<dt pn="section-10.2.2-15.5">Description:</dt>
<dd pn="section-10.2.2-15.6">A request has been received for the creation of the object instance instance, but
this action is not yet complete.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: pending renew<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: A complete.</dd>
<dt pn="section-10.2.2-15.7">Registrant Name:</dt>
<dd pn="section-10.2.2-15.8">IESG</dd>
<dt pn="section-10.2.2-15.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-15.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-16">
<dt pn="section-10.2.2-16.1">Value:</dt>
<dd pn="section-10.2.2-16.2">pending renew</dd>
<dt pn="section-10.2.2-16.3">Type:</dt>
<dd pn="section-10.2.2-16.4">status</dd>
<dt pn="section-10.2.2-16.5">Description:</dt>
<dd pn="section-10.2.2-16.6">A request has been received for the renewal of the object instance instance, but
this action is not yet complete.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: pending transfer<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: A complete.</dd>
<dt pn="section-10.2.2-16.7">Registrant Name:</dt>
<dd pn="section-10.2.2-16.8">IESG</dd>
<dt pn="section-10.2.2-16.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-16.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-17">
<dt pn="section-10.2.2-17.1">Value:</dt>
<dd pn="section-10.2.2-17.2">pending transfer</dd>
<dt pn="section-10.2.2-17.3">Type:</dt>
<dd pn="section-10.2.2-17.4">status</dd>
<dt pn="section-10.2.2-17.5">Description:</dt>
<dd pn="section-10.2.2-17.6">A request has been received for the transfer of the object instance instance, but
this action is not yet complete.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: pending update<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: A complete.</dd>
<dt pn="section-10.2.2-17.7">Registrant Name:</dt>
<dd pn="section-10.2.2-17.8">IESG</dd>
<dt pn="section-10.2.2-17.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-17.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-18">
<dt pn="section-10.2.2-18.1">Value:</dt>
<dd pn="section-10.2.2-18.2">pending update</dd>
<dt pn="section-10.2.2-18.3">Type:</dt>
<dd pn="section-10.2.2-18.4">status</dd>
<dt pn="section-10.2.2-18.5">Description:</dt>
<dd pn="section-10.2.2-18.6">A request has been received for the update or modification of the object instance instance, but
this action is not yet complete.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: pending delete<vspace blankLines="0"/>
Type: status<vspace blankLines="0"/>
Description: A complete.</dd>
<dt pn="section-10.2.2-18.7">Registrant Name:</dt>
<dd pn="section-10.2.2-18.8">IESG</dd>
<dt pn="section-10.2.2-18.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-18.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-19">
<dt pn="section-10.2.2-19.1">Value:</dt>
<dd pn="section-10.2.2-19.2">pending delete</dd>
<dt pn="section-10.2.2-19.3">Type:</dt>
<dd pn="section-10.2.2-19.4">status</dd>
<dt pn="section-10.2.2-19.5">Description:</dt>
<dd pn="section-10.2.2-19.6">A request has been received for the deletion or removal of the object instance 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.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t> database.</dd>
<dt pn="section-10.2.2-19.7">Registrant Name:</dt>
<dd pn="section-10.2.2-19.8">IESG</dd>
<dt pn="section-10.2.2-19.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.2-19.10">iesg@ietf.org</dd>
</dl>
</section>
<section title="Event Actions" anchor="sect-10.2.3"><t> anchor="sect-10.2.3" numbered="true" toc="include" removeInRFC="false" pn="section-10.2.3">
<name slugifiedName="name-event-actions">Event Actions</name>
<t indent="0" pn="section-10.2.3-1">
The following values have been registered in the "RDAP JSON Values"
registry:</t>
<t>
<list style="none">
<t>Value: registration<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-2">
<dt pn="section-10.2.3-2.1">Value:</dt>
<dd pn="section-10.2.3-2.2">registration</dd>
<dt pn="section-10.2.3-2.3">Type:</dt>
<dd pn="section-10.2.3-2.4">event action</dd>
<dt pn="section-10.2.3-2.5">Description:</dt>
<dd pn="section-10.2.3-2.6">The object instance was initially registered.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: reregistration<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The registered.</dd>
<dt pn="section-10.2.3-2.7">Registrant Name:</dt>
<dd pn="section-10.2.3-2.8">IESG</dd>
<dt pn="section-10.2.3-2.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-2.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-3">
<dt pn="section-10.2.3-3.1">Value:</dt>
<dd pn="section-10.2.3-3.2">reregistration</dd>
<dt pn="section-10.2.3-3.3">Type:</dt>
<dd pn="section-10.2.3-3.4">event action</dd>
<dt pn="section-10.2.3-3.5">Description:</dt>
<dd pn="section-10.2.3-3.6">The object instance was registered subsequently to initial registration.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: last changed<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: An registration.</dd>
<dt pn="section-10.2.3-3.7">Registrant Name:</dt>
<dd pn="section-10.2.3-3.8">IESG</dd>
<dt pn="section-10.2.3-3.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-3.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-4">
<dt pn="section-10.2.3-4.1">Value:</dt>
<dd pn="section-10.2.3-4.2">last changed</dd>
<dt pn="section-10.2.3-4.3">Type:</dt>
<dd pn="section-10.2.3-4.4">event action</dd>
<dt pn="section-10.2.3-4.5">Description:</dt>
<dd pn="section-10.2.3-4.6">An action noting when the information in the object instance was last changed.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: expiration<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The changed.</dd>
<dt pn="section-10.2.3-4.7">Registrant Name:</dt>
<dd pn="section-10.2.3-4.8">IESG</dd>
<dt pn="section-10.2.3-4.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-4.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-5">
<dt pn="section-10.2.3-5.1">Value:</dt>
<dd pn="section-10.2.3-5.2">expiration</dd>
<dt pn="section-10.2.3-5.3">Type:</dt>
<dd pn="section-10.2.3-5.4">event action</dd>
<dt pn="section-10.2.3-5.5">Description:</dt>
<dd pn="section-10.2.3-5.6">The object instance has been removed or will be removed at a pre-determined predetermined
date and time from the registry.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: deletion<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The registry.</dd>
<dt pn="section-10.2.3-5.7">Registrant Name:</dt>
<dd pn="section-10.2.3-5.8">IESG</dd>
<dt pn="section-10.2.3-5.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-5.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-6">
<dt pn="section-10.2.3-6.1">Value:</dt>
<dd pn="section-10.2.3-6.2">deletion</dd>
<dt pn="section-10.2.3-6.3">Type:</dt>
<dd pn="section-10.2.3-6.4">event action</dd>
<dt pn="section-10.2.3-6.5">Description:</dt>
<dd pn="section-10.2.3-6.6">The object instance was removed from the registry at a point in time that was not pre-determined.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: reinstantiation<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The predetermined.</dd>
<dt pn="section-10.2.3-6.7">Registrant Name:</dt>
<dd pn="section-10.2.3-6.8">IESG</dd>
<dt pn="section-10.2.3-6.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-6.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-7">
<dt pn="section-10.2.3-7.1">Value:</dt>
<dd pn="section-10.2.3-7.2">reinstantiation</dd>
<dt pn="section-10.2.3-7.3">Type:</dt>
<dd pn="section-10.2.3-7.4">event action</dd>
<dt pn="section-10.2.3-7.5">Description:</dt>
<dd pn="section-10.2.3-7.6">The object instance was reregistered after having been
removed from the registry.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: transfer<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The registry.</dd>
<dt pn="section-10.2.3-7.7">Registrant Name:</dt>
<dd pn="section-10.2.3-7.8">IESG</dd>
<dt pn="section-10.2.3-7.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-7.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-8">
<dt pn="section-10.2.3-8.1">Value:</dt>
<dd pn="section-10.2.3-8.2">transfer</dd>
<dt pn="section-10.2.3-8.3">Type:</dt>
<dd pn="section-10.2.3-8.4">event action</dd>
<dt pn="section-10.2.3-8.5">Description:</dt>
<dd pn="section-10.2.3-8.6">The object instance was transferred from one registrar to another.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: locked<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The another.</dd>
<dt pn="section-10.2.3-8.7">Registrant Name:</dt>
<dd pn="section-10.2.3-8.8">IESG</dd>
<dt pn="section-10.2.3-8.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-8.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-9">
<dt pn="section-10.2.3-9.1">Value:</dt>
<dd pn="section-10.2.3-9.2">locked</dd>
<dt pn="section-10.2.3-9.3">Type:</dt>
<dd pn="section-10.2.3-9.4">event action</dd>
<dt pn="section-10.2.3-9.5">Description:</dt>
<dd pn="section-10.2.3-9.6">The object instance was locked (see the 'locked' status).<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: unlocked<vspace blankLines="0"/>
Type: event action<vspace blankLines="0"/>
Description: The "locked" status).</dd>
<dt pn="section-10.2.3-9.7">Registrant Name:</dt>
<dd pn="section-10.2.3-9.8">IESG</dd>
<dt pn="section-10.2.3-9.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-9.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-10">
<dt pn="section-10.2.3-10.1">Value:</dt>
<dd pn="section-10.2.3-10.2">unlocked</dd>
<dt pn="section-10.2.3-10.3">Type:</dt>
<dd pn="section-10.2.3-10.4">event action</dd>
<dt pn="section-10.2.3-10.5">Description:</dt>
<dd pn="section-10.2.3-10.6">The object instance was unlocked (see the 'locked' status).<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t> "locked" status).</dd>
<dt pn="section-10.2.3-10.7">Registrant Name:</dt>
<dd pn="section-10.2.3-10.8">IESG</dd>
<dt pn="section-10.2.3-10.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.3-10.10">iesg@ietf.org</dd>
</dl>
</section>
<section title="Roles" anchor="sect-10.2.4"><t> anchor="sect-10.2.4" numbered="true" toc="include" removeInRFC="false" pn="section-10.2.4">
<name slugifiedName="name-roles">Roles</name>
<t indent="0" pn="section-10.2.4-1">
The following values have been registered in the "RDAP JSON Values"
registry:</t>
<t>
<list style="none">
<t>Value: registrant<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-2">
<dt pn="section-10.2.4-2.1">Value:</dt>
<dd pn="section-10.2.4-2.2">registrant</dd>
<dt pn="section-10.2.4-2.3">Type:</dt>
<dd pn="section-10.2.4-2.4">role</dd>
<dt pn="section-10.2.4-2.5">Description:</dt>
<dd pn="section-10.2.4-2.6">The entity object instance is the registrant of the
registration. In some registries, this is known as a maintainer.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: technical<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The maintainer.</dd>
<dt pn="section-10.2.4-2.7">Registrant Name:</dt>
<dd pn="section-10.2.4-2.8">IESG</dd>
<dt pn="section-10.2.4-2.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-2.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-3">
<dt pn="section-10.2.4-3.1">Value:</dt>
<dd pn="section-10.2.4-3.2">technical</dd>
<dt pn="section-10.2.4-3.3">Type:</dt>
<dd pn="section-10.2.4-3.4">role</dd>
<dt pn="section-10.2.4-3.5">Description:</dt>
<dd pn="section-10.2.4-3.6">The entity object instance is a technical contact for the
registration.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: administrative<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The
registration.</dd>
<dt pn="section-10.2.4-3.7">Registrant Name:</dt>
<dd pn="section-10.2.4-3.8">IESG</dd>
<dt pn="section-10.2.4-3.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-3.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-4">
<dt pn="section-10.2.4-4.1">Value:</dt>
<dd pn="section-10.2.4-4.2">administrative</dd>
<dt pn="section-10.2.4-4.3">Type:</dt>
<dd pn="section-10.2.4-4.4">role</dd>
<dt pn="section-10.2.4-4.5">Description:</dt>
<dd pn="section-10.2.4-4.6">The entity object instance is an administrative contact for
the registration.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: abuse<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The registration.</dd>
<dt pn="section-10.2.4-4.7">Registrant Name:</dt>
<dd pn="section-10.2.4-4.8">IESG</dd>
<dt pn="section-10.2.4-4.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-4.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-5">
<dt pn="section-10.2.4-5.1">Value:</dt>
<dd pn="section-10.2.4-5.2">abuse</dd>
<dt pn="section-10.2.4-5.3">Type:</dt>
<dd pn="section-10.2.4-5.4">role</dd>
<dt pn="section-10.2.4-5.5">Description:</dt>
<dd pn="section-10.2.4-5.6">The entity object instance handles network abuse issues on
behalf of the registrant of the registration.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: billing<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The registration.</dd>
<dt pn="section-10.2.4-5.7">Registrant Name:</dt>
<dd pn="section-10.2.4-5.8">IESG</dd>
<dt pn="section-10.2.4-5.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-5.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-6">
<dt pn="section-10.2.4-6.1">Value:</dt>
<dd pn="section-10.2.4-6.2">billing</dd>
<dt pn="section-10.2.4-6.3">Type:</dt>
<dd pn="section-10.2.4-6.4">role</dd>
<dt pn="section-10.2.4-6.5">Description:</dt>
<dd pn="section-10.2.4-6.6">The entity object instance handles payment and billing
issues on behalf of the registrant of the registration.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: registrar<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The registration.</dd>
<dt pn="section-10.2.4-6.7">Registrant Name:</dt>
<dd pn="section-10.2.4-6.8">IESG</dd>
<dt pn="section-10.2.4-6.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-6.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-7">
<dt pn="section-10.2.4-7.1">Value:</dt>
<dd pn="section-10.2.4-7.2">registrar</dd>
<dt pn="section-10.2.4-7.3">Type:</dt>
<dd pn="section-10.2.4-7.4">role</dd>
<dt pn="section-10.2.4-7.5">Description:</dt>
<dd pn="section-10.2.4-7.6">The entity object instance represents the authority
responsible for the registration in the registry.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: reseller<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The registry.</dd>
<dt pn="section-10.2.4-7.7">Registrant Name:</dt>
<dd pn="section-10.2.4-7.8">IESG</dd>
<dt pn="section-10.2.4-7.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-7.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-8">
<dt pn="section-10.2.4-8.1">Value:</dt>
<dd pn="section-10.2.4-8.2">reseller</dd>
<dt pn="section-10.2.4-8.3">Type:</dt>
<dd pn="section-10.2.4-8.4">role</dd>
<dt pn="section-10.2.4-8.5">Description:</dt>
<dd pn="section-10.2.4-8.6">The entity object instance represents a third party
through which the registration was conducted (i.e. (i.e., not the registry or registrar).<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: sponsor<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The registrar).</dd>
<dt pn="section-10.2.4-8.7">Registrant Name:</dt>
<dd pn="section-10.2.4-8.8">IESG</dd>
<dt pn="section-10.2.4-8.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-8.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-9">
<dt pn="section-10.2.4-9.1">Value:</dt>
<dd pn="section-10.2.4-9.2">sponsor</dd>
<dt pn="section-10.2.4-9.3">Type:</dt>
<dd pn="section-10.2.4-9.4">role</dd>
<dt pn="section-10.2.4-9.5">Description:</dt>
<dd pn="section-10.2.4-9.6">The entity object instance represents a domain policy
sponsor, such as an ICANN approved sponsor.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: proxy<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The ICANN-approved sponsor.</dd>
<dt pn="section-10.2.4-9.7">Registrant Name:</dt>
<dd pn="section-10.2.4-9.8">IESG</dd>
<dt pn="section-10.2.4-9.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-9.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-10">
<dt pn="section-10.2.4-10.1">Value:</dt>
<dd pn="section-10.2.4-10.2">proxy</dd>
<dt pn="section-10.2.4-10.3">Type:</dt>
<dd pn="section-10.2.4-10.4">role</dd>
<dt pn="section-10.2.4-10.5">Description:</dt>
<dd pn="section-10.2.4-10.6">The entity object instance represents a proxy for another
entity object, such as a registrant.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: notifications<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: An registrant.</dd>
<dt pn="section-10.2.4-10.7">Registrant Name:</dt>
<dd pn="section-10.2.4-10.8">IESG</dd>
<dt pn="section-10.2.4-10.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-10.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-11">
<dt pn="section-10.2.4-11.1">Value:</dt>
<dd pn="section-10.2.4-11.2">notifications</dd>
<dt pn="section-10.2.4-11.3">Type:</dt>
<dd pn="section-10.2.4-11.4">role</dd>
<dt pn="section-10.2.4-11.5">Description:</dt>
<dd pn="section-10.2.4-11.6">An entity object instance designated to receive notifications about
association object instances.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: noc<vspace blankLines="0"/>
Type: role<vspace blankLines="0"/>
Description: The instances.</dd>
<dt pn="section-10.2.4-11.7">Registrant Name:</dt>
<dd pn="section-10.2.4-11.8">IESG</dd>
<dt pn="section-10.2.4-11.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-11.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-12">
<dt pn="section-10.2.4-12.1">Value:</dt>
<dd pn="section-10.2.4-12.2">noc</dd>
<dt pn="section-10.2.4-12.3">Type:</dt>
<dd pn="section-10.2.4-12.4">role</dd>
<dt pn="section-10.2.4-12.5">Description:</dt>
<dd pn="section-10.2.4-12.6">The entity object instance handles communications related to a
network operations center (NOC).<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t> (NOC).</dd>
<dt pn="section-10.2.4-12.7">Registrant Name:</dt>
<dd pn="section-10.2.4-12.8">IESG</dd>
<dt pn="section-10.2.4-12.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.4-12.10">iesg@ietf.org</dd>
</dl>
</section>
<section title="Variant Relations" anchor="sect-10.2.5"><t> anchor="sect-10.2.5" numbered="true" toc="include" removeInRFC="false" pn="section-10.2.5">
<name slugifiedName="name-variant-relations">Variant Relations</name>
<t indent="0" pn="section-10.2.5-1">
The following values have been registered in the "RDAP JSON Values"
registry:</t>
<t>
<list style="none">
<t>Value: registered<vspace blankLines="0"/>
Type: domain
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-2">
<dt pn="section-10.2.5-2.1">Value:</dt>
<dd pn="section-10.2.5-2.2">registered</dd>
<dt pn="section-10.2.5-2.3">Type:</dt>
<dd pn="section-10.2.5-2.4">domain variant relation<vspace blankLines="0"/>
Description: The relation</dd>
<dt pn="section-10.2.5-2.5">Description:</dt>
<dd pn="section-10.2.5-2.6">The variant names are registered in the registry.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: unregistered<vspace blankLines="0"/>
Type: domain registry.</dd>
<dt pn="section-10.2.5-2.7">Registrant Name:</dt>
<dd pn="section-10.2.5-2.8">IESG</dd>
<dt pn="section-10.2.5-2.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.5-2.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-3">
<dt pn="section-10.2.5-3.1">Value:</dt>
<dd pn="section-10.2.5-3.2">unregistered</dd>
<dt pn="section-10.2.5-3.3">Type:</dt>
<dd pn="section-10.2.5-3.4">domain variant relation<vspace blankLines="0"/>
Description: The relation</dd>
<dt pn="section-10.2.5-3.5">Description:</dt>
<dd pn="section-10.2.5-3.6">The variant names are not found in the registry.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: registration restricted<vspace blankLines="0"/>
Type: domain registry.</dd>
<dt pn="section-10.2.5-3.7">Registrant Name:</dt>
<dd pn="section-10.2.5-3.8">IESG</dd>
<dt pn="section-10.2.5-3.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.5-3.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-4">
<dt pn="section-10.2.5-4.1">Value:</dt>
<dd pn="section-10.2.5-4.2">registration restricted</dd>
<dt pn="section-10.2.5-4.3">Type:</dt>
<dd pn="section-10.2.5-4.4">domain variant relation<vspace blankLines="0"/>
Description: Registration relation</dd>
<dt pn="section-10.2.5-4.5">Description:</dt>
<dd pn="section-10.2.5-4.6">Registration of the variant names is
restricted to certain parties or within certain rules.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: open registration<vspace blankLines="0"/>
Type: domain rules.</dd>
<dt pn="section-10.2.5-4.7">Registrant Name:</dt>
<dd pn="section-10.2.5-4.8">IESG</dd>
<dt pn="section-10.2.5-4.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.5-4.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-5">
<dt pn="section-10.2.5-5.1">Value:</dt>
<dd pn="section-10.2.5-5.2">open registration</dd>
<dt pn="section-10.2.5-5.3">Type:</dt>
<dd pn="section-10.2.5-5.4">domain variant relation<vspace blankLines="0"/>
Description: Registration relation</dd>
<dt pn="section-10.2.5-5.5">Description:</dt>
<dd pn="section-10.2.5-5.6">Registration of the variant names is available to
generally qualified registrants.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t>
<t>
<list style="none">
<t>Value: conjoined<vspace blankLines="0"/>
Type: domain registrants.</dd>
<dt pn="section-10.2.5-5.7">Registrant Name:</dt>
<dd pn="section-10.2.5-5.8">IESG</dd>
<dt pn="section-10.2.5-5.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.5-5.10">iesg@ietf.org</dd>
</dl>
<dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-6">
<dt pn="section-10.2.5-6.1">Value:</dt>
<dd pn="section-10.2.5-6.2">conjoined</dd>
<dt pn="section-10.2.5-6.3">Type:</dt>
<dd pn="section-10.2.5-6.4">domain variant relation<vspace blankLines="0"/>
Description: Registration relation</dd>
<dt pn="section-10.2.5-6.5">Description:</dt>
<dd pn="section-10.2.5-6.6">Registration of the variant names occurs automatically with the
registration of the containing domain registration.<vspace blankLines="0"/>
Registrant Name: IESG<vspace blankLines="0"/>
Registrant Contact Information: iesg@ietf.org</t>
</list>
</t> registration.</dd>
<dt pn="section-10.2.5-6.7">Registrant Name:</dt>
<dd pn="section-10.2.5-6.8">IESG</dd>
<dt pn="section-10.2.5-6.9">Registrant Contact Information:</dt>
<dd pn="section-10.2.5-6.10">iesg@ietf.org</dd>
</dl>
</section>
</section>
</section>
<section anchor="impl-status" title="Implementation Status">
<t>NOTE: Please remove this section and the reference to RFC 7942 prior to publication as an RFC.</t>
<t>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 <xref target="RFC7942"/>. 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.</t>
<t>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".</t>
<section anchor="reddog" title="RedDog">
<t><list style="none">
<t>Responsible Organization: NIC Mexico</t>
<t>Location: https://reddog.mx/</t>
<t>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.</t>
<t>Level of Maturity: Production.</t>
<t>Coverage: RedDog supports all lookups, searches and responses for all object classes described in RFC 7482 and RFC 7483.</t>
<t>Version Compatibility: RFC 7482 and RFC 7483</t>
<t>Licensing: Apache License 2.0</t>
<t>Contact Information: reddog-dev@nic.mx</t>
<t>Information last updated: November 22, 2019</t>
</list></t>
</section>
<section anchor="vrsn" title="Verisign">
<t><list style="none">
<t>Responsible Organization: Verisign</t>
<t>Location: https://rdap.verisign.com/com/v1/, https://rdap.verisign.com/net/v1/</t>
<t>Description: Verisign's production RDAP service for the .com and .net gTLDs.</t>
<t>Level of Maturity: Production.</t>
<t>Coverage: Lookup of domain names, name servers, entities; name server search by IP address; help.</t>
<t>Version Compatibility: RFC 7483</t>
<t>Contact Information: info@verisign-grs.com</t>
</list></t>
</section>
<section anchor="vrsnlabs" title="Verisign Labs">
<t><list style="none">
<t>Responsible Organization: Verisign Labs</t>
<t>Location: https://rdap.verisignlabs.com/rdap/v1/</t>
<t>Description: Verisign's experimental RDAP service for the .cc and .tv ccTLDs.</t>
<t>Level of Maturity: Experimental.</t>
<t>Coverage: Lookup of domain names, name servers, entities; name server search by IP address; basic search; regular expression search; federated authentication; help.</t>
<t>Version Compatibility: RFC 7483</t>
<t>Contact Information: Scott Hollenbeck, shollenbeck@verisign.com</t>
</list></t>
</section>
<section anchor="apnic" title="Asia-Pacific Network Information Centre (APNIC)">
<t><list style="none">
<t>Responsible Organization: Asia-Pacific Network Information Centre (APNIC)
</t>
<t>Location: https://rdap.apnic.net/, https://github.com/APNIC-net/rdapd</t>
<t>Description: APNIC's production RDAP service for Internet number resouces.</t>
<t>Level of Maturity: Production.</t>
<t>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.</t>
<t>Version Compatibility: RFC 7483</t>
<t>Contact Information: helpdesk@apnic.net</t>
</list></t>
</section>
</section>
<section title="Security Considerations" anchor="sect-11"><t> anchor="sect-11" numbered="true" toc="include" removeInRFC="false" pn="section-11">
<name slugifiedName="name-security-considerations">Security Considerations</name>
<t indent="0" pn="section-11-1">
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 <xref target="RFC8259"/> target="RFC8259" section="12" sectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc8259#section-12" derivedContent="RFC8259"/> to
prevent code injection.</t>
<t>
<t indent="0" pn="section-11-2">
Though not specific to JSON, RDAP implementers should be aware of the
security considerations specified in <xref target="RFC7480"/> target="RFC7480" format="default" sectionFormat="of" derivedContent="RFC7480"/> and the security
requirements and considerations in <xref target="RFC7481"/>.</t>
<t>RDAP target="RFC7481" format="default" sectionFormat="of" derivedContent="RFC7481"/>.</t>
<t indent="0" pn="section-11-3">RDAP responses allow for retrieval of DNSSEC (key) related information,
but the RRSIG DS from the parent zone is not conveyed alongside it.
This means that the DNSSEC keys retrieved by RDAP are disconnected
from their containing PKI, and as such are not generally expected to
be trusted without additional information. In particular, the HTTPS
channel protecting the RDAP connection is not expected to be authorized
to certify the validity of the DNSSEC keys.</t>
<t>
<t indent="0" pn="section-11-4">
Clients caching data, especially clients using RDAP-specific caches
(instead of HTTP-layer caches), should have safeguards to prevent
cache poisoning. See <xref target="sect-5"/> target="sect-5" format="default" sectionFormat="of" derivedContent="Section 5"/> for advice on using the self links
for caching.</t>
<t>
<t indent="0" pn="section-11-5">
Finally, service operators should be aware of the privacy mechanisms
noted in <xref target="sect-13"/>.</t> target="sect-13" format="default" sectionFormat="of" derivedContent="Section 13"/>.</t>
</section>
<section title="Internationalization Considerations" anchor="sect-12"><section title="Character Encoding" anchor="sect-12.1"><t> anchor="sect-12" numbered="true" toc="include" removeInRFC="false" pn="section-12">
<name slugifiedName="name-internationalization-consid">Internationalization Considerations</name>
<section anchor="sect-12.1" numbered="true" toc="include" removeInRFC="false" pn="section-12.1">
<name slugifiedName="name-character-encoding">Character Encoding</name>
<t indent="0" pn="section-12.1-1">
The default text encoding for JSON responses in RDAP is UTF-8
<xref target="RFC3629"/>, target="RFC3629" format="default" sectionFormat="of" derivedContent="RFC3629"/>, and all servers and clients MUST <bcp14>MUST</bcp14> support UTF-8.</t>
</section>
<section title="URIs anchor="sect-12.2" numbered="true" toc="include" removeInRFC="false" pn="section-12.2">
<name slugifiedName="name-uris-and-iris">URIs and IRIs" anchor="sect-12.2"><t> IRIs</name>
<t indent="0" pn="section-12.2-1">
<xref target="RFC7480"/> target="RFC7480" format="default" sectionFormat="of" derivedContent="RFC7480"/> defines the use of URIs and IRIs in RDAP.</t>
</section>
<section title="Language Tags" anchor="sect-12.3"><t> anchor="sect-12.3" numbered="true" toc="include" removeInRFC="false" pn="section-12.3">
<name slugifiedName="name-language-tags">Language Tags</name>
<t indent="0" pn="section-12.3-1">
<xref target="sect-4.4"/> target="sect-4.4" format="default" sectionFormat="of" derivedContent="Section 4.4"/> defines the use of language tags in the JSON responses
defined in this document.</t>
</section>
<section title="Internationalized anchor="sect-12.4" numbered="true" toc="include" removeInRFC="false" pn="section-12.4">
<name slugifiedName="name-internationalized-domain-na">Internationalized Domain Names" anchor="sect-12.4"><t> Names</name>
<t indent="0" pn="section-12.4-1">
IDNs are denoted in this specification by the separation of DNS names
in LDH form and Unicode form (see <xref target="sect-3"/>). target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>). Representation of IDNs
in registries is described by the "variants" object in <xref target="sect-5.3"/> target="sect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.3"/>
and the suggested values listed in <xref target="sect-10.2.5"/>.</t> target="sect-10.2.5" format="default" sectionFormat="of" derivedContent="Section 10.2.5"/>.</t>
</section>
</section>
<section title="Privacy Considerations" anchor="sect-13"><t> anchor="sect-13" numbered="true" toc="include" removeInRFC="false" pn="section-13">
<name slugifiedName="name-privacy-considerations">Privacy Considerations</name>
<t indent="0" pn="section-13-1">
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 <xref target="sect-10.2.2"/> target="sect-10.2.2" format="default" sectionFormat="of" derivedContent="Section 10.2.2"/> 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 <bcp14>SHOULD</bcp14> be used to describe data elements of a response
when appropriate:</t>
<t><list hangIndent="3" style="hanging"><t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-13-2">
<li pn="section-13-2.1">
private -- The object is not be shared in query responses, unless
the user is authorized to view this information.</t>
</list>
</t>
<t><list hangIndent="3" style="hanging"><t> information.</li>
<li pn="section-13-2.2">
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.</t>
</list>
</t>
<t><list hangIndent="3" style="hanging"><t> private.</li>
<li pn="section-13-2.3">
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".</t>
</list>
</t>
<t> "removed".</li>
</ul>
<t indent="0" pn="section-13-3">
See Appendix A.1 <xref target="sect-a.1" format="default" sectionFormat="of" derivedContent="Appendix A.1"/> for an example of applying those values to contacts
and registrants.</t>
</section>
</middle>
<back>
<references title="Normative References"> pn="section-14">
<name slugifiedName="name-references">References</name>
<references pn="section-14.1">
<name slugifiedName="name-normative-references">Normative References</name>
<reference anchor="ISO.3166.1988"><front> anchor="ISO.3166.2020" quoteTitle="true" derivedAnchor="ISO.3166.2020">
<front>
<title>Codes for the representation of names of countries, 3rd edition</title>
<author>
<organization>International countries and their subdivisions</title>
<author>
<organization showOnFrontPage="true">International Organization for Standardization</organization>
</author>
<date month="August" year="1988"/> year="2020"/>
</front>
<refcontent>Fourth edition</refcontent>
<seriesInfo name="ISO" value="Standard 3166"/>
</reference>
&RFC2119;
&RFC3339;
&RFC3629;
&RFC3986;
&RFC4034;
&RFC5396;
&RFC5646;
&RFC5890;
&RFC5952;
&RFC7095;
&RFC7480;
&RFC7481;
&RFC8126;
&RFC8174;
&RFC8259;
&RFC8288;
&I-D.ietf-regext-rfc7482bis;
</references>
<references title="Informative References">
<reference anchor="IANA_IDNTABLES" target="https://www.iana.org/domains/idn-tables"><front>
<title>Repository of IDN Practices</title>
<author>
<organization>IANA</organization> anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119" quoteTitle="true" derivedAnchor="RFC2119">
<front>
<title>Key words for use in RFCs to Indicate Requirement Levels</title>
<author initials="S." surname="Bradner" fullname="S. Bradner">
<organization showOnFrontPage="true"/>
</author>
<date/>
<date year="1997" month="March"/>
<abstract>
<t indent="0">In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="2119"/>
<seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="JSON_ascendancy" target="https://devcentral.f5.com/s/articles/the-stealthy-ascendancy-of-json"><front>
<title>The Stealthy Ascendancy of JSON</title> anchor="RFC3339" target="https://www.rfc-editor.org/info/rfc3339" quoteTitle="true" derivedAnchor="RFC3339">
<front>
<title>Date and Time on the Internet: Timestamps</title>
<author fullname="L. MacVittie" initials="L." surname="MacVittie"> initials="G." surname="Klyne" fullname="G. Klyne">
<organization showOnFrontPage="true"/>
</author>
<author initials="C." surname="Newman" fullname="C. Newman">
<organization showOnFrontPage="true"/>
</author>
<date month="April" year="2011"/> year="2002" month="July"/>
<abstract>
<t indent="0">This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="3339"/>
<seriesInfo name="DOI" value="10.17487/RFC3339"/>
</reference>
<reference anchor="JSON_performance_study" target="https://www.cs.montana.edu/izurieta/pubs/caine2009.pdf"><front>
<title>Comparison anchor="RFC3629" target="https://www.rfc-editor.org/info/rfc3629" quoteTitle="true" derivedAnchor="RFC3629">
<front>
<title>UTF-8, a transformation format of JSON and XML Data Interchange Formats: A Case Study</title> ISO 10646</title>
<author fullname="N. Nurseitov" initials="N." surname="Nurseitov"> initials="F." surname="Yergeau" fullname="F. Yergeau">
<organization showOnFrontPage="true"/>
</author>
<date year="2003" month="November"/>
<abstract>
<t indent="0">ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279.</t>
</abstract>
</front>
<seriesInfo name="STD" value="63"/>
<seriesInfo name="RFC" value="3629"/>
<seriesInfo name="DOI" value="10.17487/RFC3629"/>
</reference>
<reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986" quoteTitle="true" derivedAnchor="RFC3986">
<front>
<title>Uniform Resource Identifier (URI): Generic Syntax</title>
<author fullname="M. Paulson" initials="M." surname="Paulson"> initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
<organization showOnFrontPage="true"/>
</author>
<author fullname="R. Reynolds" initials="R." surname="Reynolds"> surname="Fielding" fullname="R. Fielding">
<organization showOnFrontPage="true"/>
</author>
<author fullname="C. Izurieta" initials="C." surname="Izurieta"> initials="L." surname="Masinter" fullname="L. Masinter">
<organization showOnFrontPage="true"/>
</author>
<date year="2009"/> year="2005" month="January"/>
<abstract>
<t indent="0">A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="STD" value="66"/>
<seriesInfo name="RFC" value="3986"/>
<seriesInfo name="DOI" value="10.17487/RFC3986"/>
</reference>
<reference anchor="RFC4034" target="https://www.rfc-editor.org/info/rfc4034" quoteTitle="true" derivedAnchor="RFC4034">
<front>
<title>Resource Records for the DNS Security Extensions</title>
<author initials="R." surname="Arends" fullname="R. Arends">
<organization showOnFrontPage="true"/>
</author>
<author initials="R." surname="Austein" fullname="R. Austein">
<organization showOnFrontPage="true"/>
</author>
<author initials="M." surname="Larson" fullname="M. Larson">
<organization showOnFrontPage="true"/>
</author>
<author initials="D." surname="Massey" fullname="D. Massey">
<organization showOnFrontPage="true"/>
</author>
<author initials="S." surname="Rose" fullname="S. Rose">
<organization showOnFrontPage="true"/>
</author>
<date year="2005" month="March"/>
<abstract>
<t indent="0">This document is part of a family of documents that describe the DNS Security Extensions (DNSSEC). The DNS Security Extensions are a collection of resource records and protocol modifications that provide source authentication for the DNS. This document defines the public key (DNSKEY), delegation signer (DS), resource record digital signature (RRSIG), and authenticated denial of existence (NSEC) resource records. The purpose and format of each resource record is described in detail, and an example of each resource record is given. </t>
<t indent="0"> This document obsoletes RFC 2535 and incorporates changes from all updates to RFC 2535. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="4034"/>
<seriesInfo name="DOI" value="10.17487/RFC4034"/>
</reference>
<reference anchor="RFC5396" target="https://www.rfc-editor.org/info/rfc5396" quoteTitle="true" derivedAnchor="RFC5396">
<front>
<title>Textual Representation of Autonomous System (AS) Numbers</title>
<author initials="G." surname="Huston" fullname="G. Huston">
<organization showOnFrontPage="true"/>
</author>
<author initials="G." surname="Michaelson" fullname="G. Michaelson">
<organization showOnFrontPage="true"/>
</author>
<date year="2008" month="December"/>
<abstract>
<t indent="0">A textual representation for Autonomous System (AS) numbers is defined as the decimal value of the AS number. This textual representation is to be used by all documents, systems, and user interfaces referring to AS numbers. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5396"/>
<seriesInfo name="DOI" value="10.17487/RFC5396"/>
</reference>
<reference anchor="RFC5646" target="https://www.rfc-editor.org/info/rfc5646" quoteTitle="true" derivedAnchor="RFC5646">
<front>
<title>Tags for Identifying Languages</title>
<author initials="A." surname="Phillips" fullname="A. Phillips" role="editor">
<organization showOnFrontPage="true"/>
</author>
<author initials="M." surname="Davis" fullname="M. Davis" role="editor">
<organization showOnFrontPage="true"/>
</author>
<date year="2009" month="September"/>
<abstract>
<t indent="0">This document describes the structure, content, construction, and semantics of language tags for use in cases where it is desirable to indicate the language used in an information object. It also describes how to register values for use in language tags and the creation of user-defined extensions for private interchange. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="47"/>
<seriesInfo name="RFC" value="5646"/>
<seriesInfo name="DOI" value="10.17487/RFC5646"/>
</reference>
<reference anchor="RFC5890" target="https://www.rfc-editor.org/info/rfc5890" quoteTitle="true" derivedAnchor="RFC5890">
<front>
<title>Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework</title>
<author initials="J." surname="Klensin" fullname="J. Klensin">
<organization showOnFrontPage="true"/>
</author>
<date year="2010" month="August"/>
<abstract>
<t indent="0">This document is one of a collection that, together, describe the protocol and usage context for a revision of Internationalized Domain Names for Applications (IDNA), superseding the earlier version. It describes the document collection and provides definitions and other material that are common to the set. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5890"/>
<seriesInfo name="DOI" value="10.17487/RFC5890"/>
</reference>
<reference anchor="RFC5952" target="https://www.rfc-editor.org/info/rfc5952" quoteTitle="true" derivedAnchor="RFC5952">
<front>
<title>A Recommendation for IPv6 Address Text Representation</title>
<author initials="S." surname="Kawamura" fullname="S. Kawamura">
<organization showOnFrontPage="true"/>
</author>
<author initials="M." surname="Kawashima" fullname="M. Kawashima">
<organization showOnFrontPage="true"/>
</author>
<date year="2010" month="August"/>
<abstract>
<t indent="0">As IPv6 deployment increases, there will be a dramatic increase in the need to use IPv6 addresses in text. While the IPv6 address architecture in Section 2.2 of RFC 4291 describes a flexible model for text representation of an IPv6 address, this flexibility has been causing problems for operators, system engineers, and users. This document defines a canonical textual representation format. It does not define a format for internal storage, such as within an application or database. It is expected that the canonical format will be followed by humans and systems when representing IPv6 addresses as text, but all implementations must accept and be able to handle any legitimate RFC 4291 format. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5952"/>
<seriesInfo name="DOI" value="10.17487/RFC5952"/>
</reference>
<reference anchor="RFC7095" target="https://www.rfc-editor.org/info/rfc7095" quoteTitle="true" derivedAnchor="RFC7095">
<front>
<title>jCard: The JSON Format for vCard</title>
<author initials="P." surname="Kewisch" fullname="P. Kewisch">
<organization showOnFrontPage="true"/>
</author>
<date year="2014" month="January"/>
<abstract>
<t indent="0">This specification defines "jCard", a JSON format for vCard data. The vCard data format is a text format for representing and exchanging information about individuals and other entities, for example, telephone numbers, email addresses, structured names, and delivery addresses. JSON is a lightweight, text-based, language- independent data interchange format commonly used in Internet applications.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="7095"/>
<seriesInfo name="DOI" value="10.17487/RFC7095"/>
</reference>
<reference anchor="RFC7480" target="https://www.rfc-editor.org/info/rfc7480" quoteTitle="true" derivedAnchor="RFC7480">
<front>
<title>HTTP Usage in the Registration Data Access Protocol (RDAP)</title>
<author initials="A." surname="Newton" fullname="A. Newton">
<organization showOnFrontPage="true"/>
</author>
<author initials="B." surname="Ellacott" fullname="B. Ellacott">
<organization showOnFrontPage="true"/>
</author>
<author initials="N." surname="Kong" fullname="N. Kong">
<organization showOnFrontPage="true"/>
</author>
<date year="2015" month="March"/>
<abstract>
<t indent="0">This document is one of a collection that together describes the Registration Data Access Protocol (RDAP). It describes how RDAP is transported using the Hypertext Transfer Protocol (HTTP). RDAP is a successor protocol to the very old WHOIS protocol. The purpose of this document is to clarify the use of standard HTTP mechanisms for this application.</t>
</abstract>
</front>
<seriesInfo name="STD" value="95"/>
<seriesInfo name="RFC" value="7480"/>
<seriesInfo name="DOI" value="10.17487/RFC7480"/>
</reference>
<reference anchor="RFC7481" target="https://www.rfc-editor.org/info/rfc7481" quoteTitle="true" derivedAnchor="RFC7481">
<front>
<title>Security Services for the Registration Data Access Protocol (RDAP)</title>
<author initials="S." surname="Hollenbeck" fullname="S. Hollenbeck">
<organization showOnFrontPage="true"/>
</author>
<author initials="N." surname="Kong" fullname="N. Kong">
<organization showOnFrontPage="true"/>
</author>
<date year="2015" month="March"/>
<abstract>
<t indent="0">The Registration Data Access Protocol (RDAP) provides "RESTful" web services to retrieve registration metadata from Domain Name and Regional Internet Registries. This document describes information security services, including access control, authentication, authorization, availability, data confidentiality, and data integrity for RDAP.</t>
</abstract>
</front>
<seriesInfo name="STD" value="95"/>
<seriesInfo name="RFC" value="7481"/>
<seriesInfo name="DOI" value="10.17487/RFC7481"/>
</reference>
<reference anchor="RFC8126" target="https://www.rfc-editor.org/info/rfc8126" quoteTitle="true" derivedAnchor="RFC8126">
<front>
<title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
<author initials="M." surname="Cotton" fullname="M. Cotton">
<organization showOnFrontPage="true"/>
</author>
<author initials="B." surname="Leiba" fullname="B. Leiba">
<organization showOnFrontPage="true"/>
</author>
<author initials="T." surname="Narten" fullname="T. Narten">
<organization showOnFrontPage="true"/>
</author>
<date year="2017" month="June"/>
<abstract>
<t indent="0">Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA).</t>
<t indent="0">To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry.</t>
<t indent="0">This is the third edition of this document; it obsoletes RFC 5226.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="26"/>
<seriesInfo name="RFC" value="8126"/>
<seriesInfo name="DOI" value="10.17487/RFC8126"/>
</reference>
<reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174" quoteTitle="true" derivedAnchor="RFC8174">
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
<author initials="B." surname="Leiba" fullname="B. Leiba">
<organization showOnFrontPage="true"/>
</author>
<date year="2017" month="May"/>
<abstract>
<t indent="0">RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
</abstract>
</front>
<seriesInfo name="BCP" value="14"/>
<seriesInfo name="RFC" value="8174"/>
<seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>
<reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259" quoteTitle="true" derivedAnchor="RFC8259">
<front>
<title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
<author initials="T." surname="Bray" fullname="T. Bray" role="editor">
<organization showOnFrontPage="true"/>
</author>
<date year="2017" month="December"/>
<abstract>
<t indent="0">JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data.</t>
<t indent="0">This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.</t>
</abstract>
</front>
<seriesInfo name="STD" value="90"/>
<seriesInfo name="RFC" value="8259"/>
<seriesInfo name="DOI" value="10.17487/RFC8259"/>
</reference>
<reference anchor="RFC8288" target="https://www.rfc-editor.org/info/rfc8288" quoteTitle="true" derivedAnchor="RFC8288">
<front>
<title>Web Linking</title>
<author initials="M." surname="Nottingham" fullname="M. Nottingham">
<organization showOnFrontPage="true"/>
</author>
<date year="2017" month="October"/>
<abstract>
<t indent="0">This specification defines a model for the relationships between resources on the Web ("links") and the type of those relationships ("link relation types").</t>
<t indent="0">It also defines the serialisation of such links in HTTP headers with the Link header field.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="8288"/>
<seriesInfo name="DOI" value="10.17487/RFC8288"/>
</reference>
<reference anchor="RFC9082" target="https://www.rfc-editor.org/info/rfc9082" quoteTitle="true" derivedAnchor="RFC9082">
<front>
<title>Registration Data Access Protocol (RDAP) Query Format</title>
<author initials="S" surname="Hollenbeck" fullname="Scott Hollenbeck">
<organization showOnFrontPage="true"/>
</author>
<author initials="A" surname="Newton" fullname="Andrew Newton">
<organization showOnFrontPage="true"/>
</author>
<date month="June" year="2021"/>
</front>
<seriesInfo name="STD" value="95"/>
<seriesInfo name="RFC" value="9082"/>
<seriesInfo name="DOI" value="10.17487/RFC9082"/>
</reference>
</references>
<references pn="section-14.2">
<name slugifiedName="name-informative-references">Informative References</name>
<reference anchor="IANA_IDNTABLES" target="https://www.iana.org/domains/idn-tables" quoteTitle="true" derivedAnchor="IANA_IDNTABLES">
<front>
<title>Repository of IDN Practices</title>
<author>
<organization showOnFrontPage="true">IANA</organization>
</author>
<date/>
</front>
</reference>
<reference anchor="JSON_ascendancy" target="https://devcentral.f5.com/s/articles/the-stealthy-ascendancy-of-json" quoteTitle="true" derivedAnchor="JSON_ascendancy">
<front>
<title>The Stealthy Ascendancy of JSON</title>
<author fullname="L. MacVittie" initials="L." surname="MacVittie">
</author>
<date month="April" year="2011"/>
</front>
</reference>
<reference anchor="JSON_performance_study" target="https://www.cs.montana.edu/izurieta/pubs/caine2009.pdf" quoteTitle="true" derivedAnchor="JSON_performance_study">
<front>
<title>Comparison of JSON and XML Data Interchange Formats: A Case Study</title>
<author fullname="N. Nurseitov" initials="N." surname="Nurseitov">
</author>
<author fullname="M. Paulson" initials="M." surname="Paulson">
</author>
<author fullname="R. Reynolds" initials="R." surname="Reynolds">
</author>
<author fullname="C. Izurieta" initials="C." surname="Izurieta">
</author>
<date year="2009"/>
</front>
</reference>
<reference anchor="RFC3912" target="https://www.rfc-editor.org/info/rfc3912" quoteTitle="true" derivedAnchor="RFC3912">
<front>
<title>WHOIS Protocol Specification</title>
<author initials="L." surname="Daigle" fullname="L. Daigle">
<organization showOnFrontPage="true"/>
</author>
<date year="2004" month="September"/>
<abstract>
<t indent="0">This document updates the specification of the WHOIS protocol, thereby obsoleting RFC 954. The update is intended to remove the material from RFC 954 that does not have to do with the on-the-wire protocol, and is no longer applicable in today's Internet. This document does not attempt to change or update the protocol per se, or document other uses of the protocol that have come into existence since the publication of RFC 954. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="3912"/>
<seriesInfo name="DOI" value="10.17487/RFC3912"/>
</reference>
<reference anchor="RFC5730" target="https://www.rfc-editor.org/info/rfc5730" quoteTitle="true" derivedAnchor="RFC5730">
<front>
<title>Extensible Provisioning Protocol (EPP)</title>
<author initials="S." surname="Hollenbeck" fullname="S. Hollenbeck">
<organization showOnFrontPage="true"/>
</author>
<date year="2009" month="August"/>
<abstract>
<t indent="0">This document describes an application-layer client-server protocol for the provisioning and management of objects stored in a shared central repository. Specified in XML, the protocol defines generic object management operations and an extensible framework that maps protocol operations to objects. This document includes a protocol specification, an object mapping template, and an XML media type registration. This document obsoletes RFC 4930. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="STD" value="69"/>
<seriesInfo name="RFC" value="5730"/>
<seriesInfo name="DOI" value="10.17487/RFC5730"/>
</reference>
<reference anchor="RFC5910" target="https://www.rfc-editor.org/info/rfc5910" quoteTitle="true" derivedAnchor="RFC5910">
<front>
<title>Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)</title>
<author initials="J." surname="Gould" fullname="J. Gould">
<organization showOnFrontPage="true"/>
</author>
<author initials="S." surname="Hollenbeck" fullname="S. Hollenbeck">
<organization showOnFrontPage="true"/>
</author>
<date year="2010" month="May"/>
<abstract>
<t indent="0">This document describes an Extensible Provisioning Protocol (EPP) extension mapping for the provisioning and management of Domain Name System security (DNSSEC) extensions for domain names stored in a shared central repository. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for the provisioning of DNS security extensions. This document obsoletes RFC 4310. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="5910"/>
<seriesInfo name="DOI" value="10.17487/RFC5910"/>
</reference>
<reference anchor="RFC6350" target="https://www.rfc-editor.org/info/rfc6350" quoteTitle="true" derivedAnchor="RFC6350">
<front>
<title>vCard Format Specification</title>
<author initials="S." surname="Perreault" fullname="S. Perreault">
<organization showOnFrontPage="true"/>
</author>
<date year="2011" month="August"/>
<abstract>
<t indent="0">This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739. [STANDARDS-TRACK]</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6350"/>
<seriesInfo name="DOI" value="10.17487/RFC6350"/>
</reference>
<reference anchor="RFC6839" target="https://www.rfc-editor.org/info/rfc6839" quoteTitle="true" derivedAnchor="RFC6839">
<front>
<title>Additional Media Type Structured Syntax Suffixes</title>
<author initials="T." surname="Hansen" fullname="T. Hansen">
<organization showOnFrontPage="true"/>
</author>
<author initials="A." surname="Melnikov" fullname="A. Melnikov">
<organization showOnFrontPage="true"/>
</author>
<date year="2013" month="January"/>
<abstract>
<t indent="0">A content media type name sometimes includes partitioned meta- information distinguished by a structured syntax to permit noting an attribute of the media as a suffix to the name. This document defines several structured syntax suffixes for use with media type registrations. In particular, it defines and registers the "+json", "+ber", "+der", "+fastinfoset", "+wbxml" and "+zip" structured syntax suffixes, and provides a media type structured syntax suffix registration form for the "+xml" structured syntax suffix. This document is not an Internet Standards Track specification; it is published for informational purposes.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6839"/>
<seriesInfo name="DOI" value="10.17487/RFC6839"/>
</reference>
&RFC3912;
&RFC5730;
&RFC5910;
&RFC6350;
&RFC6839;
&RFC7942;
</references>
</references>
<section title="Suggested anchor="sect-a" numbered="true" toc="include" removeInRFC="false" pn="section-appendix.a">
<name slugifiedName="name-suggested-data-modeling-wit">Suggested Data Modeling with the Entity Object Class" anchor="sect-a"><section title="Registrants Class</name>
<section anchor="sect-a.1" numbered="true" toc="include" removeInRFC="false" pn="section-a.1">
<name slugifiedName="name-registrants-and-contacts">Registrants and Contacts" anchor="sect-a.1"><t> Contacts</name>
<t indent="0" pn="section-a.1-1">
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 <xref target="sect-10.2.4"/> target="sect-10.2.4" format="default" sectionFormat="of" derivedContent="Section 10.2.4"/>
be used.</t>
<t>
<t indent="0" pn="section-a.1-2">
The following is an example of an elided containing object with an
embedded entity that is both a registrant and administrative contact:</t>
<figure anchor="ure-34"><artwork><![CDATA[ anchor="ure-34" align="left" suppress-title="false" pn="figure-34">
<sourcecode type="json" markers="false" pn="section-a.1-3.1">
{
...
"entities" :
[
{
"objectClassName" : "entity",
"handle" : "XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["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"
]
],
["tel",
{ "type":["work", "voice"], "pref":"1" },
"uri", "tel:+1-555-555-1234;ext=102"
],
["email",
{ "type":"work" },
"text", "joe.user@example.com"
]
]
],
"roles" : [ "registrant", "administrative" ],
"remarks" :
[
{
"description" :
[
"She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan."
]
}
],
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
},
{
"eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-a.1-4">
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 <xref target="sect-10.2.2"/>).</t>
<t> target="sect-10.2.2" format="default" sectionFormat="of" derivedContent="Section 10.2.2"/>).</t>
<t indent="0" pn="section-a.1-5">
The following is an elided example of a registrant with information
changed to reflect that of a third party.</t>
<figure anchor="ure-35"><artwork><![CDATA[ anchor="ure-35" align="left" suppress-title="false" pn="figure-35">
<sourcecode type="json" markers="false" pn="section-a.1-6.1">
{
...
"entities" :
[
{
"objectClassName" : "entity",
"handle" : "XXXX",
...
"roles" : [ "registrant", "administrative" ],
"status" : [ "proxy", "private", "obscured" ]
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Registrars" anchor="sect-a.2"><t> anchor="sect-a.2" numbered="true" toc="include" removeInRFC="false" pn="section-a.2">
<name slugifiedName="name-registrars">Registrars</name>
<t indent="0" pn="section-a.2-1">
This document does not provide a specific object class for
registrars, but like registrants and contacts (see Appendix A.1), <xref target="sect-a.1" format="default" sectionFormat="of" derivedContent="Appendix A.1"/>), the
"roles" string array maybe used. Additionally, many registrars have
publicly assigned identifiers. The publicIds structure (<xref target="sect-4.8"/>) target="sect-4.8" format="default" sectionFormat="of" derivedContent="Section 4.8"/>)
represents that information.</t>
<t>
<t indent="0" pn="section-a.2-2">
The following is an example of an elided containing object with an
embedded entity that is a registrar:</t>
<figure anchor="ure-36"><artwork><![CDATA[ anchor="ure-36" align="left" suppress-title="false" pn="figure-36">
<sourcecode type="json" markers="false" pn="section-a.2-3.1">
{
...
"entities":[
{
"objectClassName" : "entity",
"handle":"XXXX",
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe's Fish, Chips, and Domains"],
["kind", {}, "text", "org"],
["lang", {
"pref":"1"
}, "language-tag", "fr"],
["lang", {
"pref":"2"
}, "language-tag", "en"],
["org", {
"type":"work"
}, "text", "Example"],
["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", "joes_fish_chips_and_domains@example.com"
]
]
],
"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":"https://example.net/entity/XXXX",
"rel":"alternate",
"type":"text/html",
"href":"https://www.example.com"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
</section>
<section title="Modeling Events" anchor="sect-b"><t> anchor="sect-b" numbered="true" toc="include" removeInRFC="false" pn="section-appendix.b">
<name slugifiedName="name-modeling-events">Modeling Events</name>
<t indent="0" pn="section-appendix.b-1">
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.</t>
<t>
<t indent="0" pn="section-appendix.b-2">
Events can be modeled in three ways:</t>
<t><list style="numbers"><t>events
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-appendix.b-3"><li pn="section-appendix.b-3.1" derivedCounter="1.">events with no designated actor</t>
<t>events actor</li>
<li pn="section-appendix.b-3.2" derivedCounter="2.">events where the actor is only designated by an identifier</t>
<t>events identifier</li>
<li pn="section-appendix.b-3.3" derivedCounter="3.">events where the actor can be modeled as an entity</t>
</list>
</t>
<t> entity</li>
</ol>
<t indent="0" pn="section-appendix.b-4">
For the first use case, the events data structure (<xref target="sect-4.5"/>) target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>) is
used without the "eventActor" object member.</t>
<t>
<t indent="0" pn="section-appendix.b-5">
This is an example of an "events" array without the "eventActor".</t>
<figure anchor="ure-37"><artwork><![CDATA[ anchor="ure-37" align="left" suppress-title="false" pn="figure-37">
<sourcecode type="json" markers="false" pn="section-appendix.b-6.1">
"events" :
[
{
"eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z"
}
]
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-appendix.b-7">
For the second use case, the events data structure (<xref target="sect-4.5"/>) target="sect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>) is
used with the "eventActor" object member.</t>
<t>
<t indent="0" pn="section-appendix.b-8">
This is an example of an "events" array with the "eventActor".</t>
<figure anchor="ure-38"><artwork><![CDATA[ anchor="ure-38" align="left" suppress-title="false" pn="figure-38">
<sourcecode type="json" markers="false" pn="section-appendix.b-9.1">
"events" :
[
{
"eventAction" : "registration",
"eventActor" : "XYZ-NIC",
"eventDate" : "1990-12-31T23:59:59Z"
}
]
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-appendix.b-10">
For the third use case, the "asEventActor" array is used when an
entity (<xref target="sect-5.1"/>) target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>) is embedded into another object class. The
"asEventActor" array follows the same structure as the "events" array
but does not have "eventActor" attributes.</t>
<t>
<t indent="0" pn="section-appendix.b-11">
The following is an elided example of a domain object with an entity
as an event actor.</t>
<figure anchor="ure-39"><artwork><![CDATA[ anchor="ure-39" align="left" suppress-title="false" pn="figure-39">
<sourcecode type="json" markers="false" pn="section-appendix.b-12.1">
{
"objectClassName" : "domain",
"handle" : "XXXX",
"ldhName" : "foo.example",
"status" : [ "locked", "transfer prohibited" ],
...
"entities" :
[
{
"handle" : "XXXX",
...
"asEventActor" :
[
{
"eventAction" : "last changed",
"eventDate" : "1990-12-31T23:59:59Z"
}
]
}
]
}
]]></artwork>
</sourcecode>
</figure>
</section>
<section title="Structured anchor="sect-c" numbered="true" toc="include" removeInRFC="false" pn="section-appendix.c">
<name slugifiedName="name-structured-vs-unstructured-">Structured vs. Unstructured Addresses" anchor="sect-c"><t> Addresses</name>
<t indent="0" pn="section-appendix.c-1">
The entity (<xref target="sect-5.1"/>) target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>) object class uses jCard <xref target="RFC7095"/> target="RFC7095" format="default" sectionFormat="of" derivedContent="RFC7095"/> 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.</t>
<t>
<t indent="0" pn="section-appendix.c-2">
The following is an example of a jCard.</t>
<figure anchor="ure-40"><artwork><![CDATA[ anchor="ure-40" align="left" suppress-title="false" pn="figure-40">
<sourcecode type="json" markers="false" pn="section-appendix.c-3.1">
{
"vcardArray":[
"vcard",
[
["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"],
["n", {}, "text",
["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
],
["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", "https://www.example.com/joe.user/joe.asc"
],
["tz", {},
"utc-offset", "-05:00"],
["url", { "type":"home" },
"uri", "https://example.org"]
]
]
}
]]></artwork>
</sourcecode>
</figure>
<t>
<t indent="0" pn="section-appendix.c-4">
The arrays in Figure 40 <xref target="ure-40" format="default" sectionFormat="of" derivedContent="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 <xref target="RFC6350"/>. target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350"/>. In this example, the
following data corresponds to the following positional meanings:</t>
<t><list style="numbers"><t>post
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-appendix.c-5"><li pn="section-appendix.c-5.1" derivedCounter="1.">post office box -- not applicable; empty string</t>
<t>extended string</li>
<li pn="section-appendix.c-5.2" derivedCounter="2.">extended address (e.g., apartment or suite number) -- Suite 1234</t>
<t>street 1234</li>
<li pn="section-appendix.c-5.3" derivedCounter="3.">street address -- 4321 Rue Somewhere</t>
<t>locality Somewhere</li>
<li pn="section-appendix.c-5.4" derivedCounter="4.">locality (e.g., city) -- Quebec</t>
<t>region Quebec</li>
<li pn="section-appendix.c-5.5" derivedCounter="5.">region (e.g., state or province) -- QC</t>
<t>postal QC</li>
<li pn="section-appendix.c-5.6" derivedCounter="6.">postal code -- G1V 2M2</t>
<t>country 2M2</li>
<li pn="section-appendix.c-5.7" derivedCounter="7.">country name (full name) -- Canada</t>
</list>
</t>
<t> Canada</li>
</ol>
<t indent="0" pn="section-appendix.c-6">
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.</t>
</section>
<section title="Secure DNS" anchor="sect-d"><t> anchor="sect-d" numbered="true" toc="include" removeInRFC="false" pn="section-appendix.d">
<name slugifiedName="name-secure-dns">Secure DNS</name>
<t indent="0" pn="section-appendix.d-1">
<xref target="sect-5.3"/> target="sect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.3"/> defines the "secureDNS" member to represent secure DNS
information about domain names.</t>
<t>
<t indent="0" pn="section-appendix.d-2">
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 "<xref target="RFC4034" format="title" sectionFormat="of" derivedContent="Resource Records for the DNS Security Extensions" Extensions"/>" <xref target="RFC4034"/>. target="RFC4034" format="default" sectionFormat="of" derivedContent="RFC4034"/>. Creating the DS
records in the parent zone can be done by the registration authority
"Domain
"<xref target="RFC5910" format="title" sectionFormat="of" derivedContent="Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)" (EPP)"/>" <xref target="RFC5910"/>.</t>
<t> target="RFC5910" format="default" sectionFormat="of" derivedContent="RFC5910"/>.</t>
<t indent="0" pn="section-appendix.d-3">
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.</t>
<t>
<t indent="0" pn="section-appendix.d-4">
The domain object class (<xref target="sect-5.3"/>) target="sect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.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.</t>
</section>
<section title="Motivations anchor="sect-e" numbered="true" toc="include" removeInRFC="false" pn="section-appendix.e">
<name slugifiedName="name-motivations-for-using-json">Motivations for Using JSON" anchor="sect-e"><t> JSON</name>
<t indent="0" pn="section-appendix.e-1">
This section addresses a common question regarding the use of JSON
over other data formats, most notably XML.</t>
<t>
<t indent="0" pn="section-appendix.e-2">
It is often pointed out that many DNRs and one RIR support the EPP
<xref target="RFC5730"/> target="RFC5730" format="default" sectionFormat="of" derivedContent="RFC5730"/> 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.</t>
<t>
<t indent="0" pn="section-appendix.e-3">
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.</t>
<t>
<t indent="0" pn="section-appendix.e-4">
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.</t>
<t>
<t indent="0" pn="section-appendix.e-5">
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 <xref target="JSON_ascendancy"/>). target="JSON_ascendancy" format="default" sectionFormat="of" derivedContent="JSON_ascendancy"/>). Studies
have also found that JSON is generally less bulky and consequently
faster to parse (see <xref target="JSON_performance_study"/>).</t>
</section>
<section title="Acknowledgments" numbered="no" anchor="acknowledgments"><t>
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.</t>
<t>
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.</t>
<t>
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.</t>
<t>
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.</t>
<t>
The switch to and incorporation of jCard was performed by Simon
Perreault.</t>
<t>
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.</t> target="JSON_performance_study" format="default" sectionFormat="of" derivedContent="JSON_performance_study"/>).</t>
</section>
<section title="Changes from RFC 7483" numbered="no"><t>
<list style="hanging">
<t hangText="00:">Initial version ported numbered="true" toc="include" removeInRFC="false" pn="section-appendix.f">
<name slugifiedName="name-changes-from-rfc-7483">Changes from RFC 7483. Addressed 7483</name>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-appendix.f-1">
<li pn="section-appendix.f-1.1">Addressed known errata. Added Implementation Status section.</t>
<t hangText="01:">Updated errata.</li>
<li pn="section-appendix.f-1.2">Updated references to 7482 to 7482bis Internet-Draft. Updated "Change Log" to "Changes from RFC 7483". Added APNIC implementation status. 9082.
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. <xref target="sect-4.1" format="default" sectionFormat="of" derivedContent="Section 4.1"/>.
Changed "lunarNic_level_0" to "lunarNIC_level_0". Clarified "lunarNIC_level_0".</li>
<li pn="section-appendix.f-1.3">Clarified that the "value", "rel" and "href" JSON values MUST <bcp14>MUST</bcp14> be specified in the "links" array. Clarified </li>
<li pn="section-appendix.f-1.4">Clarified that the "description" array is required in the Notices and Remarks data structures and other values are OPTIONAL. Noted <bcp14>OPTIONAL</bcp14>.</li>
<li pn="section-appendix.f-1.5">Noted that all members of the "events" and "Public IDs" arrays are REQUIRED. Fix <bcp14>REQUIRED</bcp14>. </li>
<li pn="section-appendix.f-1.6">Fix "self" link values in examples. Changed "http" to "https" link values in examples.
Noted that Figure 18 <xref target="ure-18" format="default" sectionFormat="of" derivedContent="Figure 18"/> is an example of a nameserver object with all "appropriate" values given.
In appendix C, <xref target="sect-c" format="default" sectionFormat="of" derivedContent="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 </li>
<li pn="section-appendix.f-1.7">Clarified <bcp14>REQUIRED</bcp14> and OPTIONAL <bcp14>OPTIONAL</bcp14> members of the "events" array. Changed "SHOULD array.</li>
<li pn="section-appendix.f-1.8">Changed "<bcp14>SHOULD</bcp14> not" to "SHOULD NOT" in <xref target="sect-5"/>. Updated normative references (5226-8126, 5988-8288, 7159-8259). "<bcp14>SHOULD NOT</bcp14>" in <xref target="sect-5" format="default" sectionFormat="of" derivedContent="Section 5"/>. </li>
<li pn="section-appendix.f-1.9">Updated normative references (RFC 5226 to RFC 8126, RFC 5988 to RFC 8288, RFC 7159 to RFC 8259).
Changed examples using "ns1.xn--fo-5ja.example" to split URLs to avoid long lines.</t>
<t hangText="00:">Initial working group version. Added acknowledgments.</t>
<t hangText="01:">Changed lines.</li>
<li pn="section-appendix.f-1.10">Added acknowledgments.</li>
<li pn="section-appendix.f-1.11">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 <bcp14>MAY</bcp14> 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 <xref target="RFC6350" section="5.1" sectionFormat="bare" format="default" derivedLink="https://rfc-editor.org/rfc/rfc6350#section-5.1" derivedContent="RFC6350"/> of RFC 6350 [RFC6350]". Changed <xref target="RFC6350" format="default" sectionFormat="of" derivedContent="RFC6350"/>". </li>
<li pn="section-appendix.f-1.12">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 policies".</li>
<li pn="section-appendix.f-1.13">Changed "This data structure appears only in the topmost JSON object of a response" to "This data structure MUST <bcp14>MUST</bcp14> appear in the topmost JSON object of a response". Changed </li>
<li pn="section-appendix.f-1.14">Changed "Some non-answer responses may return entity bodies with information that could be more descriptive" to "Some non-answer responses MAY <bcp14>MAY</bcp14> return entity bodies with information that could be more descriptive". Changed descriptive".</li>
<li pn="section-appendix.f-1.15">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 <bcp14>REQUIRED</bcp14> error code number (corresponding to the HTTP response code) followed by an OPTIONAL <bcp14>OPTIONAL</bcp14> string named "title" and an OPTIONAL <bcp14>OPTIONAL</bcp14> array of strings named "description"". Changed "description"".</li>
<li pn="section-appendix.f-1.16">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 Autonomous System number registration". Changed "registry unique" to "registry-unique".</t>
<t hangText="02:">Changed "registry-unique".</li>
<li pn="section-appendix.f-1.17">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 </li>
<li pn="section-appendix.f-1.18">Added text to <xref target="sect-4.2"/> target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/> to note that "self" and "related" "href" URIs MUST NOT <bcp14>MUST NOT</bcp14> be the same. Added </li>
<li pn="section-appendix.f-1.19">Added text to <xref target="sect-4.2"/> target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/> to describe return of IDNs in LDH name format.</t>
<t hangText="03:">Added format.</li>
<li pn="section-appendix.f-1.20">Added text to note that the "fn" member of a contact object MAY <bcp14>MAY</bcp14> be empty in <xref target="sect-3"/>.</t>
<t hangText="04:">Added target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>.</li>
<li pn="section-appendix.f-1.21">Added text to clarify rdapConformance requirements in <xref target="sect-4.1"/>.</t>
<t hangText="05:">Added target="sect-4.1" format="default" sectionFormat="of" derivedContent="Section 4.1"/>.</li>
<li pn="section-appendix.f-1.22">Added "obsoletes 7483" to the headers, Abstract, and Introduction. Updated BCP14 template. BCP 14 boilerplate. Updated IANA Considerations to note that this new RFC (a product of the REGEXT working group) Working Group) replaces RFC 7483. Changed "simple string" to "simple character string" in Sections 3 <xref target="sect-3" format="counter" sectionFormat="of" derivedContent="3"/> and 4.7. <xref target="sect-4.7" format="counter" sectionFormat="of" derivedContent="4.7"/>. Clarified requirement for the "fn" member in Section 3. <xref target="sect-3" format="default" sectionFormat="of" derivedContent="Section 3"/>. Modified the requirement for rdapConformance placement in Section 4.1. <xref target="sect-4.1" format="default" sectionFormat="of" derivedContent="Section 4.1"/>. Changed "jCard" to "vCard" LANGUAGE property reference in Section 4.4. <xref target="sect-4.4" format="default" sectionFormat="of" derivedContent="Section 4.4"/>. Changed "no use" to "little or no use" in Section 5.1. <xref target="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"/>. Added example line wrap note in Section 5.2. <xref target="sect-5.2" format="default" sectionFormat="of" derivedContent="Section 5.2"/>. Modified the definition of "idnTable" in Section 5.3. <xref target="sect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.3"/>. Modified the dsData and keyData examples in Section 5.3. <xref target="sect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.3"/>. Changed "2001:c00::/23" to "2001:db8::/32" in Section 5.4. <xref target="sect-5.4" format="default" sectionFormat="of" derivedContent="Section 5.4"/>. Expanded the definition of "type" in Sections 5.4 <xref target="sect-5.4" format="counter" sectionFormat="of" derivedContent="5.4"/> and 5.5. <xref target="sect-5.5" format="counter" sectionFormat="of" derivedContent="5.5"/>. Modified example autnums in Section 5.5. <xref target="sect-5.5" format="default" sectionFormat="of" derivedContent="Section 5.5"/>. Added text to the Security Considerations section to note that DNSSEC information returned in a response can not cannot be trusted directly.</t>
</list>
</t> directly.</li>
</ul>
</section>
<section numbered="false" anchor="acknowledgments" toc="include" removeInRFC="false" pn="section-appendix.g">
<name slugifiedName="name-acknowledgments">Acknowledgments</name>
<t indent="0" pn="section-appendix.g-1">
This document is derived from original work on RIR responses in JSON
by <contact fullname="Byron J. Ellacott"/>, <contact fullname="Arturo L. Servin"/>,
<contact fullname="Kaveh Ranjbar"/>, and <contact fullname="Andrew L. Newton"/>.
Additionally, this document incorporates work on DNR
responses in JSON by <contact fullname="Ning Kong"/>, <contact fullname="Linlin Zhou"/>, <contact fullname="Jiagui Xie"/>, and
<contact fullname="Sean Shen"/>.</t>
<t indent="0" pn="section-appendix.g-2">
The components of the DNR object classes are derived from a
categorization of WHOIS response formats created by <contact fullname="Ning Kong"/>, <contact fullname="Linlin Zhou"/>,
<contact fullname="Guangqing Deng"/>, <contact fullname="Steve Sheng"/>, <contact fullname="Francisco Arias"/>,
<contact fullname="Ray Bellis"/>, and
<contact fullname="Frederico Neves"/>.</t>
<t indent="0" pn="section-appendix.g-3">
<contact fullname="Tom Harrison"/>, <contact fullname="Murray Kucherawy"/>, <contact fullname="Ed Lewis"/>, <contact fullname="Audric Schiltknecht"/>,
<contact fullname="Naoki Kambe"/>, <contact fullname="Maarten Bosteels"/>, <contact fullname="Mario Loffredo"/>, and <contact fullname="Jasdip Singh"/> contributed significant review comments
and provided clarifying text. <contact fullname="James Mitchell"/> provided text regarding
the processing of unknown JSON attributes and identified issues
leading to the remodeling of events. <contact fullname="Ernie Dainow"/> and
<contact fullname="Francisco Obispo"/> provided concrete suggestions that led to a better variant
model for domain names.</t>
<t indent="0" pn="section-appendix.g-4">
<contact fullname="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.</t>
<t indent="0" pn="section-appendix.g-5">
The switch to and incorporation of jCard was performed by <contact fullname="Simon Perreault"/>.</t>
<t indent="0" pn="section-appendix.g-6">
<contact fullname="Olaf Kolkman"/> and <contact fullname="Murray Kucherawy"/> chaired the IETF's WEIRDS Working
Group from which this document was originally created. <contact fullname="James Galvin"/>
and <contact fullname="Antoin Verschuren"/> chaired the REGEXT Working Group that worked
on this document.</t>
</section>
<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc="include" pn="section-appendix.h">
<name slugifiedName="name-authors-addresses">Authors' Addresses</name>
<author fullname="Scott Hollenbeck" initials="S." surname="Hollenbeck">
<organization showOnFrontPage="true">Verisign Labs</organization>
<address>
<postal>
<street>12061 Bluemont Way</street>
<city>Reston</city>
<region>VA</region>
<code>20190</code>
<country>United States of America</country>
</postal>
<email>shollenbeck@verisign.com</email>
<uri>https://www.verisignlabs.com/</uri>
</address>
</author>
<author fullname="Andy Newton" initials="A." surname="Newton">
<organization abbrev="AWS" showOnFrontPage="true">Amazon Web Services, Inc.</organization>
<address>
<postal>
<street>13200 Woodland Park Road</street>
<city>Herndon</city>
<region>VA</region>
<code>20171</code>
<country>United States of America</country>
</postal>
<email>andy@hxr.us</email>
</address>
</author>
</section>
</back>
</rfc>