File: rfc9083.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (6377 lines) | stat: -rw-r--r-- 281,665 bytes
<!DOCTYPE html>
<html lang="en" class="RFC STD">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP)</title>
<meta content="Scott Hollenbeck" name="author">
<meta content="Andy Newton" name="author">
<meta content="
       
   This document describes JSON data structures representing
   registration information maintained by Regional Internet Registries
   (RIRs) and Domain Name Registries (DNRs).  These data structures are
   used to form Registration Data Access Protocol (RDAP) query
   responses. This document obsoletes RFC 7483. 
    " name="description">
<meta content="xml2rfc 3.8.0" name="generator">
<meta content="9083" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.8.0
    Python 3.6.10
    appdirs 1.4.4
    ConfigArgParse 1.2.3
    google-i18n-address 2.3.5
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.2
    kitchen 1.2.6
    lxml 4.4.2
    pycairo 1.19.0
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.3.1
    requests 2.22.0
    setuptools 40.6.2
    six 1.14.0
    WeasyPrint 51
-->
<link href="rfc9083.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

  NOTE: Changes at the bottom of this file overrides some earlier settings.

  Once the style has stabilized and has been adopted as an official RFC style,
  this can be consolidated so that style settings occur only in one place, but
  for now the contents of this file consists first of the initial CSS work as
  provided to the RFC Formatter (xml2rfc) work, followed by itemized and
  commented changes found necssary during the development of the v3
  formatters.

*/

/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */

@viewport {
  zoom: 1.0;
  width: extend-to-zoom;
}
@-ms-viewport {
  width: extend-to-zoom;
  zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
  max-width: 90%;
  margin: 1.5em auto;
  color: #222;
  background-color: #fff;
  font-size: 14px;
  font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
  line-height: 1.6;
  scroll-behavior: smooth;
}
.ears {
  display: none;
}

/* headings */
#title, h1, h2, h3, h4, h5, h6 {
  margin: 1em 0 0.5em;
  font-weight: bold;
  line-height: 1.3;
}
#title {
  clear: both;
  border-bottom: 1px solid #ddd;
  margin: 0 0 0.5em 0;
  padding: 1em 0 0.5em;
}
.author {
  padding-bottom: 4px;
}
h1 {
  font-size: 26px;
  margin: 1em 0;
}
h2 {
  font-size: 22px;
  margin-top: -20px;  /* provide offset for in-page anchors */
  padding-top: 33px;
}
h3 {
  font-size: 18px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h4 {
  font-size: 16px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h5, h6 {
  font-size: 14px;
}
#n-copyright-notice {
  border-bottom: 1px solid #ddd;
  padding-bottom: 1em;
  margin-bottom: 1em;
}
/* general structure */
p {
  padding: 0;
  margin: 0 0 1em 0;
  text-align: left;
}
div, span {
  position: relative;
}
div {
  margin: 0;
}
.alignRight.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignRight.art-text pre {
  padding: 0;
}
.alignRight {
  margin: 1em 0;
}
.alignRight > *:first-child {
  border: none;
  margin: 0;
  float: right;
  clear: both;
}
.alignRight > *:nth-child(2) {
  clear: both;
  display: block;
  border: none;
}
svg {
  display: block;
}
.alignCenter.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
  padding: 0;
}
.alignCenter {
  margin: 1em 0;
}
.alignCenter > *:first-child {
  border: none;
  /* this isn't optimal, but it's an existence proof.  PrinceXML doesn't
     support flexbox yet.
  */
  display: table;
  margin: 0 auto;
}

/* lists */
ol, ul {
  padding: 0;
  margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
  margin-left: 1em;
}
li {
  margin: 0 0 0.25em 0;
}
.ulCompact li {
  margin: 0;
}
ul.empty, .ulEmpty {
  list-style-type: none;
}
ul.empty li, .ulEmpty li {
  margin-top: 0.5em;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

/* definition lists */
dl {
}
dl > dt {
  float: left;
  margin-right: 1em;
}
/* 
dl.nohang > dt {
  float: none;
}
*/
dl > dd {
  margin-bottom: .8em;
  min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
  margin-bottom: 0em;
}
dl > dd > dl {
  margin-top: 0.5em;
  margin-bottom: 0em;
}

/* links */
a {
  text-decoration: none;
}
a[href] {
  color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
  background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
  color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
  background-color: transparent;
  cursor: default;
} */

/* Figures */
tt, code, pre, code {
  background-color: #f9f9f9;
  font-family: 'Roboto Mono', monospace;
}
pre {
  border: 1px solid #eee;
  margin: 0;
  padding: 1em;
}
img {
  max-width: 100%;
}
figure {
  margin: 0;
}
figure blockquote {
  margin: 0.8em 0.4em 0.4em;
}
figcaption {
  font-style: italic;
  margin: 0 0 1em 0;
}
@media screen {
  pre {
    overflow-x: auto;
    max-width: 100%;
    max-width: calc(100% - 22px);
  }
}

/* aside, blockquote */
aside, blockquote {
  margin-left: 0;
  padding: 1.2em 2em;
}
blockquote {
  background-color: #f9f9f9;
  color: #111; /* Arlen: WCAG 2019 */
  border: 1px solid #ddd;
  border-radius: 3px;
  margin: 1em 0;
}
cite {
  display: block;
  text-align: right;
  font-style: italic;
}

/* tables */
table {
  width: 100%;
  margin: 0 0 1em;
  border-collapse: collapse;
  border: 1px solid #eee;
}
th, td {
  text-align: left;
  vertical-align: top;
  padding: 0.5em 0.75em;
}
th {
  text-align: left;
  background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
  background-color: #f5f5f5;
}
table caption {
  font-style: italic;
  margin: 0;
  padding: 0;
  text-align: left;
}
table p {
  /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
     be allowed within tables more generally, it would be far better to select on a class. */
  margin: 0;
}

/* pilcrow */
a.pilcrow {
  color: #666; /* Arlen: AHDJ 2019 */
  text-decoration: none;
  visibility: hidden;
  user-select: none;
  -ms-user-select: none;
  -o-user-select:none;
  -moz-user-select: none;
  -khtml-user-select: none;
  -webkit-user-select: none;
  -webkit-touch-callout: none;
}
@media screen {
  aside:hover > a.pilcrow,
  p:hover > a.pilcrow,
  blockquote:hover > a.pilcrow,
  div:hover > a.pilcrow,
  li:hover > a.pilcrow,
  pre:hover > a.pilcrow {
    visibility: visible;
  }
  a.pilcrow:hover {
    background-color: transparent;
  }
}

/* misc */
hr {
  border: 0;
  border-top: 1px solid #eee;
}
.bcp14 {
  font-variant: small-caps;
}

.role {
  font-variant: all-small-caps;
}

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
#identifiers .authors .author {
  display: inline-block;
  margin-right: 1.5em;
}
#identifiers .authors .org {
  font-style: italic;
}

/* The prepared/rendered info at the very bottom of the page */
.docInfo {
  color: #666; /* Arlen: WCAG 2019 */
  font-size: 0.9em;
  font-style: italic;
  margin-top: 2em;
}
.docInfo .prepared {
  float: left;
}
.docInfo .prepared {
  float: right;
}

/* table of contents */
#toc  {
  padding: 0.75em 0 2em 0;
  margin-bottom: 1em;
}
nav.toc ul {
  margin: 0 0.5em 0 0;
  padding: 0;
  list-style: none;
}
nav.toc li {
  line-height: 1.3em;
  margin: 0.75em 0;
  padding-left: 1.2em;
  text-indent: -1.2em;
}
/* references */
.references dt {
  text-align: right;
  font-weight: bold;
  min-width: 7em;
}
.references dd {
  margin-left: 8em;
  overflow: auto;
}

.refInstance {
  margin-bottom: 1.25em;
}

.references .ascii {
  margin-bottom: 0.25em;
}

/* index */
.index ul {
  margin: 0 0 0 1em;
  padding: 0;
  list-style: none;
}
.index ul ul {
  margin: 0;
}
.index li {
  margin: 0;
  text-indent: -2em;
  padding-left: 2em;
  padding-bottom: 5px;
}
.indexIndex {
  margin: 0.5em 0 1em;
}
.index a {
  font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
  .index ul {
    -moz-column-count: 2;
    -moz-column-gap: 20px;
  }
  .index ul ul {
    -moz-column-count: 1;
    -moz-column-gap: 0;
  }
}

/* authors */
address.vcard {
  font-style: normal;
  margin: 1em 0;
}

address.vcard .nameRole {
  font-weight: 700;
  margin-left: 0;
}
address.vcard .label {
  font-family: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

/* temporary notes */
.rfcEditorRemove::before {
  position: absolute;
  top: 0.2em;
  right: 0.2em;
  padding: 0.2em;
  content: "The RFC Editor will remove this note";
  color: #9e2a00; /* Arlen: WCAG 2019 */
  background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
  position: relative;
  padding-top: 1.8em;
  background-color: #ffd; /* Arlen: WCAG 2019 */
  border-radius: 3px;
}
.cref {
  background-color: #ffd; /* Arlen: WCAG 2019 */
  padding: 2px 4px;
}
.crefSource {
  font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
  body {
    padding-top: 2em;
  }
  #title {
    padding: 1em 0;
  }
  h1 {
    font-size: 24px;
  }
  h2 {
    font-size: 20px;
    margin-top: -18px;  /* provide offset for in-page anchors */
    padding-top: 38px;
  }
  #identifiers dd {
    max-width: 60%;
  }
  #toc {
    position: fixed;
    z-index: 2;
    top: 0;
    right: 0;
    padding: 0;
    margin: 0;
    background-color: inherit;
    border-bottom: 1px solid #ccc;
  }
  #toc h2 {
    margin: -1px 0 0 0;
    padding: 4px 0 4px 6px;
    padding-right: 1em;
    min-width: 190px;
    font-size: 1.1em;
    text-align: right;
    background-color: #444;
    color: white;
    cursor: pointer;
  }
  #toc h2::before { /* css hamburger */
    float: right;
    position: relative;
    width: 1em;
    height: 1px;
    left: -164px;
    margin: 6px 0 0 0;
    background: white none repeat scroll 0 0;
    box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
    content: "";
  }
  #toc nav {
    display: none;
    padding: 0.5em 1em 1em;
    overflow: auto;
    height: calc(100vh - 48px);
    border-left: 1px solid #ddd;
  }
}

/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
  body {
    max-width: 724px;
    margin: 42px auto;
    padding-left: 1.5em;
    padding-right: 29em;
  }
  #toc {
    position: fixed;
    top: 42px;
    right: 42px;
    width: 25%;
    margin: 0;
    padding: 0 1em;
    z-index: 1;
  }
  #toc h2 {
    border-top: none;
    border-bottom: 1px solid #ddd;
    font-size: 1em;
    font-weight: normal;
    margin: 0;
    padding: 0.25em 1em 1em 0;
  }
  #toc nav {
    display: block;
    height: calc(90vh - 84px);
    bottom: 0;
    padding: 0.5em 0 0;
    overflow: auto;
  }
  img { /* future proofing */
    max-width: 100%;
    height: auto;
  }
}

/* pagination */
@media print {
  body {

    width: 100%;
  }
  p {
    orphans: 3;
    widows: 3;
  }
  #n-copyright-notice {
    border-bottom: none;
  }
  #toc, #n-introduction {
    page-break-before: always;
  }
  #toc {
    border-top: none;
    padding-top: 0;
  }
  figure, pre {
    page-break-inside: avoid;
  }
  figure {
    overflow: scroll;
  }
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
  }
  h2+*, h3+*, h4+*, h5+*, h6+* {
    page-break-before: avoid;
  }
  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 10pt;
  }
  table {
    border: 1px solid #ddd;
  }
  td {
    border-top: 1px solid #ddd;
  }
}

/* This is commented out here, as the string-set: doesn't
   pass W3C validation currently */
/*
.ears thead .left {
  string-set: ears-top-left content();
}

.ears thead .center {
  string-set: ears-top-center content();
}

.ears thead .right {
  string-set: ears-top-right content();
}

.ears tfoot .left {
  string-set: ears-bottom-left content();
}

.ears tfoot .center {
  string-set: ears-bottom-center content();
}

.ears tfoot .right {
  string-set: ears-bottom-right content();
}
*/

@page :first {
  padding-top: 0;
  @top-left {
    content: normal;
    border: none;
  }
  @top-center {
    content: normal;
    border: none;
  }
  @top-right {
    content: normal;
    border: none;
  }
}

@page {
  size: A4;
  margin-bottom: 45mm;
  padding-top: 20px;
  /* The follwing is commented out here, but set appropriately by in code, as
     the content depends on the document */
  /*
  @top-left {
    content: 'Internet-Draft';
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-left {
    content: string(ears-top-left);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-center {
    content: string(ears-top-center);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-right {
    content: string(ears-top-right);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @bottom-left {
    content: string(ears-bottom-left);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-center {
    content: string(ears-bottom-center);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-right {
      content: '[Page ' counter(page) ']';
      vertical-align: top;
      border-top: solid 1px #ccc;
  }
  */

}

/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
  z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
  clear: both;
}


/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
  vertical-align: top;
}

/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
  width: 8em;
}

/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
  margin-left: 1em;
}

/* Give floating toc a background color (needed when it's a div inside section */
#toc {
  background-color: white;
}

/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
  #toc h2 a,
  #toc h2 a:link,
  #toc h2 a:focus,
  #toc h2 a:hover,
  #toc a.toplink,
  #toc a.toplink:hover {
    color: white;
    background-color: #444;
    text-decoration: none;
  }
}

/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
  #toc {
    padding: 0 0 1em 1em;
  }
}

/* Style section numbers with more space between number and title */
.section-number {
  padding-right: 0.5em;
}

/* prevent monospace from becoming overly large */
tt, code, pre, code {
  font-size: 95%;
}

/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
  line-height: 1.12;
}


/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
  float: right;
  margin-right: 0.5em;
}

/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
  float: left;
  margin-right: 1em;
}
dl.dlNewline > dt {
  float: none;
}

/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
  text-align: left;
}
table td.text-center,
table th.text-center {
  text-align: center;
}
table td.text-right,
table th.text-right {
  text-align: right;
}

/* Make the alternative author contact informatio look less like just another
   author, and group it closer with the primary author contact information */
.alternative-contact {
  margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
  margin: 0 0 0 2em;
}

/* With it being possible to set tables with alignment
  left, center, and right, { width: 100%; } does not make sense */
table {
  width: auto;
}

/* Avoid reference text that sits in a block with very wide left margin,
   because of a long floating dt label.*/
.references dd {
  overflow: visible;
}

/* Control caption placement */
caption {
  caption-side: bottom;
}

/* Limit the width of the author address vcard, so names in right-to-left
   script don't end up on the other side of the page. */

address.vcard {
  max-width: 30em;
  margin-right: auto;
}

/* For address alignment dependent on LTR or RTL scripts */
address div.left {
  text-align: left;
}
address div.right {
  text-align: right;
}

/* Provide table alignment support.  We can't use the alignX classes above
   since they do unwanted things with caption and other styling. */
table.right {
 margin-left: auto;
 margin-right: 0;
}
table.center {
 margin-left: auto;
 margin-right: auto;
}
table.left {
 margin-left: 0;
 margin-right: auto;
}

/* Give the table caption label the same styling as the figcaption */
caption a[href] {
  color: #222;
}

@media print {
  .toplink {
    display: none;
  }

  /* avoid overwriting the top border line with the ToC header */
  #toc {
    padding-top: 1px;
  }

  /* Avoid page breaks inside dl and author address entries */
  .vcard {
    page-break-inside: avoid;
  }

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: avoid-page;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
  margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
  margin-bottom: 0;
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc9083" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-rfc7483bis-05" rel="prev">
  </head>
<body>
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 9083</td>
<td class="center">RDAP JSON Responses</td>
<td class="right">June 2021</td>
</tr></thead>
<tfoot><tr>
<td class="left">Hollenbeck &amp; Newton</td>
<td class="center">Standards Track</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Engineering Task Force (IETF)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9083" class="eref">9083</a></dd>
<dt class="label-std">STD:</dt>
<dd class="std">95</dd>
<dt class="label-obsoletes">Obsoletes:</dt>
<dd class="obsoletes">
<a href="https://www.rfc-editor.org/rfc/rfc7483" class="eref">7483</a> </dd>
<dt class="label-category">Category:</dt>
<dd class="category">Standards Track</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2021-06" class="published">June 2021</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">S. Hollenbeck</div>
<div class="org">Verisign Labs</div>
</div>
<div class="author">
      <div class="author-name">A. Newton</div>
<div class="org">AWS</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9083</h1>
<h1 id="title">JSON Responses for the Registration Data Access Protocol (RDAP)</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">
   This document describes JSON data structures representing
   registration information maintained by Regional Internet Registries
   (RIRs) and Domain Name Registries (DNRs).  These data structures are
   used to form Registration Data Access Protocol (RDAP) query
   responses. This document obsoletes RFC 7483.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="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.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="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
            <span><a href="https://www.rfc-editor.org/info/rfc9083">https://www.rfc-editor.org/info/rfc9083</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2021 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) 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.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.1.2.1">
                <p id="section-toc.1-1.1.2.1.1" class="keepWithNext"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-terminology-and-definitions" class="xref">Terminology and Definitions</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.1.2.2">
                <p id="section-toc.1-1.1.2.2.1" class="keepWithNext"><a href="#section-1.2" class="xref">1.2</a>.  <a href="#name-data-model" class="xref">Data Model</a></p>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-use-of-json" class="xref">Use of JSON</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.2.2.1">
                <p id="section-toc.1-1.2.2.1.1"><a href="#section-2.1" class="xref">2.1</a>.  <a href="#name-naming" class="xref">Naming</a></p>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-common-data-types" class="xref">Common Data Types</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-common-data-structures" class="xref">Common Data Structures</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.4.2.1">
                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-rdap-conformance" class="xref">RDAP Conformance</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.2">
                <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-links" class="xref">Links</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.3">
                <p id="section-toc.1-1.4.2.3.1"><a href="#section-4.3" class="xref">4.3</a>.  <a href="#name-notices-and-remarks" class="xref">Notices and Remarks</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.4">
                <p id="section-toc.1-1.4.2.4.1"><a href="#section-4.4" class="xref">4.4</a>.  <a href="#name-language-identifier" class="xref">Language Identifier</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.5">
                <p id="section-toc.1-1.4.2.5.1"><a href="#section-4.5" class="xref">4.5</a>.  <a href="#name-events" class="xref">Events</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.6">
                <p id="section-toc.1-1.4.2.6.1"><a href="#section-4.6" class="xref">4.6</a>.  <a href="#name-status" class="xref">Status</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.7">
                <p id="section-toc.1-1.4.2.7.1"><a href="#section-4.7" class="xref">4.7</a>.  <a href="#name-port-43-whois-server" class="xref">Port 43 WHOIS Server</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.8">
                <p id="section-toc.1-1.4.2.8.1"><a href="#section-4.8" class="xref">4.8</a>.  <a href="#name-public-ids" class="xref">Public IDs</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.9">
                <p id="section-toc.1-1.4.2.9.1"><a href="#section-4.9" class="xref">4.9</a>.  <a href="#name-object-class-name" class="xref">Object Class Name</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.4.2.10">
                <p id="section-toc.1-1.4.2.10.1"><a href="#section-4.10" class="xref">4.10</a>. <a href="#name-an-example" class="xref">An Example</a></p>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-object-classes" class="xref">Object Classes</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.5.2.1">
                <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-the-entity-object-class" class="xref">The Entity Object Class</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.5.2.2">
                <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-the-nameserver-object-class" class="xref">The Nameserver Object Class</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.5.2.3">
                <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-the-domain-object-class" class="xref">The Domain Object Class</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.5.2.4">
                <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-the-ip-network-object-class" class="xref">The IP Network Object Class</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.5.2.5">
                <p id="section-toc.1-1.5.2.5.1"><a href="#section-5.5" class="xref">5.5</a>.  <a href="#name-the-autonomous-system-numbe" class="xref">The Autonomous System Number Object Class</a></p>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-error-response-body" class="xref">Error Response Body</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-responding-to-help-queries" class="xref">Responding to Help Queries</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-responding-to-searches" class="xref">Responding To Searches</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-indicating-truncated-respon" class="xref">Indicating Truncated Responses</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.10.2.1">
                <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-rdap-json-media-type-regist" class="xref">RDAP JSON Media Type Registration</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.10.2.2">
                <p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>.  <a href="#name-json-values-registry" class="xref">JSON Values Registry</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.10.2.2.2.1">
                    <p id="section-toc.1-1.10.2.2.2.1.1"><a href="#section-10.2.1" class="xref">10.2.1</a>.  <a href="#name-notice-and-remark-types" class="xref">Notice and Remark Types</a></p>
</li>
                  <li class="toc compact ulEmpty" id="section-toc.1-1.10.2.2.2.2">
                    <p id="section-toc.1-1.10.2.2.2.2.1"><a href="#section-10.2.2" class="xref">10.2.2</a>.  <a href="#name-status-2" class="xref">Status</a></p>
</li>
                  <li class="toc compact ulEmpty" id="section-toc.1-1.10.2.2.2.3">
                    <p id="section-toc.1-1.10.2.2.2.3.1"><a href="#section-10.2.3" class="xref">10.2.3</a>.  <a href="#name-event-actions" class="xref">Event Actions</a></p>
</li>
                  <li class="toc compact ulEmpty" id="section-toc.1-1.10.2.2.2.4">
                    <p id="section-toc.1-1.10.2.2.2.4.1"><a href="#section-10.2.4" class="xref">10.2.4</a>.  <a href="#name-roles" class="xref">Roles</a></p>
</li>
                  <li class="toc compact ulEmpty" id="section-toc.1-1.10.2.2.2.5">
                    <p id="section-toc.1-1.10.2.2.2.5.1"><a href="#section-10.2.5" class="xref">10.2.5</a>.  <a href="#name-variant-relations" class="xref">Variant Relations</a></p>
</li>
                </ul>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-11" class="xref">11</a>. <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-12" class="xref">12</a>. <a href="#name-internationalization-consid" class="xref">Internationalization Considerations</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.12.2.1">
                <p id="section-toc.1-1.12.2.1.1"><a href="#section-12.1" class="xref">12.1</a>.  <a href="#name-character-encoding" class="xref">Character Encoding</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.12.2.2">
                <p id="section-toc.1-1.12.2.2.1"><a href="#section-12.2" class="xref">12.2</a>.  <a href="#name-uris-and-iris" class="xref">URIs and IRIs</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.12.2.3">
                <p id="section-toc.1-1.12.2.3.1"><a href="#section-12.3" class="xref">12.3</a>.  <a href="#name-language-tags" class="xref">Language Tags</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.12.2.4">
                <p id="section-toc.1-1.12.2.4.1"><a href="#section-12.4" class="xref">12.4</a>.  <a href="#name-internationalized-domain-na" class="xref">Internationalized Domain Names</a></p>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.13">
            <p id="section-toc.1-1.13.1"><a href="#section-13" class="xref">13</a>. <a href="#name-privacy-considerations" class="xref">Privacy Considerations</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.14">
            <p id="section-toc.1-1.14.1"><a href="#section-14" class="xref">14</a>. <a href="#name-references" class="xref">References</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.14.2.1">
                <p id="section-toc.1-1.14.2.1.1"><a href="#section-14.1" class="xref">14.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.14.2.2">
                <p id="section-toc.1-1.14.2.2.1"><a href="#section-14.2" class="xref">14.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.15">
            <p id="section-toc.1-1.15.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-suggested-data-modeling-wit" class="xref">Suggested Data Modeling with the Entity Object Class</a></p>
<ul class="toc compact ulEmpty">
<li class="toc compact ulEmpty" id="section-toc.1-1.15.2.1">
                <p id="section-toc.1-1.15.2.1.1"><a href="#section-a.1" class="xref">A.1</a>.  <a href="#name-registrants-and-contacts" class="xref">Registrants and Contacts</a></p>
