File: rfc8909.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 (2088 lines) | stat: -rw-r--r-- 85,304 bytes
parent folder | download | duplicates (2)
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 8909: Registry Data Escrow Specification</title>
<meta content="Gustavo Lozano" name="author">
<meta content="
       This document specifies the format and contents of data escrow
       deposits targeted primarily for domain name registries.   The
       specification is designed to be independent of the underlying
       objects that are being escrowed, and therefore it could also be used for
       purposes other than domain name registries. 
    " name="description">
<meta content="xml2rfc 3.4.0" name="generator">
<meta content="data escrow" name="keyword">
<meta content="registry" name="keyword">
<meta content="8909" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.4.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="rfc8909.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";
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8909" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-data-escrow-10" 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 8909</td>
<td class="center">Registry Data Escrow</td>
<td class="right">November 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Lozano</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/rfc8909" class="eref">8909</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="2020-11" class="published">November 2020</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">G. Lozano</div>
<div class="org">ICANN</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8909</h1>
<h1 id="title">Registry Data Escrow Specification</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document specifies the format and contents of data escrow
       deposits targeted primarily for domain name registries.   The
       specification is designed to be independent of the underlying
       objects that are being escrowed, and therefore it could also be used for
       purposes other than domain name registries.<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/rfc8909">https://www.rfc-editor.org/info/rfc8909</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) 2020 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="ulEmpty toc compact">
<li class="ulEmpty toc compact" 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><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-problem-scope" class="xref">Problem Scope</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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-conventions-used-in-this-do" class="xref">Conventions Used in This Document</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" 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-date-and-time" class="xref">Date and Time</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" 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-protocol-description" class="xref">Protocol Description</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" 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-root-element-deposit" class="xref">Root Element &lt;deposit&gt;</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" 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-rebuilding-the-registry-fro" class="xref">Rebuilding the Registry from Data Escrow Deposits</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" 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-formal-syntax" class="xref">Formal Syntax</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" id="section-toc.1-1.6.2.1">
                <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-rde-schema" class="xref">RDE Schema</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" 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-internationalization-consid" class="xref">Internationalization Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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-privacy-considerations" class="xref">Privacy Considerations</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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-example-of-a-full-deposit" class="xref">Example of a Full Deposit</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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-example-of-a-differential-d" class="xref">Example of a Differential Deposit</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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-example-of-an-incremental-d" class="xref">Example of an Incremental Deposit</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" 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><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p>
<ul class="ulEmpty toc compact">
<li class="ulEmpty toc compact" 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><a href="#section-toc.1-1.14.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="ulEmpty toc compact" 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><a href="#section-toc.1-1.14.2.2.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="ulEmpty toc compact" id="section-toc.1-1.15">
            <p id="section-toc.1-1.15.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a><a href="#section-toc.1-1.15.1" class="pilcrow">¶</a></p>
</li>
          <li class="ulEmpty toc compact" id="section-toc.1-1.16">
            <p id="section-toc.1-1.16.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-address" class="xref">Author's Address</a><a href="#section-toc.1-1.16.1" class="pilcrow">¶</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<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">
                Registry Data Escrow (RDE) is the process by which a registry periodically submits data 
                deposits to a third party called an escrow agent. These deposits comprise the 
                minimum data needed by a third party to resume operations if the registry 
                cannot function and is unable or unwilling to facilitate an  
                orderly transfer of service.  
                For example, for a domain name registry or registrar, the data to be deposited
                would include all of the objects related to registered domain names, e.g.,
                names, contacts, name servers.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">          
The goal of data escrow is higher resiliency of registration services, for the benefit of Internet users.  The beneficiaries of a registry are not just those registering information there but also the users of services relying on the registry data.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">        
                In the context of domain name registries, registration data escrow is 
                a requirement for generic Top-Level Domains (gTLDs) (e.g.,
                Specification 2 of the ICANN Base Registry Agreement; see
                <span>[<a href="#ICANN-GTLD-RA-20170731" class="xref">ICANN-GTLD-RA-20170731</a>]</span>), and
                some country code TLD (ccTLD)
                managers are also currently escrowing data. 
                There is also a similar requirement for ICANN-accredited 
                domain registrars.<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4">
                This document specifies a format for data escrow deposits independent of the objects being escrowed. An independent specification is required for each type of registry/set of objects that is expected to be escrowed.<a href="#section-1-4" class="pilcrow">¶</a></p>
<p id="section-1-5">
                The format for data escrow deposits is specified using version
                1.0 of the Extensible Markup Language (XML) as described in <span>[<a href="#W3C.REC-xml-20081126" class="xref">W3C.REC-xml-20081126</a>]</span>, and XML Schema notation as described in <span>[<a href="#W3C.REC-xmlschema-1-20041028" class="xref">W3C.REC-xmlschema-1-20041028</a>]</span> and <span>[<a href="#W3C.REC-xmlschema-2-20041028" class="xref">W3C.REC-xmlschema-2-20041028</a>]</span>.<a href="#section-1-5" class="pilcrow">¶</a></p>
<p id="section-1-6">
            Readers are advised to read <a href="#terms" class="xref">Section 2</a> ("Terminology") carefully to understand the precise meanings of Differential and Incremental Deposits, as the definitions used in this document are different from the definitions typically used in the domain of data backups.<a href="#section-1-6" class="pilcrow">¶</a></p>
</section>
<div id="terms">
<section id="section-2">
      <h2 id="name-terminology">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
      </h2>
