File: rfc8748.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 (2987 lines) | stat: -rw-r--r-- 141,020 bytes
parent folder | download | duplicates (2)
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 8748: Registry Fee Extension for the Extensible Provisioning Protocol (EPP)</title>
<meta content="Roger Carney" name="author">
<meta content="Gavin Brown" name="author">
<meta content="Jothan Frakes" name="author">
<meta content="
       Given the expansion of the DNS namespace and the proliferation of 
      novel business models, it is desirable to provide a method for Extensible 
      Provisioning Protocol (EPP) clients to query EPP servers for the fees and 
      credits associated with various billable transactions and provide expected fees and credits for certain commands and 
      objects. This document describes an EPP extension mapping for registry fees.
       
    " name="description">
<meta content="xml2rfc 2.40.1" name="generator">
<meta content="8748" name="rfc.number">
<link href="rfc8748.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

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

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

*/

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

.refInstance {
  margin-bottom: 1.25em;
}

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

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

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

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

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

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

/* pagination */
@media print {
  body {

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

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

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

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

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

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

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

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

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

}

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


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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

}
/* Avoid wrapping of URLs in references */
@media screen {
  .references a {
    white-space: nowrap;
  }
}
/* 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: 0 0 0.25em 0;
  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;
  }
}
/*
  The margin-left: 0 on <dd> removes all distinction
  between levels from nested <dl>s.  Undo that.
*/
dl.olPercent > dd,
dd {
  margin-left: revert;
}
/* 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; }
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8748" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-regext-epp-fees-20" 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 8748</td>
<td class="center">Registry Fee Extension</td>
<td class="right">March 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Carney, et al.</td>
<td class="center">Standards Track</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Engineering Task Force (IETF)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8748" class="eref">8748</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Standards Track</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2020-03" class="published">March 2020</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">R. Carney</div>
<div class="org">GoDaddy Inc.</div>
</div>
<div class="author">
      <div class="author-name">G. Brown</div>
<div class="org">CentralNic Group plc</div>
</div>
<div class="author">
      <div class="author-name">J. Frakes</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8748</h1>
<h1 id="title">Registry Fee Extension for the Extensible Provisioning Protocol (EPP)</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">Given the expansion of the DNS namespace and the proliferation of 
      novel business models, it is desirable to provide a method for Extensible 
      Provisioning Protocol (EPP) clients to query EPP servers for the fees and 
      credits associated with various billable transactions and provide expected fees and credits for certain commands and 
      objects. This document describes an EPP extension mapping for registry fees.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in Section 2 of 
            RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <span><a href="https://www.rfc-editor.org/info/rfc8748">https://www.rfc-editor.org/info/rfc8748</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2020 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document. Code Components extracted from this
            document must include Simplified BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Simplified BSD License.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.1.2.1">
                <p id="section-toc.1-1.1.2.1.1"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-conventions-used-in-this-do" class="xref">Conventions Used in This Document</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><a href="#section-2" class="xref">2</a>.  <a href="#name-migrating-to-newer-versions" class="xref">Migrating to Newer Versions of This Extension</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-extension-elements" class="xref">Extension Elements</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.3.2.1">
                <p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-client-commands" class="xref">Client Commands</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.2">
                <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-currency-codes" class="xref">Currency Codes</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.3">
                <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-validity-periods" class="xref">Validity Periods</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.4">
                <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-fees-and-credits" class="xref">Fees and Credits</a><a href="#section-toc.1-1.3.2.4.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.3.2.4.2.1">
                    <p id="section-toc.1-1.3.2.4.2.1.1"><a href="#section-3.4.1" class="xref">3.4.1</a>.  <a href="#name-refunds" class="xref">Refunds</a><a href="#section-toc.1-1.3.2.4.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.4.2.2">
                    <p id="section-toc.1-1.3.2.4.2.2.1"><a href="#section-3.4.2" class="xref">3.4.2</a>.  <a href="#name-grace-periods" class="xref">Grace Periods</a><a href="#section-toc.1-1.3.2.4.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.4.2.3">
                    <p id="section-toc.1-1.3.2.4.2.3.1"><a href="#section-3.4.3" class="xref">3.4.3</a>.  <a href="#name-correlation-between-refunda" class="xref">Correlation between Refundability and Grace Periods</a><a href="#section-toc.1-1.3.2.4.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.4.2.4">
                    <p id="section-toc.1-1.3.2.4.2.4.1"><a href="#section-3.4.4" class="xref">3.4.4</a>.  <a href="#name-applicability" class="xref">Applicability</a><a href="#section-toc.1-1.3.2.4.2.4.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.5">
                <p id="section-toc.1-1.3.2.5.1"><a href="#section-3.5" class="xref">3.5</a>.  <a href="#name-account-balance" class="xref">Account Balance</a><a href="#section-toc.1-1.3.2.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.6">
                <p id="section-toc.1-1.3.2.6.1"><a href="#section-3.6" class="xref">3.6</a>.  <a href="#name-credit-limit" class="xref">Credit Limit</a><a href="#section-toc.1-1.3.2.6.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.7">
                <p id="section-toc.1-1.3.2.7.1"><a href="#section-3.7" class="xref">3.7</a>.  <a href="#name-classification-of-objects" class="xref">Classification of Objects</a><a href="#section-toc.1-1.3.2.7.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.8">
                <p id="section-toc.1-1.3.2.8.1"><a href="#section-3.8" class="xref">3.8</a>.  <a href="#name-phase-and-subphase-attribut" class="xref">"Phase" and "Subphase" Attributes</a><a href="#section-toc.1-1.3.2.8.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.9">
                <p id="section-toc.1-1.3.2.9.1"><a href="#section-3.9" class="xref">3.9</a>.  <a href="#name-reason" class="xref">Reason</a><a href="#section-toc.1-1.3.2.9.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-server-handling-of-fee-info" class="xref">Server Handling of Fee Information</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-epp-command-mapping" class="xref">EPP Command Mapping</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.5.2.1">
                <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-epp-query-commands" class="xref">EPP Query Commands</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.5.2.1.2.1">
                    <p id="section-toc.1-1.5.2.1.2.1.1"><a href="#section-5.1.1" class="xref">5.1.1</a>.  <a href="#name-epp-check-command" class="xref">EPP &lt;check&gt; Command</a><a href="#section-toc.1-1.5.2.1.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.1.2.2">
                    <p id="section-toc.1-1.5.2.1.2.2.1"><a href="#section-5.1.2" class="xref">5.1.2</a>.  <a href="#name-epp-transfer-query-command" class="xref">EPP Transfer Query Command</a><a href="#section-toc.1-1.5.2.1.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2">
                <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-epp-transform-commands" class="xref">EPP Transform Commands</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2.2.1">
                    <p id="section-toc.1-1.5.2.2.2.1.1"><a href="#section-5.2.1" class="xref">5.2.1</a>.  <a href="#name-epp-create-command" class="xref">EPP &lt;create&gt; Command</a><a href="#section-toc.1-1.5.2.2.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2.2.2">
                    <p id="section-toc.1-1.5.2.2.2.2.1"><a href="#section-5.2.2" class="xref">5.2.2</a>.  <a href="#name-epp-delete-command" class="xref">EPP &lt;delete&gt; Command</a><a href="#section-toc.1-1.5.2.2.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2.2.3">
                    <p id="section-toc.1-1.5.2.2.2.3.1"><a href="#section-5.2.3" class="xref">5.2.3</a>.  <a href="#name-epp-renew-command" class="xref">EPP &lt;renew&gt; Command</a><a href="#section-toc.1-1.5.2.2.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2.2.4">
                    <p id="section-toc.1-1.5.2.2.2.4.1"><a href="#section-5.2.4" class="xref">5.2.4</a>.  <a href="#name-epp-transfer-command" class="xref">EPP &lt;transfer&gt; Command</a><a href="#section-toc.1-1.5.2.2.2.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.5.2.2.2.5">
                    <p id="section-toc.1-1.5.2.2.2.5.1"><a href="#section-5.2.5" class="xref">5.2.5</a>.  <a href="#name-epp-update-command" class="xref">EPP &lt;update&gt; Command</a><a href="#section-toc.1-1.5.2.2.2.5.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-formal-syntax" class="xref">Formal Syntax</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" 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-fee-extension-schema" class="xref">Fee Extension Schema</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.8.2.1">
                <p id="section-toc.1-1.8.2.1.1"><a href="#section-8.1" class="xref">8.1</a>.  <a href="#name-xml-namespace" class="xref">XML Namespace</a><a href="#section-toc.1-1.8.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.8.2.2">
                <p id="section-toc.1-1.8.2.2.1"><a href="#section-8.2" class="xref">8.2</a>.  <a href="#name-epp-extension-registry" class="xref">EPP Extension Registry</a><a href="#section-toc.1-1.8.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-references" class="xref">References</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" 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-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" 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-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-appendix.a" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
</li>
</ul>
</nav>
</section>
</div>
<div id="intro">
<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">Historically, domain name registries have applied a simple fee
      structure for billable transactions, namely a basic unit price applied to
      domain &lt;create&gt;, &lt;renew&gt;, &lt;transfer&gt;, and Redemption
      Grace Period (RGP) <span>[<a href="#RFC3915" class="xref">RFC3915</a>]</span>
      restore commands. Given the relatively small number of EPP servers to
      which EPP clients have been required to connect, it has generally been the
      case that client operators have been able to obtain details of these fees
      out of band by contacting the server operators.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">Given the expansion of the DNS namespace and the proliferation
      of novel business models, it is desirable to provide a method for EPP
      clients to query EPP servers for the fees and credits associated with
      various billable transactions and certain commands and specific objects.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">This document describes an extension mapping for version 1.0 of the
      Extensible Provisioning Protocol (EPP) <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.  This EPP mapping
      provides a mechanism by which EPP clients may query the fees and credits
      associated with various billable transactions and obtain their
      current account balance.<a href="#section-1-3" class="pilcrow">¶</a></p>
<div id="conventions">
<section id="section-1.1">
        <h3 id="name-conventions-used-in-this-do">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-conventions-used-in-this-do" class="section-name selfRef">Conventions Used in This Document</a>
        </h3>
<p id="section-1.1-1">
    The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>",
        "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and
        "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as
    described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> 
    when, and only when, they appear in all capitals, as shown here.<a href="#section-1.1-1" class="pilcrow">¶</a></p>
<p id="section-1.1-2">XML is case sensitive. Unless stated otherwise, the XML specifications
        and examples provided in this document <span class="bcp14">MUST</span> be interpreted in the
        character case presented in order to develop a conforming
        implementation.<a href="#section-1.1-2" class="pilcrow">¶</a></p>
<p id="section-1.1-3">"fee" is used as an abbreviation for "urn:ietf:params:xml:ns:epp:fee-1.0".
        The XML namespace prefix "fee" is used, but implementations <span class="bcp14">MUST NOT</span>
        depend on it and instead employ a proper namespace-aware XML parser and
        serializer to interpret and output the XML documents.<a href="#section-1.1-3" class="pilcrow">¶</a></p>
<p id="section-1.1-4">In the examples, "C:" represents lines sent by a protocol client, and "S:"
        represents lines returned by a protocol server.  Indentation and white
        space in the examples are provided only to illustrate element relationships
        and are not a required feature of this protocol.<a href="#section-1.1-4" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="migrating">
<section id="section-2">
      <h2 id="name-migrating-to-newer-versions">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-migrating-to-newer-versions" class="section-name selfRef">Migrating to Newer Versions of This Extension</a>
      </h2>
<p id="section-2-1">Servers that implement this extension <span class="bcp14">SHOULD</span> provide a way for clients
      to progressively update their implementations when a new version of the
      extension is deployed.<a href="#section-2-1" class="pilcrow">¶</a></p>
<p id="section-2-2">Servers <span class="bcp14">SHOULD</span> (for a temporary migration period) provide support for
      older versions of the extension in parallel to the newest version and
      allow clients to select their preferred version via the &lt;svcExtension&gt;
      element of the &lt;login&gt; command.<a href="#section-2-2" class="pilcrow">¶</a></p>
<p id="section-2-3">If a client requests multiple versions of the extension at login, then,
      when preparing responses to commands that do not include extension
      elements, the server <span class="bcp14">SHOULD</span> only include extension elements in the
      namespace of the newest version of the extension requested by the client.<a href="#section-2-3" class="pilcrow">¶</a></p>
<p id="section-2-4">When preparing responses to commands that do include extension
      elements, the server <span class="bcp14">SHOULD</span> only include extension elements for the
      extension versions present in the command.<a href="#section-2-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="extension-elements">
<section id="section-3">
      <h2 id="name-extension-elements">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-extension-elements" class="section-name selfRef">Extension Elements</a>
      </h2>
<div id="client-commands">
<section id="section-3.1">
        <h3 id="name-client-commands">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-client-commands" class="section-name selfRef">Client Commands</a>
        </h3>
<p id="section-3.1-1">The &lt;fee:command&gt; element is used in the EPP &lt;check&gt;
        command to determine the fee that is applicable to the given
 command.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
<p id="section-3.1-2">The "name" attribute of the &lt;fee:command&gt; is used to define which transform fees the client is requesting
        information about. The possible values for the "name"
        attribute are:<a href="#section-3.1-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-3.1-3.1">"create", indicating a &lt;create&gt; command as defined in <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.<a href="#section-3.1-3.1" class="pilcrow">¶</a>
</li>
<li id="section-3.1-3.2">"delete", indicating a &lt;delete&gt; command as defined in <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.<a href="#section-3.1-3.2" class="pilcrow">¶</a>
</li>
<li id="section-3.1-3.3">"renew", indicating a &lt;renew&gt; command as defined in <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.<a href="#section-3.1-3.3" class="pilcrow">¶</a>
</li>
<li id="section-3.1-3.4">"update", indicating a &lt;update&gt; command as defined in <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.<a href="#section-3.1-3.4" class="pilcrow">¶</a>
</li>
<li id="section-3.1-3.5">"transfer", indicating a &lt;transfer&gt; command as defined in
   <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.<a href="#section-3.1-3.5" class="pilcrow">¶</a>
</li>
<li id="section-3.1-3.6">If the server supports registry grace period mapping <span>[<a href="#RFC3915" class="xref">RFC3915</a>]</span>,
          then the server <span class="bcp14">MUST</span> also support the "restore" value as defined in
          <span>[<a href="#RFC3915" class="xref">RFC3915</a>]</span>.<a href="#section-3.1-3.6" class="pilcrow">¶</a>
</li>
<li id="section-3.1-3.7">"custom", indicating a custom command that <span class="bcp14">MUST</span> set the "customName"
          attribute with a custom command name. The possible set of custom command 
          name values is dictated by the server policy.<a href="#section-3.1-3.7" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-3.1-4">The &lt;fee:command&gt; element <span class="bcp14">MAY</span> have an <span class="bcp14">OPTIONAL</span> "phase"
        attribute specifying a launch phase as described in
        <span>[<a href="#RFC8334" class="xref">RFC8334</a>]</span>.  It may also contain an <span class="bcp14">OPTIONAL</span>
        "subphase" attribute identifying the custom or subphase as described in
        <span>[<a href="#RFC8334" class="xref">RFC8334</a>]</span>.<a href="#section-3.1-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="currency-codes">
<section id="section-3.2">
        <h3 id="name-currency-codes">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-currency-codes" class="section-name selfRef">Currency Codes</a>
        </h3>
<p id="section-3.2-1">The &lt;fee:currency&gt; element is used to indicate the currency
 in which fees are charged.  The value of this element <span class="bcp14">MUST</span> be a
        three-character currency code from <span>[<a href="#ISO4217_2015" class="xref">ISO4217_2015</a>]</span>.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<p id="section-3.2-2">Note that <span>[<a href="#ISO4217_2015" class="xref">ISO4217_2015</a>]</span> provides the special "XXX" code, which <span class="bcp14">MAY</span> be used
        if the server uses a non-currency-based system for assessing fees, such
        as a system of credits.<a href="#section-3.2-2" class="pilcrow">¶</a></p>
<p id="section-3.2-3">The use of &lt;fee:currency&gt; elements in client commands is <span class="bcp14">OPTIONAL</span>: if
        a &lt;fee:currency&gt; element is not present in a command, the server
        <span class="bcp14">MUST</span> determine the currency based on the server default currency or on the client's account settings, which are agreed to by the client 
        and server via an out-of-band channel. However, the
 &lt;fee:currency&gt; element <span class="bcp14">MUST</span> be present in the responses.<a href="#section-3.2-3" class="pilcrow">¶</a></p>
<p id="section-3.2-4">Servers <span class="bcp14">SHOULD NOT</span> perform a currency conversion if a client uses an
        incorrect currency code.  Servers <span class="bcp14">SHOULD</span> return a 2004 "Parameter value
        range error" instead.<a href="#section-3.2-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="validity-periods">
<section id="section-3.3">
        <h3 id="name-validity-periods">
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-validity-periods" class="section-name selfRef">Validity Periods</a>
        </h3>
<p id="section-3.3-1">When querying for fee information using the &lt;check&gt; command,
        the &lt;fee:period&gt; element is used to indicate the validity
 period, which is to be added to extend the registration period of
 objects by the &lt;create&gt;, &lt;renew&gt;, and &lt;transfer&gt;
 commands. Validity periods are measured in years or months, with the
 appropriate units specified using the "unit" attribute. Valid values
 for the "unit" attribute are "y" for years and "m" for months. 

This element is derived from the &lt;domain:period&gt; element described in 
        <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
<p id="section-3.3-2">The &lt;fee:period&gt; element is <span class="bcp14">OPTIONAL</span> in &lt;check&gt; commands;
        if omitted, the server <span class="bcp14">MUST</span> determine the fee(s) using the server
        default period.  The &lt;fee:period&gt; element <span class="bcp14">MUST</span> be present in
        &lt;check&gt; responses.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="fees-credits">
<section id="section-3.4">
        <h3 id="name-fees-and-credits">
<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-fees-and-credits" class="section-name selfRef">Fees and Credits</a>
        </h3>
<p id="section-3.4-1">Servers that implement this extension will include elements in
        responses that provide information about the fees and/or credits
        associated with a given billable transaction. A fee will result in 
        subtracting from the Account Balance (described in <a href="#account-balance" class="xref">Section 3.5</a>), and a 
        credit will result in adding to the Account Balance (described in <a href="#account-balance" class="xref">Section 3.5</a>).<a href="#section-3.4-1" class="pilcrow">¶</a></p>
<p id="section-3.4-2">The &lt;fee:fee&gt; and &lt;fee:credit&gt; elements are used to
        provide this information.  The presence of a &lt;fee:fee&gt; element in
        a response indicates a debit against the client's account balance; a
        &lt;fee:credit&gt; element indicates a credit.  A &lt;fee:fee&gt;
        element <span class="bcp14">MUST</span> have a zero or greater (non-negative) value.  A &lt;fee:credit&gt; element 
        <span class="bcp14">MUST</span> have a negative value.<a href="#section-3.4-2" class="pilcrow">¶</a></p>
<p id="section-3.4-3">A server <span class="bcp14">MAY</span> respond with multiple &lt;fee:fee&gt; and &lt;fee:credit&gt;
        elements in the same response.  In such cases, the net fee or credit
        applicable to the transaction is the arithmetic sum of the values of
        each of the &lt;fee:fee&gt; and/or &lt;fee:credit&gt; elements.  This
        amount applies to the total additional validity period for the
        object (where applicable).<a href="#section-3.4-3" class="pilcrow">¶</a></p>
<p id="section-3.4-4">The following attributes are defined for the &lt;fee:fee&gt; element.
        These are described in detail below:<a href="#section-3.4-4" class="pilcrow">¶</a></p>
<dl class="dlParallel" id="section-3.4-5">
          <dt id="section-3.4-5.1">description:</dt>
<dd id="section-3.4-5.2">an <span class="bcp14">OPTIONAL</span> attribute that provides a human-readable
        description of the fee.  Servers should provide documentation on the
        possible values of this attribute and their meanings. An <span class="bcp14">OPTIONAL</span> 
        "lang" attribute <span class="bcp14">MAY</span> be present, per the language structure in <span>[<a href="#RFC5646" class="xref">RFC5646</a>]</span>, 
        to identify the language of the returned text and has a default value 
        of "en" (English). If the "description" attribute is not present, the 
        "lang" attribute can be ignored.<a href="#section-3.4-5.2" class="pilcrow">¶</a>
</dd>
<dt id="section-3.4-5.3">refundable:</dt>
<dd id="section-3.4-5.4">an <span class="bcp14">OPTIONAL</span> boolean attribute indicating whether the fee
        is refundable if the object is deleted.<a href="#section-3.4-5.4" class="pilcrow">¶</a>
</dd>
<dt id="section-3.4-5.5">grace-period:</dt>
<dd id="section-3.4-5.6">an <span class="bcp14">OPTIONAL</span> attribute that provides the time period
        during which the fee is refundable.<a href="#section-3.4-5.6" class="pilcrow">¶</a>
</dd>
<dt id="section-3.4-5.7">applied:</dt>
<dd id="section-3.4-5.8">an <span class="bcp14">OPTIONAL</span> attribute indicating when the fee will be
        deducted from the client's account.<a href="#section-3.4-5.8" class="pilcrow">¶</a>
</dd>
</dl>
<p id="section-3.4-6">The &lt;fee:credit&gt; element can take a "description" attribute as
          described above.  An <span class="bcp14">OPTIONAL</span> "lang" attribute <span class="bcp14">MAY</span> be present to 
          identify the language of the returned text and has a default value of 
          "en" (English).<a href="#section-3.4-6" class="pilcrow">¶</a></p>
<div id="refunds">
<section id="section-3.4.1">
          <h4 id="name-refunds">
<a href="#section-3.4.1" class="section-number selfRef">3.4.1. </a><a href="#name-refunds" class="section-name selfRef">Refunds</a>
          </h4>
<p id="section-3.4.1-1">&lt;fee:fee&gt; elements <span class="bcp14">MAY</span> have an <span class="bcp14">OPTIONAL</span> "refundable"
          attribute that takes a boolean value.  Fees may be refunded under
          certain circumstances, such as when a domain application is rejected
          (as described in <span>[<a href="#RFC8334" class="xref">RFC8334</a>]</span>) or when an object is
          deleted during the relevant grace period (see <a href="#grace-periods" class="xref">Section 3.4.2</a>).<a href="#section-3.4.1-1" class="pilcrow">¶</a></p>
<p id="section-3.4.1-2">If the "refundable" attribute is omitted, then clients <span class="bcp14">SHOULD NOT</span>
          make any assumptions about the refundability of the fee.<a href="#section-3.4.1-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="grace-periods">
<section id="section-3.4.2">
          <h4 id="name-grace-periods">
<a href="#section-3.4.2" class="section-number selfRef">3.4.2. </a><a href="#name-grace-periods" class="section-name selfRef">Grace Periods</a>
          </h4>
<p id="section-3.4.2-1"><span>[<a href="#RFC3915" class="xref">RFC3915</a>]</span> describes a system of "grace periods", which are time
          periods following a billable transaction during which, if an object is
          deleted, the client receives a refund.<a href="#section-3.4.2-1" class="pilcrow">¶</a></p>
<p id="section-3.4.2-2">The "grace-period" attribute <span class="bcp14">MAY</span> be used to indicate the relevant
          grace period for a fee.  If a server implements the registry grace
          period extension <span>[<a href="#RFC3915" class="xref">RFC3915</a>]</span>, it <span class="bcp14">MUST</span> specify the grace period for all 
          relevant transactions.<a href="#section-3.4.2-2" class="pilcrow">¶</a></p>
<p id="section-3.4.2-3">If the "grace-period" attribute is omitted, then clients <span class="bcp14">SHOULD NOT</span>
          make any assumptions about the grace period of the fee.<a href="#section-3.4.2-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="correlation-refund-grace">
<section id="section-3.4.3">
          <h4 id="name-correlation-between-refunda">
<a href="#section-3.4.3" class="section-number selfRef">3.4.3. </a><a href="#name-correlation-between-refunda" class="section-name selfRef">Correlation between Refundability and Grace Periods</a>
          </h4>
<p id="section-3.4.3-1">If a &lt;fee:fee&gt; element has a "grace-period" attribute, then it
          <span class="bcp14">MUST</span> also be refundable, and the "refundable" attribute <span class="bcp14">MUST</span> be true.  
          If the "refundable" attribute of a &lt;fee:fee&gt; element is false, 
          then it <span class="bcp14">MUST NOT</span> have a "grace-period" attribute.<a href="#section-3.4.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="applicability">
<section id="section-3.4.4">
          <h4 id="name-applicability">
<a href="#section-3.4.4" class="section-number selfRef">3.4.4. </a><a href="#name-applicability" class="section-name selfRef">Applicability</a>
          </h4>
<p id="section-3.4.4-1">Fees may be applied immediately upon receipt of a command from a
          client or may only be applied once an out-of-band process (such as
          the processing of applications at the end of a launch phase) has taken
          place.<a href="#section-3.4.4-1" class="pilcrow">¶</a></p>
<p id="section-3.4.4-2">The "applied" attribute of the &lt;fee:fee&gt; element allows
          servers to indicate whether a fee will be applied immediately or
          whether it will be applied at some point in the future.  This
          attribute takes two possible values: "immediate" or "delayed".<a href="#section-3.4.4-2" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="account-balance">
<section id="section-3.5">
        <h3 id="name-account-balance">
<a href="#section-3.5" class="section-number selfRef">3.5. </a><a href="#name-account-balance" class="section-name selfRef">Account Balance</a>
        </h3>
<p id="section-3.5-1">The &lt;fee:balance&gt; element is an <span class="bcp14">OPTIONAL</span> element that <span class="bcp14">MAY</span> be
        included in server responses to transform commands.  If present, it can
        be used by the client to determine the remaining credit at the server.<a href="#section-3.5-1" class="pilcrow">¶</a></p>
<p id="section-3.5-2">Whether or not the &lt;fee:balance&gt; is included in responses is a
        matter of server policy.  However, if a server chooses to offer support
        for this element, it <span class="bcp14">MUST</span> be included in responses to all "transform" or
        billable commands (e.g., &lt;create&gt;, &lt;renew&gt;, &lt;update&gt;,
        &lt;delete&gt;, &lt;transfer op="request"&gt;).<a href="#section-3.5-2" class="pilcrow">¶</a></p>
<p id="section-3.5-3">The value of the &lt;fee:balance&gt; <span class="bcp14">MAY</span> be negative.  A negative
        balance indicates that the server has extended a line of credit to the
        client (see <a href="#credit-limit" class="xref">Section 3.6</a>).<a href="#section-3.5-3" class="pilcrow">¶</a></p>
<p id="section-3.5-4">If a server includes a &lt;fee:balance&gt; element in response to
        transform commands, the value of the element <span class="bcp14">MUST</span> reflect the client's
        account balance after any fees or credits associated with that command
        have been applied. If the "applied" attribute of the &lt;fee:fee&gt; element 
        is "delayed", then the &lt;fee:balance&gt; <span class="bcp14">MUST</span> reflect the client's account 
        balance without any fees or credits associated with that command.<a href="#section-3.5-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="credit-limit">
<section id="section-3.6">
        <h3 id="name-credit-limit">
<a href="#section-3.6" class="section-number selfRef">3.6. </a><a href="#name-credit-limit" class="section-name selfRef">Credit Limit</a>
        </h3>
<p id="section-3.6-1">As described above, if a server returns a response containing a
        &lt;fee:balance&gt; with a negative value, then the server has extended
        a line of credit to the client.  A server <span class="bcp14">MAY</span> also
 include in responses a
        &lt;fee:creditLimit&gt; element that indicates the maximum
        credit available to a client.  A server <span class="bcp14">MAY</span> reject certain transactions
        if the absolute value of the &lt;fee:balance&gt; is equal to or exceeds the
        value of the &lt;fee:creditLimit&gt; element.<a href="#section-3.6-1" class="pilcrow">¶</a></p>
<p id="section-3.6-2">Whether or not the &lt;fee:creditLimit&gt; is included in responses
        is a matter of server policy.  However, if a server chooses to offer
        support for this element, it <span class="bcp14">MUST</span> be included in responses to all
        "transform" commands (e.g., &lt;create&gt;, &lt;renew&gt;, &lt;update&gt;,
        &lt;delete&gt;, &lt;transfer op="request"&gt;).<a href="#section-3.6-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="classification-objects">
<section id="section-3.7">
        <h3 id="name-classification-of-objects">
<a href="#section-3.7" class="section-number selfRef">3.7. </a><a href="#name-classification-of-objects" class="section-name selfRef">Classification of Objects</a>
        </h3>
<p id="section-3.7-1">Objects may be assigned to a particular class, category, or tier,
        each of which has a particular fee or set of fees associated with it.
        The &lt;fee:class&gt; element, which <span class="bcp14">MAY</span> appear in &lt;check&gt; and
        transform responses, is used to indicate the classification of an object.<a href="#section-3.7-1" class="pilcrow">¶</a></p>
<p id="section-3.7-2">If a server makes use of this element, it should provide clients with
        a list of all the values that the element may take via an out-of-band
        channel.  Servers <span class="bcp14">MUST NOT</span> use values that do not appear on this list.<a href="#section-3.7-2" class="pilcrow">¶</a></p>
<p id="section-3.7-3">Servers that make use of this element <span class="bcp14">MUST</span> use a &lt;fee:class&gt;
        element with the value "standard" for all objects that are subject to
        the standard or default fee.<a href="#section-3.7-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="phase-subphase">
<section id="section-3.8">
        <h3 id="name-phase-and-subphase-attribut">
<a href="#section-3.8" class="section-number selfRef">3.8. </a><a href="#name-phase-and-subphase-attribut" class="section-name selfRef">"Phase" and "Subphase" Attributes</a>
        </h3>
<p id="section-3.8-1">The &lt;fee:command&gt; element has two attributes, "phase" and
        "subphase", that provide additional information related to a specific
        launch phase, as described in <span>[<a href="#RFC8334" class="xref">RFC8334</a>]</span>. These
        attributes are used as filters that should refine the server processing.<a href="#section-3.8-1" class="pilcrow">¶</a></p>
<p id="section-3.8-2">If the client &lt;fee:command&gt; contains a server-supported
        combination of phase/subphase, the server <span class="bcp14">MUST</span> return
 the fee data (including
        the phase/subphase attribute(s)) for the specific combination.<a href="#section-3.8-2" class="pilcrow">¶</a></p>
<p id="section-3.8-3">If the client &lt;fee:command&gt; contains no "phase"/"subphase"
        attributes and the server has only one active phase/subphase combination,
        the server <span class="bcp14">MUST</span> return the data (including the "phase"/"subphase" attribute(s))
        of the currently active phase/subphase.<a href="#section-3.8-3" class="pilcrow">¶</a></p>
<p id="section-3.8-4">If the client &lt;fee:command&gt; contains no phase/subphase
        attributes and the server has more than one active phase/subphase
        combination, the server <span class="bcp14">MUST</span> respond with a 2003 "Required
        parameter missing" error.<a href="#section-3.8-4" class="pilcrow">¶</a></p>
<p id="section-3.8-5">If the client &lt;fee:command&gt; contains no phase/subphase
        attributes and the server is currently in a "quiet period" (e.g., not
        accepting registrations or applications), the server <span class="bcp14">MUST</span> return data
        consistent with the default general availability phase (e.g., "open" or
        "claims"), including the appropriate phase/subphase attribute(s).<a href="#section-3.8-5" class="pilcrow">¶</a></p>
<p id="section-3.8-6">If the client &lt;fee:command&gt; contains a phase attribute with no
        subphase and the server has only one active subphase (or no subphase) of
        this phase, the server <span class="bcp14">MUST</span> return the data (including the phase/subphase
        attribute(s)) of the provided phase and currently active subphase.<a href="#section-3.8-6" class="pilcrow">¶</a></p>
<p id="section-3.8-7">If the client &lt;fee:command&gt; contains a phase attribute with no
        subphase and the server has more than one active subphase combination of
        this phase, the server <span class="bcp14">MUST</span> respond with a 2003 "Required parameter
        missing" error.<a href="#section-3.8-7" class="pilcrow">¶</a></p>
<p id="section-3.8-8">If the client &lt;fee:command&gt; contains a subphase with no phase
        attribute, the server <span class="bcp14">MUST</span> respond with a 2003 "Required parameter
        missing" error.<a href="#section-3.8-8" class="pilcrow">¶</a></p>
<p id="section-3.8-9">If the client &lt;fee:command&gt; contains a phase attribute not
        defined in <span>[<a href="#RFC8334" class="xref">RFC8334</a>]</span> or not supported
 by the server,
        the server <span class="bcp14">MUST</span> respond with a 2004 "Parameter value range error".<a href="#section-3.8-9" class="pilcrow">¶</a></p>
<p id="section-3.8-10">If the client &lt;fee:command&gt; contains a subphase attribute (or
        phase/subphase combination) not supported by the server, the server <span class="bcp14">MUST</span>
        respond with a 2004 "Parameter value range error".<a href="#section-3.8-10" class="pilcrow">¶</a></p>
</section>
</div>
<div id="reason">
<section id="section-3.9">
        <h3 id="name-reason">
<a href="#section-3.9" class="section-number selfRef">3.9. </a><a href="#name-reason" class="section-name selfRef">Reason</a>
        </h3>
<p id="section-3.9-1">The &lt;fee:reason&gt; element is used to provide server-specific
        text in an effort to better explain why a &lt;check&gt; command did not
        complete as the client expected. An <span class="bcp14">OPTIONAL</span> "lang" attribute <span class="bcp14">MAY</span> be
        present to identify the language, per the language structure in 
        <span>[<a href="#RFC5646" class="xref">RFC5646</a>]</span>, of the returned text and has a default value of "en" (English).<a href="#section-3.9-1" class="pilcrow">¶</a></p>
<p id="section-3.9-2">The &lt;fee:reason&gt; element can be used within the server response
        &lt;fee:command&gt; element or within the &lt;fee:cd&gt; element. See 
        <a href="#epp-check" class="xref">Section 5.1.1</a> for details on the &lt;fee:cd&gt; "check data" element.<a href="#section-3.9-2" class="pilcrow">¶</a></p>
<p id="section-3.9-3">If the server cannot calculate the relevant fees because the object,
        command, currency, period, class, or some combination is invalid per
        server policy, the server has two ways of handling the error processing of
        &lt;fee:command&gt; element(s):<a href="#section-3.9-3" class="pilcrow">¶</a></p>
<ol start="1" type="1" class="normal type-1" id="section-3.9-4">
          <li id="section-3.9-4.1">
            <p id="section-3.9-4.1.1">Fast-fail: The server, upon error identification, <span class="bcp14">MAY</span> stop
          processing &lt;fee:command&gt; elements and return a
          &lt;fee:cd&gt; to the client containing the &lt;fee:objID&gt; and a
          &lt;fee:reason&gt; element detailing the reason for failure.<a href="#section-3.9-4.1.1" class="pilcrow">¶</a></p>
<div id="section-3.9-4.1.2">
<pre class="sourcecode">    S: &lt;fee:cd avail="0"&gt;
    S:   &lt;fee:objID&gt;example.xyz&lt;/fee:objID&gt;
    S:   &lt;fee:reason&gt;Only 1 year registration periods are
    S:   valid.&lt;/fee:reason&gt;
    S: &lt;/fee:cd&gt;
</pre><a href="#section-3.9-4.1.2" class="pilcrow">¶</a>
</div>
</li>
<li id="section-3.9-4.2">
            <p id="section-3.9-4.2.1">Partial-fail: The server, upon error identification, <span class="bcp14">MAY</span> continue
          processing &lt;fee:command&gt; elements and return a
          &lt;fee:cd&gt; to the client containing the successfully processed &lt;fee:command&gt;
          elements and failed &lt;fee:command&gt; elements. All returned failed
          &lt;fee:command&gt; elements <span class="bcp14">MUST</span> have a &lt;fee:reason&gt;
          element detailing the reason for failure, and the server <span class="bcp14">MAY</span>
          additionally include a &lt;fee:reason&gt; element at the
          &lt;fee:cd&gt; level.<a href="#section-3.9-4.2.1" class="pilcrow">¶</a></p>
<div id="section-3.9-4.2.2">
<pre class="sourcecode">    S: &lt;fee:cd avail="0"&gt;
    S:   &lt;fee:objID&gt;example.xyz&lt;/fee:objID&gt;
    S:   &lt;fee:command name="create"&gt;
    S:     &lt;fee:period unit="y"&gt;2&lt;/fee:period&gt;
    S:     &lt;fee:reason&gt;Only 1 year registration periods are
    S:     valid.&lt;/fee:reason&gt;
    S:   &lt;/fee:command&gt;
    S: &lt;/fee:cd&gt;
</pre><a href="#section-3.9-4.2.2" class="pilcrow">¶</a>
</div>
</li>
</ol>
<p id="section-3.9-5">In either failure scenario, the server <span class="bcp14">MUST</span> set the &lt;fee:cd&gt;
        "avail" attribute to false (0), and the server <span class="bcp14">MUST</span> process all objects in 
        the client request.<a href="#section-3.9-5" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="server-handling">
<section id="section-4">
      <h2 id="name-server-handling-of-fee-info">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-server-handling-of-fee-info" class="section-name selfRef">Server Handling of Fee Information</a>
      </h2>
<p id="section-4-1">Depending on the server policy, a client <span class="bcp14">MAY</span> be required to include the
      extension elements described in this document for certain transform
      commands.  Servers must provide clear documentation to clients about the
      circumstances in which this extension must be used.<a href="#section-4-1" class="pilcrow">¶</a></p>
<p id="section-4-2">The server <span class="bcp14">MUST</span> return avail="0" in its response to a &lt;check&gt;
      command for any object in the &lt;check&gt; command that does not
      include the &lt;fee:check&gt; extension where the server would
      fail a domain &lt;create&gt; command when no &lt;fee&gt;
      extension is provided for that same object.<a href="#section-4-2" class="pilcrow">¶</a></p>
<p id="section-4-3">If a server receives a &lt;check&gt; command from a client that
      results in no possible fee combination, the server <span class="bcp14">MUST</span> set the "avail" 
      attribute of the &lt;fee:cd&gt; element to false (0) and provide a 
      &lt;fee:reason&gt;.<a href="#section-4-3" class="pilcrow">¶</a></p>
<p id="section-4-4">If a server receives a &lt;check&gt; command from a client that results in an ambiguous result (i.e., multiple possible fee combinations),
      the server <span class="bcp14">MUST</span> reject the command with a 2003 "Required parameter
      missing" error.<a href="#section-4-4" class="pilcrow">¶</a></p>
<p id="section-4-5">If a server receives a command from a client that does not include the
      fee extension data elements required by the server for that command, then
      the server <span class="bcp14">MUST</span> respond with a 2003 "Required parameter missing" error.<a href="#section-4-5" class="pilcrow">¶</a></p>
<p id="section-4-6">If the total fee provided by the client is less than the server's own 
      calculation of the fee or the server determines the currency is 
      inappropriate for that command, then the server <span class="bcp14">MUST</span> reject the command 
      with a 2004 "Parameter value range error".<a href="#section-4-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="epp-command">
<section id="section-5">
      <h2 id="name-epp-command-mapping">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-epp-command-mapping" class="section-name selfRef">EPP Command Mapping</a>
      </h2>
<p id="section-5-1">A detailed description of the EPP syntax and semantics can be found in
      <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p>
<div id="epp-query">
<section id="section-5.1">
        <h3 id="name-epp-query-commands">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-epp-query-commands" class="section-name selfRef">EPP Query Commands</a>
        </h3>
<p id="section-5.1-1">This extension does not add any elements to the EPP &lt;poll&gt; or
        &lt;info&gt; commands or responses.<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<div id="epp-check">
<section id="section-5.1.1">
          <h4 id="name-epp-check-command">
<a href="#section-5.1.1" class="section-number selfRef">5.1.1. </a><a href="#name-epp-check-command" class="section-name selfRef">EPP &lt;check&gt; Command</a>
          </h4>
<p id="section-5.1.1-1">This extension defines a new command called the Fee Check Command
          that defines additional elements for the EPP &lt;check&gt; command to
          provide fee information.<a href="#section-5.1.1-1" class="pilcrow">¶</a></p>
<p id="section-5.1.1-2">The command <span class="bcp14">MAY</span> contain an &lt;extension&gt; element, which <span class="bcp14">MAY</span>
          contain a &lt;fee:check&gt; element. The &lt;fee:check&gt; element
          <span class="bcp14">MAY</span> contain one &lt;fee:currency&gt; element and <span class="bcp14">MUST</span> contain one or
          more &lt;fee:command&gt; elements.<a href="#section-5.1.1-2" class="pilcrow">¶</a></p>
<p id="section-5.1.1-3">The &lt;fee:command&gt; element(s) <span class="bcp14">MUST</span> contain a "name" attribute
          (see <a href="#client-commands" class="xref">Section 3.1</a>), an <span class="bcp14">OPTIONAL</span> "phase" attribute, and an <span class="bcp14">OPTIONAL</span>
          "subphase" attribute (see <a href="#phase-subphase" class="xref">Section 3.8</a>). The &lt;fee:command&gt;
          element(s) <span class="bcp14">MAY</span> have the following child elements:<a href="#section-5.1.1-3" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.1.1-4.1">An <span class="bcp14">OPTIONAL</span> &lt;fee:period&gt; element (as described in <a href="#validity-periods" class="xref">Section 3.3</a>).<a href="#section-5.1.1-4.1" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.1.1-5">Example &lt;check&gt; command:<a href="#section-5.1.1-5" class="pilcrow">¶</a></p>
<div id="section-5.1.1-6">
<pre class="sourcecode">
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;check&gt;
C:       &lt;domain:check
C:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:         &lt;domain:name&gt;example.net&lt;/domain:name&gt;
C:         &lt;domain:name&gt;example.xyz&lt;/domain:name&gt;
C:       &lt;/domain:check&gt;
C:     &lt;/check&gt;
C:     &lt;extension&gt;
C:       &lt;fee:check xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
C:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
C:         &lt;fee:command name="create"&gt;
C:           &lt;fee:period unit="y"&gt;2&lt;/fee:period&gt;
C:         &lt;/fee:command&gt;
C:         &lt;fee:command name="renew"/&gt;
C:         &lt;fee:command name="transfer"/&gt;
C:         &lt;fee:command name="restore"/&gt;
C:       &lt;/fee:check&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</pre><a href="#section-5.1.1-6" class="pilcrow">¶</a>
</div>
<p id="section-5.1.1-7">When the server receives a &lt;check&gt; command that includes the
          extension elements described above, its response <span class="bcp14">MUST</span> contain an
          &lt;extension&gt; element, which <span class="bcp14">MUST</span> contain a child
          &lt;fee:chkData&gt; element. The &lt;fee:chkData&gt; element <span class="bcp14">MUST</span>
          contain a &lt;fee:currency&gt; element and a &lt;fee:cd&gt; element 
          for each object referenced in the client &lt;check&gt; command.<a href="#section-5.1.1-7" class="pilcrow">¶</a></p>
<p id="section-5.1.1-8">Each &lt;fee:cd&gt; (check data) element <span class="bcp14">MUST</span> contain the following 
          child elements:<a href="#section-5.1.1-8" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.1.1-9.1">A &lt;fee:objID&gt; element, which <span class="bcp14">MUST</span> match an element
            referenced in the client &lt;check&gt; command.<a href="#section-5.1.1-9.1" class="pilcrow">¶</a>
</li>
<li id="section-5.1.1-9.2">An <span class="bcp14">OPTIONAL</span> &lt;fee:class&gt; element (as
     described in <a href="#classification-objects" class="xref">Section 3.7</a>).<a href="#section-5.1.1-9.2" class="pilcrow">¶</a>
</li>
<li id="section-5.1.1-9.3">A &lt;fee:command&gt; element matching each &lt;fee:command&gt;
            (unless the "avail" attribute of the &lt;fee:cd&gt; is false) that
            appeared in the corresponding &lt;fee:check&gt; of the client
            command. This element <span class="bcp14">MAY</span> have the <span class="bcp14">OPTIONAL</span> "standard" attribute,
            with a default value of "0" (or "false"), which indicates whether
            the fee is the standard or default fee (see
            <a href="#classification-objects" class="xref">Section 3.7</a>). This element <span class="bcp14">MAY</span> have the <span class="bcp14">OPTIONAL</span> "phase" and
            "subphase" attributes, which will match the same attributes in the
            corresponding &lt;fee:command&gt; element of the client command if
            sent by the client.<a href="#section-5.1.1-9.3" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.1.1-10">The &lt;fee:cd&gt; element also has an <span class="bcp14">OPTIONAL</span> "avail"
          attribute, which is a boolean. If the value of this attribute evaluates
          to false, this indicates that the server cannot calculate the relevant
          fees because the object, command, currency, period, class, or some
          combination is invalid per server policy. If "avail" is false, then the
          &lt;fee:cd&gt; or the &lt;fee:command&gt; element <span class="bcp14">MUST</span> contain a
          &lt;fee:reason&gt; element (as described in <a href="#reason" class="xref">Section 3.9</a>), and the
          server <span class="bcp14">MAY</span> eliminate some or all of the &lt;fee:command&gt; element(s).<a href="#section-5.1.1-10" class="pilcrow">¶</a></p>
<p id="section-5.1.1-11">The &lt;fee:command&gt; element(s) <span class="bcp14">MAY</span> have the following child
          elements:<a href="#section-5.1.1-11" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.1.1-12.1">An <span class="bcp14">OPTIONAL</span> &lt;fee:period&gt; element (as described in <a href="#validity-periods" class="xref">Section 3.3</a>), which contains the same unit, if present, that appeared in the 
            &lt;fee:period&gt; element of the command. If the value of the parent
            &lt;fee:command&gt; element is "restore", this element <span class="bcp14">MUST NOT</span> be 
            included; otherwise, it <span class="bcp14">MUST</span> be included. If no &lt;fee:period&gt; 
            appeared in the client command (and the command is not "restore"), 
            then the server <span class="bcp14">MUST</span> return its default period value.<a href="#section-5.1.1-12.1" class="pilcrow">¶</a>
</li>
<li id="section-5.1.1-12.2">Zero or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.1.1-12.2" class="pilcrow">¶</a>
</li>
<li id="section-5.1.1-12.3">Zero or more &lt;fee:credit&gt; elements (as described in
     <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.1.1-12.3" class="pilcrow">¶</a>
</li>
<li id="section-5.1.1-12.4">An <span class="bcp14">OPTIONAL</span> &lt;fee:reason&gt; element (as described in <a href="#reason" class="xref">Section 3.9</a>).<a href="#section-5.1.1-12.4" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.1.1-13">If the "avail" attribute of the &lt;fee:cd&gt; element is true (1) and
          if no &lt;fee:fee&gt; elements are present in a &lt;fee:command&gt;
          element, this indicates that no fee will be assessed by the server for
          this command.<a href="#section-5.1.1-13" class="pilcrow">¶</a></p>
<p id="section-5.1.1-14">If the "avail" attribute of the &lt;fee:cd&gt; element is true (1), 
          then the &lt;fee:command&gt; element <span class="bcp14">MUST NOT</span> contain a &lt;fee:reason&gt; 
          element.<a href="#section-5.1.1-14" class="pilcrow">¶</a></p>
<p id="section-5.1.1-15">Example &lt;check&gt; response:<a href="#section-5.1.1-15" class="pilcrow">¶</a></p>
<div id="section-5.1.1-16">
<pre class="sourcecode">
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;example.com&lt;/domain:name&gt;
S:         &lt;/domain:cd&gt;
S:         &lt;domain:cd&gt;
S:           &lt;domain:name avail="1"&gt;example.net&lt;/domain:name&gt;
S:         &lt;/domain:cd&gt;
S:         &lt;domain:cd&gt;
S:           &lt;domain:name avail="1"&gt;example.xyz&lt;/domain:name&gt;
S:         &lt;/domain:cd&gt;
S:       &lt;/domain:chkData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;fee:chkData
S:           xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
S:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
S:         &lt;fee:cd avail="1"&gt;
S:           &lt;fee:objID&gt;example.com&lt;/fee:objID&gt;
S:           &lt;fee:class&gt;Premium&lt;/fee:class&gt;
S:           &lt;fee:command name="create"&gt;
S:             &lt;fee:period unit="y"&gt;2&lt;/fee:period&gt;
S:             &lt;fee:fee
S:               description="Registration Fee"
S:               refundable="1"
S:               grace-period="P5D"&gt;10.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:           &lt;fee:command name="renew"&gt;
S:             &lt;fee:period unit="y"&gt;1&lt;/fee:period&gt;
S:             &lt;fee:fee
S:               description="Renewal Fee"
S:               refundable="1"
S:               grace-period="P5D"&gt;10.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:           &lt;fee:command name="transfer"&gt;
S:             &lt;fee:period unit="y"&gt;1&lt;/fee:period&gt;
S:             &lt;fee:fee
S:               description="Transfer Fee"
S:               refundable="1"
S:               grace-period="P5D"&gt;10.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:           &lt;fee:command name="restore"&gt;
S:             &lt;fee:fee
S:               description="Redemption Fee"&gt;15.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:         &lt;/fee:cd&gt;
S:         &lt;fee:cd avail="1"&gt;
S:           &lt;fee:objID&gt;example.net&lt;/fee:objID&gt;
S:           &lt;fee:class&gt;standard&lt;/fee:class&gt;
S:           &lt;fee:command name="create" standard="1"&gt;
S:             &lt;fee:period unit="y"&gt;2&lt;/fee:period&gt;
S:             &lt;fee:fee
S:               description="Registration Fee"
S:               refundable="1"
S:               grace-period="P5D"&gt;5.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:           &lt;fee:command name="renew" standard="1"&gt;
S:             &lt;fee:period unit="y"&gt;1&lt;/fee:period&gt;
S:             &lt;fee:fee
S:               description="Renewal Fee"
S:               refundable="1"
S:               grace-period="P5D"&gt;5.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:           &lt;fee:command name="transfer" standard="1"&gt;
S:             &lt;fee:period unit="y"&gt;1&lt;/fee:period&gt;
S:             &lt;fee:fee
S:               description="Transfer Fee"
S:               refundable="1"
S:               grace-period="P5D"&gt;5.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:           &lt;fee:command name="restore" standard="1"&gt;
S:             &lt;fee:fee
S:               description="Redemption Fee"&gt;5.00&lt;/fee:fee&gt;
S:           &lt;/fee:command&gt;
S:         &lt;/fee:cd&gt;
S:         &lt;fee:cd avail="0"&gt;
S:           &lt;fee:objID&gt;example.xyz&lt;/fee:objID&gt;
S:           &lt;fee:command name="create"&gt;
S:             &lt;fee:period unit="y"&gt;2&lt;/fee:period&gt;
S:             &lt;fee:reason&gt;Only 1 year registration periods are
S:               valid.&lt;/fee:reason&gt;
S:           &lt;/fee:command&gt;
S:         &lt;/fee:cd&gt;
S:       &lt;/fee:chkData&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><a href="#section-5.1.1-16" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="epp-transfer-query">
<section id="section-5.1.2">
          <h4 id="name-epp-transfer-query-command">
<a href="#section-5.1.2" class="section-number selfRef">5.1.2. </a><a href="#name-epp-transfer-query-command" class="section-name selfRef">EPP Transfer Query Command</a>
          </h4>
<p id="section-5.1.2-1">This extension does not add any elements to the EPP &lt;transfer&gt;
          query command, but it does include elements in the response when the
          extension is included in the &lt;login&gt; command service extensions.<a href="#section-5.1.2-1" class="pilcrow">¶</a></p>
<p id="section-5.1.2-2">When the &lt;transfer&gt; query command has been processed
          successfully, if the client has included the extension in the &lt;login&gt; 
          command service &lt;svcExtension&gt; element, and if the client is 
          authorized by the server to view information about the transfer, then 
          the server <span class="bcp14">MAY</span> include in the &lt;extension&gt; section of the EPP 
          response a &lt;fee:trnData&gt; element, which contains the following 
          child elements:<a href="#section-5.1.2-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.1.2-3.1">A &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.1.2-3.1" class="pilcrow">¶</a>
</li>
<li id="section-5.1.2-3.2">A &lt;fee:period&gt; element (as described in <a href="#validity-periods" class="xref">Section 3.3</a>).<a href="#section-5.1.2-3.2" class="pilcrow">¶</a>
</li>
<li id="section-5.1.2-3.3">Zero or more &lt;fee:fee&gt; elements  (as described in <a href="#fees-credits" class="xref">Section 3.4</a>) containing the fees that will be charged to the gaining client.<a href="#section-5.1.2-3.3" class="pilcrow">¶</a>
</li>
<li id="section-5.1.2-3.4">Zero or more &lt;fee:credit&gt; elements  (as described in
            <a href="#fees-credits" class="xref">Section 3.4</a>) containing the credits that will be refunded to the
            losing client.<a href="#section-5.1.2-3.4" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.1.2-4">Servers <span class="bcp14">SHOULD</span> omit &lt;fee:credit&gt; when returning a response to
          the gaining client and omit &lt;fee:fee&gt; elements when returning a
          response to the losing client.<a href="#section-5.1.2-4" class="pilcrow">¶</a></p>
<p id="section-5.1.2-5">If no &lt;fee:trnData&gt; element is included in the response, then
          no fee will be assessed by the server for the transfer.<a href="#section-5.1.2-5" class="pilcrow">¶</a></p>
<p id="section-5.1.2-6">Example &lt;transfer&gt; query response:<a href="#section-5.1.2-6" class="pilcrow">¶</a></p>
<div id="section-5.1.2-7">
<pre class="sourcecode">
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;example.com&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;2019-06-08T22:00:00.0Z&lt;/domain:reDate&gt;
S:         &lt;domain:acID&gt;ClientY&lt;/domain:acID&gt;
S:         &lt;domain:acDate&gt;2019-06-13T22:00:00.0Z&lt;/domain:acDate&gt;
S:         &lt;domain:exDate&gt;2021-09-08T22:00:00.0Z&lt;/domain:exDate&gt;
S:       &lt;/domain:trnData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;fee:trnData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
S:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
S:         &lt;fee:period unit="y"&gt;1&lt;/fee:period&gt;
S:         &lt;fee:fee&gt;5.00&lt;/fee:fee&gt;
S:       &lt;/fee: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><a href="#section-5.1.2-7" class="pilcrow">¶</a>
</div>
</section>
</div>
</section>
</div>
<div id="epp-transform">
<section id="section-5.2">
        <h3 id="name-epp-transform-commands">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-epp-transform-commands" class="section-name selfRef">EPP Transform Commands</a>
        </h3>
<div id="epp-create">
<section id="section-5.2.1">
          <h4 id="name-epp-create-command">
<a href="#section-5.2.1" class="section-number selfRef">5.2.1. </a><a href="#name-epp-create-command" class="section-name selfRef">EPP &lt;create&gt; Command</a>
          </h4>
<p id="section-5.2.1-1">This extension adds elements to both the EPP &lt;create&gt; command
          and response when the extension is included in the &lt;login&gt; 
          command service extensions.<a href="#section-5.2.1-1" class="pilcrow">¶</a></p>
<p id="section-5.2.1-2">When submitting a &lt;create&gt; command to the server, the client
          <span class="bcp14">MAY</span> include in the &lt;extension&gt; element a &lt;fee:create&gt;
          element, which includes the following child elements:<a href="#section-5.2.1-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.1-3.1">An <span class="bcp14">OPTIONAL</span> &lt;fee:currency&gt; element (as described in
     <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.1-3.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.1-3.2">One or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.1-3.2" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.1-4">When the &lt;create&gt; command has been processed successfully,
          the client included the extension in the &lt;login&gt; command 
          service extensions, and a fee was assessed by the server for the 
          transaction, the server <span class="bcp14">MUST</span> include in the &lt;extension&gt; section 
          of the EPP response a &lt;fee:creData&gt; element, which contains the 
          following child elements:<a href="#section-5.2.1-4" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.1-5.1">A &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.1-5.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.1-5.2">Zero or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.1-5.2" class="pilcrow">¶</a>
</li>
<li id="section-5.2.1-5.3">Zero or more &lt;fee:credit&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.1-5.3" class="pilcrow">¶</a>
</li>
<li id="section-5.2.1-5.4">An <span class="bcp14">OPTIONAL</span> &lt;fee:balance&gt; element (as described in <a href="#account-balance" class="xref">Section 3.5</a>).<a href="#section-5.2.1-5.4" class="pilcrow">¶</a>
</li>
<li id="section-5.2.1-5.5">An <span class="bcp14">OPTIONAL</span> &lt;fee:creditLimit&gt; element (as described in <a href="#credit-limit" class="xref">Section 3.6</a>).<a href="#section-5.2.1-5.5" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.1-6">Example &lt;create&gt; command:<a href="#section-5.2.1-6" class="pilcrow">¶</a></p>
<div id="section-5.2.1-7">
<pre class="sourcecode">
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;example.com&lt;/domain:name&gt;
C:         &lt;domain:period unit="y"&gt;2&lt;/domain:period&gt;
C:         &lt;domain:ns&gt;
C:           &lt;domain:hostObj&gt;ns1.example.net&lt;/domain:hostObj&gt;
C:           &lt;domain:hostObj&gt;ns2.example.net&lt;/domain:hostObj&gt;
C:         &lt;/domain:ns&gt;
C:         &lt;domain:registrant&gt;jd1234&lt;/domain:registrant&gt;
C:         &lt;domain:contact type="admin"&gt;sh8013&lt;/domain:contact&gt;
C:         &lt;domain:contact type="tech"&gt;sh8013&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;fee:create xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
C:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
C:         &lt;fee:fee&gt;5.00&lt;/fee:fee&gt;
C:       &lt;/fee:create&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</pre><a href="#section-5.2.1-7" class="pilcrow">¶</a>
</div>
<p id="section-5.2.1-8">Example &lt;create&gt; response:<a href="#section-5.2.1-8" class="pilcrow">¶</a></p>
<div id="section-5.2.1-9">
<pre class="sourcecode">
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;example.com&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;fee:creData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
S:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
S:         &lt;fee:fee
S:           description="Registration Fee"
S:           lang="en"
S:           refundable="1"
S:           grace-period="P5D"&gt;5.00&lt;/fee:fee&gt;
S:         &lt;fee:balance&gt;-5.00&lt;/fee:balance&gt;
S:         &lt;fee:creditLimit&gt;1000.00&lt;/fee:creditLimit&gt;
S:       &lt;/fee:creData&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><a href="#section-5.2.1-9" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="epp-delete">
<section id="section-5.2.2">
          <h4 id="name-epp-delete-command">
<a href="#section-5.2.2" class="section-number selfRef">5.2.2. </a><a href="#name-epp-delete-command" class="section-name selfRef">EPP &lt;delete&gt; Command</a>
          </h4>
<p id="section-5.2.2-1">This extension does not add any elements to the EPP &lt;delete&gt;
          command, but it does include elements in the response when the extension
          is included in the &lt;login&gt; command service extensions.<a href="#section-5.2.2-1" class="pilcrow">¶</a></p>
<p id="section-5.2.2-2">When the &lt;delete&gt; command has been processed successfully
          and the client included the extension in the &lt;login&gt; command 
          service extensions, the server <span class="bcp14">MAY</span> include in the &lt;extension&gt; 
          section of the EPP response a &lt;fee:delData&gt; element, which 
          contains the following child elements:<a href="#section-5.2.2-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.2-3.1">A &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.2-3.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.2-3.2">Zero or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.2-3.2" class="pilcrow">¶</a>
</li>
<li id="section-5.2.2-3.3">Zero or more &lt;fee:credit&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.2-3.3" class="pilcrow">¶</a>
</li>
<li id="section-5.2.2-3.4">An <span class="bcp14">OPTIONAL</span> &lt;fee:balance&gt; element (as described in <a href="#account-balance" class="xref">Section 3.5</a>).<a href="#section-5.2.2-3.4" class="pilcrow">¶</a>
</li>
<li id="section-5.2.2-3.5">An <span class="bcp14">OPTIONAL</span> &lt;fee:creditLimit&gt; element (as described in <a href="#credit-limit" class="xref">Section 3.6</a>).<a href="#section-5.2.2-3.5" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.2-4">Example &lt;delete&gt; response:<a href="#section-5.2.2-4" class="pilcrow">¶</a></p>
<div id="section-5.2.2-5">
<pre class="sourcecode">
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;fee:delData
S:         xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
S:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
S:         &lt;fee:credit
S:           description="AGP Credit"
S:           lang="en"&gt;-5.00&lt;/fee:credit&gt;
S:         &lt;fee:balance&gt;1005.00&lt;/fee:balance&gt;
S:       &lt;/fee: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><a href="#section-5.2.2-5" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="epp-renew">
<section id="section-5.2.3">
          <h4 id="name-epp-renew-command">
<a href="#section-5.2.3" class="section-number selfRef">5.2.3. </a><a href="#name-epp-renew-command" class="section-name selfRef">EPP &lt;renew&gt; Command</a>
          </h4>
<p id="section-5.2.3-1">This extension adds elements to both the EPP &lt;renew&gt; command
          and response when the extension is included in the &lt;login&gt; 
          command service extensions.<a href="#section-5.2.3-1" class="pilcrow">¶</a></p>
<p id="section-5.2.3-2">When submitting a &lt;renew&gt; command to the server, the client
          <span class="bcp14">MAY</span> include in the &lt;extension&gt; element a &lt;fee:renew&gt;
          element, which includes the following child elements:<a href="#section-5.2.3-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.3-3.1">An <span class="bcp14">OPTIONAL</span> &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.3-3.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.3-3.2">One or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.3-3.2" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.3-4">When the &lt;renew&gt; command has been processed successfully and
          the client included the extension in the &lt;login&gt; command service 
          extensions, the server <span class="bcp14">MAY</span> include in the &lt;extension&gt; section of 
          the EPP response a &lt;fee:renData&gt; element, which contains the 
          following child elements:<a href="#section-5.2.3-4" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.3-5.1">A &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.3-5.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.3-5.2">Zero or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.3-5.2" class="pilcrow">¶</a>
</li>
<li id="section-5.2.3-5.3">Zero or more &lt;fee:credit&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.3-5.3" class="pilcrow">¶</a>
</li>
<li id="section-5.2.3-5.4">An <span class="bcp14">OPTIONAL</span> &lt;fee:balance&gt; element (as described in <a href="#account-balance" class="xref">Section 3.5</a>).<a href="#section-5.2.3-5.4" class="pilcrow">¶</a>
</li>
<li id="section-5.2.3-5.5">An <span class="bcp14">OPTIONAL</span> &lt;fee:creditLimit&gt; element (as described in <a href="#credit-limit" class="xref">Section 3.6</a>).<a href="#section-5.2.3-5.5" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.3-6">Example &lt;renew&gt; command:<a href="#section-5.2.3-6" class="pilcrow">¶</a></p>
<div id="section-5.2.3-7">
<pre class="sourcecode">
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;renew&gt;
C:       &lt;domain:renew
C:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:         &lt;domain:curExpDate&gt;2019-04-03&lt;/domain:curExpDate&gt;
C:         &lt;domain:period unit="y"&gt;5&lt;/domain:period&gt;
C:       &lt;/domain:renew&gt;
C:     &lt;/renew&gt;
C:     &lt;extension&gt;
C:       &lt;fee:renew xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
C:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
C:         &lt;fee:fee&gt;5.00&lt;/fee:fee&gt;
C:       &lt;/fee:renew&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</pre><a href="#section-5.2.3-7" class="pilcrow">¶</a>
</div>
<p id="section-5.2.3-8">Example &lt;renew&gt; response:<a href="#section-5.2.3-8" class="pilcrow">¶</a></p>
<div id="section-5.2.3-9">
<pre class="sourcecode">
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;example.com&lt;/domain:name&gt;
S:         &lt;domain:exDate&gt;2024-04-03T22:00:00.0Z&lt;/domain:exDate&gt;
S:       &lt;/domain:renData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;fee:renData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
S:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
S:         &lt;fee:fee
S:           refundable="1"
S:           grace-period="P5D"&gt;5.00&lt;/fee:fee&gt;
S:         &lt;fee:balance&gt;1000.00&lt;/fee:balance&gt;
S:       &lt;/fee: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><a href="#section-5.2.3-9" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="epp-transfer-command">
<section id="section-5.2.4">
          <h4 id="name-epp-transfer-command">
<a href="#section-5.2.4" class="section-number selfRef">5.2.4. </a><a href="#name-epp-transfer-command" class="section-name selfRef">EPP &lt;transfer&gt; Command</a>
          </h4>
<p id="section-5.2.4-1">This extension adds elements to both the EPP &lt;transfer&gt;
          command and response when the value of the "op" attribute of the
          &lt;transfer&gt; command element is "request" and the extension is 
          included in the &lt;login&gt; command service extensions.<a href="#section-5.2.4-1" class="pilcrow">¶</a></p>
<p id="section-5.2.4-2">When submitting a &lt;transfer&gt; command to the server, the
          client <span class="bcp14">MAY</span> include in the &lt;extension&gt; element a
          &lt;fee:transfer&gt; element, which includes the following child
          elements:<a href="#section-5.2.4-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.4-3.1">An <span class="bcp14">OPTIONAL</span> &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.4-3.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.4-3.2">One or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.4-3.2" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.4-4">When the &lt;transfer&gt; command has been processed successfully
          and the client included the extension in the &lt;login&gt; command 
          service extensions, the server <span class="bcp14">MAY</span> include in the &lt;extension&gt; 
          section of the EPP response a &lt;fee:trnData&gt; element, which 
          contains the following child elements:<a href="#section-5.2.4-4" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.4-5.1">A &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.4-5.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.4-5.2">Zero or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.4-5.2" class="pilcrow">¶</a>
</li>
<li id="section-5.2.4-5.3">Zero or more &lt;fee:credit&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.4-5.3" class="pilcrow">¶</a>
</li>
<li id="section-5.2.4-5.4">An <span class="bcp14">OPTIONAL</span> &lt;fee:balance&gt; element (as described in <a href="#account-balance" class="xref">Section 3.5</a>).<a href="#section-5.2.4-5.4" class="pilcrow">¶</a>
</li>
<li id="section-5.2.4-5.5">An <span class="bcp14">OPTIONAL</span> &lt;fee:creditLimit&gt; element (as described in <a href="#credit-limit" class="xref">Section 3.6</a>).<a href="#section-5.2.4-5.5" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.4-6">Example &lt;transfer&gt; command:<a href="#section-5.2.4-6" class="pilcrow">¶</a></p>
<div id="section-5.2.4-7">
<pre class="sourcecode">
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;transfer op="request"&gt;
C:       &lt;domain:transfer
C:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:         &lt;domain:period unit="y"&gt;1&lt;/domain:period&gt;
C:         &lt;domain:authInfo&gt;
C:           &lt;domain:pw roid="JD1234-REP"&gt;2fooBAR&lt;/domain:pw&gt;
C:         &lt;/domain:authInfo&gt;
C:       &lt;/domain:transfer&gt;
C:     &lt;/transfer&gt;
C:     &lt;extension&gt;
C:      &lt;fee:transfer xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
C:        &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
C:        &lt;fee:fee&gt;5.00&lt;/fee:fee&gt;
C:      &lt;/fee:transfer&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</pre><a href="#section-5.2.4-7" class="pilcrow">¶</a>
</div>
<p id="section-5.2.4-8">Example &lt;transfer&gt; response:<a href="#section-5.2.4-8" class="pilcrow">¶</a></p>
<div id="section-5.2.4-9">
<pre class="sourcecode">
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;example.com&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;2019-06-08T22:00:00.0Z&lt;/domain:reDate&gt;
S:         &lt;domain:acID&gt;ClientY&lt;/domain:acID&gt;
S:         &lt;domain:acDate&gt;2019-06-13T22:00:00.0Z&lt;/domain:acDate&gt;
S:         &lt;domain:exDate&gt;2021-09-08T22:00:00.0Z&lt;/domain:exDate&gt;
S:       &lt;/domain:trnData&gt;
S:     &lt;/resData&gt;
S:     &lt;extension&gt;
S:       &lt;fee:trnData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
S:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
S:         &lt;fee:fee
S:           refundable="1"
S:           grace-period="P5D"&gt;5.00&lt;/fee:fee&gt;
S:       &lt;/fee: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><a href="#section-5.2.4-9" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="epp-update">
<section id="section-5.2.5">
          <h4 id="name-epp-update-command">
<a href="#section-5.2.5" class="section-number selfRef">5.2.5. </a><a href="#name-epp-update-command" class="section-name selfRef">EPP &lt;update&gt; Command</a>
          </h4>
<p id="section-5.2.5-1">This extension adds elements to both the EPP &lt;update&gt;
          command and response when the extension is included in the &lt;login&gt; 
          command service extensions.<a href="#section-5.2.5-1" class="pilcrow">¶</a></p>
<p id="section-5.2.5-2">When submitting an &lt;update&gt; command to the server, the
          client <span class="bcp14">MAY</span> include in the &lt;extension&gt; element a
          &lt;fee:update&gt; element, which includes the following child
          elements:<a href="#section-5.2.5-2" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.5-3.1">An <span class="bcp14">OPTIONAL</span> &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.5-3.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.5-3.2">One or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.5-3.2" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.5-4">When the &lt;update&gt; command has been processed successfully
          and the client included the extension in the &lt;login&gt; command 
          service extensions, the server <span class="bcp14">MAY</span> include in the &lt;extension&gt; 
          section of the EPP response a &lt;fee:updData&gt; element, which
          contains the following child elements:<a href="#section-5.2.5-4" class="pilcrow">¶</a></p>
<ul>
<li id="section-5.2.5-5.1">A &lt;fee:currency&gt; element (as described in <a href="#currency-codes" class="xref">Section 3.2</a>).<a href="#section-5.2.5-5.1" class="pilcrow">¶</a>
</li>
<li id="section-5.2.5-5.2">Zero or more &lt;fee:fee&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.5-5.2" class="pilcrow">¶</a>
</li>
<li id="section-5.2.5-5.3">Zero or more &lt;fee:credit&gt; elements (as described in <a href="#fees-credits" class="xref">Section 3.4</a>).<a href="#section-5.2.5-5.3" class="pilcrow">¶</a>
</li>
<li id="section-5.2.5-5.4">An <span class="bcp14">OPTIONAL</span> &lt;fee:balance&gt; element (as described in <a href="#account-balance" class="xref">Section 3.5</a>).<a href="#section-5.2.5-5.4" class="pilcrow">¶</a>
</li>
<li id="section-5.2.5-5.5">An <span class="bcp14">OPTIONAL</span> &lt;fee:creditLimit&gt; element (as described in <a href="#credit-limit" class="xref">Section 3.6</a>).<a href="#section-5.2.5-5.5" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-5.2.5-6">Example &lt;update&gt; command:<a href="#section-5.2.5-6" class="pilcrow">¶</a></p>
<div id="section-5.2.5-7">
<pre class="sourcecode">
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;update&gt;
C:       &lt;domain:update
C:         xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"&gt;
C:         &lt;domain:name&gt;example.com&lt;/domain:name&gt;
C:         &lt;domain:chg&gt;
C:           &lt;domain:registrant&gt;sh8013&lt;/domain:registrant&gt;
C:         &lt;/domain:chg&gt;
C:       &lt;/domain:update&gt;
C:     &lt;/update&gt;
C:     &lt;extension&gt;
C:       &lt;fee:update xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
C:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
C:         &lt;fee:fee&gt;5.00&lt;/fee:fee&gt;
C:       &lt;/fee:update&gt;
C:     &lt;/extension&gt;
C:     &lt;clTRID&gt;ABC-12345&lt;/clTRID&gt;
C:   &lt;/command&gt;
C: &lt;/epp&gt;
</pre><a href="#section-5.2.5-7" class="pilcrow">¶</a>
</div>
<p id="section-5.2.5-8">Example &lt;update&gt; response:<a href="#section-5.2.5-8" class="pilcrow">¶</a></p>
<div id="section-5.2.5-9">
<pre class="sourcecode">
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;fee:updData xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"&gt;
S:         &lt;fee:currency&gt;USD&lt;/fee:currency&gt;
S:         &lt;fee:fee&gt;5.00&lt;/fee:fee&gt;
S:       &lt;/fee:updData&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><a href="#section-5.2.5-9" class="pilcrow">¶</a>
</div>
</section>
</div>
</section>
</div>
</section>
</div>
<div id="syntax">
<section id="section-6">
      <h2 id="name-formal-syntax">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-formal-syntax" class="section-name selfRef">Formal Syntax</a>
      </h2>
<p id="section-6-1">One schema is presented here -- the EPP Fee Extension schema.<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">The formal syntax presented here is a complete schema representation of
      the object mapping suitable for automated validation of EPP XML instances.<a href="#section-6-2" class="pilcrow">¶</a></p>
<div id="fee-extension">
<section id="section-6.1">
        <h3 id="name-fee-extension-schema">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-fee-extension-schema" class="section-name selfRef">Fee Extension Schema</a>
        </h3>
<p id="section-6.1-1">The formal syntax presented here is a complete schema
 representation <span>[<a href="#W3C.REC-xmlschema-1-20041028" class="xref">W3C.REC-xmlschema-1-20041028</a>]</span>
        of the object mapping suitable for automated validation of EPP XML 
        instances.  The &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; tags are not part of the schema; they are 
        used to note the beginning and end of the schema for URI registration 
        purposes.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
<div id="section-6.1-2">
<pre class="sourcecode lang-xml">&lt;CODE BEGINS&gt;
&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;schema xmlns="http://www.w3.org/2001/XMLSchema"
  xmlns:fee="urn:ietf:params:xml:ns:epp:fee-1.0"
  xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
  xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
  targetNamespace="urn:ietf:params:xml:ns:epp:fee-1.0"
  elementFormDefault="qualified"&gt;

  &lt;import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /&gt;
  &lt;import namespace="urn:ietf:params:xml:ns:domain-1.0" /&gt;

  &lt;annotation&gt;
    &lt;documentation&gt;
      Extensible Provisioning Protocol v1.0 Fee Extension
    &lt;/documentation&gt;
  &lt;/annotation&gt;

  &lt;!-- Child elements found in EPP commands and responses --&gt;
  &lt;element name="check" type="fee:checkType" /&gt;
  &lt;element name="chkData" type="fee:chkDataType" /&gt;
  &lt;element name="create" type="fee:transformCommandType" /&gt;
  &lt;element name="creData" type="fee:transformResultType" /&gt;
  &lt;element name="renew" type="fee:transformCommandType" /&gt;
  &lt;element name="renData" type="fee:transformResultType" /&gt;
  &lt;element name="transfer" type="fee:transformCommandType" /&gt;
  &lt;element name="trnData" type="fee:transformResultType" /&gt;
  &lt;element name="update" type="fee:transformCommandType" /&gt;
  &lt;element name="updData" type="fee:transformResultType" /&gt;
  &lt;element name="delData" type="fee:transformResultType" /&gt;

  &lt;!-- client &lt;check&gt; command --&gt;
  &lt;complexType name="checkType"&gt;
    &lt;sequence&gt;
      &lt;element name="currency" type="fee:currencyType"
        minOccurs="0" /&gt;
      &lt;element name="command" type="fee:commandType"
        minOccurs="1" maxOccurs="unbounded" /&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;complexType name="objectIdentifierType"&gt;
    &lt;simpleContent&gt;
      &lt;extension base="eppcom:labelType"&gt;
        &lt;attribute name="element"
        type="NMTOKEN" default="name" /&gt;
      &lt;/extension&gt;
    &lt;/simpleContent&gt;
  &lt;/complexType&gt;

  &lt;!-- server &lt;check&gt; result --&gt;
  &lt;complexType name="chkDataType"&gt;
    &lt;sequence&gt;
      &lt;element name="currency" type="fee:currencyType" /&gt;
      &lt;element name="cd" type="fee:objectCDType"
        maxOccurs="unbounded" /&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;complexType name="objectCDType"&gt;
    &lt;sequence&gt;
      &lt;element name="objID" type="fee:objectIdentifierType" /&gt;
      &lt;element name="class" type="token" minOccurs="0" /&gt;
      &lt;element name="command" type="fee:commandDataType"
        minOccurs="0" maxOccurs="unbounded" /&gt;
      &lt;element name="reason" type="fee:reasonType" minOccurs="0" /&gt;
    &lt;/sequence&gt;
    &lt;attribute name="avail" type="boolean" default="1" /&gt;
  &lt;/complexType&gt;

  &lt;!-- general transform (create, renew, update, transfer) command--&gt;
  &lt;complexType name="transformCommandType"&gt;
    &lt;sequence&gt;
      &lt;element name="currency" type="fee:currencyType"
        minOccurs="0" /&gt;
      &lt;element name="fee" type="fee:feeType"
        maxOccurs="unbounded" /&gt;
      &lt;element name="credit" type="fee:creditType"
        minOccurs="0" maxOccurs="unbounded" /&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;!-- general transform (create, renew, update) result --&gt;
  &lt;complexType name="transformResultType"&gt;
    &lt;sequence&gt;
      &lt;element name="currency" type="fee:currencyType"
        minOccurs="0" /&gt;
      &lt;element name="period" type="domain:periodType"
        minOccurs="0" /&gt;
      &lt;element name="fee" type="fee:feeType"
        minOccurs="0" maxOccurs="unbounded" /&gt;
      &lt;element name="credit" type="fee:creditType"
        minOccurs="0" maxOccurs="unbounded" /&gt;
      &lt;element name="balance" type="fee:balanceType"
        minOccurs="0" /&gt;
      &lt;element name="creditLimit" type="fee:creditLimitType"
        minOccurs="0" /&gt;
    &lt;/sequence&gt;
  &lt;/complexType&gt;

  &lt;!-- common types --&gt;
  &lt;simpleType name="currencyType"&gt;
    &lt;restriction base="string"&gt;
      &lt;pattern value="[A-Z]{3}" /&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;complexType name="commandType"&gt;
    &lt;sequence&gt;
      &lt;element name="period" type="domain:periodType"
        minOccurs="0" maxOccurs="1" /&gt;
    &lt;/sequence&gt;
    &lt;attribute name="name" type="fee:commandEnum" use="required"/&gt;
    &lt;attribute name="customName" type="token"/&gt;
    &lt;attribute name="phase" type="token" /&gt;
    &lt;attribute name="subphase" type="token" /&gt;
  &lt;/complexType&gt;

  &lt;complexType name="commandDataType"&gt;
    &lt;complexContent&gt;
      &lt;extension base="fee:commandType"&gt;
        &lt;sequence&gt;
          &lt;element name="fee" type="fee:feeType"
            minOccurs="0" maxOccurs="unbounded" /&gt;
          &lt;element name="credit" type="fee:creditType"
            minOccurs="0" maxOccurs="unbounded" /&gt;
          &lt;element name="reason" type="fee:reasonType"
            minOccurs="0" /&gt;
        &lt;/sequence&gt;
        &lt;attribute name="standard" type="boolean" default="0" /&gt;
      &lt;/extension&gt;
    &lt;/complexContent&gt;
  &lt;/complexType&gt;

  &lt;complexType name="reasonType"&gt;
    &lt;simpleContent&gt;
      &lt;extension base="token"&gt;
        &lt;attribute name="lang" type="language" default="en"/&gt;
      &lt;/extension&gt;
    &lt;/simpleContent&gt;
  &lt;/complexType&gt;

  &lt;simpleType name="commandEnum"&gt;
    &lt;restriction base="token"&gt;
      &lt;enumeration value="create"/&gt;
      &lt;enumeration value="delete"/&gt;
      &lt;enumeration value="renew"/&gt;
      &lt;enumeration value="update"/&gt;
      &lt;enumeration value="transfer"/&gt;
      &lt;enumeration value="restore"/&gt;
      &lt;enumeration value="custom"/&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;simpleType name="nonNegativeDecimal"&gt;
    &lt;restriction base="decimal"&gt;
      &lt;minInclusive value="0" /&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;simpleType name="negativeDecimal"&gt;
    &lt;restriction base="decimal"&gt;
      &lt;maxInclusive value="0" /&gt;
    &lt;/restriction&gt;
  &lt;/simpleType&gt;

  &lt;complexType name="feeType"&gt;
    &lt;simpleContent&gt;
      &lt;extension base="fee:nonNegativeDecimal"&gt;
        &lt;attribute name="description"/&gt;
        &lt;attribute name="lang" type="language" default="en"/&gt;
        &lt;attribute name="refundable" type="boolean" /&gt;
        &lt;attribute name="grace-period" type="duration" /&gt;
        &lt;attribute name="applied"&gt;
          &lt;simpleType&gt;
            &lt;restriction base="token"&gt;
              &lt;enumeration value="immediate" /&gt;
              &lt;enumeration value="delayed" /&gt;
            &lt;/restriction&gt;
          &lt;/simpleType&gt;
        &lt;/attribute&gt;
      &lt;/extension&gt;
    &lt;/simpleContent&gt;
  &lt;/complexType&gt;

  &lt;complexType name="creditType"&gt;
    &lt;simpleContent&gt;
      &lt;extension base="fee:negativeDecimal"&gt;
        &lt;attribute name="description"/&gt;
        &lt;attribute name="lang" type="language" default="en"/&gt;
      &lt;/extension&gt;
    &lt;/simpleContent&gt;
  &lt;/complexType&gt;

  &lt;simpleType name="balanceType"&gt;
    &lt;restriction base="decimal" /&gt;
  &lt;/simpleType&gt;

  &lt;simpleType name="creditLimitType"&gt;
    &lt;restriction base="decimal" /&gt;
  &lt;/simpleType&gt;

&lt;/schema&gt;

&lt;CODE ENDS&gt;</pre><a href="#section-6.1-2" class="pilcrow">¶</a>
</div>
</section>
</div>
</section>
</div>
<div id="Security">
<section id="section-7">
      <h2 id="name-security-considerations">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-7-1">The mapping extensions described in this document do not provide any
      security services beyond those described by the EPP <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span>, the EPP domain
      name mapping <span>[<a href="#RFC5731" class="xref">RFC5731</a>]</span>, and the protocol
      layers used by the EPP.  The security
      considerations described in these other specifications apply to this
      specification as well. This extension passes financial information using 
      the EPP protocol, so confidentiality and integrity protection must be 
      provided by the transport mechanism.  All transports compliant with 
      <span>[<a href="#RFC5730" class="xref">RFC5730</a>]</span> provide the needed level of confidentiality and integrity 
      protections.  The server will only provide information, including 
      financial information, that is relevant to the authenticated client.<a href="#section-7-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="IANA">
<section id="section-8">
      <h2 id="name-iana-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<div id="xml-namespace">
<section id="section-8.1">
        <h3 id="name-xml-namespace">
<a href="#section-8.1" class="section-number selfRef">8.1. </a><a href="#name-xml-namespace" class="section-name selfRef">XML Namespace</a>
        </h3>
<p id="section-8.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-8.1-1" class="pilcrow">¶</a></p>
<p id="section-8.1-2">Registration request for the fee namespace:<a href="#section-8.1-2" class="pilcrow">¶</a></p>
<p id="section-8.1-3">URI: urn:ietf:params:xml:ns:epp:fee-1.0<a href="#section-8.1-3" class="pilcrow">¶</a></p>
<p id="section-8.1-4">Registrant Contact: IESG<a href="#section-8.1-4" class="pilcrow">¶</a></p>
<p id="section-8.1-5">XML: None. Namespace URIs do not represent an XML specification.<a href="#section-8.1-5" class="pilcrow">¶</a></p>
<p id="section-8.1-6">Registration request for the fee schema:<a href="#section-8.1-6" class="pilcrow">¶</a></p>
<p id="section-8.1-7">URI: urn:ietf:params:xml:schema:epp:fee-1.0<a href="#section-8.1-7" class="pilcrow">¶</a></p>
<p id="section-8.1-8">Registrant Contact: IESG<a href="#section-8.1-8" class="pilcrow">¶</a></p>
<p id="section-8.1-9">XML: See <a href="#syntax" class="xref">Section 6</a> of this document.<a href="#section-8.1-9" class="pilcrow">¶</a></p>
</section>
</div>
<div id="epp-extension-reg">
<section id="section-8.2">
        <h3 id="name-epp-extension-registry">
<a href="#section-8.2" class="section-number selfRef">8.2. </a><a href="#name-epp-extension-registry" class="section-name selfRef">EPP Extension Registry</a>
        </h3>
<p id="section-8.2-1">The EPP extension described in this document has been registered by
        IANA 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-8.2-1" class="pilcrow">¶</a></p>
<p id="section-8.2-2">Name of Extension: Registry Fee Extension for the Extensible 
        Provisioning Protocol (EPP)<a href="#section-8.2-2" class="pilcrow">¶</a></p>
<p id="section-8.2-3">Document status: Standards Track<a href="#section-8.2-3" class="pilcrow">¶</a></p>
<p id="section-8.2-4">Reference: RFC 8748<a href="#section-8.2-4" class="pilcrow">¶</a></p>
<p id="section-8.2-5">Registrant Name and Email Address: IESG &lt;iesg@ietf.org&gt;<a href="#section-8.2-5" class="pilcrow">¶</a></p>
<p id="section-8.2-6">TLDs: Any<a href="#section-8.2-6" class="pilcrow">¶</a></p>
<p id="section-8.2-7">IPR Disclosure: None<a href="#section-8.2-7" class="pilcrow">¶</a></p>
<p id="section-8.2-8">Status: Active<a href="#section-8.2-8" class="pilcrow">¶</a></p>
<p id="section-8.2-9">Notes: None<a href="#section-8.2-9" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<section id="section-9">
      <h2 id="name-references">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-9.1">
        <h3 id="name-normative-references">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="ISO4217_2015">[ISO4217_2015]</dt>
<dd>
<span class="refAuthor">ISO</span>, <span class="refTitle">"Codes for the representation of currencies"</span>, <span class="seriesInfo">ISO 4217:2015</span>, <time datetime="2015-08">August 2015</time>, <span>&lt;<a href="https://www.iso.org/standard/64758.html">https://www.iso.org/standard/64758.html</a>&gt;</span>. </dd>
<dt id="RFC2119">[RFC2119]</dt>
<dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<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">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>
<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">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>
<dt id="RFC5646">[RFC5646]</dt>
<dd>
<span class="refAuthor">Phillips, A., Ed.</span><span class="refAuthor"> and M. Davis, Ed.</span>, <span class="refTitle">"Tags for Identifying Languages"</span>, <span class="seriesInfo">BCP 47</span>, <span class="seriesInfo">RFC 5646</span>, <span class="seriesInfo">DOI 10.17487/RFC5646</span>, <time datetime="2009-09">September 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5646">https://www.rfc-editor.org/info/rfc5646</a>&gt;</span>. </dd>
<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">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>
<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">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>
<dt id="RFC8174">[RFC8174]</dt>
<dd>
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
<dt id="RFC8334">[RFC8334]</dt>
<dd>
<span class="refAuthor">Gould, J.</span><span class="refAuthor">, Tan, W.</span><span class="refAuthor">, and G. Brown</span>, <span class="refTitle">"Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)"</span>, <span class="seriesInfo">RFC 8334</span>, <span class="seriesInfo">DOI 10.17487/RFC8334</span>, <time datetime="2018-03">March 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8334">https://www.rfc-editor.org/info/rfc8334</a>&gt;</span>. </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><span class="refAuthor">, and N. Mendelsohn</span>, <span class="refTitle">"XML Schema Part 1: Structures Second Edition"</span>, <span class="seriesInfo">World Wide Web Consortium Recommendation REC-xmlschema-1-20041028</span>, <time datetime="2004-10">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>
</dl>
</section>
<section id="section-9.2">
        <h3 id="name-informative-references">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<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">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>
</dl>
</section>
</section>
<div id="acknowledgements">
<section id="section-appendix.a">
      <h2 id="name-acknowledgements">
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
      </h2>
<p id="section-appendix.a-1">The authors wish to thank the following persons for their feedback and
      suggestions:<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-appendix.a-2.1">
          <p id="section-appendix.a-2.1.1"><span class="contact-name">James Gould</span> of Verisign Inc.<a href="#section-appendix.a-2.1.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.2">
          <p id="section-appendix.a-2.2.1"><span class="contact-name">Luis Munoz</span> of ISC<a href="#section-appendix.a-2.2.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.3">
          <p id="section-appendix.a-2.3.1"><span class="contact-name">Michael Young</span><a href="#section-appendix.a-2.3.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.4">
          <p id="section-appendix.a-2.4.1"><span class="contact-name">Ben Levac</span><a href="#section-appendix.a-2.4.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.5">
          <p id="section-appendix.a-2.5.1"><span class="contact-name">Jeff Eckhaus</span><a href="#section-appendix.a-2.5.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.6">
          <p id="section-appendix.a-2.6.1"><span class="contact-name">Seth Goldman</span> of Google<a href="#section-appendix.a-2.6.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.7">
          <p id="section-appendix.a-2.7.1"><span class="contact-name">Klaus Malorny</span> and <span class="contact-name">Michael Bauland</span> of Knipp<a href="#section-appendix.a-2.7.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.8">
          <p id="section-appendix.a-2.8.1"><span class="contact-name">Jody Kolker</span>, <span class="contact-name">Joe  Snitker</span>, and <span class="contact-name">Kevin Allendorf</span> of GoDaddy<a href="#section-appendix.a-2.8.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.9">
          <p id="section-appendix.a-2.9.1"><span class="contact-name">Michael Holloway</span> of Com Laude<a href="#section-appendix.a-2.9.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.10">
          <p id="section-appendix.a-2.10.1"><span class="contact-name">Santosh Kalsangrah</span> of Impetus Infotech<a href="#section-appendix.a-2.10.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.11">
          <p id="section-appendix.a-2.11.1"><span class="contact-name">Alex Mayrhofer</span> of Nic.at<a href="#section-appendix.a-2.11.1" class="pilcrow">¶</a></p>
</li>
<li id="section-appendix.a-2.12">
          <p id="section-appendix.a-2.12.1"><span class="contact-name">Thomas Corte</span> of Knipp Medien und Kommunikation GmbH<a href="#section-appendix.a-2.12.1" class="pilcrow">¶</a></p>
</li>
</ul>
</section>
</div>
<div id="authors-addresses">
<section id="section-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">Roger Carney</span></div>
<div dir="auto" class="left"><span class="org">GoDaddy Inc.</span></div>
<div dir="auto" class="left"><span class="street-address">14455 N. Hayden Rd. #219</span></div>
<div dir="auto" class="left">
<span class="locality">Scottsdale</span>, <span class="region">AZ</span> <span class="postal-code">85260</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:rcarney@godaddy.com" class="email">rcarney@godaddy.com</a>
</div>
<div class="url">
<span>URI:</span>
<a href="http://www.godaddy.com" class="url">http://www.godaddy.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Gavin Brown</span></div>
<div dir="auto" class="left"><span class="org">CentralNic Group plc</span></div>
<div dir="auto" class="left"><span class="street-address">35-39 Moorgate</span></div>
<div dir="auto" class="left"><span class="locality">London</span></div>
<div dir="auto" class="left"><span class="postal-code">EC2R 6AR</span></div>
<div dir="auto" class="left"><span class="country-name">United Kingdom</span></div>
<div class="tel">
<span>Phone:</span>
<a href="tel:+44%2020%2033%2088%200600" class="tel">+44 20 33 88 0600</a>
</div>
<div class="email">
<span>Email:</span>
<a href="mailto:gavin.brown@centralnic.com" class="email">gavin.brown@centralnic.com</a>
</div>
<div class="url">
<span>URI:</span>
<a href="http://www.centralnic.com" class="url">http://www.centralnic.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jothan Frakes</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:jothan@jothan.com" class="email">jothan@jothan.com</a>
</div>
<div class="url">
<span>URI:</span>
<a href="http://jothan.com" class="url">http://jothan.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>