</li>
              <li class="toc compact ulEmpty" id="section-toc.1-1.15.2.2">
                <p id="section-toc.1-1.15.2.2.1"><a href="#section-a.2" class="xref">A.2</a>.  <a href="#name-registrars" class="xref">Registrars</a></p>
</li>
            </ul>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.16">
            <p id="section-toc.1-1.16.1"><a href="#section-appendix.b" class="xref">Appendix B</a>.  <a href="#name-modeling-events" class="xref">Modeling Events</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.17">
            <p id="section-toc.1-1.17.1"><a href="#section-appendix.c" class="xref">Appendix C</a>.  <a href="#name-structured-vs-unstructured-" class="xref">Structured vs. Unstructured Addresses</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.18">
            <p id="section-toc.1-1.18.1"><a href="#section-appendix.d" class="xref">Appendix D</a>.  <a href="#name-secure-dns" class="xref">Secure DNS</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.19">
            <p id="section-toc.1-1.19.1"><a href="#section-appendix.e" class="xref">Appendix E</a>.  <a href="#name-motivations-for-using-json" class="xref">Motivations for Using JSON</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.20">
            <p id="section-toc.1-1.20.1"><a href="#section-appendix.f" class="xref">Appendix F</a>.  <a href="#name-changes-from-rfc-7483" class="xref">Changes from RFC 7483</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.21">
            <p id="section-toc.1-1.21.1"><a href="#section-appendix.g" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
</li>
          <li class="toc compact ulEmpty" id="section-toc.1-1.22">
            <p id="section-toc.1-1.22.1"><a href="#section-appendix.h" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="sect-1">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">
   This document describes responses in the JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span> format for
   the queries as defined by the Registration Data Access Protocol Query
   Format <span>[<a href="#RFC9082" class="xref">RFC9082</a>]</span>.  A communication protocol for exchanging queries
   and responses is described in <span>[<a href="#RFC7480" class="xref">RFC7480</a>]</span>. This document obsoletes RFC 7483.<a href="#section-1-1" class="pilcrow">¶</a></p>
<div id="sect-1.1">
<section id="section-1.1">
        <h3 id="name-terminology-and-definitions">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-terminology-and-definitions" class="section-name selfRef">Terminology and Definitions</a>
        </h3>
<p id="section-1.1-1">
   The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>",
   "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
   described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they
   appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
<p id="section-1.1-2">
   The following list describes terminology and definitions used
   throughout this document:<a href="#section-1.1-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-1.1-3">
          <dt id="section-1.1-3.1">DNR:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.2">
 Domain Name Registry or Domain Name Registrar<a href="#section-1.1-3.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-3.3">LDH:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.4">
 letters, digits, hyphen<a href="#section-1.1-3.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-3.5">member:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.6">
 data found within an object as defined by JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span><a href="#section-1.1-3.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-3.7">object:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.8">
 a data structure as defined by JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span><a href="#section-1.1-3.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-3.9">object class:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.10">
 the definition of members that may be found in JSON
 objects described in this document<a href="#section-1.1-3.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-3.11">object instance:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.12">
 an instantiation or specific instance of an object
 class<a href="#section-1.1-3.12" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-3.13">RDAP:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.14">
 Registration Data Access Protocol<a href="#section-1.1-3.14" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-1.1-3.15">RIR:</dt>
          <dd style="margin-left: 0.5em" id="section-1.1-3.16">
 Regional Internet Registry<a href="#section-1.1-3.16" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="sect-1.2">
<section id="section-1.2">
        <h3 id="name-data-model">
<a href="#section-1.2" class="section-number selfRef">1.2. </a><a href="#name-data-model" class="section-name selfRef">Data Model</a>
        </h3>
<p id="section-1.2-1">
   The data model for JSON responses is specified in five sections:<a href="#section-1.2-1" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-1.2-2">
<li id="section-1.2-2.1">simple data types conveyed in JSON
 primitive types (strings, numbers, booleans, and null)<a href="#section-1.2-2.1" class="pilcrow">¶</a>
</li>
          <li id="section-1.2-2.2">data structures specified as JSON arrays or objects that are used
       repeatedly when building up larger objects<a href="#section-1.2-2.2" class="pilcrow">¶</a>
</li>
          <li id="section-1.2-2.3">object classes representing structured data corresponding to a
       lookup of a single object<a href="#section-1.2-2.3" class="pilcrow">¶</a>
</li>
          <li id="section-1.2-2.4">arrays of objects representing structured data corresponding to a
       search for multiple objects<a href="#section-1.2-2.4" class="pilcrow">¶</a>
</li>
          <li id="section-1.2-2.5">the response to an error<a href="#section-1.2-2.5" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-1.2-3">
   The object classes represent responses for two major categories of
   data: responses returned by RIRs for registration data related to IP
   addresses, reverse DNS names, and Autonomous System numbers and
   responses returned by DNRs for registration data related to forward
   DNS names.  The following object classes are returned by both RIRs
   and DNRs:<a href="#section-1.2-3" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-1.2-4">
<li id="section-1.2-4.1">domains<a href="#section-1.2-4.1" class="pilcrow">¶</a>
</li>
          <li id="section-1.2-4.2">nameservers<a href="#section-1.2-4.2" class="pilcrow">¶</a>
</li>
          <li id="section-1.2-4.3">entities<a href="#section-1.2-4.3" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-1.2-5">
   The information served by both RIRs and DNRs for these object classes
   overlap extensively and are given in this document as a unified model
   for both classes of service.<a href="#section-1.2-5" class="pilcrow">¶</a></p>
<p id="section-1.2-6">
   In addition to the object classes listed above, RIRs also serve the
   following object classes:<a href="#section-1.2-6" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-1.2-7">
<li id="section-1.2-7.1">IP networks<a href="#section-1.2-7.1" class="pilcrow">¶</a>
</li>
          <li id="section-1.2-7.2">Autonomous System numbers<a href="#section-1.2-7.2" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-1.2-8">
   Object classes defined in this document represent a minimal set of
   what a compliant client/server needs to understand to function
   correctly; however, some deployments may want to include additional
   object classes to suit individual needs.  Anticipating this need for
   extension, <a href="#sect-2.1" class="xref">Section 2.1</a> of this document defines a mechanism for
   extending the JSON objects that are described in this document.<a href="#section-1.2-8" class="pilcrow">¶</a></p>
<p id="section-1.2-9">
   Positive responses take two forms.  A response to a lookup of a
   single object in the registration system yields a JSON object, which
   is the subject of the lookup.  A response to a search for multiple
   objects yields a JSON object that contains an array of JSON objects
   that are the subject of the search.  In each type of response, other
   data structures are present within the topmost JSON object.<a href="#section-1.2-9" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="sect-2">
<section id="section-2">
      <h2 id="name-use-of-json">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-use-of-json" class="section-name selfRef">Use of JSON</a>
      </h2>
<div id="sect-2.1">
<section id="section-2.1">
        <h3 id="name-naming">
<a href="#section-2.1" class="section-number selfRef">2.1. </a><a href="#name-naming" class="section-name selfRef">Naming</a>
        </h3>
<p id="section-2.1-1">
   Clients of these JSON responses <span class="bcp14">SHOULD</span> ignore unrecognized JSON
   members in responses.  Servers can insert members into the JSON
   responses, which are not specified in this document, but that does
   not constitute an error in the response.  Servers that insert such
   unspecified members into JSON responses <span class="bcp14">SHOULD</span> have member names
   prefixed with a short identifier followed by an underscore followed
   by a meaningful name.  It has been observed that these short
   identifiers aid software implementers with identifying the
   specification of the JSON member, and failure to use one could cause
   an implementer to assume the server is erroneously using a name from
   this specification.  This allowance does not apply to jCard <span>[<a href="#RFC7095" class="xref">RFC7095</a>]</span>
   objects.  The full JSON name (the prefix plus the underscore plus the
   meaningful name) <span class="bcp14">SHOULD</span> adhere to the character and name limitations
   of the prefix registry described in <span>[<a href="#RFC7480" class="xref">RFC7480</a>]</span>.  Failure to use these
   limitations could result in slower adoption as these limitations have
   been observed to aid some client programming models.<a href="#section-2.1-1" class="pilcrow">¶</a></p>
<p id="section-2.1-2">
   Consider the following JSON response with JSON members, all of which
   are specified in this document.<a href="#section-2.1-2" class="pilcrow">¶</a></p>
<div id="ure-1">
<figure id="figure-1">
          <div id="section-2.1-3.1">