<p id="section-2-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-2-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel" id="section-2-2">
        <dt id="section-2-2.1">Deposit:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.2">There are three kinds of deposits: Full, Differential, and
         Incremental. For all three kinds of deposits, the 
                universe of registry objects to be considered for data escrow
                is comprised of any objects required to offer the registry services.<a href="#section-2-2.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.3">Differential Deposit:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.4">A Differential Deposit contains data that reflects all transactions involving the database 
                that were not reflected in the last previous Full, Incremental, or Differential Deposit, as the case may 
                be. Differential Deposit files will contain information from all database objects that were added, 
                modified, or deleted since the previous deposit was completed as of its defined Timeline Watermark.<a href="#section-2-2.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.5">Domain Name:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.6">See the definition of "domain name" in <span>[<a href="#RFC8499" class="xref">RFC8499</a>]</span>.<a href="#section-2-2.6" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.7">Escrow Agent:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.8">An escrow agent is the organization designated by the registry or the third-party beneficiary to receive and 
                guard data escrow deposits from the registry.<a href="#section-2-2.8" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.9">Full Deposit:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.10">A Full Deposit contains the registry data that reflects the current and complete registry 
                database and will consist of data that reflects the state of the registry as of a defined
                Timeline Watermark for the deposit.<a href="#section-2-2.10" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.11">Incremental Deposit:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.12">An Incremental Deposit contains data that reflects all transactions involving the database that were not 
                reflected in the last previous Full Deposit. Incremental Deposit files will contain information from 
                all database objects that were added, modified, or deleted since the previous Full Deposit was completed 
                as of its defined Timeline Watermark. If the Timeline Watermark of an
 Incremental Deposit were to cover the Timeline Watermark of another
 Incremental or Differential Deposit since the last Full Deposit
 (i.e., one or more Incremental or Differential Deposits exist for
 the period between the Timeline Watermark of a Full Deposit and an
 Incremental or Differential Deposit), the more recent deposit <span class="bcp14">MUST</span>
 contain all of the transactions of the earlier deposit.<a href="#section-2-2.12" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.13">Registrar:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.14">See the definition of "registrar" in <span>[<a href="#RFC8499" class="xref">RFC8499</a>]</span>.<a href="#section-2-2.14" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.15">Registry:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.16">See the definition of "registry" in <span>[<a href="#RFC8499" class="xref">RFC8499</a>]</span>.<a href="#section-2-2.16" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.17">Third-Party Beneficiary:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.18">A third-party beneficiary is the organization that, under extraordinary circumstances, would receive the 
                escrow deposits the registry transferred to the escrow agent. This organization could be a backup 
                registry, registry regulator, contracting party of the registry, etc.<a href="#section-2-2.18" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.19">Timeline Watermark:</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.20">The Timeline Watermark is the point in time on which to base the collecting of database objects for a deposit. 
                Deposits are expected to be consistent with that point in time.<a href="#section-2-2.20" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-2-2.21">Top-Level Domain (TLD):</dt>
        <dd style="margin-left: 1.5em" id="section-2-2.22">See the definition of "Top-Level Domain" in <span>[<a href="#RFC8499" class="xref">RFC8499</a>]</span>.<a href="#section-2-2.22" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
</section>
</div>
<section id="section-3">
      <h2 id="name-problem-scope">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-problem-scope" class="section-name selfRef">Problem Scope</a>
      </h2>
<p id="section-3-1">
                In the past few years, the issue of registry continuity has
                been carefully considered in the gTLD and 
                ccTLD spaces. Various organizations have carried out risk analyses and developed business continuity plans to 
                deal with those risks, should they materialize.<a href="#section-3-1" class="pilcrow">¶</a></p>
<p id="section-3-2">
                One of the solutions considered and used, especially in the gTLD space, is Registry Data Escrow as a 
                way to ensure the continuity of registry services in the extreme case of registry failure.<a href="#section-3-2" class="pilcrow">¶</a></p>
<p id="section-3-3">
                So far, almost every registry that uses Registry Data Escrow has its own specification. It is  
                anticipated that more registries will be implementing escrow, especially with an increasing number of domain
                registries coming into service, adding complexity to this issue.<a href="#section-3-3" class="pilcrow">¶</a></p>
<p id="section-3-4">
                It would seem beneficial to have a standardized specification for Registry Data Escrow that can be used 
                by any registry to submit its deposits.<a href="#section-3-4" class="pilcrow">¶</a></p>
<p id="section-3-5">
                While the domain name industry has been the main target for this specification, it has been designed to be as general as possible.<a href="#section-3-5" class="pilcrow">¶</a></p>
<p id="section-3-6">
                Specifications covering the objects used by registration organizations shall identify the format and contents of the deposits a 
                registry has to make, such that a different registry would be able to rebuild the registration 
                services of the former, without its help, in a timely manner and with minimum disruption to its users.<a href="#section-3-6" class="pilcrow">¶</a></p>
<p id="section-3-7">
                Since the details of the registration services provided vary from registry to registry, specifications covering the objects
                used by registration organizations shall provide mechanisms that allow extensibility to accommodate variations and
                extensions of the registration services.<a href="#section-3-7" class="pilcrow">¶</a></p>
<p id="section-3-8">
                Given the requirement for confidentiality and the importance of accuracy of the information that is handled in order to offer 
                registration services, parties using this specification shall define confidentiality and integrity mechanisms for handling 
                the registration data.<a href="#section-3-8" class="pilcrow">¶</a></p>
