File: rfc9095.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 (2608 lines) | stat: -rw-r--r-- 105,997 bytes
<!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 9095: Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration</title>
<meta content="Jiankang Yao" name="author">
<meta content="Linlin Zhou" name="author">
<meta content="Hongtao Li" name="author">
<meta content="Ning Kong" name="author">
<meta content="Jiagui Xie" name="author">
<meta content="
       
This document describes an extension of Extensible Provisioning Protocol (EPP) domain name mapping for the provisioning and management  of strict bundling registration of domain names. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for
the provisioning of bundled domain names. This is a nonstandard proprietary extension.
       
    " name="description">
<meta content="xml2rfc 3.9.1" name="generator">
<meta content="IDN" name="keyword">
<meta content="9095" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.9.1
    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="rfc9095.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.ulBare, li.ulBare {
  margin-left: 0em !important;
}
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/rfc9095" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-yao-regext-bundling-registration-06" 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 9095</td>
<td class="center">EPP Bundled Names Mapping</td>
<td class="right">July 2021</td>
</tr></thead>
<tfoot><tr>
<td class="left">Yao, et al.</td>
<td class="center">Informational</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">Independent Submission</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9095" class="eref">9095</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Informational</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2021-07" class="published">July 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">J. Yao</div>
<div class="org">CNNIC</div>
</div>
<div class="author">
      <div class="author-name">L. Zhou</div>
<div class="org">CNNIC</div>
</div>
<div class="author">
      <div class="author-name">H. Li</div>
<div class="org">CNNIC</div>
</div>
<div class="author">
      <div class="author-name">N. Kong</div>
<div class="org">Consultant</div>
</div>
<div class="author">
      <div class="author-name">J. Xie</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9095</h1>
<h1 id="title">Extensible Provisioning Protocol (EPP) Domain Name Mapping Extension for Strict Bundling Registration</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">
This document describes an extension of Extensible Provisioning Protocol (EPP) domain name mapping for the provisioning and management  of strict bundling registration of domain names. Specified in XML, this mapping extends the EPP domain name mapping to provide additional features required for
the provisioning of bundled domain names. This is a nonstandard proprietary extension.<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 document is not an Internet Standards Track specification; it is
            published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This is a contribution to the RFC Series, independently of any
            other RFC stream.  The RFC Editor has chosen to publish this
            document at its discretion and makes no statement about its value
            for implementation or deployment.  Documents approved for
            publication by the RFC Editor are not candidates for any level of
            Internet Standard; see 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/rfc9095">https://www.rfc-editor.org/info/rfc9095</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.<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="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" 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>
</li>
          <li class="compact toc ulEmpty ulBare" 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></p>
</li>
          <li class="compact toc ulEmpty ulBare" 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-overview" class="xref">Overview</a></p>
</li>
          <li class="compact toc ulEmpty ulBare" 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-requirement-for-bundling-re" class="xref">Requirement for Bundling Registration of Names</a></p>
</li>
          <li class="compact toc ulEmpty ulBare" 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-attributes" class="xref">Object Attributes</a></p>
<ul class="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" 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-rdn" class="xref">RDN</a></p>
</li>
              <li class="compact toc ulEmpty ulBare" 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-bdn" class="xref">BDN</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulEmpty ulBare" 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-epp-command-mapping" class="xref">EPP Command Mapping</a></p>
<ul class="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" 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-epp-query-commands" class="xref">EPP Query Commands</a></p>
<ul class="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.1.2.1">
                    <p id="section-toc.1-1.6.2.1.2.1.1"><a href="#section-6.1.1" class="xref">6.1.1</a>.  <a href="#name-epp-check-command" class="xref">EPP &lt;check&gt; Command</a></p>
</li>
                  <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.1.2.2">
                    <p id="section-toc.1-1.6.2.1.2.2.1"><a href="#section-6.1.2" class="xref">6.1.2</a>.  <a href="#name-epp-info-command" class="xref">EPP &lt;info&gt; Command</a></p>
</li>
                  <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.1.2.3">
                    <p id="section-toc.1-1.6.2.1.2.3.1"><a href="#section-6.1.3" class="xref">6.1.3</a>.  <a href="#name-epp-transfer-query-command" class="xref">EPP &lt;transfer&gt; Query Command</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.2">
                <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-epp-transform-commands" class="xref">EPP Transform Commands</a></p>
<ul class="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.2.2.1">
                    <p id="section-toc.1-1.6.2.2.2.1.1"><a href="#section-6.2.1" class="xref">6.2.1</a>.  <a href="#name-epp-create-command" class="xref">EPP &lt;create&gt; Command</a></p>
</li>
                  <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.2.2.2">
                    <p id="section-toc.1-1.6.2.2.2.2.1"><a href="#section-6.2.2" class="xref">6.2.2</a>.  <a href="#name-epp-delete-command" class="xref">EPP &lt;delete&gt; Command</a></p>
</li>
                  <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.2.2.3">
                    <p id="section-toc.1-1.6.2.2.2.3.1"><a href="#section-6.2.3" class="xref">6.2.3</a>.  <a href="#name-epp-renew-command" class="xref">EPP &lt;renew&gt; Command</a></p>
</li>
                  <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.2.2.4">
                    <p id="section-toc.1-1.6.2.2.2.4.1"><a href="#section-6.2.4" class="xref">6.2.4</a>.  <a href="#name-epp-transfer-command" class="xref">EPP &lt;transfer&gt; Command</a></p>
</li>
                  <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.6.2.2.2.5">
                    <p id="section-toc.1-1.6.2.2.2.5.1"><a href="#section-6.2.5" class="xref">6.2.5</a>.  <a href="#name-epp-update-command" class="xref">EPP &lt;update&gt; Command</a></p>
</li>
                </ul>
</li>
            </ul>
</li>
          <li class="compact toc ulEmpty ulBare" 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-formal-syntax" class="xref">Formal Syntax</a></p>
</li>
          <li class="compact toc ulEmpty ulBare" 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-internationalization-consid" class="xref">Internationalization Considerations</a></p>
</li>
          <li class="compact toc ulEmpty ulBare" 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-iana-considerations" class="xref">IANA Considerations</a></p>
<ul class="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" id="section-toc.1-1.9.2.1">
                <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-xml-namespace-and-xml-schem" class="xref">XML Namespace and XML Schema</a></p>
<ul class="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" id="section-toc.1-1.9.2.1.2.1">
                    <p id="section-toc.1-1.9.2.1.2.1.1"><a href="#section-9.1.1" class="xref">9.1.1</a>.  <a href="#name-bdn-namespace" class="xref">BDN Namespace</a></p>
</li>
                  <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.9.2.1.2.2">
                    <p id="section-toc.1-1.9.2.1.2.2.1"><a href="#section-9.1.2" class="xref">9.1.2</a>.  <a href="#name-bdn-xml-schema" class="xref">BDN XML Schema</a></p>
</li>
                </ul>
</li>
              <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.9.2.2">
                <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-epp-extension" class="xref">EPP Extension</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulEmpty ulBare" 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-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="compact toc ulEmpty ulBare" 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-references" class="xref">References</a></p>
<ul class="compact toc ulEmpty ulBare">
<li class="compact toc ulEmpty ulBare" id="section-toc.1-1.11.2.1">
                <p id="section-toc.1-1.11.2.1.1"><a href="#section-11.1" class="xref">11.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
</li>
              <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.11.2.2">
                <p id="section-toc.1-1.11.2.2.1"><a href="#section-11.2" class="xref">11.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a></p>
</li>
          <li class="compact toc ulEmpty ulBare" id="section-toc.1-1.13">
            <p id="section-toc.1-1.13.1"><a href="#appendix-B" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</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">
   In RFC 4290 <span>[<a href="#RFC4290" class="xref">RFC4290</a>]</span>, the "variant(s)" are character(s) and/or string(s) that are
          treated as equivalent to the base character. In this document, variants are those strings that are treated as 
   equivalent to each other according to the domain name registration policy.
   Bundled domain names are those that share the same Top-Level Domain (TLD) but whose second-level labels are 
   variants or those that have identical second-level labels for which certain parameters are shared in different TLDs.
   For example, the Public Interest Registry has requested to implement bundling of 
   second-level domains for .NGO and .ONG. So we have two kinds of bundled domain names. The first one is 
