rfc9083xml2.original.xml   rfc9083.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <rfc xmlns:xi="http://www.w3.org/2001/XInclude" version="3" category="std" conse
<!ENTITY RFC2119 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF nsus="true" docName="draft-ietf-regext-rfc7483bis-05" indexInclude="true" ipr="t
C.2119.xml"> rust200902" number="9083" obsoletes="7483" prepTime="2021-06-11T16:35:08" script
<!ENTITY RFC3339 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF s="Common,Latin" sortRefs="true" submissionType="IETF" symRefs="true" tocDepth="
C.3339.xml"> 3" tocInclude="true" xml:lang="en">
<!ENTITY RFC3629 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-rfc7483bis-05"
C.3629.xml"> rel="prev"/>
<!ENTITY RFC3912 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <link href="https://dx.doi.org/10.17487/rfc9083" rel="alternate"/>
C.3912.xml"> <link href="urn:issn:2070-1721" rel="alternate"/>
<!ENTITY RFC3986 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <front>
C.3986.xml"> <title abbrev="RDAP JSON Responses">JSON Responses for the Registration Data
<!ENTITY RFC4034 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF Access Protocol (RDAP)</title>
C.4034.xml"> <seriesInfo name="RFC" value="9083" stream="IETF"/>
<!ENTITY RFC5396 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <seriesInfo name="STD" value="95" stream="IETF"/>
C.5396.xml"> <author fullname="Scott Hollenbeck" initials="S." surname="Hollenbeck">
<!ENTITY RFC5646 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <organization showOnFrontPage="true">Verisign Labs</organization>
C.5646.xml"> <address>
<!ENTITY RFC5730 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <postal>
C.5730.xml"> <street>12061 Bluemont Way</street>
<!ENTITY RFC5890 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <city>Reston</city>
C.5890.xml"> <region>VA</region>
<!ENTITY RFC5910 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <code>20190</code>
C.5910.xml"> <country>United States of America</country>
<!ENTITY RFC5952 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF </postal>
C.5952.xml"> <email>shollenbeck@verisign.com</email>
<!ENTITY RFC6350 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <uri>https://www.verisignlabs.com/</uri>
C.6350.xml"> </address>
<!ENTITY RFC6839 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF </author>
C.6839.xml"> <author fullname="Andy Newton" initials="A." surname="Newton">
<!ENTITY RFC7095 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <organization abbrev="AWS" showOnFrontPage="true">Amazon Web Services, Inc
C.7095.xml"> .</organization>
<!ENTITY RFC7480 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <address>
C.7480.xml"> <postal>
<!ENTITY RFC7481 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <street>13200 Woodland Park Road</street>
C.7481.xml"> <city>Herndon</city>
<!ENTITY RFC7942 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <region>VA</region>
C.7942.xml"> <code>20171</code>
<!ENTITY RFC8126 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <country>United States of America</country>
C.8126.xml"> </postal>
<!ENTITY RFC8174 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <email>andy@hxr.us</email>
C.8174.xml"> </address>
<!ENTITY RFC8288 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF </author>
C.8288.xml"> <date month="06" year="2021"/>
<!ENTITY RFC8259 SYSTEM "https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RF <area>Applications and Real-Time</area>
C.8259.xml"> <workgroup>REGEXT Working Group</workgroup>
<!ENTITY I-D.ietf-regext-rfc7482bis SYSTEM 'https://xml2rfc.tools.ietf.org/publi <abstract pn="section-abstract">
c/rfc/bibxml3/reference.I-D.ietf-regext-rfc7482bis.xml'> <t indent="0" pn="section-abstract-1">
]>
<rfc category="std" docName="draft-ietf-regext-rfc7483bis-05" 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"?>
<front>
<title abbrev="RDAP JSON Responses">JSON Responses for the Registration D
ata Access Protocol (RDAP)</title>
<author fullname="Scott Hollenbeck" initials="S." surname="Hollenbeck">
<organization>Verisign Labs</organization>
<address><postal><street>12061 Bluemont Way</street>
<street>Reston, VA 20190</street>
<street>United States</street>
</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 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>
<date/>
<area>Applications and Real-Time</area>
<workgroup>REGEXT Working Group</workgroup>
<abstract><t>
This document describes JSON data structures representing This document describes JSON data structures representing
registration information maintained by Regional Internet Registries registration information maintained by Regional Internet Registries
(RIRs) and Domain Name Registries (DNRs). These data structures are (RIRs) and Domain Name Registries (DNRs). These data structures are
used to form Registration Data Access Protocol (RDAP) query used to form Registration Data Access Protocol (RDAP) query
responses. If approved, this document obsoletes RFC 7483.</t> responses. This document obsoletes RFC 7483.</t>
</abstract>
</abstract> <boilerplate>
</front> <section anchor="status-of-memo" numbered="false" removeInRFC="false" toc=
"exclude" pn="section-boilerplate.1">
<middle> <name slugifiedName="name-status-of-this-memo">Status of This Memo</name
<section title="Introduction" anchor="sect-1"><t> >
This document describes responses in the JSON <xref target="RFC8259"/> format <t indent="0" pn="section-boilerplate.1-1">
for 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="non
e"/>.
</t>
</section>
<section anchor="copyright" numbered="false" removeInRFC="false" toc="excl
ude" 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" p
n="section-toc.1">
<name slugifiedName="name-table-of-contents">Table of Contents</name>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="section-to
c.1-1">
<li pn="section-toc.1-1.1">
<t indent="0" keepWithNext="true" pn="section-toc.1-1.1.1"><xref der
ivedContent="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="sectio
n-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-te
rminology-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-da
ta-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" form
at="counter" sectionFormat="of" target="section-2"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-use-of-json">Use of JSON</xref></t
>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-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 derived
Content="" 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" form
at="counter" sectionFormat="of" target="section-3"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-common-data-types">Common Data Typ
es</xref></t>
</li>
<li pn="section-toc.1-1.4">
<t indent="0" pn="section-toc.1-1.4.1"><xref derivedContent="4" form
at="counter" sectionFormat="of" target="section-4"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-common-data-structures">Common Dat
a Structures</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-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 derived
Content="" 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 derived
Content="" 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 derived
Content="" format="title" sectionFormat="of" target="name-notices-and-remarks">N
otices 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 derived
Content="" format="title" sectionFormat="of" target="name-language-identifier">L
anguage 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 derived
Content="" 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 derived
Content="" 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 derived
Content="" 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 derived
Content="" 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 derived
Content="" format="title" sectionFormat="of" target="name-object-class-name">Obj
ect 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 deriv
edContent="" format="title" sectionFormat="of" target="name-an-example">An Examp
le</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" form
at="counter" sectionFormat="of" target="section-5"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-object-classes">Object Classes</xr
ef></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-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 derived
Content="" format="title" sectionFormat="of" target="name-the-entity-object-clas
s">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 derived
Content="" 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 derived
Content="" format="title" sectionFormat="of" target="name-the-domain-object-clas
s">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 derived
Content="" 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 derived
Content="" 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" form
at="counter" sectionFormat="of" target="section-6"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-error-response-body">Error Respons
e Body</xref></t>
</li>
<li pn="section-toc.1-1.7">
<t indent="0" pn="section-toc.1-1.7.1"><xref derivedContent="7" form
at="counter" sectionFormat="of" target="section-7"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-responding-to-help-queries">Respon
ding 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" form
at="counter" sectionFormat="of" target="section-8"/>.  <xref derivedContent="" f
ormat="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" form
at="counter" sectionFormat="of" target="section-9"/>.  <xref derivedContent="" f
ormat="title" sectionFormat="of" target="name-indicating-truncated-respon">Indic
ating 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" fo
rmat="counter" sectionFormat="of" target="section-10"/>. <xref derivedContent=""
format="title" sectionFormat="of" target="name-iana-considerations">IANA Consid
erations</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-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 deri
vedContent="" format="title" sectionFormat="of" target="name-rdap-json-media-typ
e-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 deri
vedContent="" format="title" sectionFormat="of" target="name-json-values-registr
y">JSON Values Registry</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="se
ction-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 derive
dContent="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 derive
dContent="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 derive
dContent="10.2.3" format="counter" sectionFormat="of" target="section-10.2.3"/>.
  <xref derivedContent="" format="title" sectionFormat="of" target="name-event-a