<p id="section-3-9">
                Specifications covering the objects used by registration organizations shall not include in the specification
                transient objects that can be recreated by the new registry, particularly those of delicate confidentiality,
                e.g., DNSSEC KSK/ZSK (Key Signing Key / Zone Signing Key) private keys.<a href="#section-3-9" class="pilcrow">¶</a></p>
<p id="section-3-10">
                Details that are a matter of policy should be identified as such for the benefit of the implementers.<a href="#section-3-10" class="pilcrow">¶</a></p>
<p id="section-3-11">
                Non-technical issues concerning data escrow, such as whether
                to escrow data and for what purposes the data may
                be used, are outside the scope of this document.<a href="#section-3-11" class="pilcrow">¶</a></p>
<p id="section-3-12">
            Parties using this specification shall use a signaling mechanism to control the transmission, reception, and validation of data escrow deposits. The definition of such a signaling mechanism is outside the scope of this document.<a href="#section-3-12" class="pilcrow">¶</a></p>
</section>
<section id="section-4">
      <h2 id="name-conventions-used-in-this-do">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-conventions-used-in-this-do" class="section-name selfRef">Conventions Used in This Document</a>
      </h2>
<p id="section-4-1">
            The XML namespace prefix "rde" is used for the namespace
            "urn:ietf:params:xml:ns:rde-1.0", but implementations <span class="bcp14">MUST NOT</span> depend on it;
            instead, they should employ a proper namespace-aware XML parser
            and serializer to interpret and output the XML documents.<a href="#section-4-1" class="pilcrow">¶</a></p>
<p id="section-4-2">
            The XML namespace prefixes "rdeObj1" and "rdeObj2", with the corresponding namespaces "urn:example:params:xml:ns:rdeObj1-1.0" and
            "urn:example:params:xml:ns:rdeObj2-1.0", are used as example data escrow objects.<a href="#section-4-2" class="pilcrow">¶</a></p>
<section id="section-4.1">
        <h3 id="name-date-and-time">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-date-and-time" class="section-name selfRef">Date and Time</a>
        </h3>
<p id="section-4.1-1">
                    Numerous fields indicate "dates", such as the creation and expiry
                    dates for objects.  These fields <span class="bcp14">SHALL</span> contain timestamps indicating
                    the date and time in UTC, specified in Internet Date/Time Format
                    (see <span>[<a href="#RFC3339" class="xref">RFC3339</a>], <a href="https://www.rfc-editor.org/rfc/rfc3339#section-5.6" class="relref">Section 5.6</a></span>) with the time-offset parameter specified as "Z".<a href="#section-4.1-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-5">
      <h2 id="name-protocol-description">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-protocol-description" class="section-name selfRef">Protocol Description</a>
      </h2>
<p id="section-5-1">The format for data escrow deposits as produced by a registry is
 defined below.  The deposits are represented in XML (<a href="#formalSyntax" class="xref">Section 6</a>).
 Only the format of the objects deposited is defined.  This document
 does not prescribe the method used to transfer such deposits between
 the registry and the escrow agent or vice versa.<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">The protocol intends to be object agnostic, allowing the "overload"
 of abstract elements using the "substitutionGroup" attribute
 <span>[<a href="#W3C.REC-xmlschema-1-20041028" class="xref">W3C.REC-xmlschema-1-20041028</a>]</span> of the XML Schema element to define
 the actual elements of an object to be escrowed.<a href="#section-5-2" class="pilcrow">¶</a></p>
<p id="section-5-3">
               The specification for each object to be escrowed <span class="bcp14">MUST</span> declare the identifier to be
               used to reference the object to be deleted or added/modified.<a href="#section-5-3" class="pilcrow">¶</a></p>
<div id="root_element">
<section id="section-5.1">
        <h3 id="name-root-element-deposit">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-root-element-deposit" class="section-name selfRef">Root Element &lt;deposit&gt;</a>
        </h3>
<p id="section-5.1-1">
                    The container or root element for a Registry Data Escrow deposit is &lt;deposit&gt;.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<p id="section-5.1-2">
                    The &lt;deposit&gt; element contains the following attributes:<a href="#section-5.1-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.1-3.1">
            <p id="section-5.1-3.1.1">
                     A <span class="bcp14">REQUIRED</span> "type" attribute that is used to identify the kind of deposit:<a href="#section-5.1-3.1.1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.1-3.1.2.1">
                                    FULL: Full.<a href="#section-5.1-3.1.2.1" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.1-3.1.2.2">
                                    INCR: Incremental.<a href="#section-5.1-3.1.2.2" class="pilcrow">¶</a>
</li>
              <li class="normal" id="section-5.1-3.1.2.3">
                                    DIFF: Differential.<a href="#section-5.1-3.1.2.3" class="pilcrow">¶</a>
</li>
            </ul>
</li>
          <li class="normal" id="section-5.1-3.2">
                            A <span class="bcp14">REQUIRED</span> "id" attribute that is used to uniquely identify the escrow deposit.
                            Each registry is responsible for maintaining its own escrow deposits' identifier
                            space to ensure uniqueness.<a href="#section-5.1-3.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-3.3">
                            A "prevId" attribute that can be used to identify the previous 
                            Incremental, Differential, or Full Deposit.  This attribute is <span class="bcp14">REQUIRED</span>
                            in Differential Deposits ("DIFF" type), is <span class="bcp14">OPTIONAL</span> in Incremental
                            Deposits ("INCR" type), and is not used in Full Deposits ("FULL"
                            type).<a href="#section-5.1-3.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-5.1-3.4">
                            An <span class="bcp14">OPTIONAL</span> "resend" attribute that is incremented 
                            each time the escrow deposit failed the verification procedure at the receiving party 
                            and a new escrow deposit needs to be generated by the registry for that specific date. 
                            The first time a deposit is generated, the
                            attribute either (1) is omitted or (2) <span class="bcp14">MUST</span> be "0".  
                            If a deposit needs to be generated again, the attribute <span class="bcp14">MUST</span> be set to "1", and so on.<a href="#section-5.1-3.4" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-5.1-4">
                        The &lt;deposit&gt; element contains the following child elements:<a href="#section-5.1-4" class="pilcrow">¶</a></p>