<pre class="sourcecode lang-json">
{
  "handle" : "ABC123",
  "remarks" :
  [
    {
      "description" :
      [
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a></figcaption></figure>
</div>
<p id="section-2.1-4">
   If The Registry of the Moon desires to express information not found
   in this specification, it might select "lunarNIC" as its identifying
   prefix and insert, as an example, the member named
   "lunarNIC_beforeOneSmallStep" to signify registrations occurring
   before the first moon landing and the member named
   "lunarNIC_harshMistressNotes" that contains other descriptive text.<a href="#section-2.1-4" class="pilcrow">¶</a></p>
<p id="section-2.1-5">
   Consider the following JSON response with JSON names, some of which
   should be ignored by clients without knowledge of their meaning.<a href="#section-2.1-5" class="pilcrow">¶</a></p>
<div id="ure-2">
<figure id="figure-2">
          <div id="section-2.1-6.1">
<pre class="sourcecode lang-json">
{
  "handle" : "ABC123",
  "lunarNIC_beforeOneSmallStep" : "TRUE THAT!",
  "remarks" :
  [
    {
      "description" :
      [
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ],
  "lunarNIC_harshMistressNotes" :
  [
    "In space,",
    "nobody can hear you scream."
  ]
}
</pre>
</div>
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a></figcaption></figure>
</div>
<p id="section-2.1-7">
   Insertion of unrecognized members ignored by clients may also be used
   for future revisions to this specification.<a href="#section-2.1-7" class="pilcrow">¶</a></p>
<p id="section-2.1-8">
   Clients processing JSON responses need to be prepared for members
   representing registration data specified in this document to be
   absent from a response. In other words, servers are free to omit
   unrequired/optional JSON members containing registration data based
   on their own policies.<a href="#section-2.1-8" class="pilcrow">¶</a></p>
<p id="section-2.1-9">
   Finally, all JSON names specified in this document are case
   sensitive.  Both servers and clients <span class="bcp14">MUST</span> transmit and process them
   using the specified character case.<a href="#section-2.1-9" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="sect-3">
<section id="section-3">
      <h2 id="name-common-data-types">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-common-data-types" class="section-name selfRef">Common Data Types</a>
      </h2>
<p id="section-3-1">
   JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span> defines the data types of a number, character string,
   boolean, array, object, and null.  This section describes the
   semantics and/or syntax reference for common, JSON character strings
   used in this document.<a href="#section-3-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-3-2">
        <dt id="section-3-2.1">handle:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.2">
 DNRs and RIRs have registry-unique identifiers that
 may be used to specifically reference an object
 instance.  The semantics of this data type as found
 in this document are to be a registry-unique
 reference to the closest enclosing object where the
 value is found.  The data type names "registryId",
 "roid", "nic-handle", "registrationNo", etc., are
 terms often synonymous with this data type.  In
 this document, the term "handle" is used.  The term
 exposed to users by clients is a presentation issue
 beyond the scope of this document. This value is a
 simple character string.<a href="#section-3-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.3">IPv4 addresses:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.4">
 The representation of IPv4 addresses in this
 document uses the dotted-decimal notation.  An
                     example of this textual representation is
                     "192.0.2.0".<a href="#section-3-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.5">IPv6 addresses:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.6">
 The representation of IPv6 addresses in this
 document follow the forms outlined in <span>[<a href="#RFC5952" class="xref">RFC5952</a>]</span>.
                     An example of this textual representation is
                     "2001:db8::1:0:0:1".<a href="#section-3-2.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.7">country codes:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.8">
 Where the identity of a geopolitical nation or
 country is needed, these identities are represented
    with the alpha-2 or two-character country code
    designation as defined in <span>[<a href="#ISO.3166.2020" class="xref">ISO.3166.2020</a>]</span>.  The
    alpha-2 representation is used because it is freely
    available, whereas the alpha-3 and numeric-3
    standards are not.<a href="#section-3-2.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.9">LDH names:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.10">
 Textual representations of DNS names where the
 labels of the domain are all "letters, digits, hyphen" labels as described by <span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span>.  Trailing
    periods are optional.<a href="#section-3-2.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.11">Unicode names:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.12">
 Textual representations of DNS names where one or
 more of the labels are U-labels as described by
    <span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span>.  Trailing periods are optional.<a href="#section-3-2.12" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.13">dates and times:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.14">
 The syntax for values denoting dates and times is
 defined in <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span>.<a href="#section-3-2.14" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-3-2.15">URIs:</dt>
        <dd style="margin-left: 9.0em" id="section-3-2.16">
 The syntax for values denoting a Uniform Resource
 Identifier (URI) is defined by <span>[<a href="#RFC3986" class="xref">RFC3986</a>]</span>.<a href="#section-3-2.16" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
<p id="section-3-3">
   Contact information is defined using jCards as described in
   <span>[<a href="#RFC7095" class="xref">RFC7095</a>]</span>. The "fn" member is required and <span class="bcp14">MUST NOT</span> be null according to <span>[<a href="#RFC6350" class="xref">RFC6350</a>]</span>. An empty
   "fn" member <span class="bcp14">MAY</span> be used when the contact name does not exist
   or is redacted.<a href="#section-3-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-4">
<section id="section-4">
      <h2 id="name-common-data-structures">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-common-data-structures" class="section-name selfRef">Common Data Structures</a>
      </h2>
<p id="section-4-1">
   This section defines common data structures used in responses and
   object classes.<a href="#section-4-1" class="pilcrow">¶</a></p>
<div id="sect-4.1">
<section id="section-4.1">
        <h3 id="name-rdap-conformance">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-rdap-conformance" class="section-name selfRef">RDAP Conformance</a>
        </h3>
<p id="section-4.1-1">
   The data structure named "rdapConformance" is an array of strings,
   each providing a hint as to the specifications used in the
   construction of the response.  This data structure <span class="bcp14">MUST</span> appear
   in the topmost JSON object of a response and <span class="bcp14">MUST NOT</span> appear
   anywhere else. A response to a "help"
   request will include identifiers for all of the specifications
   supported by the server. A response to any other request will
   include only identifiers for the specifications used in the
   construction of the response. The set of returned identifiers
   <span class="bcp14">MAY</span> vary depending on the authorization level of the client.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<p id="section-4.1-2">
   An example rdapConformance data structure:<a href="#section-4.1-2" class="pilcrow">¶</a></p>
<div id="ure-3">
<figure id="figure-3">
          <div id="section-4.1-3.1">
<pre class="sourcecode lang-json">
"rdapConformance" :
[
  "rdap_level_0"
]
</pre>
</div>
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a></figcaption></figure>
</div>
<p id="section-4.1-4">
   The string literal "rdap_level_0" signifies conformance with this
   specification.  When custom JSON values are inserted into responses,
   conformance to those custom specifications <span class="bcp14">MUST</span> be indicated by including
   a unique string literal value registered in the IANA RDAP Extensions
   registry specified in <span>[<a href="#RFC7480" class="xref">RFC7480</a>]</span>.  For example, if the fictional
   Registry of the Moon wants to signify that their JSON responses are
   conformant with their registered extensions, the string used might be
   "lunarNIC_level_0".  These registered values aid the identification of
   specifications for software implementers, and failure to use them
   could result in slower adoption of extensions.<a href="#section-4.1-4" class="pilcrow">¶</a></p>
<p id="section-4.1-5">
   Example rdapConformance structure with custom extensions noted:<a href="#section-4.1-5" class="pilcrow">¶</a></p>
<div id="ure-4">
<figure id="figure-4">
          <div id="section-4.1-6.1">
<pre class="sourcecode lang-json">
"rdapConformance" :
[
  "rdap_level_0",
  "lunarNIC_level_0"
]
</pre>
</div>
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-4.2">
<section id="section-4.2">
        <h3 id="name-links">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-links" class="section-name selfRef">Links</a>
        </h3>
<p id="section-4.2-1">
   The "links" array is found in data structures to signify links to
   other resources on the Internet.  The relationship of these links is
   defined by the IANA registry described by <span>[<a href="#RFC8288" class="xref">RFC8288</a>]</span>.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
<p id="section-4.2-2">The following is an example of the link structure:<a href="#section-4.2-2" class="pilcrow">¶</a></p>
<div id="ure-5">
<figure id="figure-5">
          <div id="section-4.2-3.1">
<pre class="sourcecode lang-json">
    {
      "value" : "https://example.com/context_uri",
      "rel" : "self",
      "href" : "https://example.com/target_uri",
      "hreflang" : [ "en", "ch" ],
      "title" : "title",
      "media" : "screen",
      "type" : "application/json"
    }
</pre>
</div>
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a></figcaption></figure>
</div>
<p id="section-4.2-4">
   The JSON name/values of "rel", "href", "hreflang", "title", "media",
   and "type" correspond to values found in <span><a href="https://www.rfc-editor.org/rfc/rfc8288#section-3" class="relref">Section 3</a> of [<a href="#RFC8288" class="xref">RFC8288</a>]</span>.  The
   "value" JSON value is the context URI as described by <span>[<a href="#RFC8288" class="xref">RFC8288</a>]</span>.  The
   "value", "rel", and "href" JSON values <span class="bcp14">MUST</span> be specified.  All other JSON values are
   <span class="bcp14">OPTIONAL</span>. A "related" link relation <span class="bcp14">MUST NOT</span> include an "href" URI that is the
   same as the "self" link relation "href" URI to reduce the risk of infinite client
   processing loops. Internationalized Domain Names (IDNs) returned in URIs <span class="bcp14">SHOULD</span>
   be consistently returned in LDH name format to allow clients to process these IDNs
   according to their capabilities.<a href="#section-4.2-4" class="pilcrow">¶</a></p>
<p id="section-4.2-5">
   This is an example of the "links" array as it might be found in an
   object class:<a href="#section-4.2-5" class="pilcrow">¶</a></p>
<div id="ure-6">
<figure id="figure-6">
          <div id="section-4.2-6.1">
<pre class="sourcecode lang-json">
    "links" :
    [
        {
          "value" : "https://example.com/ip/2001:db8::123",
          "rel" : "self",
          "href" : "https://example.com/ip/2001:db8::123",
          "type" : "application/rdap+json"
        },
        {
          "value" : "https://example.com/ip/2001:db8::123",
          "rel" : "up",
          "href" : "https://example.com/ip/2001:db8::/48",
          "type" : "application/rdap+json"
        }

    ]
</pre>
</div>
<figcaption><a href="#figure-6" class="selfRef">Figure 6</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-4.3">
<section id="section-4.3">
        <h3 id="name-notices-and-remarks">
<a href="#section-4.3" class="section-number selfRef">4.3. </a><a href="#name-notices-and-remarks" class="section-name selfRef">Notices and Remarks</a>
        </h3>
<p id="section-4.3-1">
   The "notices" and "remarks" data structures take the same form.  The
   notices structure denotes information about the service providing
   RDAP information and/or information about the entire response,
   whereas the remarks structure denotes information about the object
   class that contains it (see <a href="#sect-5" class="xref">Section 5</a> regarding object classes).<a href="#section-4.3-1" class="pilcrow">¶</a></p>
<p id="section-4.3-2">Both are arrays of objects.  Each object contains a "title" string
   representing the title of the object, a "type" string denoting a
   registered type of remark or notice (see <a href="#sect-10.2.1" class="xref">Section 10.2.1</a>), an
   array of strings named "description" for the purposes of conveying any
   descriptive text, and a "links" array as described in <a href="#sect-4.2" class="xref">Section 4.2</a>. The
   "description" array <span class="bcp14">MUST</span> be included. All other JSON values are <span class="bcp14">OPTIONAL</span>.<a href="#section-4.3-2" class="pilcrow">¶</a></p>
<p id="section-4.3-3">
   An example of the notices data structure:<a href="#section-4.3-3" class="pilcrow">¶</a></p>
<div id="ure-7">
<figure id="figure-7">
          <div id="section-4.3-4.1">
<pre class="sourcecode lang-json">
"notices" :
[
  {
    "title" : "Terms of Use",
    "description" :
    [
      "Service subject to The Registry of the Moon's TOS.",
      "Copyright (c) 2020 LunarNIC"
    ],
    "links" :
    [
      {
        "value" : "https://example.net/entity/XXXX",
        "rel" : "alternate",
        "type" : "text/html",
        "href" : "https://www.example.com/terms_of_use.html"
      }
    ]
  }
]
</pre>
</div>
<figcaption><a href="#figure-7" class="selfRef">Figure 7</a></figcaption></figure>
</div>
<p id="section-4.3-5">
   It is the job of the clients to determine line breaks, spacing, and
   display issues for sentences within the character strings of the
   "description" array.  Each string in the "description" array contains
   a single complete division of human-readable text indicating to
   clients where there are semantic breaks.<a href="#section-4.3-5" class="pilcrow">¶</a></p>
<p id="section-4.3-6">
   An example of the remarks data structure:<a href="#section-4.3-6" class="pilcrow">¶</a></p>
<div id="ure-8">
<figure id="figure-8">
          <div id="section-4.3-7.1">
<pre class="sourcecode lang-json">
"remarks" :
[
  {
    "description" :
    [
      "She sells sea shells down by the sea shore.",
      "Originally written by Terry Sullivan."
    ]
  }
]
</pre>
</div>
<figcaption><a href="#figure-8" class="selfRef">Figure 8</a></figcaption></figure>
</div>
<p id="section-4.3-8">
   Note that objects in the "remarks" array may also have a "links"
   array.<a href="#section-4.3-8" class="pilcrow">¶</a></p>
<p id="section-4.3-9">
   While the "title" and "description" fields are intended primarily for
   human consumption, the "type" string contains a well-known value to
   be registered with IANA (see <a href="#sect-10.2.1" class="xref">Section 10.2.1</a>) for programmatic use.<a href="#section-4.3-9" class="pilcrow">¶</a></p>
<p id="section-4.3-10">
   An example of the remarks data structure:<a href="#section-4.3-10" class="pilcrow">¶</a></p>
<div id="ure-9">
<figure id="figure-9">
          <div id="section-4.3-11.1">
<pre class="sourcecode lang-json">
"remarks" :
[
  {
    "type" : "object truncated due to authorization",
    "description" :
    [
      "Some registration data may not have been given.",
      "Use proper authorization credentials to see all of it."
    ]
  }
]
</pre>
</div>
<figcaption><a href="#figure-9" class="selfRef">Figure 9</a></figcaption></figure>
</div>
<p id="section-4.3-12">
   While the "remarks" array will appear in many object classes in a
   response, the "notices" array appears only in the topmost object of a
   response.<a href="#section-4.3-12" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-4.4">
<section id="section-4.4">
        <h3 id="name-language-identifier">
<a href="#section-4.4" class="section-number selfRef">4.4. </a><a href="#name-language-identifier" class="section-name selfRef">Language Identifier</a>
        </h3>
<p id="section-4.4-1">
   This data structure consists solely of a name/value pair, where the
   name is "lang" and the value is a string containing a language
   identifier as described in <span>[<a href="#RFC5646" class="xref">RFC5646</a>]</span>.<a href="#section-4.4-1" class="pilcrow">¶</a></p>
<div id="ure-10">
<figure id="figure-10">
          <div id="section-4.4-2.1">
<pre class="sourcecode lang-json">"lang" : "mn-Cyrl-MN"</pre>
</div>
<figcaption><a href="#figure-10" class="selfRef">Figure 10</a></figcaption></figure>
</div>
<p id="section-4.4-3">The "lang" attribute as defined in this section <span class="bcp14">MAY</span> appear anywhere
 in an object class or data structure, except for in jCard objects. vCard
 supports similar functionality by way of the LANGUAGE property parameter
 (see Section <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.1" class="relref">5.1</a> of RFC 6350 <span>[<a href="#RFC6350" class="xref">RFC6350</a>]</span>).<a href="#section-4.4-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-4.5">
<section id="section-4.5">
        <h3 id="name-events">
<a href="#section-4.5" class="section-number selfRef">4.5. </a><a href="#name-events" class="section-name selfRef">Events</a>
        </h3>
<p id="section-4.5-1">
   This data structure represents events that have occurred on an
   instance of an object class (see <a href="#sect-5" class="xref">Section 5</a> regarding object classes).<a href="#section-4.5-1" class="pilcrow">¶</a></p>
<p id="section-4.5-2">
   This is an example of an "events" array.<a href="#section-4.5-2" class="pilcrow">¶</a></p>
<div id="ure-11">
<figure id="figure-11">
          <div id="section-4.5-3.1">
<pre class="sourcecode lang-json">
"events" :
[
  {
    "eventAction" : "registration",
    "eventActor" : "SOMEID-LUNARNIC",
    "eventDate" : "1990-12-31T23:59:59Z"
  },
  {
    "eventAction" : "last changed",
    "eventActor" : "OTHERID-LUNARNIC",
    "eventDate" : "1991-12-31T23:59:59Z"
  }
]
</pre>
</div>
<figcaption><a href="#figure-11" class="selfRef">Figure 11</a></figcaption></figure>
</div>
<p id="section-4.5-4">
   The "events" array consists of objects, each with the following members:<a href="#section-4.5-4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.5-5.1">"eventAction" -- a <span class="bcp14">REQUIRED</span> string denoting the reason for the event<a href="#section-4.5-5.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.5-5.2">"eventActor" -- an <span class="bcp14">OPTIONAL</span> identifier denoting the actor
      responsible for the event<a href="#section-4.5-5.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.5-5.3">"eventDate" -- a <span class="bcp14">REQUIRED</span> string containing the time and date the event
      occurred<a href="#section-4.5-5.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.5-5.4">"links" -- <span class="bcp14">OPTIONAL</span>; see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-4.5-5.4" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-4.5-6">
   Events can be future dated.  One use case for future dating of events
   is to denote when an object expires from a registry.<a href="#section-4.5-6" class="pilcrow">¶</a></p>
<p id="section-4.5-7">
   The "links" array in this data structure is provided for references
   to the event actor.  In order to reference an RDAP entity, a "rel" of
   "related" and a "type" of "application/rdap+json" is used in the link
   reference.<a href="#section-4.5-7" class="pilcrow">¶</a></p>
<p id="section-4.5-8">
   See <a href="#sect-10.2.3" class="xref">Section 10.2.3</a> for a list of values for the "eventAction" string.
   See <a href="#sect-b" class="xref">Appendix B</a> regarding the various ways events can be modeled.<a href="#section-4.5-8" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-4.6">
<section id="section-4.6">
        <h3 id="name-status">
<a href="#section-4.6" class="section-number selfRef">4.6. </a><a href="#name-status" class="section-name selfRef">Status</a>
        </h3>
<p id="section-4.6-1">
   This data structure, named "status", is an array of strings
   indicating the state of a registered object (see <a href="#sect-10.2.2" class="xref">Section 10.2.2</a> for a
   list of values).<a href="#section-4.6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-4.7">
<section id="section-4.7">
        <h3 id="name-port-43-whois-server">
<a href="#section-4.7" class="section-number selfRef">4.7. </a><a href="#name-port-43-whois-server" class="section-name selfRef">Port 43 WHOIS Server</a>
        </h3>
<p id="section-4.7-1">
   This data structure, a member named "port43", is a simple character string
   containing the fully qualified host name or IP address of the WHOIS
   <span>[<a href="#RFC3912" class="xref">RFC3912</a>]</span> server where the containing object instance may be found.
   Note that this is not a URI, as there is no WHOIS URI scheme.<a href="#section-4.7-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-4.8">
<section id="section-4.8">
        <h3 id="name-public-ids">
<a href="#section-4.8" class="section-number selfRef">4.8. </a><a href="#name-public-ids" class="section-name selfRef">Public IDs</a>
        </h3>
<p id="section-4.8-1">
   This data structure maps a public identifier to an object class.  It
   is named "publicIds" and is an array of objects, with each object
   containing the following <span class="bcp14">REQUIRED</span> members:<a href="#section-4.8-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4.8-2.1">type -- a string denoting the type of public identifier<a href="#section-4.8-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-4.8-2.2">identifier -- a string denoting a public identifier of the type related to "type"<a href="#section-4.8-2.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-4.8-3">
   The following is an example of a publicIds structure.<a href="#section-4.8-3" class="pilcrow">¶</a></p>
<div id="ure-12">
<figure id="figure-12">
          <div id="section-4.8-4.1">
<pre class="sourcecode lang-json">
"publicIds":
[
  {
    "type":"IANA Registrar ID",
    "identifier":"1"
  }
]
</pre>
</div>
<figcaption><a href="#figure-12" class="selfRef">Figure 12</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-4.9">
<section id="section-4.9">
        <h3 id="name-object-class-name">
<a href="#section-4.9" class="section-number selfRef">4.9. </a><a href="#name-object-class-name" class="section-name selfRef">Object Class Name</a>
        </h3>
<p id="section-4.9-1">
   This data structure, a member named "objectClassName", gives the
   object class name of a particular object as a string.  This
   identifies the type of object being processed.  An objectClassName is
   <span class="bcp14">REQUIRED</span> in all RDAP response objects so that the type of the object
   can be interpreted.<a href="#section-4.9-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-4.10">
<section id="section-4.10">
        <h3 id="name-an-example">
<a href="#section-4.10" class="section-number selfRef">4.10. </a><a href="#name-an-example" class="section-name selfRef">An Example</a>
        </h3>
<p id="section-4.10-1">
   This is an example response with both rdapConformance and notices
   embedded:<a href="#section-4.10-1" class="pilcrow">¶</a></p>
<div id="ure-13">
<figure id="figure-13">
          <div id="section-4.10-2.1">
<pre class="sourcecode lang-json">
{
  "rdapConformance" :
  [
    "rdap_level_0"
  ],
  "notices" :
  [
    {
      "title" : "Content Removed",
      "description" :
      [
        "Without full authorization, content has been removed.",
        "Sorry, dude!"
      ],
      "links" :
      [
        {
          "value" : "https://example.net/ip/192.0.2.0/24",
          "rel" : "alternate",
          "type" : "text/html",
          "href" : "https://www.example.com/redaction_policy.html"
        }
      ]
    }
  ],
  "lang" : "en",
  "objectClassName" : "ip network",
  "startAddress" : "192.0.2.0",
  "endAddress" : "192.0.2.255",
  "handle" : "XXXX-RIR",
  "ipVersion" : "v4",
  "name": "NET-RTR-1",
  "parentHandle" : "YYYY-RIR",
  "remarks" :
  [

    {
      "description" :
      [
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-13" class="selfRef">Figure 13</a></figcaption></figure>
</div>
</section>
</div>
</section>
</div>
<div id="sect-5">
<section id="section-5">
      <h2 id="name-object-classes">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-object-classes" class="section-name selfRef">Object Classes</a>
      </h2>
<p id="section-5-1">
   Object classes represent structures appropriate for a response from
   the queries specified in <span>[<a href="#RFC9082" class="xref">RFC9082</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">
   Each object class contains a "links" array as specified in
   <a href="#sect-4.2" class="xref">Section 4.2</a>.  For every object class instance in a response, whether
   the object class instance is directly representing the response to a
   query or is embedded in other object class instances or is an item in
   a search result set, servers <span class="bcp14">SHOULD</span> provide a link representing a URI
   for that object class instance using the "self" relationship as
   described in the IANA registry specified by <span>[<a href="#RFC8288" class="xref">RFC8288</a>]</span>.  As explained
   in <a href="#sect-5.2" class="xref">Section 5.2</a>, this may be not always be possible for nameserver
   data.  Clients <span class="bcp14">MUST</span> be able to process object instances without a
   self link.  When present, clients can use the self link for caching
   data.  Servers <span class="bcp14">MAY</span> provide more than one self link for any given
   object instance.  Failure to provide any self link by a server may
   result in clients being unable to cache object class instances.<a href="#section-5-2" class="pilcrow">¶</a></p>
<p id="section-5-3">
   Clients using self links for caching <span class="bcp14">SHOULD NOT</span> cache any object
   class instances where the authority of the self link is different
   than the authority of the server returning the data.  Failing to do
   so might result in cache poisoning.<a href="#section-5-3" class="pilcrow">¶</a></p>
<p id="section-5-4">
   Self links <span class="bcp14">MUST</span> contain a "type" element containing the "application/rdap+json" media type when referencing RDAP object instances as
   defined by this document.<a href="#section-5-4" class="pilcrow">¶</a></p>
<p id="section-5-5">
   This is an example of the "links" array with a self link to an object
   class:<a href="#section-5-5" class="pilcrow">¶</a></p>
<div id="ure-14">
<figure id="figure-14">
        <div id="section-5-6.1">
<pre class="sourcecode lang-json">
    "links" :
    [
        {
          "value" : "https://example.com/ip/2001:db8::123",
          "rel" : "self",
          "href" : "https://example.com/ip/2001:db8::123",
          "type" : "application/rdap+json"
        }
    ]
</pre>
</div>
<figcaption><a href="#figure-14" class="selfRef">Figure 14</a></figcaption></figure>
</div>
<div id="sect-5.1">
<section id="section-5.1">
        <h3 id="name-the-entity-object-class">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-the-entity-object-class" class="section-name selfRef">The Entity Object Class</a>
        </h3>
<p id="section-5.1-1">
   The entity object class appears throughout this document and is an
   appropriate response for the /entity/XXXX query defined in
   "<a href="#RFC9082" class="xref">Registration Data Access Protocol (RDAP) Query Format</a>" <span>[<a href="#RFC9082" class="xref">RFC9082</a>]</span>.
   This object class represents the information of organizations,
   corporations, governments, non-profits, clubs, individual persons,
   and informal groups of people.  All of these representations are so
   similar that it is best to represent them in JSON <span>[<a href="#RFC8259" class="xref">RFC8259</a>]</span> with one
   construct, the entity object class, to aid in the reuse of code by
   implementers.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<p id="section-5.1-2">
   The entity object class uses jCard <span>[<a href="#RFC7095" class="xref">RFC7095</a>]</span> to represent contact
   information, such as postal addresses, email addresses, phone numbers
   and names of organizations and individuals.  Many of the types of
   information that can be represented with jCard have little or no use in RDAP,
   such as birthdays, anniversaries, and gender.<a href="#section-5.1-2" class="pilcrow">¶</a></p>
<p id="section-5.1-3">
   The entity object is served by both RIRs and DNRs.  The following is
   an example of an entity that might be served by an RIR.<a href="#section-5.1-3" class="pilcrow">¶</a></p>
<div id="ure-15">
<figure id="figure-15">
          <div id="section-5.1-4.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "entity",
  "handle":"XXXX",
  "vcardArray":[
    "vcard",
    [
      ["version", {}, "text", "4.0"],
      ["fn", {}, "text", "Joe User"],
      ["n", {}, "text",
        ["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
      ],
      ["kind", {}, "text", "individual"],
      ["lang", {
        "pref":"1"
      }, "language-tag", "fr"],
      ["lang", {
        "pref":"2"
      }, "language-tag", "en"],
      ["org", {
        "type":"work"
      }, "text", "Example"],
      ["title", {}, "text", "Research Scientist"],
      ["role", {}, "text", "Project Lead"],
      ["adr",
        { "type":"work" },
        "text",
        [
          "",
          "Suite 1234",
          "4321 Rue Somewhere",
          "Quebec",
          "QC",
          "G1V 2M2",
          "Canada"
        ]
      ],
      ["adr",
        {
          "type":"home",
          "label":"123 Maple Ave\nSuite 90001\nVancouver\nBC\n1239\n"
        },
        "text",
        [
          "", "", "", "", "", "", ""
        ]
      ],
      ["tel",
        {
          "type":["work", "voice"],
          "pref":"1"
        },
        "uri",
        "tel:+1-555-555-1234;ext=102"
      ],
      ["tel",
        { "type":["work", "cell", "voice", "video", "text"] },
        "uri",
        "tel:+1-555-555-4321"
      ],
      ["email",
        { "type":"work" },
        "text",
        "joe.user@example.com"
      ],
      ["geo", {
        "type":"work"
      }, "uri", "geo:46.772673,-71.282945"],
      ["key",
        { "type":"work" },
        "uri",
        "https://www.example.com/joe.user/joe.asc"
      ],
      ["tz", {},
        "utc-offset", "-05:00"],
      ["url", { "type":"home" },
        "uri", "https://example.org"]
    ]
  ],
  "roles":[ "registrar" ],
  "publicIds":[
    {
      "type":"IANA Registrar ID",
      "identifier":"1"
    }
  ],
  "remarks":[
    {
      "description":[
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ],
  "links":[
    {
      "value":"https://example.com/entity/XXXX",
      "rel":"self",
      "href":"https://example.com/entity/XXXX",
      "type" : "application/rdap+json"
    }
  ],
  "events":[
    {
      "eventAction":"registration",
      "eventDate":"1990-12-31T23:59:59Z"
    }
  ],
  "asEventActor":[

    {
      "eventAction":"last changed",
      "eventDate":"1991-12-31T23:59:59Z"
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-15" class="selfRef">Figure 15</a></figcaption></figure>
</div>
<p id="section-5.1-5">
   The entity object class can contain the following members:<a href="#section-5.1-5" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.1-6.1">objectClassName -- the string "entity"<a href="#section-5.1-6.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.2">handle -- a string representing a registry-unique identifier of
      the entity<a href="#section-5.1-6.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.3">vcardArray -- a jCard with the entity's contact information<a href="#section-5.1-6.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.4">roles -- an array of strings, each signifying the relationship an
      object would have with its closest containing object (see
      <a href="#sect-10.2.4" class="xref">Section 10.2.4</a> for a list of values)<a href="#section-5.1-6.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.5">publicIds -- see <a href="#sect-4.8" class="xref">Section 4.8</a><a href="#section-5.1-6.5" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.6">entities -- an array of entity objects as defined by this section<a href="#section-5.1-6.6" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.7">remarks -- see <a href="#sect-4.3" class="xref">Section 4.3</a><a href="#section-5.1-6.7" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.8">links -- see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-5.1-6.8" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.9">events -- see <a href="#sect-4.5" class="xref">Section 4.5</a><a href="#section-5.1-6.9" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.10">asEventActor -- this data structure takes the same form as the
      events data structure (see <a href="#sect-4.5" class="xref">Section 4.5</a>), but each object in the
      array <span class="bcp14">MUST NOT</span> have an "eventActor" member.  These objects denote
      that the entity is an event actor for the given events.  See
      <a href="#sect-b" class="xref">Appendix B</a> regarding the various ways events can be modeled.<a href="#section-5.1-6.10" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.11">status -- see <a href="#sect-4.6" class="xref">Section 4.6</a><a href="#section-5.1-6.11" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.12">port43 -- see <a href="#sect-4.7" class="xref">Section 4.7</a><a href="#section-5.1-6.12" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.13">networks -- an array of IP network objects as defined in
      <a href="#sect-5.4" class="xref">Section 5.4</a><a href="#section-5.1-6.13" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-6.14">autnums -- an array of autnum objects as defined in <a href="#sect-5.5" class="xref">Section 5.5</a><a href="#section-5.1-6.14" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-5.1-7">
   Entities may also have other entities embedded with them in an array.
   This can be used to model an organization with specific individuals
   fulfilling designated roles of responsibility.<a href="#section-5.1-7" class="pilcrow">¶</a></p>
<p id="section-5.1-8">
   The following is an elided example of an entity with embedded
   entities.<a href="#section-5.1-8" class="pilcrow">¶</a></p>
<div id="ure-16">
<figure id="figure-16">
          <div id="section-5.1-9.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "entity",
  "handle" : "ANENTITY",
  "roles" : [ "registrar" ],
  ...
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle": "ANEMBEDDEDENTITY",
      "roles" : [ "technical" ],
      ...
    },
    ...
  ],
  ...
}
</pre>
</div>
<figcaption><a href="#figure-16" class="selfRef">Figure 16</a></figcaption></figure>
</div>
<p id="section-5.1-10">
   The following is an example of an entity that might be served by a
   DNR.<a href="#section-5.1-10" class="pilcrow">¶</a></p>
<div id="ure-17">
<figure id="figure-17">
          <div id="section-5.1-11.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "entity",
  "handle":"XXXX",
  "vcardArray":[
    "vcard",
    [
      ["version", {}, "text", "4.0"],
      ["fn", {}, "text", "Joe User"],
      ["kind", {}, "text", "individual"],
      ["lang", {
        "pref":"1"
      }, "language-tag", "fr"],
      ["lang", {
        "pref":"2"
      }, "language-tag", "en"],
      ["org", {
        "type":"work"
      }, "text", "Example"],
      ["title", {}, "text", "Research Scientist"],
      ["role", {}, "text", "Project Lead"],
      ["adr",
        { "type":"work" },
        "text",
        [
          "",
          "Suite 1234",
          "4321 Rue Somewhere",
          "Quebec",
          "QC",
          "G1V 2M2",
          "Canada"
        ]
      ],
      ["tel",
        { "type":["work", "voice"], "pref":"1" },
        "uri", "tel:+1-555-555-1234;ext=102"
      ],
      ["email",
        { "type":"work" },
        "text", "joe.user@example.com"
      ]
    ]
  ],
  "status":[ "validated", "locked" ],
  "remarks":[
    {
      "description":[
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ],
  "links":[
    {
      "value":"https://example.com/entity/XXXX",
      "rel":"self",
      "href":"https://example.com/entity/XXXX",
      "type":"application/rdap+json"
    }
  ],
  "port43":"whois.example.net",
  "events":[
    {
      "eventAction":"registration",
      "eventDate":"1990-12-31T23:59:59Z"
    },
    {
      "eventAction":"last changed",
      "eventDate":"1991-12-31T23:59:59Z",
      "eventActor":"joe@example.com"
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-17" class="selfRef">Figure 17</a></figcaption></figure>
</div>
<p id="section-5.1-12">
   See <a href="#sect-a" class="xref">Appendix A</a> for use of the entity object class to model various
   types of entities found in both RIRs and DNRs.  See <a href="#sect-c" class="xref">Appendix C</a> 
   regarding structured vs.  unstructured postal addresses in entities.<a href="#section-5.1-12" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-5.2">
<section id="section-5.2">
        <h3 id="name-the-nameserver-object-class">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-the-nameserver-object-class" class="section-name selfRef">The Nameserver Object Class</a>
        </h3>
<p id="section-5.2-1">
   The nameserver object class represents information regarding DNS
   nameservers used in both forward and reverse DNS.  RIRs and some DNRs
   register or expose nameserver information as an attribute of a domain
   name, while other DNRs model nameservers as "first class objects".
   Please note that some of the examples in this section include lines
   that have been wrapped for reading clarity.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<p id="section-5.2-2">
   The nameserver object class accommodates both models and degrees of
   variation in between.<a href="#section-5.2-2" class="pilcrow">¶</a></p>
<p id="section-5.2-3">The following is an example of a nameserver object.<a href="#section-5.2-3" class="pilcrow">¶</a></p>
<div id="ure-18">
<figure id="figure-18">
          <div id="section-5.2-4.1">
<pre class="sourcecode lang-json">
  {
    "objectClassName" : "nameserver",
    "handle" : "XXXX",
    "ldhName" : "ns1.xn--fo-5ja.example",
    "unicodeName" : "ns.fóo.example",
    "status" : [ "active" ],
    "ipAddresses" :
    {
      "v4": [ "192.0.2.1", "192.0.2.2" ],
      "v6": [ "2001:db8::123" ]
    },
    "remarks" :
    [
      {
        "description" :
        [
          "She sells sea shells down by the sea shore.",
          "Originally written by Terry Sullivan."
        ]
      }
    ],
    "links" :
    [
      {
        "value" : "https://example.net/nameserver/
                   ns1.xn--fo-5ja.example",
        "rel" : "self",
        "href" : "https://example.net/nameserver/
                  ns1.xn--fo-5ja.example",
        "type" : "application/rdap+json"
      }
    ],
    "port43" : "whois.example.net",
    "events" :
    [
      {
        "eventAction" : "registration",
        "eventDate" : "1990-12-31T23:59:59Z"
      },
      {
        "eventAction" : "last changed",
        "eventDate" : "1991-12-31T23:59:59Z",
        "eventActor" : "joe@example.com"
      }
    ]
  }
</pre>
</div>
<figcaption><a href="#figure-18" class="selfRef">Figure 18</a></figcaption></figure>
</div>
<p id="section-5.2-5">
   <a href="#ure-18" class="xref">Figure 18</a> is an example of a nameserver object with all appropriate values given.
   Registries using a first-class nameserver data model would embed this
   in domain objects as well as allowing references to it with the
   "/nameserver" query type (all depending on the registry operators
   policy).  Other registries may pare back the information as needed.
   <a href="#ure-19" class="xref">Figure 19</a> is an example of a nameserver object as would be found in
   RIRs and some DNRs, while <a href="#ure-20" class="xref">Figure 20</a> is an example of a nameserver
   object as would be found in other DNRs.<a href="#section-5.2-5" class="pilcrow">¶</a></p>
<p id="section-5.2-6">The following is an example of the simplest nameserver object:<a href="#section-5.2-6" class="pilcrow">¶</a></p>
<div id="ure-19">
<figure id="figure-19">
          <div id="section-5.2-7.1">
<pre class="sourcecode lang-json">
  {
    "objectClassName" : "nameserver",
    "ldhName" : "ns1.example.com"
  }
</pre>
</div>
<figcaption><a href="#figure-19" class="selfRef">Figure 19</a></figcaption></figure>
</div>
<p id="section-5.2-8">
   The following is an example of a simple nameserver object that might
   be commonly used by DNRs:<a href="#section-5.2-8" class="pilcrow">¶</a></p>
<div id="ure-20">
<figure id="figure-20">
          <div id="section-5.2-9.1">
<pre class="sourcecode lang-json">
  {
    "objectClassName" : "nameserver",
    "ldhName" : "ns1.example.com",
    "ipAddresses" : { "v6" : [ "2001:db8::123", "2001:db8::124" ] }
  }
</pre>
</div>
<figcaption><a href="#figure-20" class="selfRef">Figure 20</a></figcaption></figure>
</div>
<p id="section-5.2-10">
   As nameservers can be modeled by some registries to be first-class
   objects, they may also have an array of entities (<a href="#sect-5.1" class="xref">Section 5.1</a>)
   embedded to signify parties responsible for the maintenance,
   registrations, etc., of the nameservers.<a href="#section-5.2-10" class="pilcrow">¶</a></p>
<p id="section-5.2-11">
   The following is an elided example of a nameserver with embedded
   entities.<a href="#section-5.2-11" class="pilcrow">¶</a></p>
<div id="ure-21">
<figure id="figure-21">
          <div id="section-5.2-12.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "nameserver",
  "handle" : "XXXX",
  "ldhName" : "ns.xn--fo-5ja.example",
  ...
  "entities" :
  [
    ...
  ],
  ...
}
</pre>
</div>
<figcaption><a href="#figure-21" class="selfRef">Figure 21</a></figcaption></figure>
</div>
<p id="section-5.2-13">
   The nameserver object class can contain the following members:<a href="#section-5.2-13" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.2-14.1">objectClassName -- the string "nameserver"<a href="#section-5.2-14.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.2">handle -- a string representing a registry-unique identifier of
      the nameserver<a href="#section-5.2-14.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.3">ldhName -- a string containing the LDH name of the nameserver (see
      <a href="#sect-3" class="xref">Section 3</a>)<a href="#section-5.2-14.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.4">unicodeName -- a string containing a DNS Unicode name of the
      nameserver (see <a href="#sect-3" class="xref">Section 3</a>)<a href="#section-5.2-14.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.5">
            <p id="section-5.2-14.5.1">ipAddresses -- an object containing the following members:<a href="#section-5.2-14.5.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.2-14.5.2.1">v6 -- an array of strings containing IPv6 addresses of the
         nameserver<a href="#section-5.2-14.5.2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.2-14.5.2.2">v4 -- an array of strings containing IPv4 addresses of the
         nameserver<a href="#section-5.2-14.5.2.2" class="pilcrow">¶</a>
</li>
            </ul>
</li>
          <li class="normal" id="section-5.2-14.6">entities -- an array of entity objects as defined by <a href="#sect-5.1" class="xref">Section 5.1</a><a href="#section-5.2-14.6" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.7">status -- see <a href="#sect-4.6" class="xref">Section 4.6</a><a href="#section-5.2-14.7" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.8">remarks -- see <a href="#sect-4.3" class="xref">Section 4.3</a><a href="#section-5.2-14.8" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.9">links -- see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-5.2-14.9" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.10">port43 -- see <a href="#sect-4.7" class="xref">Section 4.7</a><a href="#section-5.2-14.10" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.2-14.11">events -- see <a href="#sect-4.5" class="xref">Section 4.5</a><a href="#section-5.2-14.11" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
<div id="sect-5.3">
<section id="section-5.3">
        <h3 id="name-the-domain-object-class">
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-the-domain-object-class" class="section-name selfRef">The Domain Object Class</a>
        </h3>
<p id="section-5.3-1">
   The domain object class represents a DNS name and point of
   delegation.  For RIRs, these delegation points are in the reverse DNS
   tree, whereas for DNRs, these delegation points are in the forward
   DNS tree.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
<p id="section-5.3-2">
   In both cases, the high-level structure of the domain object class
   consists of information about the domain registration, nameserver
   information related to the domain name, and entities related to the
   domain name (e.g., registrant information, contacts, etc.).<a href="#section-5.3-2" class="pilcrow">¶</a></p>
<p id="section-5.3-3">
   The following is an elided example of the domain object showing the
   high-level structure:<a href="#section-5.3-3" class="pilcrow">¶</a></p>
<div id="ure-22">
<figure id="figure-22">
          <div id="section-5.3-4.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "domain",
  "handle" : "XXX",
  "ldhName" : "blah.example.com",
  ...
  "nameservers" :
  [
    ...
  ],
  ...
  "entities" :
  [
    ...
  ]
}
</pre>
</div>
<figcaption><a href="#figure-22" class="selfRef">Figure 22</a></figcaption></figure>
</div>
<p id="section-5.3-5">
   The domain object class can contain the following members:<a href="#section-5.3-5" class="pilcrow">¶</a></p>
<p id="section-5.3-6"></p>
<ul class="normal">
<li class="normal" id="section-5.3-7.1">objectClassName -- the string "domain"<a href="#section-5.3-7.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.2">handle -- a string representing a registry-unique identifier of
      the domain object instance<a href="#section-5.3-7.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.3">ldhName -- a string describing a domain name in LDH form as
      described in <a href="#sect-3" class="xref">Section 3</a><a href="#section-5.3-7.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.4">unicodeName -- a string containing a domain name with U-labels as
      described in <a href="#sect-3" class="xref">Section 3</a><a href="#section-5.3-7.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.5">
            <p id="section-5.3-7.5.1">variants -- an array of objects, each containing the following
      values:<a href="#section-5.3-7.5.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.3-7.5.2.1">relation -- an array of strings, with each string denoting the
         relationship between the variants and the containing domain
         object (see <a href="#sect-10.2.5" class="xref">Section 10.2.5</a> for a list of suggested variant
         relations).<a href="#section-5.3-7.5.2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.3-7.5.2.2">idnTable -- the character string literal that represents the Internationalized
 Domain Name (IDN) table that has been registered in the IANA Repository of IDN
 Practices <span>[<a href="#IANA_IDNTABLES" class="xref">IANA_IDNTABLES</a>]</span>.<a href="#section-5.3-7.5.2.2" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.3-7.5.2.3">variantNames -- an array of objects, with each object
         containing an "ldhName" member and a "unicodeName" member (see
         <a href="#sect-3" class="xref">Section 3</a>).<a href="#section-5.3-7.5.2.3" class="pilcrow">¶</a>
</li>
            </ul>
</li>
          <li class="normal" id="section-5.3-7.6">nameservers -- an array of nameserver objects as defined by
      <a href="#sect-5.2" class="xref">Section 5.2</a><a href="#section-5.3-7.6" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.7">
            <p id="section-5.3-7.7.1">secureDNS -- an object with the following members:<a href="#section-5.3-7.7.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.3-7.7.2.1">zoneSigned -- boolean true if the zone has been signed, false
         otherwise.<a href="#section-5.3-7.7.2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.3-7.7.2.2">delegationSigned -- boolean true if there are DS records in the
         parent, false otherwise.<a href="#section-5.3-7.7.2.2" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.3-7.7.2.3">maxSigLife -- an integer representing the signature lifetime in
         seconds to be used when creating the RRSIG DS record in the
         parent zone <span>[<a href="#RFC5910" class="xref">RFC5910</a>]</span>.<a href="#section-5.3-7.7.2.3" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.3-7.7.2.4">
                <p id="section-5.3-7.7.2.4.1">dsData -- an array of objects, each with the following members:<a href="#section-5.3-7.7.2.4.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.3-7.7.2.4.2.1">keyTag -- an integer as specified by the key tag field of a
            DNS DS record as specified by <span>[<a href="#RFC4034" class="xref">RFC4034</a>]</span> in presentation
            format<a href="#section-5.3-7.7.2.4.2.1" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.4.2.2">algorithm -- an integer as specified by the algorithm field
            of a DNS DS record as described by RFC 4034 in presentation
            format<a href="#section-5.3-7.7.2.4.2.2" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.4.2.3">digest -- a string as specified by the digest field of a DNS
            DS record as specified by RFC 4034 in presentation format<a href="#section-5.3-7.7.2.4.2.3" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.4.2.4">digestType -- an integer as specified by the digest type
            field of a DNS DS record as specified by RFC 4034 in
            presentation format<a href="#section-5.3-7.7.2.4.2.4" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.4.2.5">events -- see <a href="#sect-4.5" class="xref">Section 4.5</a><a href="#section-5.3-7.7.2.4.2.5" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.4.2.6">links -- see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-5.3-7.7.2.4.2.6" class="pilcrow">¶</a>
</li>
                </ul>
</li>
              <li class="normal" id="section-5.3-7.7.2.5">
                <p id="section-5.3-7.7.2.5.1">keyData -- an array of objects, each with the following
         members:<a href="#section-5.3-7.7.2.5.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.3-7.7.2.5.2.1">flags -- an integer representing the flags field value in
            the DNSKEY record <span>[<a href="#RFC4034" class="xref">RFC4034</a>]</span> in presentation format<a href="#section-5.3-7.7.2.5.2.1" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.5.2.2">protocol -- an integer representation of the protocol field
            value of the DNSKEY record <span>[<a href="#RFC4034" class="xref">RFC4034</a>]</span> in presentation format<a href="#section-5.3-7.7.2.5.2.2" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.5.2.3">publicKey -- a string representation of the public key in
            the DNSKEY record <span>[<a href="#RFC4034" class="xref">RFC4034</a>]</span> in presentation format<a href="#section-5.3-7.7.2.5.2.3" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.5.2.4">algorithm -- an integer as specified by the algorithm field
            of a DNSKEY record as specified by <span>[<a href="#RFC4034" class="xref">RFC4034</a>]</span> in presentation
            format<a href="#section-5.3-7.7.2.5.2.4" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.5.2.5">events -- see <a href="#sect-4.5" class="xref">Section 4.5</a><a href="#section-5.3-7.7.2.5.2.5" class="pilcrow">¶</a>
</li>
                  <li class="normal" id="section-5.3-7.7.2.5.2.6">
                    <p id="section-5.3-7.7.2.5.2.6.1">links -- see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-5.3-7.7.2.5.2.6.1" class="pilcrow">¶</a></p>
<p id="section-5.3-7.7.2.5.2.6.2">See <a href="#sect-d" class="xref">Appendix D</a> for background information on these objects.<a href="#section-5.3-7.7.2.5.2.6.2" class="pilcrow">¶</a></p>
</li>
                </ul>
</li>
            </ul>
</li>
          <li class="normal" id="section-5.3-7.8">entities -- an array of entity objects as defined by <a href="#sect-5.1" class="xref">Section 5.1</a><a href="#section-5.3-7.8" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.9">status -- see <a href="#sect-4.6" class="xref">Section 4.6</a><a href="#section-5.3-7.9" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.10">publicIds -- see <a href="#sect-4.8" class="xref">Section 4.8</a><a href="#section-5.3-7.10" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.11">remarks -- see <a href="#sect-4.3" class="xref">Section 4.3</a><a href="#section-5.3-7.11" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.12">links -- see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-5.3-7.12" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.13">port43 -- see <a href="#sect-4.7" class="xref">Section 4.7</a><a href="#section-5.3-7.13" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.14">events -- see <a href="#sect-4.5" class="xref">Section 4.5</a><a href="#section-5.3-7.14" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.3-7.15">network -- represents the IP network for which a reverse DNS
      domain is referenced; see <a href="#sect-5.4" class="xref">Section 5.4</a><a href="#section-5.3-7.15" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-5.3-8">
   The following is an example of a JSON domain object representing a
   reverse DNS delegation point that might be served by an RIR (note
   that the dsData digest value has been modified to fit on one line).<a href="#section-5.3-8" class="pilcrow">¶</a></p>
<div id="ure-23">
<figure id="figure-23">
          <div id="section-5.3-9.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "domain",
  "handle" : "XXXX",
  "ldhName" : "0.2.192.in-addr.arpa",
  "nameservers" :
  [
    {
      "objectClassName" : "nameserver",
      "ldhName" : "ns1.rir.example"
    },
    {
      "objectClassName" : "nameserver",
      "ldhName" : "ns2.rir.example"
    }
  ],
  "secureDNS":
  {
    "delegationSigned": true,
    "dsData":
    [
      {
        "keyTag": 25345,
        "algorithm": 8,
        "digestType": 2,
        "digest": "2788970E18EA14...C890C85B8205B94"
      }
    ]
  },
  "remarks" :
  [
    {
      "description" :
      [
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ],
  "links" :
  [
    {
      "value": "https://example.net/domain/0.2.192.in-addr.arpa",
      "rel" : "self",
      "href" : "https://example.net/domain/0.2.192.in-addr.arpa",
      "type" : "application/rdap+json"

    }
  ],
  "events" :
  [
    {
      "eventAction" : "registration",
      "eventDate" : "1990-12-31T23:59:59Z"
    },
    {
      "eventAction" : "last changed",
      "eventDate" : "1991-12-31T23:59:59Z",
      "eventActor" : "joe@example.com"
    }
  ],
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle" : "XXXX",
      "vcardArray":[
        "vcard",
        [
          ["version", {}, "text", "4.0"],
          ["fn", {}, "text", "Joe User"],
          ["kind", {}, "text", "individual"],
          ["lang", {
            "pref":"1"
          }, "language-tag", "fr"],
          ["lang", {
            "pref":"2"
          }, "language-tag", "en"],
          ["org", {
            "type":"work"
          }, "text", "Example"],
          ["title", {}, "text", "Research Scientist"],
          ["role", {}, "text", "Project Lead"],
          ["adr",
            { "type":"work" },
            "text",
            [
              "",
              "Suite 1234",
              "4321 Rue Somewhere",
              "Quebec",
              "QC",
              "G1V 2M2",
              "Canada"
            ]

          ],
          ["tel",
            { "type":["work", "voice"], "pref":"1" },
            "uri", "tel:+1-555-555-1234;ext=102"
          ],
          ["email",
            { "type":"work" },
            "text", "joe.user@example.com"
          ]
        ]
      ],
      "roles" : [ "registrant" ],
      "remarks" :
      [
        {
          "description" :
          [
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "links" :
      [
        {
          "value": "https://example.net/entity/XXXX",
          "rel" : "self",
          "href" : "https://example.net/entity/XXXX",
          "type" : "application/rdap+json"
        }
      ],
      "events" :
      [
        {
          "eventAction" : "registration",
          "eventDate" : "1990-12-31T23:59:59Z"
        },
        {
          "eventAction" : "last changed",
          "eventDate" : "1991-12-31T23:59:59Z",
          "eventActor" : "joe@example.com"
        }
      ]
    }
  ],
  "network" :
  {
    "objectClassName" : "ip network",
    "handle" : "XXXX-RIR",
    "startAddress" : "192.0.2.0",
    "endAddress" : "192.0.2.255",
    "ipVersion" : "v4",
    "name": "NET-RTR-1",
    "type" : "DIRECT ALLOCATION",
    "country" : "AU",
    "parentHandle" : "YYYY-RIR",
    "status" : [ "active" ]
  }
}
</pre>
</div>
<figcaption><a href="#figure-23" class="selfRef">Figure 23</a></figcaption></figure>
</div>
<p id="section-5.3-10">
   The following is an example of a JSON domain object representing a
   forward DNS delegation point that might be served by a DNR. Note that
   the secureDNS keyData publicKey value has been modified to fit on a
   single line.<a href="#section-5.3-10" class="pilcrow">¶</a></p>
<div id="ure-24">
<figure id="figure-24">
          <div id="section-5.3-11.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "domain",
  "handle" : "XXXX",
  "ldhName" : "xn--fo-5ja.example",
  "unicodeName" : "fóo.example",
  "variants" :
  [
    {
      "relation" : [ "registered", "conjoined" ],
      "variantNames" :
      [
        {
          "ldhName" : "xn--fo-cka.example",
          "unicodeName" : "fõo.example"
        },
        {
          "ldhName" : "xn--fo-fka.example",
          "unicodeName" : "föo.example"
        }
      ]
    },
    {
      "relation" : [ "unregistered", "registration restricted" ],
      "idnTable": ".EXAMPLE Swedish",
      "variantNames" :
      [
        {
          "ldhName": "xn--fo-8ja.example",
          "unicodeName" : "fôo.example"
        }
      ]

    }
  ],
  "status" : [ "locked", "transfer prohibited" ],
  "publicIds":[
    {
      "type":"ENS_Auth ID",
      "identifier":"1234567890"
    }
  ],
  "nameservers" :
  [
    {
      "objectClassName" : "nameserver",
      "handle" : "XXXX",
      "ldhName" : "ns1.example.com",
      "status" : [ "active" ],
      "ipAddresses" :
      {
        "v6": [ "2001:db8::123", "2001:db8::124" ],
        "v4": [ "192.0.2.1", "192.0.2.2" ]
      },
      "remarks" :
      [
        {
          "description" :
          [
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "links" :
      [
        {
          "value" : "https://example.net/nameserver/ns1.example.com",
          "rel" : "self",
          "href" : "https://example.net/nameserver/ns1.example.com",
          "type" : "application/rdap+json"
        }
      ],
      "events" :
      [
        {
          "eventAction" : "registration",
          "eventDate" : "1990-12-31T23:59:59Z"
        },
        {
          "eventAction" : "last changed",
          "eventDate" : "1991-12-31T23:59:59Z"
        }
      ]
    },
    {
      "objectClassName" : "nameserver",
      "handle" : "XXXX",
      "ldhName" : "ns2.example.com",
      "status" : [ "active" ],
      "ipAddresses" :
      {
        "v6" : [ "2001:db8::125", "2001:db8::126" ],
        "v4" : [ "192.0.2.3", "192.0.2.4" ]
      },
      "remarks" :
      [
        {
          "description" :
          [
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "links" :
      [
        {
          "value" : "https://example.net/nameserver/ns2.example.com",
          "rel" : "self",
          "href" : "https://example.net/nameserver/ns2.example.com",
          "type" : "application/rdap+json"
        }
      ],
      "events" :
      [
        {
          "eventAction" : "registration",
          "eventDate" : "1990-12-31T23:59:59Z"
        },
        {
          "eventAction" : "last changed",
          "eventDate" : "1991-12-31T23:59:59Z"
        }
      ]
    }
  ],
  "secureDNS":
  {

     "zoneSigned": true,
     "delegationSigned": true,
     "maxSigLife": 604800,
     "keyData":
     [
       {
         "flags": 257,
         "protocol": 3,
         "algorithm": 8,
         "publicKey": "AwEAAa6eDzronzjEDbT...Jg1M5N rBSPkuXpdFE=",
         "events":
         [
           {
             "eventAction": "last changed",
             "eventDate": "2012-07-23T05:15:47Z"
           }
         ]
       }
     ]
  },
  "remarks" :
  [
    {
      "description" :
      [
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ],
  "links" :
  [
    {
      "value": "https://example.net/domain/xn--fo-5ja.example",
      "rel" : "self",
      "href" : "https://example.net/domain/xn--fo-5ja.example",
      "type" : "application/rdap+json"
    }
  ],
  "port43" : "whois.example.net",
  "events" :
  [
    {
      "eventAction" : "registration",
      "eventDate" : "1990-12-31T23:59:59Z"
    },
    {
      "eventAction" : "last changed",
      "eventDate" : "1991-12-31T23:59:59Z",
      "eventActor" : "joe@example.com"
    },
    {
      "eventAction" : "transfer",
      "eventDate" : "1991-12-31T23:59:59Z",
      "eventActor" : "joe@example.com"
    },
    {
      "eventAction" : "expiration",
      "eventDate" : "2016-12-31T23:59:59Z",
      "eventActor" : "joe@example.com"
    }
  ],
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle" : "XXXX",
      "vcardArray":[
        "vcard",
        [
          ["version", {}, "text", "4.0"],
          ["fn", {}, "text", "Joe User"],
          ["kind", {}, "text", "individual"],
          ["lang", {
            "pref":"1"
          }, "language-tag", "fr"],
          ["lang", {
            "pref":"2"
          }, "language-tag", "en"],
          ["org", {
            "type":"work"
          }, "text", "Example"],
          ["title", {}, "text", "Research Scientist"],
          ["role", {}, "text", "Project Lead"],
          ["adr",
            { "type":"work" },
            "text",
            [
              "",
              "Suite 1234",
              "4321 Rue Somewhere",
              "Quebec",
              "QC",
              "G1V 2M2",
              "Canada"
            ]

          ],
          ["tel",
            { "type":["work", "voice"], "pref":"1" },
            "uri", "tel:+1-555-555-1234;ext=102"
          ],
          ["email",
            { "type":"work" },
            "text", "joe.user@example.com"
          ]
        ]
      ],
      "status" : [ "validated", "locked" ],
      "roles" : [ "registrant" ],
      "remarks" :
      [
        {
          "description" :
          [
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "links" :
      [
        {
          "value" : "https://example.net/entity/XXXX",
          "rel" : "self",
          "href" : "https://example.net/entity/XXXX",
          "type" : "application/rdap+json"
        }
      ],
      "events" :
      [
        {
          "eventAction" : "registration",
          "eventDate" : "1990-12-31T23:59:59Z"
        },
        {
          "eventAction" : "last changed",
          "eventDate" : "1991-12-31T23:59:59Z"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-24" class="selfRef">Figure 24</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-5.4">
<section id="section-5.4">
        <h3 id="name-the-ip-network-object-class">
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-the-ip-network-object-class" class="section-name selfRef">The IP Network Object Class</a>
        </h3>
<p id="section-5.4-1">
   The IP network object class models IP network registrations found in
   RIRs and is the expected response for the "/ip" query as defined by
   <span>[<a href="#RFC9082" class="xref">RFC9082</a>]</span>.  There is no equivalent object class for DNRs.  The high-
   level structure of the IP network object class consists of
   information about the network registration and entities related to
   the IP network (e.g., registrant information, contacts, etc.).<a href="#section-5.4-1" class="pilcrow">¶</a></p>
<p id="section-5.4-2">
   The following is an elided example of the IP network object type
   showing the high-level structure:<a href="#section-5.4-2" class="pilcrow">¶</a></p>
<div id="ure-25">
<figure id="figure-25">
          <div id="section-5.4-3.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "ip network",
  "handle" : "XXX",
  ...
  "entities" :
  [
    ...
  ]
}
</pre>
</div>
<figcaption><a href="#figure-25" class="selfRef">Figure 25</a></figcaption></figure>
</div>
<p id="section-5.4-4">
   The following is an example of the JSON object for the network
   registration information.<a href="#section-5.4-4" class="pilcrow">¶</a></p>
<div id="ure-26">
<figure id="figure-26">
          <div id="section-5.4-5.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "ip network",
  "handle" : "XXXX-RIR",
  "startAddress" : "2001:db8::",
  "endAddress" : "2001:db8:0:ffff:ffff:ffff:ffff:ffff",
  "ipVersion" : "v6",
  "name": "NET-RTR-1",
  "type" : "DIRECT ALLOCATION",
  "country" : "AU",
  "parentHandle" : "YYYY-RIR",
  "status" : [ "active" ],
  "remarks" :
  [
    {
      "description" :
      [
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ],
  "links" :
  [
    {
      "value" : "https://example.net/ip/2001:db8::/48",
      "rel" : "self",
      "href" : "https://example.net/ip/2001:db8::/48",
      "type" : "application/rdap+json"
    },
    {
      "value" : "https://example.net/ip/2001:db8::/48",
      "rel" : "up",
      "href" : "https://example.net/ip/2001:db8::/32",
      "type" : "application/rdap+json"
    }
  ],
  "events" :
  [
    {
      "eventAction" : "registration",
      "eventDate" : "1990-12-31T23:59:59Z"
    },
    {
      "eventAction" : "last changed",
      "eventDate" : "1991-12-31T23:59:59Z"
    }
  ],
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle" : "XXXX",
      "vcardArray":[
        "vcard",
        [
          ["version", {}, "text", "4.0"],
          ["fn", {}, "text", "Joe User"],
          ["kind", {}, "text", "individual"],
          ["lang", {
            "pref":"1"
          }, "language-tag", "fr"],
          ["lang", {
            "pref":"2"
          }, "language-tag", "en"],
          ["org", {
            "type":"work"
          }, "text", "Example"],
          ["title", {}, "text", "Research Scientist"],
          ["role", {}, "text", "Project Lead"],
          ["adr",
            { "type":"work" },
            "text",
            [
              "",
              "Suite 1234",
              "4321 Rue Somewhere",
              "Quebec",
              "QC",
              "G1V 2M2",
              "Canada"
            ]
          ],
          ["tel",
            { "type":["work", "voice"], "pref":"1" },
            "uri", "tel:+1-555-555-1234;ext=102"
          ],
          ["email",
            { "type":"work" },
            "text", "joe.user@example.com"
          ]
        ]
      ],
      "roles" : [ "registrant" ],
      "remarks" :
      [
        {
          "description" :
          [
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "links" :
      [
        {
          "value" : "https://example.net/entity/xxxx",
          "rel" : "self",
          "href" : "https://example.net/entity/xxxx",
          "type" : "application/rdap+json"
        }
      ],
      "events" :
      [
        {
          "eventAction" : "registration",
          "eventDate" : "1990-12-31T23:59:59Z"

        },
        {
          "eventAction" : "last changed",
          "eventDate" : "1991-12-31T23:59:59Z"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-26" class="selfRef">Figure 26</a></figcaption></figure>
</div>
<p id="section-5.4-6">
   The IP network object class can contain the following members:<a href="#section-5.4-6" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.4-7.1">objectClassName -- the string "ip network"<a href="#section-5.4-7.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.2">handle -- a string representing the RIR-unique identifier of the
      network registration<a href="#section-5.4-7.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.3">startAddress -- a string representing the starting IP address of the network, either
      IPv4 or IPv6<a href="#section-5.4-7.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.4">endAddress -- a string representing the ending IP address of the network, either IPv4 or
      IPv6<a href="#section-5.4-7.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.5">ipVersion -- a string signifying the IP protocol version of the
      network: "v4" signifies an IPv4 network, and "v6" signifies an
      IPv6 network<a href="#section-5.4-7.5" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.6">name -- a string representing an identifier assigned to the network registration by the
      registration holder<a href="#section-5.4-7.6" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.7">type -- a string containing an RIR-specific classification of the
      network per that RIR's registration model<a href="#section-5.4-7.7" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.8">country -- a string containing the two-character country code of
      the network<a href="#section-5.4-7.8" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.9">parentHandle -- a string containing an RIR-unique identifier of
      the parent network of this network registration<a href="#section-5.4-7.9" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.10">status -- an array of strings indicating the state of the IP
      network as defined by <a href="#sect-4.6" class="xref">Section 4.6</a><a href="#section-5.4-7.10" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.11">entities -- an array of entity objects as defined by <a href="#sect-5.1" class="xref">Section 5.1</a><a href="#section-5.4-7.11" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.12">remarks -- see <a href="#sect-4.3" class="xref">Section 4.3</a><a href="#section-5.4-7.12" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.13">links -- see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-5.4-7.13" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.14">port43 -- see <a href="#sect-4.7" class="xref">Section 4.7</a><a href="#section-5.4-7.14" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.4-7.15">events -- see <a href="#sect-4.5" class="xref">Section 4.5</a><a href="#section-5.4-7.15" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
<div id="sect-5.5">
<section id="section-5.5">
        <h3 id="name-the-autonomous-system-numbe">
<a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-the-autonomous-system-numbe" class="section-name selfRef">The Autonomous System Number Object Class</a>
        </h3>
<p id="section-5.5-1">
   The Autonomous System number (autnum) object class models Autonomous
   System number registrations found in RIRs and represents the expected
   response to an "/autnum" query as defined by <span>[<a href="#RFC9082" class="xref">RFC9082</a>]</span>.  There is no
   equivalent object class for DNRs.  The high-level structure of the
   autnum object class consists of information about the Autonomous System number
   registration and entities related to the autnum registration (e.g.,
   registrant information, contacts, etc.) and is similar to the IP
   network object class.<a href="#section-5.5-1" class="pilcrow">¶</a></p>
<p id="section-5.5-2">
   The following is an example of a JSON object representing an autnum.<a href="#section-5.5-2" class="pilcrow">¶</a></p>
<div id="ure-27">
<figure id="figure-27">
          <div id="section-5.5-3.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "autnum",
  "handle" : "XXXX-RIR",
  "startAutnum" : 65536,
  "endAutnum" : 65541,
  "name": "AS-RTR-1",
  "type" : "DIRECT ALLOCATION",
  "status" : [ "active" ],
  "country": "AU",
  "remarks" :
  [
    {
      "description" :
      [
        "She sells sea shells down by the sea shore.",
        "Originally written by Terry Sullivan."
      ]
    }
  ],
  "links" :
  [
    {
      "value" : "https://example.net/autnum/65537",
      "rel" : "self",
      "href" : "https://example.net/autnum/65537",
      "type" : "application/rdap+json"
    }
  ],
  "events" :

  [
    {
      "eventAction" : "registration",
      "eventDate" : "1990-12-31T23:59:59Z"
    },
    {
      "eventAction" : "last changed",
      "eventDate" : "1991-12-31T23:59:59Z"
    }
  ],
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle" : "XXXX",
      "vcardArray":[
        "vcard",
        [
          ["version", {}, "text", "4.0"],
          ["fn", {}, "text", "Joe User"],
          ["kind", {}, "text", "individual"],
          ["lang", {
            "pref":"1"
          }, "language-tag", "fr"],
          ["lang", {
            "pref":"2"
          }, "language-tag", "en"],
          ["org", {
            "type":"work"
          }, "text", "Example"],
          ["title", {}, "text", "Research Scientist"],
          ["role", {}, "text", "Project Lead"],
          ["adr",
            { "type":"work" },
            "text",
            [
              "",
              "Suite 1234",
              "4321 Rue Somewhere",
              "Quebec",
              "QC",
              "G1V 2M2",
              "Canada"
            ]
          ],
          ["tel",
            { "type":["work", "voice"], "pref":"1" },
            "uri", "tel:+1-555-555-1234;ext=102"
          ],
          ["email",
            { "type":"work" },
            "text", "joe.user@example.com"
          ]
        ]
      ],
      "roles" : [ "registrant" ],
      "remarks" :
      [
        {
          "description" :
          [
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "links" :
      [
        {
          "value" : "https://example.net/entity/XXXX",
          "rel" : "self",
          "href" : "https://example.net/entity/XXXX",
          "type" : "application/rdap+json"
        }
      ],
      "events" :
      [
        {
          "eventAction" : "registration",
          "eventDate" : "1990-12-31T23:59:59Z"
        },
        {
          "eventAction" : "last changed",
          "eventDate" : "1991-12-31T23:59:59Z"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-27" class="selfRef">Figure 27</a></figcaption></figure>
</div>
<p id="section-5.5-4">
   The Autonomous System number object class can contain the following
   members:<a href="#section-5.5-4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.5-5.1">objectClassName -- the string "autnum"<a href="#section-5.5-5.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.2">handle -- a string representing the RIR-unique identifier of the
      autnum registration<a href="#section-5.5-5.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.3">startAutnum -- an unsigned 32-bit integer representing the starting number <span>[<a href="#RFC5396" class="xref">RFC5396</a>]</span>
      in the block of Autonomous System numbers<a href="#section-5.5-5.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.4">endAutnum -- an unsigned 32-bit integer representing the ending number <span>[<a href="#RFC5396" class="xref">RFC5396</a>]</span> in
      the block of Autonomous System numbers<a href="#section-5.5-5.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.5">name -- a string representing an identifier assigned to the autnum registration by the
      registration holder<a href="#section-5.5-5.5" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.6">type -- a string containing an RIR-specific classification of the
      autnum per that RIR's registration model<a href="#section-5.5-5.6" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.7">status -- an array of strings indicating the state of the autnum as defined by <a href="#sect-4.6" class="xref">Section 4.6</a><a href="#section-5.5-5.7" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.8">country -- a string containing the two-character country
      code of the autnum<a href="#section-5.5-5.8" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.9">entities -- an array of entity objects as defined by <a href="#sect-5.1" class="xref">Section 5.1</a><a href="#section-5.5-5.9" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.10">remarks -- see <a href="#sect-4.3" class="xref">Section 4.3</a><a href="#section-5.5-5.10" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.11">links -- see <a href="#sect-4.2" class="xref">Section 4.2</a><a href="#section-5.5-5.11" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.12">port43 -- see <a href="#sect-4.7" class="xref">Section 4.7</a><a href="#section-5.5-5.12" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.5-5.13">events -- see <a href="#sect-4.5" class="xref">Section 4.5</a><a href="#section-5.5-5.13" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
</section>
</div>
<div id="sect-6">
<section id="section-6">
      <h2 id="name-error-response-body">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-error-response-body" class="section-name selfRef">Error Response Body</a>
      </h2>
<p id="section-6-1">
   Some non-answer responses <span class="bcp14">MAY</span> return entity bodies with information
   that could be more descriptive.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">
   The basic structure of that response is an object class containing a
   <span class="bcp14">REQUIRED</span> error code number (corresponding to the HTTP response code) followed
   by an <span class="bcp14">OPTIONAL</span> string named "title" and an <span class="bcp14">OPTIONAL</span> array of strings named
   "description".<a href="#section-6-2" class="pilcrow">¶</a></p>
<p id="section-6-3">
   This is an example of the common response body.<a href="#section-6-3" class="pilcrow">¶</a></p>
<div id="ure-28">
<figure id="figure-28">
        <div id="section-6-4.1">
<pre class="sourcecode lang-json">
{
  "errorCode": 418,
  "title": "Your Beverage Choice is Not Available",
  "description":
  [
    "I know coffee has more ummppphhh.",
    "Sorry, dude!"
  ]
}
</pre>
</div>
<figcaption><a href="#figure-28" class="selfRef">Figure 28</a></figcaption></figure>
</div>
<p id="section-6-5">
   This is an example of the common response body with an
   rdapConformance and notices data structures:<a href="#section-6-5" class="pilcrow">¶</a></p>
<div id="ure-29">
<figure id="figure-29">
        <div id="section-6-6.1">
<pre class="sourcecode lang-json">
{
  "rdapConformance" :
  [
    "rdap_level_0"
  ],
  "notices" :
  [
    {
      "title" : "Beverage Policy",
      "description" :
      [
        "Beverages with caffeine for keeping horses awake."
      ],
      "links" :
      [
        {
          "value" : "https://example.net/ip/192.0.2.0/24",
          "rel" : "alternate",
          "type" : "text/html",
          "href" : "https://www.example.com/redaction_policy.html"
        }
      ]
    }
  ],
  "lang" : "en",
  "errorCode": 418,
  "title": "Your beverage choice is not available",
  "description":
  [
    "I know coffee has more ummppphhh.",
    "Sorry, dude!"
  ]
}
</pre>
</div>
<figcaption><a href="#figure-29" class="selfRef">Figure 29</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-7">
<section id="section-7">
      <h2 id="name-responding-to-help-queries">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-responding-to-help-queries" class="section-name selfRef">Responding to Help Queries</a>
      </h2>
<p id="section-7-1">
   The appropriate response to /help queries as defined by <span>[<a href="#RFC9082" class="xref">RFC9082</a>]</span> is
   to use the notices structure as defined in <a href="#sect-4.3" class="xref">Section 4.3</a>.<a href="#section-7-1" class="pilcrow">¶</a></p>
<p id="section-7-2">
   This is an example of a response to a /help query including the
   rdapConformance data structure.<a href="#section-7-2" class="pilcrow">¶</a></p>
<div id="ure-30">
<figure id="figure-30">
        <div id="section-7-3.1">
<pre class="sourcecode lang-json">
{
  "rdapConformance" :
  [
    "rdap_level_0"
  ],
  "notices" :
  [
    {
      "title" : "Authentication Policy",
      "description" :
      [
        "Access to sensitive data for users with proper credentials."
      ],
      "links" :
      [
        {
          "value" : "https://example.net/help",
          "rel" : "alternate",
          "type" : "text/html",
          "href" : "https://www.example.com/auth_policy.html"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-30" class="selfRef">Figure 30</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-8">
<section id="section-8">
      <h2 id="name-responding-to-searches">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-responding-to-searches" class="section-name selfRef">Responding To Searches</a>
      </h2>
<p id="section-8-1">
   <span>[<a href="#RFC9082" class="xref">RFC9082</a>]</span> specifies three types of searches: domains, nameservers,
   and entities.  Responses to these searches take the form of an array
   of object instances where each instance is an appropriate object
   class for the search (i.e., a search for /domains yields an array of
   domain object instances).  These arrays are contained within the
   response object.<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">
   The names of the arrays are as follows:<a href="#section-8-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-8-3.1">for /domains searches, the array is "domainSearchResults"<a href="#section-8-3.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-8-3.2">for /nameservers searches, the array is "nameserverSearchResults"<a href="#section-8-3.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-8-3.3">for /entities searches, the array is "entitySearchResults"<a href="#section-8-3.3" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-8-4">
   The following is an elided example of a response to a /domains
   search.<a href="#section-8-4" class="pilcrow">¶</a></p>
<div id="ure-31">
<figure id="figure-31">
        <div id="section-8-5.1">
<pre class="sourcecode lang-json">
{
  "rdapConformance" :
  [
    "rdap_level_0"
  ],
  ...
  "domainSearchResults" :
  [
    {
      "objectClassName" : "domain",
      "handle" : "1-XXXX",
      "ldhName" : "1.example.com",
      ...
    },
    {
      "objectClassName" : "domain",
      "handle" : "2-XXXX",
      "ldhName" : "2.example.com",
      ...
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-31" class="selfRef">Figure 31</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-9">
<section id="section-9">
      <h2 id="name-indicating-truncated-respon">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-indicating-truncated-respon" class="section-name selfRef">Indicating Truncated Responses</a>
      </h2>
<p id="section-9-1">
   In cases where the data of a response needs to be limited or parts of
   the data need to be omitted, the response is considered "truncated".
   A truncated response is still valid JSON, but some of the results in
   a search set or some of the data in an object are not provided by the
   server.  A server may indicate this by including a typed notice in
   the response object.<a href="#section-9-1" class="pilcrow">¶</a></p>
<p id="section-9-2">
   The following is an elided example of a search response that has been
   truncated.<a href="#section-9-2" class="pilcrow">¶</a></p>
<div id="ure-32">
<figure id="figure-32">
        <div id="section-9-3.1">
<pre class="sourcecode lang-json">
{
  "rdapConformance" :
  [
    "rdap_level_0"
  ],
  "notices" :
  [
    {
      "title" : "Search Policy",
      "type" : "result set truncated due to authorization",
      "description" :
      [
        "Search results are limited to 25 per day per querying IP."
      ],
      "links" :
      [
        {
          "value" : "https://example.net/help",
          "rel" : "alternate",
          "type" : "text/html",
          "href" : "https://www.example.com/search_policy.html"
        }
      ]
    }
  ],
  "domainSearchResults" :
  [
    ...
  ]
}
</pre>
</div>
<figcaption><a href="#figure-32" class="selfRef">Figure 32</a></figcaption></figure>
</div>
<p id="section-9-4">
   A similar technique can be used with a typed remark where a single
   object has been returned and data in that object has been truncated.
   Such an example might be an entity object with only a partial set of
   the IP networks associated with it.<a href="#section-9-4" class="pilcrow">¶</a></p>
<p id="section-9-5">
   The following is an elided example of an entity truncated data.<a href="#section-9-5" class="pilcrow">¶</a></p>
<div id="ure-33">
<figure id="figure-33">
        <div id="section-9-6.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "entity",
  "handle" : "ANENTITY",
  "roles" : [ "registrant" ],
  ...
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle": "ANEMBEDDEDENTITY",
      "roles" : [ "technical" ],
      ...
    },
    ...
  ],
  "networks" :
  [
    ...
  ],
  ...
  "remarks" :
  [
    {
      "title" : "Data Policy",
      "type" : "object truncated due to unexplainable reason",
      "description" :
      [
        "Some of the data in this object has been removed."
      ],
      "links" :
      [
        {
          "value" : "https://example.net/help",
          "rel" : "alternate",
          "type" : "text/html",
          "href" : "https://www.example.com/data_policy.html"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-33" class="selfRef">Figure 33</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-10">
<section id="section-10">
      <h2 id="name-iana-considerations">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-10-1">IANA has updated the description of the "transfer" event action as described in <a href="#sect-10.2.3" class="xref">Section 10.2.3</a>.<a href="#section-10-1" class="pilcrow">¶</a></p>
<div id="sect-10.1">
<section id="section-10.1">
        <h3 id="name-rdap-json-media-type-regist">
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-rdap-json-media-type-regist" class="section-name selfRef">RDAP JSON Media Type Registration</a>
        </h3>
<p id="section-10.1-1">IANA has updated the media type registration as described below.<a href="#section-10.1-1" class="pilcrow">¶</a></p>
<p id="section-10.1-2">This specification registers the "application/rdap+json" media type.<a href="#section-10.1-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-10.1-3">
          <dt id="section-10.1-3.1">
 Type name:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.2"> application<a href="#section-10.1-3.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.3">
 Subtype name:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.4"> rdap+json<a href="#section-10.1-3.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.5">
 Required parameters:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.6"> n/a<a href="#section-10.1-3.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.7">
 Encoding considerations:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.8"> See <span><a href="https://www.rfc-editor.org/rfc/rfc6839#section-3.1" class="relref">Section 3.1</a> of [<a href="#RFC6839" class="xref">RFC6839</a>]</span>.<a href="#section-10.1-3.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.9">
 Security considerations:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.10">The media represented by this identifier
      does not have security considerations beyond that found in
      <span><a href="https://www.rfc-editor.org/rfc/rfc8259#section-12" class="relref">Section 12</a> of [<a href="#RFC8259" class="xref">RFC8259</a>]</span>.<a href="#section-10.1-3.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.11">
 Interoperability considerations:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.12"> There are no known
      interoperability problems regarding this media format.<a href="#section-10.1-3.12" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.13">
 Published specification:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.14"> RFC 9083<a href="#section-10.1-3.14" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.15">
 Applications that use this media type:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.16"> Implementations of the
      Registration Data Access Protocol (RDAP).<a href="#section-10.1-3.16" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.17">
 Additional information:</dt>
          <dd style="margin-left: 1.5em" id="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
      Working Group can be found at
      <span><a href="https://datatracker.ietf.org/wg/regext/">https://datatracker.ietf.org/wg/regext/</a></span>.<a href="#section-10.1-3.18" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.19">
 Person &amp; email address to contact for further information:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.20">
            <br>IESG
      &lt;iesg@ietf.org&gt;<a href="#section-10.1-3.20" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.21">
 Intended usage:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.22"> COMMON<a href="#section-10.1-3.22" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.23">
 Restrictions on usage:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.24"> none<a href="#section-10.1-3.24" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.25">
 Author:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.26"> Andy Newton<a href="#section-10.1-3.26" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.27">
 Change controller:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.28"> IETF<a href="#section-10.1-3.28" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-10.1-3.29">
 Provisional Registration:</dt>
          <dd style="margin-left: 1.5em" id="section-10.1-3.30"> No<a href="#section-10.1-3.30" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="sect-10.2">
<section id="section-10.2">
        <h3 id="name-json-values-registry">
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-json-values-registry" class="section-name selfRef">JSON Values Registry</a>
        </h3>
<p id="section-10.2-1">
   IANA has created a category in the protocol registries labeled
   "Registration Data Access Protocol (RDAP)", and within that category,
   IANA has established a URL-referenceable, stand-alone registry
   labeled "RDAP JSON Values".  This new registry is for use in the
   notices and remarks (<a href="#sect-4.3" class="xref">Section 4.3</a>), status (<a href="#sect-4.6" class="xref">Section 4.6</a>), role
   (<a href="#sect-5.1" class="xref">Section 5.1</a>), event action (<a href="#sect-4.5" class="xref">Section 4.5</a>), and domain variant
   relation (<a href="#sect-5.3" class="xref">Section 5.3</a>) fields specified in RDAP.<a href="#section-10.2-1" class="pilcrow">¶</a></p>
<p id="section-10.2-2">
   Each entry in the registry contains the following fields:<a href="#section-10.2-2" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-10.2-3">
<li id="section-10.2-3.1">Value -- the string value being registered.<a href="#section-10.2-3.1" class="pilcrow">¶</a>
</li>
          <li id="section-10.2-3.2">
            <p id="section-10.2-3.2.1">Type -- the type of value being registered.  It should be one of
       the following:<a href="#section-10.2-3.2.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-10.2-3.2.2.1">"notice or remark type" -- denotes a type of notice or remark.<a href="#section-10.2-3.2.2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-10.2-3.2.2.2">"status" -- denotes a value for the "status" object member as
          defined by <a href="#sect-4.6" class="xref">Section 4.6</a>.<a href="#section-10.2-3.2.2.2" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-10.2-3.2.2.3">"role" -- denotes a value for the "role" array as defined in
          <a href="#sect-5.1" class="xref">Section 5.1</a>.<a href="#section-10.2-3.2.2.3" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-10.2-3.2.2.4">"event action" -- denotes a value for an event action as
          defined in <a href="#sect-4.5" class="xref">Section 4.5</a>.<a href="#section-10.2-3.2.2.4" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-10.2-3.2.2.5">"domain variant relation" -- denotes a relationship between a
          domain and a domain variant as defined in <a href="#sect-5.3" class="xref">Section 5.3</a>.<a href="#section-10.2-3.2.2.5" class="pilcrow">¶</a>
</li>
            </ul>
</li>
          <li id="section-10.2-3.3">Description -- a one- or two-sentence description regarding the
       meaning of the value, how it might be used, and/or how it should
       be interpreted by clients.<a href="#section-10.2-3.3" class="pilcrow">¶</a>
</li>
          <li id="section-10.2-3.4">Registrant Name -- the name of the person registering the value.<a href="#section-10.2-3.4" class="pilcrow">¶</a>
</li>
          <li id="section-10.2-3.5">Registrant Contact Information -- an email address, postal
       address, or some other information to be used to contact the
       registrant.<a href="#section-10.2-3.5" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-10.2-4">
   This registry is operated under the "Expert Review" policy defined in
   <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.<a href="#section-10.2-4" class="pilcrow">¶</a></p>
<p id="section-10.2-5">
   Review of registrations into this registry by the designated
   expert(s) should be narrowly judged on the following criteria:<a href="#section-10.2-5" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-10.2-6">
<li id="section-10.2-6.1">Values in need of being placed into multiple types must be
       assigned a separate registration for each type.<a href="#section-10.2-6.1" class="pilcrow">¶</a>
</li>
          <li id="section-10.2-6.2">Values must be strings.  They should be multiple words separated
       by single space characters.  Every character should be
       lowercased.  If possible, every word should be given in English
       and each character should be US-ASCII.<a href="#section-10.2-6.2" class="pilcrow">¶</a>
</li>
          <li id="section-10.2-6.3">Registrations should not duplicate the meaning of any existing
       registration.  That is, if a request for a registration is
       significantly similar in nature to an existing registration, the
       request should be denied.  For example, the terms "maintainer"
       and "registrant" are significantly similar in nature as they both
       denote a holder of a domain name or Internet number resource.  In
       cases where it may be reasonably argued that machine
       interpretation of two similar values may alter the operation of
       client software, designated experts should not judge the values
       to be of significant similarity.<a href="#section-10.2-6.3" class="pilcrow">¶</a>
</li>
          <li id="section-10.2-6.4">Registrations should be relevant to the common usages of RDAP.
       Designated experts may rely upon the serving of the value by a
       DNR or RIR to make this determination.<a href="#section-10.2-6.4" class="pilcrow">¶</a>
</li>
        </ol>
<p id="section-10.2-7">
   The following sections provide initial registrations into this
   registry.<a href="#section-10.2-7" class="pilcrow">¶</a></p>
<div id="sect-10.2.1">
<section id="section-10.2.1">
          <h4 id="name-notice-and-remark-types">
<a href="#section-10.2.1" class="section-number selfRef">10.2.1. </a><a href="#name-notice-and-remark-types" class="section-name selfRef">Notice and Remark Types</a>
          </h4>
<p id="section-10.2.1-1">
   The following values have been registered in the "RDAP JSON Values"
   registry:<a href="#section-10.2.1-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.1-2">
            <dt id="section-10.2.1-2.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-2.2">result set truncated due to authorization<a href="#section-10.2.1-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-2.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-2.4">notice and remark type<a href="#section-10.2.1-2.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-2.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-2.6">The list of results does not contain all results due to lack of authorization.
                                           This may indicate to some clients that proper authorization will yield a longer result
                                           set.<a href="#section-10.2.1-2.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-2.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-2.8">IESG<a href="#section-10.2.1-2.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-2.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-2.10">iesg@ietf.org<a href="#section-10.2.1-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.1-3">
            <dt id="section-10.2.1-3.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-3.2">result set truncated due to excessive load<a href="#section-10.2.1-3.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-3.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-3.4">notice and remark type<a href="#section-10.2.1-3.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-3.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-3.6">The list of results does not contain all results due to an excessively heavy load on the server.
                                        This may indicate to some clients that requerying at a later time will yield a longer result
                                        set.<a href="#section-10.2.1-3.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-3.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-3.8">IESG<a href="#section-10.2.1-3.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-3.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-3.10">iesg@ietf.org<a href="#section-10.2.1-3.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.1-4">
            <dt id="section-10.2.1-4.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-4.2">result set truncated due to unexplainable reasons<a href="#section-10.2.1-4.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-4.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-4.4">notice and remark type<a href="#section-10.2.1-4.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-4.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-4.6">The list of results does not contain all results for an unexplainable reason.
                                        This may indicate to some clients that requerying for any reason will not yield a longer result set.<a href="#section-10.2.1-4.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-4.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-4.8">IESG<a href="#section-10.2.1-4.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-4.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-4.10">iesg@ietf.org<a href="#section-10.2.1-4.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.1-5">
            <dt id="section-10.2.1-5.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-5.2">object truncated due to authorization<a href="#section-10.2.1-5.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-5.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-5.4">notice and remark type<a href="#section-10.2.1-5.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-5.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-5.6">The object does not contain all data due to lack of authorization.<a href="#section-10.2.1-5.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-5.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-5.8">IESG<a href="#section-10.2.1-5.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-5.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-5.10">iesg@ietf.org<a href="#section-10.2.1-5.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.1-6">
            <dt id="section-10.2.1-6.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-6.2">object truncated due to excessive load<a href="#section-10.2.1-6.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-6.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-6.4">notice and remark type<a href="#section-10.2.1-6.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-6.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-6.6">The object does not contain all data due to an excessively heavy load on the server.
                                       This may indicate to some clients that requerying at a later time will yield all data of the object.<a href="#section-10.2.1-6.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-6.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-6.8">IESG<a href="#section-10.2.1-6.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-6.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-6.10">iesg@ietf.org<a href="#section-10.2.1-6.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.1-7">
            <dt id="section-10.2.1-7.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-7.2">object truncated due to unexplainable reasons<a href="#section-10.2.1-7.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-7.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-7.4">notice and remark type<a href="#section-10.2.1-7.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-7.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-7.6">The object does not contain all data for an unexplainable reason.<a href="#section-10.2.1-7.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-7.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-7.8">IESG<a href="#section-10.2.1-7.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.1-7.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.1-7.10">iesg@ietf.org<a href="#section-10.2.1-7.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</div>
<div id="sect-10.2.2">
<section id="section-10.2.2">
          <h4 id="name-status-2">
<a href="#section-10.2.2" class="section-number selfRef">10.2.2. </a><a href="#name-status-2" class="section-name selfRef">Status</a>
          </h4>
<p id="section-10.2.2-1">The following values have been registered in the "RDAP JSON Values" registry:<a href="#section-10.2.2-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-2">
            <dt id="section-10.2.2-2.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-2.2">validated<a href="#section-10.2.2-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-2.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-2.4">status<a href="#section-10.2.2-2.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-2.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-2.6">Signifies that the data of the object instance has been
                                    found to be accurate. This type of status is usually found on entity
                                    object instances to note the validity of identifying contact
                                    information.<a href="#section-10.2.2-2.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-2.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-2.8">IESG<a href="#section-10.2.2-2.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-2.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-2.10">iesg@ietf.org<a href="#section-10.2.2-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-3">
            <dt id="section-10.2.2-3.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-3.2">renew prohibited<a href="#section-10.2.2-3.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-3.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-3.4">status<a href="#section-10.2.2-3.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-3.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-3.6">Renewal or reregistration of the object instance is forbidden.<a href="#section-10.2.2-3.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-3.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-3.8">IESG<a href="#section-10.2.2-3.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-3.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-3.10">iesg@ietf.org<a href="#section-10.2.2-3.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-4">
            <dt id="section-10.2.2-4.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-4.2">update prohibited<a href="#section-10.2.2-4.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-4.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-4.4">status<a href="#section-10.2.2-4.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-4.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-4.6">Updates to the object instance are forbidden.<a href="#section-10.2.2-4.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-4.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-4.8">IESG<a href="#section-10.2.2-4.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-4.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-4.10">iesg@ietf.org<a href="#section-10.2.2-4.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-5">
            <dt id="section-10.2.2-5.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-5.2">transfer prohibited<a href="#section-10.2.2-5.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-5.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-5.4">status<a href="#section-10.2.2-5.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-5.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-5.6">Transfers of the registration from one registrar
                                    to another are forbidden. This type of status normally applies to DNR
                                    domain names.<a href="#section-10.2.2-5.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-5.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-5.8">IESG<a href="#section-10.2.2-5.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-5.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-5.10">iesg@ietf.org<a href="#section-10.2.2-5.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-6">
            <dt id="section-10.2.2-6.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-6.2">delete prohibited<a href="#section-10.2.2-6.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-6.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-6.4">status<a href="#section-10.2.2-6.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-6.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-6.6">Deletion of the registration of the object
                                    instance is forbidden. This type of status normally applies to DNR
                                    domain names.<a href="#section-10.2.2-6.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-6.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-6.8">IESG<a href="#section-10.2.2-6.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-6.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-6.10">iesg@ietf.org<a href="#section-10.2.2-6.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-7">
            <dt id="section-10.2.2-7.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-7.2">proxy<a href="#section-10.2.2-7.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-7.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-7.4">status<a href="#section-10.2.2-7.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-7.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-7.6">The registration of the object instance has been performed
                                    by a third party. This is most commonly applied to entities.<a href="#section-10.2.2-7.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-7.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-7.8">IESG<a href="#section-10.2.2-7.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-7.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-7.10">iesg@ietf.org<a href="#section-10.2.2-7.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-8">
            <dt id="section-10.2.2-8.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-8.2">private<a href="#section-10.2.2-8.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-8.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-8.4">status<a href="#section-10.2.2-8.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-8.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-8.6">The information of the object instance is not designated
                                    for public consumption. This is most commonly applied to entities.<a href="#section-10.2.2-8.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-8.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-8.8">IESG<a href="#section-10.2.2-8.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-8.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-8.10">iesg@ietf.org<a href="#section-10.2.2-8.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-9">
            <dt id="section-10.2.2-9.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-9.2">removed<a href="#section-10.2.2-9.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-9.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-9.4">status<a href="#section-10.2.2-9.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-9.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-9.6">Some of the information of the object instance has not
                                    been made available and has been removed. This is most commonly applied to entities.<a href="#section-10.2.2-9.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-9.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-9.8">IESG<a href="#section-10.2.2-9.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-9.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-9.10">iesg@ietf.org<a href="#section-10.2.2-9.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-10">
            <dt id="section-10.2.2-10.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-10.2">obscured<a href="#section-10.2.2-10.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-10.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-10.4">status<a href="#section-10.2.2-10.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-10.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-10.6">Some of the information of the object instance has been
                                    altered for the purposes of not readily revealing the actual information
                                    of the object instance. This is most commonly applied to entities.<a href="#section-10.2.2-10.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-10.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-10.8">IESG<a href="#section-10.2.2-10.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-10.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-10.10">iesg@ietf.org<a href="#section-10.2.2-10.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-11">
            <dt id="section-10.2.2-11.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-11.2">associated<a href="#section-10.2.2-11.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-11.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-11.4">status<a href="#section-10.2.2-11.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-11.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-11.6">The object instance is associated with other object instances
                                in the registry. This is most commonly used to signify that a nameserver is
                                associated with a domain or that an entity is associated with a network resource
                                or domain.<a href="#section-10.2.2-11.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-11.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-11.8">IESG<a href="#section-10.2.2-11.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-11.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-11.10">iesg@ietf.org<a href="#section-10.2.2-11.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-12">
            <dt id="section-10.2.2-12.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-12.2">active<a href="#section-10.2.2-12.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-12.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-12.4">status<a href="#section-10.2.2-12.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-12.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-12.6">The object instance is in use. For domain names, it signifies
                                that the domain name is published in DNS. For network and autnum registrations,
                                it signifies that they are allocated or assigned for use in operational networks.
                                This maps to the "OK" status of the Extensible Provisioning Protocol (EPP) <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.<a href="#section-10.2.2-12.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-12.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-12.8">IESG<a href="#section-10.2.2-12.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-12.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-12.10">iesg@ietf.org<a href="#section-10.2.2-12.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-13">
            <dt id="section-10.2.2-13.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-13.2">inactive<a href="#section-10.2.2-13.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-13.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-13.4">status<a href="#section-10.2.2-13.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-13.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-13.6">The object instance is not in use. See "active".<a href="#section-10.2.2-13.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-13.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-13.8">IESG<a href="#section-10.2.2-13.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-13.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-13.10">iesg@ietf.org<a href="#section-10.2.2-13.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-14">
            <dt id="section-10.2.2-14.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-14.2">locked<a href="#section-10.2.2-14.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-14.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-14.4">status<a href="#section-10.2.2-14.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-14.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-14.6">Changes to the object instance cannot be made, including the association of other
                                object instances.<a href="#section-10.2.2-14.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-14.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-14.8">IESG<a href="#section-10.2.2-14.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-14.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-14.10">iesg@ietf.org<a href="#section-10.2.2-14.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-15">
            <dt id="section-10.2.2-15.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-15.2">pending create<a href="#section-10.2.2-15.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-15.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-15.4">status<a href="#section-10.2.2-15.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-15.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-15.6">A request has been received for the creation of the object instance, but
                                this action is not yet complete.<a href="#section-10.2.2-15.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-15.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-15.8">IESG<a href="#section-10.2.2-15.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-15.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-15.10">iesg@ietf.org<a href="#section-10.2.2-15.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-16">
            <dt id="section-10.2.2-16.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-16.2">pending renew<a href="#section-10.2.2-16.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-16.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-16.4">status<a href="#section-10.2.2-16.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-16.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-16.6">A request has been received for the renewal of the object instance, but
                                    this action is not yet complete.<a href="#section-10.2.2-16.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-16.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-16.8">IESG<a href="#section-10.2.2-16.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-16.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-16.10">iesg@ietf.org<a href="#section-10.2.2-16.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-17">
            <dt id="section-10.2.2-17.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-17.2">pending transfer<a href="#section-10.2.2-17.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-17.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-17.4">status<a href="#section-10.2.2-17.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-17.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-17.6">A request has been received for the transfer of the object instance, but
                                    this action is not yet complete.<a href="#section-10.2.2-17.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-17.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-17.8">IESG<a href="#section-10.2.2-17.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-17.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-17.10">iesg@ietf.org<a href="#section-10.2.2-17.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-18">
            <dt id="section-10.2.2-18.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-18.2">pending update<a href="#section-10.2.2-18.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-18.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-18.4">status<a href="#section-10.2.2-18.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-18.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-18.6">A request has been received for the update or modification of the object instance, but
                                    this action is not yet complete.<a href="#section-10.2.2-18.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-18.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-18.8">IESG<a href="#section-10.2.2-18.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-18.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-18.10">iesg@ietf.org<a href="#section-10.2.2-18.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.2-19">
            <dt id="section-10.2.2-19.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-19.2">pending delete<a href="#section-10.2.2-19.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-19.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-19.4">status<a href="#section-10.2.2-19.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-19.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-19.6">A request has been received for the deletion or removal of the object instance, but
                                    this action is not yet complete. For domains, this might mean that the name is no longer published
                                in DNS but has not yet been purged from the registry database.<a href="#section-10.2.2-19.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-19.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-19.8">IESG<a href="#section-10.2.2-19.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.2-19.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.2-19.10">iesg@ietf.org<a href="#section-10.2.2-19.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</div>
<div id="sect-10.2.3">
<section id="section-10.2.3">
          <h4 id="name-event-actions">
<a href="#section-10.2.3" class="section-number selfRef">10.2.3. </a><a href="#name-event-actions" class="section-name selfRef">Event Actions</a>
          </h4>
<p id="section-10.2.3-1">
   The following values have been registered in the "RDAP JSON Values"
   registry:<a href="#section-10.2.3-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-2">
            <dt id="section-10.2.3-2.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-2.2">registration<a href="#section-10.2.3-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-2.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-2.4">event action<a href="#section-10.2.3-2.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-2.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-2.6">The object instance was initially registered.<a href="#section-10.2.3-2.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-2.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-2.8">IESG<a href="#section-10.2.3-2.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-2.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-2.10">iesg@ietf.org<a href="#section-10.2.3-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-3">
            <dt id="section-10.2.3-3.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-3.2">reregistration<a href="#section-10.2.3-3.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-3.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-3.4">event action<a href="#section-10.2.3-3.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-3.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-3.6">The object instance was registered subsequently to initial registration.<a href="#section-10.2.3-3.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-3.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-3.8">IESG<a href="#section-10.2.3-3.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-3.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-3.10">iesg@ietf.org<a href="#section-10.2.3-3.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-4">
            <dt id="section-10.2.3-4.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-4.2">last changed<a href="#section-10.2.3-4.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-4.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-4.4">event action<a href="#section-10.2.3-4.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-4.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-4.6">An action noting when the information in the object instance was last changed.<a href="#section-10.2.3-4.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-4.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-4.8">IESG<a href="#section-10.2.3-4.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-4.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-4.10">iesg@ietf.org<a href="#section-10.2.3-4.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-5">
            <dt id="section-10.2.3-5.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-5.2">expiration<a href="#section-10.2.3-5.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-5.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-5.4">event action<a href="#section-10.2.3-5.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-5.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-5.6">The object instance has been removed or will be removed at a predetermined
                                    date and time from the registry.<a href="#section-10.2.3-5.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-5.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-5.8">IESG<a href="#section-10.2.3-5.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-5.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-5.10">iesg@ietf.org<a href="#section-10.2.3-5.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-6">
            <dt id="section-10.2.3-6.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-6.2">deletion<a href="#section-10.2.3-6.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-6.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-6.4">event action<a href="#section-10.2.3-6.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-6.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-6.6">The object instance was removed from the registry at a point in time that was not predetermined.<a href="#section-10.2.3-6.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-6.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-6.8">IESG<a href="#section-10.2.3-6.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-6.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-6.10">iesg@ietf.org<a href="#section-10.2.3-6.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-7">
            <dt id="section-10.2.3-7.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-7.2">reinstantiation<a href="#section-10.2.3-7.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-7.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-7.4">event action<a href="#section-10.2.3-7.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-7.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-7.6">The object instance was reregistered after having been
                                    removed from the registry.<a href="#section-10.2.3-7.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-7.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-7.8">IESG<a href="#section-10.2.3-7.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-7.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-7.10">iesg@ietf.org<a href="#section-10.2.3-7.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-8">
            <dt id="section-10.2.3-8.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-8.2">transfer<a href="#section-10.2.3-8.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-8.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-8.4">event action<a href="#section-10.2.3-8.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-8.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-8.6">The object instance was transferred from one registrar to another.<a href="#section-10.2.3-8.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-8.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-8.8">IESG<a href="#section-10.2.3-8.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-8.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-8.10">iesg@ietf.org<a href="#section-10.2.3-8.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-9">
            <dt id="section-10.2.3-9.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-9.2">locked<a href="#section-10.2.3-9.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-9.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-9.4">event action<a href="#section-10.2.3-9.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-9.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-9.6">The object instance was locked (see the "locked" status).<a href="#section-10.2.3-9.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-9.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-9.8">IESG<a href="#section-10.2.3-9.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-9.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-9.10">iesg@ietf.org<a href="#section-10.2.3-9.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.3-10">
            <dt id="section-10.2.3-10.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-10.2">unlocked<a href="#section-10.2.3-10.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-10.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-10.4">event action<a href="#section-10.2.3-10.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-10.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-10.6">The object instance was unlocked (see the "locked" status).<a href="#section-10.2.3-10.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-10.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-10.8">IESG<a href="#section-10.2.3-10.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.3-10.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.3-10.10">iesg@ietf.org<a href="#section-10.2.3-10.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</div>
<div id="sect-10.2.4">
<section id="section-10.2.4">
          <h4 id="name-roles">
<a href="#section-10.2.4" class="section-number selfRef">10.2.4. </a><a href="#name-roles" class="section-name selfRef">Roles</a>
          </h4>
<p id="section-10.2.4-1">
   The following values have been registered in the "RDAP JSON Values"
   registry:<a href="#section-10.2.4-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-2">
            <dt id="section-10.2.4-2.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-2.2">registrant<a href="#section-10.2.4-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-2.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-2.4">role<a href="#section-10.2.4-2.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-2.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-2.6">The entity object instance is the registrant of the
                                    registration. In some registries, this is known as a maintainer.<a href="#section-10.2.4-2.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-2.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-2.8">IESG<a href="#section-10.2.4-2.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-2.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-2.10">iesg@ietf.org<a href="#section-10.2.4-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-3">
            <dt id="section-10.2.4-3.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-3.2">technical<a href="#section-10.2.4-3.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-3.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-3.4">role<a href="#section-10.2.4-3.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-3.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-3.6">The entity object instance is a technical contact for the
                                    registration.<a href="#section-10.2.4-3.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-3.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-3.8">IESG<a href="#section-10.2.4-3.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-3.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-3.10">iesg@ietf.org<a href="#section-10.2.4-3.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-4">
            <dt id="section-10.2.4-4.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-4.2">administrative<a href="#section-10.2.4-4.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-4.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-4.4">role<a href="#section-10.2.4-4.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-4.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-4.6">The entity object instance is an administrative contact for
                                    the registration.<a href="#section-10.2.4-4.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-4.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-4.8">IESG<a href="#section-10.2.4-4.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-4.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-4.10">iesg@ietf.org<a href="#section-10.2.4-4.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-5">
            <dt id="section-10.2.4-5.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-5.2">abuse<a href="#section-10.2.4-5.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-5.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-5.4">role<a href="#section-10.2.4-5.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-5.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-5.6">The entity object instance handles network abuse issues on
                                    behalf of the registrant of the registration.<a href="#section-10.2.4-5.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-5.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-5.8">IESG<a href="#section-10.2.4-5.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-5.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-5.10">iesg@ietf.org<a href="#section-10.2.4-5.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-6">
            <dt id="section-10.2.4-6.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-6.2">billing<a href="#section-10.2.4-6.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-6.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-6.4">role<a href="#section-10.2.4-6.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-6.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-6.6">The entity object instance handles payment and billing
                                    issues on behalf of the registrant of the registration.<a href="#section-10.2.4-6.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-6.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-6.8">IESG<a href="#section-10.2.4-6.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-6.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-6.10">iesg@ietf.org<a href="#section-10.2.4-6.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-7">
            <dt id="section-10.2.4-7.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-7.2">registrar<a href="#section-10.2.4-7.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-7.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-7.4">role<a href="#section-10.2.4-7.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-7.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-7.6">The entity object instance represents the authority
                                    responsible for the registration in the registry.<a href="#section-10.2.4-7.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-7.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-7.8">IESG<a href="#section-10.2.4-7.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-7.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-7.10">iesg@ietf.org<a href="#section-10.2.4-7.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-8">
            <dt id="section-10.2.4-8.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-8.2">reseller<a href="#section-10.2.4-8.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-8.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-8.4">role<a href="#section-10.2.4-8.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-8.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-8.6">The entity object instance represents a third party
                                    through which the registration was conducted (i.e., not the registry or registrar).<a href="#section-10.2.4-8.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-8.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-8.8">IESG<a href="#section-10.2.4-8.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-8.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-8.10">iesg@ietf.org<a href="#section-10.2.4-8.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-9">
            <dt id="section-10.2.4-9.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-9.2">sponsor<a href="#section-10.2.4-9.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-9.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-9.4">role<a href="#section-10.2.4-9.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-9.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-9.6">The entity object instance represents a domain policy
                                    sponsor, such as an ICANN-approved sponsor.<a href="#section-10.2.4-9.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-9.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-9.8">IESG<a href="#section-10.2.4-9.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-9.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-9.10">iesg@ietf.org<a href="#section-10.2.4-9.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-10">
            <dt id="section-10.2.4-10.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-10.2">proxy<a href="#section-10.2.4-10.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-10.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-10.4">role<a href="#section-10.2.4-10.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-10.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-10.6">The entity object instance represents a proxy for another
                                entity object, such as a registrant.<a href="#section-10.2.4-10.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-10.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-10.8">IESG<a href="#section-10.2.4-10.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-10.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-10.10">iesg@ietf.org<a href="#section-10.2.4-10.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-11">
            <dt id="section-10.2.4-11.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-11.2">notifications<a href="#section-10.2.4-11.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-11.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-11.4">role<a href="#section-10.2.4-11.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-11.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-11.6">An entity object instance designated to receive notifications about
                                association object instances.<a href="#section-10.2.4-11.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-11.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-11.8">IESG<a href="#section-10.2.4-11.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-11.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-11.10">iesg@ietf.org<a href="#section-10.2.4-11.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.4-12">
            <dt id="section-10.2.4-12.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-12.2">noc<a href="#section-10.2.4-12.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-12.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-12.4">role<a href="#section-10.2.4-12.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-12.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-12.6">The entity object instance handles communications related to a
                                network operations center (NOC).<a href="#section-10.2.4-12.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-12.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-12.8">IESG<a href="#section-10.2.4-12.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.4-12.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.4-12.10">iesg@ietf.org<a href="#section-10.2.4-12.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</div>
<div id="sect-10.2.5">
<section id="section-10.2.5">
          <h4 id="name-variant-relations">
<a href="#section-10.2.5" class="section-number selfRef">10.2.5. </a><a href="#name-variant-relations" class="section-name selfRef">Variant Relations</a>
          </h4>
<p id="section-10.2.5-1">
   The following values have been registered in the "RDAP JSON Values"
   registry:<a href="#section-10.2.5-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.5-2">
            <dt id="section-10.2.5-2.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-2.2">registered<a href="#section-10.2.5-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-2.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-2.4">domain variant relation<a href="#section-10.2.5-2.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-2.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-2.6">The variant names are registered in the registry.<a href="#section-10.2.5-2.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-2.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-2.8">IESG<a href="#section-10.2.5-2.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-2.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-2.10">iesg@ietf.org<a href="#section-10.2.5-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.5-3">
            <dt id="section-10.2.5-3.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-3.2">unregistered<a href="#section-10.2.5-3.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-3.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-3.4">domain variant relation<a href="#section-10.2.5-3.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-3.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-3.6">The variant names are not found in the registry.<a href="#section-10.2.5-3.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-3.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-3.8">IESG<a href="#section-10.2.5-3.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-3.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-3.10">iesg@ietf.org<a href="#section-10.2.5-3.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.5-4">
            <dt id="section-10.2.5-4.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-4.2">registration restricted<a href="#section-10.2.5-4.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-4.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-4.4">domain variant relation<a href="#section-10.2.5-4.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-4.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-4.6">Registration of the variant names is
                                    restricted to certain parties or within certain rules.<a href="#section-10.2.5-4.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-4.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-4.8">IESG<a href="#section-10.2.5-4.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-4.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-4.10">iesg@ietf.org<a href="#section-10.2.5-4.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.5-5">
            <dt id="section-10.2.5-5.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-5.2">open registration<a href="#section-10.2.5-5.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-5.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-5.4">domain variant relation<a href="#section-10.2.5-5.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-5.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-5.6">Registration of the variant names is available to
                                    generally qualified registrants.<a href="#section-10.2.5-5.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-5.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-5.8">IESG<a href="#section-10.2.5-5.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-5.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-5.10">iesg@ietf.org<a href="#section-10.2.5-5.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-10.2.5-6">
            <dt id="section-10.2.5-6.1">Value:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-6.2">conjoined<a href="#section-10.2.5-6.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-6.3">Type:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-6.4">domain variant relation<a href="#section-10.2.5-6.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-6.5">Description:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-6.6">Registration of the variant names occurs automatically with the
                                    registration of the containing domain registration.<a href="#section-10.2.5-6.6" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-6.7">Registrant Name:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-6.8">IESG<a href="#section-10.2.5-6.8" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-10.2.5-6.9">Registrant Contact Information:</dt>
            <dd style="margin-left: 1.5em" id="section-10.2.5-6.10">iesg@ietf.org<a href="#section-10.2.5-6.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</div>
</section>
</div>
</section>
</div>
<div id="sect-11">
<section id="section-11">
      <h2 id="name-security-considerations">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-11-1">
   This specification models information serialized in JSON format.  As
   JSON is a subset of JavaScript, implementations are advised to follow
   the security considerations outlined in <span><a href="https://www.rfc-editor.org/rfc/rfc8259#section-12" class="relref">Section 12</a> of [<a href="#RFC8259" class="xref">RFC8259</a>]</span> to
   prevent code injection.<a href="#section-11-1" class="pilcrow">¶</a></p>
<p id="section-11-2">
   Though not specific to JSON, RDAP implementers should be aware of the
   security considerations specified in <span>[<a href="#RFC7480" class="xref">RFC7480</a>]</span> and the security
   requirements and considerations in <span>[<a href="#RFC7481" class="xref">RFC7481</a>]</span>.<a href="#section-11-2" class="pilcrow">¶</a></p>
<p id="section-11-3">RDAP responses allow for retrieval of DNSSEC (key) related information,
   but the RRSIG DS from the parent zone is not conveyed alongside it.
   This means that the DNSSEC keys retrieved by RDAP are disconnected
   from their containing PKI, and as such are not generally expected to
   be trusted without additional information. In particular, the HTTPS
   channel protecting the RDAP connection is not expected to be authorized
   to certify the validity of the DNSSEC keys.<a href="#section-11-3" class="pilcrow">¶</a></p>
<p id="section-11-4">
   Clients caching data, especially clients using RDAP-specific caches
   (instead of HTTP-layer caches), should have safeguards to prevent
   cache poisoning.  See <a href="#sect-5" class="xref">Section 5</a> for advice on using the self links
   for caching.<a href="#section-11-4" class="pilcrow">¶</a></p>
<p id="section-11-5">
   Finally, service operators should be aware of the privacy mechanisms
   noted in <a href="#sect-13" class="xref">Section 13</a>.<a href="#section-11-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-12">
<section id="section-12">
      <h2 id="name-internationalization-consid">
<a href="#section-12" class="section-number selfRef">12. </a><a href="#name-internationalization-consid" class="section-name selfRef">Internationalization Considerations</a>
      </h2>
<div id="sect-12.1">
<section id="section-12.1">
        <h3 id="name-character-encoding">
<a href="#section-12.1" class="section-number selfRef">12.1. </a><a href="#name-character-encoding" class="section-name selfRef">Character Encoding</a>
        </h3>
<p id="section-12.1-1">
   The default text encoding for JSON responses in RDAP is UTF-8
   <span>[<a href="#RFC3629" class="xref">RFC3629</a>]</span>, and all servers and clients <span class="bcp14">MUST</span> support UTF-8.<a href="#section-12.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-12.2">
<section id="section-12.2">
        <h3 id="name-uris-and-iris">
<a href="#section-12.2" class="section-number selfRef">12.2. </a><a href="#name-uris-and-iris" class="section-name selfRef">URIs and IRIs</a>
        </h3>
<p id="section-12.2-1">
   <span>[<a href="#RFC7480" class="xref">RFC7480</a>]</span> defines the use of URIs and IRIs in RDAP.<a href="#section-12.2-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-12.3">
<section id="section-12.3">
        <h3 id="name-language-tags">
<a href="#section-12.3" class="section-number selfRef">12.3. </a><a href="#name-language-tags" class="section-name selfRef">Language Tags</a>
        </h3>
<p id="section-12.3-1">
   <a href="#sect-4.4" class="xref">Section 4.4</a> defines the use of language tags in the JSON responses
   defined in this document.<a href="#section-12.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-12.4">
<section id="section-12.4">
        <h3 id="name-internationalized-domain-na">
<a href="#section-12.4" class="section-number selfRef">12.4. </a><a href="#name-internationalized-domain-na" class="section-name selfRef">Internationalized Domain Names</a>
        </h3>
<p id="section-12.4-1">
   IDNs are denoted in this specification by the separation of DNS names
   in LDH form and Unicode form (see <a href="#sect-3" class="xref">Section 3</a>).  Representation of IDNs
   in registries is described by the "variants" object in <a href="#sect-5.3" class="xref">Section 5.3</a>
   and the suggested values listed in <a href="#sect-10.2.5" class="xref">Section 10.2.5</a>.<a href="#section-12.4-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="sect-13">
<section id="section-13">
      <h2 id="name-privacy-considerations">
<a href="#section-13" class="section-number selfRef">13. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a>
      </h2>
<p id="section-13-1">
   This specification suggests status values to denote contact and
   registrant information that has been marked as private and/or has
   been removed or obscured.  See <a href="#sect-10.2.2" class="xref">Section 10.2.2</a> for the complete list
   of status values.  A few of the status values indicate that there are
   privacy concerns associated with the object instance.  The following
   status codes <span class="bcp14">SHOULD</span> be used to describe data elements of a response
   when appropriate:<a href="#section-13-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-13-2.1">
      private -- The object is not be shared in query responses, unless
      the user is authorized to view this information.<a href="#section-13-2.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-13-2.2">
      removed -- Data elements within the object have been collected but
      have been omitted from the response.  This option can be used to
      prevent unauthorized access to associated object instances without
      the need to mark them as private.<a href="#section-13-2.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-13-2.3">
      obscured -- Data elements within the object have been collected,
      but the response value has been altered so that values are not
      easily discernible.  A value changed from "1212" to "XXXX" is an
      example of obscured data.  This option may reveal privacy
      sensitive information and should only be used when data
      sensitivity does not require a more protective option like
      "private" or "removed".<a href="#section-13-2.3" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-13-3">
   See <a href="#sect-a.1" class="xref">Appendix A.1</a> for an example of applying those values to contacts
   and registrants.<a href="#section-13-3" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-14">
      <h2 id="name-references">
<a href="#section-14" class="section-number selfRef">14. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-14.1">
        <h3 id="name-normative-references">
<a href="#section-14.1" class="section-number selfRef">14.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="ISO.3166.2020">[ISO.3166.2020]</dt>
        <dd>
<span class="refAuthor">International Organization for Standardization</span>, <span class="refTitle">"Codes for the representation of names of countries and their subdivisions"</span>, <span class="refContent">Fourth edition</span>, <span class="seriesInfo">ISO Standard 3166</span>, <time datetime="2020-08" class="refDate">August 2020</time>. </dd>
<dd class="break"></dd>
<dt id="RFC2119">[RFC2119]</dt>
        <dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3339">[RFC3339]</dt>
        <dd>
<span class="refAuthor">Klyne, G.</span> and <span class="refAuthor">C. Newman</span>, <span class="refTitle">"Date and Time on the Internet: Timestamps"</span>, <span class="seriesInfo">RFC 3339</span>, <span class="seriesInfo">DOI 10.17487/RFC3339</span>, <time datetime="2002-07" class="refDate">July 2002</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3339">https://www.rfc-editor.org/info/rfc3339</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3629">[RFC3629]</dt>
        <dd>
<span class="refAuthor">Yergeau, F.</span>, <span class="refTitle">"UTF-8, a transformation format of ISO 10646"</span>, <span class="seriesInfo">STD 63</span>, <span class="seriesInfo">RFC 3629</span>, <span class="seriesInfo">DOI 10.17487/RFC3629</span>, <time datetime="2003-11" class="refDate">November 2003</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3629">https://www.rfc-editor.org/info/rfc3629</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3986">[RFC3986]</dt>
        <dd>
<span class="refAuthor">Berners-Lee, T.</span>, <span class="refAuthor">Fielding, R.</span>, and <span class="refAuthor">L. Masinter</span>, <span class="refTitle">"Uniform Resource Identifier (URI): Generic Syntax"</span>, <span class="seriesInfo">STD 66</span>, <span class="seriesInfo">RFC 3986</span>, <span class="seriesInfo">DOI 10.17487/RFC3986</span>, <time datetime="2005-01" class="refDate">January 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3986">https://www.rfc-editor.org/info/rfc3986</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4034">[RFC4034]</dt>
        <dd>
<span class="refAuthor">Arends, R.</span>, <span class="refAuthor">Austein, R.</span>, <span class="refAuthor">Larson, M.</span>, <span class="refAuthor">Massey, D.</span>, and <span class="refAuthor">S. Rose</span>, <span class="refTitle">"Resource Records for the DNS Security Extensions"</span>, <span class="seriesInfo">RFC 4034</span>, <span class="seriesInfo">DOI 10.17487/RFC4034</span>, <time datetime="2005-03" class="refDate">March 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4034">https://www.rfc-editor.org/info/rfc4034</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5396">[RFC5396]</dt>
        <dd>
<span class="refAuthor">Huston, G.</span> and <span class="refAuthor">G. Michaelson</span>, <span class="refTitle">"Textual Representation of Autonomous System (AS) Numbers"</span>, <span class="seriesInfo">RFC 5396</span>, <span class="seriesInfo">DOI 10.17487/RFC5396</span>, <time datetime="2008-12" class="refDate">December 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5396">https://www.rfc-editor.org/info/rfc5396</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5646">[RFC5646]</dt>
        <dd>
<span class="refAuthor">Phillips, A., Ed.</span> and <span class="refAuthor">M. Davis, Ed.</span>, <span class="refTitle">"Tags for Identifying Languages"</span>, <span class="seriesInfo">BCP 47</span>, <span class="seriesInfo">RFC 5646</span>, <span class="seriesInfo">DOI 10.17487/RFC5646</span>, <time datetime="2009-09" class="refDate">September 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5646">https://www.rfc-editor.org/info/rfc5646</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5890">[RFC5890]</dt>
        <dd>
<span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework"</span>, <span class="seriesInfo">RFC 5890</span>, <span class="seriesInfo">DOI 10.17487/RFC5890</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5890">https://www.rfc-editor.org/info/rfc5890</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5952">[RFC5952]</dt>
        <dd>
<span class="refAuthor">Kawamura, S.</span> and <span class="refAuthor">M. Kawashima</span>, <span class="refTitle">"A Recommendation for IPv6 Address Text Representation"</span>, <span class="seriesInfo">RFC 5952</span>, <span class="seriesInfo">DOI 10.17487/RFC5952</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5952">https://www.rfc-editor.org/info/rfc5952</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7095">[RFC7095]</dt>
        <dd>
<span class="refAuthor">Kewisch, P.</span>, <span class="refTitle">"jCard: The JSON Format for vCard"</span>, <span class="seriesInfo">RFC 7095</span>, <span class="seriesInfo">DOI 10.17487/RFC7095</span>, <time datetime="2014-01" class="refDate">January 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7095">https://www.rfc-editor.org/info/rfc7095</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7480">[RFC7480]</dt>
        <dd>
<span class="refAuthor">Newton, A.</span>, <span class="refAuthor">Ellacott, B.</span>, and <span class="refAuthor">N. Kong</span>, <span class="refTitle">"HTTP Usage in the Registration Data Access Protocol (RDAP)"</span>, <span class="seriesInfo">STD 95</span>, <span class="seriesInfo">RFC 7480</span>, <span class="seriesInfo">DOI 10.17487/RFC7480</span>, <time datetime="2015-03" class="refDate">March 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7480">https://www.rfc-editor.org/info/rfc7480</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7481">[RFC7481]</dt>
        <dd>
<span class="refAuthor">Hollenbeck, S.</span> and <span class="refAuthor">N. Kong</span>, <span class="refTitle">"Security Services for the Registration Data Access Protocol (RDAP)"</span>, <span class="seriesInfo">STD 95</span>, <span class="seriesInfo">RFC 7481</span>, <span class="seriesInfo">DOI 10.17487/RFC7481</span>, <time datetime="2015-03" class="refDate">March 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7481">https://www.rfc-editor.org/info/rfc7481</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8126">[RFC8126]</dt>
        <dd>
<span class="refAuthor">Cotton, M.</span>, <span class="refAuthor">Leiba, B.</span>, and <span class="refAuthor">T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06" class="refDate">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8174">[RFC8174]</dt>
        <dd>
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8259">[RFC8259]</dt>
        <dd>
<span class="refAuthor">Bray, T., Ed.</span>, <span class="refTitle">"The JavaScript Object Notation (JSON) Data Interchange Format"</span>, <span class="seriesInfo">STD 90</span>, <span class="seriesInfo">RFC 8259</span>, <span class="seriesInfo">DOI 10.17487/RFC8259</span>, <time datetime="2017-12" class="refDate">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8259">https://www.rfc-editor.org/info/rfc8259</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8288">[RFC8288]</dt>
        <dd>
<span class="refAuthor">Nottingham, M.</span>, <span class="refTitle">"Web Linking"</span>, <span class="seriesInfo">RFC 8288</span>, <span class="seriesInfo">DOI 10.17487/RFC8288</span>, <time datetime="2017-10" class="refDate">October 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8288">https://www.rfc-editor.org/info/rfc8288</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9082">[RFC9082]</dt>
      <dd>
<span class="refAuthor">Hollenbeck, S.</span> and <span class="refAuthor">A. Newton</span>, <span class="refTitle">"Registration Data Access Protocol (RDAP) Query Format"</span>, <span class="seriesInfo">STD 95</span>, <span class="seriesInfo">RFC 9082</span>, <span class="seriesInfo">DOI 10.17487/RFC9082</span>, <time datetime="2021-06" class="refDate">June 2021</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9082">https://www.rfc-editor.org/info/rfc9082</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-14.2">
        <h3 id="name-informative-references">
<a href="#section-14.2" class="section-number selfRef">14.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="IANA_IDNTABLES">[IANA_IDNTABLES]</dt>
        <dd>
<span class="refAuthor">IANA</span>, <span class="refTitle">"Repository of IDN Practices"</span>, <span>&lt;<a href="https://www.iana.org/domains/idn-tables">https://www.iana.org/domains/idn-tables</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="JSON_ascendancy">[JSON_ascendancy]</dt>
        <dd>
<span class="refAuthor">MacVittie, L.</span>, <span class="refTitle">"The Stealthy Ascendancy of JSON"</span>, <time datetime="2011-04" class="refDate">April 2011</time>, <span>&lt;<a href="https://devcentral.f5.com/s/articles/the-stealthy-ascendancy-of-json">https://devcentral.f5.com/s/articles/the-stealthy-ascendancy-of-json</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="JSON_performance_study">[JSON_performance_study]</dt>
        <dd>
<span class="refAuthor">Nurseitov, N.</span>, <span class="refAuthor">Paulson, M.</span>, <span class="refAuthor">Reynolds, R.</span>, and <span class="refAuthor">C. Izurieta</span>, <span class="refTitle">"Comparison of JSON and XML Data Interchange Formats: A Case Study"</span>, <time datetime="2009" class="refDate">2009</time>, <span>&lt;<a href="https://www.cs.montana.edu/izurieta/pubs/caine2009.pdf">https://www.cs.montana.edu/izurieta/pubs/caine2009.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3912">[RFC3912]</dt>
        <dd>
<span class="refAuthor">Daigle, L.</span>, <span class="refTitle">"WHOIS Protocol Specification"</span>, <span class="seriesInfo">RFC 3912</span>, <span class="seriesInfo">DOI 10.17487/RFC3912</span>, <time datetime="2004-09" class="refDate">September 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3912">https://www.rfc-editor.org/info/rfc3912</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5730">[RFC5730]</dt>
        <dd>
<span class="refAuthor">Hollenbeck, S.</span>, <span class="refTitle">"Extensible Provisioning Protocol (EPP)"</span>, <span class="seriesInfo">STD 69</span>, <span class="seriesInfo">RFC 5730</span>, <span class="seriesInfo">DOI 10.17487/RFC5730</span>, <time datetime="2009-08" class="refDate">August 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5730">https://www.rfc-editor.org/info/rfc5730</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5910">[RFC5910]</dt>
        <dd>
<span class="refAuthor">Gould, J.</span> and <span class="refAuthor">S. Hollenbeck</span>, <span class="refTitle">"Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)"</span>, <span class="seriesInfo">RFC 5910</span>, <span class="seriesInfo">DOI 10.17487/RFC5910</span>, <time datetime="2010-05" class="refDate">May 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5910">https://www.rfc-editor.org/info/rfc5910</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6350">[RFC6350]</dt>
        <dd>
<span class="refAuthor">Perreault, S.</span>, <span class="refTitle">"vCard Format Specification"</span>, <span class="seriesInfo">RFC 6350</span>, <span class="seriesInfo">DOI 10.17487/RFC6350</span>, <time datetime="2011-08" class="refDate">August 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6350">https://www.rfc-editor.org/info/rfc6350</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6839">[RFC6839]</dt>
      <dd>
<span class="refAuthor">Hansen, T.</span> and <span class="refAuthor">A. Melnikov</span>, <span class="refTitle">"Additional Media Type Structured Syntax Suffixes"</span>, <span class="seriesInfo">RFC 6839</span>, <span class="seriesInfo">DOI 10.17487/RFC6839</span>, <time datetime="2013-01" class="refDate">January 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6839">https://www.rfc-editor.org/info/rfc6839</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<div id="sect-a">
<section id="section-appendix.a">
      <h2 id="name-suggested-data-modeling-wit">
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-suggested-data-modeling-wit" class="section-name selfRef">Suggested Data Modeling with the Entity Object Class</a>
      </h2>
<div id="sect-a.1">
<section id="section-a.1">
        <h2 id="name-registrants-and-contacts">
<a href="#section-a.1" class="section-number selfRef">A.1. </a><a href="#name-registrants-and-contacts" class="section-name selfRef">Registrants and Contacts</a>
        </h2>
<p id="section-a.1-1">
   This document does not provide specific object classes for
   registrants and contacts.  Instead, the entity object class may be
   used to represent a registrant or contact.  When the entity object is
   embedded inside a containing object such as a domain name or IP
   network, the "roles" string array can be used to signify the
   relationship.  It is recommended that the values from <a href="#sect-10.2.4" class="xref">Section 10.2.4</a>
   be used.<a href="#section-a.1-1" class="pilcrow">¶</a></p>
<p id="section-a.1-2">
   The following is an example of an elided containing object with an
   embedded entity that is both a registrant and administrative contact:<a href="#section-a.1-2" class="pilcrow">¶</a></p>
<div id="ure-34">
<figure id="figure-34">
          <div id="section-a.1-3.1">
<pre class="sourcecode lang-json">
{
  ...
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle" : "XXXX",
      "vcardArray":[
        "vcard",
        [
          ["version", {}, "text", "4.0"],
          ["fn", {}, "text", "Joe User"],
          ["kind", {}, "text", "individual"],
          ["lang", {
            "pref":"1"
          }, "language-tag", "fr"],
          ["lang", {
            "pref":"2"
          }, "language-tag", "en"],
          ["org", {
            "type":"work"
          }, "text", "Example"],
          ["title", {}, "text", "Research Scientist"],
          ["role", {}, "text", "Project Lead"],
          ["adr",
            { "type":"work" },
            "text",
            [
              "",
              "Suite 1234",
              "4321 Rue Somewhere",
              "Quebec",
              "QC",
              "G1V 2M2",
              "Canada"
            ]
          ],
          ["tel",
            { "type":["work", "voice"], "pref":"1" },
            "uri", "tel:+1-555-555-1234;ext=102"
          ],
          ["email",
            { "type":"work" },
            "text", "joe.user@example.com"
          ]
        ]
      ],
      "roles" : [ "registrant", "administrative" ],
      "remarks" :
      [
        {
          "description" :
          [
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "events" :
      [
        {
          "eventAction" : "registration",
          "eventDate" : "1990-12-31T23:59:59Z"
        },
        {
          "eventAction" : "last changed",
          "eventDate" : "1991-12-31T23:59:59Z"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-34" class="selfRef">Figure 34</a></figcaption></figure>
</div>
<p id="section-a.1-4">
   In many use cases, it is necessary to hide or obscure the information
   of a registrant or contact due to policy or other operational
   matters.  Registries can denote these situations with "status" values
   (see <a href="#sect-10.2.2" class="xref">Section 10.2.2</a>).<a href="#section-a.1-4" class="pilcrow">¶</a></p>
<p id="section-a.1-5">
   The following is an elided example of a registrant with information
   changed to reflect that of a third party.<a href="#section-a.1-5" class="pilcrow">¶</a></p>
<div id="ure-35">
<figure id="figure-35">
          <div id="section-a.1-6.1">
<pre class="sourcecode lang-json">
{
  ...
  "entities" :
  [
    {
      "objectClassName" : "entity",
      "handle" : "XXXX",
      ...
      "roles" : [ "registrant", "administrative" ],
      "status" : [ "proxy", "private", "obscured" ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-35" class="selfRef">Figure 35</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-a.2">
<section id="section-a.2">
        <h2 id="name-registrars">
<a href="#section-a.2" class="section-number selfRef">A.2. </a><a href="#name-registrars" class="section-name selfRef">Registrars</a>
        </h2>
<p id="section-a.2-1">
   This document does not provide a specific object class for
   registrars, but like registrants and contacts (see <a href="#sect-a.1" class="xref">Appendix A.1</a>), the
   "roles" string array maybe used.  Additionally, many registrars have
   publicly assigned identifiers.  The publicIds structure (<a href="#sect-4.8" class="xref">Section 4.8</a>)
   represents that information.<a href="#section-a.2-1" class="pilcrow">¶</a></p>
<p id="section-a.2-2">
   The following is an example of an elided containing object with an
   embedded entity that is a registrar:<a href="#section-a.2-2" class="pilcrow">¶</a></p>
<div id="ure-36">
<figure id="figure-36">
          <div id="section-a.2-3.1">
<pre class="sourcecode lang-json">
{
  ...
  "entities":[
    {
      "objectClassName" : "entity",
      "handle":"XXXX",
      "vcardArray":[
        "vcard",
        [
          ["version", {}, "text", "4.0"],
          ["fn", {}, "text", "Joe's Fish, Chips, and Domains"],
          ["kind", {}, "text", "org"],
          ["lang", {
            "pref":"1"
          }, "language-tag", "fr"],
          ["lang", {
            "pref":"2"
          }, "language-tag", "en"],
          ["org", {
            "type":"work"
          }, "text", "Example"],
          ["adr",
            { "type":"work" },
            "text",
            [
              "",
              "Suite 1234",
              "4321 Rue Somewhere",
              "Quebec",
              "QC",
              "G1V 2M2",
              "Canada"
            ]
          ],
          ["tel",
            {
              "type":["work", "voice"],
              "pref":"1"
            },
            "uri", "tel:+1-555-555-1234;ext=102"
          ],
          ["email",
            { "type":"work" },
            "text", "joes_fish_chips_and_domains@example.com"
          ]
        ]
      ],
      "roles":[ "registrar" ],
      "publicIds":[
        {
          "type":"IANA Registrar ID",
          "identifier":"1"
        }
      ],
      "remarks":[
        {
          "description":[
            "She sells sea shells down by the sea shore.",
            "Originally written by Terry Sullivan."
          ]
        }
      ],
      "links":[
        {
          "value":"https://example.net/entity/XXXX",
          "rel":"alternate",
          "type":"text/html",
          "href":"https://www.example.com"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-36" class="selfRef">Figure 36</a></figcaption></figure>
</div>
</section>
</div>
</section>
</div>
<div id="sect-b">
<section id="section-appendix.b">
      <h2 id="name-modeling-events">
<a href="#section-appendix.b" class="section-number selfRef">Appendix B. </a><a href="#name-modeling-events" class="section-name selfRef">Modeling Events</a>
      </h2>
<p id="section-appendix.b-1">
   Events represent actions that have taken place against a registered
   object at a certain date and time.  Events have three properties: the
   action, the actor, and the date and time of the event (which is
   sometimes in the future).  In some cases, the identity of the actor
   is not captured.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p>
<p id="section-appendix.b-2">
   Events can be modeled in three ways:<a href="#section-appendix.b-2" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-appendix.b-3">
<li id="section-appendix.b-3.1">events with no designated actor<a href="#section-appendix.b-3.1" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.b-3.2">events where the actor is only designated by an identifier<a href="#section-appendix.b-3.2" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.b-3.3">events where the actor can be modeled as an entity<a href="#section-appendix.b-3.3" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-appendix.b-4">
   For the first use case, the events data structure (<a href="#sect-4.5" class="xref">Section 4.5</a>) is
   used without the "eventActor" object member.<a href="#section-appendix.b-4" class="pilcrow">¶</a></p>
<p id="section-appendix.b-5">
   This is an example of an "events" array without the "eventActor".<a href="#section-appendix.b-5" class="pilcrow">¶</a></p>
<div id="ure-37">
<figure id="figure-37">
        <div id="section-appendix.b-6.1">
<pre class="sourcecode lang-json">
"events" :
[
  {
    "eventAction" : "registration",
    "eventDate" : "1990-12-31T23:59:59Z"
  }
]
</pre>
</div>
<figcaption><a href="#figure-37" class="selfRef">Figure 37</a></figcaption></figure>
</div>
<p id="section-appendix.b-7">
   For the second use case, the events data structure (<a href="#sect-4.5" class="xref">Section 4.5</a>) is
   used with the "eventActor" object member.<a href="#section-appendix.b-7" class="pilcrow">¶</a></p>
<p id="section-appendix.b-8">
   This is an example of an "events" array with the "eventActor".<a href="#section-appendix.b-8" class="pilcrow">¶</a></p>
<div id="ure-38">
<figure id="figure-38">
        <div id="section-appendix.b-9.1">
<pre class="sourcecode lang-json">
"events" :
[
  {
    "eventAction" : "registration",
    "eventActor" : "XYZ-NIC",
    "eventDate" : "1990-12-31T23:59:59Z"
  }
]
</pre>
</div>
<figcaption><a href="#figure-38" class="selfRef">Figure 38</a></figcaption></figure>
</div>
<p id="section-appendix.b-10">
   For the third use case, the "asEventActor" array is used when an
   entity (<a href="#sect-5.1" class="xref">Section 5.1</a>) is embedded into another object class.  The
   "asEventActor" array follows the same structure as the "events" array
   but does not have "eventActor" attributes.<a href="#section-appendix.b-10" class="pilcrow">¶</a></p>
<p id="section-appendix.b-11">
   The following is an elided example of a domain object with an entity
   as an event actor.<a href="#section-appendix.b-11" class="pilcrow">¶</a></p>
<div id="ure-39">
<figure id="figure-39">
        <div id="section-appendix.b-12.1">
<pre class="sourcecode lang-json">
{
  "objectClassName" : "domain",
  "handle" : "XXXX",
  "ldhName" : "foo.example",
  "status" : [ "locked", "transfer prohibited" ],
  ...
  "entities" :
  [
    {
      "handle" : "XXXX",
      ...
      "asEventActor" :
      [
        {
          "eventAction" : "last changed",
          "eventDate" : "1990-12-31T23:59:59Z"
        }
      ]
    }
  ]
}
</pre>
</div>
<figcaption><a href="#figure-39" class="selfRef">Figure 39</a></figcaption></figure>
</div>
</section>
</div>
<div id="sect-c">
<section id="section-appendix.c">
      <h2 id="name-structured-vs-unstructured-">
<a href="#section-appendix.c" class="section-number selfRef">Appendix C. </a><a href="#name-structured-vs-unstructured-" class="section-name selfRef">Structured vs. Unstructured Addresses</a>
      </h2>
<p id="section-appendix.c-1">
   The entity (<a href="#sect-5.1" class="xref">Section 5.1</a>) object class uses jCard <span>[<a href="#RFC7095" class="xref">RFC7095</a>]</span> to
   represent contact information, including postal addresses. jCard has
   the ability to represent multiple language preferences, multiple
   email address and phone numbers, and multiple postal addresses in
   both a structured and unstructured format.  This section describes
   the use of jCard for representing structured and unstructured
   addresses.<a href="#section-appendix.c-1" class="pilcrow">¶</a></p>
<p id="section-appendix.c-2">
   The following is an example of a jCard.<a href="#section-appendix.c-2" class="pilcrow">¶</a></p>
<div id="ure-40">
<figure id="figure-40">
        <div id="section-appendix.c-3.1">
<pre class="sourcecode lang-json">
{
  "vcardArray":[
    "vcard",
    [
      ["version", {}, "text", "4.0"],
      ["fn", {}, "text", "Joe User"],
      ["n", {}, "text",
        ["User", "Joe", "", "", ["ing. jr", "M.Sc."]]
      ],
      ["kind", {}, "text", "individual"],
      ["lang", {
        "pref":"1"
      }, "language-tag", "fr"],
      ["lang", {
        "pref":"2"
      }, "language-tag", "en"],
      ["org", {
        "type":"work"
      }, "text", "Example"],
      ["title", {}, "text", "Research Scientist"],
      ["role", {}, "text", "Project Lead"],
      ["adr",
        { "type":"work" },
        "text",
        [
          "",
          "Suite 1234",
          "4321 Rue Somewhere",
          "Quebec",
          "QC",
          "G1V 2M2",
          "Canada"
        ]
      ],
      ["adr",
        {

          "type":"home",
          "label":"123 Maple Ave\nSuite 90001\nVancouver\nBC\n1239\n"
        },
        "text",
        [
          "", "", "", "", "", "", ""
        ]
      ],
      ["tel",
        { "type":["work", "voice"], "pref":"1" },
        "uri", "tel:+1-555-555-1234;ext=102"
      ],
      ["tel",
        {
          "type":["work", "cell", "voice", "video", "text"]
        },
        "uri",
        "tel:+1-555-555-1234"
      ],
      ["email",
        { "type":"work" },
        "text", "joe.user@example.com"
      ],
      ["geo", {
        "type":"work"
      }, "uri", "geo:46.772673,-71.282945"],
      ["key",
        { "type":"work" },
        "uri", "https://www.example.com/joe.user/joe.asc"
      ],
      ["tz", {},
        "utc-offset", "-05:00"],
      ["url", { "type":"home" },
        "uri", "https://example.org"]
    ]
  ]
}
</pre>
</div>
<figcaption><a href="#figure-40" class="selfRef">Figure 40</a></figcaption></figure>
</div>
<p id="section-appendix.c-4">
   The arrays in <a href="#ure-40" class="xref">Figure 40</a> with the first member of "adr" represent
   postal addresses.  In the first example, the postal address is given
   as an array of strings and constitutes a structured address.  For
   components of the structured address that are not applicable, an
   empty string is given.  Each member of that array aligns with the
   positions of a vCard as given in <span>[<a href="#RFC6350" class="xref">RFC6350</a>]</span>.  In this example, the
   following data corresponds to the following positional meanings:<a href="#section-appendix.c-4" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-appendix.c-5">
<li id="section-appendix.c-5.1">post office box -- not applicable; empty string<a href="#section-appendix.c-5.1" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.c-5.2">extended address (e.g., apartment or suite number) -- Suite 1234<a href="#section-appendix.c-5.2" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.c-5.3">street address -- 4321 Rue Somewhere<a href="#section-appendix.c-5.3" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.c-5.4">locality (e.g., city) -- Quebec<a href="#section-appendix.c-5.4" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.c-5.5">region (e.g., state or province) -- QC<a href="#section-appendix.c-5.5" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.c-5.6">postal code -- G1V 2M2<a href="#section-appendix.c-5.6" class="pilcrow">¶</a>
</li>
        <li id="section-appendix.c-5.7">country name (full name) -- Canada<a href="#section-appendix.c-5.7" class="pilcrow">¶</a>
</li>
      </ol>
<p id="section-appendix.c-6">
   The second example is an unstructured address.  It uses the "label"
   attribute, which is a string containing a newline (\n) character to
   separate address components in an unordered, unspecified manner.
   Note that in this example, the structured address array is still
   given but that each string is an empty string.<a href="#section-appendix.c-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-d">
<section id="section-appendix.d">
      <h2 id="name-secure-dns">
<a href="#section-appendix.d" class="section-number selfRef">Appendix D. </a><a href="#name-secure-dns" class="section-name selfRef">Secure DNS</a>
      </h2>
<p id="section-appendix.d-1">
   <a href="#sect-5.3" class="xref">Section 5.3</a> defines the "secureDNS" member to represent secure DNS
   information about domain names.<a href="#section-appendix.d-1" class="pilcrow">¶</a></p>
<p id="section-appendix.d-2">
   DNSSEC provides data integrity for DNS through the digital signing of
   resource records.  To enable DNSSEC, the zone is signed by one or
   more private keys and the signatures are stored as RRSIG records.  To
   complete the chain of trust in the DNS zone hierarchy, a digest of
   each DNSKEY record (which contains the public key) must be loaded
   into the parent zone, stored as DS records, and signed by the
   parent's private key (RRSIG DS record), as indicated in "<a href="#RFC4034" class="xref">Resource Records for the DNS Security Extensions</a>" <span>[<a href="#RFC4034" class="xref">RFC4034</a>]</span>.  Creating the DS
   records in the parent zone can be done by the registration authority
   "<a href="#RFC5910" class="xref">Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP)</a>" <span>[<a href="#RFC5910" class="xref">RFC5910</a>]</span>.<a href="#section-appendix.d-2" class="pilcrow">¶</a></p>
<p id="section-appendix.d-3">
   Only DS-related information is provided by RDAP, since other
   information is not generally stored in the registration database.
   Other DNSSEC-related information can be retrieved with other DNS
   tools such as dig.<a href="#section-appendix.d-3" class="pilcrow">¶</a></p>
<p id="section-appendix.d-4">
   The domain object class (<a href="#sect-5.3" class="xref">Section 5.3</a>) can represent this information
   using either the "dsData" or "keyData" object arrays.  Client
   implementers should be aware that some registries do not collect or
   do not publish all of the secure DNS meta-information.<a href="#section-appendix.d-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="sect-e">
<section id="section-appendix.e">
      <h2 id="name-motivations-for-using-json">
<a href="#section-appendix.e" class="section-number selfRef">Appendix E. </a><a href="#name-motivations-for-using-json" class="section-name selfRef">Motivations for Using JSON</a>
      </h2>
<p id="section-appendix.e-1">
   This section addresses a common question regarding the use of JSON
   over other data formats, most notably XML.<a href="#section-appendix.e-1" class="pilcrow">¶</a></p>
<p id="section-appendix.e-2">
   It is often pointed out that many DNRs and one RIR support the EPP
   <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span> standard, which is an XML serialized protocol.  The logic
   is that since EPP is a common protocol in the industry, it follows
   that XML would be a more natural choice.  While EPP does influence
   this specification quite a bit, EPP serves a different purpose, which
   is the provisioning of Internet resources between registries and
   accredited registrars and serving a much narrower audience than that
   envisioned for RDAP.<a href="#section-appendix.e-2" class="pilcrow">¶</a></p>
<p id="section-appendix.e-3">
   By contrast, RDAP has a broader audience and is designed for public
   consumption of data.  Experience from RIRs with first generation
   RESTful web services for WHOIS indicate that a large percentage of
   clients operate within browsers and other platforms where full-blown
   XML stacks are not readily available and where JSON is a better fit.<a href="#section-appendix.e-3" class="pilcrow">¶</a></p>
<p id="section-appendix.e-4">
   Additionally, while EPP is used in much of the DNR community it is
   not a universal constant in that industry.  And finally, EPP's use of
   XML predates the specification of JSON.  If EPP had been defined
   today, it may very well have used JSON instead of XML.<a href="#section-appendix.e-4" class="pilcrow">¶</a></p>
<p id="section-appendix.e-5">
   Beyond the specific DNR and RIR communities, the trend in the broader
   Internet industry is also switching to JSON over XML, especially in
   the area of RESTful web services (see <span>[<a href="#JSON_ascendancy" class="xref">JSON_ascendancy</a>]</span>).  Studies
   have also found that JSON is generally less bulky and consequently
   faster to parse (see <span>[<a href="#JSON_performance_study" class="xref">JSON_performance_study</a>]</span>).<a href="#section-appendix.e-5" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-appendix.f">
      <h2 id="name-changes-from-rfc-7483">
<a href="#section-appendix.f" class="section-number selfRef">Appendix F. </a><a href="#name-changes-from-rfc-7483" class="section-name selfRef">Changes from RFC 7483</a>
      </h2>
<ul class="normal">
<li class="normal" id="section-appendix.f-1.1">Addressed known errata.<a href="#section-appendix.f-1.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="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 removed an "X" from "XXXXX". 
Changed IPv6 address example using "C00" to "c00". Added "a string representing" to the definitions of startAddress and endAddress. 
Removed "entity" from "Autonomous System Number Entity Object Class". 
Added "an unsigned 32-bit integer" to the definition of startAutnum and endAutnum. 
Added "a string representing" to the definition of name in the IP network and ASN object classes. 
Clarified rdapConformance identifier registration expectations in <a href="#sect-4.1" class="xref">Section 4.1</a>. 
Changed "lunarNic_level_0" to "lunarNIC_level_0".<a href="#section-appendix.f-1.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.3">Clarified that the "value", "rel" and "href" JSON values <span class="bcp14">MUST</span> be specified in the "links" array.<a href="#section-appendix.f-1.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.4">Clarified that the "description" array is required in the Notices and Remarks data structures and other values are <span class="bcp14">OPTIONAL</span>.<a href="#section-appendix.f-1.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.5">Noted that all members of the "events" and "Public IDs" arrays are <span class="bcp14">REQUIRED</span>.<a href="#section-appendix.f-1.5" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.6">Fix "self" link values in examples. Changed "http" to "https" link values in examples. 
Noted that <a href="#ure-18" class="xref">Figure 18</a> is an example of a nameserver object with all "appropriate" values given. 
In <a href="#sect-c" class="xref">Appendix C</a>, quoted the word "label" in "label attribute". 
Added reference to "status" definition in the descriptions for IP networks and autnums. 
Fixed a 404 for the informative reference to "The Stealthy Ascendancy of JSON". 
Added "boolean" to the definition of zoneSigned.<a href="#section-appendix.f-1.6" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.7">Clarified <span class="bcp14">REQUIRED</span> and <span class="bcp14">OPTIONAL</span> members of the "events" array.<a href="#section-appendix.f-1.7" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.8">Changed "<span class="bcp14">SHOULD</span> not" to "<span class="bcp14">SHOULD NOT</span>" in <a href="#sect-5" class="xref">Section 5</a>.<a href="#section-appendix.f-1.8" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.9">Updated normative references (RFC 5226 to RFC 8126, RFC 5988 to RFC 8288, RFC 7159 to RFC 8259). 
Changed examples using "ns1.xn--fo-5ja.example" to split URLs to avoid long lines.<a href="#section-appendix.f-1.9" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.10">Added acknowledgments.<a href="#section-appendix.f-1.10" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.11">Changed "The "lang" attribute may appear anywhere in an object class or data structure except for in jCard objects" to "The "lang" attribute as defined in this section <span class="bcp14">MAY</span> appear anywhere in an object class or data structure, except for in jCard objects. jCard supports similar functionality by way of the LANGUAGE property parameter (see Section <a href="https://www.rfc-editor.org/rfc/rfc6350#section-5.1" class="relref">5.1</a> of RFC 6350 <span>[<a href="#RFC6350" class="xref">RFC6350</a>]</span>".<a href="#section-appendix.f-1.11" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.12">Changed "simple data types conveyed in JSON strings" to "simple data types conveyed in JSON primitive types (strings, numbers, booleans, and null)". Changed "In other words, servers are free to not include JSON members containing registration data based on their own policies" to "In other words, servers are free to omit unrequired/optional JSON members containing registration data based on their own policies".<a href="#section-appendix.f-1.12" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.13">Changed "This data structure appears only in the topmost JSON object of a response" to "This data structure <span class="bcp14">MUST</span> appear in the topmost JSON object of a response".<a href="#section-appendix.f-1.13" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.14">Changed "Some non-answer responses may return entity bodies with information that could be more descriptive" to "Some non-answer responses <span class="bcp14">MAY</span> return entity bodies with information that could be more descriptive".<a href="#section-appendix.f-1.14" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.15">Changed "The basic structure of that response is an object class containing an error code number (corresponding to the HTTP response code) followed by a string named "title" and an array of strings named "description"" to "The basic structure of that response is an object class containing a <span class="bcp14">REQUIRED</span> error code number (corresponding to the HTTP response code) followed by an <span class="bcp14">OPTIONAL</span> string named "title" and an <span class="bcp14">OPTIONAL</span> array of strings named "description"".<a href="#section-appendix.f-1.15" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.16">Changed the "Autonomous System Number Object Class" section title to "The Autonomous System Number Object Class" for consistency with other section titles. Removed trailing periods in the "Terminology and Definitions" section for consistency. Changed instances of "lunarNic" to "lunarNIC" for consistency. Removed an extraneous trailing period after the eventDate description. Changed a "." to ";" in the description of the "network" member of the domain object class. Changed "The high-level structure of the autnum object class consists of information about the network registration" to "The high-level structure of the autnum object class consists of information about the Autonomous System number registration". Changed "registry unique" to "registry-unique".<a href="#section-appendix.f-1.16" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.17">Changed "registrant" to "registrar" in the description of the "transfer" event action to address erratum 6158. Added IANA instructions to correct the description of the value in the registry.<a href="#section-appendix.f-1.17" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.18">Added text to <a href="#sect-4.2" class="xref">Section 4.2</a> to note that "self" and "related" "href" URIs <span class="bcp14">MUST NOT</span> be the same.<a href="#section-appendix.f-1.18" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.19">Added text to <a href="#sect-4.2" class="xref">Section 4.2</a> to describe return of IDNs in LDH name format.<a href="#section-appendix.f-1.19" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.20">Added text to note that the "fn" member of a contact object <span class="bcp14">MAY</span> be empty in <a href="#sect-3" class="xref">Section 3</a>.<a href="#section-appendix.f-1.20" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.21">Added text to clarify rdapConformance requirements in <a href="#sect-4.1" class="xref">Section 4.1</a>.<a href="#section-appendix.f-1.21" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-appendix.f-1.22">Added "obsoletes 7483" to the headers, Abstract, and Introduction. Updated BCP 14 boilerplate. Updated IANA Considerations to note that this RFC (a product of the REGEXT Working Group) replaces RFC 7483. Changed "simple string" to "simple character string" in Sections <a href="#sect-3" class="xref">3</a> and <a href="#sect-4.7" class="xref">4.7</a>. Clarified requirement for the "fn" member in <a href="#sect-3" class="xref">Section 3</a>. Modified the requirement for rdapConformance placement in <a href="#sect-4.1" class="xref">Section 4.1</a>. Changed "jCard" to "vCard" LANGUAGE property reference in <a href="#sect-4.4" class="xref">Section 4.4</a>. Changed "no use" to "little or no use" in <a href="#sect-5.1" class="xref">Section 5.1</a>. Added example line wrap note in <a href="#sect-5.2" class="xref">Section 5.2</a>. Modified the definition of "idnTable" in <a href="#sect-5.3" class="xref">Section 5.3</a>. Modified the dsData and keyData examples in <a href="#sect-5.3" class="xref">Section 5.3</a>. Changed "2001:c00::/23" to "2001:db8::/32" in <a href="#sect-5.4" class="xref">Section 5.4</a>. Expanded the definition of "type" in Sections <a href="#sect-5.4" class="xref">5.4</a> and  <a href="#sect-5.5" class="xref">5.5</a>. Modified example autnums in <a href="#sect-5.5" class="xref">Section 5.5</a>. Added text to the Security Considerations section to note that DNSSEC information returned in a response cannot be trusted directly.<a href="#section-appendix.f-1.22" class="pilcrow">¶</a>
</li>
      </ul>
</section>
<div id="acknowledgments">
<section id="section-appendix.g">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="section-appendix.g-1">
   This document is derived from original work on RIR responses in JSON
   by <span class="contact-name">Byron J. Ellacott</span>, <span class="contact-name">Arturo L. Servin</span>, 
   <span class="contact-name">Kaveh Ranjbar</span>, and <span class="contact-name">Andrew L.  Newton</span>.  
   Additionally, this document incorporates work on DNR
   responses in JSON by <span class="contact-name">Ning Kong</span>, <span class="contact-name">Linlin Zhou</span>, <span class="contact-name">Jiagui Xie</span>, and 
   <span class="contact-name">Sean Shen</span>.<a href="#section-appendix.g-1" class="pilcrow">¶</a></p>
<p id="section-appendix.g-2">
   The components of the DNR object classes are derived from a
   categorization of WHOIS response formats created by <span class="contact-name">Ning Kong</span>, <span class="contact-name">Linlin Zhou</span>, 
   <span class="contact-name">Guangqing Deng</span>, <span class="contact-name">Steve Sheng</span>, <span class="contact-name">Francisco Arias</span>, 
   <span class="contact-name">Ray Bellis</span>, and
   <span class="contact-name">Frederico Neves</span>.<a href="#section-appendix.g-2" class="pilcrow">¶</a></p>
<p id="section-appendix.g-3">
   <span class="contact-name">Tom Harrison</span>, <span class="contact-name">Murray Kucherawy</span>, <span class="contact-name">Ed Lewis</span>, <span class="contact-name">Audric Schiltknecht</span>, 
   <span class="contact-name">Naoki Kambe</span>, <span class="contact-name">Maarten Bosteels</span>, <span class="contact-name">Mario Loffredo</span>, and <span class="contact-name">Jasdip Singh</span> contributed significant review comments
   and provided clarifying text.  <span class="contact-name">James Mitchell</span> provided text regarding
   the processing of unknown JSON attributes and identified issues
   leading to the remodeling of events.  <span class="contact-name">Ernie Dainow</span> and 
   <span class="contact-name">Francisco Obispo</span> provided concrete suggestions that led to a better variant
   model for domain names.<a href="#section-appendix.g-3" class="pilcrow">¶</a></p>
<p id="section-appendix.g-4">
   <span class="contact-name">Ernie Dainow</span> provided the background information on the secure DNS
   attributes and objects for domains, informative text on DNSSEC, and
   many other attributes that appear throughout the object classes of
   this document.<a href="#section-appendix.g-4" class="pilcrow">¶</a></p>
<p id="section-appendix.g-5">
   The switch to and incorporation of jCard was performed by <span class="contact-name">Simon Perreault</span>.<a href="#section-appendix.g-5" class="pilcrow">¶</a></p>
<p id="section-appendix.g-6">
   <span class="contact-name">Olaf Kolkman</span> and <span class="contact-name">Murray Kucherawy</span> chaired the IETF's WEIRDS Working
   Group from which this document was originally created. <span class="contact-name">James Galvin</span>
   and <span class="contact-name">Antoin Verschuren</span> chaired the REGEXT Working Group that worked
   on this document.<a href="#section-appendix.g-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="section-appendix.h">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Scott Hollenbeck</span></div>
<div dir="auto" class="left"><span class="org">Verisign Labs</span></div>
<div dir="auto" class="left"><span class="street-address">12061 Bluemont Way</span></div>
<div dir="auto" class="left">
<span class="locality">Reston</span>, <span class="region">VA</span> <span class="postal-code">20190</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:shollenbeck@verisign.com" class="email">shollenbeck@verisign.com</a>
</div>
<div class="url">
<span>URI:</span>
<a href="https://www.verisignlabs.com/" class="url">https://www.verisignlabs.com/</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Andy Newton</span></div>
<div dir="auto" class="left"><span class="org">Amazon Web Services, Inc.</span></div>
<div dir="auto" class="left"><span class="street-address">13200 Woodland Park Road</span></div>
<div dir="auto" class="left">
<span class="locality">Herndon</span>, <span class="region">VA</span> <span class="postal-code">20171</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:andy@hxr.us" class="email">andy@hxr.us</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
  toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
  toc.classList.remove("active");
});
</script>
</body>
</html>