ctions">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 derive
dContent="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 derive
dContent="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" fo
rmat="counter" sectionFormat="of" target="section-11"/>. <xref derivedContent=""
format="title" sectionFormat="of" target="name-security-considerations">Securit
y Considerations</xref></t>
</li>
<li pn="section-toc.1-1.12">
<t indent="0" pn="section-toc.1-1.12.1"><xref derivedContent="12" fo
rmat="counter" sectionFormat="of" target="section-12"/>. <xref derivedContent=""
format="title" sectionFormat="of" target="name-internationalization-consid">Int
ernationalization Considerations</xref></t>
<ul bare="true" empty="true" indent="2" spacing="compact" pn="sectio
n-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 deri
vedContent="" 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 deri
vedContent="" 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 deri
vedContent="" format="title" sectionFormat="of" target="name-language-tags">Lang
uage 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 deri
vedContent="" format="title" sectionFormat="of" target="name-internationalized-d
omain-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" fo
rmat="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" fo
rmat="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="sectio
n-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 deri
vedContent="" format="title" sectionFormat="of" target="name-normative-reference
s">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 deri
vedContent="" format="title" sectionFormat="of" target="name-informative-referen
ces">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="Append
ix 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="sectio
n-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 derive
dContent="" format="title" sectionFormat="of" target="name-registrants-and-conta
cts">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 derive
dContent="" format="title" sectionFormat="of" target="name-registrars">Registrar
s</xref></t>
</li>
</ul>
</li>
<li pn="section-toc.1-1.16">
<t indent="0" pn="section-toc.1-1.16.1"><xref derivedContent="Append
ix 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="Append
ix C" format="default" sectionFormat="of" target="section-appendix.c"/>.  <xref
derivedContent="" format="title" sectionFormat="of" target="name-structured-vs-u
nstructured-">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="Append
ix D" format="default" sectionFormat="of" target="section-appendix.d"/>.  <xref
derivedContent="" format="title" sectionFormat="of" target="name-secure-dns">Sec
ure DNS</xref></t>
</li>
<li pn="section-toc.1-1.19">
<t indent="0" pn="section-toc.1-1.19.1"><xref derivedContent="Append
ix 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="Append
ix F" format="default" sectionFormat="of" target="section-appendix.f"/>.  <xref
derivedContent="" format="title" sectionFormat="of" target="name-changes-from-rf
c-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="" form
at="none" sectionFormat="of" target="section-appendix.g"/><xref derivedContent="
" format="title" sectionFormat="of" target="name-acknowledgments">Acknowledgment
s</xref></t>
</li>
<li pn="section-toc.1-1.22">
<t indent="0" pn="section-toc.1-1.22.1"><xref derivedContent="" form
at="none" sectionFormat="of" target="section-appendix.h"/><xref derivedContent="
" format="title" sectionFormat="of" target="name-authors-addresses">Authors' Add
resses</xref></t>
</li>
</ul>
</section>
</toc>
</front>
<middle>
<section anchor="sect-1" numbered="true" toc="include" removeInRFC="false" p
n="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" format="
default" sectionFormat="of" derivedContent="RFC8259"/> format for
the queries as defined by the Registration Data Access Protocol Query the queries as defined by the Registration Data Access Protocol Query
Format <xref target="I-D.ietf-regext-rfc7482bis"/>. A communication protocol Format <xref target="RFC9082" format="default" sectionFormat="of" derivedCont
for exchanging queries ent="RFC9082"/>. A communication protocol for exchanging queries
and responses is described in <xref target="RFC7480"/>. If approved, this doc and responses is described in <xref target="RFC7480" format="default" section
ument obsoletes RFC 7483.</t> Format="of" derivedContent="RFC7480"/>. This document obsoletes RFC 7483.</t>
<section anchor="sect-1.1" numbered="true" toc="include" removeInRFC="fals
<section title="Terminology and Definitions" anchor="sect-1.1"><t> e" pn="section-1.1">
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL <name slugifiedName="name-terminology-and-definitions">Terminology and D
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", efinitions</name>
"MAY", and "OPTIONAL" in this document are to be interpreted as <t indent="0" pn="section-1.1-1">
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, a The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUI
nd only when, they RED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD
</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NO
T RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to b
e interpreted as
described in BCP 14 <xref target="RFC2119" format="default" sectionFormat="of
" derivedContent="RFC2119"/> <xref target="RFC8174" format="default" sectionForm
at="of" derivedContent="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t> appear in all capitals, as shown here.</t>
<t indent="0" pn="section-1.1-2">
<t>
The following list describes terminology and definitions used The following list describes terminology and definitions used
throughout this document:</t> throughout this document:</t>
<dl newline="false" spacing="normal" indent="1" pn="section-1.1-3">
<t><list style="hanging" hangIndent="1"><t hangText="DNR:"> <dt pn="section-1.1-3.1">DNR:</dt>
<dd pn="section-1.1-3.2">
Domain Name Registry or Domain Name Registrar Domain Name Registry or Domain Name Registrar
<vspace blankLines="0"/> </dd>
</t> <dt pn="section-1.1-3.3">LDH:</dt>
<dd pn="section-1.1-3.4">
<t hangText="LDH:">
letters, digits, hyphen letters, digits, hyphen
<vspace blankLines="0"/> </dd>
</t> <dt pn="section-1.1-3.5">member:</dt>
<dd pn="section-1.1-3.6">
<t hangText="member:"> data found within an object as defined by JSON <xref target="RFC8259" for
data found within an object as defined by JSON <xref target="RFC8259"/> mat="default" sectionFormat="of" derivedContent="RFC8259"/>
</t> </dd>
<dt pn="section-1.1-3.7">object:</dt>
<t hangText="object:"> <dd pn="section-1.1-3.8">
a data structure as defined by JSON <xref target="RFC8259"/> a data structure as defined by JSON <xref target="RFC8259" format="defaul
<vspace blankLines="0"/> t" sectionFormat="of" derivedContent="RFC8259"/>
</t> </dd>
<dt pn="section-1.1-3.9">object class:</dt>
<t hangText="object class:"> <dd pn="section-1.1-3.10">
the definition of members that may be found in JSON the definition of members that may be found in JSON
objects described in this document objects described in this document
</t> </dd>
<dt pn="section-1.1-3.11">object instance:</dt>
<t hangText="object instance:"> <dd pn="section-1.1-3.12">
an instantiation or specific instance of an object an instantiation or specific instance of an object
class class
</t> </dd>
<dt pn="section-1.1-3.13">RDAP:</dt>
<t hangText="RDAP:"> <dd pn="section-1.1-3.14">
Registration Data Access Protocol Registration Data Access Protocol
<vspace blankLines="0"/> </dd>
</t> <dt pn="section-1.1-3.15">RIR:</dt>
<dd pn="section-1.1-3.16">
<t hangText="RIR:">
Regional Internet Registry Regional Internet Registry
<vspace blankLines="0"/> </dd>
</t> </dl>
</section>
</list> <section anchor="sect-1.2" numbered="true" toc="include" removeInRFC="fals
</t> e" pn="section-1.2">
<name slugifiedName="name-data-model">Data Model</name>
</section> <t indent="0" pn="section-1.2-1">
<section title="Data Model" anchor="sect-1.2"><t>
The data model for JSON responses is specified in five sections:</t> The data model for JSON responses is specified in five sections:</t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-1.
<t><list style="numbers"><t>simple data types conveyed in JSON 2-2"><li pn="section-1.2-2.1" derivedCounter="1.">simple data types conveyed in
primitive types (strings, numbers, booleans, and null)</t> JSON
primitive types (strings, numbers, booleans, and null)</li>
<t>data structures specified as JSON arrays or objects that are used <li pn="section-1.2-2.2" derivedCounter="2.">data structures specified
repeatedly when building up larger objects</t> as JSON arrays or objects that are used
repeatedly when building up larger objects</li>
<t>object classes representing structured data corresponding to a <li pn="section-1.2-2.3" derivedCounter="3.">object classes representi
lookup of a single object</t> ng structured data corresponding to a
lookup of a single object</li>
<t>arrays of objects representing structured data corresponding to a <li pn="section-1.2-2.4" derivedCounter="4.">arrays of objects represe
search for multiple objects</t> nting structured data corresponding to a
search for multiple objects</li>
<t>the response to an error</t> <li pn="section-1.2-2.5" derivedCounter="5.">the response to an error<
/li>
</list> </ol>
</t> <t indent="0" pn="section-1.2-3">
<t>
The object classes represent responses for two major categories of The object classes represent responses for two major categories of
data: responses returned by RIRs for registration data related to IP data: responses returned by RIRs for registration data related to IP
addresses, reverse DNS names, and Autonomous System numbers and addresses, reverse DNS names, and Autonomous System numbers and
responses returned by DNRs for registration data related to forward responses returned by DNRs for registration data related to forward
DNS names. The following object classes are returned by both RIRs DNS names. The following object classes are returned by both RIRs
and DNRs:</t> and DNRs:</t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-1.
<t><list style="numbers"><t>domains</t> 2-4"><li pn="section-1.2-4.1" derivedCounter="1.">domains</li>
<li pn="section-1.2-4.2" derivedCounter="2.">nameservers</li>
<t>nameservers</t> <li pn="section-1.2-4.3" derivedCounter="3.">entities</li>
</ol>
<t>entities</t> <t indent="0" pn="section-1.2-5">
</list>
</t>
<t>
The information served by both RIRs and DNRs for these object classes The information served by both RIRs and DNRs for these object classes
overlap extensively and are given in this document as a unified model overlap extensively and are given in this document as a unified model
for both classes of service.</t> for both classes of service.</t>
<t indent="0" pn="section-1.2-6">
<t>
In addition to the object classes listed above, RIRs also serve the In addition to the object classes listed above, RIRs also serve the
following object classes:</t> following object classes:</t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-1.
<t><list style="numbers"><t>IP networks</t> 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>Autonomous System numbers</t> </li>
</ol>
</list> <t indent="0" pn="section-1.2-8">
</t>
<t>
Object classes defined in this document represent a minimal set of Object classes defined in this document represent a minimal set of
what a compliant client/server needs to understand to function what a compliant client/server needs to understand to function
correctly; however, some deployments may want to include additional correctly; however, some deployments may want to include additional
object classes to suit individual needs. Anticipating this need for object classes to suit individual needs. Anticipating this need for
extension, Section 2.1 of this document defines a mechanism for extension, <xref target="sect-2.1" format="default" sectionFormat="of" derive dContent="Section 2.1"/> of this document defines a mechanism for
extending the JSON objects that are described in this document.</t> extending the JSON objects that are described in this document.</t>
<t indent="0" pn="section-1.2-9">
<t>
Positive responses take two forms. A response to a lookup of a Positive responses take two forms. A response to a lookup of a
single object in the registration system yields a JSON object, which single object in the registration system yields a JSON object, which
is the subject of the lookup. A response to a search for multiple 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 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 that are the subject of the search. In each type of response, other
data structures are present within the topmost JSON object.</t> data structures are present within the topmost JSON object.</t>
</section>
</section> </section>
<section anchor="sect-2" numbered="true" toc="include" removeInRFC="false" p
</section> n="section-2">
<name slugifiedName="name-use-of-json">Use of JSON</name>
<section title="Use of JSON" anchor="sect-2"><section title="Naming" anch <section anchor="sect-2.1" numbered="true" toc="include" removeInRFC="fals
or="sect-2.1"><t> e" pn="section-2.1">
Clients of these JSON responses SHOULD ignore unrecognized JSON <name slugifiedName="name-naming">Naming</name>
<t indent="0" pn="section-2.1-1">
Clients of these JSON responses <bcp14>SHOULD</bcp14> ignore unrecognized JSO
N
members in responses. Servers can insert members into the JSON members in responses. Servers can insert members into the JSON
responses, which are not specified in this document, but that does responses, which are not specified in this document, but that does
not constitute an error in the response. Servers that insert such not constitute an error in the response. Servers that insert such
unspecified members into JSON responses SHOULD have member names unspecified members into JSON responses <bcp14>SHOULD</bcp14> have member nam es
prefixed with a short identifier followed by an underscore followed prefixed with a short identifier followed by an underscore followed
by a meaningful name. It has been observed that these short by a meaningful name. It has been observed that these short
identifiers aid software implementers with identifying the identifiers aid software implementers with identifying the
specification of the JSON member, and failure to use one could cause specification of the JSON member, and failure to use one could cause
an implementer to assume the server is erroneously using a name from an implementer to assume the server is erroneously using a name from
this specification. This allowance does not apply to jCard <xref target="RFC 7095"/> this specification. This allowance does not apply to jCard <xref target="RFC 7095" format="default" sectionFormat="of" derivedContent="RFC7095"/>
objects. The full JSON name (the prefix plus the underscore plus the objects. The full JSON name (the prefix plus the underscore plus the
meaningful name) SHOULD adhere to the character and name limitations meaningful name) <bcp14>SHOULD</bcp14> adhere to the character and name limit
of the prefix registry described in <xref target="RFC7480"/>. Failure to use ations
these of the prefix registry described in <xref target="RFC7480" format="default" s
ectionFormat="of" derivedContent="RFC7480"/>. Failure to use these
limitations could result in slower adoption as these limitations have limitations could result in slower adoption as these limitations have
been observed to aid some client programming models.</t> been observed to aid some client programming models.</t>
<t indent="0" pn="section-2.1-2">
<t>
Consider the following JSON response with JSON members, all of which Consider the following JSON response with JSON members, all of which
are specified in this document.</t> are specified in this document.</t>
<figure anchor="ure-1" align="left" suppress-title="false" pn="figure-1"
<figure anchor="ure-1"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-2.1-3.1">
{ {
"handle" : "ABC123", "handle" : "ABC123",
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-2.1-4">
If The Registry of the Moon desires to express information not found If The Registry of the Moon desires to express information not found
in this specification, it might select "lunarNIC" as its identifying in this specification, it might select "lunarNIC" as its identifying
prefix and insert, as an example, the member named prefix and insert, as an example, the member named
"lunarNIC_beforeOneSmallStep" to signify registrations occurring "lunarNIC_beforeOneSmallStep" to signify registrations occurring
before the first moon landing and the member named before the first moon landing and the member named
"lunarNIC_harshMistressNotes" that contains other descriptive text.</t> "lunarNIC_harshMistressNotes" that contains other descriptive text.</t>
<t indent="0" pn="section-2.1-5">
<t>
Consider the following JSON response with JSON names, some of which Consider the following JSON response with JSON names, some of which
should be ignored by clients without knowledge of their meaning.</t> should be ignored by clients without knowledge of their meaning.</t>
<figure anchor="ure-2" align="left" suppress-title="false" pn="figure-2"
<figure anchor="ure-2"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-2.1-6.1">
{ {
"handle" : "ABC123", "handle" : "ABC123",
"lunarNIC_beforeOneSmallStep" : "TRUE THAT!", "lunarNIC_beforeOneSmallStep" : "TRUE THAT!",
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
], ],
"lunarNIC_harshMistressNotes" : "lunarNIC_harshMistressNotes" :
[ [
"In space,", "In space,",
"nobody can hear you scream." "nobody can hear you scream."
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-2.1-7">
Insertion of unrecognized members ignored by clients may also be used Insertion of unrecognized members ignored by clients may also be used
for future revisions to this specification.</t> for future revisions to this specification.</t>
<t indent="0" pn="section-2.1-8">
<t>
Clients processing JSON responses need to be prepared for members Clients processing JSON responses need to be prepared for members
representing registration data specified in this document to be representing registration data specified in this document to be
absent from a response. In other words, servers are free to omit absent from a response. In other words, servers are free to omit
unrequired/optional JSON members containing registration data based unrequired/optional JSON members containing registration data based
on their own policies.</t> on their own policies.</t>
<t indent="0" pn="section-2.1-9">
<t>
Finally, all JSON names specified in this document are case Finally, all JSON names specified in this document are case
sensitive. Both servers and clients MUST transmit and process them sensitive. Both servers and clients <bcp14>MUST</bcp14> transmit and process them
using the specified character case.</t> using the specified character case.</t>
</section>
</section> </section>
<section anchor="sect-3" numbered="true" toc="include" removeInRFC="false" p
</section> n="section-3">
<name slugifiedName="name-common-data-types">Common Data Types</name>
<section title="Common Data Types" anchor="sect-3"><t> <t indent="0" pn="section-3-1">
JSON <xref target="RFC8259"/> defines the data types of a number, character s JSON <xref target="RFC8259" format="default" sectionFormat="of" derivedConten
tring, t="RFC8259"/> defines the data types of a number, character string,
boolean, array, object, and null. This section describes the boolean, array, object, and null. This section describes the
semantics and/or syntax reference for common, JSON character strings semantics and/or syntax reference for common, JSON character strings
used in this document.</t> used in this document.</t>
<dl newline="false" spacing="normal" indent="18" pn="section-3-2">
<t><list style="hanging" hangIndent="18"><t hangText="handle:"> <dt pn="section-3-2.1">handle:</dt>
<dd pn="section-3-2.2">
DNRs and RIRs have registry-unique identifiers that DNRs and RIRs have registry-unique identifiers that
may be used to specifically reference an object may be used to specifically reference an object
instance. The semantics of this data type as found instance. The semantics of this data type as found
in this document are to be a registry-unique in this document are to be a registry-unique
reference to the closest enclosing object where the reference to the closest enclosing object where the
value is found. The data type names "registryId", value is found. The data type names "registryId",
"roid", "nic-handle", "registrationNo", etc., are "roid", "nic-handle", "registrationNo", etc., are
terms often synonymous with this data type. In terms often synonymous with this data type. In
this document, the term "handle" is used. The term this document, the term "handle" is used. The term
exposed to users by clients is a presentation issue exposed to users by clients is a presentation issue
beyond the scope of this document. This value is a beyond the scope of this document. This value is a
simple character string. simple character string.
</t> </dd>
<dt pn="section-3-2.3">IPv4 addresses:</dt>
<t hangText="IPv4 addresses:"> <dd pn="section-3-2.4">
The representation of IPv4 addresses in this The representation of IPv4 addresses in this
document uses the dotted-decimal notation. An document uses the dotted-decimal notation. An
example of this textual representation is example of this textual representation is
"192.0.2.0". "192.0.2.0".
</t> </dd>
<dt pn="section-3-2.5">IPv6 addresses:</dt>
<t hangText="IPv6 addresses:"> <dd pn="section-3-2.6">
The representation of IPv6 addresses in this The representation of IPv6 addresses in this
document follow the forms outlined in <xref target="RFC5952"/>. document follow the forms outlined in <xref target="RFC5952" format="defa ult" sectionFormat="of" derivedContent="RFC5952"/>.
An example of this textual representation is An example of this textual representation is
"2001:db8::1:0:0:1". "2001:db8::1:0:0:1".
</t> </dd>
<dt pn="section-3-2.7">country codes:</dt>
<t hangText="country codes:"> <dd pn="section-3-2.8">
Where the identity of a geopolitical nation or Where the identity of a geopolitical nation or
country is needed, these identities are represented country is needed, these identities are represented
with the alpha-2 or two-character country code with the alpha-2 or two-character country code
designation as defined in <xref target="ISO.3166.1988"/>. The designation as defined in <xref target="ISO.3166.2020" format="default" sect ionFormat="of" derivedContent="ISO.3166.2020"/>. The
alpha-2 representation is used because it is freely alpha-2 representation is used because it is freely
available, whereas the alpha-3 and numeric-3 available, whereas the alpha-3 and numeric-3
standards are not. standards are not.
</t> </dd>
<dt pn="section-3-2.9">LDH names:</dt>
<t hangText="LDH names:"> <dd pn="section-3-2.10">
Textual representations of DNS names where the Textual representations of DNS names where the
labels of the domain are all "letters, digits, hyphen" labels as describe d by <xref target="RFC5890"/>. Trailing labels of the domain are all "letters, digits, hyphen" labels as describe d by <xref target="RFC5890" format="default" sectionFormat="of" derivedContent=" RFC5890"/>. Trailing
periods are optional. periods are optional.
</t> </dd>
<dt pn="section-3-2.11">Unicode names:</dt>
<t hangText="Unicode names:"> <dd pn="section-3-2.12">
Textual representations of DNS names where one or Textual representations of DNS names where one or
more of the labels are U-labels as described by more of the labels are U-labels as described by
<xref target="RFC5890"/>. Trailing periods are optional. <xref target="RFC5890" format="default" sectionFormat="of" derivedContent="R
</t> FC5890"/>. Trailing periods are optional.
</dd>
<t hangText="dates and times:"> <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 The syntax for values denoting dates and times is
defined in <xref target="RFC3339"/>. defined in <xref target="RFC3339" format="default" sectionFormat="of" der
</t> ivedContent="RFC3339"/>.
</dd>
<t hangText="URIs:"> <dt pn="section-3-2.15">URIs:</dt>
<dd pn="section-3-2.16">
The syntax for values denoting a Uniform Resource The syntax for values denoting a Uniform Resource
Identifier (URI) is defined by <xref target="RFC3986"/>. Identifier (URI) is defined by <xref target="RFC3986" format="default" se
</t> ctionFormat="of" derivedContent="RFC3986"/>.
</dd>
</list> </dl>
</t> <t indent="0" pn="section-3-3">
<t>
Contact information is defined using jCards as described in Contact information is defined using jCards as described in
<xref target="RFC7095"/>. The "fn" member is required and MUST <xref target="RFC7095" format="default" sectionFormat="of" derivedContent="RF
NOT be null according to <xref target="RFC6350"/>. An empty C7095"/>. The "fn" member is required and <bcp14>MUST NOT</bcp14> be null accord
"fn" member MAY be used when the contact name does not exist ing to <xref target="RFC6350" format="default" sectionFormat="of" derivedContent
="RFC6350"/>. An empty
"fn" member <bcp14>MAY</bcp14> be used when the contact name does not exist
or is redacted.</t> or is redacted.</t>
</section>
</section> <section anchor="sect-4" numbered="true" toc="include" removeInRFC="false" p
n="section-4">
<section title="Common Data Structures" anchor="sect-4"><t> <name slugifiedName="name-common-data-structures">Common Data Structures</
name>
<t indent="0" pn="section-4-1">
This section defines common data structures used in responses and This section defines common data structures used in responses and
object classes.</t> object classes.</t>
<section anchor="sect-4.1" numbered="true" toc="include" removeInRFC="fals
<section title="RDAP Conformance" anchor="sect-4.1"><t> e" 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, The data structure named "rdapConformance" is an array of strings,
each providing a hint as to the specifications used in the each providing a hint as to the specifications used in the
construction of the response. This data structure MUST appear construction of the response. This data structure <bcp14>MUST</bcp14> appear
in the topmost JSON object of a response and MUST NOT appear in the topmost JSON object of a response and <bcp14>MUST NOT</bcp14> appear
anywhere else. A response to a "help" anywhere else. A response to a "help"
request will include identifiers for all of the specifications request will include identifiers for all of the specifications
supported by the server. A response to any other request will supported by the server. A response to any other request will
include only identifiers for the specifications used in the include only identifiers for the specifications used in the
construction of the response. The set of returned identifiers construction of the response. The set of returned identifiers
MAY vary depending on the authorization level of the client.</t> <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> An example rdapConformance data structure:</t>
<figure anchor="ure-3" align="left" suppress-title="false" pn="figure-3"
<figure anchor="ure-3"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-4.1-3.1">
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-4.1-4">
The string literal "rdap_level_0" signifies conformance with this The string literal "rdap_level_0" signifies conformance with this
specification. When custom JSON values are inserted into responses, specification. When custom JSON values are inserted into responses,
conformance to those custom specifications MUST be indicated by including conformance to those custom specifications <bcp14>MUST</bcp14> be indicated b y including
a unique string literal value registered in the IANA RDAP Extensions a unique string literal value registered in the IANA RDAP Extensions
registry specified in <xref target="RFC7480"/>. For example, if the fictiona l registry specified in <xref 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 Registry of the Moon wants to signify that their JSON responses are
conformant with their registered extensions, the string used might be conformant with their registered extensions, the string used might be
"lunarNIC_level_0". These registered values aid the identification of "lunarNIC_level_0". These registered values aid the identification of
specifications for software implementers, and failure to use them specifications for software implementers, and failure to use them
could result in slower adoption of extensions.</t> could result in slower adoption of extensions.</t>
<t indent="0" pn="section-4.1-5">
<t>
Example rdapConformance structure with custom extensions noted:</t> Example rdapConformance structure with custom extensions noted:</t>
<figure anchor="ure-4" align="left" suppress-title="false" pn="figure-4"
<figure anchor="ure-4"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-4.1-6.1">
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0", "rdap_level_0",
"lunarNIC_level_0" "lunarNIC_level_0"
] ]
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-4.2" numbered="true" toc="include" removeInRFC="fals
<section title="Links" anchor="sect-4.2"><t> e" 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 The "links" array is found in data structures to signify links to
other resources on the Internet. The relationship of these links is other resources on the Internet. The relationship of these links is
defined by the IANA registry described by <xref target="RFC8288"/>.</t> defined by the IANA registry described by <xref target="RFC8288" format="defa
ult" sectionFormat="of" derivedContent="RFC8288"/>.</t>
<t><list style="hanging" hangIndent="1"><t hangText="The following is an <t indent="0" pn="section-4.2-2">The following is an example of the link
example of the link structure:"> structure:</t>
<vspace blankLines="0"/> <figure anchor="ure-5" align="left" suppress-title="false" pn="figure-5"
</t> >
<sourcecode type="json" markers="false" pn="section-4.2-3.1">
</list>
</t>
<figure anchor="ure-5"><artwork><![CDATA[
{ {
"value" : "https://example.com/context_uri", "value" : "https://example.com/context_uri",
"rel" : "self", "rel" : "self",
"href" : "https://example.com/target_uri", "href" : "https://example.com/target_uri",
"hreflang" : [ "en", "ch" ], "hreflang" : [ "en", "ch" ],
"title" : "title", "title" : "title",
"media" : "screen", "media" : "screen",
"type" : "application/json" "type" : "application/json"
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-4.2-4">
The JSON name/values of "rel", "href", "hreflang", "title", "media", The JSON name/values of "rel", "href", "hreflang", "title", "media",
and "type" correspond to values found in Section 3 of <xref target="RFC8288"/ and "type" correspond to values found in <xref target="RFC8288" section="3" s
>. The ectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc82
"value" JSON value is the context URI as described by <xref target="RFC8288"/ 88#section-3" derivedContent="RFC8288"/>. The
>. The "value" JSON value is the context URI as described by <xref target="RFC8288"
"value", "rel" and "href" JSON values MUST be specified. All other JSON valu format="default" sectionFormat="of" derivedContent="RFC8288"/>. The
es are "value", "rel", and "href" JSON values <bcp14>MUST</bcp14> be specified. All
OPTIONAL. A "related" link relation MUST NOT include an "href" URI that is th other JSON values are
e <bcp14>OPTIONAL</bcp14>. A "related" link relation <bcp14>MUST NOT</bcp14> in
clude an "href" URI that is the
same as the "self" link relation "href" URI to reduce the risk of infinite cl ient same as the "self" link relation "href" URI to reduce the risk of infinite cl ient
processing loops. Internationalized Domain Names (IDNs) returned in URIs SHOU LD processing loops. Internationalized Domain Names (IDNs) returned in URIs <bcp 14>SHOULD</bcp14>
be consistently returned in LDH name format to allow clients to process these IDNs be consistently returned in LDH name format to allow clients to process these IDNs
according to their capabilities.</t> according to their capabilities.</t>
<t indent="0" pn="section-4.2-5">
<t>
This is an example of the "links" array as it might be found in an This is an example of the "links" array as it might be found in an
object class:</t> object class:</t>
<figure anchor="ure-6" align="left" suppress-title="false" pn="figure-6"
<figure anchor="ure-6"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-4.2-6.1">
"links" : "links" :
[ [
{ {
"value" : "https://example.com/ip/2001:db8::123", "value" : "https://example.com/ip/2001:db8::123",
"rel" : "self", "rel" : "self",
"href" : "https://example.com/ip/2001:db8::123", "href" : "https://example.com/ip/2001:db8::123",
"type" : "application/rdap+json" "type" : "application/rdap+json"
}, },
{ {
"value" : "https://example.com/ip/2001:db8::123", "value" : "https://example.com/ip/2001:db8::123",
"rel" : "up", "rel" : "up",
"href" : "https://example.com/ip/2001:db8::/48", "href" : "https://example.com/ip/2001:db8::/48",
"type" : "application/rdap+json" "type" : "application/rdap+json"
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-4.3" numbered="true" toc="include" removeInRFC="fals
<section title="Notices and Remarks" anchor="sect-4.3"><t> e" pn="section-4.3">
<name slugifiedName="name-notices-and-remarks">Notices and Remarks</name
>
<t indent="0" pn="section-4.3-1">
The "notices" and "remarks" data structures take the same form. The The "notices" and "remarks" data structures take the same form. The
notices structure denotes information about the service providing notices structure denotes information about the service providing
RDAP information and/or information about the entire response, RDAP information and/or information about the entire response,
whereas the remarks structure denotes information about the object whereas the remarks structure denotes information about the object
class that contains it (see <xref target="sect-5"/> regarding object classes) class that contains it (see <xref target="sect-5" format="default" sectionFor
.</t> mat="of" derivedContent="Section 5"/> regarding object classes).</t>
<t indent="0" pn="section-4.3-2">Both are arrays of objects. Each objec
<t>Both are arrays of objects. Each object contains a "title" string t contains a "title" string
representing the title of the object, a "type" string denoting a representing the title of the object, a "type" string denoting a
registered type of remark or notice (see <xref target="sect-10.2.1"/>), an registered type of remark or notice (see <xref target="sect-10.2.1" format="d efault" sectionFormat="of" derivedContent="Section 10.2.1"/>), an
array of strings named "description" for the purposes of conveying any 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" descriptive text, and a "links" array as described in <xref target="sect-4.2"
/>. The format="default" sectionFormat="of" derivedContent="Section 4.2"/>. The
"description" array MUST be included. All other JSON values are OPTIONAL.</t> "description" array <bcp14>MUST</bcp14> be included. All other JSON values ar
e <bcp14>OPTIONAL</bcp14>.</t>
<t> <t indent="0" pn="section-4.3-3">
An example of the notices data structure:</t> An example of the notices data structure:</t>
<figure anchor="ure-7" align="left" suppress-title="false" pn="figure-7"
<figure anchor="ure-7"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-4.3-4.1">
"notices" : "notices" :
[ [
{ {
"title" : "Terms of Use", "title" : "Terms of Use",
"description" : "description" :
[ [
"Service subject to The Registry of the Moon's TOS.", "Service subject to The Registry of the Moon's TOS.",
"Copyright (c) 2020 LunarNIC" "Copyright (c) 2020 LunarNIC"
], ],
"links" : "links" :
[ [
{ {
"value" : "https://example.net/entity/XXXX", "value" : "https://example.net/entity/XXXX",
"rel" : "alternate", "rel" : "alternate",
"type" : "text/html", "type" : "text/html",
"href" : "https://www.example.com/terms_of_use.html" "href" : "https://www.example.com/terms_of_use.html"
} }
] ]
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-4.3-5">
It is the job of the clients to determine line breaks, spacing, and It is the job of the clients to determine line breaks, spacing, and
display issues for sentences within the character strings of the display issues for sentences within the character strings of the
"description" array. Each string in the "description" array contains "description" array. Each string in the "description" array contains
a single complete division of human-readable text indicating to a single complete division of human-readable text indicating to
clients where there are semantic breaks.</t> clients where there are semantic breaks.</t>
<t indent="0" pn="section-4.3-6">
<t>
An example of the remarks data structure:</t> An example of the remarks data structure:</t>
<figure anchor="ure-8" align="left" suppress-title="false" pn="figure-8"
<figure anchor="ure-8"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-4.3-7.1">
"remarks" : "remarks" :
[ [
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-4.3-8">
Note that objects in the "remarks" array may also have a "links" Note that objects in the "remarks" array may also have a "links"
array.</t> array.</t>
<t indent="0" pn="section-4.3-9">
<t>
While the "title" and "description" fields are intended primarily for While the "title" and "description" fields are intended primarily for
human consumption, the "type" string contains a well-known value to human consumption, the "type" string contains a well-known value to
be registered with IANA (see <xref target="sect-10.2.1"/>) for programmatic u be registered with IANA (see <xref target="sect-10.2.1" format="default" sect
se.</t> ionFormat="of" derivedContent="Section 10.2.1"/>) for programmatic use.</t>
<t indent="0" pn="section-4.3-10">
<t>
An example of the remarks data structure:</t> An example of the remarks data structure:</t>
<figure anchor="ure-9" align="left" suppress-title="false" pn="figure-9"
<figure anchor="ure-9"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-4.3-11.1">
"remarks" : "remarks" :
[ [
{ {
"type" : "object truncated due to authorization", "type" : "object truncated due to authorization",
"description" : "description" :
[ [
"Some registration data may not have been given.", "Some registration data may not have been given.",
"Use proper authorization credentials to see all of it." "Use proper authorization credentials to see all of it."
] ]
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-4.3-12">
While the "remarks" array will appear in many object classes in a 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, the "notices" array appears only in the topmost object of a
response.</t> response.</t>
</section>
</section> <section anchor="sect-4.4" numbered="true" toc="include" removeInRFC="fals
e" pn="section-4.4">
<section title="Language Identifier" anchor="sect-4.4"><t> <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 This data structure consists solely of a name/value pair, where the
name is "lang" and the value is a string containing a language name is "lang" and the value is a string containing a language
identifier as described in <xref target="RFC5646"/>.</t> identifier as described in <xref target="RFC5646" format="default" sectionFor
mat="of" derivedContent="RFC5646"/>.</t>
<t><figure anchor="ure-10"><artwork>"lang" : "mn-Cyrl-MN"</artwork></figu <figure anchor="ure-10" align="left" suppress-title="false" pn="figure-1
re> 0">
</t> <sourcecode type="json" markers="false" pn="section-4.4-2.1">"lang" :
"mn-Cyrl-MN"</sourcecode>
<t>The "lang" attribute as defined in this section MAY appear anywhere </figure>
<t indent="0" pn="section-4.4-3">The "lang" attribute as defined in this
section <bcp14>MAY</bcp14> appear anywhere
in an object class or data structure, except for in jCard objects. vCard in an object class or data structure, except for in jCard objects. vCard
supports similar functionality by way of the LANGUAGE property parameter supports similar functionality by way of the LANGUAGE property parameter
(see Section 5.1 of RFC 6350 <xref target="RFC6350"/>).</t> (see Section <xref target="RFC6350" section="5.1" sectionFormat="bare" fo
rmat="default" derivedLink="https://rfc-editor.org/rfc/rfc6350#section-5.1" deri
</section> vedContent="RFC6350"/> of RFC 6350 <xref target="RFC6350" format="default" secti
onFormat="of" derivedContent="RFC6350"/>).</t>
<section title="Events" anchor="sect-4.5"><t> </section>
<section anchor="sect-4.5" numbered="true" toc="include" removeInRFC="fals
e" 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 This data structure represents events that have occurred on an
instance of an object class (see <xref target="sect-5"/> regarding object cla instance of an object class (see <xref target="sect-5" format="default" secti
sses).</t> onFormat="of" derivedContent="Section 5"/> regarding object classes).</t>
<t indent="0" pn="section-4.5-2">
<t>
This is an example of an "events" array.</t> This is an example of an "events" array.</t>
<figure anchor="ure-11" align="left" suppress-title="false" pn="figure-1
<figure anchor="ure-11"><artwork><![CDATA[ 1">
<sourcecode type="json" markers="false" pn="section-4.5-3.1">
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventActor" : "SOMEID-LUNARNIC", "eventActor" : "SOMEID-LUNARNIC",
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventActor" : "OTHERID-LUNARNIC", "eventActor" : "OTHERID-LUNARNIC",
"eventDate" : "1991-12-31T23:59:59Z" "eventDate" : "1991-12-31T23:59:59Z"
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-4.5-4">
The "events" array consists of objects, each with the following members:</t> The "events" array consists of objects, each with the following members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4
<t><list style="symbols"><t>"eventAction" -- a REQUIRED string denoting t .5-5">
he reason for the event</t> <li pn="section-4.5-5.1">"eventAction" -- a <bcp14>REQUIRED</bcp14> st
ring denoting the reason for the event</li>
<t>"eventActor" -- an OPTIONAL identifier denoting the actor <li pn="section-4.5-5.2">"eventActor" -- an <bcp14>OPTIONAL</bcp14> id
responsible for the event</t> entifier denoting the actor
responsible for the event</li>
<t>"eventDate" -- a REQUIRED string containing the time and date the even <li pn="section-4.5-5.3">"eventDate" -- a <bcp14>REQUIRED</bcp14> stri
t ng containing the time and date the event
occurred</t> occurred</li>
<li pn="section-4.5-5.4">"links" -- <bcp14>OPTIONAL</bcp14>; see <xref
<t>"links" -- OPTIONAL; see <xref target="sect-4.2"/> target="sect-4.2" format="default" sectionFormat="of" derivedContent="Section 4
</t> .2"/>
</li>
</list> </ul>
</t> <t indent="0" pn="section-4.5-6">
<t>
Events can be future dated. One use case for future dating of events Events can be future dated. One use case for future dating of events
is to denote when an object expires from a registry.</t> is to denote when an object expires from a registry.</t>
<t indent="0" pn="section-4.5-7">
<t>
The "links" array in this data structure is provided for references 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 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 "related" and a "type" of "application/rdap+json" is used in the link
reference.</t> reference.</t>
<t indent="0" pn="section-4.5-8">
<t> See <xref target="sect-10.2.3" format="default" sectionFormat="of" derivedCon
See <xref target="sect-10.2.3"/> for a list of values for the "eventAction" s tent="Section 10.2.3"/> for a list of values for the "eventAction" string.
tring. See <xref target="sect-b" format="default" sectionFormat="of" derivedContent=
See Appendix B regarding the various ways events can be modeled.</t> "Appendix B"/> regarding the various ways events can be modeled.</t>
</section>
</section> <section anchor="sect-4.6" numbered="true" toc="include" removeInRFC="fals
e" pn="section-4.6">
<section title="Status" anchor="sect-4.6"><t> <name slugifiedName="name-status">Status</name>
<t indent="0" pn="section-4.6-1">
This data structure, named "status", is an array of strings This data structure, named "status", is an array of strings
indicating the state of a registered object (see <xref target="sect-10.2.2"/> for a indicating the state of a registered object (see <xref target="sect-10.2.2" f ormat="default" sectionFormat="of" derivedContent="Section 10.2.2"/> for a
list of values).</t> list of values).</t>
</section>
</section> <section anchor="sect-4.7" numbered="true" toc="include" removeInRFC="fals
e" pn="section-4.7">
<section title="Port 43 WHOIS Server" anchor="sect-4.7"><t> <name slugifiedName="name-port-43-whois-server">Port 43 WHOIS Server</na
me>
<t indent="0" pn="section-4.7-1">
This data structure, a member named "port43", is a simple character string This data structure, a member named "port43", is a simple character string
containing the fully qualified host name or IP address of the WHOIS containing the fully qualified host name or IP address of the WHOIS
<xref target="RFC3912"/> server where the containing object instance may be f ound. <xref target="RFC3912" format="default" sectionFormat="of" derivedContent="RF C3912"/> server where the containing object instance may be found.
Note that this is not a URI, as there is no WHOIS URI scheme.</t> Note that this is not a URI, as there is no WHOIS URI scheme.</t>
</section>
</section> <section anchor="sect-4.8" numbered="true" toc="include" removeInRFC="fals
e" pn="section-4.8">
<section title="Public IDs" anchor="sect-4.8"><t> <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 This data structure maps a public identifier to an object class. It
is named "publicIds" and is an array of objects, with each object is named "publicIds" and is an array of objects, with each object
containing the following REQUIRED members:</t> containing the following <bcp14>REQUIRED</bcp14> members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-4
<t><list style="symbols"><t>type -- a string denoting the type of public .8-2">
identifier</t> <li pn="section-4.8-2.1">type -- a string denoting the type of public
identifier</li>
<t>identifier -- a string denoting a public identifier of the type relate <li pn="section-4.8-2.2">identifier -- a string denoting a public iden
d to "type"</t> tifier of the type related to "type"</li>
</ul>
</list> <t indent="0" pn="section-4.8-3">
</t>
<t>
The following is an example of a publicIds structure.</t> The following is an example of a publicIds structure.</t>
<figure anchor="ure-12" align="left" suppress-title="false" pn="figure-1
<figure anchor="ure-12"><artwork><![CDATA[ 2">
<sourcecode type="json" markers="false" pn="section-4.8-4.1">
"publicIds": "publicIds":
[ [
{ {
"type":"IANA Registrar ID", "type":"IANA Registrar ID",
"identifier":"1" "identifier":"1"
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-4.9" numbered="true" toc="include" removeInRFC="fals
<section title="Object Class Name" anchor="sect-4.9"><t> e" pn="section-4.9">
<name slugifiedName="name-object-class-name">Object Class Name</name>
<t indent="0" pn="section-4.9-1">
This data structure, a member named "objectClassName", gives the This data structure, a member named "objectClassName", gives the
object class name of a particular object as a string. This object class name of a particular object as a string. This
identifies the type of object being processed. An objectClassName is identifies the type of object being processed. An objectClassName is
REQUIRED in all RDAP response objects so that the type of the object <bcp14>REQUIRED</bcp14> in all RDAP response objects so that the type of the object
can be interpreted.</t> can be interpreted.</t>
</section>
</section> <section anchor="sect-4.10" numbered="true" toc="include" removeInRFC="fal
se" pn="section-4.10">
<section title="An Example" anchor="sect-4.10"><t> <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 This is an example response with both rdapConformance and notices
embedded:</t> embedded:</t>
<figure anchor="ure-13" align="left" suppress-title="false" pn="figure-1
<figure anchor="ure-13"><artwork><![CDATA[ 3">
<sourcecode type="json" markers="false" pn="section-4.10-2.1">
{ {
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
], ],
"notices" : "notices" :
[ [
{ {
"title" : "Content Removed", "title" : "Content Removed",
"description" : "description" :
skipping to change at line 760 skipping to change at line 906
{ {
"description" : "description" :
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
</section>
</section> <section anchor="sect-5" numbered="true" toc="include" removeInRFC="false" p
n="section-5">
<section title="Object Classes" anchor="sect-5"><t> <name slugifiedName="name-object-classes">Object Classes</name>
<t indent="0" pn="section-5-1">
Object classes represent structures appropriate for a response from Object classes represent structures appropriate for a response from
the queries specified in <xref target="I-D.ietf-regext-rfc7482bis"/>.</t> the queries specified in <xref target="RFC9082" format="default" sectionForma
t="of" derivedContent="RFC9082"/>.</t>
<t> <t indent="0" pn="section-5-2">
Each object class contains a "links" array as specified in Each object class contains a "links" array as specified in
<xref target="sect-4.2"/>. For every object class instance in a response, wh ether <xref target="sect-4.2" format="default" sectionFormat="of" derivedContent="S ection 4.2"/>. For every object class instance in a response, whether
the object class instance is directly representing the response to a 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 query or is embedded in other object class instances or is an item in
a search result set, servers SHOULD provide a link representing a URI a search result set, servers <bcp14>SHOULD</bcp14> provide a link representin g a URI
for that object class instance using the "self" relationship as for that object class instance using the "self" relationship as
described in the IANA registry specified by <xref target="RFC8288"/>. As exp described in the IANA registry specified by <xref target="RFC8288" format="de
lained fault" sectionFormat="of" derivedContent="RFC8288"/>. As explained
in <xref target="sect-5.2"/>, this may be not always be possible for nameserv in <xref target="sect-5.2" format="default" sectionFormat="of" derivedContent
er ="Section 5.2"/>, this may be not always be possible for nameserver
data. Clients MUST be able to process object instances without a data. Clients <bcp14>MUST</bcp14> be able to process object instances withou
t a
self link. When present, clients can use the self link for caching self link. When present, clients can use the self link for caching
data. Servers MAY provide more than one self link for any given data. Servers <bcp14>MAY</bcp14> provide more than one self link for any giv en
object instance. Failure to provide any self link by a server may object instance. Failure to provide any self link by a server may
result in clients being unable to cache object class instances.</t> result in clients being unable to cache object class instances.</t>
<t indent="0" pn="section-5-3">
<t> Clients using self links for caching <bcp14>SHOULD NOT</bcp14> cache any obje
Clients using self links for caching SHOULD NOT cache any object ct
class instances where the authority of the self link is different class instances where the authority of the self link is different
than the authority of the server returning the data. Failing to do than the authority of the server returning the data. Failing to do
so might result in cache poisoning.</t> so might result in cache poisoning.</t>
<t indent="0" pn="section-5-4">
<t> Self links <bcp14>MUST</bcp14> contain a "type" element containing the "appli
Self links MUST contain a "type" element containing the "application/rdap+jso cation/rdap+json" media type when referencing RDAP object instances as
n" media type when referencing RDAP object instances as
defined by this document.</t> defined by this document.</t>
<t indent="0" pn="section-5-5">
<t>
This is an example of the "links" array with a self link to an object This is an example of the "links" array with a self link to an object
class:</t> class:</t>
<figure anchor="ure-14" align="left" suppress-title="false" pn="figure-14"
<figure anchor="ure-14"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-5-6.1">
"links" : "links" :
[ [
{ {
"value" : "https://example.com/ip/2001:db8::123", "value" : "https://example.com/ip/2001:db8::123",
"rel" : "self", "rel" : "self",
"href" : "https://example.com/ip/2001:db8::123", "href" : "https://example.com/ip/2001:db8::123",
"type" : "application/rdap+json" "type" : "application/rdap+json"
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<section title="The Entity Object Class" anchor="sect-5.1"><t> <section anchor="sect-5.1" numbered="true" toc="include" removeInRFC="fals
e" pn="section-5.1">
<name slugifiedName="name-the-entity-object-class">The Entity Object Cla
ss</name>
<t indent="0" pn="section-5.1-1">
The entity object class appears throughout this document and is an The entity object class appears throughout this document and is an
appropriate response for the /entity/XXXX query defined in appropriate response for the /entity/XXXX query defined in
"Registration Data Access Protocol (RDAP) Query Format" <xref target="I-D.iet f-regext-rfc7482bis"/>. "<xref target="RFC9082" format="title" sectionFormat="of" derivedContent="Reg istration Data Access Protocol (RDAP) Query Format"/>" <xref target="RFC9082" fo rmat="default" sectionFormat="of" derivedContent="RFC9082"/>.
This object class represents the information of organizations, This object class represents the information of organizations,
corporations, governments, non-profits, clubs, individual persons, corporations, governments, non-profits, clubs, individual persons,
and informal groups of people. All of these representations are so and informal groups of people. All of these representations are so
similar that it is best to represent them in JSON <xref target="RFC8259"/> wi th one similar that it is best to represent them in JSON <xref target="RFC8259" form at="default" sectionFormat="of" derivedContent="RFC8259"/> with one
construct, the entity object class, to aid in the reuse of code by construct, the entity object class, to aid in the reuse of code by
implementers.</t> implementers.</t>
<t indent="0" pn="section-5.1-2">
<t> The entity object class uses jCard <xref target="RFC7095" format="default" se
The entity object class uses jCard <xref target="RFC7095"/> to represent cont ctionFormat="of" derivedContent="RFC7095"/> to represent contact
act
information, such as postal addresses, email addresses, phone numbers information, such as postal addresses, email addresses, phone numbers
and names of organizations and individuals. Many of the types of 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, information that can be represented with jCard have little or no use in RDAP,
such as birthdays, anniversaries, and gender.</t> such as birthdays, anniversaries, and gender.</t>
<t indent="0" pn="section-5.1-3">
<t>
The entity object is served by both RIRs and DNRs. The following is The entity object is served by both RIRs and DNRs. The following is
an example of an entity that might be served by an RIR.</t> an example of an entity that might be served by an RIR.</t>
<figure anchor="ure-15" align="left" suppress-title="false" pn="figure-1
<figure anchor="ure-15"><artwork><![CDATA[ 5">
<sourcecode type="json" markers="false" pn="section-5.1-4.1">
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle":"XXXX", "handle":"XXXX",
"vcardArray":[ "vcardArray":[
"vcard", "vcard",
[ [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"], ["fn", {}, "text", "Joe User"],
["n", {}, "text", ["n", {}, "text",
["User", "Joe", "", "", ["ing. jr", "M.Sc."]] ["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
skipping to change at line 949 skipping to change at line 1091
} }
], ],
"asEventActor":[ "asEventActor":[
{ {
"eventAction":"last changed", "eventAction":"last changed",
"eventDate":"1991-12-31T23:59:59Z" "eventDate":"1991-12-31T23:59:59Z"
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.1-5">
The entity object class can contain the following members:</t> The entity object class can contain the following members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
<t><list style="symbols"><t>objectClassName -- the string "entity"</t> .1-6">
<li pn="section-5.1-6.1">objectClassName -- the string "entity"</li>
<t>handle -- a string representing a registry-unique identifier of <li pn="section-5.1-6.2">handle -- a string representing a registry-un
the entity</t> ique identifier of
the entity</li>
<t>vcardArray -- a jCard with the entity's contact information</t> <li pn="section-5.1-6.3">vcardArray -- a jCard with the entity's conta
ct information</li>
<t>roles -- an array of strings, each signifying the relationship an <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 object would have with its closest containing object (see
<xref target="sect-10.2.4"/> for a list of values)</t> <xref target="sect-10.2.4" format="default" sectionFormat="of" derivedCont
ent="Section 10.2.4"/> for a list of values)</li>
<t>publicIds -- see <xref target="sect-4.8"/> <li pn="section-5.1-6.5">publicIds -- see <xref target="sect-4.8" form
</t> at="default" sectionFormat="of" derivedContent="Section 4.8"/>
</li>
<t>entities -- an array of entity objects as defined by this section</t> <li pn="section-5.1-6.6">entities -- an array of entity objects as def
ined by this section</li>
<t>remarks -- see <xref target="sect-4.3"/> <li pn="section-5.1-6.7">remarks -- see <xref target="sect-4.3" format
</t> ="default" sectionFormat="of" derivedContent="Section 4.3"/>
</li>
<t>links -- see <xref target="sect-4.2"/> <li pn="section-5.1-6.8">links -- see <xref target="sect-4.2" format="
</t> default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
<t>events -- see <xref target="sect-4.5"/> <li pn="section-5.1-6.9">events -- see <xref target="sect-4.5" format=
</t> "default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
<t>asEventActor -- this data structure takes the same form as the <li pn="section-5.1-6.10">asEventActor -- this data structure takes th
events data structure (see <xref target="sect-4.5"/>), but each object in e same form as the
the events data structure (see <xref target="sect-4.5" format="default" sectio
array MUST NOT have an "eventActor" member. These objects denote nFormat="of" derivedContent="Section 4.5"/>), but each object in the
array <bcp14>MUST NOT</bcp14> have an "eventActor" member. These objects
denote
that the entity is an event actor for the given events. See that the entity is an event actor for the given events. See
Appendix B regarding the various ways events can be modeled.</t> <xref target="sect-b" format="default" sectionFormat="of" derivedContent="
Appendix B"/> regarding the various ways events can be modeled.</li>
<t>status -- see <xref target="sect-4.6"/> <li pn="section-5.1-6.11">status -- see <xref target="sect-4.6" format
</t> ="default" sectionFormat="of" derivedContent="Section 4.6"/>
</li>
<t>port43 -- see <xref target="sect-4.7"/> <li pn="section-5.1-6.12">port43 -- see <xref target="sect-4.7" format
</t> ="default" sectionFormat="of" derivedContent="Section 4.7"/>
</li>
<t>networks -- an array of IP network objects as defined in <li pn="section-5.1-6.13">networks -- an array of IP network objects a
<xref target="sect-5.4"/> s defined in
</t> <xref target="sect-5.4" format="default" sectionFormat="of" derivedContent
="Section 5.4"/>
<t>autnums -- an array of autnum objects as defined in <xref target="sect </li>
-5.5"/> <li pn="section-5.1-6.14">autnums -- an array of autnum objects as def
</t> ined in <xref target="sect-5.5" format="default" sectionFormat="of" derivedConte
nt="Section 5.5"/>
</list> </li>
</t> </ul>
<t indent="0" pn="section-5.1-7">
<t>
Entities may also have other entities embedded with them in an array. Entities may also have other entities embedded with them in an array.
This can be used to model an organization with specific individuals This can be used to model an organization with specific individuals
fulfilling designated roles of responsibility.</t> fulfilling designated roles of responsibility.</t>
<t indent="0" pn="section-5.1-8">
<t>
The following is an elided example of an entity with embedded The following is an elided example of an entity with embedded
entities.</t> entities.</t>
<figure anchor="ure-16" align="left" suppress-title="false" pn="figure-1
<figure anchor="ure-16"><artwork><![CDATA[ 6">
<sourcecode type="json" markers="false" pn="section-5.1-9.1">
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle" : "ANENTITY", "handle" : "ANENTITY",
"roles" : [ "registrar" ], "roles" : [ "registrar" ],
... ...
"entities" : "entities" :
[ [
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle": "ANEMBEDDEDENTITY", "handle": "ANEMBEDDEDENTITY",
"roles" : [ "technical" ], "roles" : [ "technical" ],
... ...
}, },
... ...
], ],
... ...
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.1-10">
The following is an example of an entity that might be served by a The following is an example of an entity that might be served by a
DNR.</t> DNR.</t>
<figure anchor="ure-17" align="left" suppress-title="false" pn="figure-1
<figure anchor="ure-17"><artwork><![CDATA[ 7">
<sourcecode type="json" markers="false" pn="section-5.1-11.1">
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle":"XXXX", "handle":"XXXX",
"vcardArray":[ "vcardArray":[
"vcard", "vcard",
[ [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"], ["fn", {}, "text", "Joe User"],
["kind", {}, "text", "individual"], ["kind", {}, "text", "individual"],
["lang", { ["lang", {
skipping to change at line 1108 skipping to change at line 1233
"eventAction":"registration", "eventAction":"registration",
"eventDate":"1990-12-31T23:59:59Z" "eventDate":"1990-12-31T23:59:59Z"
}, },
{ {
"eventAction":"last changed", "eventAction":"last changed",
"eventDate":"1991-12-31T23:59:59Z", "eventDate":"1991-12-31T23:59:59Z",
"eventActor":"joe@example.com" "eventActor":"joe@example.com"
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.1-12">
See Appendix A for use of the entity object class to model various See <xref target="sect-a" format="default" sectionFormat="of" derivedContent=
types of entities found in both RIRs and DNRs. See Appendix C "Appendix A"/> for use of the entity object class to model various
types of entities found in both RIRs and DNRs. See <xref target="sect-c" for
mat="default" sectionFormat="of" derivedContent="Appendix C"/>
regarding structured vs. unstructured postal addresses in entities.</t> regarding structured vs. unstructured postal addresses in entities.</t>
</section>
</section> <section anchor="sect-5.2" numbered="true" toc="include" removeInRFC="fals
e" pn="section-5.2">
<section title="The Nameserver Object Class" anchor="sect-5.2"><t> <name slugifiedName="name-the-nameserver-object-class">The Nameserver Ob
ject Class</name>
<t indent="0" pn="section-5.2-1">
The nameserver object class represents information regarding DNS The nameserver object class represents information regarding DNS
nameservers used in both forward and reverse DNS. RIRs and some DNRs nameservers used in both forward and reverse DNS. RIRs and some DNRs
register or expose nameserver information as an attribute of a domain register or expose nameserver information as an attribute of a domain
name, while other DNRs model nameservers as "first class objects". name, while other DNRs model nameservers as "first class objects".
Please note that some of the examples in this section include lines Please note that some of the examples in this section include lines
that have been wrapped for reading clarity.</t> that have been wrapped for reading clarity.</t>
<t indent="0" pn="section-5.2-2">
<t>
The nameserver object class accommodates both models and degrees of The nameserver object class accommodates both models and degrees of
variation in between.</t> variation in between.</t>
<t indent="0" pn="section-5.2-3">The following is an example of a namese
<t><list style="hanging" hangIndent="1"><t hangText="The following is an rver object.</t>
example of a nameserver object."> <figure anchor="ure-18" align="left" suppress-title="false" pn="figure-1
<vspace blankLines="0"/> 8">
</t> <sourcecode type="json" markers="false" pn="section-5.2-4.1">
</list>
</t>
<figure anchor="ure-18"><artwork><![CDATA[
{ {
"objectClassName" : "nameserver", "objectClassName" : "nameserver",
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "ns1.xn--fo-5ja.example", "ldhName" : "ns1.xn--fo-5ja.example",
"unicodeName" : "ns.fóo.example", "unicodeName" : "ns.fóo.example",
"status" : [ "active" ], "status" : [ "active" ],
"ipAddresses" : "ipAddresses" :
{ {
"v4": [ "192.0.2.1", "192.0.2.2" ], "v4": [ "192.0.2.1", "192.0.2.2" ],
"v6": [ "2001:db8::123" ] "v6": [ "2001:db8::123" ]
skipping to change at line 1162 skipping to change at line 1280
[ [
"She sells sea shells down by the sea shore.", "She sells sea shells down by the sea shore.",
"Originally written by Terry Sullivan." "Originally written by Terry Sullivan."
] ]
} }
], ],
"links" : "links" :
[ [
{ {
"value" : "https://example.net/nameserver/ "value" : "https://example.net/nameserver/
ns1.xn--fo-5ja.example", ns1.xn--fo-5ja.example",
"rel" : "self", "rel" : "self",
"href" : "https://example.net/nameserver/ "href" : "https://example.net/nameserver/
ns1.xn--fo-5ja.example", ns1.xn--fo-5ja.example",
"type" : "application/rdap+json" "type" : "application/rdap+json"
} }
], ],
"port43" : "whois.example.net", "port43" : "whois.example.net",
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z", "eventDate" : "1991-12-31T23:59:59Z",
"eventActor" : "joe@example.com" "eventActor" : "joe@example.com"
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.2-5">
Figure 18 is an example of a nameserver object with all appropriate values gi <xref target="ure-18" format="default" sectionFormat="of" derivedContent="Fig
ven. ure 18"/> is an example of a nameserver object with all appropriate values given
.
Registries using a first-class nameserver data model would embed this Registries using a first-class nameserver data model would embed this
in domain objects as well as allowing references to it with the in domain objects as well as allowing references to it with the
"/nameserver" query type (all depending on the registry operators "/nameserver" query type (all depending on the registry operators
policy). Other registries may pare back the information as needed. policy). Other registries may pare back the information as needed.
Figure 19 is an example of a nameserver object as would be found in <xref target="ure-19" format="default" sectionFormat="of" derivedContent="Fig
RIRs and some DNRs, while Figure 20 is an example of a nameserver ure 19"/> is an example of a nameserver object as would be found in
RIRs and some DNRs, while <xref target="ure-20" format="default" sectionForma
t="of" derivedContent="Figure 20"/> is an example of a nameserver
object as would be found in other DNRs.</t> object as would be found in other DNRs.</t>
<t indent="0" pn="section-5.2-6">The following is an example of the simp
<t><list style="hanging" hangIndent="1"><t hangText="The following is an lest nameserver object:</t>
example of the simplest nameserver object:"> <figure anchor="ure-19" align="left" suppress-title="false" pn="figure-1
<vspace blankLines="0"/> 9">
</t> <sourcecode type="json" markers="false" pn="section-5.2-7.1">
</list>
</t>
<figure anchor="ure-19"><artwork><![CDATA[
{ {
"objectClassName" : "nameserver", "objectClassName" : "nameserver",
"ldhName" : "ns1.example.com" "ldhName" : "ns1.example.com"
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.2-8">
The following is an example of a simple nameserver object that might The following is an example of a simple nameserver object that might
be commonly used by DNRs:</t> be commonly used by DNRs:</t>
<figure anchor="ure-20" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-20"><artwork><![CDATA[ 0">
<sourcecode type="json" markers="false" pn="section-5.2-9.1">
{ {
"objectClassName" : "nameserver", "objectClassName" : "nameserver",
"ldhName" : "ns1.example.com", "ldhName" : "ns1.example.com",
"ipAddresses" : { "v6" : [ "2001:db8::123", "2001:db8::124" ] } "ipAddresses" : { "v6" : [ "2001:db8::123", "2001:db8::124" ] }
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.2-10">
As nameservers can be modeled by some registries to be first-class 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"/>) objects, they may also have an array of entities (<xref target="sect-5.1" for mat="default" sectionFormat="of" derivedContent="Section 5.1"/>)
embedded to signify parties responsible for the maintenance, embedded to signify parties responsible for the maintenance,
registrations, etc., of the nameservers.</t> registrations, etc., of the nameservers.</t>
<t indent="0" pn="section-5.2-11">
<t>
The following is an elided example of a nameserver with embedded The following is an elided example of a nameserver with embedded
entities.</t> entities.</t>
<figure anchor="ure-21" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-21"><artwork><![CDATA[ 1">
<sourcecode type="json" markers="false" pn="section-5.2-12.1">
{ {
"objectClassName" : "nameserver", "objectClassName" : "nameserver",
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "ns.xn--fo-5ja.example", "ldhName" : "ns.xn--fo-5ja.example",
... ...
"entities" : "entities" :
[ [
... ...
], ],
... ...
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.2-13">
The nameserver object class can contain the following members:</t> The nameserver object class can contain the following members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
<t><list style="symbols"><t>objectClassName -- the string "nameserver"</t .2-14">
> <li pn="section-5.2-14.1">objectClassName -- the string "nameserver"</
li>
<t>handle -- a string representing a registry-unique identifier of <li pn="section-5.2-14.2">handle -- a string representing a registry-u
the nameserver</t> nique identifier of
the nameserver</li>
<t>ldhName -- a string containing the LDH name of the nameserver (see <li pn="section-5.2-14.3">ldhName -- a string containing the LDH name
<xref target="sect-3"/>)</t> of the nameserver (see
<xref target="sect-3" format="default" sectionFormat="of" derivedContent="
<t>unicodeName -- a string containing a DNS Unicode name of the Section 3"/>)</li>
nameserver (see <xref target="sect-3"/>)</t> <li pn="section-5.2-14.4">unicodeName -- a string containing a DNS Uni
code name of the
<t>ipAddresses -- an object containing the following members:<list style= nameserver (see <xref target="sect-3" format="default" sectionFormat="of"
"symbols"><t>v6 -- an array of strings containing IPv6 addresses of the derivedContent="Section 3"/>)</li>
nameserver</t> <li pn="section-5.2-14.5">
<t indent="0" pn="section-5.2-14.5.1">ipAddresses -- an object conta
<t>v4 -- an array of strings containing IPv4 addresses of the ining the following members:</t>
nameserver</t> <ul spacing="normal" bare="false" empty="false" indent="3" pn="secti
on-5.2-14.5.2">
</list> <li pn="section-5.2-14.5.2.1">v6 -- an array of strings containing
</t> IPv6 addresses of the
nameserver</li>
<t>entities -- an array of entity objects as defined by <xref target="sec <li pn="section-5.2-14.5.2.2">v4 -- an array of strings containing
t-5.1"/> IPv4 addresses of the
</t> nameserver</li>
</ul>
<t>status -- see <xref target="sect-4.6"/> </li>
</t> <li pn="section-5.2-14.6">entities -- an array of entity objects as de
fined by <xref target="sect-5.1" format="default" sectionFormat="of" derivedCont
<t>remarks -- see <xref target="sect-4.3"/> ent="Section 5.1"/>
</t> </li>
<li pn="section-5.2-14.7">status -- see <xref target="sect-4.6" format
<t>links -- see <xref target="sect-4.2"/> ="default" sectionFormat="of" derivedContent="Section 4.6"/>
</t> </li>
<li pn="section-5.2-14.8">remarks -- see <xref target="sect-4.3" forma
<t>port43 -- see <xref target="sect-4.7"/> t="default" sectionFormat="of" derivedContent="Section 4.3"/>
</t> </li>
<li pn="section-5.2-14.9">links -- see <xref target="sect-4.2" format=
<t>events -- see <xref target="sect-4.5"/> "default" sectionFormat="of" derivedContent="Section 4.2"/>
</t> </li>
<li pn="section-5.2-14.10">port43 -- see <xref target="sect-4.7" forma
</list> t="default" sectionFormat="of" derivedContent="Section 4.7"/>
</t> </li>
<li pn="section-5.2-14.11">events -- see <xref target="sect-4.5" forma
</section> t="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
<section title="The Domain Object Class" anchor="sect-5.3"><t> </ul>
</section>
<section anchor="sect-5.3" numbered="true" toc="include" removeInRFC="fals
e" pn="section-5.3">
<name slugifiedName="name-the-domain-object-class">The Domain Object Cla
ss</name>
<t indent="0" pn="section-5.3-1">
The domain object class represents a DNS name and point of The domain object class represents a DNS name and point of
delegation. For RIRs, these delegation points are in the reverse DNS delegation. For RIRs, these delegation points are in the reverse DNS
tree, whereas for DNRs, these delegation points are in the forward tree, whereas for DNRs, these delegation points are in the forward
DNS tree.</t> DNS tree.</t>
<t indent="0" pn="section-5.3-2">
<t>
In both cases, the high-level structure of the domain object class In both cases, the high-level structure of the domain object class
consists of information about the domain registration, nameserver consists of information about the domain registration, nameserver
information related to the domain name, and entities related to the information related to the domain name, and entities related to the
domain name (e.g., registrant information, contacts, etc.).</t> domain name (e.g., registrant information, contacts, etc.).</t>
<t indent="0" pn="section-5.3-3">
<t>
The following is an elided example of the domain object showing the The following is an elided example of the domain object showing the
high-level structure:</t> high-level structure:</t>
<figure anchor="ure-22" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-22"><artwork><![CDATA[ 2">
<sourcecode type="json" markers="false" pn="section-5.3-4.1">
{ {
"objectClassName" : "domain", "objectClassName" : "domain",
"handle" : "XXX", "handle" : "XXX",
"ldhName" : "blah.example.com", "ldhName" : "blah.example.com",
... ...
"nameservers" : "nameservers" :
[ [
... ...
], ],
... ...
"entities" : "entities" :
[ [
... ...
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.3-5">
The domain object class can contain the following members:</t> The domain object class can contain the following members:</t>
<t indent="0" pn="section-5.3-6">
<t><!-- </t>
rfc7483.xml.txt(1543): Warning: Found unexpected inentation change: worked on <ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
' .3-7">
+ links - see Section 4.2', found ' See Appendix D for background <li pn="section-5.3-7.1">objectClassName -- the string "domain"</li>
information on these objects.' <li pn="section-5.3-7.2">handle -- a string representing a registry-un
--><list style="symbols"><t>objectClassName -- the string "domain"</t> ique identifier of
the domain object instance</li>
<t>handle -- a string representing a registry-unique identifier of <li pn="section-5.3-7.3">ldhName -- a string describing a domain name
the domain object instance</t> in LDH form as
described in <xref target="sect-3" format="default" sectionFormat="of" der
<t>ldhName -- a string describing a domain name in LDH form as ivedContent="Section 3"/>
described in <xref target="sect-3"/> </li>
</t> <li pn="section-5.3-7.4">unicodeName -- a string containing a domain n
ame with U-labels as
<t>unicodeName -- a string containing a domain name with U-labels as described in <xref target="sect-3" format="default" sectionFormat="of" der
described in <xref target="sect-3"/> ivedContent="Section 3"/>
</t> </li>
<li pn="section-5.3-7.5">
<t>variants -- an array of objects, each containing the following <t indent="0" pn="section-5.3-7.5.1">variants -- an array of objects
values:<list style="symbols"><t>relation -- an array of strings, with each , each containing the following
string denoting the values:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="secti
on-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 relationship between the variants and the containing domain
object (see <xref target="sect-10.2.5"/> for a list of suggested varian object (see <xref target="sect-10.2.5" format="default" sectionFormat="
t of" derivedContent="Section 10.2.5"/> for a list of suggested variant
relations).</t> relations).</li>
<li pn="section-5.3-7.5.2.2">idnTable -- the character string lite
<t>idnTable -- the character string literal that represents the Internati ral that represents the Internationalized
onalized
Domain Name (IDN) table that has been registered in the IANA Repository o f IDN Domain Name (IDN) table that has been registered in the IANA Repository o f IDN
Practices <xref target="IANA_IDNTABLES"/>.</t> Practices <xref target="IANA_IDNTABLES" format="default" sectionFormat="o
f" derivedContent="IANA_IDNTABLES"/>.</li>
<t>variantNames -- an array of objects, with each object <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 containing an "ldhName" member and a "unicodeName" member (see
<xref target="sect-3"/>).</t> <xref target="sect-3" format="default" sectionFormat="of" derivedConten
t="Section 3"/>).</li>
</list> </ul>
</t> </li>
<li pn="section-5.3-7.6">nameservers -- an array of nameserver objects
<t>nameservers -- an array of nameserver objects as defined by as defined by
<xref target="sect-5.2"/> <xref target="sect-5.2" format="default" sectionFormat="of" derivedContent
</t> ="Section 5.2"/>
</li>
<t>secureDNS -- an object with the following members:<list style="symbols <li pn="section-5.3-7.7">
"><t>zoneSigned -- boolean true if the zone has been signed, false <t indent="0" pn="section-5.3-7.7.1">secureDNS -- an object with the
otherwise.</t> following members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="secti
<t>delegationSigned -- boolean true if there are DS records in the on-5.3-7.7.2">
parent, false otherwise.</t> <li pn="section-5.3-7.7.2.1">zoneSigned -- boolean true if the zon
e has been signed, false
<t>maxSigLife -- an integer representing the signature lifetime in otherwise.</li>
<li pn="section-5.3-7.7.2.2">delegationSigned -- boolean true if t
here are DS records in the
parent, false 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 seconds to be used when creating the RRSIG DS record in the
parent zone <xref target="RFC5910"/>.</t> parent zone <xref target="RFC5910" format="default" sectionFormat="of"
derivedContent="RFC5910"/>.</li>
<t>dsData -- an array of objects, each with the following members:<list s <li pn="section-5.3-7.7.2.4">
tyle="symbols"><t>keyTag -- an integer as specified by the key tag field of a <t indent="0" pn="section-5.3-7.7.2.4.1">dsData -- an array of o
DNS DS record as specified by <xref target="RFC4034"/> in presentati bjects, each with the following members:</t>
on <ul spacing="normal" bare="false" empty="false" indent="3" pn="s
format</t> ection-5.3-7.7.2.4.2">
<li pn="section-5.3-7.7.2.4.2.1">keyTag -- an integer as speci
<t>algorithm -- an integer as specified by the algorithm field fied by the key tag field of a
DNS DS record as specified by <xref target="RFC4034" format="default
" sectionFormat="of" derivedContent="RFC4034"/> in presentation
format</li>
<li pn="section-5.3-7.7.2.4.2.2">algorithm -- an integer as sp
ecified by the algorithm field
of a DNS DS record as described by RFC 4034 in presentation of a DNS DS record as described by RFC 4034 in presentation
format</t> format</li>
<li pn="section-5.3-7.7.2.4.2.3">digest -- a string as specifi
<t>digest -- a string as specified by the digest field of a DNS ed by the digest field of a DNS
DS record as specified by RFC 4034 in presentation format</t> DS record as specified by RFC 4034 in presentation format</li>
<li pn="section-5.3-7.7.2.4.2.4">digestType -- an integer as s
<t>digestType -- an integer as specified by the digest type pecified by the digest type
field of a DNS DS record as specified by RFC 4034 in field of a DNS DS record as specified by RFC 4034 in
presentation format</t> presentation format</li>
<li pn="section-5.3-7.7.2.4.2.5">events -- see <xref target="s
<t>events -- see <xref target="sect-4.5"/> ect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
</t> </li>
<li pn="section-5.3-7.7.2.4.2.6">links -- see <xref target="se
<t>links -- see <xref target="sect-4.2"/> ct-4.2" format="default" sectionFormat="of" derivedContent="Section 4.2"/>
</t> </li>
</ul>
</list> </li>
</t> <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
<t>keyData -- an array of objects, each with the following objects, each with the following
members:<list style="symbols"><t>flags -- an integer representing the f members:</t>
lags field value in <ul spacing="normal" bare="false" empty="false" indent="3" pn="s
the DNSKEY record <xref target="RFC4034"/> in presentation format</t ection-5.3-7.7.2.5.2">
> <li pn="section-5.3-7.7.2.5.2.1">flags -- an integer represent
ing the flags field value in
<t>protocol -- an integer representation of the protocol field the DNSKEY record <xref target="RFC4034" format="default" sectionFor
value of the DNSKEY record <xref target="RFC4034"/> in presentation mat="of" derivedContent="RFC4034"/> in presentation format</li>
format</t> <li pn="section-5.3-7.7.2.5.2.2">protocol -- an integer repres
entation of the protocol field
<t>publicKey -- a string representation of the public key in value of the DNSKEY record <xref target="RFC4034" format="default" s
the DNSKEY record <xref target="RFC4034"/> in presentation format</t ectionFormat="of" derivedContent="RFC4034"/> in presentation format</li>
> <li pn="section-5.3-7.7.2.5.2.3">publicKey -- a string represe
ntation of the public key in
<t>algorithm -- an integer as specified by the algorithm field the DNSKEY record <xref target="RFC4034" format="default" sectionFor
of a DNSKEY record as specified by <xref target="RFC4034"/> in prese mat="of" derivedContent="RFC4034"/> in presentation format</li>
ntation <li pn="section-5.3-7.7.2.5.2.4">algorithm -- an integer as sp
format</t> ecified by the algorithm field
of a DNSKEY record as specified by <xref target="RFC4034" format="de
<t>events -- see <xref target="sect-4.5"/> fault" sectionFormat="of" derivedContent="RFC4034"/> in presentation
</t> format</li>
<li pn="section-5.3-7.7.2.5.2.5">events -- see <xref target="s
<t>links -- see <xref target="sect-4.2"/> ect-4.5" format="default" sectionFormat="of" derivedContent="Section 4.5"/>
<list style="hanging" hangIndent="1"><t hangText="See Appendix D for back </li>
ground information on these objects."> <li pn="section-5.3-7.7.2.5.2.6">
<vspace blankLines="0"/> <t indent="0" pn="section-5.3-7.7.2.5.2.6.1">links -- see <x
</t> ref target="sect-4.2" format="default" sectionFormat="of" derivedContent="Sectio
n 4.2"/>
</list> </t>
</t> <t indent="0" pn="section-5.3-7.7.2.5.2.6.2">See <xref targe
t="sect-d" format="default" sectionFormat="of" derivedContent="Appendix D"/> for
</list> background information on these objects.</t>
</t> </li>
</ul>
</list> </li>
</t> </ul>
</li>
<t>entities -- an array of entity objects as defined by <xref target="sec <li pn="section-5.3-7.8">entities -- an array of entity objects as def
t-5.1"/> ined by <xref target="sect-5.1" format="default" sectionFormat="of" derivedConte
</t> nt="Section 5.1"/>
</li>
<t>status -- see <xref target="sect-4.6"/> <li pn="section-5.3-7.9">status -- see <xref target="sect-4.6" format=
</t> "default" sectionFormat="of" derivedContent="Section 4.6"/>
</li>
<t>publicIds -- see <xref target="sect-4.8"/> <li pn="section-5.3-7.10">publicIds -- see <xref target="sect-4.8" for
</t> mat="default" sectionFormat="of" derivedContent="Section 4.8"/>
</li>
<t>remarks -- see <xref target="sect-4.3"/> <li pn="section-5.3-7.11">remarks -- see <xref target="sect-4.3" forma
</t> t="default" sectionFormat="of" derivedContent="Section 4.3"/>
</li>
<t>links -- see <xref target="sect-4.2"/> <li pn="section-5.3-7.12">links -- see <xref target="sect-4.2" format=
</t> "default" sectionFormat="of" derivedContent="Section 4.2"/>
</li>
<t>port43 -- see <xref target="sect-4.7"/> <li pn="section-5.3-7.13">port43 -- see <xref target="sect-4.7" format
</t> ="default" sectionFormat="of" derivedContent="Section 4.7"/>
</li>
<t>events -- see <xref target="sect-4.5"/> <li pn="section-5.3-7.14">events -- see <xref target="sect-4.5" format
</t> ="default" sectionFormat="of" derivedContent="Section 4.5"/>
</li>
<t>network -- represents the IP network for which a reverse DNS <li pn="section-5.3-7.15">network -- represents the IP network for whi
domain is referenced; see <xref target="sect-5.4"/> ch a reverse DNS
</t> domain is referenced; see <xref target="sect-5.4" format="default" section
Format="of" derivedContent="Section 5.4"/>
</list> </li>
</t> </ul>
<t indent="0" pn="section-5.3-8">
<t>
The following is an example of a JSON domain object representing a The following is an example of a JSON domain object representing a
reverse DNS delegation point that might be served by an RIR (note 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> that the dsData digest value has been modified to fit on one line).</t>
<figure anchor="ure-23" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-23"><artwork><![CDATA[ 3">
<sourcecode type="json" markers="false" pn="section-5.3-9.1">
{ {
"objectClassName" : "domain", "objectClassName" : "domain",
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "0.2.192.in-addr.arpa", "ldhName" : "0.2.192.in-addr.arpa",
"nameservers" : "nameservers" :
[ [
{ {
"objectClassName" : "nameserver", "objectClassName" : "nameserver",
"ldhName" : "ns1.rir.example" "ldhName" : "ns1.rir.example"
}, },
skipping to change at line 1619 skipping to change at line 1688
"startAddress" : "192.0.2.0", "startAddress" : "192.0.2.0",
"endAddress" : "192.0.2.255", "endAddress" : "192.0.2.255",
"ipVersion" : "v4", "ipVersion" : "v4",
"name": "NET-RTR-1", "name": "NET-RTR-1",
"type" : "DIRECT ALLOCATION", "type" : "DIRECT ALLOCATION",
"country" : "AU", "country" : "AU",
"parentHandle" : "YYYY-RIR", "parentHandle" : "YYYY-RIR",
"status" : [ "active" ] "status" : [ "active" ]
} }
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.3-10">
The following is an example of a JSON domain object representing a The following is an example of a JSON domain object representing a
forward DNS delegation point that might be served by a DNR. Note that 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 the secureDNS keyData publicKey value has been modified to fit on a
single line.</t> single line.</t>
<figure anchor="ure-24" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-24"><artwork><![CDATA[ 4">
<sourcecode type="json" markers="false" pn="section-5.3-11.1">
{ {
"objectClassName" : "domain", "objectClassName" : "domain",
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "xn--fo-5ja.example", "ldhName" : "xn--fo-5ja.example",
"unicodeName" : "fóo.example", "unicodeName" : "fóo.example",
"variants" : "variants" :
[ [
{ {
"relation" : [ "registered", "conjoined" ], "relation" : [ "registered", "conjoined" ],
"variantNames" : "variantNames" :
skipping to change at line 1900 skipping to change at line 1969
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z" "eventDate" : "1991-12-31T23:59:59Z"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-5.4" numbered="true" toc="include" removeInRFC="fals
<section title="The IP Network Object Class" anchor="sect-5.4"><t> e" pn="section-5.4">
<name slugifiedName="name-the-ip-network-object-class">The IP Network Ob
ject Class</name>
<t indent="0" pn="section-5.4-1">
The IP network object class models IP network registrations found in The IP network object class models IP network registrations found in
RIRs and is the expected response for the "/ip" query as defined by RIRs and is the expected response for the "/ip" query as defined by
<xref target="I-D.ietf-regext-rfc7482bis"/>. There is no equivalent object c lass for DNRs. The high- <xref target="RFC9082" format="default" sectionFormat="of" derivedContent="RF C9082"/>. There is no equivalent object class for DNRs. The high-
level structure of the IP network object class consists of level structure of the IP network object class consists of
information about the network registration and entities related to information about the network registration and entities related to
the IP network (e.g., registrant information, contacts, etc.).</t> the IP network (e.g., registrant information, contacts, etc.).</t>
<t indent="0" pn="section-5.4-2">
<t>
The following is an elided example of the IP network object type The following is an elided example of the IP network object type
showing the high-level structure:</t> showing the high-level structure:</t>
<figure anchor="ure-25" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-25"><artwork><![CDATA[ 5">
<sourcecode type="json" markers="false" pn="section-5.4-3.1">
{ {
"objectClassName" : "ip network", "objectClassName" : "ip network",
"handle" : "XXX", "handle" : "XXX",
... ...
"entities" : "entities" :
[ [
... ...
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.4-4">
The following is an example of the JSON object for the network The following is an example of the JSON object for the network
registration information.</t> registration information.</t>
<figure anchor="ure-26" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-26"><artwork><![CDATA[ 6">
<sourcecode type="json" markers="false" pn="section-5.4-5.1">
{ {
"objectClassName" : "ip network", "objectClassName" : "ip network",
"handle" : "XXXX-RIR", "handle" : "XXXX-RIR",
"startAddress" : "2001:db8::", "startAddress" : "2001:db8::",
"endAddress" : "2001:db8:0:ffff:ffff:ffff:ffff:ffff", "endAddress" : "2001:db8:0:ffff:ffff:ffff:ffff:ffff",
"ipVersion" : "v6", "ipVersion" : "v6",
"name": "NET-RTR-1", "name": "NET-RTR-1",
"type" : "DIRECT ALLOCATION", "type" : "DIRECT ALLOCATION",
"country" : "AU", "country" : "AU",
"parentHandle" : "YYYY-RIR", "parentHandle" : "YYYY-RIR",
skipping to change at line 2060 skipping to change at line 2129
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z" "eventDate" : "1991-12-31T23:59:59Z"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.4-6">
The IP network object class can contain the following members:</t> The IP network object class can contain the following members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
<t><list style="symbols"><t>objectClassName -- the string "ip network"</t .4-7">
> <li pn="section-5.4-7.1">objectClassName -- the string "ip network"</l
i>
<t>handle -- a string representing the RIR-unique identifier of the <li pn="section-5.4-7.2">handle -- a string representing the RIR-uniqu
network registration</t> e identifier of the
network registration</li>
<t>startAddress -- a string representing the starting IP address of the n <li pn="section-5.4-7.3">startAddress -- a string representing the sta
etwork, either rting IP address of the network, either
IPv4 or IPv6</t> IPv4 or IPv6</li>
<li pn="section-5.4-7.4">endAddress -- a string representing the endin
<t>endAddress -- a string representing the ending IP address of the netwo g IP address of the network, either IPv4 or
rk, either IPv4 or IPv6</li>
IPv6</t> <li pn="section-5.4-7.5">ipVersion -- a string signifying the IP proto
col version of the
<t>ipVersion -- a string signifying the IP protocol version of the
network: "v4" signifies an IPv4 network, and "v6" signifies an network: "v4" signifies an IPv4 network, and "v6" signifies an
IPv6 network</t> IPv6 network</li>
<li pn="section-5.4-7.6">name -- a string representing an identifier a
<t>name -- a string representing an identifier assigned to the network re ssigned to the network registration by the
gistration by the registration holder</li>
registration holder</t> <li pn="section-5.4-7.7">type -- a string containing an RIR-specific c
lassification of the
<t>type -- a string containing an RIR-specific classification of the network per that RIR's registration model
network as per that RIR's registration model </li>
</t> <li pn="section-5.4-7.8">country -- a string containing the two-charac
ter country code of
<t>country -- a string containing the two-character country code of the network</li>
the network</t> <li pn="section-5.4-7.9">parentHandle -- a string containing an RIR-un
ique identifier of
<t>parentHandle -- a string containing an RIR-unique identifier of the parent network of this network registration</li>
the parent network of this network registration</t> <li pn="section-5.4-7.10">status -- an array of strings indicating the
state of the IP
<t>status -- an array of strings indicating the state of the IP network as defined by <xref target="sect-4.6" format="default" sectionForm
network as defined by <xref target="sect-4.6"/></t> at="of" derivedContent="Section 4.6"/></li>
<li pn="section-5.4-7.11">entities -- an array of entity objects as de
<t>entities -- an array of entity objects as defined by <xref target="sec fined by <xref target="sect-5.1" format="default" sectionFormat="of" derivedCont
t-5.1"/> ent="Section 5.1"/>
</t> </li>
<li pn="section-5.4-7.12">remarks -- see <xref target="sect-4.3" forma
<t>remarks -- see <xref target="sect-4.3"/> t="default" sectionFormat="of" derivedContent="Section 4.3"/>
</t> </li>
<li pn="section-5.4-7.13">links -- see <xref target="sect-4.2" format=
<t>links -- see <xref target="sect-4.2"/> "default" sectionFormat="of" derivedContent="Section 4.2"/>
</t> </li>
<li pn="section-5.4-7.14">port43 -- see <xref target="sect-4.7" format
<t>port43 -- see <xref target="sect-4.7"/> ="default" sectionFormat="of" derivedContent="Section 4.7"/>
</t> </li>
<li pn="section-5.4-7.15">events -- see <xref target="sect-4.5" format
<t>events -- see <xref target="sect-4.5"/> ="default" sectionFormat="of" derivedContent="Section 4.5"/>
</t> </li>
</ul>
</list> </section>
</t> <section anchor="sect-5.5" numbered="true" toc="include" removeInRFC="fals
e" pn="section-5.5">
</section> <name slugifiedName="name-the-autonomous-system-numbe">The Autonomous Sy
stem Number Object Class</name>
<section title="The Autonomous System Number Object Class" anchor="sect-5 <t indent="0" pn="section-5.5-1">
.5"><t>
The Autonomous System number (autnum) object class models Autonomous The Autonomous System number (autnum) object class models Autonomous
System number registrations found in RIRs and represents the expected System number registrations found in RIRs and represents the expected
response to an "/autnum" query as defined by <xref target="I-D.ietf-regext-rf c7482bis"/>. There is no response to an "/autnum" query as defined by <xref target="RFC9082" format="d efault" sectionFormat="of" derivedContent="RFC9082"/>. There is no
equivalent object class for DNRs. The high-level structure of the equivalent object class for DNRs. The high-level structure of the
autnum object class consists of information about the autonomous system numbe r autnum object class consists of information about the Autonomous System numbe r
registration and entities related to the autnum registration (e.g., registration and entities related to the autnum registration (e.g.,
registrant information, contacts, etc.) and is similar to the IP registrant information, contacts, etc.) and is similar to the IP
network object class.</t> network object class.</t>
<t indent="0" pn="section-5.5-2">
<t>
The following is an example of a JSON object representing an autnum.</t> The following is an example of a JSON object representing an autnum.</t>
<figure anchor="ure-27" align="left" suppress-title="false" pn="figure-2
<figure anchor="ure-27"><artwork><![CDATA[ 7">
<sourcecode type="json" markers="false" pn="section-5.5-3.1">
{ {
"objectClassName" : "autnum", "objectClassName" : "autnum",
"handle" : "XXXX-RIR", "handle" : "XXXX-RIR",
"startAutnum" : 65536, "startAutnum" : 65536,
"endAutnum" : 65541, "endAutnum" : 65541,
"name": "AS-RTR-1", "name": "AS-RTR-1",
"type" : "DIRECT ALLOCATION", "type" : "DIRECT ALLOCATION",
"status" : [ "active" ], "status" : [ "active" ],
"country": "AU", "country": "AU",
"remarks" : "remarks" :
skipping to change at line 2249 skipping to change at line 2301
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z" "eventDate" : "1991-12-31T23:59:59Z"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-5.5-4">
The Autonomous System number object class can contain the following The Autonomous System number object class can contain the following
members:</t> members:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-5
<t><list style="symbols"><t>objectClassName -- the string "autnum"</t> .5-5">
<li pn="section-5.5-5.1">objectClassName -- the string "autnum"</li>
<t>handle -- a string representing the RIR-unique identifier of the <li pn="section-5.5-5.2">handle -- a string representing the RIR-uniqu
autnum registration</t> e identifier of the
autnum registration</li>
<t>startAutnum -- an unsigned 32-bit integer representing the starting nu <li pn="section-5.5-5.3">startAutnum -- an unsigned 32-bit integer rep
mber <xref target="RFC5396"/> resenting the starting number <xref target="RFC5396" format="default" sectionFor
in the block of Autonomous System numbers</t> mat="of" derivedContent="RFC5396"/>
in the block of Autonomous System numbers</li>
<t>endAutnum -- an unsigned 32-bit integer representing the ending number <li pn="section-5.5-5.4">endAutnum -- an unsigned 32-bit integer repre
<xref target="RFC5396"/> in senting the ending number <xref target="RFC5396" format="default" sectionFormat=
the block of Autonomous System numbers</t> "of" derivedContent="RFC5396"/> in
the block of Autonomous System numbers</li>
<t>name -- a string representing an identifier assigned to the autnum reg <li pn="section-5.5-5.5">name -- a string representing an identifier a
istration by the ssigned to the autnum registration by the
registration holder</t> registration holder</li>
<li pn="section-5.5-5.6">type -- a string containing an RIR-specific c
<t>type -- a string containing an RIR-specific classification of the lassification of the
autnum as per that RIR's registration model</t> autnum per that RIR's registration model</li>
<li pn="section-5.5-5.7">status -- an array of strings indicating the
<t>status -- an array of strings indicating the state of the autnum as de state of the autnum as defined by <xref target="sect-4.6" format="default" secti
fined by <xref target="sect-4.6"/></t> onFormat="of" derivedContent="Section 4.6"/></li>
<li pn="section-5.5-5.8">country -- a string containing the two-charac
<t>country -- a string containing the two-character country ter country
code of the autnum</t> code of the autnum</li>
<li pn="section-5.5-5.9">entities -- an array of entity objects as def
<t>entities -- an array of entity objects as defined by <xref target="sec ined by <xref target="sect-5.1" format="default" sectionFormat="of" derivedConte
t-5.1"/> nt="Section 5.1"/>
</t> </li>
<li pn="section-5.5-5.10">remarks -- see <xref target="sect-4.3" forma
<t>remarks -- see <xref target="sect-4.3"/> t="default" sectionFormat="of" derivedContent="Section 4.3"/>
</t> </li>
<li pn="section-5.5-5.11">links -- see <xref target="sect-4.2" format=
<t>links -- see <xref target="sect-4.2"/> "default" sectionFormat="of" derivedContent="Section 4.2"/>
</t> </li>
<li pn="section-5.5-5.12">port43 -- see <xref target="sect-4.7" format
<t>port43 -- see <xref target="sect-4.7"/> ="default" sectionFormat="of" derivedContent="Section 4.7"/>
</t> </li>
<li pn="section-5.5-5.13">events -- see <xref target="sect-4.5" format
<t>events -- see <xref target="sect-4.5"/> ="default" sectionFormat="of" derivedContent="Section 4.5"/>
</t> </li>
</ul>
</list> </section>
</t> </section>
<section anchor="sect-6" numbered="true" toc="include" removeInRFC="false" p
</section> n="section-6">
<name slugifiedName="name-error-response-body">Error Response Body</name>
</section> <t indent="0" pn="section-6-1">
Some non-answer responses <bcp14>MAY</bcp14> return entity bodies with inform
<section title="Error Response Body" anchor="sect-6"><t> ation
Some non-answer responses MAY return entity bodies with information
that could be more descriptive.</t> that could be more descriptive.</t>
<t indent="0" pn="section-6-2">
<t>
The basic structure of that response is an object class containing a The basic structure of that response is an object class containing a
REQUIRED error code number (corresponding to the HTTP response code) followed <bcp14>REQUIRED</bcp14> error code number (corresponding to the HTTP response
by an OPTIONAL string named "title" and an OPTIONAL array of strings named code) followed
by an <bcp14>OPTIONAL</bcp14> string named "title" and an <bcp14>OPTIONAL</bc
p14> array of strings named
"description".</t> "description".</t>
<t indent="0" pn="section-6-3">
<t>
This is an example of the common response body.</t> This is an example of the common response body.</t>
<figure anchor="ure-28" align="left" suppress-title="false" pn="figure-28"
<figure anchor="ure-28"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-6-4.1">
{ {
"errorCode": 418, "errorCode": 418,
"title": "Your Beverage Choice is Not Available", "title": "Your Beverage Choice is Not Available",
"description": "description":
[ [
"I know coffee has more ummppphhh.", "I know coffee has more ummppphhh.",
"Sorry, dude!" "Sorry, dude!"
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-6-5">
This is an example of the common response body with an This is an example of the common response body with an
rdapConformance and notices data structures:</t> rdapConformance and notices data structures:</t>
<figure anchor="ure-29" align="left" suppress-title="false" pn="figure-29"
<figure anchor="ure-29"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-6-6.1">
{ {
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
], ],
"notices" : "notices" :
[ [
{ {
"title" : "Beverage Policy", "title" : "Beverage Policy",
"description" : "description" :
skipping to change at line 2362 skipping to change at line 2397
], ],
"lang" : "en", "lang" : "en",
"errorCode": 418, "errorCode": 418,
"title": "Your beverage choice is not available", "title": "Your beverage choice is not available",
"description": "description":
[ [
"I know coffee has more ummppphhh.", "I know coffee has more ummppphhh.",
"Sorry, dude!" "Sorry, dude!"
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-7" numbered="true" toc="include" removeInRFC="false" p
<section title="Responding to Help Queries" anchor="sect-7"><t> n="section-7">
The appropriate response to /help queries as defined by <xref target="I-D.iet <name slugifiedName="name-responding-to-help-queries">Responding to Help Q
f-regext-rfc7482bis"/> is ueries</name>
to use the notices structure as defined in <xref target="sect-4.3"/>.</t> <t indent="0" pn="section-7-1">
The appropriate response to /help queries as defined by <xref target="RFC9082
<t> " format="default" sectionFormat="of" derivedContent="RFC9082"/> is
to use the notices structure as defined in <xref target="sect-4.3" format="de
fault" 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 This is an example of a response to a /help query including the
rdapConformance data structure.</t> rdapConformance data structure.</t>
<figure anchor="ure-30" align="left" suppress-title="false" pn="figure-30"
<figure anchor="ure-30"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-7-3.1">
{ {
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
], ],
"notices" : "notices" :
[ [
{ {
"title" : "Authentication Policy", "title" : "Authentication Policy",
"description" : "description" :
skipping to change at line 2400 skipping to change at line 2435
{ {
"value" : "https://example.net/help", "value" : "https://example.net/help",
"rel" : "alternate", "rel" : "alternate",
"type" : "text/html", "type" : "text/html",
"href" : "https://www.example.com/auth_policy.html" "href" : "https://www.example.com/auth_policy.html"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-8" numbered="true" toc="include" removeInRFC="false" p
<section title="Responding To Searches" anchor="sect-8"><t> n="section-8">
<xref target="I-D.ietf-regext-rfc7482bis"/> specifies three types of searches <name slugifiedName="name-responding-to-searches">Responding To Searches</
: domains, nameservers, name>
<t indent="0" pn="section-8-1">
<xref target="RFC9082" format="default" sectionFormat="of" derivedContent="RF
C9082"/> specifies three types of searches: domains, nameservers,
and entities. Responses to these searches take the form of an array and entities. Responses to these searches take the form of an array
of object instances where each instance is an appropriate object of object instances where each instance is an appropriate object
class for the search (i.e., a search for /domains yields an array of class for the search (i.e., a search for /domains yields an array of
domain object instances). These arrays are contained within the domain object instances). These arrays are contained within the
response object.</t> response object.</t>
<t indent="0" pn="section-8-2">
<t>
The names of the arrays are as follows:</t> The names of the arrays are as follows:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-8-3
<t><list style="symbols"><t>for /domains searches, the array is "domainSe ">
archResults"</t> <li pn="section-8-3.1">for /domains searches, the array is "domainSearch
Results"</li>
<t>for /nameservers searches, the array is "nameserverSearchResults"</t> <li pn="section-8-3.2">for /nameservers searches, the array is "nameserv
erSearchResults"</li>
<t>for /entities searches, the array is "entitySearchResults"</t> <li pn="section-8-3.3">for /entities searches, the array is "entitySearc
hResults"</li>
</list> </ul>
</t> <t indent="0" pn="section-8-4">
<t>
The following is an elided example of a response to a /domains The following is an elided example of a response to a /domains
search.</t> search.</t>
<figure anchor="ure-31" align="left" suppress-title="false" pn="figure-31"
<figure anchor="ure-31"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-8-5.1">
{ {
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
], ],
... ...
"domainSearchResults" : "domainSearchResults" :
[ [
{ {
"objectClassName" : "domain", "objectClassName" : "domain",
skipping to change at line 2451 skipping to change at line 2481
... ...
}, },
{ {
"objectClassName" : "domain", "objectClassName" : "domain",
"handle" : "2-XXXX", "handle" : "2-XXXX",
"ldhName" : "2.example.com", "ldhName" : "2.example.com",
... ...
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-9" numbered="true" toc="include" removeInRFC="false" p
<section title="Indicating Truncated Responses" anchor="sect-9"><t> n="section-9">
<name slugifiedName="name-indicating-truncated-respon">Indicating Truncate
d Responses</name>
<t indent="0" pn="section-9-1">
In cases where the data of a response needs to be limited or parts of 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". 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 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 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 server. A server may indicate this by including a typed notice in
the response object.</t> the response object.</t>
<t indent="0" pn="section-9-2">
<t>
The following is an elided example of a search response that has been The following is an elided example of a search response that has been
truncated.</t> truncated.</t>
<figure anchor="ure-32" align="left" suppress-title="false" pn="figure-32"
<figure anchor="ure-32"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-9-3.1">
{ {
"rdapConformance" : "rdapConformance" :
[ [
"rdap_level_0" "rdap_level_0"
], ],
"notices" : "notices" :
[ [
{ {
"title" : "Search Policy", "title" : "Search Policy",
"type" : "result set truncated due to authorization", "type" : "result set truncated due to authorization",
skipping to change at line 2498 skipping to change at line 2528
"href" : "https://www.example.com/search_policy.html" "href" : "https://www.example.com/search_policy.html"
} }
] ]
} }
], ],
"domainSearchResults" : "domainSearchResults" :
[ [
... ...
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-9-4">
A similar technique can be used with a typed remark where a single 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. 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 Such an example might be an entity object with only a partial set of
the IP networks associated with it.</t> the IP networks associated with it.</t>
<t indent="0" pn="section-9-5">
<t>
The following is an elided example of an entity truncated data.</t> The following is an elided example of an entity truncated data.</t>
<figure anchor="ure-33" align="left" suppress-title="false" pn="figure-33"
<figure anchor="ure-33"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-9-6.1">
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle" : "ANENTITY", "handle" : "ANENTITY",
"roles" : [ "registrant" ], "roles" : [ "registrant" ],
... ...
"entities" : "entities" :
[ [
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle": "ANEMBEDDEDENTITY", "handle": "ANEMBEDDEDENTITY",
skipping to change at line 2551 skipping to change at line 2580
{ {
"value" : "https://example.net/help", "value" : "https://example.net/help",
"rel" : "alternate", "rel" : "alternate",
"type" : "text/html", "type" : "text/html",
"href" : "https://www.example.com/data_policy.html" "href" : "https://www.example.com/data_policy.html"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-10" numbered="true" toc="include" removeInRFC="false"
<section title="IANA Considerations" anchor="sect-10"> pn="section-10">
<t>IANA is requested to update the description of the "transfer" event <name slugifiedName="name-iana-considerations">IANA Considerations</name>
action as described in <xref target="sect-10.2.3"/>.</t> <t indent="0" pn="section-10-1">IANA has updated the description of the "t
ransfer" event action as described in <xref target="sect-10.2.3" format="default
<section title="RDAP JSON Media Type Registration" anchor="sect-10.1"> " sectionFormat="of" derivedContent="Section 10.2.3"/>.</t>
<t>IANA is requested to update the media type registration as described b <section anchor="sect-10.1" numbered="true" toc="include" removeInRFC="fal
elow.</t> se" pn="section-10.1">
<t><list style="hanging" hangIndent="3"><t hangText="This specification r <name slugifiedName="name-rdap-json-media-type-regist">RDAP JSON Media T
egisters the &quot;application/rdap+json&quot; media type."> ype Registration</name>
<vspace blankLines="1"/> <t indent="0" pn="section-10.1-1">IANA has updated the media type regist
Type name: application ration as described below.</t>
<vspace blankLines="1"/> <t indent="0" pn="section-10.1-2">This specification registers the "appl
Subtype name: rdap+json ication/rdap+json" media type.</t>
<vspace blankLines="1"/> <dl indent="3" newline="false" spacing="normal" pn="section-10.1-3">
Required parameters: n/a <dt pn="section-10.1-3.1">
<vspace blankLines="1"/> Type name:</dt>
Encoding considerations: See Section 3.1 of <xref target="RFC6839"/>. <dd pn="section-10.1-3.2"> application
<vspace blankLines="1"/> </dd>
Security considerations: The media represented by this identifier <dt pn="section-10.1-3.3">
Subtype name:</dt>
<dd pn="section-10.1-3.4"> rdap+json
</dd>
<dt pn="section-10.1-3.5">
Required parameters:</dt>
<dd pn="section-10.1-3.6"> n/a
</dd>
<dt pn="section-10.1-3.7">
Encoding considerations:</dt>
<dd pn="section-10.1-3.8"> See <xref target="RFC6839" section="3.1" se
ctionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc683
9#section-3.1" derivedContent="RFC6839"/>.
</dd>
<dt pn="section-10.1-3.9">
Security considerations:</dt>
<dd pn="section-10.1-3.10">The media represented by this identifier
does not have security considerations beyond that found in does not have security considerations beyond that found in
Section 12 of <xref target="RFC8259"/>. <xref target="RFC8259" section="12" sectionFormat="of" format="default" de
<vspace blankLines="1"/> rivedLink="https://rfc-editor.org/rfc/rfc8259#section-12" derivedContent="RFC825
Interoperability considerations: There are no known 9"/>.
</dd>
<dt pn="section-10.1-3.11">
Interoperability considerations:</dt>
<dd pn="section-10.1-3.12"> There are no known
interoperability problems regarding this media format. interoperability problems regarding this media format.
<vspace blankLines="1"/> </dd>
Published specification: RFC &lt;this new RFC number&gt; <dt pn="section-10.1-3.13">
<vspace blankLines="1"/> Published specification:</dt>
Applications that use this media type: Implementations of the <dd pn="section-10.1-3.14"> RFC 9083
</dd>
<dt pn="section-10.1-3.15">
Applications that use this media type:</dt>
<dd pn="section-10.1-3.16"> Implementations of the
Registration Data Access Protocol (RDAP). Registration Data Access Protocol (RDAP).
<vspace blankLines="1"/> </dd>
Additional information: This media type is a product of the IETF <dt pn="section-10.1-3.17">
REGEXT working group. The REGEXT charter, information on the Additional information:</dt>
<dd pn="section-10.1-3.18"> This media type is a product of the IETF
REGEXT Working Group. The REGEXT charter, information on the
REGEXT mailing list, and other documents produced by the REGEXT REGEXT mailing list, and other documents produced by the REGEXT
working group can be found at Working Group can be found at
<eref target="https://datatracker.ietf.org/wg/regext/"/>. <eref target="https://datatracker.ietf.org/wg/regext/" brackets="none"/>.
<vspace blankLines="1"/> </dd>
Person &amp; email address to contact for further information: IESG <dt pn="section-10.1-3.19">
Person &amp; email address to contact for further information:</dt>
<dd pn="section-10.1-3.20">
<br/>IESG
&lt;iesg@ietf.org&gt; &lt;iesg@ietf.org&gt;
<vspace blankLines="1"/> </dd>
Intended usage: COMMON <dt pn="section-10.1-3.21">
<vspace blankLines="1"/> Intended usage:</dt>
Restrictions on usage: none <dd pn="section-10.1-3.22"> COMMON
<vspace blankLines="1"/> </dd>
Author: Andy Newton <dt pn="section-10.1-3.23">
<vspace blankLines="1"/> Restrictions on usage:</dt>
Change controller: IETF <dd pn="section-10.1-3.24"> none
<vspace blankLines="1"/> </dd>
Provisional Registration: No (upon publication of this RFC) <dt pn="section-10.1-3.25">
</t> Author:</dt>
<dd pn="section-10.1-3.26"> Andy Newton
</list> </dd>
</t> <dt pn="section-10.1-3.27">
Change controller:</dt>
</section> <dd pn="section-10.1-3.28"> IETF
</dd>
<section title="JSON Values Registry" anchor="sect-10.2"><t> <dt pn="section-10.1-3.29">
Provisional Registration:</dt>
<dd pn="section-10.1-3.30"> No
</dd>
</dl>
</section>
<section anchor="sect-10.2" numbered="true" toc="include" removeInRFC="fal
se" pn="section-10.2">
<name slugifiedName="name-json-values-registry">JSON Values Registry</na
me>
<t indent="0" pn="section-10.2-1">
IANA has created a category in the protocol registries labeled IANA has created a category in the protocol registries labeled
"Registration Data Access Protocol (RDAP)", and within that category, "Registration Data Access Protocol (RDAP)", and within that category,
IANA has established a URL-referenceable, stand-alone registry IANA has established a URL-referenceable, stand-alone registry
labeled "RDAP JSON Values". This new registry is for use in the labeled "RDAP JSON Values". This new registry is for use in the
notices and remarks (<xref target="sect-4.3"/>), status (<xref target="sect-4 notices and remarks (<xref target="sect-4.3" format="default" sectionFormat="
.6"/>), role of" derivedContent="Section 4.3"/>), status (<xref target="sect-4.6" format="def
(<xref target="sect-5.1"/>), event action (<xref target="sect-4.5"/>), and do ault" sectionFormat="of" derivedContent="Section 4.6"/>), role
main variant (<xref target="sect-5.1" format="default" sectionFormat="of" derivedContent="
relation (<xref target="sect-5.3"/>) fields specified in RDAP.</t> Section 5.1"/>), event action (<xref target="sect-4.5" format="default" sectionF
ormat="of" derivedContent="Section 4.5"/>), and domain variant
<t> relation (<xref target="sect-5.3" format="default" sectionFormat="of" derived
Content="Section 5.3"/>) fields specified in RDAP.</t>
<t indent="0" pn="section-10.2-2">
Each entry in the registry contains the following fields:</t> Each entry in the registry contains the following fields:</t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-10
<t><list style="numbers"><t>Value -- the string value being registered.</ .2-3"><li pn="section-10.2-3.1" derivedCounter="1.">Value -- the string value be
t> ing registered.</li>
<li pn="section-10.2-3.2" derivedCounter="2.">
<t>Type -- the type of value being registered. It should be one of <t indent="0" pn="section-10.2-3.2.1">Type -- the type of value bein
the following:<list style="symbols"><t>"notice or remark type" -- denotes g registered. It should be one of
a type of notice or remark.</t> the following:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="secti
<t>"status" -- denotes a value for the "status" object member as on-10.2-3.2.2">
defined by <xref target="sect-4.6"/>.</t> <li pn="section-10.2-3.2.2.1">"notice or remark type" -- denotes a
type of notice or remark.</li>
<t>"role" -- denotes a value for the "role" array as defined in <li pn="section-10.2-3.2.2.2">"status" -- denotes a value for the
<xref target="sect-5.1"/>.</t> "status" object member as
defined by <xref target="sect-4.6" format="default" sectionFormat="of"
<t>"event action" -- denotes a value for an event action as derivedContent="Section 4.6"/>.</li>
defined in <xref target="sect-4.5"/>.</t> <li pn="section-10.2-3.2.2.3">"role" -- denotes a value for the "r
ole" array as defined in
<t>"domain variant relation" -- denotes a relationship between a <xref target="sect-5.1" format="default" sectionFormat="of" derivedCon
domain and a domain variant as defined in <xref target="sect-5.3"/>.</ tent="Section 5.1"/>.</li>
t> <li pn="section-10.2-3.2.2.4">"event action" -- denotes a value fo
r an event action as
</list> defined in <xref target="sect-4.5" format="default" sectionFormat="of"
</t> derivedContent="Section 4.5"/>.</li>
<li pn="section-10.2-3.2.2.5">"domain variant relation" -- denotes
<t>Description -- a one- or two-sentence description regarding the a relationship between a
domain and a domain variant as defined in <xref target="sect-5.3" form
at="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 meaning of the value, how it might be used, and/or how it should
be interpreted by clients.</t> be interpreted by clients.</li>
<li pn="section-10.2-3.4" derivedCounter="4.">Registrant Name -- the n
<t>Registrant Name -- the name of the person registering the value.</t> ame of the person registering the value.</li>
<li pn="section-10.2-3.5" derivedCounter="5.">Registrant Contact Infor
<t>Registrant Contact Information -- an email address, postal mation -- an email address, postal
address, or some other information to be used to contact the address, or some other information to be used to contact the
registrant.</t> registrant.</li>
</ol>
</list> <t indent="0" pn="section-10.2-4">
</t>
<t>
This registry is operated under the "Expert Review" policy defined in This registry is operated under the "Expert Review" policy defined in
<xref target="RFC8126"/>.</t> <xref target="RFC8126" format="default" sectionFormat="of" derivedContent="RF
C8126"/>.</t>
<t> <t indent="0" pn="section-10.2-5">
Review of registrations into this registry by the designated Review of registrations into this registry by the designated
expert(s) should be narrowly judged on the following criteria:</t> expert(s) should be narrowly judged on the following criteria:</t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-10
<t><list style="numbers"><t>Values in need of being placed into multiple .2-6"><li pn="section-10.2-6.1" derivedCounter="1.">Values in need of being plac
types must be ed into multiple types must be
assigned a separate registration for each type.</t> assigned a separate registration for each type.</li>
<li pn="section-10.2-6.2" derivedCounter="2.">Values must be strings.
<t>Values must be strings. They should be multiple words separated They should be multiple words separated
by single space characters. Every character should be by single space characters. Every character should be
lowercased. If possible, every word should be given in English lowercased. If possible, every word should be given in English
and each character should be US-ASCII.</t> and each character should be US-ASCII.</li>
<li pn="section-10.2-6.3" derivedCounter="3.">Registrations should not
<t>Registrations should not duplicate the meaning of any existing duplicate the meaning of any existing
registration. That is, if a request for a registration is registration. That is, if a request for a registration is
significantly similar in nature to an existing registration, the significantly similar in nature to an existing registration, the
request should be denied. For example, the terms "maintainer" request should be denied. For example, the terms "maintainer"
and "registrant" are significantly similar in nature as they both and "registrant" are significantly similar in nature as they both
denote a holder of a domain name or Internet number resource. In denote a holder of a domain name or Internet number resource. In
cases where it may be reasonably argued that machine cases where it may be reasonably argued that machine
interpretation of two similar values may alter the operation of interpretation of two similar values may alter the operation of
client software, designated experts should not judge the values client software, designated experts should not judge the values
to be of significant similarity.</t> to be of significant similarity.</li>
<li pn="section-10.2-6.4" derivedCounter="4.">Registrations should be
<t>Registrations should be relevant to the common usages of RDAP. relevant to the common usages of RDAP.
Designated experts may rely upon the serving of the value by a Designated experts may rely upon the serving of the value by a
DNR or RIR to make this determination.</t> DNR or RIR to make this determination.</li>
</ol>
</list> <t indent="0" pn="section-10.2-7">
</t>
<t>
The following sections provide initial registrations into this The following sections provide initial registrations into this
registry.</t> registry.</t>
<section anchor="sect-10.2.1" numbered="true" toc="include" removeInRFC=
<section title="Notice and Remark Types" anchor="sect-10.2.1"><t> "false" pn="section-10.2.1">
<name slugifiedName="name-notice-and-remark-types">Notice and Remark T
ypes</name>
<t indent="0" pn="section-10.2.1-1">
The following values have been registered in the "RDAP JSON Values" The following values have been registered in the "RDAP JSON Values"
registry:</t> registry:</t>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-2"
<list style="none"> >
<t>Value: result set truncated due to author <dt pn="section-10.2.1-2.1">Value:</dt>
ization<vspace blankLines="0"/> <dd pn="section-10.2.1-2.2">result set truncated due to authorizatio
Type: notice and remark type<vspace blankLin n</dd>
es="0"/> <dt pn="section-10.2.1-2.3">Type:</dt>
Description: The list of results does not co <dd pn="section-10.2.1-2.4">notice and remark type</dd>
ntain all results due to lack of authorization. <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 tha t proper authorization will yield a longer result This may indicate to some clients tha t proper authorization will yield a longer result
set.<vspace blankLines="0"/> set.</dd>
Registrant Name: IESG<vspace blankLines="0"/ <dt pn="section-10.2.1-2.7">Registrant Name:</dt>
> <dd pn="section-10.2.1-2.8">IESG</dd>
Registrant Contact Information: iesg@ietf.or <dt pn="section-10.2.1-2.9">Registrant Contact Information:</dt>
g</t> <dd pn="section-10.2.1-2.10">iesg@ietf.org</dd>
</list> </dl>
</t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-3"
<t> >
<list style="none"> <dt pn="section-10.2.1-3.1">Value:</dt>
<t>Value: result set truncated due to excess <dd pn="section-10.2.1-3.2">result set truncated due to excessive lo
ive load<vspace blankLines="0"/> ad</dd>
Type: notice and remark type<vspace blankLin <dt pn="section-10.2.1-3.3">Type:</dt>
es="0"/> <dd pn="section-10.2.1-3.4">notice and remark type</dd>
Description: The list of results does not co <dt pn="section-10.2.1-3.5">Description:</dt>
ntain all results due to excessively heavy load on the server. <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 r equerying at a later time will yield a longer result This may indicate to some clients that r equerying at a later time will yield a longer result
set.<vspace blankLines="0"/> set.</dd>
Registrant Name: IESG<vspace blankLines="0"/ <dt pn="section-10.2.1-3.7">Registrant Name:</dt>
> <dd pn="section-10.2.1-3.8">IESG</dd>
Registrant Contact Information: iesg@ietf.or <dt pn="section-10.2.1-3.9">Registrant Contact Information:</dt>
g</t> <dd pn="section-10.2.1-3.10">iesg@ietf.org</dd>
</list> </dl>
</t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-4"
<t> >
<list style="none"> <dt pn="section-10.2.1-4.1">Value:</dt>
<t>Value: result set truncated due to unexpl <dd pn="section-10.2.1-4.2">result set truncated due to unexplainabl
ainable reasons<vspace blankLines="0"/> e reasons</dd>
Type: notice and remark type<vspace blankLin <dt pn="section-10.2.1-4.3">Type:</dt>
es="0"/> <dd pn="section-10.2.1-4.4">notice and remark type</dd>
Description: The list of results does not co <dt pn="section-10.2.1-4.5">Description:</dt>
ntain all results for an unexplainable reason. <dd pn="section-10.2.1-4.6">The list of results does not contain all
This may indicate to some clients that r results for an unexplainable reason.
equerying for any reason will not yield a longer result set.<vspace blankLines=" This may indicate to some clients that r
0"/> equerying for any reason will not yield a longer result set.</dd>
Registrant Name: IESG<vspace blankLines="0"/ <dt pn="section-10.2.1-4.7">Registrant Name:</dt>
> <dd pn="section-10.2.1-4.8">IESG</dd>
Registrant Contact Information: iesg@ietf.or <dt pn="section-10.2.1-4.9">Registrant Contact Information:</dt>
g</t> <dd pn="section-10.2.1-4.10">iesg@ietf.org</dd>
</list> </dl>
</t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-5"
<t> >
<list style="none"> <dt pn="section-10.2.1-5.1">Value:</dt>
<t>Value: object truncated due to authorizat <dd pn="section-10.2.1-5.2">object truncated due to authorization</d
ion<vspace blankLines="0"/> d>
Type: notice and remark type<vspace blankLin <dt pn="section-10.2.1-5.3">Type:</dt>
es="0"/> <dd pn="section-10.2.1-5.4">notice and remark type</dd>
Description: The object does not contain all <dt pn="section-10.2.1-5.5">Description:</dt>
data due to lack of authorization.<vspace blankLines="0"/> <dd pn="section-10.2.1-5.6">The object does not contain all data due
Registrant Name: IESG<vspace blankLines="0"/ to lack of authorization.</dd>
> <dt pn="section-10.2.1-5.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.or <dd pn="section-10.2.1-5.8">IESG</dd>
g</t> <dt pn="section-10.2.1-5.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.1-5.10">iesg@ietf.org</dd>
</t> </dl>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-6"
<list style="none"> >
<t>Value: object truncated due to excessive <dt pn="section-10.2.1-6.1">Value:</dt>
load<vspace blankLines="0"/> <dd pn="section-10.2.1-6.2">object truncated due to excessive load</
Type: notice and remark type<vspace blankLin dd>
es="0"/> <dt pn="section-10.2.1-6.3">Type:</dt>
Description: The object does not contain all <dd pn="section-10.2.1-6.4">notice and remark type</dd>
data due to excessively heavy load on the server. <dt pn="section-10.2.1-6.5">Description:</dt>
This may indicate to some clients that r <dd pn="section-10.2.1-6.6">The object does not contain all data due
equerying at a later time will yield all data of the object.<vspace blankLines=" to an excessively heavy load on the server.
0"/> This may indicate to some clients that re
Registrant Name: IESG<vspace blankLines="0"/ querying at a later time will yield all data of the object.</dd>
> <dt pn="section-10.2.1-6.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.or <dd pn="section-10.2.1-6.8">IESG</dd>
g</t> <dt pn="section-10.2.1-6.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.1-6.10">iesg@ietf.org</dd>
</t> </dl>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.1-7"
<list style="none"> >
<t>Value: object truncated due to unexplaina <dt pn="section-10.2.1-7.1">Value:</dt>
ble reasons<vspace blankLines="0"/> <dd pn="section-10.2.1-7.2">object truncated due to unexplainable re
Type: notice and remark type<vspace blankLin asons</dd>
es="0"/> <dt pn="section-10.2.1-7.3">Type:</dt>
Description: The object does not contain all <dd pn="section-10.2.1-7.4">notice and remark type</dd>
data for an unexplainable reason.<vspace blankLines="0"/> <dt pn="section-10.2.1-7.5">Description:</dt>
Registrant Name: IESG<vspace blankLines="0"/ <dd pn="section-10.2.1-7.6">The object does not contain all data for
> an unexplainable reason.</dd>
Registrant Contact Information: iesg@ietf.or <dt pn="section-10.2.1-7.7">Registrant Name:</dt>
g</t> <dd pn="section-10.2.1-7.8">IESG</dd>
</list> <dt pn="section-10.2.1-7.9">Registrant Contact Information:</dt>
</t> <dd pn="section-10.2.1-7.10">iesg@ietf.org</dd>
</section> </dl>
</section>
<section title="Status" anchor="sect-10.2.2"> <section anchor="sect-10.2.2" numbered="true" toc="include" removeInRFC=
<t>The following values have been registered in the "RDAP JSON Values" re "false" pn="section-10.2.2">
gistry:</t> <name slugifiedName="name-status-2">Status</name>
<t> <t indent="0" pn="section-10.2.2-1">The following values have been reg
<list style="none"> istered in the "RDAP JSON Values" registry:</t>
<t>Value: validated<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-2"
Type: status<vspace blankLines="0"/> >
Description: Signifies that the data of the obje <dt pn="section-10.2.2-2.1">Value:</dt>
ct instance has been <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 in
stance has been
found to be accurate. This type of status is usually found on entity found to be accurate. This type of status is usually found on entity
object instances to note the validity of ide ntifying contact object instances to note the validity of ide ntifying contact
information.<vspace blankLines="0"/> information.</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.2-2.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.2-2.8">IESG</dd>
> <dt pn="section-10.2.2-2.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.2-2.10">iesg@ietf.org</dd>
</t> </dl>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-3"
<list style="none"> >
<t>Value: renew prohibited<vspace blankLines="0" <dt pn="section-10.2.2-3.1">Value:</dt>
/> <dd pn="section-10.2.2-3.2">renew prohibited</dd>
Type: status<vspace blankLines="0"/> <dt pn="section-10.2.2-3.3">Type:</dt>
Description: Renewal or reregistration of the ob <dd pn="section-10.2.2-3.4">status</dd>
ject instance is forbidden.<vspace blankLines="0"/> <dt pn="section-10.2.2-3.5">Description:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.2-3.6">Renewal or reregistration of the object
Registrant Contact Information: iesg@ietf.org</t instance is forbidden.</dd>
> <dt pn="section-10.2.2-3.7">Registrant Name:</dt>
</list> <dd pn="section-10.2.2-3.8">IESG</dd>
</t> <dt pn="section-10.2.2-3.9">Registrant Contact Information:</dt>
<t> <dd pn="section-10.2.2-3.10">iesg@ietf.org</dd>
<list style="none"> </dl>
<t>Value: update prohibited<vspace blankLines="0 <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-4"
"/> >
Type: status<vspace blankLines="0"/> <dt pn="section-10.2.2-4.1">Value:</dt>
Description: Updates to the object instance are <dd pn="section-10.2.2-4.2">update prohibited</dd>
forbidden.<vspace blankLines="0"/> <dt pn="section-10.2.2-4.3">Type:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.2-4.4">status</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.2-4.5">Description:</dt>
> <dd pn="section-10.2.2-4.6">Updates to the object instance are forbi
</list> dden.</dd>
</t> <dt pn="section-10.2.2-4.7">Registrant Name:</dt>
<t> <dd pn="section-10.2.2-4.8">IESG</dd>
<list style="none"> <dt pn="section-10.2.2-4.9">Registrant Contact Information:</dt>
<t>Value: transfer prohibited<vspace blankLines= <dd pn="section-10.2.2-4.10">iesg@ietf.org</dd>
"0"/> </dl>
Type: status<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-5"
Description: Transfers of the registration from >
one registrar <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 r
egistrar
to another are forbidden. This type of statu s normally applies to DNR to another are forbidden. This type of statu s normally applies to DNR
domain names.<vspace blankLines="0"/> domain names.</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.2-5.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.2-5.8">IESG</dd>
> <dt pn="section-10.2.2-5.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.2-5.10">iesg@ietf.org</dd>
</t> </dl>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-6"
<list style="none"> >
<t>Value: delete prohibited<vspace blankLines="0 <dt pn="section-10.2.2-6.1">Value:</dt>
"/> <dd pn="section-10.2.2-6.2">delete prohibited</dd>
Type: status<vspace blankLines="0"/> <dt pn="section-10.2.2-6.3">Type:</dt>
Description: Deletion of the registration of the <dd pn="section-10.2.2-6.4">status</dd>
object <dt pn="section-10.2.2-6.5">Description:</dt>
<dd pn="section-10.2.2-6.6">Deletion of the registration of the obje
ct
instance is forbidden. This type of status n ormally applies to DNR instance is forbidden. This type of status n ormally applies to DNR
domain names.<vspace blankLines="0"/> domain names.</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.2-6.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.2-6.8">IESG</dd>
> <dt pn="section-10.2.2-6.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.2-6.10">iesg@ietf.org</dd>
</t> </dl>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-7"
<list style="none"> >
<t>Value: proxy<vspace blankLines="0"/> <dt pn="section-10.2.2-7.1">Value:</dt>
Type: status<vspace blankLines="0"/> <dd pn="section-10.2.2-7.2">proxy</dd>
Description: The registration of the object inst <dt pn="section-10.2.2-7.3">Type:</dt>
ance has been performed <dd pn="section-10.2.2-7.4">status</dd>
by a third party. This is most commonly appl <dt pn="section-10.2.2-7.5">Description:</dt>
ied to entities.<vspace blankLines="0"/> <dd pn="section-10.2.2-7.6">The registration of the object instance
Registrant Name: IESG<vspace blankLines="0"/> has been performed
Registrant Contact Information: iesg@ietf.org</t by a third party. This is most commonly appl
> ied to entities.</dd>
</list> <dt pn="section-10.2.2-7.7">Registrant Name:</dt>
</t> <dd pn="section-10.2.2-7.8">IESG</dd>
<t> <dt pn="section-10.2.2-7.9">Registrant Contact Information:</dt>
<list style="none"> <dd pn="section-10.2.2-7.10">iesg@ietf.org</dd>
<t>Value: private<vspace blankLines="0"/> </dl>
Type: status<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-8"
Description: The information of the object insta >
nce is not designated <dt pn="section-10.2.2-8.1">Value:</dt>
for public consumption. This is most commonl <dd pn="section-10.2.2-8.2">private</dd>
y applied to entities.<vspace blankLines="0"/> <dt pn="section-10.2.2-8.3">Type:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.2-8.4">status</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.2-8.5">Description:</dt>
> <dd pn="section-10.2.2-8.6">The information of the object instance i
</list> s not designated
</t> for public consumption. This is most commonl
<t> y applied to entities.</dd>
<list style="none"> <dt pn="section-10.2.2-8.7">Registrant Name:</dt>
<t>Value: removed<vspace blankLines="0"/> <dd pn="section-10.2.2-8.8">IESG</dd>
Type: status<vspace blankLines="0"/> <dt pn="section-10.2.2-8.9">Registrant Contact Information:</dt>
Description: Some of the information of the obje <dd pn="section-10.2.2-8.10">iesg@ietf.org</dd>
ct instance has not </dl>
been made available and has been removed. Th <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-9"
is is most commonly applied to entities.<vspace blankLines="0"/> >
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.2-9.1">Value:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.2-9.2">removed</dd>
> <dt pn="section-10.2.2-9.3">Type:</dt>
</list> <dd pn="section-10.2.2-9.4">status</dd>
</t> <dt pn="section-10.2.2-9.5">Description:</dt>
<t> <dd pn="section-10.2.2-9.6">Some of the information of the object in
<list style="none"> stance has not
<t>Value: obscured<vspace blankLines="0"/> been made available and has been removed. Th
Type: status<vspace blankLines="0"/> is is most commonly applied to entities.</dd>
Description: Some of the information of the obje <dt pn="section-10.2.2-9.7">Registrant Name:</dt>
ct instance has been <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 i
nstance has been
altered for the purposes of not readily reve aling the actual information altered for the purposes of not readily reve aling the actual information
of the object instance. This is most commonl of the object instance. This is most commonl
y applied to entities.<vspace blankLines="0"/> y applied to entities.</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.2-10.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.2-10.8">IESG</dd>
> <dt pn="section-10.2.2-10.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.2-10.10">iesg@ietf.org</dd>
</t> </dl>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-11
<list style="none"> ">
<t>Value: associated<vspace blankLines="0"/> <dt pn="section-10.2.2-11.1">Value:</dt>
Type: status<vspace blankLines="0"/> <dd pn="section-10.2.2-11.2">associated</dd>
Description: The object instance is associated w <dt pn="section-10.2.2-11.3">Type:</dt>
ith other object instances <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 s ignify that a nameserver is in the registry. This is most commonly used to s ignify that a nameserver is
associated with a domain or that an entity is as sociated with a network resource associated with a domain or that an entity is as sociated with a network resource
or domain.<vspace blankLines="0"/> or domain.</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.2-11.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.2-11.8">IESG</dd>
> <dt pn="section-10.2.2-11.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.2-11.10">iesg@ietf.org</dd>
</t> </dl>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-12
<list style="none"> ">
<t>Value: active<vspace blankLines="0"/> <dt pn="section-10.2.2-12.1">Value:</dt>
Type: status<vspace blankLines="0"/> <dd pn="section-10.2.2-12.2">active</dd>
Description: The object instance is in use. For <dt pn="section-10.2.2-12.3">Type:</dt>
domain names, it signifies <dd pn="section-10.2.2-12.4">status</dd>
that the domain name is published in DNS. For ne <dt pn="section-10.2.2-12.5">Description:</dt>
twork and autnum registrations <dd pn="section-10.2.2-12.6">The object instance is in use. For doma
in names, it signifies
that the domain name is published in DNS. For ne
twork and autnum registrations,
it signifies that they are allocated or assigned for use in operational networks. it signifies that they are allocated or assigned for use in operational networks.
This maps to the Extensible Provisioning Protoco This maps to the "OK" status of the Extensible P
l (EPP) <xref target="RFC5730"></xref> 'OK' status.<vspace blankLines="0"/> rovisioning Protocol (EPP) <xref target="RFC5730" format="default" sectionFormat
Registrant Name: IESG<vspace blankLines="0"/> ="of" derivedContent="RFC5730"/>.</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.2-12.7">Registrant Name:</dt>
> <dd pn="section-10.2.2-12.8">IESG</dd>
</list> <dt pn="section-10.2.2-12.9">Registrant Contact Information:</dt>
</t> <dd pn="section-10.2.2-12.10">iesg@ietf.org</dd>
<t> </dl>
<list style="none"> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-13
<t>Value: inactive<vspace blankLines="0"/> ">
Type: status<vspace blankLines="0"/> <dt pn="section-10.2.2-13.1">Value:</dt>
Description: The object instance is not in use. <dd pn="section-10.2.2-13.2">inactive</dd>
See 'active'.<vspace blankLines="0"/> <dt pn="section-10.2.2-13.3">Type:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.2-13.4">status</dd>
Registrant Contact Information: iesg@ietf.org</t <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
</list> "active".</dd>
</t> <dt pn="section-10.2.2-13.7">Registrant Name:</dt>
<t> <dd pn="section-10.2.2-13.8">IESG</dd>
<list style="none"> <dt pn="section-10.2.2-13.9">Registrant Contact Information:</dt>
<t>Value: locked<vspace blankLines="0"/> <dd pn="section-10.2.2-13.10">iesg@ietf.org</dd>
Type: status<vspace blankLines="0"/> </dl>
Description: Changes to the object instance cann <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-14
ot be made, including the association of other ">
object instances.<vspace blankLines="0"/> <dt pn="section-10.2.2-14.1">Value:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.2-14.2">locked</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.2-14.3">Type:</dt>
> <dd pn="section-10.2.2-14.4">status</dd>
</list> <dt pn="section-10.2.2-14.5">Description:</dt>
</t> <dd pn="section-10.2.2-14.6">Changes to the object instance cannot b
<t> e made, including the association of other
<list style="none"> object instances.</dd>
<t>Value: pending create<vspace blankLines="0"/> <dt pn="section-10.2.2-14.7">Registrant Name:</dt>
Type: status<vspace blankLines="0"/> <dd pn="section-10.2.2-14.8">IESG</dd>
Description: A request has been received for the <dt pn="section-10.2.2-14.9">Registrant Contact Information:</dt>
creation of the object instance but <dd pn="section-10.2.2-14.10">iesg@ietf.org</dd>
this action is not yet complete.<vspace blankLin </dl>
es="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-15
Registrant Name: IESG<vspace blankLines="0"/> ">
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.2-15.1">Value:</dt>
> <dd pn="section-10.2.2-15.2">pending create</dd>
</list> <dt pn="section-10.2.2-15.3">Type:</dt>
</t> <dd pn="section-10.2.2-15.4">status</dd>
<t> <dt pn="section-10.2.2-15.5">Description:</dt>
<list style="none"> <dd pn="section-10.2.2-15.6">A request has been received for the cre
<t>Value: pending renew<vspace blankLines="0"/> ation of the object instance, but
Type: status<vspace blankLines="0"/> this action is not yet complete.</dd>
Description: A request has been received for the <dt pn="section-10.2.2-15.7">Registrant Name:</dt>
renewal of the object instance but <dd pn="section-10.2.2-15.8">IESG</dd>
this action is not yet complete.<vspace blan <dt pn="section-10.2.2-15.9">Registrant Contact Information:</dt>
kLines="0"/> <dd pn="section-10.2.2-15.10">iesg@ietf.org</dd>
Registrant Name: IESG<vspace blankLines="0"/> </dl>
Registrant Contact Information: iesg@ietf.org</t <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-16
> ">
</list> <dt pn="section-10.2.2-16.1">Value:</dt>
</t> <dd pn="section-10.2.2-16.2">pending renew</dd>
<t> <dt pn="section-10.2.2-16.3">Type:</dt>
<list style="none"> <dd pn="section-10.2.2-16.4">status</dd>
<t>Value: pending transfer<vspace blankLines="0" <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 ren
Type: status<vspace blankLines="0"/> ewal of the object instance, but
Description: A request has been received for the this action is not yet complete.</dd>
transfer of the object instance but <dt pn="section-10.2.2-16.7">Registrant Name:</dt>
this action is not yet complete.<vspace blan <dd pn="section-10.2.2-16.8">IESG</dd>
kLines="0"/> <dt pn="section-10.2.2-16.9">Registrant Contact Information:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.2-16.10">iesg@ietf.org</dd>
Registrant Contact Information: iesg@ietf.org</t </dl>
> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-17
</list> ">
</t> <dt pn="section-10.2.2-17.1">Value:</dt>
<t> <dd pn="section-10.2.2-17.2">pending transfer</dd>
<list style="none"> <dt pn="section-10.2.2-17.3">Type:</dt>
<t>Value: pending update<vspace blankLines="0"/> <dd pn="section-10.2.2-17.4">status</dd>
Type: status<vspace blankLines="0"/> <dt pn="section-10.2.2-17.5">Description:</dt>
Description: A request has been received for the <dd pn="section-10.2.2-17.6">A request has been received for the tra
update or modification of the object instance but nsfer of the object instance, but
this action is not yet complete.<vspace blan this action is not yet complete.</dd>
kLines="0"/> <dt pn="section-10.2.2-17.7">Registrant Name:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.2-17.8">IESG</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.2-17.9">Registrant Contact Information:</dt>
> <dd pn="section-10.2.2-17.10">iesg@ietf.org</dd>
</list> </dl>
</t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.2-18
<t> ">
<list style="none"> <dt pn="section-10.2.2-18.1">Value:</dt>
<t>Value: pending delete<vspace blankLines="0"/> <dd pn="section-10.2.2-18.2">pending update</dd>
Type: status<vspace blankLines="0"/> <dt pn="section-10.2.2-18.3">Type:</dt>
Description: A request has been received for the <dd pn="section-10.2.2-18.4">status</dd>
deletion or removal of the object instance but <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 upd
ate or modification of the object instance, but
this action is not yet 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 del
etion or removal of the object instance, but
this action is not yet complete. For domains , this might mean that the name is no longer published 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 regi in DNS but has not yet been purged from the regi
stry database.<vspace blankLines="0"/> stry database.</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.2-19.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.2-19.8">IESG</dd>
> <dt pn="section-10.2.2-19.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.2-19.10">iesg@ietf.org</dd>
</t> </dl>
</section>
</section> <section anchor="sect-10.2.3" numbered="true" toc="include" removeInRFC=
"false" pn="section-10.2.3">
<section title="Event Actions" anchor="sect-10.2.3"><t> <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" The following values have been registered in the "RDAP JSON Values"
registry:</t> registry:</t>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-2"
<list style="none"> >
<t>Value: registration<vspace blankLines="0"/> <dt pn="section-10.2.3-2.1">Value:</dt>
Type: event action<vspace blankLines="0"/> <dd pn="section-10.2.3-2.2">registration</dd>
Description: The object instance was initially r <dt pn="section-10.2.3-2.3">Type:</dt>
egistered.<vspace blankLines="0"/> <dd pn="section-10.2.3-2.4">event action</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.3-2.5">Description:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.3-2.6">The object instance was initially regist
> ered.</dd>
</list> <dt pn="section-10.2.3-2.7">Registrant Name:</dt>
</t> <dd pn="section-10.2.3-2.8">IESG</dd>
<t> <dt pn="section-10.2.3-2.9">Registrant Contact Information:</dt>
<list style="none"> <dd pn="section-10.2.3-2.10">iesg@ietf.org</dd>
<t>Value: reregistration<vspace blankLines="0"/> </dl>
Type: event action<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-3"
Description: The object instance was registered >
subsequently to initial registration.<vspace blankLines="0"/> <dt pn="section-10.2.3-3.1">Value:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.3-3.2">reregistration</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.3-3.3">Type:</dt>
> <dd pn="section-10.2.3-3.4">event action</dd>
</list> <dt pn="section-10.2.3-3.5">Description:</dt>
</t> <dd pn="section-10.2.3-3.6">The object instance was registered subse
<t> quently to initial registration.</dd>
<list style="none"> <dt pn="section-10.2.3-3.7">Registrant Name:</dt>
<t>Value: last changed<vspace blankLines="0"/> <dd pn="section-10.2.3-3.8">IESG</dd>
Type: event action<vspace blankLines="0"/> <dt pn="section-10.2.3-3.9">Registrant Contact Information:</dt>
Description: An action noting when the informati <dd pn="section-10.2.3-3.10">iesg@ietf.org</dd>
on in the object instance was last changed.<vspace blankLines="0"/> </dl>
Registrant Name: IESG<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-4"
Registrant Contact Information: iesg@ietf.org</t >
> <dt pn="section-10.2.3-4.1">Value:</dt>
</list> <dd pn="section-10.2.3-4.2">last changed</dd>
</t> <dt pn="section-10.2.3-4.3">Type:</dt>
<t> <dd pn="section-10.2.3-4.4">event action</dd>
<list style="none"> <dt pn="section-10.2.3-4.5">Description:</dt>
<t>Value: expiration<vspace blankLines="0"/> <dd pn="section-10.2.3-4.6">An action noting when the information in
Type: event action<vspace blankLines="0"/> the object instance was last changed.</dd>
Description: The object instance has been remove <dt pn="section-10.2.3-4.7">Registrant Name:</dt>
d or will be removed at a pre-determined <dd pn="section-10.2.3-4.8">IESG</dd>
date and time from the registry.<vspace blan <dt pn="section-10.2.3-4.9">Registrant Contact Information:</dt>
kLines="0"/> <dd pn="section-10.2.3-4.10">iesg@ietf.org</dd>
Registrant Name: IESG<vspace blankLines="0"/> </dl>
Registrant Contact Information: iesg@ietf.org</t <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-5"
> >
</list> <dt pn="section-10.2.3-5.1">Value:</dt>
</t> <dd pn="section-10.2.3-5.2">expiration</dd>
<t> <dt pn="section-10.2.3-5.3">Type:</dt>
<list style="none"> <dd pn="section-10.2.3-5.4">event action</dd>
<t>Value: deletion<vspace blankLines="0"/> <dt pn="section-10.2.3-5.5">Description:</dt>
Type: event action<vspace blankLines="0"/> <dd pn="section-10.2.3-5.6">The object instance has been removed or
Description: The object instance was removed fro will be removed at a predetermined
m the registry at a point in time that was not pre-determined.<vspace blankLines date and time from the registry.</dd>
="0"/> <dt pn="section-10.2.3-5.7">Registrant Name:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.3-5.8">IESG</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.3-5.9">Registrant Contact Information:</dt>
> <dd pn="section-10.2.3-5.10">iesg@ietf.org</dd>
</list> </dl>
</t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-6"
<t> >
<list style="none"> <dt pn="section-10.2.3-6.1">Value:</dt>
<t>Value: reinstantiation<vspace blankLines="0"/ <dd pn="section-10.2.3-6.2">deletion</dd>
> <dt pn="section-10.2.3-6.3">Type:</dt>
Type: event action<vspace blankLines="0"/> <dd pn="section-10.2.3-6.4">event action</dd>
Description: The object instance was reregistere <dt pn="section-10.2.3-6.5">Description:</dt>
d after having been <dd pn="section-10.2.3-6.6">The object instance was removed from the
removed from the registry.<vspace blankLines registry at a point in time that was not predetermined.</dd>
="0"/> <dt pn="section-10.2.3-6.7">Registrant Name:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.3-6.8">IESG</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.3-6.9">Registrant Contact Information:</dt>
> <dd pn="section-10.2.3-6.10">iesg@ietf.org</dd>
</list> </dl>
</t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-7"
<t> >
<list style="none"> <dt pn="section-10.2.3-7.1">Value:</dt>
<t>Value: transfer<vspace blankLines="0"/> <dd pn="section-10.2.3-7.2">reinstantiation</dd>
Type: event action<vspace blankLines="0"/> <dt pn="section-10.2.3-7.3">Type:</dt>
Description: The object instance was transferred <dd pn="section-10.2.3-7.4">event action</dd>
from one registrar to another.<vspace blankLines="0"/> <dt pn="section-10.2.3-7.5">Description:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.3-7.6">The object instance was reregistered aft
Registrant Contact Information: iesg@ietf.org</t er having been
> removed from the registry.</dd>
</list> <dt pn="section-10.2.3-7.7">Registrant Name:</dt>
</t> <dd pn="section-10.2.3-7.8">IESG</dd>
<t> <dt pn="section-10.2.3-7.9">Registrant Contact Information:</dt>
<list style="none"> <dd pn="section-10.2.3-7.10">iesg@ietf.org</dd>
<t>Value: locked<vspace blankLines="0"/> </dl>
Type: event action<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-8"
Description: The object instance was locked (see >
the 'locked' status).<vspace blankLines="0"/> <dt pn="section-10.2.3-8.1">Value:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.3-8.2">transfer</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.3-8.3">Type:</dt>
> <dd pn="section-10.2.3-8.4">event action</dd>
</list> <dt pn="section-10.2.3-8.5">Description:</dt>
</t> <dd pn="section-10.2.3-8.6">The object instance was transferred from
<t> one registrar to another.</dd>
<list style="none"> <dt pn="section-10.2.3-8.7">Registrant Name:</dt>
<t>Value: unlocked<vspace blankLines="0"/> <dd pn="section-10.2.3-8.8">IESG</dd>
Type: event action<vspace blankLines="0"/> <dt pn="section-10.2.3-8.9">Registrant Contact Information:</dt>
Description: The object instance was unlocked (s <dd pn="section-10.2.3-8.10">iesg@ietf.org</dd>
ee the 'locked' status).<vspace blankLines="0"/> </dl>
Registrant Name: IESG<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.3-9"
Registrant Contact Information: iesg@ietf.org</t >
> <dt pn="section-10.2.3-9.1">Value:</dt>
</list> <dd pn="section-10.2.3-9.2">locked</dd>
</t> <dt pn="section-10.2.3-9.3">Type:</dt>
</section> <dd pn="section-10.2.3-9.4">event action</dd>
<dt pn="section-10.2.3-9.5">Description:</dt>
<section title="Roles" anchor="sect-10.2.4"><t> <dd pn="section-10.2.3-9.6">The object instance was locked (see 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 t
he "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 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" The following values have been registered in the "RDAP JSON Values"
registry:</t> registry:</t>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-2"
<list style="none"> >
<t>Value: registrant<vspace blankLines="0"/> <dt pn="section-10.2.4-2.1">Value:</dt>
Type: role<vspace blankLines="0"/> <dd pn="section-10.2.4-2.2">registrant</dd>
Description: The entity object instance is the r <dt pn="section-10.2.4-2.3">Type:</dt>
egistrant of the <dd pn="section-10.2.4-2.4">role</dd>
registration. In some registries, this is kn <dt pn="section-10.2.4-2.5">Description:</dt>
own as a maintainer.<vspace blankLines="0"/> <dd pn="section-10.2.4-2.6">The entity object instance is the regist
Registrant Name: IESG<vspace blankLines="0"/> rant of the
Registrant Contact Information: iesg@ietf.org</t registration. In some registries, this is kn
> own as a maintainer.</dd>
</list> <dt pn="section-10.2.4-2.7">Registrant Name:</dt>
</t> <dd pn="section-10.2.4-2.8">IESG</dd>
<t> <dt pn="section-10.2.4-2.9">Registrant Contact Information:</dt>
<list style="none"> <dd pn="section-10.2.4-2.10">iesg@ietf.org</dd>
<t>Value: technical<vspace blankLines="0"/> </dl>
Type: role<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-3"
Description: The entity object instance is a tec >
hnical contact for the <dt pn="section-10.2.4-3.1">Value:</dt>
registration.<vspace blankLines="0"/> <dd pn="section-10.2.4-3.2">technical</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.4-3.3">Type:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.4-3.4">role</dd>
> <dt pn="section-10.2.4-3.5">Description:</dt>
</list> <dd pn="section-10.2.4-3.6">The entity object instance is a technica
</t> l contact for the
<t> registration.</dd>
<list style="none"> <dt pn="section-10.2.4-3.7">Registrant Name:</dt>
<t>Value: administrative<vspace blankLines="0"/> <dd pn="section-10.2.4-3.8">IESG</dd>
Type: role<vspace blankLines="0"/> <dt pn="section-10.2.4-3.9">Registrant Contact Information:</dt>
Description: The entity object instance is an ad <dd pn="section-10.2.4-3.10">iesg@ietf.org</dd>
ministrative contact for </dl>
the registration.<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-4"
Registrant Name: IESG<vspace blankLines="0"/> >
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.4-4.1">Value:</dt>
> <dd pn="section-10.2.4-4.2">administrative</dd>
</list> <dt pn="section-10.2.4-4.3">Type:</dt>
</t> <dd pn="section-10.2.4-4.4">role</dd>
<t> <dt pn="section-10.2.4-4.5">Description:</dt>
<list style="none"> <dd pn="section-10.2.4-4.6">The entity object instance is an adminis
<t>Value: abuse<vspace blankLines="0"/> trative contact for
Type: role<vspace blankLines="0"/> the registration.</dd>
Description: The entity object instance handles <dt pn="section-10.2.4-4.7">Registrant Name:</dt>
network abuse issues on <dd pn="section-10.2.4-4.8">IESG</dd>
behalf of the registrant of the registration <dt pn="section-10.2.4-4.9">Registrant Contact Information:</dt>
.<vspace blankLines="0"/> <dd pn="section-10.2.4-4.10">iesg@ietf.org</dd>
Registrant Name: IESG<vspace blankLines="0"/> </dl>
Registrant Contact Information: iesg@ietf.org</t <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-5"
> >
</list> <dt pn="section-10.2.4-5.1">Value:</dt>
</t> <dd pn="section-10.2.4-5.2">abuse</dd>
<t> <dt pn="section-10.2.4-5.3">Type:</dt>
<list style="none"> <dd pn="section-10.2.4-5.4">role</dd>
<t>Value: billing<vspace blankLines="0"/> <dt pn="section-10.2.4-5.5">Description:</dt>
Type: role<vspace blankLines="0"/> <dd pn="section-10.2.4-5.6">The entity object instance handles netwo
Description: The entity object instance handles rk abuse issues on
payment and billing behalf of the registrant of the registration
issues on behalf of the registrant of the re .</dd>
gistration.<vspace blankLines="0"/> <dt pn="section-10.2.4-5.7">Registrant Name:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.4-5.8">IESG</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.4-5.9">Registrant Contact Information:</dt>
> <dd pn="section-10.2.4-5.10">iesg@ietf.org</dd>
</list> </dl>
</t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-6"
<t> >
<list style="none"> <dt pn="section-10.2.4-6.1">Value:</dt>
<t>Value: registrar<vspace blankLines="0"/> <dd pn="section-10.2.4-6.2">billing</dd>
Type: role<vspace blankLines="0"/> <dt pn="section-10.2.4-6.3">Type:</dt>
Description: The entity object instance represen <dd pn="section-10.2.4-6.4">role</dd>
ts the authority <dt pn="section-10.2.4-6.5">Description:</dt>
responsible for the registration in the regi <dd pn="section-10.2.4-6.6">The entity object instance handles payme
stry.<vspace blankLines="0"/> nt and billing
Registrant Name: IESG<vspace blankLines="0"/> issues on behalf of the registrant of the re
Registrant Contact Information: iesg@ietf.org</t gistration.</dd>
> <dt pn="section-10.2.4-6.7">Registrant Name:</dt>
</list> <dd pn="section-10.2.4-6.8">IESG</dd>
</t> <dt pn="section-10.2.4-6.9">Registrant Contact Information:</dt>
<t> <dd pn="section-10.2.4-6.10">iesg@ietf.org</dd>
<list style="none"> </dl>
<t>Value: reseller<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-7"
Type: role<vspace blankLines="0"/> >
Description: The entity object instance represen <dt pn="section-10.2.4-7.1">Value:</dt>
ts a third party <dd pn="section-10.2.4-7.2">registrar</dd>
through which the registration was conducted <dt pn="section-10.2.4-7.3">Type:</dt>
(i.e. not the registry or registrar).<vspace blankLines="0"/> <dd pn="section-10.2.4-7.4">role</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.4-7.5">Description:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.4-7.6">The entity object instance represents th
> e authority
</list> responsible for the registration in the regi
</t> stry.</dd>
<t> <dt pn="section-10.2.4-7.7">Registrant Name:</dt>
<list style="none"> <dd pn="section-10.2.4-7.8">IESG</dd>
<t>Value: sponsor<vspace blankLines="0"/> <dt pn="section-10.2.4-7.9">Registrant Contact Information:</dt>
Type: role<vspace blankLines="0"/> <dd pn="section-10.2.4-7.10">iesg@ietf.org</dd>
Description: The entity object instance represen </dl>
ts a domain policy <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-8"
sponsor, such as an ICANN approved sponsor.< >
vspace blankLines="0"/> <dt pn="section-10.2.4-8.1">Value:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.4-8.2">reseller</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.4-8.3">Type:</dt>
> <dd pn="section-10.2.4-8.4">role</dd>
</list> <dt pn="section-10.2.4-8.5">Description:</dt>
</t> <dd pn="section-10.2.4-8.6">The entity object instance represents a
<t> third party
<list style="none"> through which the registration was conducted
<t>Value: proxy<vspace blankLines="0"/> (i.e., not the registry or registrar).</dd>
Type: role<vspace blankLines="0"/> <dt pn="section-10.2.4-8.7">Registrant Name:</dt>
Description: The entity object instance represen <dd pn="section-10.2.4-8.8">IESG</dd>
ts a proxy for another <dt pn="section-10.2.4-8.9">Registrant Contact Information:</dt>
entity object, such as a registrant.<vspace blan <dd pn="section-10.2.4-8.10">iesg@ietf.org</dd>
kLines="0"/> </dl>
Registrant Name: IESG<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-9"
Registrant Contact Information: iesg@ietf.org</t >
> <dt pn="section-10.2.4-9.1">Value:</dt>
</list> <dd pn="section-10.2.4-9.2">sponsor</dd>
</t> <dt pn="section-10.2.4-9.3">Type:</dt>
<t> <dd pn="section-10.2.4-9.4">role</dd>
<list style="none"> <dt pn="section-10.2.4-9.5">Description:</dt>
<t>Value: notifications<vspace blankLines="0"/> <dd pn="section-10.2.4-9.6">The entity object instance represents a
Type: role<vspace blankLines="0"/> domain policy
Description: An entity object instance designate sponsor, such as an ICANN-approved sponsor.<
d to receive notifications about /dd>
association object instances.<vspace blankLines= <dt pn="section-10.2.4-9.7">Registrant Name:</dt>
"0"/> <dd pn="section-10.2.4-9.8">IESG</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.4-9.9">Registrant Contact Information:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.4-9.10">iesg@ietf.org</dd>
> </dl>
</list> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-10
</t> ">
<t> <dt pn="section-10.2.4-10.1">Value:</dt>
<list style="none"> <dd pn="section-10.2.4-10.2">proxy</dd>
<t>Value: noc<vspace blankLines="0"/> <dt pn="section-10.2.4-10.3">Type:</dt>
Type: role<vspace blankLines="0"/> <dd pn="section-10.2.4-10.4">role</dd>
Description: The entity object instance handles <dt pn="section-10.2.4-10.5">Description:</dt>
communications related to a <dd pn="section-10.2.4-10.6">The entity object instance represents a
network operations center (NOC).<vspace blankLin proxy for another
es="0"/> entity object, such as a registrant.</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.4-10.7">Registrant Name:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.4-10.8">IESG</dd>
> <dt pn="section-10.2.4-10.9">Registrant Contact Information:</dt>
</list> <dd pn="section-10.2.4-10.10">iesg@ietf.org</dd>
</t> </dl>
</section> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.4-11
">
<section title="Variant Relations" anchor="sect-10.2.5"><t> <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.</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 comm
unications related to a
network operations center (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 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" The following values have been registered in the "RDAP JSON Values"
registry:</t> registry:</t>
<t> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-2"
<list style="none"> >
<t>Value: registered<vspace blankLines="0"/> <dt pn="section-10.2.5-2.1">Value:</dt>
Type: domain variant relation<vspace blankLines= <dd pn="section-10.2.5-2.2">registered</dd>
"0"/> <dt pn="section-10.2.5-2.3">Type:</dt>
Description: The variant names are registered in <dd pn="section-10.2.5-2.4">domain variant relation</dd>
the registry.<vspace blankLines="0"/> <dt pn="section-10.2.5-2.5">Description:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.5-2.6">The variant names are registered in the
Registrant Contact Information: iesg@ietf.org</t registry.</dd>
> <dt pn="section-10.2.5-2.7">Registrant Name:</dt>
</list> <dd pn="section-10.2.5-2.8">IESG</dd>
</t> <dt pn="section-10.2.5-2.9">Registrant Contact Information:</dt>
<t> <dd pn="section-10.2.5-2.10">iesg@ietf.org</dd>
<list style="none"> </dl>
<t>Value: unregistered<vspace blankLines="0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-3"
Type: domain variant relation<vspace blankLines= >
"0"/> <dt pn="section-10.2.5-3.1">Value:</dt>
Description: The variant names are not found in <dd pn="section-10.2.5-3.2">unregistered</dd>
the registry.<vspace blankLines="0"/> <dt pn="section-10.2.5-3.3">Type:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.5-3.4">domain variant relation</dd>
Registrant Contact Information: iesg@ietf.org</t <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 r
</list> egistry.</dd>
</t> <dt pn="section-10.2.5-3.7">Registrant Name:</dt>
<t> <dd pn="section-10.2.5-3.8">IESG</dd>
<list style="none"> <dt pn="section-10.2.5-3.9">Registrant Contact Information:</dt>
<t>Value: registration restricted<vspace blankLi <dd pn="section-10.2.5-3.10">iesg@ietf.org</dd>
nes="0"/> </dl>
Type: domain variant relation<vspace blankLines= <dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-4"
"0"/> >
Description: Registration of the variant names i <dt pn="section-10.2.5-4.1">Value:</dt>
s <dd pn="section-10.2.5-4.2">registration restricted</dd>
restricted to certain parties or within cert <dt pn="section-10.2.5-4.3">Type:</dt>
ain rules.<vspace blankLines="0"/> <dd pn="section-10.2.5-4.4">domain variant relation</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.5-4.5">Description:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.5-4.6">Registration of the variant names is
> restricted to certain parties or within cert
</list> ain rules.</dd>
</t> <dt pn="section-10.2.5-4.7">Registrant Name:</dt>
<t> <dd pn="section-10.2.5-4.8">IESG</dd>
<list style="none"> <dt pn="section-10.2.5-4.9">Registrant Contact Information:</dt>
<t>Value: open registration<vspace blankLines="0 <dd pn="section-10.2.5-4.10">iesg@ietf.org</dd>
"/> </dl>
Type: domain variant relation<vspace blankLines= <dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-5"
"0"/> >
Description: Registration of the variant names i <dt pn="section-10.2.5-5.1">Value:</dt>
s available to <dd pn="section-10.2.5-5.2">open registration</dd>
generally qualified registrants.<vspace blan <dt pn="section-10.2.5-5.3">Type:</dt>
kLines="0"/> <dd pn="section-10.2.5-5.4">domain variant relation</dd>
Registrant Name: IESG<vspace blankLines="0"/> <dt pn="section-10.2.5-5.5">Description:</dt>
Registrant Contact Information: iesg@ietf.org</t <dd pn="section-10.2.5-5.6">Registration of the variant names is ava
> ilable to
</list> generally qualified registrants.</dd>
</t> <dt pn="section-10.2.5-5.7">Registrant Name:</dt>
<t> <dd pn="section-10.2.5-5.8">IESG</dd>
<list style="none"> <dt pn="section-10.2.5-5.9">Registrant Contact Information:</dt>
<t>Value: conjoined<vspace blankLines="0"/> <dd pn="section-10.2.5-5.10">iesg@ietf.org</dd>
Type: domain variant relation<vspace blankLines= </dl>
"0"/> <dl spacing="compact" indent="3" newline="false" pn="section-10.2.5-6"
Description: Registration of the variant names o >
ccurs automatically with the <dt pn="section-10.2.5-6.1">Value:</dt>
registration of the containing domain regist <dd pn="section-10.2.5-6.2">conjoined</dd>
ration.<vspace blankLines="0"/> <dt pn="section-10.2.5-6.3">Type:</dt>
Registrant Name: IESG<vspace blankLines="0"/> <dd pn="section-10.2.5-6.4">domain variant relation</dd>
Registrant Contact Information: iesg@ietf.org</t <dt pn="section-10.2.5-6.5">Description:</dt>
> <dd pn="section-10.2.5-6.6">Registration of the variant names occurs
</list> automatically with the
</t> registration of the containing domain regist
</section> ration.</dd>
<dt pn="section-10.2.5-6.7">Registrant Name:</dt>
</section> <dd pn="section-10.2.5-6.8">IESG</dd>
<dt pn="section-10.2.5-6.9">Registrant Contact Information:</dt>
</section> <dd pn="section-10.2.5-6.10">iesg@ietf.org</dd>
</dl>
<section anchor="impl-status" title="Implementation Status"> </section>
<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 protoco
l defined by this specification at the time of posting of this Internet-Draft, a
nd is based on a proposal described in RFC 7942 <xref target="RFC7942"/>. The de
scription of implementations in this section is intended to assist the IETF in i
ts decision processes in progressing drafts to RFCs. Please note that the listin
g of any individual implementation here does not imply endorsement by the IETF.
Furthermore, no effort has been spent to verify the information presented here t
hat 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. Reade
rs 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, wh
ich may serve as evidence of valuable experimentation and feedback that have mad
e the implemented protocols more mature. It is up to the individual working grou
ps 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 Serv
er defined in RFCs 7480,7481,7482 and 7483. RedDog is highly configurable and ex
tensible 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 al
l 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.c
om/net/v1/</t>
<t>Description: Verisign's production RDAP service for the .com and .ne
t gTLDs.</t>
<t>Level of Maturity: Production.</t>
<t>Coverage: Lookup of domain names, name servers, entities; name serve
r 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 .t
v ccTLDs.</t>
<t>Level of Maturity: Experimental.</t>
<t>Coverage: Lookup of domain names, name servers, entities; name serve
r search by IP address; basic search; regular expression search; federated authe
ntication; 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 (AP
NIC)">
<t><list style="none">
<t>Responsible Organization: Asia-Pacific Network Information Centre (A
PNIC)
</t>
<t>Location: https://rdap.apnic.net/, https://github.com/APNIC-net/rdap
d</t>
<t>Description: APNIC's production RDAP service for Internet number res
ouces.</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 resp
onses.</t>
<t>Version Compatibility: RFC 7483</t>
<t>Contact Information: helpdesk@apnic.net</t>
</list></t>
</section> </section>
</section> </section>
<section anchor="sect-11" numbered="true" toc="include" removeInRFC="false"
<section title="Security Considerations" anchor="sect-11"><t> 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 This specification models information serialized in JSON format. As
JSON is a subset of JavaScript, implementations are advised to follow JSON is a subset of JavaScript, implementations are advised to follow
the security considerations outlined in Section 12 of <xref target="RFC8259"/ > to the security considerations outlined in <xref target="RFC8259" section="12" s ectionFormat="of" format="default" derivedLink="https://rfc-editor.org/rfc/rfc82 59#section-12" derivedContent="RFC8259"/> to
prevent code injection.</t> prevent code injection.</t>
<t indent="0" pn="section-11-2">
<t>
Though not specific to JSON, RDAP implementers should be aware of the Though not specific to JSON, RDAP implementers should be aware of the
security considerations specified in <xref target="RFC7480"/> and the securit security considerations specified in <xref target="RFC7480" format="default"
y sectionFormat="of" derivedContent="RFC7480"/> and the security
requirements and considerations in <xref target="RFC7481"/>.</t> requirements and considerations in <xref target="RFC7481" format="default" se
ctionFormat="of" derivedContent="RFC7481"/>.</t>
<t>RDAP responses allow for retrieval of DNSSEC (key) related information, <t indent="0" pn="section-11-3">RDAP responses allow for retrieval of DNSS
EC (key) related information,
but the RRSIG DS from the parent zone is not conveyed alongside it. but the RRSIG DS from the parent zone is not conveyed alongside it.
This means that the DNSSEC keys retrieved by RDAP are disconnected This means that the DNSSEC keys retrieved by RDAP are disconnected
from their containing PKI, and as such are not generally expected to from their containing PKI, and as such are not generally expected to
be trusted without additional information. In particular, the HTTPS be trusted without additional information. In particular, the HTTPS
channel protecting the RDAP connection is not expected to be authorized channel protecting the RDAP connection is not expected to be authorized
to certify the validity of the DNSSEC keys.</t> to certify the validity of the DNSSEC keys.</t>
<t indent="0" pn="section-11-4">
<t>
Clients caching data, especially clients using RDAP-specific caches Clients caching data, especially clients using RDAP-specific caches
(instead of HTTP-layer caches), should have safeguards to prevent (instead of HTTP-layer caches), should have safeguards to prevent
cache poisoning. See <xref target="sect-5"/> for advice on using the self li nks cache poisoning. See <xref target="sect-5" format="default" sectionFormat="o f" derivedContent="Section 5"/> for advice on using the self links
for caching.</t> for caching.</t>
<t indent="0" pn="section-11-5">
<t>
Finally, service operators should be aware of the privacy mechanisms Finally, service operators should be aware of the privacy mechanisms
noted in <xref target="sect-13"/>.</t> noted in <xref target="sect-13" format="default" sectionFormat="of" derivedCo
ntent="Section 13"/>.</t>
</section> </section>
<section anchor="sect-12" numbered="true" toc="include" removeInRFC="false"
<section title="Internationalization Considerations" anchor="sect-12"><se pn="section-12">
ction title="Character Encoding" anchor="sect-12.1"><t> <name slugifiedName="name-internationalization-consid">Internationalizatio
n Considerations</name>
<section anchor="sect-12.1" numbered="true" toc="include" removeInRFC="fal
se" 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 The default text encoding for JSON responses in RDAP is UTF-8
<xref target="RFC3629"/>, and all servers and clients MUST support UTF-8.</t> <xref target="RFC3629" format="default" sectionFormat="of" derivedContent="RF
C3629"/>, and all servers and clients <bcp14>MUST</bcp14> support UTF-8.</t>
</section> </section>
<section anchor="sect-12.2" numbered="true" toc="include" removeInRFC="fal
<section title="URIs and IRIs" anchor="sect-12.2"><t> se" pn="section-12.2">
<xref target="RFC7480"/> defines the use of URIs and IRIs in RDAP.</t> <name slugifiedName="name-uris-and-iris">URIs and IRIs</name>
<t indent="0" pn="section-12.2-1">
</section> <xref target="RFC7480" format="default" sectionFormat="of" derivedContent="RF
C7480"/> defines the use of URIs and IRIs in RDAP.</t>
<section title="Language Tags" anchor="sect-12.3"><t> </section>
<xref target="sect-4.4"/> defines the use of language tags in the JSON respon <section anchor="sect-12.3" numbered="true" toc="include" removeInRFC="fal
ses se" 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" format="default" sectionFormat="of" derivedContent="S
ection 4.4"/> defines the use of language tags in the JSON responses
defined in this document.</t> defined in this document.</t>
</section>
</section> <section anchor="sect-12.4" numbered="true" toc="include" removeInRFC="fal
se" pn="section-12.4">
<section title="Internationalized Domain Names" anchor="sect-12.4"><t> <name slugifiedName="name-internationalized-domain-na">Internationalized
Domain Names</name>
<t indent="0" pn="section-12.4-1">
IDNs are denoted in this specification by the separation of DNS names IDNs are denoted in this specification by the separation of DNS names
in LDH form and Unicode form (see <xref target="sect-3"/>). Representation o in LDH form and Unicode form (see <xref target="sect-3" format="default" sect
f IDNs ionFormat="of" derivedContent="Section 3"/>). Representation of IDNs
in registries is described by the "variants" object in <xref target="sect-5.3 in registries is described by the "variants" object in <xref 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> and the suggested values listed in <xref target="sect-10.2.5" format="default
" sectionFormat="of" derivedContent="Section 10.2.5"/>.</t>
</section> </section>
</section>
</section> <section anchor="sect-13" numbered="true" toc="include" removeInRFC="false"
pn="section-13">
<section title="Privacy Considerations" anchor="sect-13"><t> <name slugifiedName="name-privacy-considerations">Privacy Considerations</
name>
<t indent="0" pn="section-13-1">
This specification suggests status values to denote contact and This specification suggests status values to denote contact and
registrant information that has been marked as private and/or has registrant information that has been marked as private and/or has
been removed or obscured. See <xref target="sect-10.2.2"/> for the complete list been removed or obscured. See <xref target="sect-10.2.2" format="default" se ctionFormat="of" derivedContent="Section 10.2.2"/> for the complete list
of status values. A few of the status values indicate that there are of status values. A few of the status values indicate that there are
privacy concerns associated with the object instance. The following privacy concerns associated with the object instance. The following
status codes SHOULD be used to describe data elements of a response status codes <bcp14>SHOULD</bcp14> be used to describe data elements of a res ponse
when appropriate:</t> when appropriate:</t>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-13-
<t><list hangIndent="3" style="hanging"><t> 2">
<li pn="section-13-2.1">
private -- The object is not be shared in query responses, unless private -- The object is not be shared in query responses, unless
the user is authorized to view this information.</t> the user is authorized to view this information.</li>
<li pn="section-13-2.2">
</list>
</t>
<t><list hangIndent="3" style="hanging"><t>
removed -- Data elements within the object have been collected but removed -- Data elements within the object have been collected but
have been omitted from the response. This option can be used to have been omitted from the response. This option can be used to
prevent unauthorized access to associated object instances without prevent unauthorized access to associated object instances without
the need to mark them as private.</t> the need to mark them as private.</li>
<li pn="section-13-2.3">
</list>
</t>
<t><list hangIndent="3" style="hanging"><t>
obscured -- Data elements within the object have been collected, obscured -- Data elements within the object have been collected,
but the response value has been altered so that values are not but the response value has been altered so that values are not
easily discernible. A value changed from "1212" to "XXXX" is an easily discernible. A value changed from "1212" to "XXXX" is an
example of obscured data. This option may reveal privacy example of obscured data. This option may reveal privacy
sensitive information and should only be used when data sensitive information and should only be used when data
sensitivity does not require a more protective option like sensitivity does not require a more protective option like
"private" or "removed".</t> "private" or "removed".</li>
</ul>
</list> <t indent="0" pn="section-13-3">
</t> See <xref target="sect-a.1" format="default" sectionFormat="of" derivedConten
t="Appendix A.1"/> for an example of applying those values to contacts
<t>
See Appendix A.1 for an example of applying those values to contacts
and registrants.</t> and registrants.</t>
</section>
</section> </middle>
<back>
</middle> <references pn="section-14">
<name slugifiedName="name-references">References</name>
<back> <references pn="section-14.1">
<references title="Normative References"> <name slugifiedName="name-normative-references">Normative References</na
<reference anchor="ISO.3166.1988"><front> me>
<title>Codes for the representation of names of countries, 3rd edition</t <reference anchor="ISO.3166.2020" quoteTitle="true" derivedAnchor="ISO.3
itle> 166.2020">
<author> <front>
<organization>International Organization for Standardization</organizatio <title>Codes for the representation of names of countries and their
n> subdivisions</title>
</author> <author>
<organization showOnFrontPage="true">International Organization fo
<date month="August" year="1988"/> r Standardization</organization>
</front> </author>
<date month="August" year="2020"/>
<seriesInfo name="ISO" value="Standard 3166"/> </front>
</reference> <refcontent>Fourth edition</refcontent>
&RFC2119; <seriesInfo name="ISO" value="Standard 3166"/>
&RFC3339; </reference>
&RFC3629; <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2
&RFC3986; 119" quoteTitle="true" derivedAnchor="RFC2119">
&RFC4034; <front>
&RFC5396; <title>Key words for use in RFCs to Indicate Requirement Levels</tit
&RFC5646; le>
&RFC5890; <author initials="S." surname="Bradner" fullname="S. Bradner">
&RFC5952; <organization showOnFrontPage="true"/>
&RFC7095; </author>
&RFC7480; <date year="1997" month="March"/>
&RFC7481; <abstract>
&RFC8126; <t indent="0">In many standards track documents several words are
&RFC8174; used to signify the requirements in the specification. These words are often ca
&RFC8259; pitalized. This document defines these words as they should be interpreted in IE
&RFC8288; TF documents. This document specifies an Internet Best Current Practices for th
&I-D.ietf-regext-rfc7482bis; e Internet Community, and requests discussion and suggestions for improvements.<
</references> /t>
<references title="Informative References"> </abstract>
<reference anchor="IANA_IDNTABLES" target="https://www.iana.org/domains/i </front>
dn-tables"><front> <seriesInfo name="BCP" value="14"/>
<title>Repository of IDN Practices</title> <seriesInfo name="RFC" value="2119"/>
<author> <seriesInfo name="DOI" value="10.17487/RFC2119"/>
<organization>IANA</organization> </reference>
</author> <reference anchor="RFC3339" target="https://www.rfc-editor.org/info/rfc3
339" quoteTitle="true" derivedAnchor="RFC3339">
<date/> <front>
</front> <title>Date and Time on the Internet: Timestamps</title>
<author initials="G." surname="Klyne" fullname="G. Klyne">
</reference> <organization showOnFrontPage="true"/>
<reference anchor="JSON_ascendancy" target="https://devcentral.f5.com/s/a </author>
rticles/the-stealthy-ascendancy-of-json"><front> <author initials="C." surname="Newman" fullname="C. Newman">
<title>The Stealthy Ascendancy of JSON</title> <organization showOnFrontPage="true"/>
<author fullname="L. MacVittie" initials="L." surname="MacVittie"> </author>
<date 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 representa
tion 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="RFC3629" target="https://www.rfc-editor.org/info/rfc3
629" quoteTitle="true" derivedAnchor="RFC3629">
<front>
<title>UTF-8, a transformation format of ISO 10646</title>
<author 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 compa
tible with many current applications and protocols, and this has led to the deve
lopment of UTF-8, the object of this memo. UTF-8 has the characteristic of pres
erving the full US-ASCII range, providing compatibility with file systems, parse
rs 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/rfc3
986" quoteTitle="true" derivedAnchor="RFC3986">
<front>
<title>Uniform Resource Identifier (URI): Generic Syntax</title>
<author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee
">
<organization showOnFrontPage="true"/>
</author>
<author initials="R." surname="Fielding" fullname="R. Fielding">
<organization showOnFrontPage="true"/>
</author>
<author initials="L." surname="Masinter" fullname="L. Masinter">
<organization showOnFrontPage="true"/>
</author>
<date year="2005" month="January"/>
<abstract>
<t indent="0">A Uniform Resource Identifier (URI) is a compact seq
uence of characters that identifies an abstract or physical resource. This spec
ification defines the generic URI syntax and a process for resolving URI referen
ces that might be in relative form, along with guidelines and security considera
tions for the use of URIs on the Internet. The URI syntax defines a grammar tha
t is a superset of all valid URIs, allowing an implementation to parse the commo
n 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 eac
h 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/rfc4
034" 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), dele
gation signer (DS), resource record digital signature (RRSIG), and authenticated
denial of existence (NSEC) resource records. The purpose and format of each re
source 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 c
hanges 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/rfc5
396" quoteTitle="true" derivedAnchor="RFC5396">
<front>
<title>Textual Representation of Autonomous System (AS) Numbers</tit
le>
<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 represen
tation 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/rfc5
646" 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="edit
or">
<organization showOnFrontPage="true"/>
</author>
<date year="2009" month="September"/>
<abstract>
<t indent="0">This document describes the structure, content, cons
truction, 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 t
o register values for use in language tags and the creation of user-defined exte
nsions for private interchange. This document specifies an Internet Best Curre
nt 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/rfc5
890" quoteTitle="true" derivedAnchor="RFC5890">
<front>
<title>Internationalized Domain Names for Applications (IDNA): Defin
itions 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 Dom
ain Names for Applications (IDNA), superseding the earlier version. It describe
s the document collection and provides definitions and other material that are c
ommon 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/rfc5
952" 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 dramat
ic increase in the need to use IPv6 addresses in text. While the IPv6 address a
rchitecture in Section 2.2 of RFC 4291 describes a flexible model for text repre
sentation of an IPv6 address, this flexibility has been causing problems for ope
rators, system engineers, and users. This document defines a canonical textual
representation format. It does not define a format for internal storage, such a
s within an application or database. It is expected that the canonical format w
ill 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 429
1 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/rfc7
095" 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 fo
r vCard data. The vCard data format is a text format for representing and exchan
ging information about individuals and other entities, for example, telephone nu
mbers, email addresses, structured names, and delivery addresses. JSON is a lig
htweight, text-based, language- independent data interchange format commonly use
d 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/rfc7
480" quoteTitle="true" derivedAnchor="RFC7480">
<front>
<title>HTTP Usage in the Registration Data Access Protocol (RDAP)</t
itle>
<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 d
escribes 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 cla
rify 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/rfc7
481" 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) provide
s "RESTful" web services to retrieve registration metadata from Domain Name and
Regional Internet Registries. This document describes information security serv
ices, including access control, authentication, authorization, availability, dat
a 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/rfc8
126" 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 t
hat use constants to identify various protocol parameters. To ensure that the v
alues in these fields do not have conflicting uses and to promote interoperabili
ty, their allocations are often coordinated by a central record keeper. For IET
F protocols, that role is filled by the Internet Assigned Numbers Authority (IAN
A).</t>
<t indent="0">To make assignments in a given registry prudently, g
uidance 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. T
his document defines a framework for the documentation of these guidelines by sp
ecification 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 obsol
etes 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/rfc8
174" quoteTitle="true" derivedAnchor="RFC8174">
<front>
<title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</ti
tle>
<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 cla
rifying that only UPPERCASE usage of the key words have the defined special mea
nings.</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/rfc8
259" 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 t
he ECMAScript Programming Language Standard. JSON defines a small set of format
ting rules for the portable representation of structured data.</t>
<t indent="0">This document removes inconsistencies with other spe
cifications of JSON, repairs specification errors, and offers experience-based i
nteroperability 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/rfc8
288" 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 relations
hips 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 H
TTP 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/rfc9
082" 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> </author>
<date month="April" year="2011"/>
<date month="April" year="2011"/> </front>
</front> </reference>
<reference anchor="JSON_performance_study" target="https://www.cs.montan
</reference> a.edu/izurieta/pubs/caine2009.pdf" quoteTitle="true" derivedAnchor="JSON_perform
<reference anchor="JSON_performance_study" target="https://www.cs.montana ance_study">
.edu/izurieta/pubs/caine2009.pdf"><front> <front>
<title>Comparison of JSON and XML Data Interchange Formats: A Case Study< <title>Comparison of JSON and XML Data Interchange Formats: A Case S
/title> tudy</title>
<author fullname="N. Nurseitov" initials="N." surname="Nurseitov"> <author fullname="N. Nurseitov" initials="N." surname="Nurseitov">
</author> </author>
<author fullname="M. Paulson" initials="M." surname="Paulson">
<author fullname="M. Paulson" initials="M." surname="Paulson">
</author> </author>
<author fullname="R. Reynolds" initials="R." surname="Reynolds">
<author fullname="R. Reynolds" initials="R." surname="Reynolds">
</author> </author>
<author fullname="C. Izurieta" initials="C." surname="Izurieta">
<author fullname="C. Izurieta" initials="C." surname="Izurieta">
</author> </author>
<date year="2009"/>
<date year="2009"/> </front>
</front> </reference>
<reference anchor="RFC3912" target="https://www.rfc-editor.org/info/rfc3
</reference> 912" quoteTitle="true" derivedAnchor="RFC3912">
&RFC3912; <front>
&RFC5730; <title>WHOIS Protocol Specification</title>
&RFC5910; <author initials="L." surname="Daigle" fullname="L. Daigle">
&RFC6350; <organization showOnFrontPage="true"/>
&RFC6839; </author>
&RFC7942; <date year="2004" month="September"/>
</references> <abstract>
<section title="Suggested Data Modeling with the Entity Object Class" anc <t indent="0">This document updates the specification of the WHOIS
hor="sect-a"><section title="Registrants and Contacts" anchor="sect-a.1"><t> protocol, thereby obsoleting RFC 954. The update is intended to remove the mat
erial from RFC 954 that does not have to do with the on-the-wire protocol, and i
s no longer applicable in today's Internet. This document does not attempt to c
hange 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/rfc5
730" 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 share
d central repository. Specified in XML, the protocol defines generic object man
agement operations and an extensible framework that maps protocol operations to
objects. This document includes a protocol specification, an object mapping tem
plate, 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/rfc5
910" 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 P
rotocol (EPP) extension mapping for the provisioning and management of Domain Na
me System security (DNSSEC) extensions for domain names stored in a shared centr
al repository. Specified in XML, this mapping extends the EPP domain name mappi
ng 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/rfc6
350" 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 repr
esenting and exchanging a variety of information about individuals and other ent
ities (e.g., formatted and structured name and delivery addresses, email address
, multiple telephone numbers, photograph, logo, audio clips, etc.). This docume
nt 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/rfc6
839" 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 partiti
oned 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 s
tructured 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 synt
ax suffix registration form for the "+xml" structured syntax suffix. This docum
ent is not an Internet Standards Track specification; it is published for info
rmational purposes.</t>
</abstract>
</front>
<seriesInfo name="RFC" value="6839"/>
<seriesInfo name="DOI" value="10.17487/RFC6839"/>
</reference>
</references>
</references>
<section anchor="sect-a" numbered="true" toc="include" removeInRFC="false" p
n="section-appendix.a">
<name slugifiedName="name-suggested-data-modeling-wit">Suggested Data Mode
ling with the Entity Object Class</name>
<section anchor="sect-a.1" numbered="true" toc="include" removeInRFC="fals
e" pn="section-a.1">
<name slugifiedName="name-registrants-and-contacts">Registrants and Cont
acts</name>
<t indent="0" pn="section-a.1-1">
This document does not provide specific object classes for This document does not provide specific object classes for
registrants and contacts. Instead, the entity object class may be registrants and contacts. Instead, the entity object class may be
used to represent a registrant or contact. When the entity object is used to represent a registrant or contact. When the entity object is
embedded inside a containing object such as a domain name or IP embedded inside a containing object such as a domain name or IP
network, the "roles" string array can be used to signify the network, the "roles" string array can be used to signify the
relationship. It is recommended that the values from <xref target="sect-10.2 .4"/> relationship. It is recommended that the values from <xref target="sect-10.2 .4" format="default" sectionFormat="of" derivedContent="Section 10.2.4"/>
be used.</t> be used.</t>
<t indent="0" pn="section-a.1-2">
<t>
The following is an example of an elided containing object with an The following is an example of an elided containing object with an
embedded entity that is both a registrant and administrative contact:</t> embedded entity that is both a registrant and administrative contact:</t>
<figure anchor="ure-34" align="left" suppress-title="false" pn="figure-3
<figure anchor="ure-34"><artwork><![CDATA[ 4">
<sourcecode type="json" markers="false" pn="section-a.1-3.1">
{ {
... ...
"entities" : "entities" :
[ [
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle" : "XXXX", "handle" : "XXXX",
"vcardArray":[ "vcardArray":[
"vcard", "vcard",
[ [
skipping to change at line 3531 skipping to change at line 3997
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
}, },
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1991-12-31T23:59:59Z" "eventDate" : "1991-12-31T23:59:59Z"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-a.1-4">
In many use cases, it is necessary to hide or obscure the information In many use cases, it is necessary to hide or obscure the information
of a registrant or contact due to policy or other operational of a registrant or contact due to policy or other operational
matters. Registries can denote these situations with "status" values matters. Registries can denote these situations with "status" values
(see <xref target="sect-10.2.2"/>).</t> (see <xref target="sect-10.2.2" format="default" sectionFormat="of" derivedCo
ntent="Section 10.2.2"/>).</t>
<t> <t indent="0" pn="section-a.1-5">
The following is an elided example of a registrant with information The following is an elided example of a registrant with information
changed to reflect that of a third party.</t> changed to reflect that of a third party.</t>
<figure anchor="ure-35" align="left" suppress-title="false" pn="figure-3
<figure anchor="ure-35"><artwork><![CDATA[ 5">
<sourcecode type="json" markers="false" pn="section-a.1-6.1">
{ {
... ...
"entities" : "entities" :
[ [
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle" : "XXXX", "handle" : "XXXX",
... ...
"roles" : [ "registrant", "administrative" ], "roles" : [ "registrant", "administrative" ],
"status" : [ "proxy", "private", "obscured" ] "status" : [ "proxy", "private", "obscured" ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-a.2" numbered="true" toc="include" removeInRFC="fals
<section title="Registrars" anchor="sect-a.2"><t> e" 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 This document does not provide a specific object class for
registrars, but like registrants and contacts (see Appendix A.1), the registrars, but like registrants and contacts (see <xref target="sect-a.1" fo rmat="default" sectionFormat="of" derivedContent="Appendix A.1"/>), the
"roles" string array maybe used. Additionally, many registrars have "roles" string array maybe used. Additionally, many registrars have
publicly assigned identifiers. The publicIds structure (<xref target="sect-4 .8"/>) publicly assigned identifiers. The publicIds structure (<xref target="sect-4 .8" format="default" sectionFormat="of" derivedContent="Section 4.8"/>)
represents that information.</t> represents that information.</t>
<t indent="0" pn="section-a.2-2">
<t>
The following is an example of an elided containing object with an The following is an example of an elided containing object with an
embedded entity that is a registrar:</t> embedded entity that is a registrar:</t>
<figure anchor="ure-36" align="left" suppress-title="false" pn="figure-3
<figure anchor="ure-36"><artwork><![CDATA[ 6">
<sourcecode type="json" markers="false" pn="section-a.2-3.1">
{ {
... ...
"entities":[ "entities":[
{ {
"objectClassName" : "entity", "objectClassName" : "entity",
"handle":"XXXX", "handle":"XXXX",
"vcardArray":[ "vcardArray":[
"vcard", "vcard",
[ [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
skipping to change at line 3646 skipping to change at line 4111
{ {
"value":"https://example.net/entity/XXXX", "value":"https://example.net/entity/XXXX",
"rel":"alternate", "rel":"alternate",
"type":"text/html", "type":"text/html",
"href":"https://www.example.com" "href":"https://www.example.com"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
</section>
</section> <section anchor="sect-b" numbered="true" toc="include" removeInRFC="false" p
n="section-appendix.b">
<section title="Modeling Events" anchor="sect-b"><t> <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 Events represent actions that have taken place against a registered
object at a certain date and time. Events have three properties: the object at a certain date and time. Events have three properties: the
action, the actor, and the date and time of the event (which is action, the actor, and the date and time of the event (which is
sometimes in the future). In some cases, the identity of the actor sometimes in the future). In some cases, the identity of the actor
is not captured.</t> is not captured.</t>
<t indent="0" pn="section-appendix.b-2">
<t>
Events can be modeled in three ways:</t> Events can be modeled in three ways:</t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-appe
<t><list style="numbers"><t>events with no designated actor</t> ndix.b-3"><li pn="section-appendix.b-3.1" derivedCounter="1.">events with no des
ignated actor</li>
<t>events where the actor is only designated by an identifier</t> <li pn="section-appendix.b-3.2" derivedCounter="2.">events where the act
or is only designated by an identifier</li>
<t>events where the actor can be modeled as an entity</t> <li pn="section-appendix.b-3.3" derivedCounter="3.">events where the act
or can be modeled as an entity</li>
</list> </ol>
</t> <t indent="0" pn="section-appendix.b-4">
For the first use case, the events data structure (<xref target="sect-4.5" fo
<t> rmat="default" sectionFormat="of" derivedContent="Section 4.5"/>) is
For the first use case, the events data structure (<xref target="sect-4.5"/>)
is
used without the "eventActor" object member.</t> used without the "eventActor" object member.</t>
<t indent="0" pn="section-appendix.b-5">
<t>
This is an example of an "events" array without the "eventActor".</t> This is an example of an "events" array without the "eventActor".</t>
<figure anchor="ure-37" align="left" suppress-title="false" pn="figure-37"
<figure anchor="ure-37"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-appendix.b-6.1">
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-appendix.b-7">
For the second use case, the events data structure (<xref target="sect-4.5"/> For the second use case, the events data structure (<xref target="sect-4.5" f
) is ormat="default" sectionFormat="of" derivedContent="Section 4.5"/>) is
used with the "eventActor" object member.</t> used with the "eventActor" object member.</t>
<t indent="0" pn="section-appendix.b-8">
<t>
This is an example of an "events" array with the "eventActor".</t> This is an example of an "events" array with the "eventActor".</t>
<figure anchor="ure-38" align="left" suppress-title="false" pn="figure-38"
<figure anchor="ure-38"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-appendix.b-9.1">
"events" : "events" :
[ [
{ {
"eventAction" : "registration", "eventAction" : "registration",
"eventActor" : "XYZ-NIC", "eventActor" : "XYZ-NIC",
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
} }
] ]
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-appendix.b-10">
For the third use case, the "asEventActor" array is used when an For the third use case, the "asEventActor" array is used when an
entity (<xref target="sect-5.1"/>) is embedded into another object class. Th e entity (<xref target="sect-5.1" format="default" sectionFormat="of" derivedCo ntent="Section 5.1"/>) is embedded into another object class. The
"asEventActor" array follows the same structure as the "events" array "asEventActor" array follows the same structure as the "events" array
but does not have "eventActor" attributes.</t> but does not have "eventActor" attributes.</t>
<t indent="0" pn="section-appendix.b-11">
<t>
The following is an elided example of a domain object with an entity The following is an elided example of a domain object with an entity
as an event actor.</t> as an event actor.</t>
<figure anchor="ure-39" align="left" suppress-title="false" pn="figure-39"
<figure anchor="ure-39"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-appendix.b-12.1">
{ {
"objectClassName" : "domain", "objectClassName" : "domain",
"handle" : "XXXX", "handle" : "XXXX",
"ldhName" : "foo.example", "ldhName" : "foo.example",
"status" : [ "locked", "transfer prohibited" ], "status" : [ "locked", "transfer prohibited" ],
... ...
"entities" : "entities" :
[ [
{ {
"handle" : "XXXX", "handle" : "XXXX",
skipping to change at line 3738 skipping to change at line 4193
"asEventActor" : "asEventActor" :
[ [
{ {
"eventAction" : "last changed", "eventAction" : "last changed",
"eventDate" : "1990-12-31T23:59:59Z" "eventDate" : "1990-12-31T23:59:59Z"
} }
] ]
} }
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
</section> </section>
<section anchor="sect-c" numbered="true" toc="include" removeInRFC="false" p
<section title="Structured vs. Unstructured Addresses" anchor="sect-c"><t n="section-appendix.c">
> <name slugifiedName="name-structured-vs-unstructured-">Structured vs. Unst
The entity (<xref target="sect-5.1"/>) object class uses jCard <xref target=" ructured Addresses</name>
RFC7095"/> to <t indent="0" pn="section-appendix.c-1">
The entity (<xref target="sect-5.1" format="default" sectionFormat="of" deriv
edContent="Section 5.1"/>) object class uses jCard <xref target="RFC7095" format
="default" sectionFormat="of" derivedContent="RFC7095"/> to
represent contact information, including postal addresses. jCard has represent contact information, including postal addresses. jCard has
the ability to represent multiple language preferences, multiple the ability to represent multiple language preferences, multiple
email address and phone numbers, and multiple postal addresses in email address and phone numbers, and multiple postal addresses in
both a structured and unstructured format. This section describes both a structured and unstructured format. This section describes
the use of jCard for representing structured and unstructured the use of jCard for representing structured and unstructured
addresses.</t> addresses.</t>
<t indent="0" pn="section-appendix.c-2">
<t>
The following is an example of a jCard.</t> The following is an example of a jCard.</t>
<figure anchor="ure-40" align="left" suppress-title="false" pn="figure-40"
<figure anchor="ure-40"><artwork><![CDATA[ >
<sourcecode type="json" markers="false" pn="section-appendix.c-3.1">
{ {
"vcardArray":[ "vcardArray":[
"vcard", "vcard",
[ [
["version", {}, "text", "4.0"], ["version", {}, "text", "4.0"],
["fn", {}, "text", "Joe User"], ["fn", {}, "text", "Joe User"],
["n", {}, "text", ["n", {}, "text",
["User", "Joe", "", "", ["ing. jr", "M.Sc."]] ["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
], ],
["kind", {}, "text", "individual"], ["kind", {}, "text", "individual"],
skipping to change at line 3829 skipping to change at line 4284
{ "type":"work" }, { "type":"work" },
"uri", "https://www.example.com/joe.user/joe.asc" "uri", "https://www.example.com/joe.user/joe.asc"
], ],
["tz", {}, ["tz", {},
"utc-offset", "-05:00"], "utc-offset", "-05:00"],
["url", { "type":"home" }, ["url", { "type":"home" },
"uri", "https://example.org"] "uri", "https://example.org"]
] ]
] ]
} }
]]></artwork> </sourcecode>
</figure> </figure>
<t> <t indent="0" pn="section-appendix.c-4">
The arrays in Figure 40 with the first member of "adr" represent The arrays in <xref target="ure-40" format="default" sectionFormat="of" deriv
edContent="Figure 40"/> with the first member of "adr" represent
postal addresses. In the first example, the postal address is given postal addresses. In the first example, the postal address is given
as an array of strings and constitutes a structured address. For as an array of strings and constitutes a structured address. For
components of the structured address that are not applicable, an components of the structured address that are not applicable, an
empty string is given. Each member of that array aligns with the empty string is given. Each member of that array aligns with the
positions of a vCard as given in <xref target="RFC6350"/>. In this example, the positions of a vCard as given in <xref target="RFC6350" format="default" sect ionFormat="of" derivedContent="RFC6350"/>. In this example, the
following data corresponds to the following positional meanings:</t> following data corresponds to the following positional meanings:</t>
<ol spacing="normal" type="1" indent="adaptive" start="1" pn="section-appe
<t><list style="numbers"><t>post office box -- not applicable; empty stri ndix.c-5"><li pn="section-appendix.c-5.1" derivedCounter="1.">post office box --
ng</t> not applicable; empty string</li>
<li pn="section-appendix.c-5.2" derivedCounter="2.">extended address (e.
<t>extended address (e.g., apartment or suite number) -- Suite 1234</t> g., apartment or suite number) -- Suite 1234</li>
<li pn="section-appendix.c-5.3" derivedCounter="3.">street address -- 43
<t>street address -- 4321 Rue Somewhere</t> 21 Rue Somewhere</li>
<li pn="section-appendix.c-5.4" derivedCounter="4.">locality (e.g., city
<t>locality (e.g., city) -- Quebec</t> ) -- Quebec</li>
<li pn="section-appendix.c-5.5" derivedCounter="5.">region (e.g., state
<t>region (e.g., state or province) -- QC</t> or province) -- QC</li>
<li pn="section-appendix.c-5.6" derivedCounter="6.">postal code -- G1V 2
<t>postal code -- G1V 2M2</t> M2</li>
<li pn="section-appendix.c-5.7" derivedCounter="7.">country name (full n
<t>country name (full name) -- Canada</t> ame) -- Canada</li>
</ol>
</list> <t indent="0" pn="section-appendix.c-6">
</t>
<t>
The second example is an unstructured address. It uses the "label" The second example is an unstructured address. It uses the "label"
attribute, which is a string containing a newline (\n) character to attribute, which is a string containing a newline (\n) character to
separate address components in an unordered, unspecified manner. separate address components in an unordered, unspecified manner.
Note that in this example, the structured address array is still Note that in this example, the structured address array is still
given but that each string is an empty string.</t> given but that each string is an empty string.</t>
</section>
</section> <section anchor="sect-d" numbered="true" toc="include" removeInRFC="false" p
n="section-appendix.d">
<section title="Secure DNS" anchor="sect-d"><t> <name slugifiedName="name-secure-dns">Secure DNS</name>
<xref target="sect-5.3"/> defines the "secureDNS" member to represent secure <t indent="0" pn="section-appendix.d-1">
DNS <xref target="sect-5.3" format="default" sectionFormat="of" derivedContent="S
ection 5.3"/> defines the "secureDNS" member to represent secure DNS
information about domain names.</t> information about domain names.</t>
<t indent="0" pn="section-appendix.d-2">
<t>
DNSSEC provides data integrity for DNS through the digital signing of DNSSEC provides data integrity for DNS through the digital signing of
resource records. To enable DNSSEC, the zone is signed by one or resource records. To enable DNSSEC, the zone is signed by one or
more private keys and the signatures are stored as RRSIG records. To 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 complete the chain of trust in the DNS zone hierarchy, a digest of
each DNSKEY record (which contains the public key) must be loaded each DNSKEY record (which contains the public key) must be loaded
into the parent zone, stored as DS records, and signed by the into the parent zone, stored as DS records, and signed by the
parent's private key (RRSIG DS record), as indicated in "Resource Records for the DNS Security Extensions" <xref target="RFC4034"/>. Creating the DS parent's private key (RRSIG DS record), as indicated in "<xref target="RFC403 4" format="title" sectionFormat="of" derivedContent="Resource Records for the DN S Security Extensions"/>" <xref target="RFC4034" format="default" sectionFormat= "of" derivedContent="RFC4034"/>. Creating the DS
records in the parent zone can be done by the registration authority records in the parent zone can be done by the registration authority
"Domain Name System (DNS) Security Extensions Mapping for the Extensible Prov "<xref target="RFC5910" format="title" sectionFormat="of" derivedContent="Dom
isioning Protocol (EPP)" <xref target="RFC5910"/>.</t> ain Name System (DNS) Security Extensions Mapping for the Extensible Provisionin
g Protocol (EPP)"/>" <xref target="RFC5910" format="default" sectionFormat="of"
<t> derivedContent="RFC5910"/>.</t>
<t indent="0" pn="section-appendix.d-3">
Only DS-related information is provided by RDAP, since other Only DS-related information is provided by RDAP, since other
information is not generally stored in the registration database. information is not generally stored in the registration database.
Other DNSSEC-related information can be retrieved with other DNS Other DNSSEC-related information can be retrieved with other DNS
tools such as dig.</t> tools such as dig.</t>
<t indent="0" pn="section-appendix.d-4">
<t> The domain object class (<xref target="sect-5.3" format="default" sectionForm
The domain object class (<xref target="sect-5.3"/>) can represent this inform at="of" derivedContent="Section 5.3"/>) can represent this information
ation
using either the "dsData" or "keyData" object arrays. Client using either the "dsData" or "keyData" object arrays. Client
implementers should be aware that some registries do not collect or implementers should be aware that some registries do not collect or
do not publish all of the secure DNS meta-information.</t> do not publish all of the secure DNS meta-information.</t>
</section>
</section> <section anchor="sect-e" numbered="true" toc="include" removeInRFC="false" p
n="section-appendix.e">
<section title="Motivations for Using JSON" anchor="sect-e"><t> <name slugifiedName="name-motivations-for-using-json">Motivations for Usin
g JSON</name>
<t indent="0" pn="section-appendix.e-1">
This section addresses a common question regarding the use of JSON This section addresses a common question regarding the use of JSON
over other data formats, most notably XML.</t> over other data formats, most notably XML.</t>
<t indent="0" pn="section-appendix.e-2">
<t>
It is often pointed out that many DNRs and one RIR support the EPP It is often pointed out that many DNRs and one RIR support the EPP
<xref target="RFC5730"/> standard, which is an XML serialized protocol. The logic <xref target="RFC5730" format="default" sectionFormat="of" derivedContent="RF C5730"/> standard, which is an XML serialized protocol. The logic
is that since EPP is a common protocol in the industry, it follows is that since EPP is a common protocol in the industry, it follows
that XML would be a more natural choice. While EPP does influence that XML would be a more natural choice. While EPP does influence
this specification quite a bit, EPP serves a different purpose, which this specification quite a bit, EPP serves a different purpose, which
is the provisioning of Internet resources between registries and is the provisioning of Internet resources between registries and
accredited registrars and serving a much narrower audience than that accredited registrars and serving a much narrower audience than that
envisioned for RDAP.</t> envisioned for RDAP.</t>
<t indent="0" pn="section-appendix.e-3">
<t>
By contrast, RDAP has a broader audience and is designed for public By contrast, RDAP has a broader audience and is designed for public
consumption of data. Experience from RIRs with first generation consumption of data. Experience from RIRs with first generation
RESTful web services for WHOIS indicate that a large percentage of RESTful web services for WHOIS indicate that a large percentage of
clients operate within browsers and other platforms where full-blown clients operate within browsers and other platforms where full-blown
XML stacks are not readily available and where JSON is a better fit.</t> XML stacks are not readily available and where JSON is a better fit.</t>
<t indent="0" pn="section-appendix.e-4">
<t>
Additionally, while EPP is used in much of the DNR community it is Additionally, while EPP is used in much of the DNR community it is
not a universal constant in that industry. And finally, EPP's use of not a universal constant in that industry. And finally, EPP's use of
XML predates the specification of JSON. If EPP had been defined XML predates the specification of JSON. If EPP had been defined
today, it may very well have used JSON instead of XML.</t> today, it may very well have used JSON instead of XML.</t>
<t indent="0" pn="section-appendix.e-5">
<t>
Beyond the specific DNR and RIR communities, the trend in the broader Beyond the specific DNR and RIR communities, the trend in the broader
Internet industry is also switching to JSON over XML, especially in Internet industry is also switching to JSON over XML, especially in
the area of RESTful web services (see <xref target="JSON_ascendancy"/>). Stu dies the area of RESTful web services (see <xref target="JSON_ascendancy" format=" default" sectionFormat="of" derivedContent="JSON_ascendancy"/>). Studies
have also found that JSON is generally less bulky and consequently have also found that JSON is generally less bulky and consequently
faster to parse (see <xref target="JSON_performance_study"/>).</t> faster to parse (see <xref target="JSON_performance_study" format="default" s
ectionFormat="of" derivedContent="JSON_performance_study"/>).</t>
</section> </section>
<section numbered="true" toc="include" removeInRFC="false" pn="section-appen
<section title="Acknowledgments" numbered="no" anchor="acknowledgments">< dix.f">
t> <name slugifiedName="name-changes-from-rfc-7483">Changes from RFC 7483</na
me>
<ul spacing="normal" bare="false" empty="false" indent="3" pn="section-app
endix.f-1">
<li pn="section-appendix.f-1.1">Addressed known errata.</li>
<li pn="section-appendix.f-1.2">Updated references to 7482 to RFC 9082.
Adjusted case of "xxxx" used in examples where "XXXX" was previously used, and r
emoved 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 endAutnu
m.
Added "a string representing" to the definition of name in the IP network and AS
N object classes.
Clarified rdapConformance identifier registration expectations in <xref target="
sect-4.1" format="default" sectionFormat="of" derivedContent="Section 4.1"/>.
Changed "lunarNic_level_0" to "lunarNIC_level_0".</li>
<li pn="section-appendix.f-1.3">Clarified that the "value", "rel" and "h
ref" JSON values <bcp14>MUST</bcp14> be specified in the "links" array. </li>
<li pn="section-appendix.f-1.4">Clarified that the "description" array i
s required in the Notices and Remarks data structures and other values are <bcp1
4>OPTIONAL</bcp14>.</li>
<li pn="section-appendix.f-1.5">Noted that all members of the "events" a
nd "Public IDs" arrays are <bcp14>REQUIRED</bcp14>. </li>
<li pn="section-appendix.f-1.6">Fix "self" link values in examples. Chan
ged "http" to "https" link values in examples.
Noted that <xref target="ure-18" format="default" sectionFormat="of" derivedCont
ent="Figure 18"/> is an example of a nameserver object with all "appropriate" va
lues given.
In <xref target="sect-c" format="default" sectionFormat="of" derivedContent="App
endix C"/>, quoted the word "label" in "label attribute".
Added reference to "status" definition in the descriptions for IP networks and a
utnums.
Fixed a 404 for the informative reference to "The Stealthy Ascendancy of JSON".
Added "boolean" to the definition of zoneSigned. </li>
<li pn="section-appendix.f-1.7">Clarified <bcp14>REQUIRED</bcp14> and <b
cp14>OPTIONAL</bcp14> members of the "events" array.</li>
<li pn="section-appendix.f-1.8">Changed "<bcp14>SHOULD</bcp14> not" to "
<bcp14>SHOULD NOT</bcp14>" in <xref target="sect-5" format="default" sectionForm
at="of" derivedContent="Section 5"/>. </li>
<li pn="section-appendix.f-1.9">Updated normative references (RFC 5226 t
o 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 line
s.</li>
<li pn="section-appendix.f-1.10">Added acknowledgments.</li>
<li pn="section-appendix.f-1.11">Changed "The "lang" attribute may appea
r anywhere in an object class or data structure except for in jCard objects" to
"The "lang" attribute as defined in this section <bcp14>MAY</bcp14> appear anywh
ere in an object class or data structure, except for in jCard objects. jCard sup
ports similar functionality by way of the LANGUAGE property parameter (see Secti
on <xref target="RFC6350" section="5.1" sectionFormat="bare" format="default" de
rivedLink="https://rfc-editor.org/rfc/rfc6350#section-5.1" derivedContent="RFC63
50"/> of RFC 6350 <xref target="RFC6350" format="default" sectionFormat="of" der
ivedContent="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, n
umbers, booleans, and null)". Changed "In other words, servers are free to not i
nclude JSON members containing registration data based on their own policies" to
"In other words, servers are free to omit unrequired/optional JSON members cont
aining registration data based on their own policies".</li>
<li pn="section-appendix.f-1.13">Changed "This data structure appears on
ly in the topmost JSON object of a response" to "This data structure <bcp14>MUST
</bcp14> appear in the topmost JSON object of a response". </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 n
on-answer responses <bcp14>MAY</bcp14> return entity bodies with information tha
t could be more descriptive".</li>
<li pn="section-appendix.f-1.15">Changed "The basic structure of that re
sponse 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 n
amed "description"" to "The basic structure of that response is an object class
containing a <bcp14>REQUIRED</bcp14> error code number (corresponding to the HTT
P response code) followed by an <bcp14>OPTIONAL</bcp14> string named "title" and
an <bcp14>OPTIONAL</bcp14> array of strings named "description"".</li>
<li pn="section-appendix.f-1.16">Changed the "Autonomous System Number O
bject Class" section title to "The Autonomous System Number Object Class" for co
nsistency with other section titles. Removed trailing periods in the "Terminolog
y and Definitions" section for consistency. Changed instances of "lunarNic" to "
lunarNIC" for consistency. Removed an extraneous trailing period after the event
Date description. Changed a "." to ";" in the description of the "network" membe
r of the domain object class. Changed "The high-level structure of the autnum ob
ject class consists of information about the network registration" to "The high-
level structure of the autnum object class consists of information about the Aut
onomous System number registration". Changed "registry unique" to "registry-uniq
ue".</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 IA
NA instructions to correct the description of the value in the registry. </li>
<li pn="section-appendix.f-1.18">Added text to <xref target="sect-4.2" f
ormat="default" sectionFormat="of" derivedContent="Section 4.2"/> to note that "
self" and "related" "href" URIs <bcp14>MUST NOT</bcp14> be the same. </li>
<li pn="section-appendix.f-1.19">Added text to <xref target="sect-4.2" f
ormat="default" sectionFormat="of" derivedContent="Section 4.2"/> to describe re
turn of IDNs in LDH name format.</li>
<li pn="section-appendix.f-1.20">Added text to note that the "fn" member
of a contact object <bcp14>MAY</bcp14> be empty in <xref target="sect-3" format
="default" sectionFormat="of" derivedContent="Section 3"/>.</li>
<li pn="section-appendix.f-1.21">Added text to clarify rdapConformance r
equirements in <xref target="sect-4.1" format="default" sectionFormat="of" deriv
edContent="Section 4.1"/>.</li>
<li pn="section-appendix.f-1.22">Added "obsoletes 7483" to the headers,
Abstract, and Introduction. Updated BCP 14 boilerplate. Updated IANA Considerati
ons to note that this RFC (a product of the REGEXT Working Group) replaces RFC 7
483. Changed "simple string" to "simple character string" in Sections <xref targ
et="sect-3" format="counter" sectionFormat="of" derivedContent="3"/> and <xref t
arget="sect-4.7" format="counter" sectionFormat="of" derivedContent="4.7"/>. Cla
rified requirement for the "fn" member in <xref target="sect-3" format="default"
sectionFormat="of" derivedContent="Section 3"/>. Modified the requirement for r
dapConformance placement in <xref target="sect-4.1" format="default" sectionForm
at="of" derivedContent="Section 4.1"/>. Changed "jCard" to "vCard" LANGUAGE prop
erty reference in <xref target="sect-4.4" format="default" sectionFormat="of" de
rivedContent="Section 4.4"/>. Changed "no use" to "little or no use" in <xref ta
rget="sect-5.1" format="default" sectionFormat="of" derivedContent="Section 5.1"
/>. Added example line wrap note in <xref target="sect-5.2" format="default" sec
tionFormat="of" derivedContent="Section 5.2"/>. Modified the definition of "idnT
able" in <xref target="sect-5.3" format="default" sectionFormat="of" derivedCont
ent="Section 5.3"/>. Modified the dsData and keyData examples in <xref target="s
ect-5.3" format="default" sectionFormat="of" derivedContent="Section 5.3"/>. Cha
nged "2001:c00::/23" to "2001:db8::/32" in <xref target="sect-5.4" format="defau
lt" sectionFormat="of" derivedContent="Section 5.4"/>. Expanded the definition o
f "type" in Sections <xref target="sect-5.4" format="counter" sectionFormat="of"
derivedContent="5.4"/> and <xref target="sect-5.5" format="counter" sectionFor
mat="of" derivedContent="5.5"/>. Modified example autnums in <xref target="sect-
5.5" format="default" sectionFormat="of" derivedContent="Section 5.5"/>. Added t
ext to the Security Considerations section to note that DNSSEC information retur
ned in a response cannot be trusted 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 This document is derived from original work on RIR responses in JSON
by Byron J. Ellacott, Arturo L. Servin, Kaveh Ranjbar, and Andrew L. by <contact fullname="Byron J. Ellacott"/>, <contact fullname="Arturo L. Serv
Newton. Additionally, this document incorporates work on DNR in"/>,
responses in JSON by Ning Kong, Linlin Zhou, Jiagui Xie, and Sean <contact fullname="Kaveh Ranjbar"/>, and <contact fullname="Andrew L. Newton
Shen.</t> "/>.
Additionally, this document incorporates work on DNR
<t> responses in JSON by <contact fullname="Ning Kong"/>, <contact fullname="Linl
in 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 The components of the DNR object classes are derived from a
categorization of WHOIS response formats created by Ning Kong, Linlin categorization of WHOIS response formats created by <contact fullname="Ning K
Zhou, Guangqing Deng, Steve Sheng, Francisco Arias, Ray Bellis, and ong"/>, <contact fullname="Linlin Zhou"/>,
Frederico Neves.</t> <contact fullname="Guangqing Deng"/>, <contact fullname="Steve Sheng"/>, <con
tact fullname="Francisco Arias"/>,
<t> <contact fullname="Ray Bellis"/>, and
Tom Harrison, Murray Kucherawy, Ed Lewis, Audric Schiltknecht, Naoki <contact fullname="Frederico Neves"/>.</t>
Kambe, Maarten Bosteels, Mario Loffredo, and Jasdip Singh contributed signifi <t indent="0" pn="section-appendix.g-3">
cant review comments <contact fullname="Tom Harrison"/>, <contact fullname="Murray Kucherawy"/>, <
and provided clarifying text. James Mitchell provided text regarding contact fullname="Ed Lewis"/>, <contact fullname="Audric Schiltknecht"/>,
<contact fullname="Naoki Kambe"/>, <contact fullname="Maarten Bosteels"/>, <c
ontact fullname="Mario Loffredo"/>, and <contact fullname="Jasdip Singh"/> contr
ibuted significant review comments
and provided clarifying text. <contact fullname="James Mitchell"/> provided
text regarding
the processing of unknown JSON attributes and identified issues the processing of unknown JSON attributes and identified issues
leading to the remodeling of events. Ernie Dainow and Francisco leading to the remodeling of events. <contact fullname="Ernie Dainow"/> and
Obispo provided concrete suggestions that led to a better variant <contact fullname="Francisco Obispo"/> provided concrete suggestions that led
to a better variant
model for domain names.</t> model for domain names.</t>
<t indent="0" pn="section-appendix.g-4">
<t> <contact fullname="Ernie Dainow"/> provided the background information on the
Ernie Dainow provided the background information on the secure DNS secure DNS
attributes and objects for domains, informative text on DNSSEC, and attributes and objects for domains, informative text on DNSSEC, and
many other attributes that appear throughout the object classes of many other attributes that appear throughout the object classes of
this document.</t> this document.</t>
<t indent="0" pn="section-appendix.g-5">
<t> The switch to and incorporation of jCard was performed by <contact fullname="
The switch to and incorporation of jCard was performed by Simon Simon Perreault"/>.</t>
Perreault.</t> <t indent="0" pn="section-appendix.g-6">
<contact fullname="Olaf Kolkman"/> and <contact fullname="Murray Kucherawy"/>
<t> chaired the IETF's WEIRDS Working
Olaf Kolkman and Murray Kucherawy chaired the IETF's WEIRDS working Group from which this document was originally created. <contact fullname="Jam
group from which this document was originally created. James Galvin es Galvin"/>
and Antoin Verschuren chaired the REGEXT working group that worked and <contact fullname="Antoin Verschuren"/> chaired the REGEXT Working Group
on the -bis version.</t> that worked
on this document.</t>
</section> </section>
<section anchor="authors-addresses" numbered="false" removeInRFC="false" toc
<section title="Changes from RFC 7483" numbered="no"><t> ="include" pn="section-appendix.h">
<list style="hanging"> <name slugifiedName="name-authors-addresses">Authors' Addresses</name>
<t hangText="00:">Initial version ported from RFC 7483. Addressed kno <author fullname="Scott Hollenbeck" initials="S." surname="Hollenbeck">
wn errata. Added Implementation Status section.</t> <organization showOnFrontPage="true">Verisign Labs</organization>
<t hangText="01:">Updated references to 7482 to 7482bis Internet-Draf <address>
t. Updated "Change Log" to "Changes from RFC 7483". Added APNIC implementation s <postal>
tatus. Adjusted case of "xxxx" used in examples where "XXXX" was previously used <street>12061 Bluemont Way</street>
, and removed an "X" from "XXXXX". Changed IPv6 address example using "C00" to " <city>Reston</city>
c00". Added "a string representing" to the definitions of startAddress and endAd <region>VA</region>
dress. Removed "entity" from "Autonomous System Number Entity Object Class". Add <code>20190</code>
ed "an unsigned 32-bit integer" to the definition of startAutnum and endAutnum. <country>United States of America</country>
Added "a string representing" to the definition of name in the IP network and AS </postal>
N object classes. Clarified rdapConformance identifier registration expectations <email>shollenbeck@verisign.com</email>
in Section 4.1. Changed "lunarNic_level_0" to "lunarNIC_level_0". Clarified tha <uri>https://www.verisignlabs.com/</uri>
t the "value", "rel" and "href" JSON values MUST be specified in the "links" arr </address>
ay. Clarified that the "description" array is required in the Notices and Remark </author>
s data structures and other values are OPTIONAL. Noted that all members of the " <author fullname="Andy Newton" initials="A." surname="Newton">
events" and "Public IDs" arrays are REQUIRED. Fix "self" link values in examples <organization abbrev="AWS" showOnFrontPage="true">Amazon Web Services, I
. Changed "http" to "https" link values in examples. Noted that Figure 18 is an nc.</organization>
example of a nameserver object with all "appropriate" values given. In appendix <address>
C, quoted the word "label" in "label attribute". Added reference to "status" def <postal>
inition in the descriptions for IP networks and autnums. Fixed a 404 for the inf <street>13200 Woodland Park Road</street>
ormative reference to "The Stealthy Ascendancy of JSON". Added "boolean" to the <city>Herndon</city>
definition of zoneSigned. Clarified REQUIRED and OPTIONAL members of the "events <region>VA</region>
" array. Changed "SHOULD not" to "SHOULD NOT" in <xref target="sect-5"/>. Update <code>20171</code>
d normative references (5226-8126, 5988-8288, 7159-8259). Changed examples using <country>United States of America</country>
"ns1.xn--fo-5ja.example" to split URLs to avoid long lines.</t> </postal>
<t hangText="00:">Initial working group version. Added acknowledgment <email>andy@hxr.us</email>
s.</t> </address>
<t hangText="01:">Changed "The "lang" attribute may appear anywhere i </author>
n an object class or data structure except for in jCard objects" to "The "lang" </section>
attribute as defined in this section MAY appear anywhere in an object class or d </back>
ata structure, except for in jCard objects. jCard supports similar functionality </rfc>
by way of the LANGUAGE property parameter (see Section 5.1 of RFC 6350 [RFC
6350]". Changed "simple data types conveyed in JSON strings" to "simple data typ
es conveyed in JSON primitive types (strings, numbers, booleans, and null)". Cha
nged "In other words, servers are free to not include JSON members containing re
gistration data based on their own policies" to "In other words, servers are fre
e to omit unrequired/optional JSON members containing registration data based on
their own policies". Changed "This data structure appears only in the topmost J
SON object of a response" to "This data structure MUST appear in the topmost JSO
N object of a response". Changed "Some non-answer responses may return entity bo
dies with information that could be more descriptive" to "Some non-answer respon
ses MAY return entity bodies with information that could be more descriptive". C
hanged "The basic structure of that response is an object class containing an er
ror code number (corresponding to the HTTP response code) followed by a string n
amed "title" and an array of strings named "description"" to "The basic structur
e of that response is an object class containing a REQUIRED error code number (c
orresponding to the HTTP response code) followed by an OPTIONAL string named "ti
tle" and an OPTIONAL array of strings named "description"". Changed the "Autonom
ous System Number Object Class" section title to "The Autonomous System Number O
bject 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 per
iod after the eventDate description. Changed a "." to ";" in the description of
the "network" member of the domain object class. Changed "The high-level structu
re of the autnum object class consists of information about the network registra
tion" to "The high-level structure of the autnum object class consists of inform
ation about the autonomous system number registration". Changed "registry unique
" to "registry-unique".</t>
<t hangText="02:">Changed "registrant" to "registrar" in the desc
ription of the "transfer" event action to address erratum 6158. Added IANA instr
uctions to correct the description of the value in the registry. Added text to <
xref target="sect-4.2"/> to note that "self" and "related" "href" URIs MUST NOT
be the same. Added text to <xref target="sect-4.2"/> to describe return of IDNs
in LDH name format.</t>
<t hangText="03:">Added text to note that the "fn" member of a co
ntact object MAY be empty in <xref target="sect-3"/>.</t>
<t hangText="04:">Added text to clarify rdapConformance requireme
nts in <xref target="sect-4.1"/>.</t>
<t hangText="05:">Added "obsoletes 7483" to the headers, Abstract, an
d Introduction. Updated BCP14 template. Updated IANA Considerations to note that
this new RFC (a product of the REGEXT working group) replaces 7483. Changed "si
mple string" to "simple character string" in Sections 3 and 4.7. Clarified requi
rement for the "fn" member in Section 3. Modified the requirement for rdapConfor
mance placement in Section 4.1. Changed "jCard" to "vCard" LANGUAGE property ref
erence in Section 4.4. Changed "no use" to "little or no use" in Section 5.1. Ad
ded example line wrap note in Section 5.2. Modified the definition of "idnTable"
in Section 5.3. Modified the dsData and keyData examples in Section 5.3. Change
d "2001:c00::/23" to "2001:db8::/32" in Section 5.4. Expanded the definition of
"type" in Sections 5.4 and 5.5. Modified example autnums in Section 5.5. Added t
ext to the Security Considerations section to note that DNSSEC information retur
ned in a response can not be trusted directly.</t>
</list>
</t>
</section>
</back>
</rfc>
 End of changes. 280 change blocks. 
2197 lines changed or deleted 3345 lines changed or added

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