<div id="watermark">
<section id="section-5.1.1">
          <h4 id="name-child-watermark-element">
<a href="#section-5.1.1" class="section-number selfRef">5.1.1. </a><a href="#name-child-watermark-element" class="section-name selfRef">Child &lt;watermark&gt; Element</a>
          </h4>
<p id="section-5.1.1-1">
                    A <span class="bcp14">REQUIRED</span> &lt;watermark&gt; element
                    contains the date-time <span>[<a href="#RFC3339" class="xref">RFC3339</a>]</span> corresponding to
                    the Timeline Watermark of the deposit.<a href="#section-5.1.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rdeMenu">
<section id="section-5.1.2">
          <h4 id="name-child-rdemenu-element">
<a href="#section-5.1.2" class="section-number selfRef">5.1.2. </a><a href="#name-child-rdemenu-element" class="section-name selfRef">Child &lt;rdeMenu&gt; Element</a>
          </h4>
<p id="section-5.1.2-1">
                    This element contains auxiliary information regarding the data escrow deposit.<a href="#section-5.1.2-1" class="pilcrow">¶</a></p>
<p id="section-5.1.2-2">
                    A <span class="bcp14">REQUIRED</span> &lt;rdeMenu&gt; element contains the following child elements:<a href="#section-5.1.2-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5.1.2-3.1">
                            A <span class="bcp14">REQUIRED</span> &lt;version&gt; element that identifies the RDE protocol version. This value <span class="bcp14">MUST</span> be 1.0.<a href="#section-5.1.2-3.1" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-5.1.2-3.2">
                            One or more &lt;objURI&gt; elements that contain namespace URIs
                            representing the &lt;contents&gt; and &lt;deletes&gt; element objects.<a href="#section-5.1.2-3.2" class="pilcrow">¶</a>
</li>
          </ul>
</section>
</div>
<div id="deletes">
<section id="section-5.1.3">
          <h4 id="name-child-deletes-element">
<a href="#section-5.1.3" class="section-number selfRef">5.1.3. </a><a href="#name-child-deletes-element" class="section-name selfRef">Child &lt;deletes&gt; Element</a>
          </h4>
<p id="section-5.1.3-1">For Differential Deposits, this element contains the list of objects that have
    been deleted since the previous deposit of any type.  For Incremental
    Deposits, this element contains the list of objects that have been deleted
    since the previous Full Deposit.<a href="#section-5.1.3-1" class="pilcrow">¶</a></p>
<p id="section-5.1.3-2">
                    This section of the deposit <span class="bcp14">MUST NOT</span> be present in Full Deposits.<a href="#section-5.1.3-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="contents">
<section id="section-5.1.4">
          <h4 id="name-child-contents-element">
<a href="#section-5.1.4" class="section-number selfRef">5.1.4. </a><a href="#name-child-contents-element" class="section-name selfRef">Child &lt;contents&gt; Element</a>
          </h4>
<p id="section-5.1.4-1">For Full Deposits, this element contains all objects.  For Differential
    Deposits, this element contains the list of objects that have been added or
    modified since the previous deposit of any type.  For Incremental Deposits,
    this element contains the list of objects that have been added or modified
    since the previous Full Deposit.<a href="#section-5.1.4-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="rebuilding">
<section id="section-5.2">
        <h3 id="name-rebuilding-the-registry-fro">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-rebuilding-the-registry-fro" class="section-name selfRef">Rebuilding the Registry from Data Escrow Deposits</a>
        </h3>
<p id="section-5.2-1">
                    When applying Incremental or Differential Deposits (when rebuilding
                    the registry from data escrow deposits), the relative order of the
                    &lt;deletes&gt; and &lt;contents&gt; elements is important because dependencies
                    may exist between the objects.  All of the &lt;deletes&gt; elements <span class="bcp14">MUST</span> be applied
                    first, in the order in which they appear.  All of the &lt;contents&gt; elements
                    <span class="bcp14">MUST</span> be applied next, in the order in which
 they appear.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<p id="section-5.2-2">
                    If an object is present in the &lt;contents&gt; or
                    &lt;deletes&gt; section of several deposits (e.g., Full
                    and Differential), the registry data from the latest
                    deposit (as defined by the Timeline Watermark)
                    <span class="bcp14">SHOULD</span> be used when rebuilding the
                    registry. An object <span class="bcp14">SHOULD NOT</span> exist
                    multiple times in either the &lt;contents&gt; or
                    &lt;deletes&gt; elements in a single deposit.<a href="#section-5.2-2" class="pilcrow">¶</a></p>
<p id="section-5.2-3">When rebuilding a 
                    registry, the
                    &lt;deletes&gt; section <span class="bcp14">MUST</span> be ignored if present in a Full Deposit.<a href="#section-5.2-3" class="pilcrow">¶</a></p>