in the form of "V-label.TLD", in which the second-level label (V-label) is a variant sharing the same TLD. 
The second one is 
in the form of "LABEL.V-tld", in which the second-level label (LABEL) remains the same 
but ends with a different TLD (V-tld) and 
these different V-tlds are managed by the same entity.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">
Bundled domain names normally share some attributes. Policy-wise
   bundling can be implemented in three ways. The first one 
 is strict bundling, which
 requires all bundled names to share many of the same attributes. When creating,
updating, or transferring any of the bundled domain names,
 all bundled domain names will be created, updated, or transferred atomically.
 The second one is partial bundling, which requires
the bundled domain names to be registered by the
same registrant.
 The third one is relaxed bundling, which has no specific requirements on the domain
registration.

This document mainly addresses the strict bundling name registration.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3"> 

For the name variants, different registries have different policies. Some registries adopt 
the policy that variant Internationalized Domain Names (IDNs) should be blocked. But some registries adopt the policy that variant IDNs 
that are identified as
equivalent are allocated or delegated to the same registrant. For example, most registries offering a Chinese Domain Name (CDN) adopt a registration policy whereby a registrant can apply for an original CDN in
any form: Simplified Chinese (SC) form, Traditional Chinese (TC) form, or other variant forms. The corresponding variant CDN in SC form and in TC form will also be delegated to the
same registrant. All variant names in the same TLD share a common set of attributes.
This document mainly discusses the situation in which variant IDNs 
that are identified as
equivalent are allocated or delegated to the same registrant.<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4">
The basic Extensible Provisioning Protocol (EPP) domain name mapping
<span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span> provides the facility for single domain name registration. 
It does not specify how to register
the strict bundled names that share many of the attributes.<a href="#section-1-4" class="pilcrow">¶</a></p>
<p id="section-1-5">
In order to meet the above requirements of strict bundled name registration, this document describes an
extension of the EPP domain name mapping
<span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span> for the provisioning and management of bundled names. 
This document describes a nonstandard
proprietary extension. This extension is especially useful for registries performing Chinese Domain Name registration.

This method is also useful for other language domain names that have similar issues with Chinese Domain Names.