</section>
</div>
</section>
<div id="formalSyntax">
<section id="section-6">
      <h2 id="name-formal-syntax">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-formal-syntax" class="section-name selfRef">Formal Syntax</a>
      </h2>
<p id="section-6-1">RDE is specified in XML Schema notation.  The formal syntax presented
                        here is a complete schema representation of RDE suitable for
                        automated validation of RDE XML instances.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">The &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; tags are not part of the schema; they are used to note
                        the beginning and ending of the schema for URI registration purposes.<a href="#section-6-2" class="pilcrow">¶</a></p>
<section id="section-6.1">
        <h3 id="name-rde-schema">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-rde-schema" class="section-name selfRef">RDE Schema</a>
        </h3>
<div id="section-6.1-1">
<pre class="sourcecode lang-xml">&lt;CODE BEGINS&gt;
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;schema targetNamespace="urn:ietf:params:xml:ns:rde-1.0"
  xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
  xmlns="http://www.w3.org/2001/XMLSchema"
  elementFormDefault="qualified"&gt;

  &lt;annotation&gt;
    &lt;documentation&gt;
      Registry Data Escrow schema
    &lt;/documentation&gt;
  &lt;/annotation&gt;

  &lt;!-- Root element --&gt;
  &lt;element name="deposit" type="rde:escrowDepositType"/&gt;

  &lt;!-- RDE types --&gt;
  &lt;complexType name="escrowDepositType"&gt;
    &lt;sequence&gt;
      &lt;element name="watermark" type="dateTime"/&gt;
      &lt;element name="rdeMenu" type="rde:rdeMenuType"/&gt;
      &lt;element name="deletes" type="rde:deletesType" minOccurs="0"/&gt;
      &lt;element name="contents" type="rde:contentsType"
        minOccurs="0"/&gt;
    &lt;/sequence&gt;
    &lt;attribute name="type" type="rde:depositTypeType"
      use="required"/&gt;
    &lt;attribute name="id" type="rde:depositIdType" use="required"/&gt;
    &lt;attribute name="prevId" type="rde:depositIdType"/&gt;
    &lt;attribute name="resend" type="unsignedShort" default="0"/&gt;
  &lt;/complexType&gt;

  &lt;!-- Menu type --&gt;
  &lt;complexType name="rdeMenuType"&gt;
    &lt;sequence&gt;
      &lt;element name="version" type="rde:versionType"/&gt;
      &lt;element name="objURI" type="anyURI" maxOccurs="unbounded"/&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;!-- Deletes type --&gt;
  &lt;complexType name="deletesType"&gt;
    &lt;sequence minOccurs="0" maxOccurs="unbounded"&gt;
      &lt;element ref="rde:delete"/&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;element name="delete" type="rde:deleteType" abstract="true"/&gt;
  &lt;complexType name="deleteType"&gt;
    &lt;complexContent&gt;
      &lt;restriction base="anyType"/&gt;
    &lt;/complexContent&gt;
  &lt;/complexType&gt;

  &lt;!-- Contents type --&gt;
  &lt;complexType name="contentsType"&gt;
    &lt;sequence minOccurs="0" maxOccurs="unbounded"&gt;
      &lt;element ref="rde:content"/&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;element name="content" type="rde:contentType" abstract="true"/&gt;
  &lt;complexType name="contentType"&gt;
    &lt;complexContent&gt;
      &lt;restriction base="anyType"/&gt;
    &lt;/complexContent&gt;
  &lt;/complexType&gt;

  &lt;!-- Type of deposit --&gt;
  &lt;simpleType name="depositTypeType"&gt;
    &lt;restriction base="token"&gt;
      &lt;enumeration value="FULL"/&gt;
      &lt;enumeration value="INCR"/&gt;
      &lt;enumeration value="DIFF"/&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;!-- Deposit identifier type --&gt;
  &lt;simpleType name="depositIdType"&gt;
    &lt;restriction base="token"&gt;
      &lt;pattern value="\w{1,13}"/&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;!-- A RDE version number is a dotted pair of decimal numbers --&gt;
  &lt;simpleType name="versionType"&gt;
    &lt;restriction base="token"&gt;
      &lt;pattern value="[1-9]+\.[0-9]+"/&gt;
      &lt;enumeration value="1.0"/&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

&lt;/schema&gt;
&lt;CODE ENDS&gt;</pre><a href="#section-6.1-1" class="pilcrow">¶</a>
</div>
</section>
</section>
</div>
<section id="section-7">
      <h2 id="name-internationalization-consid">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-internationalization-consid" class="section-name selfRef">Internationalization Considerations</a>
      </h2>
<p id="section-7-1">
                Data escrow deposits are represented in XML, which provides native support for encoding information 
                using the Unicode character set and its more compact representations, including UTF-8. Conformant XML 
                processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other 
                character encodings through the use of an "encoding" attribute
                in an &lt;?xml?&gt; declaration, the use of UTF-8 
                is <span class="bcp14">RECOMMENDED</span>.<a href="#section-7-1" class="pilcrow">¶</a></p>
</section>
<section id="section-8">
      <h2 id="name-iana-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-8-1">
                This document uses URNs to describe XML namespaces and XML schemas
                conforming to a registry mechanism described in <span>[<a href="#RFC3688" class="xref">RFC3688</a>]</span>.
                Two URI assignments have been registered by the IANA.<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">Registration for the RDE namespace:<a href="#section-8-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-8-3">
        <dt id="section-8-3.1">URI:</dt>
        <dd style="margin-left: 1.5em" id="section-8-3.2">urn:ietf:params:xml:ns:rde-1.0<a href="#section-8-3.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-3.3">Registrant Contact:</dt>
        <dd style="margin-left: 1.5em" id="section-8-3.4">IESG<a href="#section-8-3.4" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-3.5">XML:</dt>
        <dd style="margin-left: 1.5em" id="section-8-3.6">None.  Namespace URIs do not represent an XML specification.<a href="#section-8-3.6" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
<p id="section-8-4">Registration for the RDE XML schema:<a href="#section-8-4" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-8-5">
        <dt id="section-8-5.1">URI:</dt>
        <dd style="margin-left: 1.5em" id="section-8-5.2">urn:ietf:params:xml:schema:rde-1.0<a href="#section-8-5.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-8-5.3">Registrant Contact:</dt>
        <dd style="margin-left: 1.5em" id="section-8-5.4">IESG<a href="#section-8-5.4" class="pilcrow">¶</a>
</dd>
      <dd class="break"></dd>
</dl>
<p id="section-8-6">See <a href="#formalSyntax" class="xref">Section 6</a> ("Formal Syntax") of this document.<a href="#section-8-6" class="pilcrow">¶</a></p>
</section>
<section id="section-9">
      <h2 id="name-security-considerations">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-9-1">
                This specification does not define the security mechanisms to be used in the transmission of the data escrow 
                deposits, since it only specifies the minimum necessary to enable the rebuilding of a registry from 
                deposits without intervention from the original registry.<a href="#section-9-1" class="pilcrow">¶</a></p>
<p id="section-9-2">
                Depending on local policies, some elements -- or, most likely,
                the whole deposit -- will be considered confidential. As such, the parties <span class="bcp14">SHOULD</span> take all necessary precautions, such as encrypting the data at rest and in transit to avoid inadvertent disclosure of private data. Regardless of the precautions taken by the parties regarding data at rest and in transit, authentication credentials <span class="bcp14">MUST NOT</span> be escrowed.<a href="#section-9-2" class="pilcrow">¶</a></p>
<p id="section-9-3">
                Authentication of the parties passing data escrow deposit files is also of the utmost importance. The 
                escrow agent <span class="bcp14">MUST</span> properly authenticate the identity of the registry before accepting data escrow
                deposits. Similarly, the registry <span class="bcp14">MUST</span> authenticate the identity of the escrow agent
                before submitting any data.<a href="#section-9-3" class="pilcrow">¶</a></p>
<p id="section-9-4">
                Additionally, the registry and the escrow agent
                <span class="bcp14">MUST</span> use integrity-checking mechanisms to
                ensure that the
                data transmitted is what the source intended. Validation of the contents by the escrow agent is <span class="bcp14">RECOMMENDED</span>
                to ensure not only that the file was transmitted correctly from the registry but also that the contents are 
                "meaningful".<a href="#section-9-4" class="pilcrow">¶</a></p>
<aside id="section-9-5">
        <p id="section-9-5.1">Note: If Transport Layer Security (TLS) is used when providing
      an escrow service, the recommendations in <span>[<a href="#RFC7525" class="xref">RFC7525</a>]</span> <span class="bcp14">MUST</span> be implemented.<a href="#section-9-5.1" class="pilcrow">¶</a></p>
</aside>
</section>
<section id="section-10">
      <h2 id="name-privacy-considerations">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a>
      </h2>
<p id="section-10-1">
This specification defines a format that may be used to escrow personal data.
The process of data escrow is governed by a legal document agreed upon by the
parties, and such a legal document must ensure that privacy-sensitive and/or personal data receives the required protection.<a href="#section-10-1" class="pilcrow">¶</a></p>
</section>
<section id="section-11">
      <h2 id="name-example-of-a-full-deposit">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-example-of-a-full-deposit" class="section-name selfRef">Example of a Full Deposit</a>
      </h2>
<p id="section-11-1">Example of a Full Deposit with the two example objects rdeObj1 and rdeObj2:<a href="#section-11-1" class="pilcrow">¶</a></p>
<div id="section-11-2">
<pre class="sourcecode lang-xml">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;rde:deposit
  xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
  xmlns:rdeObj1="urn:example:params:xml:ns:rdeObj1-1.0"
  xmlns:rdeObj2="urn:example:params:xml:ns:rdeObj2-1.0"
  type="FULL"
  id="20191018001"&gt;
  &lt;rde:watermark&gt;2019-10-17T23:59:59Z&lt;/rde:watermark&gt;
  &lt;rde:rdeMenu&gt;
    &lt;rde:version&gt;1.0&lt;/rde:version&gt;
    &lt;rde:objURI&gt;urn:example:params:xml:ns:rdeObj1-1.0&lt;/rde:objURI&gt;
    &lt;rde:objURI&gt;urn:example:params:xml:ns:rdeObj2-1.0&lt;/rde:objURI&gt;
  &lt;/rde:rdeMenu&gt;
  &lt;rde:contents&gt;
    &lt;rdeObj1:rdeObj1&gt;
      &lt;rdeObj1:name&gt;EXAMPLE&lt;/rdeObj1:name&gt;
    &lt;/rdeObj1:rdeObj1&gt;
    &lt;rdeObj2:rdeObj2&gt;
      &lt;rdeObj2:id&gt;fsh8013-EXAMPLE&lt;/rdeObj2:id&gt;
    &lt;/rdeObj2:rdeObj2&gt;
  &lt;/rde:contents&gt;
&lt;/rde:deposit&gt;</pre><a href="#section-11-2" class="pilcrow">¶</a>
</div>
</section>
<section id="section-12">
      <h2 id="name-example-of-a-differential-d">