This document
is specified using Extensible Markup Language (XML) 1.0 as described in
<span>[<a href="#W3C.REC-xml-20040204" class="xref">W3C.REC-xml-20040204</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">
The EPP core protocol specification <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span> provides a complete description
of EPP command and response structures. A thorough understanding of the base protocol specification
is necessary to understand the extension mapping described in this document.<a href="#section-1-6" class="pilcrow">¶</a></p>
<p id="section-1-7">
This document uses many IDN concepts, so a thorough understanding of the IDNs for
Application (IDNA, described in <span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span>, <span>[<a href="#RFC5891" class="xref">RFC5891</a>]</span>, and
<span>[<a href="#RFC5892" class="xref">RFC5892</a>]</span>) and the variant approach discussed in
<span>[<a href="#RFC4290" class="xref">RFC4290</a>]</span> is assumed.<a href="#section-1-7" class="pilcrow">¶</a></p>
</section>
<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">
 Variants in this document are those strings that are treated as equivalent to each other according to the domain name registration policy for certain TLDs.<a href="#section-2-1" class="pilcrow">¶</a></p>
<p id="section-2-2">
 Bundled domain names are bundled together according to the domain name registration policy.
 For example, many Chinese Domain Name registries follow the principle described in RFC 3743 <span>[<a href="#RFC3743" class="xref">RFC3743</a>]</span>.
 
 Bundled domain names should belong to the same owner. If bundled domain names are under different TLDs, those TLDs should 
 be managed by the same entity.<a href="#section-2-2" class="pilcrow">¶</a></p>
<p id="section-2-3">
The terms "registered domain name" (RDN) and "bundled domain name" (BDN) are used in this document.
 RDN represents the valid domain name that registrants submitted for
the initial registration.
 BDN represents the bundled domain name produced according to the bundled domain name 
registration policy.


 In current practice, the number of BDNs is
usually kept at one according to the registration policy set by
the registry.


 Both the RDN and BDN specified in this document will be registered via EPP. All other domain names related to
the RDN will be blocked.<a href="#section-2-3" class="pilcrow">¶</a></p>
<p id="section-2-4">
  The "uLabel" attribute in this document is used to express the U-label of an Internationalized Domain Name as a series of characters
  where non-ASCII characters will be represented in the format of "&amp;#xXXXX;" where XXXX is a Unicode point by using the XML escaping mechanism.
  The U-label is defined in <span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span>. This document chooses this format of literal HTML ampersand codes, not the expected Unicode character codes. Unicode characters may not be displayed correctly in some text file readers, while HTML numeric character references are easy for HTML processors. The implementation following this document should use Unicode characters directly.<a href="#section-2-4" class="pilcrow">¶</a></p>
<p id="section-2-5">
 This document uses the prefix "b-dn" for the namespace "urn:ietf:params:xml:ns:epp:b-dn" throughout. 
 Implementations cannot assume that any particular prefix is used and 
 must employ a namespace-aware XML parser and serializer to interpret and output the XML documents.<a href="#section-2-5" class="pilcrow">¶</a></p>
<p id="section-2-6">
In the examples, "C:" represents lines sent by a protocol client, and "S:" represents lines returned by
a protocol server. Indentation and spacing in the examples are provided only to illustrate element
relationships and are not a required feature of this specification.<a href="#section-2-6" class="pilcrow">¶</a></p>
<p id="section-2-7">
XML is case sensitive. Unless stated otherwise, the XML specifications and examples provided in this
document must be interpreted in the character case presented to develop a conforming implementation.<a href="#section-2-7" class="pilcrow">¶</a></p>
</section>
<section id="section-3">
      <h2 id="name-overview">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-overview" class="section-name selfRef">Overview</a>
      </h2>
<p id="section-3-1">
Domain registries have usually adopted a registration model whereby metadata relating to a
domain name, such as its expiration date and sponsoring registrar, are stored as properties of the
domain object. The domain object is then considered an atomic unit of registration on which
operations such as update, renewal, and deletion may be performed.<a href="#section-3-1" class="pilcrow">¶</a></p>
<p id="section-3-2">
Bundled names brought about the need for multiple domain names to be registered and
managed as a single package. In this model, the registry typically accepts
a domain registration request (i.e., EPP domain &lt;create&gt; command) containing the domain name
to be registered. This domain name is referred to as the RDN in this document. As part of the
processing of the registration request, the registry generates a set of bundled names that
are related to the RDN, either programmatically or with the guidance of registration policies, and
places them in the registration package together with the RDN.<a href="#section-3-2" class="pilcrow">¶</a></p>
<p id="section-3-3">
The bundled names share many properties, such as expiration date and sponsoring
registrar, by sharing the same domain object. 
So when registrants update any property of a domain object within a bundle package,


that property will be updated at the same time for all other domain
 objects in the bundle package.<a href="#section-3-3" class="pilcrow">¶</a></p>
</section>
<section id="section-4">
      <h2 id="name-requirement-for-bundling-re">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-requirement-for-bundling-re" class="section-name selfRef">Requirement for Bundling Registration of Names</a>
      </h2>
<p id="section-4-1">
The bundled names, whether they are in the form of "V-label.TLD" or "LABEL.V-tld", should share 
some parameters or attributes associated with domain names. Typically, bundled names will share the following
parameters or attributes:<a href="#section-4-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4-2.1">
Registrar ownership<a href="#section-4-2.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-2.2">
Registration and expiry dates<a href="#section-4-2.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-2.3">
Registrant, admin, billing, and technical contacts<a href="#section-4-2.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-2.4">
Name server association<a href="#section-4-2.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-2.5">
Domain status<a href="#section-4-2.5" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-2.6">
Applicable grace periods (add grace period, renew grace period, auto-renew grace period, transfer grace period, and redemption grace period) <span>[<a href="#RFC3915" class="xref">RFC3915</a>]</span><a href="#section-4-2.6" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-4-3">
Because the domain names are bundled and share the same parameters or attributes, the EPP command should 
do some processing for these requirements:<a href="#section-4-3" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-4-4.1">
When performing a domain &lt;check&gt; command, either the BDN or RDN can be queried with the EPP command and
will return the same response.<a href="#section-4-4.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-4.2">
When performing a domain &lt;info&gt; command, either the BDN or RDN can be queried, and
the same response will include both BDN and RDN information with the same attributes.<a href="#section-4-4.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-4.3">
When performing a domain &lt;create&gt; command,
 if the domain name is available, both the BDN and RDN
 will be registered.<a href="#section-4-4.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-4.4">
When performing a domain &lt;delete&gt; command,
 either the BDN or RDN will be accepted. If the domain name is registered, both the BDN and RDN
 will be deleted.<a href="#section-4-4.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-4.5">
When performing a domain &lt;renew&gt; command,
 either the BDN or RDN will be accepted. Upon a successful domain renewal, both the BDN and RDN
 will have their expiry date extended by the requested term. Upon a successful domain
renewal, both the BDN and RDN will conform to the same renew grace period.<a href="#section-4-4.5" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-4.6">When performing a domain &lt;transfer&gt; command,
 either the BDN or RDN will be accepted. Upon successful completion of a domain
transfer request, both the BDN and RDN will enter a pendingTransfer status. Upon approval of the
transfer request, both the BDN and RDN will be owned and managed by the same new registrant.<a href="#section-4-4.6" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-4-4.7">
When performing a domain &lt;update&gt; command, 
 either the BDN or RDN will be accepted. Any modifications to contact associations,
name server associations, domain status values, and authorization information will be
 applied to both the BDN and RDN.<a href="#section-4-4.7" class="pilcrow">¶</a>
</li>
      </ul>
</section>
<section id="section-5">
      <h2 id="name-object-attributes">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-object-attributes" class="section-name selfRef">Object Attributes</a>
      </h2>
<p id="section-5-1">
This extension defines the following additional elements to the EPP domain name mapping
<span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. All of these additional elements are returned from the &lt;domain:info&gt;
command.<a href="#section-5-1" class="pilcrow">¶</a></p>
<section id="section-5.1">
        <h3 id="name-rdn">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-rdn" class="section-name selfRef">RDN</a>
        </h3>
<p id="section-5.1-1">
The RDN is an ASCII name or an IDN with the A-label <span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span> form. 
In this document, its corresponding element is &lt;b-dn:rdn&gt;. An optional attribute
"uLabel" associated with &lt;b-dn:rdn&gt; is used to represent the U-label
<span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span> form.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<p id="section-5.1-2">
For example:<a href="#section-5.1-2" class="pilcrow">¶</a></p>
<div id="section-5.1-3">
<pre class="sourcecode lang-xml">
&lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example"&gt; xn--
   fsq270a.example&lt;/b-dn:rdn&gt;
</pre><a href="#section-5.1-3" class="pilcrow">¶</a>
</div>
</section>
<section id="section-5.2">
        <h3 id="name-bdn">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-bdn" class="section-name selfRef">BDN</a>
        </h3>
<p id="section-5.2-1">
The BDN is an ASCII name or an IDN with the A-label <span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span> form that is converted from the
corresponding BDN. In this document, its corresponding element is &lt;b-dn:bdn&gt;. An optional attribute
"uLabel" associated with &lt;b-dn:bdn&gt; is used to represent the U-label
<span>[<a href="#RFC5890" class="xref">RFC5890</a>]</span> form.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<p id="section-5.2-2">
For example:<a href="#section-5.2-2" class="pilcrow">¶</a></p>
<div id="section-5.2-3">
<pre class="sourcecode lang-xml">
&lt;b-dn:bdn uLabel="&amp;#x5BE6;&amp;#x4F8B;.example"&gt; xn--
   fsqz41a.example&lt;/b-dn:bdn&gt;
</pre><a href="#section-5.2-3" class="pilcrow">¶</a>
</div>
</section>
</section>
<section id="section-6">
      <h2 id="name-epp-command-mapping">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-epp-command-mapping" class="section-name selfRef">EPP Command Mapping</a>
      </h2>
<p id="section-6-1">
A detailed description of the EPP syntax and semantics can be found in the EPP core protocol
specification <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>. The command mappings described here are specifically
for use in provisioning and managing bundled names via EPP.<a href="#section-6-1" class="pilcrow">¶</a></p>
<section id="section-6.1">
        <h3 id="name-epp-query-commands">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-epp-query-commands" class="section-name selfRef">EPP Query Commands</a>
        </h3>
<p id="section-6.1-1">
EPP provides three commands to retrieve domain information: &lt;check&gt; to determine if a domain
object can be provisioned within a repository, &lt;info&gt; to retrieve detailed information
associated with a domain object, and &lt;transfer&gt; to retrieve domain-object transfer status
information.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
<section id="section-6.1.1">
          <h4 id="name-epp-check-command">
<a href="#section-6.1.1" class="section-number selfRef">6.1.1. </a><a href="#name-epp-check-command" class="section-name selfRef">EPP &lt;check&gt; Command</a>
          </h4>
<p id="section-6.1.1-1">
This extension does not add any element to the EPP &lt;check&gt; command or &lt;check&gt; response described in the EPP domain name mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. However, when either the RDN or BDN is sent for a check, the response should contain both RDN and BDN information, which may also give some explanation in the reason field to tell the registrant that the associated domain name is a produced name according to some bundle domain name policy.<a href="#section-6.1.1-1" class="pilcrow">¶</a></p>
<span id="name-example-check-response"></span><figure id="figure-1">
            <div id="section-6.1.1-2.1">
<pre class="sourcecode lang-xml">
S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:  &lt;response&gt;
S:    &lt;result code="1000"&gt;
S:      &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:    &lt;/result&gt;
S:    &lt;resData&gt;
S:      &lt;domain:chkData
S:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
S:          &lt;domain:cd&gt;
S:           &lt;domain:name avail="1"&gt;
S:            xn--fsq270a.example&lt;/domain:name&gt;
S:          &lt;/domain:cd&gt;
S:          &lt;domain:cd&gt;
S:            &lt;domain:name avail="1"&gt;
S:              xn--fsqz41a.example
S:            &lt;/domain:name&gt;
S:            &lt;domain:reason&gt;This associated domain name is
S:              a produced name based on bundle name policy.
S:            &lt;/domain:reason&gt;
S:          &lt;/domain:cd&gt;
S:      &lt;/domain:chkData&gt;
S:    &lt;/resData&gt;
S:    &lt;trID&gt;
S:      &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:      &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:    &lt;/trID&gt;
S:  &lt;/response&gt;
S:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
<a href="#name-example-check-response" class="selfRef">Example &lt;check&gt; Response</a>
            </figcaption></figure>
</section>
<section id="section-6.1.2">
          <h4 id="name-epp-info-command">
<a href="#section-6.1.2" class="section-number selfRef">6.1.2. </a><a href="#name-epp-info-command" class="section-name selfRef">EPP &lt;info&gt; Command</a>
          </h4>
<p id="section-6.1.2-1">
This extension does not add any element to the EPP &lt;info&gt; command described in the EPP domain
mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. However, additional elements are defined for the
&lt;info&gt; response.<a href="#section-6.1.2-1" class="pilcrow">¶</a></p>
<p id="section-6.1.2-2">
When an &lt;info&gt; command has been processed successfully, the EPP &lt;resData&gt; element must
contain child elements as described in the EPP domain mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. In
addition, unless some registration policy has some special processing, the EPP &lt;extension&gt; element should contain a child &lt;b-dn:infData&gt; element that
identifies the extension namespace if the domain object has data associated with this extension and
based on its registration policy. The &lt;b-dn:infData&gt; element contains the &lt;b-dn:bundle&gt;, which
has the following child elements:<a href="#section-6.1.2-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-6.1.2-3.1">
A &lt;b-dn:rdn&gt; element that contains the RDN, along with the attribute described below.<a href="#section-6.1.2-3.1" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-6.1.2-3.2">
An optional &lt;b-dn:bdn&gt; element that contains the BDN, along with the attribute described
below.<a href="#section-6.1.2-3.2" class="pilcrow">¶</a>
</li>
          </ul>
<p id="section-6.1.2-4">
The above elements contain the following attribute:<a href="#section-6.1.2-4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-6.1.2-5.1">
An optional "uLabel" attribute represents the U-label of the element.<a href="#section-6.1.2-5.1" class="pilcrow">¶</a>
</li>
          </ul>
<span id="name-example-info-response-for-a"></span><figure id="figure-2">
            <div id="section-6.1.2-6.1">
<pre class="sourcecode lang-xml">
S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:  &lt;response&gt;
S:    &lt;result code="1000"&gt;
S:      &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:    &lt;/result&gt;
S:    &lt;resData&gt;
S:      &lt;domain:infData
S:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
S:        &lt;domain:name&gt;xn--fsq270a.example&lt;/domain:name&gt;
S:        &lt;domain:roid&gt;58812678-domain&lt;/domain:roid&gt;
S:        &lt;domain:status s="ok"/&gt;
S:        &lt;domain:registrant&gt;123&lt;/domain:registrant&gt;
S:        &lt;domain:contact type="admin"&gt;123&lt;/domain:contact&gt;
S:        &lt;domain:contact type="tech"&gt;123&lt;/domain:contact&gt;
S:        &lt;domain:ns&gt;
S:          &lt;domain:hostObj&gt;ns1.example.cn
S:          &lt;/domain:hostObj&gt;
S:        &lt;/domain:ns&gt;
S:        &lt;domain:clID&gt;ClientX&lt;/domain:clID&gt;
S:        &lt;domain:crID&gt;ClientY&lt;/domain:crID&gt;
S:        &lt;domain:crDate&gt;2019-04-03T22:00:00.0Z
S:        &lt;/domain:crDate&gt;
S:        &lt;domain:exDate&gt;2022-04-03T22:00:00.0Z
S:        &lt;/domain:exDate&gt;
S:        &lt;domain:authInfo&gt;
S:          &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt;
S:        &lt;/domain:authInfo&gt;
S:      &lt;/domain:infData&gt;
S:    &lt;/resData&gt;
S:    &lt;extension&gt;
S:      &lt;b-dn:infData
S:        xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"&gt;
S:        &lt;b-dn:bundle&gt;
S:          &lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example"&gt;
S:            xn--fsq270a.example
S:          &lt;/b-dn:rdn&gt;
S:          &lt;b-dn:bdn uLabel="&amp;#x5BE6;&amp;#x4F8B;.example"&gt;
S:            xn--fsqz41a.example
S:          &lt;/b-dn:bdn&gt;
S:        &lt;/b-dn:bundle&gt;
S:      &lt;/b-dn:infData&gt;
S:    &lt;/extension&gt;
S:    &lt;trID&gt;
S:      &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:      &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:    &lt;/trID&gt;
S:  &lt;/response&gt;
S:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
<a href="#name-example-info-response-for-a" class="selfRef">Example &lt;info&gt; Response for an Authorized Client</a>
            </figcaption></figure>
<p id="section-6.1.2-7">
The &lt;info&gt; response for the unauthorized client has not been changed, see
<span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span> for details.<a href="#section-6.1.2-7" class="pilcrow">¶</a></p>
<p id="section-6.1.2-8">
An EPP error response must be returned if an &lt;info&gt; command cannot be processed for any reason.<a href="#section-6.1.2-8" class="pilcrow">¶</a></p>
</section>
<section id="section-6.1.3">
          <h4 id="name-epp-transfer-query-command">
<a href="#section-6.1.3" class="section-number selfRef">6.1.3. </a><a href="#name-epp-transfer-query-command" class="section-name selfRef">EPP &lt;transfer&gt; Query Command</a>
          </h4>
<p id="section-6.1.3-1">
This extension does not add any element to the EPP &lt;transfer&gt; command or &lt;transfer&gt; response described in the EPP domain mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>.<a href="#section-6.1.3-1" class="pilcrow">¶</a></p>
</section>
</section>
<section id="section-6.2">
        <h3 id="name-epp-transform-commands">
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-epp-transform-commands" class="section-name selfRef">EPP Transform Commands</a>
        </h3>
<p id="section-6.2-1">
EPP provides five commands to transform domain objects: &lt;create&gt; to create an instance of a
domain object, &lt;delete&gt; to delete an instance of a domain object, &lt;renew&gt; to extend the
validity period of a domain object, &lt;transfer&gt; to manage domain object sponsorship changes,
and &lt;update&gt; to change information associated with a domain object.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
<p id="section-6.2-2">
When these commands have been processed successfully, the EPP &lt;resData&gt; element must
contain child elements as described in the EPP domain mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. Unless some registration policy has some special processing,
 this EPP &lt;extension&gt; element should contain 
 the &lt;b-dn:bundle&gt;, which
has the following child elements:<a href="#section-6.2-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-6.2-3.1">
A &lt;b-dn:rdn&gt; element that contains the RDN, along with the attribute described below.<a href="#section-6.2-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-6.2-3.2">
An optional &lt;b-dn:bdn&gt; element that contains the BDN, along with the attribute described
below.<a href="#section-6.2-3.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-6.2-4">
The above elements contain the following attribute:<a href="#section-6.2-4" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-6.2-5.1">
An optional "uLabel" attribute represents the U-label of the element.<a href="#section-6.2-5.1" class="pilcrow">¶</a>
</li>
        </ul>
<section id="section-6.2.1">
          <h4 id="name-epp-create-command">
<a href="#section-6.2.1" class="section-number selfRef">6.2.1. </a><a href="#name-epp-create-command" class="section-name selfRef">EPP &lt;create&gt; Command</a>
          </h4>
<p id="section-6.2.1-1">
This extension defines additional elements to extend the EPP &lt;create&gt; command described in the
EPP domain name mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span> for bundled names registration.<a href="#section-6.2.1-1" class="pilcrow">¶</a></p>
<p id="section-6.2.1-2">
In addition to the EPP command elements described in the EPP domain mapping
<span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>, the &lt;create&gt; command shall contain an &lt;extension&gt;
element. 

Unless some registration policy has some special processing, the &lt;extension&gt; element should contain a child &lt;b-dn:create&gt; element that
identifies the bundle namespace and a child &lt;b-dn:rdn&gt; element that identifies the U-label form
of the registered domain name with the "uLabel" attribute. The U-label is used for easy reading by the registrants and easy debugging by the registrars and the registries.<a href="#section-6.2.1-2" class="pilcrow">¶</a></p>
<span id="name-example-create-command"></span><figure id="figure-3">
            <div id="section-6.2.1-3.1">
<pre class="sourcecode lang-xml">
C:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
C:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
C:  &lt;command&gt;
C:    &lt;create&gt;
C:      &lt;domain:create
C:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:        &lt;domain:name&gt;xn--fsq270a.example&lt;/domain:name&gt;
C:        &lt;domain:period unit="y"&gt;2&lt;/domain:period&gt;
C:        &lt;domain:registrant&gt;123&lt;/domain:registrant&gt;
C:        &lt;domain:contact type="admin"&gt;123&lt;/domain:contact&gt;
C:        &lt;domain:contact type="tech"&gt;123&lt;/domain:contact&gt;
C:        &lt;domain:authInfo&gt;
C:          &lt;domain:pw&gt;2fooBAR&lt;/domain:pw&gt;
C:        &lt;/domain:authInfo&gt;
C:      &lt;/domain:create&gt;
C:    &lt;/create&gt;
C:    &lt;extension&gt;
C:      &lt;b-dn:create
C:        xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"&gt;
C:        &lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example"&gt;
C:          xn--fsq270a.example
C:        &lt;/b-dn:rdn&gt;
C:      &lt;/b-dn:create&gt;
C:    &lt;/extension&gt;
C:    &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:  &lt;/command&gt;
C:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
<a href="#name-example-create-command" class="selfRef">Example &lt;create&gt; Command</a>
            </figcaption></figure>
<p id="section-6.2.1-4">
When a &lt;create&gt; command has been processed successfully, the EPP &lt;creData&gt; element
must contain child elements as described in the EPP domain mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>.




In addition, unless some registration policy has some special processing, the EPP &lt;extension&gt; element should contain a child &lt;b-dn:creData&gt; element
that identifies the extension namespace if the domain object has data associated with this extension
and based on its registration policy. The &lt;b-dn:creData&gt; element contains the &lt;b-dn:bundle&gt;
element.<a href="#section-6.2.1-4" class="pilcrow">¶</a></p>
<span id="name-example-create-response"></span><figure id="figure-4">
            <div id="section-6.2.1-5.1">
<pre class="sourcecode lang-xml">
S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:  &lt;response&gt;
S:    &lt;result code="1000"&gt;
S:      &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:    &lt;/result&gt;
S:    &lt;resData&gt;
S:      &lt;domain:creData
S:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
S:        &lt;domain:name&gt;xn--fsq270a.example&lt;/domain:name&gt;
S:        &lt;domain:crDate&gt;2019-04-03T22:00:00.0Z&lt;/domain:crDate&gt;
S:        &lt;domain:exDate&gt;2021-04-03T22:00:00.0Z&lt;/domain:exDate&gt;
S:      &lt;/domain:creData&gt;
S:    &lt;/resData&gt;
S:    &lt;extension&gt;
S:      &lt;b-dn:creData
S:        xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"&gt;
S:        &lt;b-dn:bundle&gt;
S:          &lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example"&gt;
S:            xn--fsq270a.example
S:          &lt;/b-dn:rdn&gt;
S:          &lt;b-dn:bdn uLabel="&amp;#x5BE6;&amp;#x4F8B;.example" &gt;
S:            xn--fsqz41a.example
S:          &lt;/b-dn:bdn&gt;
S:        &lt;/b-dn:bundle&gt;
S:      &lt;/b-dn:creData&gt;
S:    &lt;/extension&gt;
S:    &lt;trID&gt;
S:      &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:      &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:    &lt;/trID&gt;
S:  &lt;/response&gt;
S:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
<a href="#name-example-create-response" class="selfRef">Example &lt;create&gt; Response</a>
            </figcaption></figure>
<p id="section-6.2.1-6">
An EPP error response must be returned if a &lt;create&gt;      command cannot be processed     for     any
reason.<a href="#section-6.2.1-6" class="pilcrow">¶</a></p>
</section>
<section id="section-6.2.2">
          <h4 id="name-epp-delete-command">
<a href="#section-6.2.2" class="section-number selfRef">6.2.2. </a><a href="#name-epp-delete-command" class="section-name selfRef">EPP &lt;delete&gt; Command</a>
          </h4>
<p id="section-6.2.2-1">
This extension does not add any element to the EPP &lt;delete&gt; command described in the EPP
domain mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. However, additional elements are defined for the
&lt;delete&gt; response.<a href="#section-6.2.2-1" class="pilcrow">¶</a></p>
<p id="section-6.2.2-2">
When a &lt;delete&gt; command has been processed successfully, the EPP &lt;delData&gt; element must
contain child elements as described in the EPP domain mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. 
In addition, unless some registration policy has some special processing, the EPP &lt;extension&gt; element should contain a child &lt;b-dn:delData&gt; element that
identifies the extension namespace if the domain object has data associated with this extension and
based on its registration policy. The &lt;b-dn:delData&gt; element should contain the &lt;b-dn:bundle&gt;
element.<a href="#section-6.2.2-2" class="pilcrow">¶</a></p>
<span id="name-example-delete-response"></span><figure id="figure-5">
            <div id="section-6.2.2-3.1">
<pre class="sourcecode lang-xml">
S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:  &lt;response&gt;
S:    &lt;result code="1000"&gt;
S:      &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:    &lt;/result&gt;
S:    &lt;extension&gt;
S:      &lt;b-dn:delData
S:        xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"&gt;
S:        &lt;b-dn:bundle&gt;
S:          &lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example"&gt;
S:            xn--fsq270a.example
S:          &lt;/b-dn:rdn&gt;
S:          &lt;b-dn:bdn uLabel="&amp;#x5BE6;&amp;#x4F8B;.example"&gt;
S:            xn--fsqz41a.example
S:          &lt;/b-dn:bdn&gt;
S:        &lt;/b-dn:bundle&gt;
S:      &lt;/b-dn:delData&gt;
S:    &lt;/extension&gt;
S:    &lt;trID&gt;
S:      &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:      &lt;svTRID&gt;54321-XYZ&lt;/svTRID&gt;
S:    &lt;/trID&gt;
S:  &lt;/response&gt;
S:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
<a href="#name-example-delete-response" class="selfRef">Example &lt;delete&gt; Response</a>
            </figcaption></figure>
<p id="section-6.2.2-4">
An EPP error response must be returned if a &lt;delete&gt; command cannot be processed for any
reason.<a href="#section-6.2.2-4" class="pilcrow">¶</a></p>
</section>
<section id="section-6.2.3">
          <h4 id="name-epp-renew-command">
<a href="#section-6.2.3" class="section-number selfRef">6.2.3. </a><a href="#name-epp-renew-command" class="section-name selfRef">EPP &lt;renew&gt; Command</a>
          </h4>
<p id="section-6.2.3-1">

This extension does not add any element to the EPP &lt;renew&gt; command 
described in the EPP domain name mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. However, when either the RDN or BDN is sent for renewal,
 the response should contain both RDN and BDN information. 
 
 When the command has been processed successfully,  
  the EPP &lt;extension&gt; element shall be contained in the response if the domain object has data associated with bundled names. 
  Unless some registration policy has some special processing, this EPP &lt;extension&gt; element should contain 
 the &lt;b-dn:renData&gt;, which contains the &lt;b-dn:bundle&gt; element.<a href="#section-6.2.3-1" class="pilcrow">¶</a></p>
<span id="name-example-renew-response"></span><figure id="figure-6">
            <div id="section-6.2.3-2.1">
<pre class="sourcecode lang-xml">
S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:  &lt;response&gt;
S:    &lt;result code="1000"&gt;
S:      &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:    &lt;/result&gt;
S:    &lt;resData&gt;
S:      &lt;domain:renData
S:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
S:        &lt;domain:name&gt;xn--fsq270a.example&lt;/domain:name&gt;
S:        &lt;domain:exDate&gt;2022-04-03T22:00:00.0Z&lt;/domain:exDate&gt;
S:      &lt;/domain:renData&gt;
S:    &lt;/resData&gt;
S:    &lt;extension&gt;
S:      &lt;b-dn:renData
S:        xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"&gt;
S:        &lt;b-dn:bundle&gt;
S:          &lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example"&gt;
S:            xn--fsq270a.example
S:          &lt;/b-dn:rdn&gt;
S:          &lt;b-dn:bdn uLabel="&amp;#x5BE6;&amp;#x4F8B;.example" &gt;
S:            xn--fsqz41a.example
S:          &lt;/b-dn:bdn&gt;
S:        &lt;/b-dn:bundle&gt;
S:      &lt;/b-dn:renData&gt;
S:    &lt;/extension&gt;
S:    &lt;trID&gt;
S:      &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:      &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:    &lt;/trID&gt;
S:  &lt;/response&gt;
S:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
<a href="#name-example-renew-response" class="selfRef">Example &lt;renew&gt; Response</a>
            </figcaption></figure>
</section>
<section id="section-6.2.4">
          <h4 id="name-epp-transfer-command">
<a href="#section-6.2.4" class="section-number selfRef">6.2.4. </a><a href="#name-epp-transfer-command" class="section-name selfRef">EPP &lt;transfer&gt; Command</a>
          </h4>
<p id="section-6.2.4-1">
    
  This extension does not add any element to the EPP &lt;transfer&gt; command 
described in the EPP domain name mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. 
 
However, additional elements are defined for the &lt;transfer&gt; response in the EPP object mapping. 

 
  When the command has been processed successfully,  
  the EPP &lt;extension&gt; element shall be contained in the response if the domain object has data associated with bundled names. 
  Unless some registration policy has some special processing, this EPP &lt;extension&gt; element should contain 
 the &lt;b-dn:trnData&gt;, which contains the &lt;b-dn:bundle&gt; element.<a href="#section-6.2.4-1" class="pilcrow">¶</a></p>
<span id="name-example-transfer-response"></span><figure id="figure-7">
            <div id="section-6.2.4-2.1">
<pre class="sourcecode lang-xml">
S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:  &lt;response&gt;
S:    &lt;result code="1001"&gt;
S:      &lt;msg&gt;Command completed successfully; action pending&lt;/msg&gt;
S:    &lt;/result&gt;
S:    &lt;resData&gt;
S:      &lt;domain:trnData
S:        xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
S:        &lt;domain:name&gt;xn--fsq270a.example&lt;/domain:name&gt;
S:        &lt;domain:trStatus&gt;pending&lt;/domain:trStatus&gt;
S:        &lt;domain:reID&gt;ClientX&lt;/domain:reID&gt;
S:        &lt;domain:reDate&gt;2021-04-03T22:00:00.0Z&lt;/domain:reDate&gt;
S:        &lt;domain:acID&gt;ClientY&lt;/domain:acID&gt;
S:        &lt;domain:acDate&gt;2021-04-08T22:00:00.0Z&lt;/domain:acDate&gt;
S:        &lt;domain:exDate&gt;2022-04-03T22:00:00.0Z&lt;/domain:exDate&gt;
S:      &lt;/domain:trnData&gt;
S:    &lt;/resData&gt;
S:    &lt;extension&gt;
S:      &lt;b-dn:trnData
S:        xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"&gt;
S:        &lt;b-dn:bundle&gt;
S:          &lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example"&gt;
S:            xn--fsq270a.example
S:          &lt;/b-dn:rdn&gt;
S:          &lt;b-dn:bdn uLabel="&amp;#x5BE6;&amp;#x4F8B;.example"&gt;
S:            xn--fsqz41a.example
S:          &lt;/b-dn:bdn&gt;
S:        &lt;/b-dn:bundle&gt;
S:      &lt;/b-dn:trnData&gt;
S:    &lt;/extension&gt;
S:    &lt;trID&gt;
S:      &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:      &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:    &lt;/trID&gt;
S:  &lt;/response&gt;
S:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-7" class="selfRef">Figure 7</a>:
<a href="#name-example-transfer-response" class="selfRef">Example &lt;transfer&gt; Response</a>
            </figcaption></figure>
</section>
<section id="section-6.2.5">
          <h4 id="name-epp-update-command">
<a href="#section-6.2.5" class="section-number selfRef">6.2.5. </a><a href="#name-epp-update-command" class="section-name selfRef">EPP &lt;update&gt; Command</a>
          </h4>
<p id="section-6.2.5-1">
    
  This extension does not add any element to the EPP &lt;update&gt; command 
described in the EPP domain name mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>. 
 However, additional elements are defined for the &lt;update&gt; response in the EPP object mapping. 

 
  When the command has been processed successfully,  
  the EPP &lt;extension&gt; element shall be contained in the response if the domain object has data associated with bundled names. 
  Unless some registration policy has some special processing, this EPP &lt;extension&gt; element should contain 
 the &lt;b-dn:upData&gt;, which contains the &lt;b-dn:bundle&gt; element.<a href="#section-6.2.5-1" class="pilcrow">¶</a></p>
<span id="name-example-update-response"></span><figure id="figure-8">
            <div id="section-6.2.5-2.1">
<pre class="sourcecode lang-xml">
S:&lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;
S:&lt;epp xmlns="urn:ietf:params:xml:ns:epp-1.0"&gt;
S:  &lt;response&gt;
S:    &lt;result code="1000"&gt;
S:      &lt;msg&gt;Command completed successfully&lt;/msg&gt;
S:    &lt;/result&gt;
S:    &lt;extension&gt;
S:      &lt;b-dn:upData
S:        xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"&gt;
S:        &lt;b-dn:bundle&gt;
S:          &lt;b-dn:rdn uLabel="&amp;#x5B9E;&amp;#x4F8B;.example" &gt;
S:            xn--fsq270a.example
S:          &lt;/b-dn:rdn&gt;
S:          &lt;b-dn:bdn uLabel="&amp;#x5BE6;&amp;#x4F8B;.example"&gt;
S:            xn--fsqz41a.example
S:          &lt;/b-dn:bdn&gt;
S:        &lt;/b-dn:bundle&gt;
S:      &lt;/b-dn:upData&gt;
S:    &lt;/extension&gt;
S:    &lt;trID&gt;
S:      &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
S:      &lt;svTRID&gt;54322-XYZ&lt;/svTRID&gt;
S:    &lt;/trID&gt;
S:  &lt;/response&gt;
S:&lt;/epp&gt;
</pre>
</div>
<figcaption><a href="#figure-8" class="selfRef">Figure 8</a>:
<a href="#name-example-update-response" class="selfRef">Example &lt;update&gt; Response</a>
            </figcaption></figure>
</section>
</section>
</section>
<div id="formal">
<section id="section-7">
      <h2 id="name-formal-syntax">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-formal-syntax" class="section-name selfRef">Formal Syntax</a>
      </h2>
<p id="section-7-1">
An EPP object name mapping extension for bundled names is specified in XML Schema notation. The
formal syntax presented here is a complete schema representation of the object mapping suitable for
automated validation of EPP XML instances. The BEGIN and END 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-7-1" class="pilcrow">¶</a></p>
<div id="section-7-2">
<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:epp:b-dn"
  xmlns:b-dn="urn:ietf:params:xml:ns:epp:b-dn"
  xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
  xmlns="http://www.w3.org/2001/XMLSchema"
  elementFormDefault="qualified"&gt;

&lt;!--
  Import common element types.
--&gt;
&lt;import namespace="urn:iana:xml:ns:eppcom-1.0"/&gt;

&lt;annotation&gt;
  &lt;documentation&gt;
    Extensible Provisioning Protocol v1.0
    Bundle Domain Extension Schema v1.0
  &lt;/documentation&gt;
&lt;/annotation&gt;

&lt;!--
  Child elements found in EPP commands.
--&gt;
&lt;element name="create" type="b-dn:createDataType"/&gt;

&lt;!--
  Child elements of the &lt;b-dn:create&gt; command.
  All elements must be present at time of creation
--&gt;
&lt;complexType name="createDataType"&gt;
  &lt;sequence&gt;
    &lt;element name="rdn" type="b-dn:rdnType"
      minOccurs="0"/&gt;
  &lt;/sequence&gt;
&lt;/complexType&gt;

&lt;!--
  Child response elements in &lt;b-dn:infData&gt;, &lt;b-dn:delData&gt;,
  &lt;b-dn:creData&gt;, &lt;b-dn:renData&gt;, &lt;b-dn:trnData&gt; and &lt;b-dn:upData&gt;.
--&gt;
&lt;element name="infData" type="b-dn:bundleDataType"/&gt;
&lt;element name="delData" type="b-dn:bundleDataType"/&gt;
&lt;element name="creData" type="b-dn:bundleDataType"/&gt;
&lt;element name="renData" type="b-dn:bundleDataType"/&gt;
&lt;element name="trnData" type="b-dn:bundleDataType"/&gt;
&lt;element name="upData" type="b-dn:bundleDataType"/&gt;

&lt;complexType name="bundleDataType"&gt;
  &lt;sequence&gt;
    &lt;element name="bundle" type="b-dn:bundleType" /&gt;
  &lt;/sequence&gt;
&lt;/complexType&gt;

&lt;complexType name="bundleType"&gt;
  &lt;sequence&gt;
    &lt;element name="rdn" type="b-dn:rdnType" /&gt;
    &lt;element name="bdn" type="b-dn:rdnType"
      minOccurs="0" maxOccurs="unbounded" /&gt;
  &lt;/sequence&gt;
&lt;/complexType&gt;

&lt;complexType name="rdnType"&gt;
  &lt;simpleContent&gt;
    &lt;extension base="eppcom:labelType"&gt;
      &lt;attribute name="uLabel" type="eppcom:labelType"/&gt;
    &lt;/extension&gt;
  &lt;/simpleContent&gt;
&lt;/complexType&gt;

&lt;!--
  End of schema.
--&gt;
&lt;/schema&gt;

&lt;CODE ENDS&gt;</pre><a href="#section-7-2" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="Internationalization">
<section id="section-8">
      <h2 id="name-internationalization-consid">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-internationalization-consid" class="section-name selfRef">Internationalization Considerations</a>
      </h2>
<p id="section-8-1">
EPP is represented in XML, which provides 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 use of an "encoding" attribute in an &lt;?xml?&gt; declaration, use of UTF-8 is
recommended.<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">
As an extension of the EPP domain name mapping, the elements and element content described in this
document must inherit the internationalization conventions used to represent higher-layer domain
and core protocol structures present in an XML instance that includes this extension.<a href="#section-8-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Iana">
<section id="section-9">
      <h2 id="name-iana-considerations">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<div id="Iana1">
<section id="section-9.1">
        <h3 id="name-xml-namespace-and-xml-schem">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-xml-namespace-and-xml-schem" class="section-name selfRef">XML Namespace and XML Schema</a>
        </h3>
<p id="section-9.1-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>.<a href="#section-9.1-1" class="pilcrow">¶</a></p>
<div id="Iana11">
<section id="section-9.1.1">
          <h4 id="name-bdn-namespace">
<a href="#section-9.1.1" class="section-number selfRef">9.1.1. </a><a href="#name-bdn-namespace" class="section-name selfRef">BDN Namespace</a>
          </h4>
<p id="section-9.1.1-1">
   IANA has assigned the following for the BDN namespace in the "ns" subregistry of the "IETF XML Registry", with this document
   as the reference:<a href="#section-9.1.1-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-9.1.1-2">
            <dt id="section-9.1.1-2.1">
URI:</dt>
            <dd style="margin-left: 1.5em" id="section-9.1.1-2.2">urn:ietf:params:xml:ns:epp:b-dn<a href="#section-9.1.1-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-9.1.1-2.3">
Registrant Contact:</dt>
            <dd style="margin-left: 1.5em" id="section-9.1.1-2.4">See the "Authors' Addresses" section of this document.<a href="#section-9.1.1-2.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-9.1.1-2.5">
XML:</dt>
            <dd style="margin-left: 1.5em" id="section-9.1.1-2.6">None. The namespace URI does not represent an XML specification.<a href="#section-9.1.1-2.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</div>
<div id="Iana12">
<section id="section-9.1.2">
          <h4 id="name-bdn-xml-schema">
<a href="#section-9.1.2" class="section-number selfRef">9.1.2. </a><a href="#name-bdn-xml-schema" class="section-name selfRef">BDN XML Schema</a>
          </h4>
<p id="section-9.1.2-1">
   IANA has made the following  assignment in the "schema" subregistry of the "IETF XML Registry" for the BDN XML schema, with this
   document as the reference:<a href="#section-9.1.2-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-9.1.2-2">
            <dt id="section-9.1.2-2.1">
URI:</dt>
            <dd style="margin-left: 1.5em" id="section-9.1.2-2.2">urn:ietf:params:xml:schema:epp:b-dn<a href="#section-9.1.2-2.2" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-9.1.2-2.3">
Registrant Contact:</dt>
            <dd style="margin-left: 1.5em" id="section-9.1.2-2.4">See the "Authors' Addresses" section of this document.<a href="#section-9.1.2-2.4" class="pilcrow">¶</a>
</dd>
            <dd class="break"></dd>
<dt id="section-9.1.2-2.5">
XML:</dt>
            <dd style="margin-left: 1.5em" id="section-9.1.2-2.6">See the "<a href="#formal" class="xref">Formal Syntax</a>" section of this document.<a href="#section-9.1.2-2.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
</dl>
</section>
</div>
</section>
</div>
<div id="Iana2">
<section id="section-9.2">
        <h3 id="name-epp-extension">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-epp-extension" class="section-name selfRef">EPP Extension</a>
        </h3>
<p id="section-9.2-1"> 
   IANA has registered the EPP extension described in this document 
   in the "Extensions for the Extensible Provisioning Protocol
   (EPP)" registry described in <span>[<a href="#RFC7451" class="xref">RFC7451</a>]</span>.  The details of the
   registration are as follows:<a href="#section-9.2-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlParallel dlCompact" id="section-9.2-2">
          <dt id="section-9.2-2.1">
Name of Extension:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.2">"Domain Name Mapping Extension for Strict Bundling Registration"<a href="#section-9.2-2.2" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-9.2-2.3">
Document Status:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.4">Informational<a href="#section-9.2-2.4" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-9.2-2.5">
Reference:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.6">This document<a href="#section-9.2-2.6" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-9.2-2.7">
Registrant Name and Email Address:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.8"> See the "Authors' Addresses" section of this document.<a href="#section-9.2-2.8" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-9.2-2.9">
TLDs:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.10">Any<a href="#section-9.2-2.10" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-9.2-2.11">
IPR Disclosure:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.12">
            <span><a href="https://datatracker.ietf.org/ipr/2479">https://datatracker.ietf.org/ipr/2479</a></span><a href="#section-9.2-2.12" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-9.2-2.13">
Status:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.14">Active<a href="#section-9.2-2.14" class="pilcrow">¶</a>
</dd>
          <dd class="break"></dd>
<dt id="section-9.2-2.15">
Notes:</dt>
          <dd style="margin-left: 1.5em" id="section-9.2-2.16">None<a href="#section-9.2-2.16" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
</section>
</div>
<div id="security">
<section id="section-10">
      <h2 id="name-security-considerations">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-10-1">
   Normally, the EPP server will only be connected by the authorized EPP client,
   which knows whether the EPP server supports the extension described in this document via out-of-band service.
   The EPP client should avoid sending this extension to the unimplemented EPP server. In case a client that supports this document sends a request to a server that does not support this document, the server will return the result code 2103 according to <span><a href="https://www.rfc-editor.org/rfc/rfc5730#section-3" class="relref">Section 3</a> of [<a href="#RFC5730" class="xref">RFC5730</a>]</span>.
   
<span><a href="https://www.rfc-editor.org/rfc/rfc5730#section-3" class="relref">Section 3</a> of [<a href="#RFC5730" class="xref">RFC5730</a>]</span> has the following information for result code 2103.<a href="#section-10-1" class="pilcrow">¶</a></p>
<blockquote id="section-10-2">
        <p id="section-10-2.1"> 2103    "Unimplemented extension"<a href="#section-10-2.1" class="pilcrow">¶</a></p>
<p id="section-10-2.2">
              This response code <span class="bcp14">MUST</span> be returned when a server receives
              a valid EPP command element that contains a protocol
              command extension that is not implemented by the server.<a href="#section-10-2.2" class="pilcrow">¶</a></p>
</blockquote>
<p id="section-10-3">
  Some registries and registrars have more than 15 years' experience with the bundled registration of domain names (especially Chinese Domain Names).
  They have not found any significant security issues. One principle that
   the registry and registrar should let the registrants know is that 
   bundled registered domain names will be created, transferred, updated, and deleted together as a group.
   The registrants for bundled domain names should remember this principle when performing operations to these domain names. 

<span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span> also introduces some security consideration.<a href="#section-10-3" class="pilcrow">¶</a></p>
<p id="section-10-4"> This document 
does not take a position regarding whether or not the bundled domain names share a key for Delegation Signer (DS) and/or DNS Public Key (DNSKEY) resource records.
The DNS administrator can choose whether DS/DNSKEY information can be shared or not.
If a DS/DNSKEY key is shared, then the bundled domain names share fate if there is a key 
compromise.<a href="#section-10-4" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-11">
      <h2 id="name-references">
<a href="#section-11" class="section-number selfRef">11. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-11.1">
        <h3 id="name-normative-references">
<a href="#section-11.1" class="section-number selfRef">11.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<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="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="RFC5731">[RFC5731]</dt>
        <dd>
<span class="refAuthor">Hollenbeck, S.</span>, <span class="refTitle">"Extensible Provisioning Protocol (EPP) Domain Name Mapping"</span>, <span class="seriesInfo">STD 69</span>, <span class="seriesInfo">RFC 5731</span>, <span class="seriesInfo">DOI 10.17487/RFC5731</span>, <time datetime="2009-08" class="refDate">August 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5731">https://www.rfc-editor.org/info/rfc5731</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="RFC5891">[RFC5891]</dt>
        <dd>
<span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Internationalized Domain Names in Applications (IDNA): Protocol"</span>, <span class="seriesInfo">RFC 5891</span>, <span class="seriesInfo">DOI 10.17487/RFC5891</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5891">https://www.rfc-editor.org/info/rfc5891</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5892">[RFC5892]</dt>
        <dd>
<span class="refAuthor">Faltstrom, P., Ed.</span>, <span class="refTitle">"The Unicode Code Points and Internationalized Domain Names for Applications (IDNA)"</span>, <span class="seriesInfo">RFC 5892</span>, <span class="seriesInfo">DOI 10.17487/RFC5892</span>, <time datetime="2010-08" class="refDate">August 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5892">https://www.rfc-editor.org/info/rfc5892</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7451">[RFC7451]</dt>
        <dd>
<span class="refAuthor">Hollenbeck, S.</span>, <span class="refTitle">"Extension Registry for the Extensible Provisioning Protocol"</span>, <span class="seriesInfo">RFC 7451</span>, <span class="seriesInfo">DOI 10.17487/RFC7451</span>, <time datetime="2015-02" class="refDate">February 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7451">https://www.rfc-editor.org/info/rfc7451</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="W3C.REC-xml-20040204">[W3C.REC-xml-20040204]</dt>
        <dd>
<span class="refAuthor">Bray, T.</span>, <span class="refAuthor">Paoli, J.</span>, <span class="refAuthor">Sperberg-McQueen, C.M.</span>, <span class="refAuthor">Maler, E.</span>, and <span class="refAuthor">F. Yergeau</span>, <span class="refTitle">"Extensible Markup Language (XML) 1.0 (Third Edition)"</span>, <span class="refContent">W3C Recommendation REC-xml-20040204</span>, <time datetime="2004-02" class="refDate">February 2004</time>, <span>&lt;<a href="http://www.w3.org/TR/2004/REC-xml-20040204">http://www.w3.org/TR/2004/REC-xml-20040204</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.</span>, <span class="refAuthor">Beech, D.</span>, <span class="refAuthor">Maloney, M.</span>, and <span class="refAuthor">N. Mendelsohn</span>, <span class="refTitle">"XML Schema Part 1: Structures Second Edition"</span>, <span class="refContent">W3C Recommendation REC-xmlschema-1-20041028</span>, <time datetime="2004-10" class="refDate">October 2004</time>, <span>&lt;<a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028">http://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.</span> and <span class="refAuthor">A. Malhotra</span>, <span class="refTitle">"XML Schema Part 2: Datatypes Second Edition"</span>, <span class="refContent">W3C Recommendation REC-xmlschema-2-20041028</span>, <time datetime="2004-10" class="refDate">October 2004</time>, <span>&lt;<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-11.2">
        <h3 id="name-informative-references">
<a href="#section-11.2" class="section-number selfRef">11.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="RFC3743">[RFC3743]</dt>
        <dd>
<span class="refAuthor">Konishi, K.</span>, <span class="refAuthor">Huang, K.</span>, <span class="refAuthor">Qian, H.</span>, and <span class="refAuthor">Y. Ko</span>, <span class="refTitle">"Joint Engineering Team (JET) Guidelines for Internationalized Domain Names (IDN) Registration and Administration for Chinese, Japanese, and Korean"</span>, <span class="seriesInfo">RFC 3743</span>, <span class="seriesInfo">DOI 10.17487/RFC3743</span>, <time datetime="2004-04" class="refDate">April 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3743">https://www.rfc-editor.org/info/rfc3743</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC3915">[RFC3915]</dt>
        <dd>
<span class="refAuthor">Hollenbeck, S.</span>, <span class="refTitle">"Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)"</span>, <span class="seriesInfo">RFC 3915</span>, <span class="seriesInfo">DOI 10.17487/RFC3915</span>, <time datetime="2004-09" class="refDate">September 2004</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc3915">https://www.rfc-editor.org/info/rfc3915</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4290">[RFC4290]</dt>
      <dd>
<span class="refAuthor">Klensin, J.</span>, <span class="refTitle">"Suggested Practices for Registration of Internationalized Domain Names (IDN)"</span>, <span class="seriesInfo">RFC 4290</span>, <span class="seriesInfo">DOI 10.17487/RFC4290</span>, <time datetime="2005-12" class="refDate">December 2005</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4290">https://www.rfc-editor.org/info/rfc4290</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<div id="Acknowledgements">
<section id="appendix-A">
      <h2 id="name-acknowledgements">
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
      </h2>
<p id="appendix-A-1">
The authors especially thank the authors of <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span> and
<span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span> and the following members of the China Internet Network Information Center (CNNIC): <span class="contact-name">Weiping Yang</span>, <span class="contact-name">Chao Qi</span>.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
<p id="appendix-A-2">
Useful comments were made by <span class="contact-name">John Klensin</span>, <span class="contact-name">Scott Hollenbeck</span>,  <span class="contact-name">Patrick Mevzek</span>,  <span class="contact-name">Edward Lewis</span>, <span class="contact-name">Wil Tan</span>, and  <span class="contact-name">Adrian Farrel</span>.<a href="#appendix-A-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="appendix-B">
      <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">Jiankang Yao</span></div>
<div dir="auto" class="left"><span class="org">CNNIC</span></div>
<div dir="auto" class="left"><span class="street-address">4 South 4th Street, Zhongguancun, Haidian District</span></div>
<div dir="auto" class="left"><span class="locality">Beijing</span></div>
<div dir="auto" class="left">
<span class="region">Beijing</span>, <span class="postal-code">100190</span>
</div>
<div dir="auto" class="left"><span class="country-name">China</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+86%2010%205881%203007" class="tel">+86 10 5881 3007</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:yaojk@cnnic.cn" class="email">yaojk@cnnic.cn</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Linlin Zhou</span></div>
<div dir="auto" class="left"><span class="org">CNNIC</span></div>
<div dir="auto" class="left"><span class="street-address">4 South 4th Street, Zhongguancun, Haidian District</span></div>
<div dir="auto" class="left"><span class="locality">Beijing</span></div>
<div dir="auto" class="left">
<span class="region">Beijing</span>, <span class="postal-code">100190</span>
</div>
<div dir="auto" class="left"><span class="country-name">China</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+86%2010%205881%202677" class="tel">+86 10 5881 2677</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:zhoulinlin@cnnic.cn" class="email">zhoulinlin@cnnic.cn</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Hongtao Li</span></div>
<div dir="auto" class="left"><span class="org">CNNIC</span></div>
<div dir="auto" class="left"><span class="street-address">4 South 4th Street, Zhongguancun, Haidian District</span></div>
<div dir="auto" class="left"><span class="locality">Beijing</span></div>
<div dir="auto" class="left">
<span class="region">Beijing</span>, <span class="postal-code">100190</span>
</div>
<div dir="auto" class="left"><span class="country-name">China</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:lihongtao@cnnic.cn" class="email">lihongtao@cnnic.cn</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Ning Kong</span></div>
<div dir="auto" class="left"><span class="org">Consultant</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:ietfing@gmail.com" class="email">ietfing@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jiagui Xie</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:jiagui1984@163.com" class="email">jiagui1984@163.com</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>