<a href="#section-12" class="section-number selfRef">12. </a><a href="#name-example-of-a-differential-d" class="section-name selfRef">Example of a Differential Deposit</a>
      </h2>
<p id="section-12-1">Example of a Differential Deposit with the two example objects rdeObj1 and rdeObj2:<a href="#section-12-1" class="pilcrow">¶</a></p>
<div id="section-12-2">
<pre class="sourcecode lang-xml">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;rde:deposit
  xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
  xmlns:rdeObj1="urn:example:params:xml:ns:rdeObj1-1.0"
  xmlns:rdeObj2="urn:example:params:xml:ns:rdeObj2-1.0"
  type="DIFF"
  id="20191019001" prevId="20191018001"&gt;
  &lt;rde:watermark&gt;2019-10-18T23:59:59Z&lt;/rde:watermark&gt;
  &lt;rde:rdeMenu&gt;
    &lt;rde:version&gt;1.0&lt;/rde:version&gt;
      &lt;rde:objURI&gt;urn:example:params:xml:ns:rdeObj1-1.0&lt;/rde:objURI&gt;
      &lt;rde:objURI&gt;urn:example:params:xml:ns:rdeObj2-1.0&lt;/rde:objURI&gt;
  &lt;/rde:rdeMenu&gt;
  &lt;rde:contents&gt;
    &lt;rdeObj1:rdeObj1&gt;
      &lt;rdeObj1:name&gt;EXAMPLE2&lt;/rdeObj1:name&gt;
    &lt;/rdeObj1:rdeObj1&gt;
    &lt;rdeObj2:rdeObj2&gt;
      &lt;rdeObj2:id&gt;sh8014-EXAMPLE&lt;/rdeObj2:id&gt;
    &lt;/rdeObj2:rdeObj2&gt;
  &lt;/rde:contents&gt;
&lt;/rde:deposit&gt;</pre><a href="#section-12-2" class="pilcrow">¶</a>
</div>
</section>
<section id="section-13">
      <h2 id="name-example-of-an-incremental-d">
<a href="#section-13" class="section-number selfRef">13. </a><a href="#name-example-of-an-incremental-d" class="section-name selfRef">Example of an Incremental Deposit</a>
      </h2>
<p id="section-13-1">Example of an Incremental Deposit with the two example objects rdeObj1 and rdeObj2:<a href="#section-13-1" class="pilcrow">¶</a></p>
<div id="section-13-2">
<pre class="sourcecode lang-xml">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;rde:deposit
  xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
  xmlns:rdeObj1="urn:example:params:xml:ns:rdeObj1-1.0"
  xmlns:rdeObj2="urn:example:params:xml:ns:rdeObj2-1.0"
  type="INCR"
  id="20200317001" prevId="20200314001"&gt;
  &lt;rde:watermark&gt;2020-03-16T23:59:59Z&lt;/rde:watermark&gt;
  &lt;rde:rdeMenu&gt;
    &lt;rde:version&gt;1.0&lt;/rde:version&gt;
    &lt;rde:objURI&gt;urn:example:params:xml:ns:rdeObj1-1.0&lt;/rde:objURI&gt;
    &lt;rde:objURI&gt;urn:example:params:xml:ns:rdeObj2-1.0&lt;/rde:objURI&gt;
  &lt;/rde:rdeMenu&gt;
  &lt;rde:deletes&gt;
    &lt;rdeObj1:delete&gt;
      &lt;rdeObj1:name&gt;EXAMPLE1&lt;/rdeObj1:name&gt;
    &lt;/rdeObj1:delete&gt;
    &lt;rdeObj2:delete&gt;
      &lt;rdeObj2:id&gt;fsh8013-EXAMPLE&lt;/rdeObj2:id&gt;
    &lt;/rdeObj2:delete&gt;
  &lt;/rde:deletes&gt;
  &lt;rde:contents&gt;
    &lt;rdeObj1:rdeObj1&gt;
      &lt;rdeObj1:name&gt;EXAMPLE2&lt;/rdeObj1:name&gt;
    &lt;/rdeObj1:rdeObj1&gt;
    &lt;rdeObj2:rdeObj2&gt;
      &lt;rdeObj2:id&gt;sh8014-EXAMPLE&lt;/rdeObj2:id&gt;
    &lt;/rdeObj2:rdeObj2&gt;
  &lt;/rde:contents&gt;
&lt;/rde:deposit&gt;</pre><a href="#section-13-2" class="pilcrow">¶</a>
</div>
</section>
<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="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><span class="refAuthor"> and 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="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="RFC8499">[RFC8499]</dt>
        <dd>
<span class="refAuthor">Hoffman, P.</span><span class="refAuthor">, Sullivan, A.</span><span class="refAuthor">, and K. Fujiwara</span>, <span class="refTitle">"DNS Terminology"</span>, <span class="seriesInfo">BCP 219</span>, <span class="seriesInfo">RFC 8499</span>, <span class="seriesInfo">DOI 10.17487/RFC8499</span>, <time datetime="2019-01" class="refDate">January 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8499">https://www.rfc-editor.org/info/rfc8499</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="W3C.REC-xml-20081126">[W3C.REC-xml-20081126]</dt>
        <dd>
<span class="refAuthor">Bray, T., Ed.</span><span class="refAuthor">, Paoli, J., Ed.</span><span class="refAuthor">, Sperberg-McQueen, C.M., Ed.</span><span class="refAuthor">, Maler, E., Ed.</span><span class="refAuthor">, and F. Yergeau, Ed.</span>, <span class="refTitle">"Extensible Markup Language (XML) 1.0 (Fifth Edition)"</span>, <span class="refContent">REC-xml-20081126</span>, <time datetime="2008-11" class="refDate">November 2008</time>, <span>&lt;<a href="https://www.w3.org/TR/2008/REC-xml-20081126/">https://www.w3.org/TR/2008/REC-xml-20081126/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="W3C.REC-xmlschema-1-20041028">[W3C.REC-xmlschema-1-20041028]</dt>
        <dd>
<span class="refAuthor">Thompson, H.S., Ed.</span><span class="refAuthor">, Beech, D., Ed.</span><span class="refAuthor">, Maloney, M., Ed.</span><span class="refAuthor">, and N. Mendelsohn, Ed.</span>, <span class="refTitle">"XML Schema Part 1: Structures Second Edition"</span>, <span class="refContent">REC-xmlschema-1-20041028</span>, <time datetime="2004-10" class="refDate">October 2004</time>, <span>&lt;<a href="https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="W3C.REC-xmlschema-2-20041028">[W3C.REC-xmlschema-2-20041028]</dt>
      <dd>
<span class="refAuthor">Biron, P. V., Ed.</span><span class="refAuthor"> and A. Malhotra, Ed.</span>, <span class="refTitle">"XML Schema Part 2: Datatypes Second Edition"</span>, <span class="refContent">REC-xmlschema-2-20041028</span>, <time datetime="2004-10" class="refDate">October 2004</time>, <span>&lt;<a href="https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/</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="ICANN-GTLD-RA-20170731">[ICANN-GTLD-RA-20170731]</dt>
        <dd>
<span class="refAuthor">ICANN</span>, <span class="refTitle">"Base Registry Agreement"</span>, <time datetime="2017-07-31" class="refDate">31 July 2017</time>, <span>&lt;<a href="https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.pdf">https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3688">[RFC3688]</dt>
        <dd>
<span class="refAuthor">Mealling, M.</span>, <span class="refTitle">"The IETF XML Registry"</span>, <span class="seriesInfo">BCP 81</span>, <span class="seriesInfo">RFC 3688</span>, <span class="seriesInfo">DOI 10.17487/RFC3688</span>, <time datetime="2004-01" class="refDate">January 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3688">https://www.rfc-editor.org/info/rfc3688</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7525">[RFC7525]</dt>
      <dd>
<span class="refAuthor">Sheffer, Y.</span><span class="refAuthor">, Holz, R.</span><span class="refAuthor">, and P. Saint-Andre</span>, <span class="refTitle">"Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"</span>, <span class="seriesInfo">BCP 195</span>, <span class="seriesInfo">RFC 7525</span>, <span class="seriesInfo">DOI 10.17487/RFC7525</span>, <time datetime="2015-05" class="refDate">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7525">https://www.rfc-editor.org/info/rfc7525</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<section id="section-appendix.a">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="section-appendix.a-1">
                Special suggestions that were incorporated into this document
                were provided by <span class="contact-name">James Gould</span>, <span class="contact-name">Edward Lewis</span>, <span class="contact-name">Jaap Akkerhuis</span>, <span class="contact-name">Lawrence Conroy</span>, <span class="contact-name">Marc Groeneweg</span>,
                <span class="contact-name">Michael Young</span>, <span class="contact-name">Chris Wright</span>, <span class="contact-name">Patrick Mevzek</span>, <span class="contact-name">Stephen Morris</span>, <span class="contact-name">Scott Hollenbeck</span>, <span class="contact-name">Stephane Bortzmeyer</span>,
                <span class="contact-name">Warren Kumari</span>, <span class="contact-name">Paul Hoffman</span>, <span class="contact-name">Vika Mpisane</span>, <span class="contact-name">Bernie Hoeneisen</span>, <span class="contact-name">Jim Galvin</span>, <span class="contact-name">Andrew Sullivan</span>, <span class="contact-name">Hiro Hotta</span>,
                <span class="contact-name">Christopher Browne</span>, <span class="contact-name">Daniel Kalchev</span>, <span class="contact-name">David Conrad</span>, <span class="contact-name">James Mitchell</span>, <span class="contact-name">Francisco Obispo</span>, <span class="contact-name">Bhadresh Modi</span>, and
                <span class="contact-name">Alexander Mayrhofer</span>.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
<p id="section-appendix.a-2">              <span class="contact-name">Shoji Noguchi</span> and <span class="contact-name">Francisco Arias</span> participated
                as coauthors through version 07 of
                draft-arias-noguchi-registry-data-escrow (the precursor to
                this document) and provided invaluable support for this
                document.<a href="#section-appendix.a-2" class="pilcrow">¶</a></p>
</section>
<div id="authors-addresses">
<section id="section-appendix.b">
      <h2 id="name-authors-address">
<a href="#name-authors-address" class="section-name selfRef">Author's Address</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Gustavo Lozano</span></div>
<div dir="auto" class="left"><span class="org">Internet Corporation for Assigned Names and Numbers</span></div>
<div dir="auto" class="left"><span class="street-address">12025 Waterfront Drive, Suite 300</span></div>
<div dir="auto" class="left">
<span class="locality">Los Angeles</span>, <span class="region">CA</span> <span class="postal-code">90292</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+1.310.823.9358" class="tel">+1.310.823.9358</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:gustavo.lozano@icann.org" class="email">gustavo.lozano@icann.org</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>