rfc9022xml2.original.xml   rfc9022.xml 
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [ <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<!-- One method to get references from the online citation libraries.
There has to be one entity for each item to be referenced.
An alternate method (rfc include) is described in the references. -->
<!ENTITY RFC0791 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.0791.xml">
<!ENTITY RFC1952 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.1952.xml">
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.2119.xml">
<!ENTITY RFC2818 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.2818.xml">
<!ENTITY RFC3339 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.3339.xml">
<!ENTITY RFC3688 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.3688.xml">
<!ENTITY RFC3912 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.3912.xml">
<!ENTITY RFC3915 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.3915.xml">
<!ENTITY RFC4180 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.4180.xml">
<!ENTITY RFC5730 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5730.xml">
<!ENTITY RFC5731 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5731.xml">
<!ENTITY RFC5732 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5732.xml">
<!ENTITY RFC5733 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5733.xml">
<!ENTITY RFC5891 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5891.xml">
<!ENTITY RFC5910 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5910.xml">
<!ENTITY RFC5952 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.5952.xml">
<!ENTITY RFC6234 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.6234.xml">
<!ENTITY RFC7942 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.7942.xml">
<!ENTITY RFC8174 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8174.xml">
<!ENTITY RFC8499 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC
.8499.xml">
<!ENTITY I-D.ietf-regext-data-escrow SYSTEM "https://xml2rfc.ietf.org/public/rfc
/bibxml3/reference.I-D.draft-ietf-regext-data-escrow-10.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<?rfc toc="yes"?>
<?rfc strict="yes"?>
<?rfc tocompact="yes"?>
<?rfc compact="no"?>
<?rfc subcompact="no"?>
<?rfc tocdepth="2"?>
<?rfc symrefs="yes"?>
<?rfc comments="yes" ?>
<?rfc sortrefs="yes" ?>
<rfc category="std" ipr="trust200902" docName="draft-ietf-regext-dnrd-objects-ma
pping-11">
<front> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft -ietf-regext-dnrd-objects-mapping-11" number="9022" obsoletes="" updates="" subm issionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true " tocDepth="2" symRefs="true" sortRefs="true" version="3">
<title abbrev="DNRD Objects Mapping"> <!-- xml2rfc v2v3 conversion 3.5.0 -->
<front>
<title abbrev="DNRD Objects Mapping">
Domain Name Registration Data (DNRD) Objects Mapping Domain Name Registration Data (DNRD) Objects Mapping
</title> </title>
<seriesInfo name="RFC" value="9022"/>
<author initials="G." surname="Lozano" fullname="Gustavo Lozano"> <author initials="G." surname="Lozano" fullname="Gustavo Lozano">
<organization abbrev="ICANN"> <organization abbrev="ICANN">
Internet Corporation for Assigned Names and Numbers Internet Corporation for Assigned Names and Numbers
</organization> </organization>
<address> <address>
<postal> <postal>
<street>12025 Waterfront Drive, Suite 300</street> <extaddr>Suite 300</extaddr>
<country>United States of America</country> <street>12025 Waterfront Drive</street>
<code>90292</code> <city>Los Angeles</city> <city>Los Angeles</city>
</postal> <region>CA</region>
<phone>+1.310.823.9358</phone> <code>90292</code>
<email>gustavo.lozano@icann.org</email> <country>United States of America</country>
</address> </postal>
</author> <phone>+1.310.823.9358</phone>
<email>gustavo.lozano@icann.org</email>
<author initials="J." surname="Gould" fullname="James Gould"> </address>
<organization abbrev="VeriSign"> </author>
<author initials="J." surname="Gould" fullname="James Gould">
<organization abbrev="VeriSign">
VeriSign, Inc. VeriSign, Inc.
</organization> </organization>
<address> <address>
<postal> <postal>
<street>12061 Bluemont Way</street> <street>12061 Bluemont Way</street>
<country>United States of America</country> <city>Reston</city>
<code>20190</code> <city>Reston</city> <region>VA</region>
</postal> <code>20190</code>
<email>jgould@verisign.com</email> <country>United States of America</country>
</address> </postal>
</author> <email>jgould@verisign.com</email>
</address>
<author initials="C." surname="Thippeswamy" fullname="Chethan Thippeswam </author>
y"> <author initials="C." surname="Thippeswamy" fullname="Chethan Thippeswamy">
<organization abbrev="VeriSign"> <organization abbrev="VeriSign">
VeriSign, Inc. VeriSign, Inc.
</organization> </organization>
<address> <address>
<postal> <postal>
<street>12061 Bluemont Way</street> <street>12061 Bluemont Way</street>
<country>United States of America</country> <city>Reston</city>
<code>20190</code> <city>Reston</city> <region>VA</region>
</postal> <code>20190</code>
<email>cthippeswamy@verisign.com</email> <country>United States of America</country>
</address> </postal>
</author> <email>cthippeswamy@verisign.com</email>
</address>
<date day="16" month="Dec" year="2020"/> </author>
<date month="May" year="2021"/>
<area> Applications </area> <area> Applications </area>
<keyword>data escrow</keyword>
<keyword>data escrow</keyword> <keyword>registry</keyword>
<keyword>registry</keyword> <keyword>domain name</keyword>
<keyword>domain name</keyword> <keyword>domain name registration data</keyword>
<keyword>domain name registration data</keyword> <abstract>
<t>
<abstract> This document specifies the format, contents, and semantics of
<t> Domain Name Registration Data (DNRD) escrow deposits for a
This document specifies the format, contents and semantics of domain name registry.
Domain Name Registration Data (DNRD) Escrow deposits for a </t>
Domain Name Registry. </abstract>
</t> </front>
</abstract> <middle>
<section numbered="true" toc="default">
</front> <name>Introduction</name>
<t>
<middle>
<section title="Introduction">
<t>
Registry Data Escrow (RDE) is the process by which a registry pe riodically submits data Registry Data Escrow (RDE) is the process by which a registry pe riodically submits data
deposits to a third-party called an escrow agent. These deposits deposits to a third party called an escrow agent. These deposits
comprise the comprise the
minimum data needed by a third-party to resume operations if the minimum data needed by a third party to resume operations if the
registry registry
cannot function and is unable or unwilling to facilitate an cannot function and is unable or unwilling to facilitate an
orderly transfer of service. orderly transfer of service.
For example, for a domain name registry or registrar, the data t o be deposited For example, for a domain name registry or registrar, the data t o be deposited
would include all the objects related to registered domain names , e.g., would include all the objects related to registered domain names , e.g.,
names, contacts, name servers, etc. names, contacts, name servers, etc.
</t> </t>
<t> <t>
The goal of data escrow is higher resiliency of registration services, for the b The goal of data escrow is higher resiliency of registration services for the be
enefit of Internet users. The beneficiaries of a registry are not just those re nefit of Internet users. The beneficiaries of a registry are not just those reg
gistering information there, but also the users of services relying on the regis istering information there, but also the users of services relying on the regist
try data. ry data.
</t> </t>
<t> <t>
In the context of domain name registries, registration data escr ow is In the context of domain name registries, registration data escr ow is
a requirement for generic top-level domains (e.g., Specification a requirement for generic top-level domains (e.g., Specification
2 of the ICANN Base Registry Agreement, see <xref 2 of the ICANN Base Registry Agreement, see <xref target="ICANN-GTLD-RA-2017073
target='ICANN-GTLD-RA-20170731' />) and some country code top-leve 1" format="default"/>) and some country code top-level
l
domain managers are also currently escrowing data. domain managers are also currently escrowing data.
There is also a similar requirement for ICANN-accredited There is also a similar requirement for ICANN-accredited
domain registrars. domain registrars.
</t> </t>
<t> <t>
This document defines the standard set of objects for This document defines the standard set of objects for
a Domain Name Registry that uses the Registry Data Escrow Specif ication described in <xref target="I-D.ietf-regext-data-escrow"/> for escrow. a domain name registry that uses the Registry Data Escrow Specif ication described in <xref target="RFC8909" format="default"/> for escrow.
The set of objects include: The set of objects include:
</t> </t>
<t> <dl spacing="normal">
<list style="symbols"> <dt>
<t> Domain:</dt><dd>Internet domain names that are typically provi
Domain: Internet domain names that are typically provisioned i sioned in a domain name registry using the
n a Domain Name Registry using the Extensible Provisioning Protocol (EPP) domain name mapping <xr
EPP domain name mapping <xref target="RFC5731"/>. The attribut ef target="RFC5731" format="default"/>. The attributes defined in the EPP domain
es defined in the EPP domain name name
mapping <xref target="RFC5731"/> are fully supported by this d mapping <xref target="RFC5731" format="default"/> are fully su
ocument. pported by this document.
</t> </dd>
<t> <dt>
Host: Internet host names that are typically provisioned in a Host:</dt><dd>Internet host names that are typically provision
Domain Name Registry using the EPP host ed in a domain name registry using the EPP host
mapping <xref target="RFC5732"/>. The attributes defined in th mapping <xref target="RFC5732" format="default"/>. The attribu
e EPP host mapping <xref target="RFC5732"/> tes defined in the EPP host mapping <xref target="RFC5732" format="default"/>
are fully supported by this document. are fully supported by this document.
</t> </dd>
<t> <dt>
Contact: Individual or organization social information provisi Contact:</dt><dd>Individual or organization social information
oned in a Domain Name Registry using provisioned in a domain name registry using
the EPP contact mapping <xref target="RFC5733"/>. The attribut the EPP contact mapping <xref target="RFC5733" format="default
es defined in the EPP contact mapping "/>. The attributes defined in the EPP contact mapping
<xref target="RFC5733"/> are fully supported by this document. <xref target="RFC5733" format="default"/> are fully supported
</t> by this document.
<t> </dd>
Registrar: The organization that sponsors objects like domains <dt>
, hosts, and contacts in a Domain Name Registrar:</dt><dd>The organization that sponsors objects like
Registry. domains, hosts, and contacts in a domain name
</t> registry.
<t> </dd>
NNDN (NNDN&apos;s not domain name): Domain Name Registries may <dt>
maintain domain names without being persisted as domain objects in the registry NNDN (NNDN's not domain name):</dt><dd>Domain Name Registries
system, for example, a list of reserved names not available for registration. T may maintain domain names without being persisted as domain objects in the regis
he NNDN is a lightweight domain-like object that is used to escrow domain names try system, for example, a list of reserved names not available for registration
not maintained as domain name objects. . The NNDN is a lightweight domain-like object that is used to escrow domain nam
</t> es not maintained as domain name objects.
</list> </dd>
</t> </dl>
<t> <t>
This document defines the following pseudo-objects: This document defines the following pseudo-objects:
</t> </t>
<t> <dl spacing="normal">
<list style="symbols"> <dt>
<t> IDN table reference:</dt><dd>Internationalized Domain Na
IDN Table Reference: Internationalized Domain Names (IDN mes (IDN) included in the domain object data escrow
) included in the Domain Object Data Escrow include references to the IDN table and policy used in I
include references to the IDN Table and Policy used in I DN registration.
DN registration. </dd>
</t> <dt>
<t> EPP parameters:</dt><dd>Contains the EPP parameters supp
EPP parameters: Contains the EPP parameters supported by orted by the registry operator.
the Registry Operator. </dd>
</t> <dt>
<t> Header:</dt><dd>Used to specify counters of objects in t
Header: Used to specify counters of objects in the datab he database at a certain point in time (Timeline Watermark).
ase at a certain point in time (watermark). </dd>
</t> <dt>
<t> Policy:</dt><dd>Used to specify <bcp14>OPTIONAL</bcp14>
Policy: Used to specify OPTIONAL elements from this spec elements from this specification that are <bcp14>REQUIRED</bcp14> based on
ification that are REQUIRED based on
the business model of the registry. the business model of the registry.
</t> </dd>
</list> </dl>
</t> <t>Extensible Markup Language (XML) 1.0 as described in <xref target="W3C.
REC-xml-20081126" format="default"/> and XML Schema notation as described in <xr
<t>Extensible Markup Language (XML) 1.0 as described in <xref target ef target="W3C.REC-xmlschema-1-20041028" format="default"/> and <xref target="W3
='W3C.REC-xml-20081126' /> and XML Schema notation as described in <xref target= C.REC-xmlschema-2-20041028" format="default"/> are used in this specification.
'W3C.REC-xmlschema-1-20041028' /> and <xref target='W3C.REC-xmlschema-2-20041028 </t>
' /> are used in this specification. </section>
</t> <section anchor="models" numbered="true" toc="default">
</section> <name>Models</name>
<t>
<section title="Models" anchor="models">
<t>
This document defines two different models that can be used to This document defines two different models that can be used to
deposit data escrow objects: XML and CSV. deposit data escrow objects: XML and CSV (comma-separated values
</t> ).
<t> </t>
The data escrow deposit MAY contain a mix of both models but an o <t>
bject MUST The data escrow deposit <bcp14>MAY</bcp14> contain a mix of both
models, but an object <bcp14>MUST</bcp14>
be escrowed only in one model. be escrowed only in one model.
</t> </t>
<t> <t>
This document does not suggest the use of a particular model, and both are equivalent. This document does not suggest the use of a particular model, and both are equivalent.
A Domain Name Registry may choose the model that is more appropr iate for the peculiarities of its systems. A domain name registry may choose the model that is more appropr iate for the peculiarities of its systems.
For example, a registry may use the CSV-export functionality of the Relational Database Management System (RDBMS) for escrow; For example, a registry may use the CSV-export functionality of the Relational Database Management System (RDBMS) for escrow;
therefore, the CSV model may be more appropriate. therefore, the CSV model may be more appropriate.
Another registry may use the code developed for EPP to implement escrow. Another registry may use the code developed for EPP to implement escrow.
</t> </t>
<section numbered="true" toc="default">
<section title="XML Model"> <name>XML Model</name>
<t> <t>
XML: The XML model includes all the deposit information The XML model includes all the deposit information (meta
(meta-data data
and data) in an XML document. The definition of the XML format is and data) in an XML document. The definition of the XML format is
fully defined in the XML schemas. As a convention, the objects represented fully defined in the XML schemas. As a convention, the objects represented
using the XML model are referenced using RDE and an XML namespace that is using the XML model are referenced using RDE and an XML namespace that is
prefixed with "rde". For example, the Domain Name objec t represented using prefixed with "rde". For example, the Domain Name objec t represented using
the XML model can be referred to as the RDE Domain Name with the XML the XML model can be referred to as the RDE Domain Name with the XML
namespace including rdeDomain (urn:ietf:params:xml:ns:rd eDomain-1.0). namespace including rdeDomain (urn:ietf:params:xml:ns:rd eDomain-1.0).
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="CSV Model"> <name>CSV Model</name>
<t> <t>
CSV: The CSV model uses XML to define the data escrow fo The CSV model uses XML to define the data escrow format
rmat of the of the
data contained in referenced Comma-Separated Values (CSV data contained in referenced CSV files. As a
) files. As a
convention, the objects represented using the CSV model is referenced convention, the objects represented using the CSV model is referenced
using CSV and an XML namespace that is prefixed with "cs v". For example, using CSV and an XML namespace that is prefixed with "cs v". For example,
the Domain Name object represented using the CSV model c an be referred the domain name object represented using the CSV model c an be referred
to as the CSV Domain Name with the XML namespace includi ng csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). to as the CSV Domain Name with the XML namespace includi ng csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0).
</t> </t>
</section>
</section> </section>
<section numbered="true" toc="default">
</section> <name>Terminology</name>
<section title="Terminology">
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when
, and only when, they
appear in all capitals, as shown here.
</t>
<section anchor="glossary" title="Glossary">
<t> <t>
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be interpreted as
described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/>
when, and only when, they appear in all capitals, as shown here.
</t>
<section anchor="glossary" numbered="true" toc="default">
<name>Glossary</name>
<t>
In the following section, the most common terms are briefly explained: In the following section, the most common terms are briefly explained:
<list style='symbols'> </t>
<dl spacing="normal">
<t> <dt>
Allocated: a status of some label with respect to a zone, whereby th Allocated:</dt><dd>A status of some label with respect to a zone, wh
e label is associated administratively ereby the label is associated administratively
to some entity that has requested the label. This term (and its cogn to some entity that has requested the label. This term (and its cogn
ates “allocation” and “to allocate”) ates "allocation" and "to allocate")
may represent the first step on the way to delegation in the DNS. may represent the first step on the way to delegation in the DNS.
</t> </dd>
<t> <dt>
Comma-Separated Values (CSV), see <xref target='RFC4180' />. Comma-Separated Values (CSV): </dt><dd> See <xref target="RFC4180" f
</t> ormat="default"/>.
<t> </dd>
Domain name: see definition of Domain name in <xref target='RFC8499' <dt>
/>. Domain Name:</dt><dd>See the definition of Domain Name in <xref targ
</t> et="RFC8499" section="2" sectionFormat="of" format="default"/>.
<t> </dd>
Extensible Provisioning Protocol (EPP), see definition of the Extens <dt>
ible Provisioning Protocol in <xref target='RFC8499' />. Extensible Provisioning Protocol (EPP): </dt><dd>See the definition
</t> of the Extensible Provisioning Protocol in <xref target="RFC8499" section="9" se
<t> ctionFormat="of" format="default"/>.
Fully-Qualified Domain Name (FQDN), see definition of FQDN in <xref </dd>
target='RFC8499' />. <dt>
</t> Fully-Qualified Domain Name (FQDN): </dt><dd>See the definition of F
<t> QDN in <xref target="RFC8499" section="2" sectionFormat="of" format="default"/>.
Internationalized Domain Name (IDN), see definition of International </dd>
ized Domain Name in <xref target='RFC8499' />. <dt>
</t> Internationalized Domain Name (IDN): </dt><dd>See the definition of
<t> Internationalized Domain Name in <xref target="RFC8499" section="2" sectionForma
Label: see definition of Label in <xref target='RFC8499' />. t="of" format="default"/>.
</t> </dd>
<t> <dt>
Registrant: see definition of Registrant in <xref target='RFC8499' / Label</dt><dd>See the definition of Label in <xref target="RFC8499"
>. section="2" sectionFormat="of" format="default"/>.
</t> </dd>
<t> <dt>
Registrar: see definition of Registrar in <xref target='RFC8499' />. Registrant:</dt><dd>See the definition of Registrant in <xref target
</t> ="RFC8499" section="9" sectionFormat="of" format="default"/>.
<t> </dd>
Registry: see definition of Registry in <xref target='RFC8499' />. <dt>
</t> Registrar:</dt><dd>See the definition of Registrar in <xref target="
<t> RFC8499" section="9" sectionFormat="of" format="default"/>.
Registry-class domain name (RCDN): refers to a top-level domain (TLD </dd>
) or any other domain name at any <dt>
level in the DNS tree for which a Registry (either directly or throu Registry:</dt><dd>See the definition of Registry in <xref target="RF
gh an affiliate company) provides C8499" section="9" sectionFormat="of" format="default"/>.
</dd>
<dt>
Registry-Class Domain Name (RCDN):</dt><dd>Refers to a top-level dom
ain (TLD) or any other domain name at any
level in the DNS tree for which a registry (either directly or throu
gh an affiliate company) provides
Registry Services for other organizations or individuals. For exampl e: .COM, .ORG, .BIZ, .CO.JP, .B.BR. Registry Services for other organizations or individuals. For exampl e: .COM, .ORG, .BIZ, .CO.JP, .B.BR.
</t> </dd>
<t> <dt>
Registry Data Escrow (RDE): registry data escrow is the process by w Registry Data Escrow (RDE):</dt><dd>Registry Data Escrow is the proc
hich a registry periodically submits data ess by which a registry periodically submits data
deposits to a third-party called an escrow agent. These deposits com deposits to a third party called an escrow agent. These deposits com
prise the prise the
minimum data needed by a third-party to resume operations if the reg minimum data needed by a third party to resume operations if the reg
istry istry
cannot function and is unable or unwilling to facilitate an cannot function and is unable or unwilling to facilitate an
orderly transfer of service. orderly transfer of service.
</t> </dd>
<t> <dt>
Registry services: services offered by the Registry critical to the Registry Services:</dt><dd>Services offered by the registry critical
following tasks: the provisioning of to the following tasks: the provisioning of
domain names on receipt of requests and data from registrars; respon ding to registrar queries for domain names on receipt of requests and data from registrars; respon ding to registrar queries for
status information relating to the DNS servers for the RCDN; dissemi nation of RCDN zone files; status information relating to the DNS servers for the RCDN; dissemi nation of RCDN zone files;
operation of the Registry DNS servers; responding to queries for con operation of the registry DNS servers; responding to queries for con
tact and other information concerning tact and other information concerning
DNS registrations in the RCDN; and any other products or services th DNS registrations in the RCDN; and any other products or services th
at only a Registry is capable of at only a registry is capable of
providing, by reason of its designation as the Registry. Typical exa providing, by reason of its designation as the registry. Typical exa
mples of Registry Services are mples of Registry Services are
DNS resolution for the RCDN, WHOIS and EPP. DNS resolution for the RCDN, WHOIS, and EPP.
</t> </dd>
<t> <dt>
SRS: Shared Registration System, see also <xref target='ICANN-GTLD-A SRS:</dt><dd>Shared Registration System, see also <xref target="ICAN
GB-20120604' />. N-GTLD-AGB-20120604" format="default"/>.
</t> </dd>
<t> <dt>
Top-Level Domain Name (TLD), see definition of Top-Level Domain in < Top-Level Domain Name (TLD): </dt><dd>See the definition of Top-Leve
xref target='RFC8499' />. l Domain in <xref target="RFC8499" section="2" sectionFormat="of" format="defaul
</t> t"/>.
<t> </dd>
UTC: Coordinated Universal Time, as maintained by the <dt>
Bureau International des Poids et Mesures (BIPM); see UTC:</dt><dd>Coordinated Universal Time, as maintained by the
also <xref target='RFC3339' />. Bureau International des Poids et Mesures (BIPM), see
</t> also <xref target="RFC3339" format="default"/>.
</dd>
</list> </dl>
</section>
</t>
</section> </section>
<section numbered="true" toc="default">
</section> <name>Conventions Used in This Document</name>
<section numbered="true" toc="default">
<section title="Conventions Used in This Document"> <name>Date and Time</name>
<t>
<section title="Date and Time">
<t>
Numerous fields indicate "dates", such as the creation and e xpiry dates for domain names. These fields Numerous fields indicate "dates", such as the creation and e xpiry dates for domain names. These fields
SHALL contain timestamps indicating the date and time in UTC as specified in <xref target="RFC3339"/>, <bcp14>SHALL</bcp14> contain timestamps indicating the date and time in UTC as specified in <xref target="RFC3339" format="default"/>,
with no offset from the zero meridian. with no offset from the zero meridian.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Country names"> <name>Country Names</name>
<t> <t>
Country identifiers SHALL be represented using two character Country identifiers <bcp14>SHALL</bcp14> be represented usin
identifiers as specified in g two character identifiers as specified in
<xref target="ISO-3166-1"/>. <xref target="ISO-3166-1" format="default"/>.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Telephone numbers"> <name>Telephone Numbers</name>
<t> <t>
Telephone numbers (both voice and facsimile) SHALL be formatted ba Telephone numbers (both voice and facsimile) <bcp14>SHALL</bcp14>
sed on structures defined in be formatted based on structures defined in
<xref target="ITU-E164"/>. Telephone numbers described in this spe <xref target="ITU-E164" format="default"/>. Telephone numbers desc
cification are character strings ribed in this specification are character strings
that MUST begin with a plus sign ("+", ASCII value 0x2B), followed that <bcp14>MUST</bcp14> begin with a plus sign ("+", ASCII value
by a country code defined in 0x2B), followed by a country code defined in
<xref target="ITU-E164"/>, followed by a dot (".", ASCII value 0x2 <xref target="ITU-E164" format="default"/>, followed by a dot ("."
E), followed by a sequence of , ASCII value 0x2E), followed by a sequence of
digits representing the telephone number. digits representing the telephone number.
</t> </t>
</section> </section>
<section anchor="checksum" numbered="true" toc="default">
<section title="CSV Integrity Check" anchor="checksum"> <name>CSV Integrity Check</name>
<t> <t>
A checksum MAY be used to verify the integrity of the CSV file A checksum <bcp14>MAY</bcp14> be used to verify the integrity
s, for example, if another layer (i.e., encryption of an archive containing the of the CSV files, for example, if another layer (i.e., encryption of an archive
deposit files) does not provide integrity. By default the CRC32 algorithm (see, containing the deposit files) does not provide integrity. By default, the CRC32
8.1.1.6.2 of <xref target="V42"/>) is used. A stronger algorithm, such as SHA-25 algorithm (see Section 8.1.1.6.2 of <xref target="V42" format="default"/>) is us
6 (see, <xref target="RFC6234"/>) MAY be used for enhanced security if required. ed. A stronger algorithm, such as SHA-256 (see <xref target="RFC6234" format="de
</t> fault"/>) <bcp14>MAY</bcp14> be used for enhanced security if required.
</section> </t>
</section>
<section title="IP addresses"> <section numbered="true" toc="default">
<t> <name>IP Addresses</name>
The syntax of IP addresses MUST conform to the text representation <t>
of either Internet Protocol Version 4 <xref target="RFC0791"/> The syntax of IP addresses <bcp14>MUST</bcp14> conform to the text
or Internet Protocol Version 6 <xref target="RFC5952"/>. representation of either Internet Protocol Version 4 <xref target="RFC0791" for
</t> mat="default"/>
</section> or Internet Protocol Version 6 <xref target="RFC5952" format="defa
ult"/>.
<section title="Conventions applicable to the CSV Model"> </t>
</section>
<section title="CSV Parent Child Relationship" anchor="csvParentC <section numbered="true" toc="default">
hildRelationship"> <name>Conventions Applicable to the CSV Model</name>
<t> <section anchor="csvParentChildRelationship" numbered="true" toc="defaul
The CSV model represents a relational model, where the CSV files r t">
epresent relational tables, the fields of the CSV files represent columns of the <name>CSV Parent Child Relationship</name>
tables, and each line of the CSV file <t>
The CSV model represents a relational model where the CSV files re
present relational tables, the fields of the CSV files represent columns of the
tables, and each line of the CSV file
represents a record. As in a relational model, the CSV files can have relationships utilizing primary keys in the parent CSV file definitions and represents a record. As in a relational model, the CSV files can have relationships utilizing primary keys in the parent CSV file definitions and
foreign keys in the child CSV file definitions for a 1-to-many rel ationship. The primary keys are not explicitly defined, but the foreign keys ar e using the foreign keys in the child CSV file definitions for a one-to-many r elationship. The primary keys are not explicitly defined, but the foreign keys are using the
boolean "parent" field attribute in the child CSV file. The relat ionships between the CSV files are used to support a cascade replace or cascade delete of records starting boolean "parent" field attribute in the child CSV file. The relat ionships between the CSV files are used to support a cascade replace or cascade delete of records starting
from the parent record in Differential and Incremental Deposits (s from the parent record in Differential and Incremental Deposits (s
ee <xref target="I-D.ietf-regext-data-escrow"/>). ee <xref target="RFC8909" format="default"/>).
</t> </t>
<t> <t keepWithNext="true">
<figure> The following is an example of the CSV file d
<preamble> efinitions, using the element &lt;rdeCsv:csv&gt; (see <xref target="rdeCsv-csv"
The following is an example of the CSV file d format="default"/>), for a Sample object consisting of a parent "sample" CSV Fil
efinitions, using the element &lt;rdeCsv:csv&gt; (see <xref target="rdeCsv-csv"/ e Definition
>), for a Sample object consisting of a parent "sample" CSV File Definition
and a child "sampleStatuses" CSV File Def inition. The primary key for the Sample object is the field &lt;csvSample:fName &gt; that is and a child "sampleStatuses" CSV File Def inition. The primary key for the Sample object is the field &lt;csvSample:fName &gt; that is
used as the foreign key in the "sampleSta tuses" CSV File Definition by specifying the "parent=true" attribute. If a Samp le record is updated used as the foreign key in the "sampleSta tuses" CSV File Definition by specifying the "parent=true" attribute. If a Samp le record is updated
or deleted in a Differential or Increment al Deposit, it should cascade replace the data using the records included in the child "sampleStatuses" or deleted in a Differential or Increment al Deposit, it should cascade replace the data using the records included in the child "sampleStatuses"
CSV File Definition or cascade delete the existing records in the child "sampleStatuses" CSV File Definition, respectivel y. CSV File Definition or cascade delete the existing records in the child "sampleStatuses" CSV File Definition, respectivel y.
</preamble> </t>
<artwork><![CDATA[ <sourcecode markers="false" name="" type="xml"><![CDATA[
<csvSample:contents> <csvSample:contents>
... ...
<rdeCsv:csv name="sample" sep=","> <rdeCsv:csv name="sample" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvSample:fName/> <csvSample:fName/>
<rdeCsv:fClID/> <rdeCsv:fClID/>
<rdeCsv:fCrRr/> <rdeCsv:fCrRr/>
<rdeCsv:fCrID/> <rdeCsv:fCrID/>
<rdeCsv:fCrDate/> <rdeCsv:fCrDate/>
<rdeCsv:fUpRr/> <rdeCsv:fUpRr/>
skipping to change at line 424 skipping to change at line 369
<rdeCsv:fLang/> <rdeCsv:fLang/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="EB9C558E"> cksum="EB9C558E">
sampleStatuses-YYYYMMDD.csv sampleStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvSample:contents>]]> </csvSample:contents>
</artwork> ]]></sourcecode>
</figure> </section>
</t> <section anchor="csvElements" numbered="true" toc="default">
</section> <name>CSV Elements</name>
<section anchor="rdeCsv-csv" numbered="true" toc="default">
<section title="CSV elements" anchor="csvElements"> <name>&lt;rdeCsv:csv&gt; Element</name>
<section title="&lt;rdeCsv:csv&gt; element" anchor="rdeCsv-csv"> <t>
<t>
To support the CSV model, an element is defined To support the CSV model, an element is defined
for each object that substitutes for the &lt;rde:content&gt; element and f or the &lt;rde:delete&gt; element, that contains one or more for each object that substitutes for the &lt;rde:content&gt; element and f or the &lt;rde:delete&gt; element, that contains one or more
&lt;rdeCsv:csv&gt; elements. For example, the <xref target="domainNameObj ect">Domain Name Object</xref> defines the &lt;csvDomain:contents&gt; element, t hat substitutes for the &lt;rde:content&gt; element, &lt;rdeCsv:csv&gt; elements. For example, the <xref target="domainNameObj ect" format="default">'Domain Name Object'</xref> defines the &lt;csvDomain:cont ents&gt; element, that substitutes for the &lt;rde:content&gt; element,
and the &lt;csvDomain:deletes&gt; element, that substitutes for the &lt;rd e:delete&gt; element. Both the &lt;csvDomain:contents&gt; element and the and the &lt;csvDomain:deletes&gt; element, that substitutes for the &lt;rd e:delete&gt; element. Both the &lt;csvDomain:contents&gt; element and the
&lt;csvDomain:deletes&gt; elements contain one or more &lt;rdeCsv:csv&gt; elements. &lt;csvDomain:deletes&gt; elements contain one or more &lt;rdeCsv:csv&gt; elements.
The &lt;rdeCsv:csv&gt; element has the following child element s:</t> The &lt;rdeCsv:csv&gt; element has the following child element s:</t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fields&gt;">Ordered list of CSV fiel <dt>&lt;rdeCsv:fields&gt;</dt>
ds used in the CSV files. There are one or more <dd>Ordered list of CSV fields used in the CSV files. There are o
ne or more
child elements that substitute for the &lt;rdeCsv:field&gt; abstract element. Each element child elements that substitute for the &lt;rdeCsv:field&gt; abstract element. Each element
defines the format of the CSV field contained in the CSV fil es. The &lt;rdeCsv:field&gt; elements defines the format of the CSV field contained in the CSV fil es. The &lt;rdeCsv:field&gt; elements
support the "type" attribute that defines the XML simple dat a type of the field element. The &lt;rdeCsv:field&gt; support the "type" attribute that defines the XML simple dat a type of the field element. The &lt;rdeCsv:field&gt;
elements support the "isRequired" attribute, with a default elements support the "isRequired" attribute, which has a def
value of "false", when set to "true" indicates that the field must be non-empty ault value of "false". When set to "true", this indicates that the field must be
in the CSV files and when set to "false" indicates that the non-empty
field MAY be empty in the CSV files. The "isRequired" in the CSV files, and when set to "false", this indicates th
attribute MAY be specifically set for the field elements wit at the field <bcp14>MAY</bcp14> be empty in the CSV files. The "isRequired"
hin the XML schema and MAY be overridden when specifying attribute <bcp14>MAY</bcp14> be specifically set for the fie
the fields under the &lt;rdeCsv:fields&gt; element. The &lt ld elements within the XML schema and <bcp14>MAY</bcp14> be overridden when spec
;rdeCsv:field&gt; element supports an OPTIONAL "parent" attribute ifying
that identifies the field as a reference to a parent object, the fields under the &lt;rdeCsv:fields&gt; element. The &lt
as defined in <xref target="csvParentChildRelationship">CSV Parent Child Relati ;rdeCsv:field&gt; element supports an <bcp14>OPTIONAL</bcp14> "parent" attribute
onship</xref>. that identifies the field as a reference to a parent object,
For example, the &lt;rdeCsv:csv name="domainStatuses"&gt; &l as defined in the <xref target="csvParentChildRelationship" format="default">'C
t;csvDomain:fName&gt; field SHOULD SV Parent Child Relationship'</xref>.
set the "parent" attribute to "true" to identify it as the p For example, the &lt;rdeCsv:csv name="domainStatuses"&gt; &l
arent domain name of the domain status.</t> t;csvDomain:fName&gt; field <bcp14>SHOULD</bcp14>
<t hangText="&lt;rdeCsv:files&gt;">A list of one or more CSV set the "parent" attribute to "true" to identify it as the p
files using the &lt;rdeCsv:file&gt; child element. arent domain name of the domain status.</dd>
<dt>&lt;rdeCsv:files&gt;</dt>
<dd><t>A list of one or more CSV files using the &lt;rdeCsv:file&g
t; child element.
The &lt;rdeCsv:file&gt; child element defines a reference to the CSV file name and has the following optional attributes:</t> The &lt;rdeCsv:file&gt; child element defines a reference to the CSV file name and has the following optional attributes:</t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="compression">If the CSV file is compressed, t <dt>compression</dt>
he "compression" attribute defines the compression format. For example, setting <dd>If the CSV file is compressed, the "compression" attribute
this attribute to "gzip" signals that the CSV file is compressed using the GZIP defines the compression format. For example, setting this attribute to "gzip" s
file format (see, <xref target="RFC1952"/>). The supported compression formats a ignals that the CSV file is compressed using the GZIP file format (see <xref tar
re negotiated out-of-band. get="RFC1952" format="default"/>). The supported compression formats are negotia
</t> ted out of band.
<t hangText="encoding">Defines the encoding of the CSV fil </dd>
e with the default encoding of "UTF-8". <dt>encoding</dt>
</t> <dd>Defines the encoding of the CSV file with the default enco
<t hangText="cksum">Defines the checksum of the CSV file, ding of "UTF-8".
as described in <xref target="checksum"/>, using the algorithm defined by the "c </dd>
ksumAlg" attribute. If the "cksumAlg" attribute is not present, the checksum is <dt>cksum</dt>
calculated using "CRC32". <dd>Defines the checksum of the CSV file, as described in <xre
</t> f target="checksum" format="default"/>, using the algorithm defined by the "cksu
<t hangText="cksumAlg">Defines the checksum algorithm used mAlg" attribute. If the "cksumAlg" attribute is not present, the checksum is cal
to calculate the "cksum" attribute, with the default value of "CRC32". If the v culated using "CRC32".
alue "SHA256" is specified, the SHA-256 algorithm (see, <xref target="RFC6234"/> </dd>
) MUST be used to calculate the "cksum" attribute. Parties receiving and process <dt>cksumAlg</dt>
ing data escrow deposits MUST support CRC32 and SHA-256. If this attribute is pr <dd>Defines the checksum algorithm used to calculate the "cksu
esent, the "cksum" attribute MUST also be present. Additional checksum algorithm m" attribute, with the default value of "CRC32". If the value "SHA256" is specif
s are negotiated out-of-band. ied, the SHA-256 algorithm (see <xref target="RFC6234" format="default"/>) <bcp1
</t> 4>MUST</bcp14> be used to calculate the "cksum" attribute. Parties receiving and
</list></t> processing data escrow deposits <bcp14>MUST</bcp14> support CRC32 and SHA-256.
</list></t> If this attribute is present, the "cksum" attribute <bcp14>MUST</bcp14> also be
<t>The &lt;rdeCsv:csv&gt; element requires a "name" attribute present. Additional checksum algorithms are negotiated out of band.
that defines the </dd>
</dl>
</dd>
</dl>
<t>The &lt;rdeCsv:csv&gt; element requires a "name" attribute that d
efines the
purpose of the CSV file with values like "domain", "host", "co ntact". The supported "name" attribute values purpose of the CSV file with values like "domain", "host", "co ntact". The supported "name" attribute values
are defined for each object type. The OPTIONAL "sep" attribut are defined for each object type. The <bcp14>OPTIONAL</bcp14>
e defines the CSV separator character with the default separator character of ", "sep" attribute defines the CSV separator character with the default separator
". The need for quoting/escaping of the CSV data could be avoided by choosing a character of ",". The need for quoting or escaping of the CSV data could be avoi
separator character that is not in the data set of the CSV files. ded by choosing a separator character that is not in the data set of the CSV fil
</t> es.
<t> </t>
<figure> <t keepWithNext="true">
<preamble>
The following is an example of the &lt;csvDomain:con tents&gt; &lt;rdeCsv:csv&gt; element for domain name records The following is an example of the &lt;csvDomain:con tents&gt; &lt;rdeCsv:csv&gt; element for domain name records
where the &lt;rdeCsv:fRegistrant&gt; is set as requi red with isRequired="true". where the &lt;rdeCsv:fRegistrant&gt; is set as requi red with isRequired="true".
</preamble> </t>
<artwork><![CDATA[ <sourcecode markers="false" name="" type="xml"><![CDATA[
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domain" sep=","> <rdeCsv:csv name="domain" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
<rdeCsv:fIdnTableId/> <rdeCsv:fIdnTableId/>
<csvDomain:fOriginalName/> <csvDomain:fOriginalName/>
<rdeCsv:fRegistrant isRequired="true"/> <rdeCsv:fRegistrant isRequired="true"/>
<rdeCsv:fClID/> <rdeCsv:fClID/>
skipping to change at line 501 skipping to change at line 450
<rdeCsv:fExDate/> <rdeCsv:fExDate/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="75E2D01F"> cksum="75E2D01F">
domain-YYYYMMDD.csv domain-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents>]]> </csvDomain:contents>
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the domain-YYYYMMDD.c
<t> sv file
<figure>
<preamble>
The following is example of the "domain-YYYYMMDD.csv
" file
with one record matching the &lt;rdeCsv:fields&gt; d efinition. with one record matching the &lt;rdeCsv:fields&gt; d efinition.
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX,
clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z]]> 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
</artwork> ]]></artwork>
</figure> <t keepWithNext="true">
</t>
<t>
<figure>
<preamble>
The following is an example of the &lt;csvDomain:del etes&gt; &lt;rdeCsv:csv&gt; element for domain name records. The following is an example of the &lt;csvDomain:del etes&gt; &lt;rdeCsv:csv&gt; element for domain name records.
</preamble> </t>
<artwork><![CDATA[ <sourcecode markers="false" name="" type="xml"><![CDATA[
<csvDomain:deletes> <csvDomain:deletes>
... ...
<rdeCsv:csv name="domain"> <rdeCsv:csv name="domain">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="6F2B988F"> cksum="6F2B988F">
domain-delete-YYYYMMDD.csv domain-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:deletes>]]> </csvDomain:deletes>
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is example of the domain-delete-YYYYMM
<t> DD.csv file
<figure>
<preamble>
The following is example of the "domain-delete-YYYYM
MDD.csv" file
with three records that matches the single &lt;csvDo main:fName&gt; field. with three records that matches the single &lt;csvDo main:fName&gt; field.
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1.example domain1.example
domain2.example domain2.example
domainN.example]]> domainN.example
</artwork> ]]></artwork>
</figure> </section>
</t>
</section> <section anchor="csvCommonFieldElements" numbered="true" toc="default"
<section title="CSV common field elements" anchor="csvCommonFieldE >
lements"> <name>CSV Common Field Elements</name>
<t>The &lt;rdeCsv:fields&gt; element defined in the <t>The &lt;rdeCsv:fields&gt; element defined in the
<xref target="rdeCsv-csv">&lt;rdeCsv:csv&gt; element</xref> <xref target="rdeCsv-csv" format="default">'&lt;rdeCsv:csv&gt; E
section has child elements that substitute for the abstract &lt; lement'</xref>
rdeCsv:field&gt; element. has child elements that substitute for the abstract &lt;rdeCsv:f
By convention &lt;rdeCsv:field&gt; elements include an 'f' prefi ield&gt; element.
x to identify them as field By convention, &lt;rdeCsv:field&gt; elements include an "f" pref
ix to identify them as field
definition elements. There are a set of common field elements t hat are used across definition elements. There are a set of common field elements t hat are used across
multiple data escrow objects. The common field elements are def ined using the multiple data escrow objects. The common field elements are def ined using the
"urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and using the "rde Csv" sample namespace prefix. "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and using the "rde Csv" sample namespace prefix.
The CSV common field elements include: The CSV common field elements include:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fUName&gt;">UTF-8 encoded name field w <dt>&lt;rdeCsv:fUName&gt;</dt>
ith type="eppcom:labelType". <dd>UTF-8 encoded name field with type="eppcom:labelType".
</t> </dd>
<t hangText="&lt;rdeCsv:fRoid&gt;">Repository Object IDentifie <dt>&lt;rdeCsv:fRoid&gt;</dt>
r (ROID) field with type="eppcom:roidType" and isRequired="true". <dd>Repository Object IDentifier (ROID) field with type="eppcom:ro
</t> idType" and isRequired="true".
<t hangText="&lt;rdeCsv:fRegistrant&gt;">Registrant contact id </dd>
entifier with type="eppcom:clIDType". <dt>&lt;rdeCsv:fRegistrant&gt;</dt>
</t> <dd>Registrant contact identifier with type="eppcom:clIDType".
<t hangText="&lt;rdeCsv:fStatusDescription&gt;">The object st </dd>
atus description, which is free form text describing the rationale for the statu <dt>&lt;rdeCsv:fStatusDescription&gt;</dt>
s, with type="normalizedString". <dd>The object status description, which is free-form text descri
</t> bing the rationale for the status, with type="normalizedString".
<t hangText="&lt;rdeCsv:fClID&gt;">Identifier of the client (r </dd>
egistrar) that sponsors the object with type="eppcom:clIDType" and isRequired="t <dt>&lt;rdeCsv:fClID&gt;</dt>
rue". <dd>Identifier of the client (registrar) that sponsors the object
</t> with type="eppcom:clIDType" and isRequired="true".
<t hangText="&lt;rdeCsv:fCrRr&gt;">Identifier of the registrar </dd>
, defined in <xref target="registrarObject"/>, of the client that created the ob <dt>&lt;rdeCsv:fCrRr&gt;</dt>
ject with type="eppcom:clIDType". <dd>Identifier of the registrar, defined in <xref target="registra
</t> rObject" format="default"/>, of the client that created the object with type="ep
<t hangText="&lt;rdeCsv:fCrID&gt;">Identifier of the client th pcom:clIDType".
at created the object with type="eppcom:clIDType". </dd>
</t> <dt>&lt;rdeCsv:fCrID&gt;</dt>
<t hangText="&lt;rdeCsv:fUpRr&gt;">Identifier of the registrar <dd>Identifier of the client that created the object with type="ep
, defined in <xref target="registrarObject"/>, of the client that last updated t pcom:clIDType".
he object with type="eppcom:clIDType". </dd>
</t> <dt>&lt;rdeCsv:fUpRr&gt;</dt>
<t hangText="&lt;rdeCsv:fUpID&gt;">Identifier of the client th <dd>Identifier of the registrar, defined in <xref target="registra
at last updated the object with type="eppcom:clIDType". rObject" format="default"/>, of the client that last updated the object with typ
</t> e="eppcom:clIDType".
<t hangText="&lt;rdeCsv:fReRr&gt;">Identifier of the registrar </dd>
, defined in <xref target="registrarObject"/>, of the client that requested the <dt>&lt;rdeCsv:fUpID&gt;</dt>
transfer with type="eppcom:clIDType" and isRequired="true". <dd>Identifier of the client that last updated the object with typ
</t> e="eppcom:clIDType".
<t hangText="&lt;rdeCsv:fReID&gt;">Identifier of the client th </dd>
at requested the transfer with type="eppcom:clIDType". <dt>&lt;rdeCsv:fReRr&gt;</dt>
</t> <dd>Identifier of the registrar, defined in <xref target="registra
<t hangText="&lt;rdeCsv:fAcRr&gt;">Identifier of the registrar rObject" format="default"/>, of the client that requested the transfer with type
, defined in <xref target="registrarObject"/>, of the client that should take or ="eppcom:clIDType" and isRequired="true".
took action with type="eppcom:clIDType" and isRequired="true". </dd>
</t> <dt>&lt;rdeCsv:fReID&gt;</dt>
<t hangText="&lt;rdeCsv:fAcID&gt;">Identifier of the client th <dd>Identifier of the client that requested the transfer with type
at should take or took action for transfer with type="eppcom:clIDType". ="eppcom:clIDType".
</t> </dd>
<t hangText="&lt;rdeCsv:fCrDate&gt;">Created date of object wi <dt>&lt;rdeCsv:fAcRr&gt;</dt>
th type="dateTime". <dd>Identifier of the registrar, defined in <xref target="registra
</t> rObject" format="default"/>, of the client that should take or took action with
<t hangText="&lt;rdeCsv:fUpDate&gt;">Updated date of object wi type="eppcom:clIDType" and isRequired="true".
th type="dateTime". </dd>
</t> <dt>&lt;rdeCsv:fAcID&gt;</dt>
<t hangText="&lt;rdeCsv:fExDate&gt;">Expiration date of object <dd>Identifier of the client that should take or took action for t
with type="dateTime". ransfer with type="eppcom:clIDType".
</t> </dd>
<t hangText="&lt;rdeCsv:fReDate&gt;">Date that transfer was re <dt>&lt;rdeCsv:fCrDate&gt;</dt>
quested with type="dateTime" and isRequired="true". <dd>Created date of object with type="dateTime".
</t> </dd>
<t hangText="&lt;rdeCsv:fAcDate&gt;">Date that transfer action <dt>&lt;rdeCsv:fUpDate&gt;</dt>
should be taken or has been taken with type="dateTime" and isRequired="true". <dd>Updated date of object with type="dateTime".
</t> </dd>
<t hangText="&lt;rdeCsv:fTrDate&gt;">Date of last transfer wit <dt>&lt;rdeCsv:fExDate&gt;</dt>
h type="dateTime". <dd>Expiration date of object with type="dateTime".
</t> </dd>
<t hangText="&lt;rdeCsv:fTrStatus&gt;">State of the most recen <dt>&lt;rdeCsv:fReDate&gt;</dt>
t transfer request with type="eppcom:trStatusType" and isRequired="true". <dd>Date that transfer was requested with type="dateTime" and isRe
</t> quired="true".
<t hangText="&lt;rdeCsv:fTokenType&gt;">General token field wi </dd>
th type="token". <dt>&lt;rdeCsv:fAcDate&gt;</dt>
</t> <dd>Date that transfer action should be taken or has been taken wi
<t hangText="&lt;rdeCsv:fLang&gt;">General language field with th type="dateTime" and isRequired="true".
type="language". </dd>
</t> <dt>&lt;rdeCsv:fTrDate&gt;</dt>
<t hangText="&lt;rdeCsv:fIdnTableId&gt;">IDN Table Identifier <dd>Date of last transfer with type="dateTime".
used for IDN domain names with type="token". </dd>
</t> <dt>&lt;rdeCsv:fTrStatus&gt;</dt>
<t hangText="&lt;rdeCsv:fPositiveIntegerType&gt;">General posi <dd>State of the most recent transfer request with type="eppcom:tr
tive integer field with type="positiveInteger". StatusType" and isRequired="true".
</t> </dd>
<t hangText="&lt;rdeCsv:fUrl&gt;">Contains the URL of an objec <dt>&lt;rdeCsv:fTokenType&gt;</dt>
t like a registrar object with type="anyURI". <dd>General token field with type="token".
</t> </dd>
<t hangText="&lt;rdeCsv:fCustom&gt;">Custom field with name at <dt>&lt;rdeCsv:fLang&gt;</dt>
tribute that defines the custom field name" with type="token". <dd>General language field with type="language".
</t> </dd>
</list></t> <dt>&lt;rdeCsv:fIdnTableId&gt;</dt>
</section> <dd>IDN table identifier used for IDN domain names with type="toke
</section> n".
</dd>
<section title="Internationalized and Localized Elements" anchor="in <dt>&lt;rdeCsv:fPositiveIntegerType&gt;</dt>
tandloc"> <dd>General positive integer field with type="positiveInteger".
<t> </dd>
Some elements MAY be provided in either internationalized fo <dt>&lt;rdeCsv:fUrl&gt;</dt>
rm ("int") or localized <dd>Contains the URL of an object like a registrar object with typ
e="anyURI".
</dd>
<dt>&lt;rdeCsv:fCustom&gt;</dt>
<dd>Custom field with name attribute that defines the custom field
name with type="token".
</dd>
</dl>
</section>
</section>
<section anchor="intandloc" numbered="true" toc="default">
<name>Internationalized and Localized Elements</name>
<t>
Some elements <bcp14>MAY</bcp14> be provided in either inter
nationalized form ("int") or localized
form ("loc"). Those elements use a field value or "isLoc" a ttribute to specify the form used. If form ("loc"). Those elements use a field value or "isLoc" a ttribute to specify the form used. If
an "isLoc" attribute is used, a value of "true" indicates th an "isLoc" attribute is used, a value of "true" indicates th
e use of the localized form and a value e use of the localized form, and a value
of "false" indicates the use of the internationalized form. of "false" indicates the use of the internationalized form.
This MAY override the form specified for a parent This <bcp14>MAY</bcp14> override the form specified for a parent
element. A value of "int" is used to indicate the internati element. A value of "int" is used to indicate the internati
onalized form and onalized form, and
a value of "loc" is used to indicate the localized form. a value of "loc" is used to indicate the localized form.
When the internalized form ("int") is provided, the field va lue MUST be represented in a subset of When the internalized form ("int") is provided, the field va lue <bcp14>MUST</bcp14> be represented in a subset of
UTF-8 that can be represented in the 7-bit US-ASCII characte r set. When the localized form ("loc") UTF-8 that can be represented in the 7-bit US-ASCII characte r set. When the localized form ("loc")
is provided, the field value MAY be represented in unrestric is provided, the field value <bcp14>MAY</bcp14> be represent
ted UTF-8. ed in unrestricted UTF-8.
</t> </t>
<t> <t keepWithNext="true">
<figure> The field elements below of the "registrar" &lt;rdeCsv:csv&g
<preamble> t; &lt;rdeCsv:fields&gt; element
The field elements below of the "registrar" &lt;rdeCsv:csv"&
gt; &lt;rdeCsv:fields&gt; element
specify the internationalized form with the isLoc="false" at tribute. specify the internationalized form with the isLoc="false" at tribute.
</preamble> </t>
<artwork><![CDATA[ <sourcecode markers="false" name="" type="xml"><![CDATA[
... ...
<csvRegistrar:contents> <csvRegistrar:contents>
... ...
<rdeCsv:csv name="registrar" sep=","> <rdeCsv:csv name="registrar" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvRegistrar:fId/> <csvRegistrar:fId/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
<csvRegistrar:fName isLoc="false"/> <csvRegistrar:fName isLoc="false"/>
<csvRegistrar:fGurid/> <csvRegistrar:fGurid/>
<csvRegistrar:fStatus/> <csvRegistrar:fStatus/>
skipping to change at line 682 skipping to change at line 643
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="306178BB"> cksum="306178BB">
registrar-YYYYMMDD.csv registrar-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvRegistrar:contents> </csvRegistrar:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t>
<t>
<figure>
<preamble>
The following is an example of using the &lt;csvContact:fP ostalType&gt; The following is an example of using the &lt;csvContact:fP ostalType&gt;
field value to define the internationalized or localized f orm of the remainder of field value to define the internationalized or localized f orm of the remainder of
the "contactPostal" field values. the "contactPostal" field values.
</preamble> </t>
<artwork><![CDATA[ <sourcecode markers="false" name="" type="xml"><![CDATA[
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contactPostal"> <rdeCsv:csv name="contactPostal">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId parent="true"/> <csvContact:fId parent="true"/>
<csvContact:fPostalType/> <csvContact:fPostalType/>
<csvContact:fName/> <csvContact:fName/>
<csvContact:fOrg/> <csvContact:fOrg/>
<csvContact:fStreet index="0"/> <csvContact:fStreet index="0"/>
skipping to change at line 720 skipping to change at line 677
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="02CC2504"> cksum="02CC2504">
contactPostal-YYYYMMDD.csv contactPostal-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:contents> </csvContact:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure>
</t>
</section>
</section>
</section> </section>
</section>
<section title="Object Description" anchor="Object_Description"> </section>
<t> <section anchor="Object_Description" numbered="true" toc="default">
<name>Object Description</name>
<t>
This section describes the base objects supported by this specif ication: This section describes the base objects supported by this specif ication:
</t> </t>
<section anchor="domainNameObject" numbered="true" toc="default">
<section title="Domain Name Object" anchor="domainNameObject"> <name>Domain Name Object</name>
<t> <t>
The domain name object is based on the EPP domain name mappi The domain name object is based on the EPP domain name mappi
ng specified in <xref target="RFC5731"/>. The domain name object supports both t ng specified in <xref target="RFC5731" format="default"/>. The domain name objec
he XML Model and the CSV Model, defined in the <xref target="models">Models</xre t supports both the XML model and the CSV model, defined in <xref target="models
f> section. The elements used for both models are defined in the following sect " format="default">'Models'</xref>. The elements used for both models are defin
ions. ed in the following sections.
</t> </t>
<section title="XML Model" anchor="domainXmlModel"> <section anchor="domainXmlModel" numbered="true" toc="default">
<t>There are <name>XML Model</name>
two elements used in the data escrow of the domain name objec <t>There are
ts for the XML model including the two elements used in the data escrow of the domain name objec
&lt;rdeDomain:domain&gt;, under the &lt;rde:contents&gt; elem ts for the XML model, including the
ent, and the &lt;rdeDomain:delete&gt; element, &lt;rdeDomain:domain&gt; element, under the &lt;rde:contents&
gt; element, and the &lt;rdeDomain:delete&gt; element,
under the &lt;rde:deletes&gt; element. under the &lt;rde:deletes&gt; element.
</t> </t>
<section anchor="rdeDomainElement" numbered="true" toc="default">
<section title="&lt;rdeDomain:domain&gt; object" anchor="rdeDoma <name>&lt;rdeDomain:domain&gt; Object</name>
inElement"> <t>
<t>
The domain element is based on the EPP domain &lt;info&g t; The domain element is based on the EPP domain &lt;info&g t;
response for an authorized client (see Section 3.1.2. of response for an authorized client (see <xref target="RFC
<xref target="RFC5731"/>) 5731" section="3.1.2" sectionFormat="of" format="default"/>)
with additional data from an EPP &lt;transfer&gt; Query with additional data from an EPP &lt;transfer&gt; query
Response, see response, see
Section 3.1.3. of <xref target="RFC5731"/>, Registry Gra <xref target="RFC5731" section="3.1.3" sectionFormat="of
ce Period (RGP) status from <xref target="RFC3915"/>, and data from " format="default"/>, Registry Grace Period (RGP) status from <xref target="RFC3
the EPP &lt;secDns:create&gt; command, see Section 5.2.1 915" format="default"/>, and data from
. of <xref target="RFC5910"/>. the EPP &lt;secDNS:create&gt; command, see <xref target=
</t> "RFC5910" section="5.2.1" sectionFormat="of" format="default"/>.
<t> </t>
<t>
A &lt;domain&gt; element substitutes for the &lt;abstrac tDomain&gt; A &lt;domain&gt; element substitutes for the &lt;abstrac tDomain&gt;
abstract element to define a concrete definition of a do main. The abstract element to create a concrete definition of a do main. The
&lt;abstractDomain&gt; element can be replaced by other domain definitions &lt;abstractDomain&gt; element can be replaced by other domain definitions
using the XML schema substitution groups feature. using the XML schema substitution groups feature.
</t> </t>
<t> <t>
The &lt;domain&gt; element contains the following child elements: The &lt;domain&gt; element contains the following child elements:
</t> </t>
<t> <ul spacing="normal">
<list style="symbols"> <li>
<t> A &lt;name&gt; element that contains the fully q
A &lt;name&gt; element that contains the fully-q ualified name of the domain name object.
ualified name of the domain name object. For IDNs, the A-label is
For IDNs the A-Label is u used (see <xref target="RFC5891" section="4.4" sectionFormat="comma" format="def
sed (see <xref target="RFC5891"/>, Section 4.4). ault"/>).
</t> </li>
<t> <li>
A &lt;roid&gt; element that contains the reposit A &lt;roid&gt; element that contains the ROID as
ory object identifier assigned to the domain signed to the domain
name object when it was created. name object when it was created.
</t> </li>
<t> <li>
An OPTIONAL &lt;uName&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;uName&gt; element
the fully-qualified domain name in Unicode character set. It that contains the FQDN in the Unicode character set. It
MUST be provided if available. <bcp14>MUST</bcp14> be provided if available.
</t> </li>
<t> <li>
An OPTIONAL &lt;idnTableId&gt; element that refe An <bcp14>OPTIONAL</bcp14> &lt;idnTableId&gt; el
rences the IDN Table used for the IDN. ement that references the IDN table used for the IDN.
This corresponds to the &quot;id&quot; attribute This corresponds to the "id" attribute of the &l
of the &lt;idnTableRef&gt; element. This t;idnTableRef&gt; element. This
element MUST be present if the domain name is an element <bcp14>MUST</bcp14> be present if the do
IDN. main name is an IDN.
</t> </li>
<t> <li>
An OPTIONAL &lt;originalName&gt; element is used An <bcp14>OPTIONAL</bcp14> &lt;originalName&gt;
to indicate that the domain name is an IDN variant. element is used to indicate that the domain name is an IDN variant.
This element contains the domain name used to ge nerate the IDN variant. This element contains the domain name used to ge nerate the IDN variant.
</t> </li>
<t> <li>
One or more &lt;status&gt; elements that contain the current status descriptors associated One or more &lt;status&gt; elements that contain the current status descriptors associated
with the domain name. with the domain name.
</t> </li>
<li>
<t> Zero or more <bcp14>OPTIONAL</bcp14> &lt;rgpStat
Zero or more OPTIONAL &lt;rgpStatus&gt; elements us&gt; elements to represent "pendingDelete" sub-statuses,
to represent "pendingDelete" sub-statuses,
including "redemptionPeriod", "pendingRestore", and "pendingDelete", that including "redemptionPeriod", "pendingRestore", and "pendingDelete", that
a domain name can be in as a result of grace per iod processing as specified a domain name can be in as a result of grace per iod processing as specified
in <xref target="RFC3915"/>. in <xref target="RFC3915" format="default"/>.
</t> </li>
<li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;registrant&gt; el
An OPTIONAL &lt;registrant&gt; element that cont ement that contains the identifier for the human or the organizational social in
ains the identifier for the human or organizational social information object as formation object associated with the holder of the domain name object.
sociated as the holder of the domain name object. </li>
</t> <li>
Zero or more <bcp14>OPTIONAL</bcp14> &lt;contact
<t> &gt; elements that contain identifiers for the human or organizational
Zero or more OPTIONAL &lt;contact&gt; elements t
hat contain identifiers for the human or organizational
social information objects associated with the d omain name object. social information objects associated with the d omain name object.
</t> </li>
<li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;ns&gt; element th
An OPTIONAL &lt;ns&gt; element that contains the at contains the fully qualified names of the delegated host objects or
fully-qualified names of the delegated host objects or host attributes (name servers) associated with t
host attributes (name servers) associated with t he domain name object. See
he domain name object. See Section 1.1 of <xref target="RFC5731" section="1.1" sectionForm
<xref target="RFC5731"/> for a description of th at="of" format="default"/> for a description of the elements used to specify hos
e elements used to specify host objects or t objects or
host attributes. host attributes.
</t> </li>
<li>
<t>
A &lt;clID&gt; element that contains the identif ier of the sponsoring registrar. A &lt;clID&gt; element that contains the identif ier of the sponsoring registrar.
</t> </li>
<t> <li>
An OPTIONAL &lt;crRr&gt; element that contains t An <bcp14>OPTIONAL</bcp14> &lt;crRr&gt; element
he identifier of the registrar that created the domain that contains the identifier of the registrar that created the domain
name object. An OPTIONAL client attribute is use name object. An <bcp14>OPTIONAL</bcp14> "client"
d to specify the client that attribute is used to specify the client that
performed the operation. performed the operation.
</t> </li>
<li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;crDate&gt; elemen
An OPTIONAL &lt;crDate&gt; element that contains t that contains the date and time of the domain name object creation.
the date and time of the domain name object creation. This element <bcp14>MUST</bcp14> be present if t
This element MUST be present if the domain name he domain name has been allocated.
has been allocated. </li>
</t> <li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;exDate&gt; elemen
An OPTIONAL &lt;exDate&gt; element that contains t that contains the date and time identifying the end (expiration) of the
the date and time identifying the end (expiration) of the domain name object's registration period. This e
domain name object's registration period. This e lement <bcp14>MUST</bcp14> be present if the domain name has been allocated.
lement MUST be present if the domain name has been allocated. </li>
</t> <li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;upRr&gt; element
An OPTIONAL &lt;upRr&gt; element that contains t that contains the identifier of the registrar that last updated the
he identifier of the registrar that last updated the domain name object. This element <bcp14>MUST NOT
domain name object. This element MUST NOT be pre </bcp14> be present if the domain has never been modified. An <bcp14>OPTIONAL</b
sent if the domain has never been modified. An OPTIONAL cp14>
client attribute is used to specify the client t "client" attribute is used to specify the client
hat performed the operation. that performed the operation.
</t> </li>
<t> <li>
An OPTIONAL &lt;upDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;upDate&gt; elemen
the date and time of the most recent domain-name-object t that contains the date and time of the most recent modification of the domain
modification. This element MUST NOT be present i name object.
f the domain name object has never been modified. This element <bcp14>MUST NOT</bcp14> be present
</t> if the domain name object has never been modified.
<t> </li>
An OPTIONAL &lt;secDNS&gt; element that contains <li>
the public key information associated with Domain Name An <bcp14>OPTIONAL</bcp14> &lt;secDNS&gt; elemen
System security (DNSSEC) extensions for the doma t that contains the public key information associated with Domain Name
in name as specified in <xref target="RFC5910"/>. System security (DNSSEC) extensions for the doma
</t> in name as specified in <xref target="RFC5910" format="default"/>.
<t> </li>
An OPTIONAL &lt;trDate&gt; element that contains <li>
the date and time of the most recent domain name object successful An <bcp14>OPTIONAL</bcp14> &lt;trDate&gt; elemen
transfer. This element MUST NOT be present if th t that contains the date and time of the most recent successful transfer of a do
e domain name object has never been transferred. main name object.
</t> This element <bcp14>MUST NOT</bcp14> be present
<t> if the domain name object has never been transferred.
An OPTIONAL &lt;trnData&gt; element that contain </li>
s the following child elements related to the last transfer <li>
request of the domain name object. This element <t>
MUST NOT be present if a transfer request for the domain name has never An <bcp14>OPTIONAL</bcp14> &lt;trnData&gt; eleme
nt that contains the following child elements related to the last transfer
request of the domain name object. This element
<bcp14>MUST NOT</bcp14> be present if a transfer request for the domain name has
never
been created. been created.
<list style="symbols"> </t>
<t> <ul spacing="normal">
<li>
A &lt;trStatus&gt; element that contains the state of the most recent transfer request. A &lt;trStatus&gt; element that contains the state of the most recent transfer request.
</t> </li>
<t> <li>
A &lt;reRr&gt; element that contains the identifier of the registrar that requested A &lt;reRr&gt; element that contains the identifier of the registrar that requested
the domain name object transfer. An OPTI ONAL client attribute is used to specify the domain name object transfer. An <bcp 14>OPTIONAL</bcp14> "client" attribute is used to specify
the client that performed the operation. the client that performed the operation.
</t> </li>
<t> <li>
A &lt;reDate&gt; element that contains t he date and time that the transfer was requested. A &lt;reDate&gt; element that contains t he date and time that the transfer was requested.
</t> </li>
<t> <li>
An &lt;acRr&gt; element that contains th e identifier of the registrar that should act upon An &lt;acRr&gt; element that contains th e identifier of the registrar that should act upon
a PENDING transfer request. For all othe a pending transfer request. For all othe
r status types, the value identifies the registrar r status types, the value identifies the registrar
that took the indicated action. An OPTIO that took the indicated action. An <bcp1
NAL client attribute is used to specify 4>OPTIONAL</bcp14> "client" attribute is used to specify
the client that performed the operation. the client that performed the operation.
</t> </li>
<t> <li>
An &lt;acDate&gt; element that contains the date and time of a required or completed An &lt;acDate&gt; element that contains the date and time of a required or completed
response. For a PENDING request, the val ue identifies the date and time by which a response. For a pending request, the val ue identifies the date and time by which a
response is required before an automated response action will be taken by the registry. response is required before an automated response action will be taken by the registry.
For all other status types, the value id entifies the date and time when the request was For all other status types, the value id entifies the date and time when the request was
completed. completed.
</t> </li>
<t> <li>
An OPTIONAL &lt;exDate&gt; element that An <bcp14>OPTIONAL</bcp14> &lt;exDate&gt
contains the end of the domain name object's validity ; element that contains the end of the domain name object's validity
period (expiry date) if the transfer cau sed or causes a change in the validity period. period (expiry date) if the transfer cau sed or causes a change in the validity period.
</t> </li>
</list> </ul>
</t> </li>
</ul>
</list> <t keepWithNext="true">
</t> The following is an example of a domain name objec
t:
<t> </t>
<figure> <sourcecode markers="false" name="" type="xml"><![CDATA[
<preamble>
Example of a domain name object:
</preamble>
<artwork><![CDATA[
... ...
<rdeDomain:domain> <rdeDomain:domain>
<rdeDomain:name>xn--exampl-gva.example</rdeDomain:name> <rdeDomain:name>xn--exampl-gva.example</rdeDomain:name>
<rdeDomain:roid>Dexample1-TEST</rdeDomain:roid> <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid>
<rdeDomain:idnTableId>pt-BR</rdeDomain:idnTableId> <rdeDomain:idnTableId>pt-BR</rdeDomain:idnTableId>
<rdeDomain:originalName>example.example</rdeDomain:originalName> <rdeDomain:originalName>example.example</rdeDomain:originalName>
<rdeDomain:status s="ok"/> <rdeDomain:status s="ok"/>
<rdeDomain:registrant>jd1234</rdeDomain:registrant> <rdeDomain:registrant>jd1234</rdeDomain:registrant>
<rdeDomain:contact type="admin">sh8013</rdeDomain:contact> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact>
<rdeDomain:contact type="tech">sh8013</rdeDomain:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact>
<rdeDomain:ns> <rdeDomain:ns>
<domain:hostObj>ns1.example.com</domain:hostObj> <domain:hostObj>ns1.example.com</domain:hostObj>
<domain:hostObj>ns1.example1.example</domain:hostObj> <domain:hostObj>ns1.example1.example</domain:hostObj>
</rdeDomain:ns> </rdeDomain:ns>
<rdeDomain:clID>RegistrarX</rdeDomain:clID> <rdeDomain:clID>RegistrarX</rdeDomain:clID>
<rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr> <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr>
<rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate>
<rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate> <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate>
</rdeDomain:domain> </rdeDomain:domain>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> <section anchor="rdeDomainDeleteElement" numbered="true" toc="default"
</section> >
<name>&lt;rdeDomain:delete&gt; Object</name>
<section title="&lt;rdeDomain:delete&gt; object" anchor="rdeDoma <t>
inDeleteElement"> The &lt;rdeDomain:delete&gt; element contains the FQDN t
hat was deleted and purged.
<t> </t>
The &lt;rdeDomain:delete&gt; element contains the fully- <t keepWithNext="true">
qualified domain name that was deleted and purged. The following is an example of an &lt;rdeDomain:dele
</t> te&gt; object:
</t>
<t> <sourcecode markers="false" name="" type="xml"><![CDATA[
<figure>
<preamble>
Example of &lt;rdeDomain:delete&gt; object:
</preamble>
<artwork><![CDATA[
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeDomain:delete> <rdeDomain:delete>
<rdeDomain:name>foo.example</rdeDomain:name> <rdeDomain:name>foo.example</rdeDomain:name>
<rdeDomain:name>bar.example</rdeDomain:name> <rdeDomain:name>bar.example</rdeDomain:name>
</rdeDomain:delete> </rdeDomain:delete>
... ...
</rde:deletes> </rde:deletes>
...]]> ...
</artwork></figure> ]]></sourcecode>
</t> </section>
</section> </section>
<section anchor="domainCsvModel" numbered="true" toc="default">
</section> <name>CSV Model</name>
<t>For the CSV model of the domain name object, the &lt;csvDomain:cont
<section title="CSV Model" anchor="domainCsvModel"> ents&gt; child
<t>For the CSV Model of the domain name object, the &lt;csvDomai
n:contents&gt; child
element of the &lt;rde:contents&gt; element is used to hold t he new or updated domain name objects for the deposit. element of the &lt;rde:contents&gt; element is used to hold t he new or updated domain name objects for the deposit.
The &lt;csvDomain:deletes&gt; child element of the &lt;rde:de letes&gt; element is used to hold the deleted or The &lt;csvDomain:deletes&gt; child element of the &lt;rde:de letes&gt; element is used to hold the deleted or
purged domain name objects for the deposit. Both the &lt;csv Domain:contents&gt; and &lt;csvDomain:deletes&gt; purged domain name objects for the deposit. Both the &lt;csv Domain:contents&gt; and &lt;csvDomain:deletes&gt;
elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te. elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te.
</t> </t>
<t> <t>
Differential and Incremental Deposits are based on changes to the domain name objects. The updated domain name object Differential and Incremental Deposits are based on changes to the domain name objects. The updated domain name object
data under the &lt;csvDomain:contents&gt; element is a cascad e replace down all of the domain name CSV files starting with the data under the &lt;csvDomain:contents&gt; element is a cascad e replace down all of the domain name CSV files starting with the
parent <xref target="csvDomainDefinition">"domain" CSV File D parent <xref target="csvDomainDefinition" format="default">'"
efinition</xref>. The child CSV file definitions include a &lt;csvDomain:fName domain" CSV File Definition'</xref>. The child CSV file definitions include a &
parent="true"&gt; field. lt;csvDomain:fName parent="true"&gt; field.
All the child CSV file definition data for the domain name ob All the child CSV file definition data for the domain name ob
jects in the parent <xref target="csvDomainDefinition">"domain" CSV File Definit jects in the parent <xref target="csvDomainDefinition" format="default">'"domain
ion</xref> " CSV File Definition'</xref>
MUST first be deleted and then set using the data in the chil <bcp14>MUST</bcp14> first be deleted and then set using the d
d CSV files. The deleted domain name object data under the &lt;csvDomain:delete ata in the child CSV files. The deleted domain name object data under the &lt;c
s&gt; svDomain:deletes&gt;
element is a cascade delete starting from the <xref target="c element is a cascade delete starting from the <xref target="c
svDomainDeletesDefinition">"domain" Deletes CSV File Definition</xref>. svDomainDeletesDefinition" format="default">'"domain" Deletes CSV File Definitio
</t> n'</xref>.
</t>
<section title="&lt;csvDomain:contents&gt;" anchor="csvDomainCont <section anchor="csvDomainContents" numbered="true" toc="default">
ents"> <name>&lt;csvDomain:contents&gt;</name>
<t>The &lt;csvDomain:contents&gt; is used to hold the new or u <t>The &lt;csvDomain:contents&gt; is used to hold the new or updated
pdated domain name object information for the deposit. domain name object information for the deposit.
The &lt;csvDomain:contents&gt; is split into separate CSV file definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute. The &lt;csvDomain:contents&gt; is split into separate CSV file definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute.
The following sections include the supported domain name CSV f The following sections include the supported domain name CSV f
ile definitions: ile definitions.
</t> </t>
<section anchor="csvDomainDefinition" numbered="true" toc="default">
<section title="&quot;domain&quot; CSV File Definition" anchor <name>"domain" CSV File Definition</name>
="csvDomainDefinition"> <t>The "domain" CSV File Definition defines the fields and CSV fil
e references
<t>The "domain" CSV File Definition defines the fields and CSV file
references
used for the parent domain name object records. All the other domai n name CSV file definitions are used for the parent domain name object records. All the other domai n name CSV file definitions are
child CSV files based on the inclusion of the &lt;csvDomain:fName pa rent="true"&gt; field.</t> child CSV files based on the inclusion of the &lt;csvDomain:fName pa rent="true"&gt; field.</t>
<t>The following "csvDomain" field elements MUST be used in the "dom ain" <t>The following "csvDomain" field elements <bcp14>MUST</bcp14> be used in the "domain"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t>
<t><list style="hanging">
<t hangText="&lt;csvDomain:fName&gt;">Domain name field with type=
"eppcom:labelType" and isRequired="true".
</t> </t>
</list></t> <dl newline="false" spacing="normal">
<t>The following "csvDomain" field elements MAY be used in the "domain <dt>&lt;csvDomain:fName&gt;</dt>
" <dd>Domain name field with type="eppcom:labelType" and isRequire
d="true".
</dd>
</dl>
<t>The following "csvDomain" field elements <bcp14>MAY</bcp14> be
used in the "domain"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvDomain:fOriginalName&gt;">Fully-qualified name <dt>&lt;csvDomain:fOriginalName&gt;</dt>
of the original IDN domain name object related to the <dd>Fully qualified name of the original IDN domain name object
related to the
variant domain name object with type="eppcom:labelType". variant domain name object with type="eppcom:labelType".
</dd>
</dl>
<t>The following "rdeCsv" and "csvRegistrar" fields,
<bcp14>MUST</bcp14> be used in the "domain" &lt;rdeCsv:csv&gt; &lt;r
deCsv:fields&gt; element:
</t> </t>
<dl newline="false" spacing="normal">
<dt>&lt;rdeCsv:fRoid&gt;</dt>
<dd>ROID for the domain name object with isRequired="true".</dd>
<dt>&lt;rdeCsv:fClID&gt; or &lt;csvRegistrar:fGurid&gt;</dt>
<dd>
<t>A choice of the following:
</list></t> </t>
<t>The following "rdeCsv" and "csvRegistrar" fields, <dl newline="false" spacing="normal">
MUST be used in the "domain" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt <dt>&lt;rdeCsv:fClID&gt;</dt>
; element: <dd>Identifier of the sponsoring client with isRequired="tru
</t> e".
<t><list style="hanging"> </dd>
<t hangText="&lt;rdeCsv:fRoid&gt;">Registry Object IDentifier (ROID) <dt>&lt;csvRegistrar:fGurid&gt;</dt>
for the domain name object with isRequired="true".</t> <dd>Contains the Globally Unique
<t hangText="&lt;rdeCsv:fClID&gt; or &lt;csvRegistrar:fGurid&gt;">A
choice of:
<list style="hanging">
<t hangText="&lt;rdeCsv:fClID&gt;">Identifier of the spo
nsoring client with isRequired="true".
</t>
<t hangText="&lt;csvRegistrar:fGurid&gt;">Contains the G
lobally Unique
Registrar Identifier (GURID) assigned by ICANN with type="positiveInteger" a nd isRequired="true". Registrar Identifier (GURID) assigned by ICANN with type="positiveInteger" a nd isRequired="true".
</t> </dd>
</list></t> </dl>
</dd>
</list></t> </dl>
<t>The following "rdeCsv" fields, defined in section <xref target="c <t>The following "rdeCsv" fields, defined in <xref target="csvComm
svCommonFieldElements">CSV common field elements</xref>, onFieldElements" format="default">'CSV Common Field Elements'</xref>,
MAY be used in the "domain" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; <bcp14>MAY</bcp14> be used in the "domain" &lt;rdeCsv:csv&gt; &lt;rd
element: eCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fCrRr&gt;">Identifier of the registrar, defi <dt>&lt;rdeCsv:fCrRr&gt;</dt>
ned in <xref target="registrarObject"/>, of the client that created the domain n <dd>Identifier of the registrar, defined in <xref target="regist
ame object.</t> rarObject" format="default"/>, of the client that created the domain name object
<t hangText="&lt;rdeCsv:fCrID&gt;">Identifier of the client that cre .</dd>
ated the domain name object.</t> <dt>&lt;rdeCsv:fCrID&gt;</dt>
<t hangText="&lt;rdeCsv:fUpRr&gt;">Identifier of the registrar, defi <dd>Identifier of the client that created the domain name object
ned in <xref target="registrarObject"/>, of the client that last updated the dom .</dd>
ain name object.</t> <dt>&lt;rdeCsv:fUpRr&gt;</dt>
<t hangText="&lt;rdeCsv:fUpID&gt;">Identifier of the client that las <dd>Identifier of the registrar, defined in <xref target="regist
t updated the domain name object.</t> rarObject" format="default"/>, of the client that last updated the domain name o
<t hangText="&lt;rdeCsv:fUName&gt;">UTF8 encoded domain name for the bject.</dd>
&lt;csvDomain:fName&gt; field element.</t> <dt>&lt;rdeCsv:fUpID&gt;</dt>
<t hangText="&lt;rdeCsv:fIdnTableId&gt;">IDN Table Identifier used f <dd>Identifier of the client that last updated the domain name o
or the IDN domain name object that MUST match a &lt;rdeCsv:fIdnTableId&gt; field bject.</dd>
element in the "idnLanguage" CSV files, as defined in <xref target="idnCsvModel <dt>&lt;rdeCsv:fUName&gt;</dt>
"/>.</t> <dd>UTF-8 encoded domain name for the &lt;csvDomain:fName&gt; fi
<t hangText="&lt;rdeCsv:fRegistrant&gt;">Registrant contact identifi eld element.</dd>
er for the domain name object.</t> <dt>&lt;rdeCsv:fIdnTableId&gt;</dt>
<t hangText="&lt;rdeCsv:fCrDate&gt;">Created date and time of the do <dd>IDN table identifier used for the IDN domain name object tha
main name object.</t> t <bcp14>MUST</bcp14> match an &lt;rdeCsv:fIdnTableId&gt; field element in the "
<t hangText="&lt;rdeCsv:fUpDate&gt;">Date and time of the last updat idnLanguage" CSV files, as defined in <xref target="idnCsvModel" format="default
e to the domain name object. This field MUST NOT be set if the domain name objec "/>.</dd>
t has never been modified.</t> <dt>&lt;rdeCsv:fRegistrant&gt;</dt>
<t hangText="&lt;rdeCsv:fExDate&gt;">Expiration date and time for th <dd>Registrant contact identifier for the domain name object.</d
e domain name object.</t> d>
<t hangText="&lt;rdeCsv:fTrDate&gt;">Date and time of the last trans <dt>&lt;rdeCsv:fCrDate&gt;</dt>
fer for the domain name object. This field MUST NOT be set if the domain name ob <dd>Date and time of the domain name object creation.</dd>
ject has never been transferred.</t> <dt>&lt;rdeCsv:fUpDate&gt;</dt>
</list></t> <dd>Date and time of the last update to the domain name object.
<t> This field <bcp14>MUST NOT</bcp14> be set if the domain name object has never be
<figure> en modified.</dd>
<preamble> <dt>&lt;rdeCsv:fExDate&gt;</dt>
Example of a "domain" &lt;csvDomain:contents&gt; &lt;rdeCsv:csv& <dd>Expiration date and time for the domain name object.</dd>
gt; element. <dt>&lt;rdeCsv:fTrDate&gt;</dt>
</preamble> <dd>Date and time of the last transfer for the domain name objec
<artwork><![CDATA[ t. This field <bcp14>MUST NOT</bcp14> be set if the domain name object has never
been transferred.</dd>
</dl>
<t keepWithNext="true">
The following is an example of a "domain" &lt;csvDomain:contents
&gt; &lt;rdeCsv:csv&gt; element.
</t>
<sourcecode markers="false" name="" type="xml"><![CDATA[
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domain"> <rdeCsv:csv name="domain">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
<rdeCsv:fIdnTableId/> <rdeCsv:fIdnTableId/>
<csvDomain:fOriginalName/> <csvDomain:fOriginalName/>
<rdeCsv:fRegistrant/> <rdeCsv:fRegistrant/>
skipping to change at line 1058 skipping to change at line 1006
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="5E403BD6"> cksum="5E403BD6">
domain-YYYYMMDD.csv domain-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding domain-YYYYMMDD
<t> .csv file.
<figure>
<preamble>
Example of the corresponding domain-YYYYMMDD.csv file.
The file contains four records (two active ASCII domains, The file contains four records (two active ASCII domains,
original IDN with LANG-1 language rules, and variant IDN original IDN with LANG-1 language rules, and variant IDN
with LANG-1 language rules). with LANG-1 language rules).
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX,
clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX,
clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, clientY,1999-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX,
registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,
2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example,
registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z, registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z,
registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z]]> registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvDomainContactsDefinition" numbered="true" toc="d
</section> efault">
<section title="&quot;domainContacts&quot; CSV File Definition <name>"domainContacts" CSV File Definition</name>
" anchor="csvDomainContactsDefinition"> <t>The "domainContacts" CSV File Definition defines the fields and
<t>The "domainContacts" CSV File Definition defines the fields and C CSV file references
SV file references used for the domain name object link records to contact objects, as
used for the domain name object link records to contact objects, as described in <xref target="contactObject" format="default">'Contact Object'</xre
described in <xref target="contactObject">Contact Object</xref>.</t> f>.</t>
<t>The following "csvDomain" field elements, defined for the <xref ta <t>The following "csvDomain" field elements, defined for the <xref
rget="csvDomainDefinition">"domain" CSV File Definition</xref>, target="csvDomainDefinition" format="default">'"domain" CSV File Definition'</x
MUST be used in the "domainContacts" &lt;rdeCsv:csv&gt; &lt;rdeCsv:f ref>,
ields&gt; element: <bcp14>MUST</bcp14> be used in the "domainContacts" &lt;rdeCsv:csv&g
</t> t; &lt;rdeCsv:fields&gt; element:
<t><list style="hanging"> </t>
<t hangText="&lt;csvDomain:fName&gt;">The name of the domain objec <dl newline="false" spacing="normal">
t that is linked to the contact object with isRequired="true".</t> <dt>&lt;csvDomain:fName&gt;</dt>
<t hangText="&lt;csvDomain:fContactType&gt;">The contact type for <dd>The name of the domain object that is linked to the contact
the contact object link with type="domain:contactAttrType" and isRequired="true" object with isRequired="true".</dd>
. The supported <dt>&lt;csvDomain:fContactType&gt;</dt>
<dd>The contact type for the contact object link with type="doma
in:contactAttrType" and isRequired="true". The supported
contact type values include "admin" for the administration contact, "b illing" for the billing contact, and "tech" for the technical contact. contact type values include "admin" for the administration contact, "b illing" for the billing contact, and "tech" for the technical contact.
</t> </dd>
</list></t> </dl>
<t>The following "csvContact" fields, defined for the <xref target
<t>The following "csvContact" fields, defined for the <xref target=" ="csvContactDefinition" format="default">'"contact" CSV File Definition'</xref>,
csvContactDefinition">"contact" CSV File Definition</xref>, <bcp14>MUST</bcp14> be used in the "domainContacts" &lt;rdeCsv:csv&g
MUST be used in the "domainContacts" &lt;rdeCsv:csv&gt; &lt;rdeCsv:f t; &lt;rdeCsv:fields&gt; element:
ields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvContact:fId&gt;</dt>
<t hangText="&lt;csvContact:fId&gt;">The server-unique contact ide <dd>The server-unique contact identifier with isRequired="true".
ntifier with isRequired="true".</t> </dd>
</list></t> </dl>
<t keepWithNext="true">
<t> The following is an example of a "domainContacts" &lt;csvDomain:
<figure> contents&gt; &lt;rdeCsv:csv&gt; element:
<preamble> </t>
Example of a "domainContacts" &lt;csvDomain:contents&gt; &lt;rde <sourcecode name="" type="xml" markers="false"><![CDATA[
Csv:csv&gt; element.
</preamble>
<artwork><![CDATA[
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainContacts"> <rdeCsv:csv name="domainContacts">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<csvContact:fId/> <csvContact:fId/>
<csvDomain:fContactType/> <csvDomain:fContactType/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="6B976A6C"> cksum="6B976A6C">
domainContacts-YYYYMMDD.csv domainContacts-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork></figure> ]]></sourcecode>
</t> <t keepWithNext="true">
<t> The following is an example of the corresponding domainContacts-
<figure> YYYYMMDD.csv file.
<preamble>
Example of the corresponding domainContacts-YYYYMMDD.csv file.
The file contains an admin, tech, and billing contact for The file contains an admin, tech, and billing contact for
the four domain names domain1.example, domain2.example, xn--bc12 the four domain names domain1.example, domain2.example, xn--bc12
3-3ve.example 3-3ve.example,
and xn--bc321-3ve.example. and xn--bc321-3ve.example:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1.example,domain1admin,admin domain1.example,domain1admin,admin
domain1.example,domain1tech,tech domain1.example,domain1tech,tech
domain1.example,domain1billing,billing domain1.example,domain1billing,billing
domain2.example,domain2admin,admin domain2.example,domain2admin,admin
domain2.example,domain2tech,tech domain2.example,domain2tech,tech
domain2.example,domain2billing,billing domain2.example,domain2billing,billing
xn--bc123-3ve.example,xnabc123admin,admin xn--bc123-3ve.example,xnabc123admin,admin
xn--bc123-3ve.example,xnabc123tech,tech xn--bc123-3ve.example,xnabc123tech,tech
xn--bc123-3ve.example,xnabc123billing,billing xn--bc123-3ve.example,xnabc123billing,billing
xn--bc321-3ve.example,xnabc123admin,admin xn--bc321-3ve.example,xnabc123admin,admin
xn--bc321-3ve.example,xnabc123tech,tech xn--bc321-3ve.example,xnabc123tech,tech
xn--bc321-3ve.example,xnabc123billing,billing]]> xn--bc321-3ve.example,xnabc123billing,billing
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvDomainStatusesDefinition" numbered="true" toc="d
efault">
</section> <name>"domainStatuses" CSV File Definition</name>
<section title="&quot;domainStatuses&quot; CSV File Definition <t>The "domainStatuses" CSV File Definition defines the fields and
" anchor="csvDomainStatusesDefinition"> CSV file references
<t>The "domainStatuses" CSV File Definition defines the fields and C
SV file references
used for the domain name object statuses.</t> used for the domain name object statuses.</t>
<t>The following "csvDomain" fields, defined for the <xref target="cs <t>The following "csvDomain" fields, defined for the <xref target=
vDomainDefinition">"domain" CSV File Definition</xref>, "csvDomainDefinition" format="default">'"domain" CSV File Definition'</xref>,
MUST be used in the "domainStatuses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:f <bcp14>MUST</bcp14> be used in the "domainStatuses" &lt;rdeCsv:csv&g
ields&gt; element: t; &lt;rdeCsv:fields&gt; element:
</t>
<t><list style="hanging">
<t hangText="&lt;csvDomain:fName&gt;">Domain name of status with is
Required="true".</t>
<t hangText="&lt;csvDomain:fStatus&gt;">The status of the domain n
ame with type="domain:statusValueType" and isRequired="true".
</t> </t>
<t hangText="&lt;csvDomain:fRgpStatus&gt;">The RGP status, as a <dl newline="false" spacing="normal">
sub-status of the &lt;csvDomain:fStatus&gt; <dt>&lt;csvDomain:fName&gt;</dt>
<dd>Domain name of status with isRequired="true".</dd>
<dt>&lt;csvDomain:fStatus&gt;</dt>
<dd>The status of the domain name with type="domain:statusValueT
ype" and isRequired="true".
</dd>
<dt>&lt;csvDomain:fRgpStatus&gt;</dt>
<dd>The RGP status, as a sub-status of the &lt;csvDomain:fStatus
&gt;
"pendingDelete" status value, with type="rgp:statusValueType" as "pendingDelete" status value, with type="rgp:statusValueType" as
defined in <xref target="RFC3915"/>. defined in <xref target="RFC3915" format="default"/>.
</dd>
</dl>
<t>The following "rdeCsv" fields, defined in <xref target="csvComm
onFieldElements" format="default">'CSV Common Field Elements'</xref>,
<bcp14>MAY</bcp14> be used in the "domainStatuses" &lt;rdeCsv:csv&gt
; &lt;rdeCsv:fields&gt; element:
</t> </t>
</list></t> <dl newline="false" spacing="normal">
<dt>&lt;rdeCsv:fStatusDescription&gt;</dt>
<t>The following "rdeCsv" fields, defined in section <xref target="cs <dd>Domain name object status description, which is free-form te
vCommonFieldElements">CSV common field elements</xref>, xt describing the rationale for the status.</dd>
MAY be used in the "domainStatuses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fi <dt>&lt;rdeCsv:fLang&gt;</dt>
elds&gt; element: <dd>Language of the &lt;rdeCsv:fStatusDescription&gt; field.</dd
</t> >
<t><list style="hanging"> </dl>
<t hangText="&lt;rdeCsv:fStatusDescription&gt;">Domain name object <t keepWithNext="true">
status description which is free form text describing the rationale for the stat The following is an example of a "domainStatuses" &lt;csvDomai
us.</t> n:contents&gt; &lt;rdeCsv:csv&gt; element:
<t hangText="&lt;rdeCsv:fLang&gt;">Language of the &lt;rdeCsv:fStat </t>
usDescription&gt; field.</t> <sourcecode name="" type="xml" markers="false"><![CDATA[
</list></t>
<t>
<figure>
<preamble>
Example of a "domainStatuses" &lt;csvDomain:contents&gt; &lt;r
deCsv:csv&gt; element.
</preamble>
<artwork><![CDATA[
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainStatuses"> <rdeCsv:csv name="domainStatuses">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<csvDomain:fStatus/> <csvDomain:fStatus/>
<rdeCsv:fStatusDescription/> <rdeCsv:fStatusDescription/>
<rdeCsv:fLang/> <rdeCsv:fLang/>
<csvDomain:fRgpStatus/> <csvDomain:fRgpStatus/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="98D139A3"> cksum="98D139A3">
domainStatuses-YYYYMMDD.csv domainStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding domainStatuses-
<t> YYYYMMDD.csv file.
<figure>
<preamble>
Example of the corresponding domainStatuses-YYYYMMDD.csv file.
The file contains the statuses for The file contains the statuses for
the four domain names domain1.example, domain2.example, xn--bc12 the four domain names domain1.example, domain2.example, xn--bc12
3-3ve.example 3-3ve.example,
and xn--bc321-3ve.example. and xn--bc321-3ve.example:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1.example,clientUpdateProhibited,"Disallow update", domain1.example,clientUpdateProhibited,"Disallow update",
en, en,
domain1.example,clientDeleteProhibited,"Disallow delete", domain1.example,clientDeleteProhibited,"Disallow delete",
en, en,
domain2.example,ok,,, domain2.example,ok,,,
xn--bc123-3ve.example,ok,,, xn--bc123-3ve.example,ok,,,
xn--bc321-3ve.example,ok,,,]]> xn--bc321-3ve.example,ok,,,
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvDomainNameServersDefinition" numbered="true" toc
="default">
</section> <name>"domainNameServers" CSV File Definition</name>
<section title="&quot;domainNameServers&quot; CSV File Definit <t>The "domainNameServers" CSV File Definition defines the fields
ion" anchor="csvDomainNameServersDefinition"> and CSV file references
<t>The "domainNameServers" CSV File Definition defines the fields an
d CSV file references
used for the domain name delegated hosts (name servers). The "domai nNameServers" CSV files used for the domain name delegated hosts (name servers). The "domai nNameServers" CSV files
define the relationship between a domain name object and a delegated host. define the relationship between a domain name object and a delegated host.
The "domainNameServers" CSV File is used to support the &lt;domain:h The "domainNameServers" CSV File is used to support the &lt;domain:h
ostObj&gt; model, defined in <xref target="RFC5731"/>. ostObj&gt; model, defined in <xref target="RFC5731" format="default"/>.
</t> </t>
<t>The following "csvDomain" fields, defined for the <xref target=
<t>The following "csvDomain" fields, defined for the <xref target="cs "csvDomainDefinition" format="default">'"domain" CSV File Definition'</xref>,
vDomainDefinition">"domain" CSV File Definition</xref>, <bcp14>MUST</bcp14> be used in the "domainNameServers" &lt;rdeCsv:cs
MUST be used in the "domainNameServers" &lt;rdeCsv:csv&gt; &lt;rdeCs v&gt; &lt;rdeCsv:fields&gt; element:
v:fields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvDomain:fName&gt;</dt>
<t hangText="&lt;csvDomain:fName&gt;">Domain name using the delega <dd>Domain name using the delegated host with isRequired="true".
ted host with isRequired="true".</t> </dd>
</list></t> </dl>
<t>The following "csvHost" and "rdeCsv" field elements <bcp14>MUST
<t>The following "csvHost" and "rdeCsv" field elements MUST be used </bcp14> be used in the "domainNameServers" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields
in the "domainNameServers" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &gt; element:
</t> </t>
<t> <dl newline="false" spacing="normal">
<list style="hanging"> <dt>&lt;csvHost:fName&gt; or &lt;rdeCsv:fRoid&gt;</dt>
<dd>
<t hangText="&lt;csvHost:fName&gt; or &lt;rdeCsv:fRoid&g <t>A choice of the following:
t;">A choice of:
<list style="hanging">
<t hangText="&lt;csvHost:fName&gt;">Host name field with
type="eppcom:labelType" and isRequired="true".
</t>
<t hangText="&lt;rdeCsv:fRoid&gt;">Host object Registry
Object IDentifier (ROID) assigned to the host object with isRequired="true".
</t>
</list></t>
</list>
</t>
<t> </t>
<figure> <dl newline="false" spacing="normal">
<preamble> <dt>&lt;csvHost:fName&gt;</dt>
Example of a "domainNameServers" &lt;csvDomain:contents&gt; &lt; <dd>Host name field with type="eppcom:labelType" and isRequi
rdeCsv:csv&gt; element. red="true".
</preamble> </dd>
<artwork><![CDATA[ <dt>&lt;rdeCsv:fRoid&gt;</dt>
<dd>Host object ROID assigned to the host object with isRequ
ired="true".
</dd>
</dl>
</dd>
</dl>
<t keepWithNext="true">
The following is an example of a "domainNameServers" &lt;csvDoma
in:contents&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainNameServers"> <rdeCsv:csv name="domainNameServers">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="8FE6E9E1"> cksum="8FE6E9E1">
domainNameServers-YYYYMMDD.csv domainNameServers-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding domainNameServe
rs-YYYYMMDD.csv file.
<t>
<figure>
<preamble>
Example of the corresponding domainNameServers-YYYYMMDD.csv file
.
The file contains the delegated hosts (name servers) for The file contains the delegated hosts (name servers) for
the four domain names domain1.example, domain2.example, xn--bc12 3-3ve.example the four domain names domain1.example, domain2.example, xn--bc12 3-3ve.example,
and xn--bc321-3ve.example referenced via and xn--bc321-3ve.example referenced via
the &lt;rdeCsv:fRoid&gt; field element. the &lt;rdeCsv:fRoid&gt; field element:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1.example,Hns1_domain1_test-TEST domain1.example,Hns1_domain1_test-TEST
domain1.example,Hns2_domain1_test-TEST domain1.example,Hns2_domain1_test-TEST
domain2.example,Hns1_domain2_test-TEST domain2.example,Hns1_domain2_test-TEST
domain2.example,Hns2_domain2_test-TEST domain2.example,Hns2_domain2_test-TEST
xn--bc123-3ve.example,Hns1_example_test-TEST xn--bc123-3ve.example,Hns1_example_test-TEST
xn--bc123-3ve.example,Hns2_example_test-TEST xn--bc123-3ve.example,Hns2_example_test-TEST
xn--bc321-3ve.example,Hns1_example_test-TEST xn--bc321-3ve.example,Hns1_example_test-TEST
xn--bc321-3ve.example,Hns2_example_test-TEST]]> xn--bc321-3ve.example,Hns2_example_test-TEST
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvDomainNameServersAddressesDefinition" numbered="
</section> true" toc="default">
<name>"domainNameServersAddresses" CSV File Definition</name>
<section title="&quot;domainNameServersAddresses&quot; CSV File <t>The "domainNameServersAddresses" CSV File Definition defines th
Definition" anchor="csvDomainNameServersAddressesDefinition"> e fields and CSV file references
<t>The "domainNameServersAddresses" CSV File Definition defin
es the fields and CSV file references
used for supporting the domain host attributes model. used for supporting the domain host attributes model.
</t> </t>
<t>The following "csvDomain" fields, defined for the <xref target=
<t>The following "csvDomain" fields, defined for the <xref ta "csvDomainDefinition" format="default">'"domain" CSV File Definition'</xref>,
rget="csvDomainDefinition">"domain" CSV File Definition</xref>, <bcp14>MUST</bcp14> be used in the "domainNameServersAddres
MUST be used in the "domainNameServersAddresses" &lt;rdeCsv ses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
:csv&gt; &lt;rdeCsv:fields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvDomain:fName&gt;</dt>
<t hangText="&lt;csvDomain:fName&gt;">Domain name using the <dd>Domain name using the delegated host with host &lt;csvHost:f
delegated host with host &lt;csvHost:fName&gt; and isRequired="true".</t> Name&gt; and isRequired="true".</dd>
</list></t> </dl>
<t>The following "rdeCsv" fields, defined in <xref target="hostCsv
<t>The following "rdeCsv" fields, defined in section <xref ta Model" format="default">'CSV Model'</xref>,
rget="hostCsvModel">Host CSV model elements</xref>, <bcp14>MUST</bcp14> be used in the "domainNameServersAddres
MUST be used in the "domainNameServersAddresses" &lt;rdeCsv ses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
:csv&gt; &lt;rdeCsv:fields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvHost:fName&gt;</dt>
<t hangText="&lt;csvHost:fName&gt;">Host name field with ty <dd>Host name field with type="eppcom:labelType" and isRequired=
pe="eppcom:labelType" and isRequired="true". "true".
</t> </dd>
</dl>
</list></t> <t>The following "csvHost" fields, defined in <xref target="hostCs
<t>The following "csvHost" fields, defined in section <xref t vModel" format="default">'CSV Model'</xref>,
arget="hostCsvModel">Host CSV model elements</xref>, <bcp14>MAY</bcp14> be used in the "domainNameServersAddress
MAY be used in the "domainNameServersAddresses" &lt;rdeCsv: es" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
csv&gt; &lt;rdeCsv:fields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvHost:fAddr&gt;</dt>
<t hangText="&lt;csvHost:fAddr&gt;">IP addresses associate <dd>IP addresses associated with the host object with type="host
d with the host object with type="host:addrStringType". :addrStringType".
</t> </dd>
<t hangText="&lt;csvHost:fAddrVersion&gt;">IP addresses ve <dt>&lt;csvHost:fAddrVersion&gt;</dt>
rsion associated with the host object with type="host:ipType". <dd>IP addresses version associated with the host object with ty
pe="host:ipType".
"host:ipType" has the enumerated values of "v4" or "v6". "host:ipType" has the enumerated values of "v4" or "v6".
</t> </dd>
</list></t> </dl>
<t> <t keepWithNext="true">
<figure> The following is an example of a "domainNameServersAddr
<preamble> esses" &lt;csvDomain:contents&gt; &lt;rdeCsv:csv&gt; element:
Example of a "domainNameServersAddresses" &lt;csvDomain </t>
:contents&gt; &lt;rdeCsv:csv&gt; element. <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainNameServersAddresses"> <rdeCsv:csv name="domainNameServersAddresses">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<csvHost:fName/> <csvHost:fName/>
<csvHost:fAddr/> <csvHost:fAddr/>
<csvHost:fAddrVersion/> <csvHost:fAddrVersion/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="D3B77438"> cksum="D3B77438">
domainNameServersAddresses-YYYYMMDD.csv domainNameServersAddresses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding domain
NameServersAddresses-YYYYMMDD.csv file.
<t>
<figure>
<preamble>
Example of the corresponding domainNameServersAddresses
-YYYYMMDD.csv file.
The file contains the delegated hosts (name servers) fo r The file contains the delegated hosts (name servers) fo r
the four domain names domain1.example, domain2.example, the four domain names domain1.example, domain2.example,
xn--bc123-3ve.example xn--bc123-3ve.example,
and xn--bc321-3ve.example. and xn--bc321-3ve.example:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1.example,ns1.domain1.example,192.0.2.1,v4 domain1.example,ns1.domain1.example,192.0.2.1,v4
domain1.example,ns2.domain1.example,2001:DB8::1,v6 domain1.example,ns2.domain1.example,2001:DB8::1,v6
domain2.example,ns1.example.net,, domain2.example,ns1.example.net,,
domain2.example,ns2.example.net,, domain2.example,ns2.example.net,,
xn--bc123-3ve.example,ns1.example.net,, xn--bc123-3ve.example,ns1.example.net,,
xn--bc123-3ve.example,ns2.example.net,, xn--bc123-3ve.example,ns2.example.net,,
xn--bc321-3ve.example,ns1.example.net,, xn--bc321-3ve.example,ns1.example.net,,
xn--bc321-3ve.example,ns2.example.net,,]]> xn--bc321-3ve.example,ns2.example.net,,
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvDnssecDefinition" numbered="true" toc="default">
</section> <name>"dnssec" CSV File Definition</name>
<t>The "dnssec" CSV File Definition defines the fields and CSV fil
<section title="&quot;dnssec&quot; CSV File Definition" anchor e references used
="csvDnssecDefinition"> for the domain name object DNSSEC records (Delegation Signer (DS) or
<t>The "dnssec" CSV File Definition defines the fields and CSV file key data).</t>
references used <t>The following "csvDomain" field elements <bcp14>MUST</bcp14> be
for the domain name object DNSSEC records (DS or Key Data).</t> used
<t>The following "csvDomain" field elements MUST be used in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element w
in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element w hen the DS Data Interface per <xref target="RFC5910" format="default"/> is used:
hen the DS Data Interface per <xref target="RFC5910"/> is used: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvDomain:fKeyTag&gt;</dt>
<t hangText="&lt;csvDomain:fKeyTag&gt;">Contains the DS key tag va <dd>Contains the DS key tag value per <xref target="RFC5910" for
lue per <xref target="RFC5910"/> with type="unsignedShort" and isRequired="true" mat="default"/> with type="unsignedShort" and isRequired="true".
. </dd>
</t> <dt>&lt;csvDomain:fDsAlg&gt;</dt>
<dd>Contains the DS algorithm value per <xref target="RFC5910" f
<t hangText="&lt;csvDomain:fDsAlg&gt;">Contains the DS algorithm v ormat="default"/> with type="unsignedByte" and isRequired="true".
alue per <xref target="RFC5910"/> with type="unsignedByte" and isRequired="true" </dd>
. <dt>&lt;csvDomain:fDigestType&gt;</dt>
</t> <dd>Contains the DS digest type value per <xref target="RFC5910"
format="default"/> with type="unsignedByte" and isRequired="true".
<t hangText="&lt;csvDomain:fDigestType&gt;">Contains the DS digest </dd>
type value per <xref target="RFC5910"/> with type="unsignedByte" and isRequired <dt>&lt;csvDomain:fDigest&gt;</dt>
="true". <dd>Contains the DS digest value per <xref target="RFC5910" form
</t> at="default"/> with type="hexBinary" and isRequired="true".
</dd>
<t hangText="&lt;csvDomain:fDigest&gt;">Contains the DS digest val </dl>
ue per <xref target="RFC5910"/> with type="hexBinary" and isRequired="true". <t>The following "csvDomain" field elements <bcp14>MUST</bcp14> be
</t> used
</list></t> in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element wh
<t>The following "csvDomain" field elements MUST be used en the Key Data Interface per <xref target="RFC5910" format="default"/> is used
in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element wh and <bcp14>MAY</bcp14> be used in the "dnssec" &lt;rdeCsv:csv&gt; &
en the Key Data Interface per <xref target="RFC5910"/> is used lt;rdeCsv:fields&gt; element when the DS Data Interface per <xref target="RFC591
and MAY be used in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:field 0" format="default"/> is used:
s&gt; element when the DS Data Interface per <xref target="RFC5910"/> is used: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvDomain:fFlags&gt;</dt>
<t hangText="&lt;csvDomain:fFlags&gt;">Contains the flags field va <dd>Contains the flags field value per <xref target="RFC5910" fo
lue per <xref target="RFC5910"/> with type="unsignedShort" and isRequired="true" rmat="default"/> with type="unsignedShort" and isRequired="true".
. </dd>
</t> <dt>&lt;csvDomain:fProtocol&gt;</dt>
<dd>Contains the key protocol value per <xref target="RFC5910" f
<t hangText="&lt;csvDomain:fProtocol&gt;">Contains the Key protoco ormat="default"/> with type="unsignedByte" and isRequired="true".
l value per <xref target="RFC5910"/> with type="unsignedByte" and isRequired="tr </dd>
ue". <dt>&lt;csvDomain:fKeyAlg&gt;</dt>
</t> <dd>Contains the key algorithm value per <xref target="RFC5910"
format="default"/> with type="unsignedByte" and isRequired="true".
<t hangText="&lt;csvDomain:fKeyAlg&gt;">Contains the Key algorithm </dd>
value per <xref target="RFC5910"/> with type="unsignedByte" and isRequired="tru <dt>&lt;csvDomain:fPubKey&gt;</dt>
e". <dd>Contains the public key value per <xref target="RFC5910" for
</t> mat="default"/> with type="secDNS:keyType" and isRequired="true".
</dd>
<t hangText="&lt;csvDomain:fPubKey&gt;">Contains the public key va </dl>
lue per <xref target="RFC5910"/> with type="secDNS:keyType" and isRequired="true <t>The following "csvDomain" field elements <bcp14>MAY</bcp14> be
". used
</t>
</list></t>
<t>The following "csvDomain" field elements MAY be used
in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvDomain:fMaxSigLife&gt;">Indicates a child's prefer <dt>&lt;csvDomain:fMaxSigLife&gt;</dt>
ence for the number of seconds <dd>Indicates a child's preference for the number of seconds
after signature generation when the parent's signature on the DS infor mation provided by the child after signature generation when the parent's signature on the DS infor mation provided by the child
will expire with type="secDNS:maxSigLifeType" defined in <xref target= will expire with type="secDNS:maxSigLifeType" defined in <xref target=
"RFC5910"/>. "RFC5910" format="default"/>.
</t> </dd>
</list></t> </dl>
<t>The following "domain" fields, defined for the <xref target="csvD <t>The following "domain" fields, defined for the <xref target="cs
omainDefinition">"domain" CSV File Definition</xref>, vDomainDefinition" format="default">'"domain" CSV File Definition'</xref>,
MUST be used in the "dnssec" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt <bcp14>MUST</bcp14> be used in the "dnssec" &lt;rdeCsv:csv&gt; &lt;r
; element: deCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvDomain:fName&gt;">Domain name of the domain na <dt>&lt;csvDomain:fName&gt;</dt>
me object associated with the DNSSEC record and isRequired="true".</t> <dd>Domain name of the domain name object associated with the DN
</list></t> SSEC record and isRequired="true".</dd>
<t> </dl>
<figure> <t keepWithNext="true">
<preamble> The following is an example of a "dnssec" &lt;csvDomain:contents
Example of a "dnssec" &lt;csvDomain:contents&gt; &lt;rdeCsv:csv& &gt; &lt;rdeCsv:csv&gt; element with the DS Data Interface of <xref target="RFC5
gt; element with the DS Data Interface of <xref target="RFC5910"/>: 910" format="default"/>:
</preamble> </t>
<artwork><![CDATA[ <sourcecode name="" type="xml" markers="false"><![CDATA[
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="dnssec"> <rdeCsv:csv name="dnssec">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<csvDomain:fMaxSigLife/> <csvDomain:fMaxSigLife/>
<csvDomain:fKeyTag/> <csvDomain:fKeyTag/>
<csvDomain:fDsAlg/> <csvDomain:fDsAlg/>
<csvDomain:fDigestType/> <csvDomain:fDigestType/>
<csvDomain:fDigest/> <csvDomain:fDigest/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="10ED6C42"> cksum="10ED6C42">
dnssec-ds-YYYYMMDD.csv dnssec-ds-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding dnssec-ds-YYYYM
<t> MDD.csv file.
<figure> The file contains two DS records for domain1.example:
<preamble> </t>
Example of the corresponding dnssec-ds-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains two DS records for domain1.example.
</preamble>
<artwork><![CDATA[
domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55 domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55
domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3]]> domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3
</artwork> ]]></artwork>
</figure> <t keepWithNext="true">
</t> The following is an example of a "dnssec" &lt;csvDomain:contents
<t> &gt; &lt;rdeCsv:csv&gt; element with the Key Data Interface of <xref target="RFC
<figure> 5910" format="default"/>:
<preamble> </t>
Example of a "dnssec" &lt;csvDomain:contents&gt; &lt;rdeCsv:csv& <sourcecode name="" type="xml" markers="false"><![CDATA[
gt; element with the Key Data Interface of <xref target="RFC5910"/>:
</preamble>
<artwork><![CDATA[
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="dnssec"> <rdeCsv:csv name="dnssec">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<csvDomain:fMaxSigLife/> <csvDomain:fMaxSigLife/>
<csvDomain:fFlags/> <csvDomain:fFlags/>
<csvDomain:fProtocol/> <csvDomain:fProtocol/>
<csvDomain:fKeyAlg/> <csvDomain:fKeyAlg/>
<csvDomain:fPubKey/> <csvDomain:fPubKey/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="183C3F79"> cksum="183C3F79">
dnssec-key-YYYYMMDD.csv dnssec-key-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding dnssec-key-YYYY
<t> MMDD.csv file.
<figure> The file contains two key records for domain1.example:
<preamble> </t>
Example of the corresponding dnssec-key-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains two key records for domain1.example.
</preamble>
<artwork><![CDATA[
domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c= domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c=
domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940=]]> domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940=
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvDomainTransferDefinition" numbered="true" toc="d
efault">
</section> <name>"domainTransfer" CSV File Definition</name>
<section title="&quot;domainTransfer&quot; CSV File Definition <t>The "domainTransfer" CSV File Definition defines the fields and
" anchor="csvDomainTransferDefinition"> CSV file references
<t>The "domainTransfer" CSV File Definition defines the fields and C
SV file references
used for the domain name object pending and completed transfer recor ds. No additional used for the domain name object pending and completed transfer recor ds. No additional
field elements were added for use in the "domainTransfer" &lt;rdeCs v:csv&gt; &lt;rdeCsv:fields&gt; element.</t> field elements were added for use in the "domainTransfer" &lt;rdeCs v:csv&gt; &lt;rdeCsv:fields&gt; element.</t>
<t>The following "rdeCsv" fields, defined in <xref target="csvComm
<t>The following "rdeCsv" fields, defined in section <xref target="c onFieldElements" format="default">'CSV Common Field Elements'</xref>,
svCommonFieldElements">CSV common field elements</xref>, <bcp14>MUST</bcp14> be used in the "domainTransfer" &lt;rdeCsv:csv&g
MUST be used in the "domainTransfer" &lt;rdeCsv:csv&gt; &lt;rdeCsv:f t; &lt;rdeCsv:fields&gt; element:
ields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;rdeCsv:fTrStatus&gt;</dt>
<t hangText="&lt;rdeCsv:fTrStatus&gt;">State of the most recent tr <dd>State of the most recent transfer request with isRequired="t
ansfer request with isRequired="true".</t> rue".</dd>
<t hangText="&lt;rdeCsv:fReRr&gt;">Identifier of the registrar, de <dt>&lt;rdeCsv:fReRr&gt;</dt>
fined in <xref target="registrarObject"/>, of the client that requested the tran <dd>Identifier of the registrar, defined in <xref target="regist
sfer with isRequired="true".</t> rarObject" format="default"/>, of the client that requested the transfer with is
<t hangText="&lt;rdeCsv:fReDate&gt;">Date and time that the transf Required="true".</dd>
er was requested with isRequired="true".</t> <dt>&lt;rdeCsv:fReDate&gt;</dt>
<t hangText="&lt;rdeCsv:fAcRr&gt;">Identifier of the registrar, de <dd>Date and time that the transfer was requested with isRequire
fined in <xref target="registrarObject"/>, of the client that should take or too d="true".</dd>
k action with isRequired="true".</t> <dt>&lt;rdeCsv:fAcRr&gt;</dt>
<t hangText="&lt;rdeCsv:fAcDate&gt;">Date and time that the transf <dd>Identifier of the registrar, defined in <xref target="regist
er action should be taken or has been taken with isRequired="true".</t> rarObject" format="default"/>, of the client that should take or took action wit
</list></t> h isRequired="true".</dd>
<dt>&lt;rdeCsv:fAcDate&gt;</dt>
<t>The following "rdeCsv" fields, defined in section <xref target="cs <dd>Date and time that the transfer action should be taken or ha
vCommonFieldElements">CSV common field elements</xref>, s been taken with isRequired="true".</dd>
MAY be used in the "domainTransfer" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fi </dl>
elds&gt; element: <t>The following "rdeCsv" fields, defined in <xref target="csvComm
</t> onFieldElements" format="default">'CSV Common Field Elements'</xref>,
<t><list style="hanging"> <bcp14>MAY</bcp14> be used in the "domainTransfer" &lt;rdeCsv:csv&gt
<t hangText="&lt;rdeCsv:fExDate&gt;">Expiration date if the transfer ; &lt;rdeCsv:fields&gt; element:
command caused or causes a change in the validity period.</t> </t>
<t hangText="&lt;rdeCsv:fReID&gt;">Identifier of the client that req <dl newline="false" spacing="normal">
uested the transfer.</t> <dt>&lt;rdeCsv:fExDate&gt;</dt>
<t hangText="&lt;rdeCsv:fAcID&gt;">Identifier of the client that sho <dd>Expiration date if the transfer command caused or causes a c
uld take or took action for transfer.</t> hange in the validity period.</dd>
</list></t> <dt>&lt;rdeCsv:fReID&gt;</dt>
<dd>Identifier of the client that requested the transfer.</dd>
<t>The following "csvDomain" fields, defined for the <xref target="c <dt>&lt;rdeCsv:fAcID&gt;</dt>
svDomainDefinition">"domain" CSV File Definition</xref>, <dd>Identifier of the client that should take or took action for
MUST be used in the "domainTransfer" &lt;rdeCsv:csv&gt; &lt;rdeCsv:f transfer.</dd>
ields&gt; element: </dl>
</t> <t>The following "csvDomain" fields, defined for the <xref target=
<t><list style="hanging"> "csvDomainDefinition" format="default">'"domain" CSV File Definition'</xref>,
<t hangText="&lt;csvDomain:fName&gt;">Domain name of the domain name <bcp14>MUST</bcp14> be used in the "domainTransfer" &lt;rdeCsv:csv&g
object involved in the transfer with isRequired="true".</t> t; &lt;rdeCsv:fields&gt; element:
</list></t> </t>
<dl newline="false" spacing="normal">
<t> <dt>&lt;csvDomain:fName&gt;</dt>
<figure> <dd>Domain name of the domain name object involved in the transf
<preamble> er with isRequired="true".</dd>
Example of a "domainTransfer" &lt;csvDomain:contents&gt; &lt;rde </dl>
Csv:csv&gt; element. <t keepWithNext="true">
</preamble> The following is an example of a "domainTransfer" &lt;csvDomain:
<artwork><![CDATA[ contents&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvDomain:contents> <csvDomain:contents>
... ...
<rdeCsv:csv name="domainTransfer"> <rdeCsv:csv name="domainTransfer">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName parent="true"/> <csvDomain:fName parent="true"/>
<rdeCsv:fTrStatus/> <rdeCsv:fTrStatus/>
<rdeCsv:fReRr/> <rdeCsv:fReRr/>
<rdeCsv:fReID/> <rdeCsv:fReID/>
<rdeCsv:fReDate/> <rdeCsv:fReDate/>
skipping to change at line 1599 skipping to change at line 1504
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="2E5A9ACD"> cksum="2E5A9ACD">
domainTransfer-YYYYMMDD.csv domainTransfer-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:contents> </csvDomain:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding domainTransfer-
<t> YYYYMMDD.csv file.
<figure> The file contains one domain transfer record with a pending stat
<preamble> us:
Example of the corresponding domainTransfer-YYYYMMDD.csv file. </t>
The file contains one domain transfer record with a pending stat <artwork name="" type="" align="left" alt=""><![CDATA[
us.
</preamble>
<artwork><![CDATA[
domain1.example,pending,registrarX,clientY, domain1.example,pending,registrarX,clientY,
2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z, 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z,
2025-04-03T22:00:00.0Z]]> 2025-04-03T22:00:00.0Z
</artwork> ]]></artwork>
</figure> </section>
</t>
</section> </section>
<section anchor="csvDomainDeletes" numbered="true" toc="default">
</section> <name>&lt;csvDomain:deletes&gt;</name>
<t>
<section title="&lt;csvDomain:deletes&gt;" anchor="csvDomainDelet
es">
<t>
The &lt;csvDomain:deletes&gt; is used to hold the deleted doma in name objects in a Differential or Incremental Deposit. The &lt;csvDomain:deletes&gt; is used to hold the deleted doma in name objects in a Differential or Incremental Deposit.
All the domain name object data is deleted as part of a cascad e delete. The &lt;csvDomain:deletes&gt; is split into All the domain name object data is deleted as part of a cascad e delete. The &lt;csvDomain:deletes&gt; is split into
separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute. separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute.
The following section defines the supported domain name delete s CSV file definition. The following section defines the supported domain name delete s CSV file definition.
</t>
<section title="&quot;domain&quot; Deletes CSV File Definition
" anchor="csvDomainDeletesDefinition">
<t>
The following "csvDomain" field elements MUST be used in the
deletes "domain"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <section anchor="csvDomainDeletesDefinition" numbered="true" toc="de
<t hangText="&lt;csvDomain:fName&gt;">Domain name field with type= fault">
"eppcom:labelType" and isRequired="true". <name>"domain" Deletes CSV File Definition</name>
</t> <t>
</list></t> The following "csvDomain" field elements <bcp14>MUST</bcp14>
<t> be used in the deletes "domain"
<figure> &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
<preamble> </t>
Example of a "domain" &lt;csvDomain:deletes&gt; &lt;rdeCsv:csv <dl newline="false" spacing="normal">
&gt; element: <dt>&lt;csvDomain:fName&gt;</dt>
</preamble> <dd>Domain name field with type="eppcom:labelType" and isRequire
<artwork><![CDATA[ d="true".
</dd>
</dl>
<t keepWithNext="true">
The following is an example of a "domain" &lt;csvDomain:delete
s&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvDomain:deletes> <csvDomain:deletes>
... ...
<rdeCsv:csv name="domain"> <rdeCsv:csv name="domain">
<rdeCsv:fields> <rdeCsv:fields>
<csvDomain:fName/> <csvDomain:fName/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="A06D8194"> cksum="A06D8194">
domain-delete-YYYYMMDD.csv domain-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvDomain:deletes> </csvDomain:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding domain-delete-Y
<t> YYYMMDD.csv file.
<figure> The file contains two domain name records:
<preamble> </t>
Example of the corresponding domain-delete-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains two domain name records.
</preamble>
<artwork><![CDATA[
domain1.example domain1.example
domain2.example]]> domain2.example
</artwork> ]]></artwork>
</figure>
</t>
</section>
</section>
</section>
</section> </section>
</section>
<section title="Host Object" anchor="hostObject"> </section>
<t> </section>
The host object is based on the EPP host name mapping in <xr <section anchor="hostObject" numbered="true" toc="default">
ef target="RFC5732"/>. The <name>Host Object</name>
host object supports both the XML Model and the CSV Model, d <t>
efined in <xref target="models">Models</xref> section. The The host object is based on the EPP host name mapping in <xr
ef target="RFC5732" format="default"/>. The
host object supports both the XML model and the CSV model, d
efined in <xref target="models" format="default">'Models'</xref>. The
elements used for both models are defined in the following s ections. Both the &lt;csvHost:contents&gt; and &lt;csvHost:deletes&gt; elements used for both models are defined in the following s ections. Both the &lt;csvHost:contents&gt; and &lt;csvHost:deletes&gt;
elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te. elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te.
</t> </t>
<section title="XML Model" anchor="hostXmlModel"> <section anchor="hostXmlModel" numbered="true" toc="default">
<t>There are <name>XML Model</name>
<t>There are
two elements used in the data escrow of the host objects for the XML model including the two elements used in the data escrow of the host objects for the XML model including the
&lt;rdeHost:host&gt;, under the &lt;rdeHost:contents&gt; elem ent, and the &lt;rdeHost:delete&gt; element, &lt;rdeHost:host&gt; element, under the &lt;rdeHost:contents& gt; element, and the &lt;rdeHost:delete&gt; element,
under the &lt;rde:deletes&gt; element. under the &lt;rde:deletes&gt; element.
</t> </t>
<t> <t>
A &lt;rdeHost:host&gt; element substitutes for the &lt;rdeHo An &lt;rdeHost:host&gt; element substitutes for the &lt;rdeH
st:abstractHost&gt; ost:abstractHost&gt;
abstract element to define a concrete definition of a host. abstract element to create a concrete definition of a host.
The The
&lt;rdeHost:abstractHost&gt; element can be replaced by othe r host definitions &lt;rdeHost:abstractHost&gt; element can be replaced by othe r host definitions
using the XML schema substitution groups feature. using the XML schema substitution groups feature.
</t> </t>
<section anchor="rdeHostElement" numbered="true" toc="default">
<section title="&lt;rdeHost:host&gt; element" anchor="rdeHostEle <name>&lt;rdeHost:host&gt; Element</name>
ment"> <t>
<t> The RDE host object is based on the EPP host &lt;info&gt
The RDE host object is based on the EPP host &lt;info&g ; response for
t; response for an authorized client (<xref target="RFC5732" section="3.
an authorized client (Section 3.1.2. of <xref target="RF 1.2" sectionFormat="of" format="default"/>).
C5732"/>). </t>
</t> <t>
The <bcp14>OPTIONAL</bcp14> &lt;host&gt; element contain
<t> s the following child elements:
The OPTIONAL &lt;host&gt; element contains the following </t>
child elements: <ul spacing="normal">
</t> <li>
<t> A &lt;name&gt; element that contains the fully q
<list style="symbols"> ualified name of the host object.
<t> </li>
A &lt;name&gt; element that contains the fully-q <li>
ualified name of the host object. A &lt;roid&gt; element that contains the ROID as
</t> signed to the host
<t>
A &lt;roid&gt; element that contains the reposit
ory object identifier assigned to the host
object when the object was created. object when the object was created.
</t> </li>
<t> <li>
One or more &lt;status&gt; elements that describ e the status of the host object. One or more &lt;status&gt; elements that describ e the status of the host object.
</t> </li>
<t> <li>
Zero or more &lt;addr&gt; elements that contain the IP addresses associated with the host object. Zero or more &lt;addr&gt; elements that contain the IP addresses associated with the host object.
</t> </li>
<t> <li>
A &lt;clID&gt; element that contains the identif ier of the sponsoring registrar. A &lt;clID&gt; element that contains the identif ier of the sponsoring registrar.
</t> </li>
<t> <li>
An OPTIONAL &lt;crRr&gt; element that contains t An <bcp14>OPTIONAL</bcp14> &lt;crRr&gt; element
he identifier of the registrar that created the host object. that contains the identifier of the registrar that created the host object.
An OPTIONAL client attribute is used to specify An <bcp14>OPTIONAL</bcp14> "client" attribute is
the client that performed the operation. used to specify the client that performed the operation.
</t> </li>
<t> <li>
An OPTIONAL &lt;crDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;crDate&gt; elemen
the date and time of host-object creation. t that contains the date and time of host object creation.
</t> </li>
<t> <li>
An OPTIONAL &lt;upRr&gt; element that contains t An <bcp14>OPTIONAL</bcp14> &lt;upRr&gt; element
he identifier of the registrar that last updated the host that contains the identifier of the registrar that last updated the host
object. This element MUST NOT be present if the object. This element <bcp14>MUST NOT</bcp14> be
host object has never been modified. An OPTIONAL client present if the host object has never been modified. An <bcp14>OPTIONAL</bcp14> "
client"
attribute is used to specify the client that per formed the operation. attribute is used to specify the client that per formed the operation.
</t> </li>
<t> <li>
An OPTIONAL &lt;upDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;upDate&gt; elemen
the date and time of the most recent host-object t that contains the date and time of the most recent host object
modification. This element MUST NOT be present i modification. This element <bcp14>MUST NOT</bcp1
f the host object has never been modified. 4> be present if the host object has never been modified.
</t> </li>
<t> <li>
An OPTIONAL &lt;trDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;trDate&gt; elemen
the date and time of the most recent host object successful t that contains the date and time of the most recent host object successful
transfer. This element MUST NOT be present if th transfer. This element <bcp14>MUST NOT</bcp14> b
e domain name object has never been transfered. e present if the domain name object has never been transferred.
</t> </li>
</list> </ul>
</t> <t keepWithNext="true">
The following is an example of a &lt;host&gt; object
<t> :
<figure> </t>
<preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
Example of &lt;host&gt; object:
</preamble>
<artwork><![CDATA[
... ...
<rdeHost:host> <rdeHost:host>
<rdeHost:name>ns1.example1.example</rdeHost:name> <rdeHost:name>ns1.example1.example</rdeHost:name>
<rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid> <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid>
<rdeHost:status s="ok"/> <rdeHost:status s="ok"/>
<rdeHost:status s="linked"/> <rdeHost:status s="linked"/>
<rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr>
<rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr>
<rdeHost:addr ip="v6">2001:DB8:1::1</rdeHost:addr> <rdeHost:addr ip="v6">2001:DB8:1::1</rdeHost:addr>
<rdeHost:clID>RegistrarX</rdeHost:clID> <rdeHost:clID>RegistrarX</rdeHost:clID>
<rdeHost:crRr>RegistrarX</rdeHost:crRr> <rdeHost:crRr>RegistrarX</rdeHost:crRr>
<rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate> <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate>
<rdeHost:upRr>RegistrarX</rdeHost:upRr> <rdeHost:upRr>RegistrarX</rdeHost:upRr>
<rdeHost:upDate>2009-10-03T09:34:00.0Z</rdeHost:upDate> <rdeHost:upDate>2009-10-03T09:34:00.0Z</rdeHost:upDate>
</rdeHost:host> </rdeHost:host>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> <section anchor="del_host_object" numbered="true" toc="default">
</section> <name>&lt;rdeHost:delete&gt; Object</name>
<t>
<section title="&lt;rdeHost:delete&gt; object" anchor="del_host_ The &lt;rdeHost:delete&gt; element contains the FQDN of
object"> a host
<t>
The &lt;rdeHost:delete&gt; element contains the fully-qu
alified domain name of a host
that was deleted. that was deleted.
The &lt;rdeHost:delete&gt; element also supports host re The &lt;rdeHost:delete&gt; element also supports host re
moval based on roid to support moval based on ROID to support
SRS systems in which different hosts with the same fully SRS systems in which different hosts with the same FQDN
-qualified domain name are active at the same time. are active at the same time.
</t> </t>
<t keepWithNext="true">
<t> The following is an example of an &lt;rdeHost:delete
<figure> &gt; object:
<preamble> </t>
Example of &lt;rdeHost:delete&gt; object: <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeHost:delete> <rdeHost:delete>
<rdeHost:name>ns1.example.example</rdeHost:name> <rdeHost:name>ns1.example.example</rdeHost:name>
</rdeHost:delete> </rdeHost:delete>
... ...
</rde:deletes> </rde:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> </section>
</section> <section anchor="hostCsvModel" numbered="true" toc="default">
</section> <name>CSV Model</name>
<section title="CSV Model" anchor="hostCsvModel"> <t>For the CSV model of the host object, the &lt;csvHost:contents&gt;
<t>For the CSV Model of the host object, the &lt;csvHost:content child
s&gt; child
element of the &lt;rde:contents&gt; element is used to hold t he new or updated host objects for the deposit. element of the &lt;rde:contents&gt; element is used to hold t he new or updated host objects for the deposit.
The &lt;csvHost:deletes&gt; child element of the &lt;rde:dele tes&gt; element is used to hold the deleted or The &lt;csvHost:deletes&gt; child element of the &lt;rde:dele tes&gt; element is used to hold the deleted or
purged host objects for the deposit. purged host objects for the deposit.
</t> </t>
<t> <t>
Differential and Incremental Deposits are based on changes to the host objects. The updated host object Differential and Incremental Deposits are based on changes to the host objects. The updated host object
data under the &lt;csvHost:contents&gt; element is a cascade replace down all of the host CSV files starting with the data under the &lt;csvHost:contents&gt; element is a cascade replace down all of the host CSV files starting with the
parent <xref target="csvHostDefinition">"host" CSV File Defin parent <xref target="csvHostDefinition" format="default">'"ho
ition</xref>. The child CSV file definitions include a &lt;rdeCsv:fRoid parent= st" CSV File Definition'</xref>. The child CSV file definitions include an &lt;
"true"&gt; field. rdeCsv:fRoid parent="true"&gt; field.
All the child CSV file definition data for the host objects i All the child CSV file definition data for the host objects i
n the parent <xref target="csvHostDefinition">"host" CSV File Definition</xref> n the parent <xref target="csvHostDefinition" format="default">'"host" CSV File
MUST first be deleted and then set using the data in the chil Definition'</xref>
d CSV files. The deleted host object data under the &lt;csvHost:deletes&gt; <bcp14>MUST</bcp14> first be deleted and then set using the d
element is a cascade delete starting from the <xref target="c ata in the child CSV files. The deleted host object data under the &lt;csvHost:
svHostDeletesDefinition">"host" Deletes CSV File Definition</xref>. deletes&gt;
</t> element is a cascade delete starting from the <xref target="c
svHostDeletesDefinition" format="default">'"host" Deletes CSV File Definition'</
<section title="&lt;csvHost:contents&gt;" anchor="csvHostContents xref>.
"> </t>
<t>The &lt;csvHost:contents&gt; is used to hold the new or upd <section anchor="csvHostContents" numbered="true" toc="default">
ated host object information for the deposit. <name>&lt;csvHost:contents&gt;</name>
<t>The &lt;csvHost:contents&gt; is used to hold the new or updated h
ost object information for the deposit.
The &lt;csvHost:contents&gt; is split into separate CSV file d efinitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute. The &lt;csvHost:contents&gt; is split into separate CSV file d efinitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute.
The following sections include the supported host CSV file def initions. The following sections include the supported host CSV file def initions.
</t> </t>
<section title="&quot;host&quot; CSV File Definition" anchor=" <section anchor="csvHostDefinition" numbered="true" toc="default">
csvHostDefinition"> <name>"host" CSV File Definition</name>
<t>The "host" CSV File Definition defines the fields and CSV file re <t>The "host" CSV File Definition defines the fields and CSV file
ferences references
used for the host object records.</t> used for the host object records.</t>
<t>The following "csvHost" field elements MUST be used in the "host" <t>The following "csvHost" field elements <bcp14>MUST</bcp14> be u sed in the "host"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<dt>&lt;csvHost:fName&gt;</dt>
<t hangText="&lt;csvHost:fName&gt;">Host name field with type="eppco <dd>Host name field with type="eppcom:labelType" and isRequired=
m:labelType" and isRequired="true". "true".
</t> </dd>
</dl>
</list></t> <t>The following "rdeCsv" fields, defined in <xref target="csvComm
<t>The following "rdeCsv" fields, defined in section <xref target="c onFieldElements" format="default">'CSV Common Field Elements'</xref>,
svCommonFieldElements">CSV common field elements</xref>, <bcp14>MUST</bcp14> be used in the "host" &lt;rdeCsv:csv&gt; &lt;rde
MUST be used in the "host" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; Csv:fields&gt; element:
element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;rdeCsv:fRoid&gt;</dt>
<t hangText="&lt;rdeCsv:fRoid&gt;">Repository Object IDentifier (ROI <dd>ROID assigned to the host object with isRequired="true".</dd
D) assigned to the host object with isRequired="true".</t> >
</list></t> </dl>
<t>The following "rdeCsv" and "csvRegistrar" fields, <t>The following "rdeCsv" and "csvRegistrar" fields
MAY be used in the "host" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; e <bcp14>MAY</bcp14> be used in the "host" &lt;rdeCsv:csv&gt; &lt;rdeC
lement: sv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fClID&gt; or &lt;csvRegistrar:fGurid&gt;">A <dt>&lt;rdeCsv:fClID&gt; or &lt;csvRegistrar:fGurid&gt;</dt>
choice of: <dd>
<t>A choice of the following:
<list style="hanging">
<t hangText="&lt;rdeCsv:fClID&gt;">Identifier of the spo
nsoring client with isRequired="true".
</t>
<t hangText="&lt;csvRegistrar:fGurid&gt;">Contains the G </t>
lobally Unique <dl newline="false" spacing="normal">
Registrar Identifier (GURID) assigned by ICANN with type="positiveInteger" a <dt>&lt;rdeCsv:fClID&gt;</dt>
nd isRequired="true". <dd>Identifier of the sponsoring client with isRequired="tru
</t> e".
</list></t> </dd>
<t hangText="&lt;rdeCsv:fCrRr&gt;">Identifier of the registrar, defi <dt>&lt;csvRegistrar:fGurid&gt;</dt>
ned in <xref target="registrarObject"/>, of the client that created the host obj <dd>Contains the
ect.</t> GURID assigned by ICANN with type="positiveInteger" and isRequired="true".
<t hangText="&lt;rdeCsv:fCrID&gt;">Identifier of the client that cre </dd>
ated the host object.</t> </dl>
<t hangText="&lt;rdeCsv:fUpRr&gt;">Identifier of the registrar, defi </dd>
ned in <xref target="registrarObject"/>, of the client that last updated the hos <dt>&lt;rdeCsv:fCrRr&gt;</dt>
t object.</t> <dd>Identifier of the registrar, defined in <xref target="regist
<t hangText="&lt;rdeCsv:fUpID&gt;">Identifier of the client that las rarObject" format="default"/>, of the client that created the host object.</dd>
t updated the host object.</t> <dt>&lt;rdeCsv:fCrID&gt;</dt>
<t hangText="&lt;rdeCsv:fCrDate&gt;">Date and time that the host obj <dd>Identifier of the client that created the host object.</dd>
ect was created.</t> <dt>&lt;rdeCsv:fUpRr&gt;</dt>
<t hangText="&lt;rdeCsv:fUpDate&gt;">Date and time that the host obj <dd>Identifier of the registrar, defined in <xref target="regist
ect was last updated. This field MUST NOT be set if the domain name object has n rarObject" format="default"/>, of the client that last updated the host object.<
ever been modified.</t> /dd>
<t hangText="&lt;rdeCsv:fTrDate&gt;">Date and time that the host obj <dt>&lt;rdeCsv:fUpID&gt;</dt>
ect was last transferred. This field MUST NOT be set if the domain name object h <dd>Identifier of the client that last updated the host object.<
as never been transferred.</t> /dd>
</list></t> <dt>&lt;rdeCsv:fCrDate&gt;</dt>
<t> <dd>Date and time that the host object was created.</dd>
<figure> <dt>&lt;rdeCsv:fUpDate&gt;</dt>
<preamble>Example of a "host" &lt;csvHost:contents&gt; &lt;rdeCs <dd>Date and time that the host object was last updated. This fi
v:csv&gt; element.</preamble> eld <bcp14>MUST NOT</bcp14> be set if the domain name object has never been modi
<artwork><![CDATA[ fied.</dd>
<dt>&lt;rdeCsv:fTrDate&gt;</dt>
<dd>Date and time that the host object was last transferred. Thi
s field <bcp14>MUST NOT</bcp14> be set if the domain name object has never been
transferred.</dd>
</dl>
<t keepWithNext="true">The following is an example of a "host" &lt
;csvHost:contents&gt; &lt;rdeCsv:csv&gt; element:</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvHost:contents> <csvHost:contents>
... ...
<rdeCsv:csv name="host"> <rdeCsv:csv name="host">
<rdeCsv:fields> <rdeCsv:fields>
<csvHost:fName/> <csvHost:fName/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
<rdeCsv:fClID/> <rdeCsv:fClID/>
<rdeCsv:fCrRr/> <rdeCsv:fCrRr/>
<rdeCsv:fCrID/> <rdeCsv:fCrID/>
skipping to change at line 1897 skipping to change at line 1785
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="6F1E58E5"> cksum="6F1E58E5">
host-YYYYMMDD.csv host-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:contents> </csvHost:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding host-YYYYMMDD.c
<t> sv file.
<figure>
<preamble>
Example of the corresponding host-YYYYMMDD.csv file.
The file contains six host records with four being The file contains six host records with four being
internal hosts and two being external internal hosts and two being external
hosts. hosts:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX,
clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,
clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z]]> clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvHostStatusesDefinition" numbered="true" toc="def
</section> ault">
<section title="&quot;hostStatuses&quot; CSV File Definition" <name>"hostStatuses" CSV File Definition</name>
anchor="csvHostStatusesDefinition"> <t>The "hostStatuses" CSV File Definition defines the fields and C
<t>The "hostStatuses" CSV File Definition defines the fields and CSV SV file references
file references
used for the host object statuses. used for the host object statuses.
</t> </t>
<t>The following "csvHost" fields, defined for the <xref target="c
<t>The following "csvHost" fields, defined for the <xref target="csvH svHostDefinition" format="default">'"host" CSV File Definition'</xref>,
ostDefinition">"host" CSV File Definition</xref>, <bcp14>MUST</bcp14> be used in the "hostStatuses" &lt;rdeCsv:csv&gt;
MUST be used in the "hostStatuses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fie &lt;rdeCsv:fields&gt; element:
lds&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvHost:fStatus&gt;</dt>
<t hangText="&lt;csvHost:fStatus&gt;">The status of the host with type <dd>The status of the host with type="host:statusValueType" and
="host:statusValueType" and isRequired="true".</t> isRequired="true".</dd>
</list></t> </dl>
<t>The following "rdeCsv" fields, defined in <xref target="csvComm
<t>The following "rdeCsv" fields, defined in section <xref target="c onFieldElements" format="default">'CSV Common Field Elements'</xref>,
svCommonFieldElements">CSV common field elements</xref>, <bcp14>MUST</bcp14> be used in the "hostStatuses" &lt;rdeCsv:csv&gt;
MUST be used in the "hostStatuses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fie &lt;rdeCsv:fields&gt; element:
lds&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;rdeCsv:fRoid&gt;</dt>
<t hangText="&lt;rdeCsv:fRoid&gt;">Host object Registry Object IDent <dd>Host object ROID assigned to the host object with isRequired
ifier (ROID) assigned to the host object with isRequired="true".</t> ="true".</dd>
</list></t> </dl>
<t>The following "rdeCsv" fields, defined in section <xref target="c <t>The following "rdeCsv" fields, defined in <xref target="csvComm
svCommonFieldElements">CSV common field elements</xref>, onFieldElements" format="default">'CSV Common Field Elements'</xref>,
MAY be used in the "hostStatuses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fiel <bcp14>MAY</bcp14> be used in the "hostStatuses" &lt;rdeCsv:csv&gt;
ds&gt; element: &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fStatusDescription&gt;">Host object status <dt>&lt;rdeCsv:fStatusDescription&gt;</dt>
description which is free form text describing the rationale for the status.</t <dd>Host object status description, which is free-form text desc
> ribing the rationale for the status.</dd>
<t hangText="&lt;rdeCsv:fLang&gt;">Language of the &lt;rdeCsv:fStatu <dt>&lt;rdeCsv:fLang&gt;</dt>
sDescription&gt; field.</t> <dd>Language of the &lt;rdeCsv:fStatusDescription&gt; field.</dd
</list></t> >
<t> </dl>
<figure> <t keepWithNext="true">
<preamble> The following is an example of a "hostStatuses" &lt;csvHost:co
Example of a "hostStatuses" &lt;csvHost:contents&gt; &lt;rdeCs ntents&gt; &lt;rdeCsv:csv&gt; element:
v:csv&gt; element. </t>
</preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
<artwork><![CDATA[
... ...
<csvHost:contents> <csvHost:contents>
... ...
<rdeCsv:csv name="hostStatuses"> <rdeCsv:csv name="hostStatuses">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fRoid parent="true"/> <rdeCsv:fRoid parent="true"/>
<csvHost:fStatus/> <csvHost:fStatus/>
<rdeCsv:fStatusDescription/> <rdeCsv:fStatusDescription/>
<rdeCsv:fLang/> <rdeCsv:fLang/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="0DAE0583"> cksum="0DAE0583">
hostStatuses-YYYYMMDD.csv hostStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:contents> </csvHost:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding hostStatuses-YY
<t> YYMMDD.csv file.
<figure>
<preamble>
Example of the corresponding hostStatuses-YYYYMMDD.csv file.
The file contains the statuses for The file contains the statuses for
the six host names ns1.domain1.example, ns2.domain1.example, the six host names ns1.domain1.example, ns2.domain1.example,
ns1.domain2.example, ns2.domain2.example, ns1.example.net and ns ns1.domain2.example, ns2.domain2.example, ns1.example.net, and n
2.example.net. s2.example.net:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
Hns1_domain1_test-TEST,ok,, Hns1_domain1_test-TEST,ok,,
Hns2_domain1_test-TEST,ok,, Hns2_domain1_test-TEST,ok,,
Hns1_domain2_test-TEST,ok,, Hns1_domain2_test-TEST,ok,,
Hns2_domain2_test-TEST,ok,, Hns2_domain2_test-TEST,ok,,
Hns1_example_test-TEST,ok,, Hns1_example_test-TEST,ok,,
Hns2_example_test-TEST,ok,,]]> Hns2_example_test-TEST,ok,,
</artwork> ]]></artwork>
</figure>
</t>
</section> </section>
<section title="&quot;hostAddresses&quot; CSV File Definition" <section anchor="csvHostAddressesDefinition" numbered="true" toc="de
anchor="csvHostAddressesDefinition"> fault">
<t>The "hostAddresses" CSV File Definition defines the fields and CS <name>"hostAddresses" CSV File Definition</name>
V file references <t>The "hostAddresses" CSV File Definition defines the fields and
CSV file references
used for the host object IP addresses.</t> used for the host object IP addresses.</t>
<t>The following "csvHost" field elements MUST be used in the "hostAd dresses" <t>The following "csvHost" field elements <bcp14>MUST</bcp14> be u sed in the "hostAddresses"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<dt>&lt;csvHost:fAddr&gt;</dt>
<t hangText="&lt;csvHost:fAddr&gt;">IP addresses associated with t <dd>IP addresses associated with the host object with type="host
he host object with type="host:addrStringType". The attribute "isRequired" MUST :addrStringType". The attribute "isRequired" <bcp14>MUST</bcp14> equal "true".
equal "true". </dd>
</t> <dt>&lt;csvHost:fAddrVersion&gt;</dt>
<t hangText="&lt;csvHost:fAddrVersion&gt;">IP addresses version associ <dd>IP addresses version associated with the host object with ty
ated with the host object with type="host:ipType". pe="host:ipType".
"host:ipType" has the enumerated values of "v4" or "v6". The attribu "host:ipType" has the enumerated values of "v4" or "v6". The attribu
te "isRequired" MUST equal "true". te "isRequired" <bcp14>MUST</bcp14> equal "true".
</t> </dd>
</dl>
</list></t> <t>The following "rdeCsv" fields, defined in <xref target="csvComm
onFieldElements" format="default">'CSV Common Field Elements'</xref>,
<t>The following "rdeCsv" fields, defined in section <xref target="c <bcp14>MUST</bcp14> be used in the "hostAddresses" &lt;rdeCsv:csv&gt
svCommonFieldElements">CSV common field elements</xref>, ; &lt;rdeCsv:fields&gt; element:
MUST be used in the "hostAddresses" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fi </t>
elds&gt; element: <dl newline="false" spacing="normal">
</t> <dt>&lt;rdeCsv:fRoid&gt;</dt>
<t><list style="hanging"> <dd>Host object ROID assigned to the host object with isRequired
<t hangText="&lt;rdeCsv:fRoid&gt;">Host object Registry Object IDent ="true".</dd>
ifier (ROID) assigned to the host object with isRequired="true".</t> </dl>
</list></t> <t keepWithNext="true">
<t> The following is an example of a "hostAddresses" &lt;csvHost:c
<figure> ontents&gt; &lt;rdeCsv:csv&gt; element:
<preamble> </t>
Example of a "hostAddresses" &lt;csvHost:contents&gt; &lt;rdeC <sourcecode name="" type="xml" markers="false"><![CDATA[
sv:csv&gt; element.
</preamble>
<artwork><![CDATA[
... ...
<csvHost:contents> <csvHost:contents>
... ...
<rdeCsv:csv name="hostAddresses"> <rdeCsv:csv name="hostAddresses">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fRoid parent="true"/> <rdeCsv:fRoid parent="true"/>
<csvHost:fAddr isRequired="true"/> <csvHost:fAddr isRequired="true"/>
<csvHost:fAddrVersion isRequired="true"/> <csvHost:fAddrVersion isRequired="true"/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="28B194B0"> cksum="28B194B0">
hostAddresses-YYYYMMDD.csv hostAddresses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:contents> </csvHost:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding hostAddresses-Y
<t> YYYMMDD.csv file.
<figure>
<preamble>
Example of the corresponding hostAddresses-YYYYMMDD.csv file.
The file contains the IP addresses for The file contains the IP addresses for
the host names ns1.domain1.example, ns2.domain1.example, the host names ns1.domain1.example, ns2.domain1.example,
ns1.domain2.example and ns2.domain2.example. ns1.domain2.example, and ns2.domain2.example:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
Hns1_domain1_test-TEST,192.0.2.1,v4 Hns1_domain1_test-TEST,192.0.2.1,v4
Hns2_domain1_test-TEST,2001:DB8::1,v6 Hns2_domain1_test-TEST,2001:DB8::1,v6
Hns1_domain2_test-TEST,192.0.2.2,v4 Hns1_domain2_test-TEST,192.0.2.2,v4
Hns2_domain2_test-TEST,2001:DB8::2,v6]]> Hns2_domain2_test-TEST,2001:DB8::2,v6
</artwork> ]]></artwork>
</figure> </section>
</t>
</section> </section>
<section anchor="csvHostDeletes" numbered="true" toc="default">
</section> <name>&lt;csvHost:deletes&gt;</name>
<t>
<section title="&lt;csvHost:deletes&gt;" anchor="csvHostDeletes">
<t>
The &lt;csvHost:deletes&gt; is used to hold the deleted host o bjects in a Differential or Incremental Deposit. The &lt;csvHost:deletes&gt; is used to hold the deleted host o bjects in a Differential or Incremental Deposit.
All the host object data is deleted as part of a cascade delet e. The &lt;csvHost:deletes&gt; is split into All the host object data is deleted as part of a cascade delet e. The &lt;csvHost:deletes&gt; is split into
separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute. separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute.
The following section defines the supported host deletes CSV f ile definition. The following section defines the supported host deletes CSV f ile definition.
</t>
<section title="&quot;host&quot; Deletes CSV File Definition"
anchor="csvHostDeletesDefinition">
<t>The following "rdeCsv" fields, defined in section <xref target="c
svCommonFieldElements">CSV common field elements</xref>,
MUST be used in the "host" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt
; element:
</t> </t>
<t><list style="hanging"> <section anchor="csvHostDeletesDefinition" numbered="true" toc="defa
<t hangText="&lt;rdeCsv:fRoid&gt;">Repository Object IDentifier (R ult">
OID) assigned to the host object with isRequired="true".</t> <name>"host" Deletes CSV File Definition</name>
</list></t> <t>The following "rdeCsv" fields, defined in <xref target="csvComm
<t> onFieldElements" format="default">'CSV Common Field Elements'</xref>,
<figure> <bcp14>MUST</bcp14> be used in the "host" &lt;rdeCsv:csv&gt; &lt;r
<preamble> deCsv:fields&gt; element:
Example of a "host" &lt;csvHost:deletes&gt; &lt;rdeCsv:csv&gt; e </t>
lement. <dl newline="false" spacing="normal">
</preamble> <dt>&lt;rdeCsv:fRoid&gt;</dt>
<artwork><![CDATA[ <dd>ROID assigned to the host object with isRequired="true".</dd
>
</dl>
<t keepWithNext="true">
The following is an example of a "host" &lt;csvHost:deletes&gt;
&lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvHost:deletes> <csvHost:deletes>
... ...
<rdeCsv:csv name="host"> <rdeCsv:csv name="host">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="777F5F0E"> cksum="777F5F0E">
host-delete-YYYYMMDD.csv host-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvHost:deletes> </csvHost:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the host-delete-YYYYMMDD.csv file
<t> .
<figure> The file contains four host records:
<preamble> </t>
Example of the host-delete-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains four host records.
</preamble>
<artwork><![CDATA[
Hns1_domain1_test-TEST Hns1_domain1_test-TEST
Hns2_domain1_test-TEST Hns2_domain1_test-TEST
Hns1_domain2_test-TEST Hns1_domain2_test-TEST
Hns2_domain2_test-TEST]]> Hns2_domain2_test-TEST
</artwork> ]]></artwork>
</figure>
</t>
</section>
</section>
</section>
</section> </section>
</section>
<section title="Contact Object" anchor="contactObject"> </section>
<t> </section>
The contact object is based on the EPP contact name mapping <section anchor="contactObject" numbered="true" toc="default">
in <xref target="RFC5733"/>. The <name>Contact Object</name>
contact object supports both the XML Model and the CSV Model <t>
, defined in <xref target="models">Models</xref> section. The The contact object is based on the EPP contact name mapping
in <xref target="RFC5733" format="default"/>. The
contact object supports both the XML model and the CSV model
, defined in <xref target="models" format="default">'Models'</xref>. The
elements used for both models are defined in the following s ections. elements used for both models are defined in the following s ections.
</t> </t>
<section anchor="contactXmlModel" numbered="true" toc="default">
<section title="XML Model" anchor="contactXmlModel"> <name>XML Model</name>
<t>There are <t>There are
two elements used in the data escrow of the contact objects f or the XML model including the two elements used in the data escrow of the contact objects f or the XML model including the
&lt;rdeContact:contact&gt;, under the &lt;rdeContact:contents &gt; element, and the &lt;rdeContact:delete&gt; element, &lt;rdeContact:contact&gt; element, under the &lt;rdeContact: contents&gt; element, and the &lt;rdeContact:delete&gt; element,
under the &lt;rde:deletes&gt; element. under the &lt;rde:deletes&gt; element.
</t> </t>
<t>
<t>
A &lt;contact&gt; element substitutes for the &lt;abstractCo ntact&gt; A &lt;contact&gt; element substitutes for the &lt;abstractCo ntact&gt;
abstract element to define a concrete definition of a contac t. The abstract element to create a concrete definition of a contac t. The
&lt;abstractContact&gt; element can be replaced by other con tact definitions &lt;abstractContact&gt; element can be replaced by other con tact definitions
using the XML schema substitution groups feature. using the XML schema substitution groups feature.
</t> </t>
<section title="&lt;rdeContact:contact&gt; object" anchor="rdeCo <section anchor="rdeContactElement" numbered="true" toc="default">
ntactElement"> <name>&lt;rdeContact:contact&gt; Object</name>
<t>
<t>
The contact object is based on the EPP contact &lt;info& gt; The contact object is based on the EPP contact &lt;info& gt;
response for an authorized client (Section 3.1.2. of <xr response for an authorized client (<xref target="RFC5733
ef target="RFC5733"/>) with " section="3.1.2" sectionFormat="of" format="default"/>) with
some additions including the data from an EPP &lt;transf some additions including the data from an EPP &lt;transf
er&gt; Query Response, see er&gt; query response, see
Section 3.1.3. of <xref target="RFC5733"/>. <xref target="RFC5733" section="3.1.3" sectionFormat="of
</t> " format="default"/>.
<t> </t>
The OPTIONAL &lt;contact&gt; element contains the follow <t>
ing child elements: The <bcp14>OPTIONAL</bcp14> &lt;contact&gt; element cont
</t> ains the following child elements:
<t> </t>
<list style="symbols"> <ul spacing="normal">
<t> <li>
A &lt;id&gt; element that contains the server-unique identifier A &lt;id&gt; element that contains the server-unique identifier
of the contact object of the contact object.
</t> </li>
<t> <li>
A &lt;roid&gt; element that contains the Repository A &lt;roid&gt; element that contains the ROID
Object assigned to the contact object when the object was
IDentifier assigned to the contact object when the o
bject was
created. created.
</t> </li>
<t> <li>
One or more &lt;status&gt; elements that describ e the status of the contact object. One or more &lt;status&gt; elements that describ e the status of the contact object.
</t> </li>
<t> <li>
<t>
One or two &lt;postalInfo&gt; elements that cont ain postal-address information. Two elements One or two &lt;postalInfo&gt; elements that cont ain postal-address information. Two elements
are provided so that address information can be provided in both internationalized and localized are provided so that address information can be provided in both internationalized and localized
forms; a "type" attribute is used to identify th e two forms. If an internationalized form forms; a "type" attribute is used to identify th e two forms. If an internationalized form
(type="int") is provided, element content MUST b e represented in a subset of UTF-8 that can be (type="int") is provided, element content <bcp14 >MUST</bcp14> be represented in a subset of UTF-8 that can be
represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided, represented in the 7-bit US-ASCII character set. If a localized form (type="loc") is provided,
element content MAY be represented in unrestrict ed UTF-8. The &lt;postalInfo&gt; element contains element content <bcp14>MAY</bcp14> be represente d in unrestricted UTF-8. The &lt;postalInfo&gt; element contains
the following child elements: the following child elements:
<list style="symbols"> </t>
<t> <ul spacing="normal">
<li>
A &lt;name&gt; element that contains the name of the individual or role represented by A &lt;name&gt; element that contains the name of the individual or role represented by
the contact. the contact.
</t> </li>
<li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;org&g
An OPTIONAL &lt;org&gt; element that t; element that contains the name of the organization with which the contact
contains the name of the organization with which the contact
is affiliated. is affiliated.
</t> </li>
<t> <li>
<t>
An &lt;addr&gt; element that contain s address information associated with the contact. An &lt;addr&gt; element that contain s address information associated with the contact.
An &lt;addr&gt; element contains the following child elements: An &lt;addr&gt; element contains the following child elements:
<list style="symbols"> </t>
<ul spacing="normal">
<t> <li>
One, two, or three OPTIONAL One, two, or three <bcp14>OP
&lt;street&gt; elements that contain the contact's street TIONAL</bcp14> &lt;street&gt; elements that contain the contact's street
address. address.
</t> </li>
<li>
<t>
A &lt;city&gt; element that contains the contact's city. A &lt;city&gt; element that contains the contact's city.
</t> </li>
<li>
<t> An <bcp14>OPTIONAL</bcp14> &
An OPTIONAL &lt;sp&gt; eleme lt;sp&gt; element that contains the contact's state or province.
nt that contains the contact's state or province. </li>
</t> <li>
An <bcp14>OPTIONAL</bcp14> &
<t> lt;pc&gt; element that contains the contact's postal code.
An OPTIONAL &lt;pc&gt; eleme </li>
nt that contains the contact's postal code. <li>
</t>
<t>
A &lt;cc&gt; element that co ntains the contact's two-letter country code. A &lt;cc&gt; element that co ntains the contact's two-letter country code.
</t> </li>
</list> </ul>
</t> </li>
</list> </ul>
</t> </li>
<li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;voice&gt; element
An OPTIONAL &lt;voice&gt; element that contains that contains the contact's voice telephone number.
the contact's voice telephone number. </li>
</t> <li>
An <bcp14>OPTIONAL</bcp14> &lt;fax&gt; element t
<t> hat contains the contact's facsimile telephone number.
An OPTIONAL &lt;fax&gt; element that contains th </li>
e contact's facsimile telephone number. <li>
</t>
<t>
An &lt;email&gt; element that contains the conta ct's email address. An &lt;email&gt; element that contains the conta ct's email address.
</t> </li>
<t> <li>
A &lt;clID&gt; element that contains the identif ier of the sponsoring registrar. A &lt;clID&gt; element that contains the identif ier of the sponsoring registrar.
</t> </li>
<t> <li>
An OPTIONAL &lt;crRr&gt; element that contains t An <bcp14>OPTIONAL</bcp14> &lt;crRr&gt; element
he identifier of the registrar that created the contact that contains the identifier of the registrar that created the contact
object. An OPTIONAL client attribute is used to object. An <bcp14>OPTIONAL</bcp14> "client" attr
specify the client that performed the operation. ibute is used to specify the client that performed the operation.
</t> </li>
<t> <li>
An OPTIONAL &lt;crDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;crDate&gt; elemen
the date and time of contact-object creation. t that contains the date and time of contact object creation.
</t> </li>
<t> <li>
An OPTIONAL &lt;upRr&gt; element that contains t An <bcp14>OPTIONAL</bcp14> &lt;upRr&gt; element
he identifier of the registrar that last updated the contact that contains the identifier of the registrar that last updated the contact
object. This element MUST NOT be present if the object. This element <bcp14>MUST NOT</bcp14> be
contact has never been modified. An OPTIONAL client present if the contact has never been modified. An <bcp14>OPTIONAL</bcp14> "clie
nt"
attribute is used to specify the client that per formed the operation. attribute is used to specify the client that per formed the operation.
</t> </li>
<t> <li>
An OPTIONAL &lt;upDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;upDate&gt; elemen
the date and time of the most recent contact-object t that contains the date and time of the most recent contact object
modification. This element MUST NOT be present i modification. This element <bcp14>MUST NOT</bcp1
f the contact object has never been modified. 4> be present if the contact object has never been modified.
</t> </li>
<t> <li>
An OPTIONAL &lt;trDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;trDate&gt; elemen
the date and time of the most recent contact object t that contains the date and time of the most recent contact object
successful transfer. This element MUST NOT be pr successful transfer. This element <bcp14>MUST NO
esent if the contact object has never been transferred. T</bcp14> be present if the contact object has never been transferred.
</t> </li>
<t> <li>
An OPTIONAL &lt;trnData&gt; element that contain <t>
s the following child elements related to the last transfer An <bcp14>OPTIONAL</bcp14> &lt;trnData&gt; eleme
nt that contains the following child elements related to the last transfer
request of the contact object: request of the contact object:
<list style="symbols"> </t>
<t> <ul spacing="normal">
<li>
A &lt;trStatus&gt; element that contains the state of the most recent transfer request. A &lt;trStatus&gt; element that contains the state of the most recent transfer request.
</t> </li>
<t> <li>
A &lt;reRr&gt; element that contains the An &lt;reRr&gt; element that contains th
identifier of the registrar that requested e identifier of the registrar that requested
the domain name object transfer. An OPTI the domain name object transfer. An <bcp
ONAL client attribute is used to specify 14>OPTIONAL</bcp14> "client" attribute is used to specify
the client that performed the operation. the client that performed the operation.
</t> </li>
<t> <li>
An &lt;acRr&gt; element that contains th e identifier of the registrar that should act upon An &lt;acRr&gt; element that contains th e identifier of the registrar that should act upon
a PENDING transfer request. For all othe a pending transfer request. For all othe
r status types, the value identifies the registrar r status types, the value identifies the registrar
that took the indicated action. An OPTIO that took the indicated action. An <bcp1
NAL client attribute is used to specify 4>OPTIONAL</bcp14> "client" attribute is used to specify
the client that performed the operation. the client that performed the operation.
</t> </li>
<t> <li>
A &lt;reDate&gt; element that contains t An &lt;reDate&gt; element that contains
he date and time that the transfer was requested. the date and time that the transfer was requested.
</t> </li>
<t> <li>
An &lt;acDate&gt; element that contains the date and time of a required or completed An &lt;acDate&gt; element that contains the date and time of a required or completed
response. For a PENDING request, the val ue identifies the date and time by which a response. For a pending request, the val ue identifies the date and time by which a
response is required before an automated response action will be taken by the registry. response is required before an automated response action will be taken by the registry.
For all other status types, the value id entifies the date and time when the request was For all other status types, the value id entifies the date and time when the request was
completed. completed.
</t> </li>
</list> </ul>
</t> </li>
<t> <li>
An OPTIONAL &lt;disclose&gt; element that identi An <bcp14>OPTIONAL</bcp14> &lt;disclose&gt; elem
fies elements that requiring exceptional server-operator ent that identifies elements that requiring exceptional server-operator
handling to allow or restrict disclosure to thir handling to allow or restrict disclosure to thir
d parties. See Section 2.9 of d parties. See
<xref target="RFC5733"/> for a description of th <xref target="RFC5733" section="2.9" sectionForm
e child elements contained within the at="of" format="default"/> for a description of the child elements contained wit
hin the
&lt;disclose&gt; element. &lt;disclose&gt; element.
</t> </li>
</list> </ul>
</t> <t keepWithNext="true">
The following is an example of a &lt;contact&gt; obj
<t> ect:
<figure> </t>
<preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
Example &lt;contact&gt; object:
</preamble>
<artwork><![CDATA[
... ...
<rdeContact:contact> <rdeContact:contact>
<rdeContact:id>sh8013</rdeContact:id> <rdeContact:id>sh8013</rdeContact:id>
<rdeContact:roid>Csh8013-TEST</rdeContact:roid> <rdeContact:roid>Csh8013-TEST</rdeContact:roid>
<rdeContact:status s="linked"/> <rdeContact:status s="linked"/>
<rdeContact:status s="clientDeleteProhibited"/> <rdeContact:status s="clientDeleteProhibited"/>
<rdeContact:postalInfo type="int"> <rdeContact:postalInfo type="int">
<contact:name>John Doe</contact:name> <contact:name>John Doe</contact:name>
<contact:org>Example Inc.</contact:org> <contact:org>Example Inc.</contact:org>
<contact:addr> <contact:addr>
skipping to change at line 2349 skipping to change at line 2199
<rdeContact:reRr client="jstiles">clientW</rdeContact:reRr> <rdeContact:reRr client="jstiles">clientW</rdeContact:reRr>
<rdeContact:reDate>2011-03-08T19:38:00.0Z</rdeContact:reDate> <rdeContact:reDate>2011-03-08T19:38:00.0Z</rdeContact:reDate>
<rdeContact:acRr client="rmiles">RegistrarX</rdeContact:acRr> <rdeContact:acRr client="rmiles">RegistrarX</rdeContact:acRr>
<rdeContact:acDate>2011-03-13T23:59:59.0Z</rdeContact:acDate> <rdeContact:acDate>2011-03-13T23:59:59.0Z</rdeContact:acDate>
</rdeContact:trnData> </rdeContact:trnData>
<rdeContact:disclose flag="0"> <rdeContact:disclose flag="0">
<contact:voice/> <contact:voice/>
<contact:email/> <contact:email/>
</rdeContact:disclose> </rdeContact:disclose>
</rdeContact:contact> </rdeContact:contact>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> <section anchor="del_contact_object" numbered="true" toc="default">
</section> <name>&lt;rdeContact:delete&gt; Object</name>
<t>
<section title="&lt;rdeContact:delete&gt; object" anchor="del_co
ntact_object">
<t>
The &lt;rdeContact:delete&gt; element contains the id of a contact that was deleted. The &lt;rdeContact:delete&gt; element contains the id of a contact that was deleted.
</t> </t>
<t keepWithNext="true">
<t> The following is an example of an &lt;rdeContact:del
<figure> ete&gt; object:
<preamble> </t>
Example of &lt;rdeContact:delete&gt; object: <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeContact:delete> <rdeContact:delete>
<rdeContact:id>sh8013-TEST</rdeContact:id> <rdeContact:id>sh8013-TEST</rdeContact:id>
<rdeContact:id>co8013-TEST</rdeContact:id> <rdeContact:id>co8013-TEST</rdeContact:id>
</rdeContact:delete> </rdeContact:delete>
... ...
</rde:deletes> </rde:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> </section>
</section> <section anchor="contactCsvModel" numbered="true" toc="default">
<name>CSV Model</name>
</section> <t>For the CSV model of the contact object, the &lt;csvContact:content
s&gt; child
<section title="CSV Model" anchor="contactCsvModel">
<t>For the CSV Model of the contact object, the &lt;csvContact:c
ontents&gt; child
element of the &lt;rde:contents&gt; element is used to hold t he new or updated contacts objects for the deposit. element of the &lt;rde:contents&gt; element is used to hold t he new or updated contacts objects for the deposit.
The &lt;csvContact:deletes&gt; child element of the &lt;rde:d eletes&gt; element is used to hold the deleted or The &lt;csvContact:deletes&gt; child element of the &lt;rde:d eletes&gt; element is used to hold the deleted or
purged contact objects for the deposit. Both the &lt;csvCont act:contents&gt; and &lt;csvContact:deletes&gt; purged contact objects for the deposit. Both the &lt;csvCont act:contents&gt; and &lt;csvContact:deletes&gt;
elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te. elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te.
</t> </t>
<t> <t>
Differential and Incremental Deposits are based on changes to the contact objects. The updated contact object Differential and Incremental Deposits are based on changes to the contact objects. The updated contact object
data under the &lt;csvContact:contents&gt; element is a casca de replace down all of the contact CSV files starting with the data under the &lt;csvContact:contents&gt; element is a casca de replace down all of the contact CSV files starting with the
parent <xref target="csvContactDefinition">"contact" CSV File parent <xref target="csvContactDefinition" format="default">'
Definition</xref>. The child CSV file definitions include a &lt;csvContact:fId "contact" CSV File Definition'</xref>. The child CSV file definitions include a
parent="true"&gt; field. &lt;csvContact:fId parent="true"&gt; field.
All the child CSV file definition data for the contact object All the child CSV file definition data for the contact object
s in the parent <xref target="csvContactDefinition">"contact" CSV File Definitio s in the parent <xref target="csvContactDefinition" format="default">'"contact"
n</xref> CSV File Definition'</xref>
MUST first be deleted and then set using the data in the chil <bcp14>MUST</bcp14> first be deleted and then set using the d
d CSV files. The deleted contact object data under the &lt;csvContact:deletes&g ata in the child CSV files. The deleted contact object data under the &lt;csvCo
t; ntact:deletes&gt;
element is a cascade delete starting from the <xref target="c element is a cascade delete starting from the <xref target="c
svContactDeletesDefinition">"contact" Deletes CSV File Definition</xref>. svContactDeletesDefinition" format="default">'"contact" Deletes CSV File Definit
</t> ion'</xref>.
</t>
<section title="&lt;csvContact:contents&gt;" anchor="csvContactCo <section anchor="csvContactContents" numbered="true" toc="default">
ntents"> <name>&lt;csvContact:contents&gt;</name>
<t>The &lt;csvContact:contents&gt; is used to hold the new or <t>The &lt;csvContact:contents&gt; is used to hold the new or update
updated contact object information for the deposit. d contact object information for the deposit.
The &lt;csvContact:contents&gt; is split into separate CSV fil e definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute. The &lt;csvContact:contents&gt; is split into separate CSV fil e definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute.
The following sections include the supported contact CSV file definitions. The following sections include the supported contact CSV file definitions.
</t> </t>
<section title="&quot;contact&quot; CSV File Definition" ancho <section anchor="csvContactDefinition" numbered="true" toc="default"
r="csvContactDefinition"> >
<name>"contact" CSV File Definition</name>
<t>The "contact" CSV File Definition defines the fields an <t>The "contact" CSV File Definition defines the fields and CSV fi
d CSV file references le references
used for the contact object records. used for the contact object records.
</t> </t>
<t>The following "csvContact" field elements MUST be used <t>The following "csvContact" field elements <bcp14>MUST</bcp14> b
in the e used in the
"contact" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; eleme nt: "contact" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; eleme nt:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<dt>&lt;csvContact:fId&gt;</dt>
<t hangText="&lt;csvContact:fId&gt;">Contains the server <dd>Contains the server-unique contact identifier with type="epp
-unique contact identifier with type="eppcom:clIDType" and isRequired="true". com:clIDType" and isRequired="true".
</t> </dd>
<dt>&lt;csvContact:fEmail&gt;</dt>
<t hangText="&lt;csvContact:fEmail&gt;">Contains the con <dd>Contains the contact's email address with type="eppcom:minTo
tact's email address with type="eppcom:minTokenType" and isRequired="true". kenType" and isRequired="true".
</t> </dd>
</list></t> </dl>
<t>The following field elements <bcp14>MAY</bcp14> be used in the
<t>The following field elements MAY be used in the
"contact" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; eleme nt: "contact" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; eleme nt:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<dt>&lt;csvContact:fVoice&gt;</dt>
<t hangText="&lt;csvContact:fVoice&gt;">Contains the con <dd>Contains the contact's voice telephone number with type="con
tact's voice telephone number with type="contact:e164StringType". tact:e164StringType".
</t> </dd>
<dt>&lt;csvContact:fVoiceExt&gt;</dt>
<t hangText="&lt;csvContact:fVoiceExt&gt;">Contains the <dd>Contains the contact's voice telephone number extension with
contact's voice telephone number extension with type="token". type="token".
</t> </dd>
<dt>&lt;csvContact:fFax&gt;</dt>
<t hangText="&lt;csvContact:fFax&gt;">Contains the conta <dd>Contains the contact's facsimile telephone number with type=
ct's facsimile telephone number with type="contact:e164StringType". "contact:e164StringType".
</t> </dd>
<dt>&lt;csvContact:fFaxExt&gt;</dt>
<t hangText="&lt;csvContact:fFaxExt&gt;">Contains the co <dd>Contains the contact's facsimile telephone number extension
ntact's facsimile telephone number extension with type="token". with type="token".
</t> </dd>
</list></t> </dl>
<t>The following "rdeCsv" and "csvRegistrar" fields, <t>The following "rdeCsv" and "csvRegistrar" fields
MUST be used in the "contact" &lt;rdeCsv:csv&gt; &lt;rde <bcp14>MUST</bcp14> be used in the "contact" &lt;rdeCsv:
Csv:fields&gt; element: csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fRoid&gt;">The Registry Object I <dt>&lt;rdeCsv:fRoid&gt;</dt>
Dentifier (ROID) for the contact object with isRequired="true".</t> <dd>The ROID for the contact object with isRequired="true".</dd>
<t hangText="&lt;rdeCsv:fClID&gt; or &lt;csvRegistrar:fG <dt>&lt;rdeCsv:fClID&gt; or &lt;csvRegistrar:fGurid&gt;</dt>
urid&gt;">A choice of: <dd>
<t>A choice of the following:
<list style="hanging">
<t hangText="&lt;rdeCsv:fClID&gt;">Identifier of the spo
nsoring client with isRequired="true".
</t>
<t hangText="&lt;csvRegistrar:fGurid&gt;">Contains the G </t>
lobally Unique <dl newline="false" spacing="normal">
Registrar Identifier (GURID) assigned by ICANN with type="positiveInteger" a <dt>&lt;rdeCsv:fClID&gt;</dt>
nd isRequired="true". <dd>Identifier of the sponsoring client with isRequired="tru
</t> e".
</list></t> </dd>
</list></t> <dt>&lt;csvRegistrar:fGurid&gt;</dt>
<t>The following "rdeCsv" fields, defined in section <xref <dd>Contains the
target="csvCommonFieldElements">CSV common field elements</xref>, GURID assigned by ICANN with type="positiveInteger" and isRequired="true".
MAY be used in the "contact" &lt;rdeCsv:csv&gt; &lt;rdeC </dd>
sv:fields&gt; element: </dl>
</t> </dd>
<t><list style="hanging"> </dl>
<t hangText="&lt;rdeCsv:fCrRr&gt;">Identifier of <t>The following "rdeCsv" fields, defined in <xref target="csvComm
the registrar, defined in <xref target="registrarObject"/>, of the client that c onFieldElements" format="default">'CSV Common Field Elements'</xref>,
reated the contact object.</t> <bcp14>MAY</bcp14> be used in the "contact" &lt;rdeCsv:c
<t hangText="&lt;rdeCsv:fCrID&gt;">Identifier of the cli sv&gt; &lt;rdeCsv:fields&gt; element:
ent that created the contact object.</t> </t>
<t hangText="&lt;rdeCsv:fUpRr&gt;">Identifier of the reg <dl newline="false" spacing="normal">
istrar, defined in <xref target="registrarObject"/>, of the client that last upd <dt>&lt;rdeCsv:fCrRr&gt;</dt>
ated the contact object.</t> <dd>Identifier of the registrar, defined in <xref target="regist
<t hangText="&lt;rdeCsv:fUpID&gt;">Identifier of the cli rarObject" format="default"/>, of the client that created the contact object.</d
ent that last updated the contact object.</t> d>
<t hangText="&lt;rdeCsv:fCrDate&gt;">Created date and ti <dt>&lt;rdeCsv:fCrID&gt;</dt>
me of the contact object.</t> <dd>Identifier of the client that created the contact object.</d
<t hangText="&lt;rdeCsv:fUpDate&gt;">Date and time of th d>
e last update to the contact object. This field MUST NOT be set if the domain na <dt>&lt;rdeCsv:fUpRr&gt;</dt>
me object has never been modified.</t> <dd>Identifier of the registrar, defined in <xref target="regist
<t hangText="&lt;rdeCsv:fTrDate&gt;">Date and time of th rarObject" format="default"/>, of the client that last updated the contact objec
e last transfer for the contact object. This field MUST NOT be set if the domain t.</dd>
name object has never been transferred.</t> <dt>&lt;rdeCsv:fUpID&gt;</dt>
</list></t> <dd>Identifier of the client that last updated the contact objec
<t> t.</dd>
<figure> <dt>&lt;rdeCsv:fCrDate&gt;</dt>
<preamble> <dd>Date and time of the contact object creation.</dd>
Example of a "contact" &lt;csvContact:contacts&gt; &lt <dt>&lt;rdeCsv:fUpDate&gt;</dt>
;rdeCsv:csv&gt; element. <dd>Date and time of the last update to the contact object. This
</preamble> field <bcp14>MUST NOT</bcp14> be set if the domain name object has never been m
<artwork><![CDATA[ odified.</dd>
<dt>&lt;rdeCsv:fTrDate&gt;</dt>
<dd>Date and time of the last transfer for the contact object. T
his field <bcp14>MUST NOT</bcp14> be set if the domain name object has never bee
n transferred.</dd>
</dl>
<t keepWithNext="true">
The following is an example of a "contact" &lt;csvCont
act:contacts&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contact"> <rdeCsv:csv name="contact">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId/> <csvContact:fId/>
<rdeCsv:fRoid/> <rdeCsv:fRoid/>
<csvContact:fVoice/> <csvContact:fVoice/>
<csvContact:fVoiceExt/> <csvContact:fVoiceExt/>
<csvContact:fFax/> <csvContact:fFax/>
skipping to change at line 2503 skipping to change at line 2353
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="8587AA49"> cksum="8587AA49">
contact-YYYYMMDD.csv contact-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:contents> </csvContact:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the contact-YYYYMMDD.cs
<t> v file.
<figure> The file contains nine object contact records:
<preamble> </t>
Example of the contact-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains nine object contact records.
</preamble>
<artwork><![CDATA[
domain1admin,Cdomain1admin-TEST,+1.7035555555,1234, domain1admin,Cdomain1admin-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain1tech,Cdomain1tech-TEST,+1.7035555555,1234, domain1tech,Cdomain1tech-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain1billing,Cdomain1billing-TEST,+1.7035555555,1234, domain1billing,Cdomain1billing-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain2admin,Cdomain2admin-TEST,+1.7035555555,1234, domain2admin,Cdomain2admin-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain2tech,Cdomain2tech-TEST,+1.7035555555,1234, domain2tech,Cdomain2tech-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
domain2billing,Cdomain2billing-TEST,+1.7035555555,1234, domain2billing,Cdomain2billing-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234, xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234, xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z 2009-11-26T09:10:00.0Z
xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234, xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,registrarX,registarX, +1.7035555556,,jdoe@example.example,registrarX,registrarX,
clientY,2009-09-13T08:01:00.0Z,registarX,clientY, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY,
2009-11-26T09:10:00.0Z]]> 2009-11-26T09:10:00.0Z
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvContactStatusesDefinition" numbered="true" toc="
</section> default">
<section title="&quot;contactStatuses&quot; CSV File Definition <name>"contactStatuses" CSV File Definition</name>
" anchor="csvContactStatusesDefinition"> <t>The "contactStatuses" CSV File Definition defines the fields an
d CSV file references
<t>The "contactStatuses" CSV File Definition defines the fiel
ds and CSV file references
used for the contact object statuses. used for the contact object statuses.
</t> </t>
<t>The following "csvContact" field elements, defined in the <xref
<t>The following "csvContact" field elements, defined for the target="csvContactDefinition" format="default">'"contact" CSV File Definition'<
<xref target="csvContactDefinition">"contact" CSV File Definition</xref>, /xref>,
MUST be used in the "contactStatuses" &lt;rdeCsv:csv&gt; &l <bcp14>MUST</bcp14> be used in the "contactStatuses" &lt;rd
t;rdeCsv:fields&gt; element: eCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvContact:fId&gt;">Server-unique contact <dt>&lt;csvContact:fId&gt;</dt>
identifier of status with isRequired="true" and parent=”true".</t> <dd>Server-unique contact identifier of status with isRequired="
<t hangText="&lt;csvContact:fStatus&gt;">The status of the true" and parent="true".</dd>
contact with type="contact:statusValueType" and isRequired="true".</t> <dt>&lt;csvContact:fStatus&gt;</dt>
</list></t> <dd>The status of the contact with type="contact:statusValueType
" and isRequired="true".</dd>
<t>The following "rdeCsv" fields, defined in section <xref ta </dl>
rget="csvCommonFieldElements">CSV common field elements</xref>, <t>The following "rdeCsv" fields, defined in <xref target="csvComm
MAY be used in the "contactStatuses" &lt;rdeCsv:csv&gt; &lt onFieldElements" format="default">'CSV Common Field Elements'</xref>,
;rdeCsv:fields&gt; element: <bcp14>MAY</bcp14> be used in the "contactStatuses" &lt;rde
</t> Csv:csv&gt; &lt;rdeCsv:fields&gt; element:
<t><list style="hanging"> </t>
<t hangText="&lt;rdeCsv:fStatusDescription&gt;">The contact <dl newline="false" spacing="normal">
object status description which is free form text describing the rationale for <dt>&lt;rdeCsv:fStatusDescription&gt;</dt>
the status.</t> <dd>The contact object status description, which is free-form te
<t hangText="&lt;rdeCsv:fLang&gt;">Language of the &lt;rdeC xt describing the rationale for the status.</dd>
sv:fStatusDescription&gt; field.</t> <dt>&lt;rdeCsv:fLang&gt;</dt>
</list></t> <dd>Language of the &lt;rdeCsv:fStatusDescription&gt; field.</dd
<t> >
<figure> </dl>
<preamble> <t keepWithNext="true">
Example of a "contactStatuses" &lt;csvContact:contents& The following is an example of a "contactStatuses" &lt;
gt; &lt;rdeCsv:csv&gt; element. csvContact:contents&gt; &lt;rdeCsv:csv&gt; element:
</preamble> </t>
<artwork><![CDATA[ <sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contactStatuses"> <rdeCsv:csv name="contactStatuses">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId parent="true"/> <csvContact:fId parent="true"/>
<csvContact:fStatus/> <csvContact:fStatus/>
<rdeCsv:fStatusDescription/> <rdeCsv:fStatusDescription/>
<rdeCsv:fLang/> <rdeCsv:fLang/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="137E13EC"> cksum="137E13EC">
contactStatuses-YYYYMMDD.csv contactStatuses-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:contents> </csvContact:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding conta
<t> ctStatuses-YYYYMMDD.csv file.
<figure>
<preamble>
Example of the corresponding contactStatuses-YYYYMMDD.
csv file.
The file contains the statuses for The file contains the statuses for
the nine contact identifiers. the nine contact identifiers:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
domain1admin,ok,, domain1admin,ok,,
domain1tech,ok,, domain1tech,ok,,
domain1billing,ok,, domain1billing,ok,,
domain2admin,ok,, domain2admin,ok,,
domain2tech,ok,, domain2tech,ok,,
domain2billing,ok,, domain2billing,ok,,
xnabc123admin,ok,, xnabc123admin,ok,,
xnabc123tech,ok,, xnabc123tech,ok,,
xnabc123billing,ok,,]]> xnabc123billing,ok,,
</artwork> ]]></artwork>
</figure>
</t>
</section> </section>
<section title="&quot;contactPostal&quot; CSV File Definition" <section anchor="csvContactPostalDefinition" numbered="true" toc="de
anchor="csvContactPostalDefinition"> fault">
<t>The "contactPostal" CSV File Definition defines the field <name>"contactPostal" CSV File Definition</name>
s and CSV file references <t>The "contactPostal" CSV File Definition defines the fields and
CSV file references
used for the contact postal info object records. used for the contact postal info object records.
</t> </t>
<t>The following "csvContact" field elements MUST be used in <t>The following "csvContact" field elements <bcp14>MUST</bcp14> b
the "contactPostal" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: e used in the "contactPostal" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<dt>&lt;csvContact:fPostalType&gt;</dt>
<t hangText="&lt;csvContact:fPostalType&gt;">Contains the f <dd>Contains the form of the postal address information with typ
orm of the postal-address information with type="contact:postalLineType" and isR e="contact:postalLineType" and isRequired="true".
equired="true". This field specifies the form ("int" or "loc"), as defin
This field specifies the form ("int" or "loc"), as defin ed in <xref target="intandloc" format="default"/>, of the
ed in <xref target="intandloc"/>, of the
&lt;csvContact:fName&gt;, &lt;csvContact:fOrg&gt;, &lt;c svContact:fStreet&gt;, &lt;csvContact:fCity&gt;, &lt;csvContact:fName&gt;, &lt;csvContact:fOrg&gt;, &lt;c svContact:fStreet&gt;, &lt;csvContact:fCity&gt;,
&lt;csvContact:fSp&gt;, &lt;csvContact:fPc&gt;, &lt;csvC &lt;csvContact:fSp&gt;, &lt;csvContact:fPc&gt;, and &lt;
ontact:fCc&gt; fields. csvContact:fCc&gt; fields.
</t> </dd>
<dt>&lt;csvContact:fName&gt;</dt>
<t hangText="&lt;csvContact:fName&gt;">Contains the contac <dd>Contains the contact's name of the individual or role repres
t's name of the individual or role represented by the contact with type="contact ented by the contact with type="contact:postalLineType" and isRequired="true".
:postalLineType" and isRequired="true". An <bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to
An OPTIONAL "isLoc" attribute is used to indicate the lo indicate the localized or internationalized form as defined in <xref target="int
calized or internationalized form as defined in <xref target="intandloc"/>. andloc" format="default"/>.
</t> </dd>
<dt>&lt;csvContact:fStreet&gt;</dt>
<t hangText="&lt;csvContact:fStreet&gt;">Contains the cont <dd>Contains the contact's street address line with type="contac
act's street address line with type="contact:fPostalLineType". An index attribu t:fPostalLineType". An "index" attribute is required to indicate which street a
te is required to indicate which street address line the field represents with i ddress line the field represents with index="0" for the first line and increment
ndex "0" for the first line and incrementing for each line up to index "2" for t ing for each line up to index="2" for the third line.
he third line. An <bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to
An OPTIONAL "isLoc" attribute is used to indicate the lo indicate the localized or internationalized form as defined in <xref target="int
calized or internationalized form as defined in <xref target="intandloc"/>. andloc" format="default"/>.
</t> </dd>
<dt>&lt;csvContact:fCity&gt;</dt>
<t hangText="&lt;csvContact:fCity&gt;">Contains the contac <dd>Contains the contact's city with type="contact:postalLineTyp
t's city with type="contact:postalLineType" and isRequired="true". e" and isRequired="true".
An OPTIONAL "isLoc" attribute is used to indicate the lo An <bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to
calized or internationalized form as defined in <xref target="intandloc"/>. indicate the localized or internationalized form as defined in <xref target="int
</t> andloc" format="default"/>.
</dd>
<t hangText="&lt;csvContact:fCc&gt;">Contains the contact' <dt>&lt;csvContact:fCc&gt;</dt>
s country code with type="contact:ccType" and isRequired="true". <dd>Contains the contact's country code with type="contact:ccTyp
An OPTIONAL "isLoc" attribute is used to indicate the lo e" and isRequired="true".
calized or internationalized form as defined in <xref target="intandloc"/>. An <bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to
</t> indicate the localized or internationalized form as defined in <xref target="int
andloc" format="default"/>.
</list></t> </dd>
</dl>
<t>The following "csvContact" field elements MAY be used in <t>The following "csvContact" field elements <bcp14>MAY</bcp14> be
the "contactPostal" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: used in the "contactPostal" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<dt>&lt;csvContact:fOrg&gt;</dt>
<t hangText="&lt;csvContact:fOrg&gt;">Contains the name of <dd>Contains the name of the organization with which the contact
the organization with which the contact is affiliated with type="contact:optPos is affiliated with type="contact:optPostalLineType".
talLineType". An <bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to
An OPTIONAL "isLoc" attribute is used to indicate the lo indicate the localized or internationalized form as defined in <xref target="int
calized or internationalized form as defined in <xref target="intandloc"/>. andloc" format="default"/>.
</t> </dd>
<dt>&lt;csvContact:fSp&gt;</dt>
<t hangText="&lt;csvContact:fSp&gt;">Contains the contact' <dd>Contains the contact's state or province with type="contact:
s state or province with type="contact:optPostalLineType". optPostalLineType".
An OPTIONAL "isLoc" attribute is used to indicate the lo An <bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to
calized or internationalized form as defined in <xref target="intandloc"/>. indicate the localized or internationalized form as defined in <xref target="int
</t> andloc" format="default"/>.
</dd>
<t hangText="&lt;csvContact:fPc&gt;">Contains the contact' <dt>&lt;csvContact:fPc&gt;</dt>
s postal code with type="contact:pcType". <dd>Contains the contact's postal code with type="contact:pcType
An OPTIONAL "isLoc" attribute is used to indicate the lo ".
calized or internationalized form as defined in <xref target="intandloc"/>. An <bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to
</t> indicate the localized or internationalized form as defined in <xref target="int
andloc" format="default"/>.
</list></t> </dd>
</dl>
<t>The following "csvContact" fields, defined for the <xref <t>The following "csvContact" fields, defined in the <xref target=
target="csvContactDefinition">"contact" CSV File Definition</xref>, "csvContactDefinition" format="default">'"contact" CSV File Definition'</xref>,
MUST be used in the "contactPostal" &lt;rdeCsv:csv&gt; &lt <bcp14>MUST</bcp14> be used in the "contactPostal" &lt;rde
;rdeCsv:fields&gt; element: Csv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvContact:fId&gt;">Server-unique contact <dt>&lt;csvContact:fId&gt;</dt>
identifier for the contact object with isRequired="true" and parent=”true".</t> <dd>Server-unique contact identifier for the contact object with
</list></t> isRequired="true" and parent="true".</dd>
</dl>
<t> <t keepWithNext="true">
<figure> The following is an example of a "contactPostal" &lt;c
<preamble> svContact:contents&gt; &lt;rdeCsv:csv&gt; element:
Example of a "contactPostal" &lt;csvContact:contents&g </t>
t; &lt;rdeCsv:csv&gt; element. <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contactPostal"> <rdeCsv:csv name="contactPostal">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId parent="true"/> <csvContact:fId parent="true"/>
<csvContact:fPostalType/> <csvContact:fPostalType/>
<csvContact:fName/> <csvContact:fName/>
<csvContact:fOrg/> <csvContact:fOrg/>
<csvContact:fStreet index="0"/> <csvContact:fStreet index="0"/>
skipping to change at line 2715 skipping to change at line 2547
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="1456A89C"> cksum="1456A89C">
contactPostal-YYYYMMDD.csv contactPostal-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:contents> </csvContact:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the contactPostal-YYYYM
<t> MDD.csv file.
<figure> The file contains nine contact postal records:
<preamble> </t>
Example of the contactPostal-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains nine contact postal records.
</preamble>
<artwork><![CDATA[
domain1admin,int,"John Doe","Example Inc.", domain1admin,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
domain1tech,int,"John Doe","Example Inc.", domain1tech,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
domain1billing,int,"John Doe","Example Inc.", domain1billing,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
domain2admin,int,"John Doe","Example Inc.", domain2admin,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
domain2tech,int,"John Doe","Example Inc.", domain2tech,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
domain2billing,int,"John Doe","Example Inc.", domain2billing,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
xnabc123admin,int,"John Doe","Example Inc.", xnabc123admin,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
xnabc123tech,int,"John Doe","Example Inc.", xnabc123tech,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US "123 Example Dr.","Suite 100",,Reston,VA,20190,US
xnabc123billing,int,"John Doe","Example Inc.", xnabc123billing,int,"John Doe","Example Inc.",
"123 Example Dr.","Suite 100",,Reston,VA,20190,US]]> "123 Example Dr.","Suite 100",,Reston,VA,20190,US
</artwork> ]]></artwork>
</figure> </section>
</t> <section anchor="csvContactTransferDefinition" numbered="true" toc="
default">
</section> <name>"contactTransfer" CSV File Definition</name>
<section title="&quot;contactTransfer&quot; CSV File Definitio <t>The "contactTransfer" CSV File Definition defines the fields an
n" anchor="csvContactTransferDefinition"> d CSV file references
<t>The "contactTransfer" CSV File Definition defines the fie
lds and CSV file references
used for the contact object pending and completed transfer r ecords. No additional used for the contact object pending and completed transfer r ecords. No additional
field elements were added for use in the "contactTransfer" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element. field elements were added for use in the "contactTransfer" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element.
The following "rdeCsv" fields, defined in section <xref targ The following "rdeCsv" fields, defined in <xref target="csvC
et="csvCommonFieldElements">CSV common field elements</xref>, ommonFieldElements" format="default">'CSV Common Field Elements'</xref>,
MUST be used in the "contactTransfer" &lt;rdeCsv:csv&gt; &lt <bcp14>MUST</bcp14> be used in the "contactTransfer" &lt;rde
;rdeCsv:fields&gt; element: Csv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fTrStatus&gt;">State of the most r <dt>&lt;rdeCsv:fTrStatus&gt;</dt>
ecent transfer request with isRequired="true".</t> <dd>State of the most recent transfer request with isRequired="t
<t hangText="&lt;rdeCsv:fReRr&gt;">Identifier of the regis rue".</dd>
trar, defined in <xref target="registrarObject"/>, of the client that requested <dt>&lt;rdeCsv:fReRr&gt;</dt>
the transfer with isRequired="true".</t> <dd>Identifier of the registrar, defined in <xref target="regist
<t hangText="&lt;rdeCsv:fReDate&gt;">Date and time that th rarObject" format="default"/>, of the client that requested the transfer with is
e transfer was requested with isRequired="true".</t> Required="true".</dd>
<t hangText="&lt;rdeCsv:fAcRr&gt;">Identifier of the regis <dt>&lt;rdeCsv:fReDate&gt;</dt>
trar, defined in <xref target="registrarObject"/>, of the client that should tak <dd>Date and time that the transfer was requested with isRequire
e or took action with isRequired="true".</t> d="true".</dd>
<t hangText="&lt;rdeCsv:fAcDate&gt;">Date and time that th <dt>&lt;rdeCsv:fAcRr&gt;</dt>
e transfer action should be taken or has been taken with isRequired="true".</t> <dd>Identifier of the registrar, defined in <xref target="regist
</list></t> rarObject" format="default"/>, of the client that should take or took action wit
<t>The following "rdeCsv" fields, defined in section <xref t h isRequired="true".</dd>
arget="csvCommonFieldElements">CSV common field elements</xref>, <dt>&lt;rdeCsv:fAcDate&gt;</dt>
MAY be used in the "contactTransfer" &lt;rdeCsv:csv&gt; &l <dd>Date and time that the transfer action should be taken or ha
t;rdeCsv:fields&gt; element: s been taken with isRequired="true".</dd>
</t> </dl>
<t><list style="hanging"> <t>The following "rdeCsv" fields, defined in <xref target="csvComm
<t hangText="&lt;rdeCsv:fReID&gt;">Identifier of the clien onFieldElements" format="default">'CSV Common Field Elements'</xref>,
t that requested the transfer.</t> <bcp14>MAY</bcp14> be used in the "contactTransfer" &lt;rd
<t hangText="&lt;rdeCsv:fAcID&gt;">Identifier of the clien eCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
t that should take or took action for transfer.</t> </t>
</list></t> <dl newline="false" spacing="normal">
<t>The following "csvContact" fields, defined for the <xref <dt>&lt;rdeCsv:fReID&gt;</dt>
target="csvContactDefinition">"contact" CSV File Definition</xref>, <dd>Identifier of the client that requested the transfer.</dd>
MUST be used in the "contactTransfer" &lt;rdeCsv:csv&gt; & <dt>&lt;rdeCsv:fAcID&gt;</dt>
lt;rdeCsv:fields&gt; element: <dd>Identifier of the client that should take or took action for
</t> transfer.</dd>
<t><list style="hanging"> </dl>
<t hangText="&lt;csvContact:fId&gt;">Server-unique contact <t>The following "csvContact" fields, defined for the <xref target
identifier for the contact object with isRequired="true".</t> ="csvContactDefinition" format="default">'"contact" CSV File Definition'</xref>,
</list></t> <bcp14>MUST</bcp14> be used in the "contactTransfer" &lt;r
deCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
<t> </t>
<figure> <dl newline="false" spacing="normal">
<preamble> <dt>&lt;csvContact:fId&gt;</dt>
Example of a "contactTransfer" &lt;csvContact:contents <dd>Server-unique contact identifier for the contact object with
&gt; &lt;rdeCsv:csv&gt; element. isRequired="true".</dd>
</preamble> </dl>
<artwork><![CDATA[ <t keepWithNext="true">
The following is an example of a "contactTransfer" &lt
;csvContact:contents&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contactTransfer"> <rdeCsv:csv name="contactTransfer">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId parent="true"/> <csvContact:fId parent="true"/>
<rdeCsv:fTrStatus/> <rdeCsv:fTrStatus/>
<rdeCsv:fReRr/> <rdeCsv:fReRr/>
<rdeCsv:fReID/> <rdeCsv:fReID/>
<rdeCsv:fReDate/> <rdeCsv:fReDate/>
skipping to change at line 2806 skipping to change at line 2637
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="788D308E"> cksum="788D308E">
contactTransfer-YYYYMMDD.csv contactTransfer-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:contents> </csvContact:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the contactTransfer-YYY
<t> YMMDD.csv file.
<figure> The file contains one contact transfer record in pendi
<preamble> ng status:
Example of the contactTransfer-YYYYMMDD.csv file. </t>
The file contains one contact transfer record in pendi <artwork name="" type="" align="left" alt=""><![CDATA[
ng status.
</preamble>
<artwork><![CDATA[
xnabc123admin,clientApproved,registrarX,clientX, xnabc123admin,clientApproved,registrarX,clientX,
2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z]]> 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z
</artwork> ]]></artwork>
</figure>
</t>
</section> </section>
<section title="&quot;contactDisclose&quot; CSV File Definitio <section anchor="csvContactDiscloseDefinition" numbered="true" toc="
n" anchor="csvContactDiscloseDefinition"> default">
<t>The "contactDisclose" CSV File Definition defines the fie <name>"contactDisclose" CSV File Definition</name>
lds and CSV file references <t>The "contactDisclose" CSV File Definition defines the fields an
d CSV file references
used for the contact disclose object records.</t> used for the contact disclose object records.</t>
<t>The following "csvContact" field elements MAY be used in the "contactDisclose" <t>The following "csvContact" field elements <bcp14>MAY</bcp14> be used in the "contactDisclose"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<dt>&lt;csvContact:fDiscloseFlag&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseFlag&gt;">Contains fl <dd>Contains flag with a value of "true" or "1" (one) notes the
ag with a value of "true" or "1" (one) notes the preference preference
to allow disclosure of the specified elements as an exce ption to the stated data-collection policy. to allow disclosure of the specified elements as an exce ption to the stated data-collection policy.
A value of "false" or "0" (zero) notes a client preferen ce to not allow disclosure of the specified elements as an exception A value of "false" or "0" (zero) notes a client preferen ce to not allow disclosure of the specified elements as an exception
to the stated data-collection policy with type="boolean" . The additional fields define specific exceptional disclosure to the stated data-collection policy with type="boolean" . The additional fields define specific exceptional disclosure
preferences based on the &lt;csvContact:fDiscloseFlag&gt ; field. preferences based on the &lt;csvContact:fDiscloseFlag&gt ; field.
</t> </dd>
<dt>&lt;csvContact:fDiscloseNameLoc&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseNameLoc&gt;">Exceptio <dd>Exceptional disclosure preference flag for the localized for
nal disclosure preference flag for the localized form of the m of the
contact name with type="boolean". contact name with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseNameInt&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseNameInt&gt;">Exceptio <dd>Exceptional disclosure preference flag for the international
nal disclosure preference flag for the internationalized form of the ized form of the
contact name with type="boolean". contact name with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseOrgLoc&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseOrgLoc&gt;">Exception <dd>Exceptional disclosure preference flag for the localized for
al disclosure preference flag for the localized form of the m of the
contact organization with type="boolean". contact organization with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseOrgInt&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseOrgInt&gt;">Exception <dd>Exceptional disclosure preference flag for the international
al disclosure preference flag for the internationalized form of the ized form of the
contact organization with type="boolean". contact organization with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseAddrLoc&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseAddrLoc&gt;">Exceptio <dd>Exceptional disclosure preference flag for the localized for
nal disclosure preference flag for the localized form of the m of the
contact address with type="boolean". contact address with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseAddrInt&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseAddrInt&gt;">Exceptio <dd>Exceptional disclosure preference flag for the international
nal disclosure preference flag for the internationalized form of the ized form of the
contact address with type="boolean". contact address with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseVoice&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseVoice&gt;">Exceptiona <dd>Exceptional disclosure preference flag of the
l disclosure preference flag of the
contact voice telephone number with type="boolean". contact voice telephone number with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseFax&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseFax&gt;">Exceptional <dd>Exceptional disclosure preference flag of the
disclosure preference flag of the
contact facsimile telephone number with type="boolean". contact facsimile telephone number with type="boolean".
</t> </dd>
<dt>&lt;csvContact:fDiscloseEmail&gt;</dt>
<t hangText="&lt;csvContact:fDiscloseEmail&gt;">Exceptiona <dd>Exceptional disclosure preference flag of the
l disclosure preference flag of the
contact email address with type="boolean". contact email address with type="boolean".
</t> </dd>
</dl>
</list></t> <t>The following "csvContact" fields, defined for the <xref target
<t>The following "csvContact" fields, defined for the <xref ="csvContactDefinition" format="default">'"contact" CSV File Definition'</xref>,
target="csvContactDefinition">"contact" CSV File Definition</xref>, <bcp14>MUST</bcp14> be used in the "contactDisclose" &lt;r
MUST be used in the "contactDisclose" &lt;rdeCsv:csv&gt; & deCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
lt;rdeCsv:fields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvContact:fId&gt;</dt>
<t hangText="&lt;csvContact:fId&gt;">Server-unique contact <dd>Server-unique contact identifier for the contact object with
identifier for the contact object with isRequired="true".</t> isRequired="true".</dd>
</list></t> </dl>
<t keepWithNext="true">
<t> The following is an example of a "contactDisclose" &lt
<figure> ;csvContact:contents&gt; &lt;rdeCsv:csv&gt; element:
<preamble> </t>
Example of a "contactDisclose" &lt;csvContact:contents <sourcecode name="" type="xml" markers="false"><![CDATA[
&gt; &lt;rdeCsv:csv&gt; element.
</preamble>
<artwork><![CDATA[
... ...
<csvContact:contents> <csvContact:contents>
... ...
<rdeCsv:csv name="contactDisclose"> <rdeCsv:csv name="contactDisclose">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId parent="true"/> <csvContact:fId parent="true"/>
<csvContact:fDiscloseFlag/> <csvContact:fDiscloseFlag/>
<csvContact:fDiscloseNameLoc/> <csvContact:fDiscloseNameLoc/>
<csvContact:fDiscloseNameInt/> <csvContact:fDiscloseNameInt/>
<csvContact:fDiscloseOrgLoc/> <csvContact:fDiscloseOrgLoc/>
skipping to change at line 2915 skipping to change at line 2737
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="1141EFD4"> cksum="1141EFD4">
contactDisclose-YYYYMMDD.csv contactDisclose-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:contents> </csvContact:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the contactDisclose-YYY
<t> YMMDD.csv file.
<figure>
<preamble>
Example of the contactDisclose-YYYYMMDD.csv file.
The file contains one disclosure records, disabling The file contains one disclosure records, disabling
disclosure of voice, fax, and email. disclosure of voice, fax, and email:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
xnabc123admin,0,0,0,0,0,0,0,1,1,1]]> xnabc123admin,0,0,0,0,0,0,0,1,1,1
</artwork> ]]></artwork>
</figure> </section>
</t> </section>
<section anchor="csvContactDeletes" numbered="true" toc="default">
</section> <name>&lt;csvContact:deletes&gt;</name>
<t>
</section>
<section title="&lt;csvContact:deletes&gt;" anchor="csvContactDel
etes">
<t>
The &lt;csvContact:deletes&gt; is used to hold the deleted con tact objects in a Differential or Incremental Deposit. The &lt;csvContact:deletes&gt; is used to hold the deleted con tact objects in a Differential or Incremental Deposit.
All the contact object data is deleted as part of a cascade de lete. The &lt;csvContact:deletes&gt; is split into All the contact object data is deleted as part of a cascade de lete. The &lt;csvContact:deletes&gt; is split into
separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute. separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute.
The following section defines the supported contact deletes CS V file definition. The following section defines the supported contact deletes CS V file definition.
</t>
<section title="&quot;contact&quot; Deletes CSV File Definitio
n" anchor="csvContactDeletesDefinition">
<t>
The following "csvContact" field elements MUST be used in th
e deletes "contact"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <section anchor="csvContactDeletesDefinition" numbered="true" toc="d
<t hangText="&lt;csvContact:fId&gt;">Contains the server efault">
-unique contact identifier with type="eppcom:clIDType" and isRequired="true". <name>"contact" Deletes CSV File Definition</name>
</t> <t>
</list></t> The following "csvContact" field elements <bcp14>MUST</bcp14
<t> > be used in the deletes "contact"
<figure> &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
<preamble> </t>
Example of a "contact" &lt;csvContact:deletes&gt; &lt; <dl newline="false" spacing="normal">
rdeCsv:csv&gt; element. <dt>&lt;csvContact:fId&gt;</dt>
</preamble> <dd>Contains the server-unique contact identifier with type="epp
<artwork><![CDATA[ com:clIDType" and isRequired="true".
</dd>
</dl>
<t keepWithNext="true">
The following is an example of a "contact" &lt;csvCont
act:deletes&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvContact:deletes> <csvContact:deletes>
... ...
<rdeCsv:csv name="contact"> <rdeCsv:csv name="contact">
<rdeCsv:fields> <rdeCsv:fields>
<csvContact:fId/> <csvContact:fId/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="0C4B70DC"> cksum="0C4B70DC">
contact-delete-YYYYMMDD.csv contact-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvContact:deletes> </csvContact:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the contact-delete-YYYY
<t> MMDD.csv file.
<figure> The file contains six contact records:
<preamble> </t>
Example of the contact-delete-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains six contact records.
</preamble>
<artwork><![CDATA[
domain1admin domain1admin
domain1tech domain1tech
domain1billing domain1billing
domain2admin domain2admin
domain2tech domain2tech
domain2billing]]> domain2billing
</artwork> ]]></artwork>
</figure> </section>
</t>
</section> </section>
</section> </section>
</section>
</section> <section anchor="registrarObject" numbered="true" toc="default">
<name>Registrar Object</name>
</section> <t>
The registrar object represents the sponsoring client for ot
<section title="Registrar Object" anchor="registrarObject"> her objects and is typically referred to as the sponsoring registrar.
<t> The registrar object supports both the XML model and the CSV
The registrar object represents the sponsoring client for ot model, defined in <xref target="models" format="default"/>. The
her objects, and is typically referred to as the sponsoring registrar.
The registrar object supports both the XML Model and the CSV
Model, defined in <xref target="models"/>. The
elements used for both models are defined in the following s ections. elements used for both models are defined in the following s ections.
</t> </t>
<section anchor="registrarXmlModel" numbered="true" toc="default">
<section title="XML Model" anchor="registrarXmlModel"> <name>XML Model</name>
<t>There are <t>There are
two elements used in the data escrow of the registrar objects for the XML model including the two elements used in the data escrow of the registrar objects for the XML model including the
&lt;rdeRegistrar:registrar&gt;, under the &lt;rdeRegistrar:co ntents&gt; element, and the &lt;rdeRegistrar:delete&gt; element, &lt;rdeRegistrar:registrar&gt; element, under the &lt;rdeRegi strar:contents&gt; element, and the &lt;rdeRegistrar:delete&gt; element,
under the &lt;rde:deletes&gt; element. under the &lt;rde:deletes&gt; element.
</t> </t>
<t> <t>
A &lt;rdeRegistrar:registrar&gt; element substitutes for the An &lt;rdeRegistrar:registrar&gt; element substitutes for th
&lt;rdeRegistrar:abstractRegistrar&gt; e &lt;rdeRegistrar:abstractRegistrar&gt;
abstract element to define a concrete definition of a regist abstract element to create a concrete definition of a regist
rar. The rar. The
&lt;rdeRegistrar:abstractRegistrar&gt; element can be replac ed by other domain definitions &lt;rdeRegistrar:abstractRegistrar&gt; element can be replac ed by other domain definitions
using the XML schema substitution groups feature. using the XML schema substitution groups feature.
</t> </t>
<section title="&lt;rdeRegistrar:registrar&gt; element" anchor=" <section anchor="rdeRegistrarElement" numbered="true" toc="default">
rdeRegistrarElement"> <name>&lt;rdeRegistrar:registrar&gt; Element</name>
<t> <t>
The &lt;registrar&gt; element contains the following chi ld elements: The &lt;registrar&gt; element contains the following chi ld elements:
</t> </t>
<t> <ul spacing="normal">
<list style="symbols"> <li>
<t> An &lt;id&gt; element that contains the registry
An &lt;id&gt; element that contains the Registry -unique identifier of the
-unique identifier of the
registrar object. This &lt;id&gt; has a superord inate relationship to a subordinate registrar object. This &lt;id&gt; has a superord inate relationship to a subordinate
unique identifier of the &lt;clID&gt;, &lt;crRr&gt;, or &lt;upRr&gt; of d
&lt;clID&gt;, &lt;crRr&gt; or &lt;upRr&gt; of do omain, contact, and host objects.
main, contact and host objects. </li>
</t> <li>
<t>
An &lt;name&gt; element that contains the name o f the registrar. An &lt;name&gt; element that contains the name o f the registrar.
</t> </li>
<t> <li>
An OPTIONAL &lt;gurid&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;gurid&gt; element
the Globally Unique that contains the
Registrar Identifier (GURID) assigned by ICANN. GURID assigned by ICANN.
</t> </li>
<t> <li>
An OPTIONAL &lt;status&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;status&gt; elemen
the operational status of the registrar. Possible t that contains the operational status of the registrar. Possible
values are: ok, readonly and terminated. values are: ok, readonly, and terminated.
</t> </li>
<t> <li>
One or two OPTIONAL &lt;postalInfo&gt; elements <t>
that contain postal- One or two <bcp14>OPTIONAL</bcp14> &lt;postalInf
o&gt; elements that contain postal
address information. Two elements are provided so that address address information. Two elements are provided so that address
information can be provided in both internationa lized and information can be provided in both internationa lized and
localized forms; a "type" attribute is used to i dentify the two localized forms; a "type" attribute is used to i dentify the two
forms. If an internationalized form (type="int" ) is provided, forms. If an internationalized form (type="int" ) is provided,
element content MUST be represented in a subset of UTF-8 that can element content <bcp14>MUST</bcp14> be represent ed in a subset of UTF-8 that can
be represented in the 7-bit US-ASCII character s et. If a be represented in the 7-bit US-ASCII character s et. If a
localized form (type="loc") is provided, element content MAY be localized form (type="loc") is provided, element content <bcp14>MAY</bcp14> be
represented in unrestricted UTF-8. The &lt;post alInfo&gt; represented in unrestricted UTF-8. The &lt;post alInfo&gt;
element contains the following child elements: element contains the following child elements:
<list style="symbols"> </t>
<ul spacing="normal">
<t> <li>
<t>
A &lt;addr&gt; element that contains add ress information associated A &lt;addr&gt; element that contains add ress information associated
with the registrar. with the registrar.
The &lt;addr&gt; element contains the fo llowing child elements: The &lt;addr&gt; element contains the fo llowing child elements:
<list style="symbols"> </t>
<t> <ul spacing="normal">
One, two, or three OPTIONAL &lt; <li>
street&gt; elements that One, two, or three <bcp14>OPTION
contain the registrar&apos;s str AL</bcp14> &lt;street&gt; elements that
eet address. contain the registrar's street a
</t> ddress.
<t> </li>
A &lt;city&gt; element that cont <li>
ains the registrar&apos;s A &lt;city&gt; element that cont
ains the registrar's
city. city.
</t> </li>
<t> <li>
An OPTIONAL &lt;sp&gt; element t An <bcp14>OPTIONAL</bcp14> &lt;s
hat contains the p&gt; element that contains the
registrar&apos;s state or provin registrar's state or province.
ce. </li>
</t> <li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;p
An OPTIONAL &lt;pc&gt; element t c&gt; element that contains the
hat contains the registrar's postal code.
registrar&apos;s postal code. </li>
</t> <li>
<t> A &lt;cc&gt; element that contai
A &lt;cc&gt; element that contai ns the registrar's
ns the registrar&apos;s
country code. country code.
</t> </li>
</list> </ul>
</t> </li>
</list> </ul>
</t> </li>
<t> <li>
An OPTIONAL &lt;voice&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;voice&gt; element
the registrar&apos;s voice that contains the registrar's voice
telephone number. telephone number.
</t> </li>
<t> <li>
An OPTIONAL &lt;fax&gt; element that contains th An <bcp14>OPTIONAL</bcp14> &lt;fax&gt; element t
e registrar&apos;s hat contains the registrar's
facsimile telephone number. facsimile telephone number.
</t> </li>
<t> <li>
An OPTIONAL &lt;email&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;email&gt; element
the registrar&apos;s email address. that contains the registrar's email address.
</t> </li>
<t> <li>
An OPTIONAL &lt;url&gt; element that contains th An <bcp14>OPTIONAL</bcp14> &lt;url&gt; element t
e registrar&apos;s URL. hat contains the registrar's URL.
</t> </li>
<t> <li>
An OPTIONAL &lt;whoisInfo&gt; elements that cont <t>
ains whois information. An <bcp14>OPTIONAL</bcp14> &lt;whoisInfo&gt; ele
ment that contains WHOIS information.
The &lt;whoisInfo&gt; element contains the follo wing child elements: The &lt;whoisInfo&gt; element contains the follo wing child elements:
<list style="symbols"> </t>
<t> <ul spacing="normal">
An OPTIONAL &lt;name&gt; element that co <li>
ntains the name of the registrar An <bcp14>OPTIONAL</bcp14> &lt;name&gt;
WHOIS server listening on TCP port 43 as element that contains the name of the registrar
specified in <xref target="RFC3912"/>. WHOIS server listening on TCP port 43 as
</t> specified in <xref target="RFC3912" format="default"/>.
<t> </li>
An OPTIONAL &lt;url&gt; element that con <li>
tains the name of the registrar An <bcp14>OPTIONAL</bcp14> &lt;url&gt; e
lement that contains the name of the registrar
WHOIS server listening on TCP port 80/44 3. WHOIS server listening on TCP port 80/44 3.
</t> </li>
</list> </ul>
</t> </li>
<t> <li>
An OPTIONAL &lt;crDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;crDate&gt; elemen
the date and time of t that contains the creation date and time of
registrar-object creation. the registrar object.
</t> </li>
<t> <li>
An OPTIONAL &lt;upDate&gt; element that contains An <bcp14>OPTIONAL</bcp14> &lt;upDate&gt; elemen
the date and time of the most t that contains the date and time of the most
recent registrar-object modification. recent modification of the registrar object.
This element MUST NOT be present if the registra This element <bcp14>MUST NOT</bcp14> be present
r-object has never been modified. if the registrar object has never been modified.
</t> </li>
</list> </ul>
</t> <t keepWithNext="true">
<t> The following is an example of a &lt;registrar&gt; o
<figure> bject:
<preamble> </t>
Example of a &lt;registrar&gt; object: <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
... ...
<rdeRegistrar:registrar> <rdeRegistrar:registrar>
<rdeRegistrar:id>RegistrarX</rdeRegistrar:id> <rdeRegistrar:id>RegistrarX</rdeRegistrar:id>
<rdeRegistrar:name>Registrar X</rdeRegistrar:name> <rdeRegistrar:name>Registrar X</rdeRegistrar:name>
<rdeRegistrar:gurid>8</rdeRegistrar:gurid> <rdeRegistrar:gurid>8</rdeRegistrar:gurid>
<rdeRegistrar:status>ok</rdeRegistrar:status> <rdeRegistrar:status>ok</rdeRegistrar:status>
<rdeRegistrar:postalInfo type="int"> <rdeRegistrar:postalInfo type="int">
<rdeRegistrar:addr> <rdeRegistrar:addr>
<rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street> <rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street>
<rdeRegistrar:street>Suite 100</rdeRegistrar:street> <rdeRegistrar:street>Suite 100</rdeRegistrar:street>
skipping to change at line 3158 skipping to change at line 2965
<rdeRegistrar:fax>+1.7035555556</rdeRegistrar:fax> <rdeRegistrar:fax>+1.7035555556</rdeRegistrar:fax>
<rdeRegistrar:email>jdoe@example.example</rdeRegistrar:email> <rdeRegistrar:email>jdoe@example.example</rdeRegistrar:email>
<rdeRegistrar:url>http://www.example.example</rdeRegistrar:url> <rdeRegistrar:url>http://www.example.example</rdeRegistrar:url>
<rdeRegistrar:whoisInfo> <rdeRegistrar:whoisInfo>
<rdeRegistrar:name>whois.example.example</rdeRegistrar:name> <rdeRegistrar:name>whois.example.example</rdeRegistrar:name>
<rdeRegistrar:url>http://whois.example.example</rdeRegistrar:url> <rdeRegistrar:url>http://whois.example.example</rdeRegistrar:url>
</rdeRegistrar:whoisInfo> </rdeRegistrar:whoisInfo>
<rdeRegistrar:crDate>2005-04-23T11:49:00.0Z</rdeRegistrar:crDate> <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z</rdeRegistrar:crDate>
<rdeRegistrar:upDate>2009-02-17T17:51:00.0Z</rdeRegistrar:upDate> <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z</rdeRegistrar:upDate>
</rdeRegistrar:registrar> </rdeRegistrar:registrar>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> <section anchor="del_registrar_object" numbered="true" toc="default">
</section> <name>&lt;rdeRegistrar:delete&gt; Object</name>
<t>
<section title="&lt;rdeRegistrar:delete&gt; object" anchor="del_
registrar_object">
<t>
The &lt;rdeRegistrar:delete&gt; element contains the id of a registrar that was deleted. The &lt;rdeRegistrar:delete&gt; element contains the id of a registrar that was deleted.
</t> </t>
<t keepWithNext="true">
<t> The following is an example of &lt;rdeRegistrar:dele
<figure> te&gt; object:
<preamble> </t>
Example of &lt;rdeRegistrar:delete&gt; object: <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeRegistrar:delete> <rdeRegistrar:delete>
<rdeRegistrar:id>agnt0001-TEST</rdeRegistrar:id> <rdeRegistrar:id>agnt0001-TEST</rdeRegistrar:id>
</rdeRegistrar:delete> </rdeRegistrar:delete>
... ...
</rde:deletes> </rde:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> </section>
</section> <section anchor="registrarCsvModel" numbered="true" toc="default">
<name>CSV Model</name>
</section> <t>For the CSV model of the registrar object, the &lt;csvRegistrar:con
tents&gt; child
<section title="CSV Model" anchor="registrarCsvModel">
<t>For the CSV Model of the registrar object, the &lt;csvRegistr
ar:contents&gt; child
element of the &lt;rde:contents&gt; element is used to hold t he new or updated registrar objects for the deposit. element of the &lt;rde:contents&gt; element is used to hold t he new or updated registrar objects for the deposit.
The &lt;csvRegistrar:deletes&gt; child element of the &lt;rde :deletes&gt; element is used to hold the deleted or The &lt;csvRegistrar:deletes&gt; child element of the &lt;rde :deletes&gt; element is used to hold the deleted or
purged registrar objects for the deposit. Both the &lt;csvRe gistrar:contents&gt; and &lt;csvRegistrar:deletes&gt; purged registrar objects for the deposit. Both the &lt;csvRe gistrar:contents&gt; and &lt;csvRegistrar:deletes&gt;
elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te. elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te.
</t> </t>
<t> <t>
Differential and Incremental Deposits are based on changes to the registrar objects. The updated registrar object Differential and Incremental Deposits are based on changes to the registrar objects. The updated registrar object
data under the &lt;csvContact:contents&gt; element is a casca de replace down all of the registrar CSV files starting with the data under the &lt;csvContact:contents&gt; element is a casca de replace down all of the registrar CSV files starting with the
parent <xref target="csvRegistrarDefinition">"registrar" CSV parent <xref target="csvRegistrarDefinition" format="default"
File Definition</xref>. The child CSV file definitions include a &lt;csvRegistr >'"registrar" CSV File Definition'</xref>. The child CSV file definitions inclu
ar:fId parent="true"&gt; field. de a &lt;csvRegistrar:fId parent="true"&gt; field.
All the child CSV file definition data for the registrar obje All the child CSV file definition data for the registrar obje
cts in the parent <xref target="csvRegistrarDefinition">"registrar" CSV File Def cts in the parent <xref target="csvRegistrarDefinition" format="default">'"regis
inition</xref> trar" CSV File Definition'</xref>
MUST first be deleted and then set using the data in the chil <bcp14>MUST</bcp14> first be deleted and then set using the d
d CSV files. The deleted registrar object data under the &lt;csvRegistrar:delet ata in the child CSV files. The deleted registrar object data under the &lt;csv
es&gt; Registrar:deletes&gt;
element is a cascade delete starting from the <xref target="c element is a cascade delete starting from the <xref target="c
svRegistrarDeletesDefinition">"registrar" Deletes CSV File Definition</xref>. svRegistrarDeletesDefinition" format="default">'"registrar" Deletes CSV File Def
</t> inition'</xref>.
</t>
<section title="&lt;csvRegistrar:contents&gt;" anchor="csvRegistr <section anchor="csvRegistrarContents" numbered="true" toc="default">
arContents"> <name>&lt;csvRegistrar:contents&gt;</name>
<t>The &lt;csvRegistrar:contents&gt; is used to hold the new or upda
<t>The &lt;csvRegistrar:contents&gt; is used to hold the new o ted registrar object information for the deposit.
r updated registrar object information for the deposit.
The &lt;csvRegistrar:contents&gt; is split into separate CSV f ile definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribut e. The &lt;csvRegistrar:contents&gt; is split into separate CSV f ile definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribut e.
The following sections include the supported contact CSV file The following sections include the supported registrar CSV fil
definitions. e definitions.
</t> </t>
<section anchor="csvRegistrarDefinition" numbered="true" toc="defaul
<section title="&quot;registrar&quot; CSV File Definition" anc t">
hor="csvRegistrarDefinition"> <name>"registrar" CSV File Definition</name>
<t>The "registrar" CSV File Definition defines the fields and CSV
<t>The "registrar" CSV File Definition defines the fields file references
and CSV file references
used for the registrar object records.</t> used for the registrar object records.</t>
<t>The following "csvRegistrar" field elements MUST be use d in the "registrar" <t>The following "csvRegistrar" field elements <bcp14>MUST</bcp14> be used in the "registrar"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;csvRegistrar:fId&gt; or &lt;csvRegistrar:fGurid&gt;</dt>
<dd>
<t hangText="&lt;csvRegistrar:fId&gt; or &lt;csvRegistrar: <t>A choice of the following:
fGurid&gt;">A choice of:
<list style="hanging">
<t hangText="&lt;csvRegistrar:fId&gt;">Contains the serv
er-unique registrar identifier with type="eppcom:clIDType" and isRequired="true"
.
</t>
<t hangText="&lt;csvRegistrar:fGurid&gt;">Contains the G
lobally Unique
Registrar Identifier (GURID) assigned by ICANN with type="positiveInteger" a
nd isRequired="true".
</t>
</list></t>
<t hangText="&lt;csvRegistrar:fName&gt;">Contains the na
me of the registrar with type="normalizedString" and isRequired="true".
</t>
</list></t>
<t>The following field elements MAY be used in the "regist </t>
rar" <dl newline="false" spacing="normal">
<dt>&lt;csvRegistrar:fId&gt;</dt>
<dd>Contains the server-unique registrar identifier with typ
e="eppcom:clIDType" and isRequired="true".
</dd>
<dt>&lt;csvRegistrar:fGurid&gt;</dt>
<dd>Contains the
GURID assigned by ICANN with type="positiveInteger" and isRequired="true".
</dd>
</dl>
</dd>
<dt>&lt;csvRegistrar:fName&gt;</dt>
<dd>Contains the name of the registrar with type="normalizedStri
ng" and isRequired="true".
</dd>
</dl>
<t>The following field elements <bcp14>MAY</bcp14> be used in the
"registrar"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvRegistrar:fStatus&gt;">Contains the <dt>&lt;csvRegistrar:fStatus&gt;</dt>
status of the registrar with type="csvRegistrar:statusValueType". <dd>Contains the status of the registrar with type="csvRegistrar
</t> :statusValueType".
<t hangText="&lt;csvRegistrar:fGurid&gt;">Contains the I </dd>
D assigned by ICANN with type="positiveInteger". This field is included in this <dt>&lt;csvRegistrar:fGurid&gt;</dt>
section in addition <dd>Contains the ID assigned by ICANN with type="positiveInteger
to the section above to support optionally providing the ". This field is included in this section in addition
&lt;csvRegistrar:fGurid&gt; field when the &lt;csvRegistrar:fId&gt; field is us to the section above to support optionally providing the
ed.</t> &lt;csvRegistrar:fGurid&gt; field when the &lt;csvRegistrar:fId&gt; field is us
<t hangText="&lt;csvRegistrar:fWhoisUrl&gt;">Contains th ed.</dd>
e Whois URL of the registrar with type="anyURI". <dt>&lt;csvRegistrar:fWhoisUrl&gt;</dt>
</t> <dd>Contains the Whois URL of the registrar with type="anyURI".
</dd>
</list></t> </dl>
<t>The following "rdeCsv" fields, defined in <xref target="csvComm
<t>The following "rdeCsv" fields, defined in section <xref onFieldElements" format="default">'CSV Common Field Elements'</xref>,
target="csvCommonFieldElements">CSV common field elements</xref>, <bcp14>MAY</bcp14> be used in the "registrar" &lt;rdeCsv
MAY be used in the "registrar" &lt;rdeCsv:csv&gt; &lt;rd :csv&gt; &lt;rdeCsv:fields&gt; element:
eCsv:fields&gt; element: </t>
</t> <dl newline="false" spacing="normal">
<t><list style="hanging"> <dt>&lt;rdeCsv:fCrDate&gt;</dt>
<t hangText="&lt;rdeCsv:fCrDate&gt;">Created date and ti <dd>Date and time of the registrar object creation.</dd>
me of the registrar object.</t> <dt>&lt;rdeCsv:fUpDate&gt;</dt>
<t hangText="&lt;rdeCsv:fUpDate&gt;">Date and time of th <dd>Date and time of the last update to the registrar object. Th
e last update to the registrar object. This field MUST NOT be set if the domain is field <bcp14>MUST NOT</bcp14> be set if the domain name object has never been
name object has never been modified.</t> modified.</dd>
<t hangText="&lt;rdeCsv:fUrl&gt;">URL for the registrar <dt>&lt;rdeCsv:fUrl&gt;</dt>
web home page.</t> <dd>URL for the registrar web home page.</dd>
</list></t> </dl>
<t>The following "csvContact" fields, defined in section <x <t>The following "csvContact" fields, defined in <xref target="con
ref target="contactObject">Contact Object</xref>, tactObject" format="default">'Contact Object'</xref>,
MAY be used in the "registrar" &lt;rdeCsv:csv&gt; &lt;rde <bcp14>MAY</bcp14> be used in the "registrar" &lt;rdeCsv:
Csv:fields&gt; element: csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvContact:fStreet&gt;">Registrar street <dt>&lt;csvContact:fStreet&gt;</dt>
address line with an "index" attribute that represents the order of the street <dd>Registrar street address line with an "index" attribute that
address line from "0" to "2". represents the order of the street address line from "0" to "2".
An OPTIONAL "isLoc" attribute that is used to indicate An <bcp14>OPTIONAL</bcp14> "isLoc" attribute that is us
the localized or internationalized form, as defined in <xref target="intandloc"/ ed to indicate the localized or internationalized form, as defined in <xref targ
>.</t> et="intandloc" format="default"/>.</dd>
<t hangText="&lt;csvContact:fCity&gt;">Registrar city wit <dt>&lt;csvContact:fCity&gt;</dt>
h an OPTIONAL "isLoc" attribute that is used to <dd>Registrar city with an <bcp14>OPTIONAL</bcp14> "isLoc" attri
indicate the localized or internationalized form, as de bute that is used to
fined in <xref target="intandloc"/>.</t> indicate the localized or internationalized form, as de
<t hangText="&lt;csvContact:fCc&gt;">Registrar country co fined in <xref target="intandloc" format="default"/>.</dd>
de with an OPTIONAL "isLoc" attribute that is used to <dt>&lt;csvContact:fCc&gt;</dt>
indicate the localized or internationalized form, as de <dd>Registrar country code with an <bcp14>OPTIONAL</bcp14> "isLo
fined in <xref target="intandloc"/>.</t> c" attribute that is used to
<t hangText="&lt;csvContact:fEmail&gt;">Registrar email a indicate the localized or internationalized form, as de
ddress. The attribute "isRequired" MUST equal "false".</t> fined in <xref target="intandloc" format="default"/>.</dd>
<t hangText="&lt;csvContact:fSp&gt;">Registrar state or p <dt>&lt;csvContact:fEmail&gt;</dt>
rovince with an OPTIONAL "isLoc" attribute that is used to <dd>Registrar email address. The attribute "isRequired" <bcp14>
indicate the localized or internationalized form, as de MUST</bcp14> equal "false".</dd>
fined in <xref target="intandloc"/>.</t> <dt>&lt;csvContact:fSp&gt;</dt>
<t hangText="&lt;csvContact:fPc&gt;">Registrar postal cod <dd>Registrar state or province with an <bcp14>OPTIONAL</bcp14>
e with an OPTIONAL "isLoc" attribute that is used to "isLoc" attribute that is used to
indicate the localized or internationalized form, as de indicate the localized or internationalized form, as de
fined in <xref target="intandloc"/>.</t> fined in <xref target="intandloc" format="default"/>.</dd>
<t hangText="&lt;csvContact:fVoice&gt;">Registrar voice t <dt>&lt;csvContact:fPc&gt;</dt>
elephone number.</t> <dd>Registrar postal code with an <bcp14>OPTIONAL</bcp14> "isLoc
<t hangText="&lt;csvContact:fVoiceExt&gt;">Registrar voic " attribute that is used to
e telephone number extension.</t> indicate the localized or internationalized form, as de
<t hangText="&lt;csvContact:fFax&gt;">Registrar facsimile fined in <xref target="intandloc" format="default"/>.</dd>
telephone number.</t> <dt>&lt;csvContact:fVoice&gt;</dt>
<t hangText="&lt;csvContact:fFaxExt&gt;">Registrar facsim <dd>Registrar voice telephone number.</dd>
ile telephone number extension.</t> <dt>&lt;csvContact:fVoiceExt&gt;</dt>
</list></t> <dd>Registrar voice telephone number extension.</dd>
<t> <dt>&lt;csvContact:fFax&gt;</dt>
<figure> <dd>Registrar facsimile telephone number.</dd>
<preamble> <dt>&lt;csvContact:fFaxExt&gt;</dt>
Example of a "registrar" &lt;csvRegistrar:contents&gt <dd>Registrar facsimile telephone number extension.</dd>
; &lt;rdeCsv:csv&gt; element. </dl>
</preamble> <t keepWithNext="true">
<artwork><![CDATA[ The following is an example of a "registrar" &lt;csvR
egistrar:contents&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvRegistrar:contents> <csvRegistrar:contents>
... ...
<rdeCsv:csv name="registrar"> <rdeCsv:csv name="registrar">
<rdeCsv:fields> <rdeCsv:fields>
<csvRegistrar:fId/> <csvRegistrar:fId/>
<csvRegistrar:fName isLoc="false"/> <csvRegistrar:fName isLoc="false"/>
<csvRegistrar:fGurid/> <csvRegistrar:fGurid/>
<csvRegistrar:fStatus/> <csvRegistrar:fStatus/>
<csvContact:fStreet isLoc="false" index="0"/> <csvContact:fStreet isLoc="false" index="0"/>
skipping to change at line 3325 skipping to change at line 3132
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="57F6856F"> cksum="57F6856F">
registrar-YYYYMMDD.csv registrar-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvRegistrar:contents> </csvRegistrar:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the registrar-YYYYMMD
<t> D.csv file.
<figure> The file contains one registrar record:
<preamble> </t>
Example of the registrar-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains one registrar record.
</preamble>
<artwork><![CDATA[
registrarX,"Example Inc.",8,ok,"123 Example Dr.", registrarX,"Example Inc.",8,ok,"123 Example Dr.",
"Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234,
+1.7035555556,,jdoe@example.example,http://www.example.example, +1.7035555556,,jdoe@example.example,http://www.example.example,
http://whois.example.example,2005-04-23T11:49:00.0Z, http://whois.example.example,2005-04-23T11:49:00.0Z,
2009-02-17T17:51:00.0Z]]> 2009-02-17T17:51:00.0Z
</artwork> ]]></artwork>
</figure> </section>
</t> </section>
<section anchor="csvRegistrarDeletes" numbered="true" toc="default">
</section> <name>&lt;csvRegistrar:deletes&gt;</name>
<t>
</section>
<section title="&lt;csvRegistrar:deletes&gt;" anchor="csvRegistra
rDeletes">
<t>
The &lt;csvRegistrar:deletes&gt; is used to hold the deleted r egistrar objects in a Differential or Incremental Deposit. The &lt;csvRegistrar:deletes&gt; is used to hold the deleted r egistrar objects in a Differential or Incremental Deposit.
All the registrar object data is deleted as part of a cascade delete. The &lt;csvRegistrar:deletes&gt; is split into All the registrar object data is deleted as part of a cascade delete. The &lt;csvRegistrar:deletes&gt; is split into
separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute. separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute.
The following section defines the supported registrar deletes CSV file definition. The following section defines the supported registrar deletes CSV file definition.
</t>
<section title="&quot;registrar&quot; Deletes CSV File Definit
ion" anchor="csvRegistrarDeletesDefinition">
<t>
The following "csvRegistrar" field elements MUST be used in
the deletes "registrar"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <section anchor="csvRegistrarDeletesDefinition" numbered="true" toc=
<t hangText="&lt;csvRegistrar:fId&gt; or &lt;csvRegistrar: "default">
fGurid&gt;">A choice of: <name>"registrar" Deletes CSV File Definition</name>
<t>
<list style="hanging"> The following "csvRegistrar" field elements <bcp14>MUST</bcp
14> be used in the deletes "registrar"
<t hangText="&lt;csvRegistrar:fId&gt;">Contains the serv &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
er-unique registrar identifier with type="eppcom:clIDType" and isRequired="true" </t>
. <dl newline="false" spacing="normal">
</t> <dt>&lt;csvRegistrar:fId&gt; or &lt;csvRegistrar:fGurid&gt;</dt>
<dd>
<t>A choice of the following:
<t hangText="&lt;csvRegistrar:fGurid&gt;">Contains the G </t>
lobally Unique <dl newline="false" spacing="normal">
Registrar Identifier (GURID) assigned by ICANN with type="positiveInteger". <dt>&lt;csvRegistrar:fId&gt;</dt>
The attribute "isRequired" MUST equal "true". <dd>Contains the server-unique registrar identifier with typ
</t> e="eppcom:clIDType" and isRequired="true".
</list></t> </dd>
</list></t> <dt>&lt;csvRegistrar:fGurid&gt;</dt>
<t> <dd>Contains the
<figure> GURID assigned by ICANN with type="positiveInteger".
<preamble> The attribute "isRequired" <bcp14>MUST</bcp14> equal "tr
Example of a "registrar" &lt;csvRegistrar:deletes&gt; ue".
&lt;rdeCsv:csv&gt; element. </dd>
</preamble> </dl>
<artwork><![CDATA[ </dd>
</dl>
<t keepWithNext="true">
The following is an example of a "registrar" &lt;csvRe
gistrar:deletes&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvRegistrar:deletes> <csvRegistrar:deletes>
... ...
<rdeCsv:csv name="registrar"> <rdeCsv:csv name="registrar">
<rdeCsv:fields> <rdeCsv:fields>
<csvRegistrar:fId/> <csvRegistrar:fId/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="5CB20A52"> cksum="5CB20A52">
registrar-delete-YYYYMMDD.csv registrar-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvRegistrar:deletes> </csvRegistrar:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the registrar-delete-YY
<t> YYMMDD.csv file.
<figure> The file contains one registrar record:
<preamble> </t>
Example of the registrar-delete-YYYYMMDD.csv file. <artwork name="" type="" align="left" alt=""><![CDATA[
The file contains one registrar record. registrarZ
</preamble> ]]></artwork>
<artwork><![CDATA[ </section>
registrarZ]]>
</artwork>
</figure>
</t>
</section> </section>
</section> </section>
</section>
</section> <section numbered="true" toc="default">
<name>IDN Table Reference Object</name>
</section> <t>
<section title="IDN Table Reference Object">
<t>
The Internationalized Domain Names (IDN) table reference object is a pseudo-object that is used to The Internationalized Domain Names (IDN) table reference object is a pseudo-object that is used to
provide a short reference to the IDN Table and Policy used in ID provide a short reference to the IDN table and policy used in ID
N registrations. The IDN reference N registrations. The IDN reference
object supports both the XML and the CSV Model, defined in the < object supports both the XML and the CSV model, defined in <xref
xref target="models">Models</xref> section. target="models" format="default">'Models'</xref>.
The elements used for both models are defined in the following s ections. The elements used for both models are defined in the following s ections.
</t> </t>
<section anchor="idnXmlModel" numbered="true" toc="default">
<section title="XML Model" anchor="idnXmlModel"> <name>XML Model</name>
<t>There is <t>There is
one element used in the data escrow of the IDN table referenc one element used in the data escrow of the IDN table referenc
e objects for the XML model that is the e objects for the XML model, and that is the
&lt;rdeIDN:idnTableRef&gt;, under the &lt;rde:contents&gt; el ement. &lt;rdeIDN:idnTableRef&gt;, under the &lt;rde:contents&gt; el ement.
</t> </t>
<section title="&lt;rdeIDN:idnTableRef&gt; object" anchor="idnTa <section anchor="idnTableRef_object" numbered="true" toc="default">
bleRef_object"> <name>&lt;rdeIDN:idnTableRef&gt; Object</name>
<t> <t>
The &lt;rdeIDN:idnTableRef&gt; contains the following el ements. An "id" attribute is used The &lt;rdeIDN:idnTableRef&gt; contains the following el ements. An "id" attribute is used
to specify an identifier for the IDN table. to specify an identifier for the IDN table.
</t> </t>
<t> <ul spacing="normal">
<list style="symbols"> <li>
<t> A &lt;url&gt; element that contains the URL of t
An &lt;url&gt; element that contains the URL of he IDN table that is being referenced.
the IDN table that is being referenced. </li>
</t> <li>
<t>
A &lt;urlPolicy&gt; element that contains the UR L of the IDN policy document. A &lt;urlPolicy&gt; element that contains the UR L of the IDN policy document.
If IDN variants are generated algorithmically, t he policy document MUST define the If IDN variants are generated algorithmically, t he policy document <bcp14>MUST</bcp14> define the
algorithm and the algorithm and the
state of the implicit generated IDN variants. Fo state of the implicitly generated IDN variants.
r a list of suggested states for implicit For a list of suggested states for implicit
IDN variants, please see <xref target="variantTL IDN variants, please see <xref target="variantTL
DsReport"/>. DsReport" format="default"/>.
</t> </li>
</list> </ul>
</t> <t keepWithNext="true">
The following is an example of &lt;idnTableRef&gt; o
<t> bject:
<figure> </t>
<preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
Example of &lt;idnTableRef&gt; object:
</preamble>
<artwork><![CDATA[
... ...
<rdeIDN:idnTableRef id="pt-BR"> <rdeIDN:idnTableRef id="pt-BR">
<rdeIDN:url> <rdeIDN:url>
http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html
</rdeIDN:url> </rdeIDN:url>
<rdeIDN:urlPolicy> <rdeIDN:urlPolicy>
http://registro.br/dominio/regras.html http://registro.br/dominio/regras.html
</rdeIDN:urlPolicy> </rdeIDN:urlPolicy>
</rdeIDN:idnTableRef> </rdeIDN:idnTableRef>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> </section>
</section> <section anchor="idnCsvModel" numbered="true" toc="default">
</section> <name>CSV Model</name>
<t>
<section title="CSV Model" anchor="idnCsvModel"> The IDN domain names, defined in <xref target="domainNameObje
<t> ct" format="default"/>, <bcp14>MAY</bcp14> have references
The IDN domain names, defined in <xref target="domainNameObje
ct"/>, MAY have references
to the IDN language identifier using the &lt;rdeCsv:fIdnTable Id&gt; field element. to the IDN language identifier using the &lt;rdeCsv:fIdnTable Id&gt; field element.
The IDN table reference object defines the mapping of a langu age identifier to a language table URL. The IDN table reference object defines the mapping of a langu age identifier to a language table URL.
The language table URL defines the character code points that can be used for The language table URL defines the character code points that can be used for
the language identifier. The elements used for the IDN table reference object is defined in this section. the language identifier. The elements used for the IDN table reference object are defined in this section.
The &lt;csvIDN:contents&gt; child The &lt;csvIDN:contents&gt; child
element of the &lt;rde:contents&gt; element is used to hold t he new or updated IDN table reference objects for the deposit. element of the &lt;rde:contents&gt; element is used to hold t he new or updated IDN table reference objects for the deposit.
The &lt;csvIDN:deletes&gt; child element of the &lt;rde:delet es&gt; element is used to hold the deleted or The &lt;csvIDN:deletes&gt; child element of the &lt;rde:delet es&gt; element is used to hold the deleted or
purged IDN table reference objects for the deposit. Both the &lt;csvIDN:contents&gt; and &lt;csvIDN:deletes&gt; purged IDN table reference objects for the deposit. Both the &lt;csvIDN:contents&gt; and &lt;csvIDN:deletes&gt;
elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te. elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te.
</t> </t>
<section title="&lt;csvIDN:contents&gt;" anchor="csvIDNContents"> <section anchor="csvIDNContents" numbered="true" toc="default">
<name>&lt;csvIDN:contents&gt;</name>
<t>The &lt;csvIDN:contents&gt; is used to hold the new or updat <t>The &lt;csvIDN:contents&gt; is used to hold the new or updated ID
ed IDN table reference object information for the deposit. N table reference object information for the deposit.
The &lt;csvIDN:contents&gt; is split into separate CSV file d efinitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute. The &lt;csvIDN:contents&gt; is split into separate CSV file d efinitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute.
The following sections include the supported IDN table refere nce CSV file definitions. The following sections include the supported IDN table refere nce CSV file definitions.
</t> </t>
<section title="&quot;idnLanguage&quot; CSV File Definition" an <section anchor="csvIDNDefinition" numbered="true" toc="default">
chor="csvIDNDefinition"> <name>"idnLanguage" CSV File Definition</name>
<t>The "idnLanguage" CSV File Definition defines the fields and CS
<t>The "idnLanguage" CSV File Definition defines the fields a V file references
nd CSV file references
used for the IDN table reference object records. used for the IDN table reference object records.
</t> </t>
<t>The following "rdeCsv" fields, defined in <xref target="cs <t>The following "rdeCsv" fields, defined in <xref target="csvComm
vCommonFieldElements"/>, onFieldElements" format="default"/>,
MUST be used in the "idnLanguage" &lt;rdeCsv:csv&gt; &lt;rd <bcp14>MUST</bcp14> be used in the "idnLanguage" &lt;rdeCsv
eCsv:fields&gt; element: :csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fIdnTableId&gt;">The language ident <dt>&lt;rdeCsv:fIdnTableId&gt;</dt>
ifier that matches the values for the &lt;rdeCsv:fIdnTableId&gt; field element i <dd>The language identifier that matches the values for the &lt;
n the <xref target="csvDomainDefinition">"domain" CSV File Definition</xref> fil rdeCsv:fIdnTableId&gt; field element in the <xref target="csvDomainDefinition" f
es. The attribute "isRequired" MUST equal "true".</t> ormat="default">'"domain" CSV File Definition'</xref> files. The attribute "isRe
<t hangText="&lt;rdeCsv:fUrl&gt;">URL that defines the char quired" <bcp14>MUST</bcp14> equal "true".</dd>
acter code points that can be <dt>&lt;rdeCsv:fUrl&gt;</dt>
used for &lt;csvDomain:fName&gt; field in the "domain" CSV <dd>URL that defines the character code points that can be
File Definition <xref target="csvDomainDefinition"/> files. The attribute "is used for &lt;csvDomain:fName&gt; field in the <xref target="csvDomainDefiniti
Required" MUST equal "true".</t> on" format="default">'"domain" CSV
</list></t> File Definition'</xref> files. The attribute "isRequired" <bcp14>MUST</bcp14>
<t> equal "true".</dd>
<figure> </dl>
<preamble> <t keepWithNext="true">
Example of a "idnLanguage" &lt;csvIDN:contents&gt; &lt The following is an example of a "idnLanguage" &lt;csv
;rdeCsv:csv&gt; element. IDN:contents&gt; &lt;rdeCsv:csv&gt; element:
</preamble> </t>
<artwork><![CDATA[ <sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvIDN:contents> <csvIDN:contents>
... ...
<rdeCsv:csv name="idnLanguage" sep=","> <rdeCsv:csv name="idnLanguage" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fIdnTableId isRequired="true"/>
<rdeCsv:fUrl isRequired="true"/> <rdeCsv:fUrl isRequired="true"/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="D6B0424F"> cksum="D6B0424F">
idnLanguage-YYYYMMDD.csv idnLanguage-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvIDN:contents> </csvIDN:contents>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding idnLa
<t> nguage-YYYYMMDD.csv file.
<figure> The file contains two IDN language records:
<preamble> </t>
Example of the corresponding idnLanguage-YYYYMMDD.csv <artwork name="" type="" align="left" alt=""><![CDATA[
file.
The file contains two IDN language records.
</preamble>
<artwork><![CDATA[
LANG-1, LANG-1,
http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt
LANG-2, LANG-2,
http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt]]> http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt
</artwork></figure> ]]></artwork>
</t> </section>
</section>
</section> <section anchor="csvIDNDeletes" numbered="true" toc="default">
<name>&lt;csvIDN:deletes&gt;</name>
</section> <t>
<section title="&lt;csvIDN:deletes&gt;" anchor="csvIDNDeletes">
<t>
The &lt;csvIDN:deletes&gt; is used to hold the deleted IDN tab le reference objects in a Differential or Incremental Deposit. The &lt;csvIDN:deletes&gt; is used to hold the deleted IDN tab le reference objects in a Differential or Incremental Deposit.
The &lt;csvIDN:deletes&gt; is split into The &lt;csvIDN:deletes&gt; is split into
separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute. separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute.
The following section defines the supported IDN table referenc e deletes CSV file definition. The following section defines the supported IDN table referenc e deletes CSV file definition.
</t>
<section title="&quot;idnLanguage&quot; Deletes CSV File Defin
ition" anchor="csvIDNDeletesDefinition">
<t>
The following "idnLanguage" field elements MUST be used in t
he deletes "idnLanguage"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <section anchor="csvIDNDeletesDefinition" numbered="true" toc="defau
<t hangText="&lt;rdeCsv:fIdnTableId&gt;">The language identifier t lt">
hat matches the values for the &lt;rdeCsv:fIdnTableId&gt; field element in the < <name>"idnLanguage" Deletes CSV File Definition</name>
xref target="csvDomainDefinition">"domain" CSV File Definition</xref> files. The <t>
attribute "isRequired" MUST equal "true".</t> The following "idnLanguage" field elements <bcp14>MUST</bcp1
</list></t> 4> be used in the deletes "idnLanguage"
<t> &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
<figure> </t>
<preamble> <dl newline="false" spacing="normal">
Example of a "idnLanguage" &lt;csvIDN:deletes&gt; &lt; <dt>&lt;rdeCsv:fIdnTableId&gt;</dt>
rdeCsv:csv&gt; element. <dd>The language identifier that matches the values for the &lt;
</preamble> rdeCsv:fIdnTableId&gt; field element in the <xref target="csvDomainDefinition" f
<artwork><![CDATA[ ormat="default">'"domain" CSV File Definition'</xref> files. The attribute "isRe
quired" <bcp14>MUST</bcp14> equal "true".</dd>
</dl>
<t keepWithNext="true">
The following is an example of a "idnLanguage" &lt;csv
IDN:deletes&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvIDN:deletes> <csvIDN:deletes>
... ...
<rdeCsv:csv name="idnLanguage"> <rdeCsv:csv name="idnLanguage">
<rdeCsv:fields> <rdeCsv:fields>
<rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fIdnTableId isRequired="true"/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="4A28A569"> cksum="4A28A569">
idnLanguage-delete-YYYYMMDD.csv idnLanguage-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvIDN:deletes> </csvIDN:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the idnLanguage-delete-
<t> YYYYMMDD.csv file.
<figure> The file contains one IDN language record:
<preamble>
Example of the idnLanguage-delete-YYYYMMDD.csv file.
The file contains one IDN language record.
</preamble>
<artwork><![CDATA[
LANG-2]]>
</artwork>
</figure>
</t>
</section>
</section>
</section>
</section>
<section title="NNDN Object">
<t>
An NNDN (NNDN's not domain name) can be used to store registry
reserved names or (blocked, withheld or mirrored) IDN variants.
</t>
<t>
Domain Name Registries may maintain domain names without their
being persisted as domain objects in the registry system, for example, a list o
f reserved names not available for registration. The NNDN is a lightweight domai
n-like object that is used to escrow domain names not maintained as domain name
objects.
</t> </t>
<t> <artwork name="" type="" align="left" alt=""><![CDATA[
LANG-2
]]></artwork>
</section>
</section>
</section>
</section>
<section numbered="true" toc="default">
<name>NNDN Object</name>
<t>
An NNDN (NNDN's not domain name) can be used to store registry
reserved names or (blocked, withheld, or mirrored) IDN variants.
</t>
<t>
Domain name registries may maintain domain names without their
being persisted as domain objects in the registry system, for example, a list o
f reserved names not available for registration. The NNDN is a lightweight domai
n-like object that is used to escrow domain names not maintained as domain name
objects.
</t>
<t>
A domain name can only exist as a domain name object or an NNDN o bject, but not both. A domain name can only exist as a domain name object or an NNDN o bject, but not both.
</t> </t>
<t> <t>
The NNDN object supports The NNDN object supports
both the XML and the CSV Model, defined in the <xref target= "models">Models</xref> section. both the XML and the CSV model, defined in <xref target="mod els" format="default">'Models'</xref>.
The elements used for both models are defined in the followi ng sections. The elements used for both models are defined in the followi ng sections.
</t> </t>
<section anchor="nndnXmlModel" numbered="true" toc="default">
<section title="XML Model" anchor="nndnXmlModel"> <name>XML Model</name>
<t>There are <t>There are
two elements used in the data escrow of the NNDN objects for the XML model including the two elements used in the data escrow of the NNDN objects for the XML model including the
&lt;rdeNNDN:NNDN&gt;, under the &lt;rde:contents&gt; element, and the &lt;rdeNNDN:delete&gt; element, &lt;rdeNNDN:NNDN&gt; element, under the &lt;rde:contents&gt; element, and the &lt;rdeNNDN:delete&gt; element,
under the &lt;rde:deletes&gt; element. under the &lt;rde:deletes&gt; element.
</t> </t>
<t> <t>
A &lt;rdeNNDN:NNDN&gt; element substitutes for the &lt;rdeNN An &lt;rdeNNDN:NNDN&gt; element substitutes for the &lt;rdeN
DN:abstractNNDN&gt; NDN:abstractNNDN&gt;
abstract element to define a concrete definition of an NNDN. abstract element to create a concrete definition of an NNDN.
The The
&lt;rdeNNDN:abstractDomain&gt; element can be replaced by ot her NNDN definitions &lt;rdeNNDN:abstractDomain&gt; element can be replaced by ot her NNDN definitions
using the XML schema substitution groups feature. using the XML schema substitution groups feature.
</t> </t>
<section anchor="ndn_object" numbered="true" toc="default">
<section title="&lt;rdeNNDN:NNDN&gt; object" anchor="ndn_object" <name>&lt;rdeNNDN:NNDN&gt; Object</name>
> <t>
<t>
The &lt;rdeNNDN:NNDN&gt; element contains the following child elements: The &lt;rdeNNDN:NNDN&gt; element contains the following child elements:
</t> </t>
<t> <ul spacing="normal">
<list style="symbols"> <li>
<t> An &lt;aName&gt; element that contains the fully qua
An &lt;aName&gt; element that contains the fully-qua lified name of the NNDN.
lified qualified name of the NNDN. For IDNs, the A-label is used (see <xref target="RFC
For IDNs the A-Label is used (see <xref target="RFC5 5891" section="4.4" sectionFormat="comma" format="default"/>).
891"/>, Section 4.4). </li>
</t> <li>
<t> An <bcp14>OPTIONAL</bcp14> &lt;uName&gt; element t
An OPTIONAL &lt;uName&gt; element that contains th hat contains the fully qualified name of the NNDN in the Unicode character set.
e fully-qualified name of the NNDN in Unicode character set. It It
MUST be provided if available. <bcp14>MUST</bcp14> be provided if available.
</t> </li>
<t> <li>
An OPTIONAL &lt;idnTableId&gt; element that refe An <bcp14>OPTIONAL</bcp14> &lt;idnTableId&gt; el
rences the IDN Table used for the NNDN. ement that references the IDN table used for the NNDN.
This corresponds to the &quot;id&quot; attribute This corresponds to the "id" attribute of the &l
of the &lt;idnTableRef&gt; element. This t;idnTableRef&gt; element. This
element MUST be present if the NNDN is an IDN. element <bcp14>MUST</bcp14> be present if the NN
</t> DN is an IDN.
<t> </li>
An OPTIONAL &lt;originalName&gt; element is used <li>
to indicate that the NNDN is used for an IDN variant. An <bcp14>OPTIONAL</bcp14> &lt;originalName&gt;
element is used to indicate that the NNDN is used for an IDN variant.
This element contains the domain name used to ge nerate the IDN variant. This element contains the domain name used to ge nerate the IDN variant.
</t> </li>
<t> <li>
A &lt;nameState&gt; element that indicates the s <t>
tate of the NNDN: blocked, withheld or mirrored. A &lt;nameState&gt; element that indicates the s
<list style="symbols"> tate of the NNDN: blocked, withheld, or mirrored.
<t> </t>
<ul spacing="normal">
<li>
If an NNDN is considered undesirable for registration (i.e., unavailable for allocation to If an NNDN is considered undesirable for registration (i.e., unavailable for allocation to
anyone), then the NNDN will be tagged as "blocked". anyone), then the NNDN will be tagged as "blocked".
</t> </li>
<t> <li>
If an NNDN is considered a potential registr ation of a domain name object for a registrant, If an NNDN is considered a potential registr ation of a domain name object for a registrant,
then the NNDN will be tagged as "withheld". This status is only used when the NNDN is used for an then the NNDN will be tagged as "withheld". This status is only used when the NNDN is used for an
IDN variant. IDN variant.
</t> </li>
<t> <li>
If an NNDN is considered a mirrored IDN vari If an NNDN is considered a mirrored IDN vari
ant of a domain name object, then the NNDN will be tagged as "mirrored". A mirro ant of a domain name object, then the NNDN will be tagged as "mirrored". A "mirr
ringNS attribute is used to specify if the mirrored IDN variant uses the NS mirr oringNS" attribute is used to specify if the mirrored IDN variant uses the NS mi
or mechanism, meaning that the activated variant domain name (i.e., NNDN) is del rror mechanism, meaning that the activated variant domain name (i.e., NNDN) is d
egated in the DNS using the same NS records as in the &lt;originalName&gt;. The elegated in the DNS using the same NS records as in the &lt;originalName&gt;. Th
default value of mirroringNS is true. If another mechanism such as DNAME is used e default value of "mirroringNS" is true. If another mechanism such as DNAME <xr
, the value of mirroringNS attribute MUST be false. ef target="RFC6672" format="default"/> is used, the value of the "mirroringNS" a
</t> ttribute <bcp14>MUST</bcp14> be false.
</list> </li>
</t> </ul>
<t> </li>
An OPTIONAL &lt;crDate&gt; element that contains <li>
the date and time of the NNDN object creation. An <bcp14>OPTIONAL</bcp14> &lt;crDate&gt; elemen
</t> t that contains the date and time of the NNDN object creation.
</list> </li>
</t> </ul>
<t> <t keepWithNext="true">
<figure> The following is an example of an &lt;rdeNNDN:NNDN&g
<preamble> t; object:
Example of an &lt;rdeNNDN:NNDN&gt; object: </t>
</preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
<artwork><![CDATA[
... ...
<rdeNNDN:NNDN> <rdeNNDN:NNDN>
<rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName> <rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName>
<rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId> <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId>
<rdeNNDN:originalName>example.example</rdeNNDN:originalName> <rdeNNDN:originalName>example.example</rdeNNDN:originalName>
<rdeNNDN:nameState>withheld</rdeNNDN:nameState> <rdeNNDN:nameState>withheld</rdeNNDN:nameState>
<rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate> <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate>
</rdeNNDN:NNDN> </rdeNNDN:NNDN>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> <section anchor="delNDNObject" numbered="true" toc="default">
</section> <name>&lt;rdeNNDN:delete&gt; Object</name>
<t>
<section title="&lt;rdeNNDN:delete&gt; object" anchor="delNDNObj
ect">
<t>
The &lt;rdeNNDN:delete&gt; element contains the NNDN tha t was deleted, i.e., the &lt;aName&gt;. The &lt;rdeNNDN:delete&gt; element contains the NNDN tha t was deleted, i.e., the &lt;aName&gt;.
</t> </t>
<t> <t keepWithNext="true">
<figure> The following is an example of an &lt;rdeNNDN::delet
<preamble> e&gt; object:
Example of an &lt;rdeNNDN::delete&gt; object: </t>
</preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
<artwork><![CDATA[
... ...
<rde:deletes> <rde:deletes>
... ...
<rdeNNDN:delete> <rdeNNDN:delete>
<rdeNNDN:aName>xn--pingino-q2a.example</rdeNNDN:aName> <rdeNNDN:aName>xn--pingino-q2a.example</rdeNNDN:aName>
</rdeNNDN:delete> </rdeNNDN:delete>
... ...
</rde:deletes> </rde:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> </section>
</section> <section anchor="nndnCsvModel" numbered="true" toc="default">
</section> <name>CSV Model</name>
<t>For the CSV model of the NNDN object, the &lt;csvNNDN:contents&gt;
<section title="CSV Model" anchor="nndnCsvModel"> child
<t>For the CSV Model of the NNDN object, the &lt;csvNNDN:content
s&gt; child
element of the &lt;rde:contents&gt; element is used to hold t he new or updated NNDN objects for the deposit. element of the &lt;rde:contents&gt; element is used to hold t he new or updated NNDN objects for the deposit.
The &lt;csvNNDN:deletes&gt; child element of the &lt;rde:dele tes&gt; element is used to hold the deleted or The &lt;csvNNDN:deletes&gt; child element of the &lt;rde:dele tes&gt; element is used to hold the deleted or
purged NNDN objects for the deposit. Both the &lt;csvNNDN:co ntents&gt; and &lt;csvNNDN:deletes&gt; purged NNDN objects for the deposit. Both the &lt;csvNNDN:co ntents&gt; and &lt;csvNNDN:deletes&gt;
elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te. elements contain one or more &lt;rdeCsv:csv&gt; elements with a set of named CSV file definitions using the &lt;rdeCsv:csv&gt; "name" attribu te.
</t> </t>
<section title="&lt;csvNNDN:contents&gt;" anchor="csvNNDNContents <section anchor="csvNNDNContents" numbered="true" toc="default">
"> <name>&lt;csvNNDN:contents&gt;</name>
<t>The &lt;csvNNDN:contents&gt; is used to hold the new or updated N
<t>The &lt;csvNNDN:contents&gt; is used to hold the new or upda NDN object information for the deposit.
ted NNDN object information for the deposit.
The &lt;csvNNDN:contents&gt; is split into separate CSV file definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute. The &lt;csvNNDN:contents&gt; is split into separate CSV file definitions using named &lt;rdeCsv:csv&gt; elements with the "name" attribute.
The following sections include the supported NNDN CSV file de finitions. The following sections include the supported NNDN CSV file de finitions.
</t> </t>
<section title="&quot;NNDN&quot; CSV File Definition" anchor="c <section anchor="csvNNDNDefinition" numbered="true" toc="default">
svNNDNDefinition"> <name>"NNDN" CSV File Definition</name>
<t>The "NNDN" CSV File Definition defines the fields and CSV file
<t>The "NNDN" CSV File Definition defines the fields and CSV references
file references
used for the NNDN object records.</t> used for the NNDN object records.</t>
<t>The following "csvNNDN" field elements MUST be used in the "NNDN" <t>The following "csvNNDN" field elements <bcp14>MUST</bcp14> be u sed in the "NNDN"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvNNDN:fAName&gt;">Fully-qualified name o <dt>&lt;csvNNDN:fAName&gt;</dt>
f the NNDN with type="eppcom:labelType" and isRequired="true". For IDNs the A-La <dd>Fully qualified name of the NNDN with type="eppcom:labelType
bel is used (see <xref target="RFC5891"/>, Section 4.4). " and isRequired="true". For IDNs, the A-label is used (see <xref target="RFC589
</t> 1" section="4.4" sectionFormat="comma" format="default"/>).
<t hangText="&lt;csvNNDN:fNameState&gt;">State of the NNDN: </dd>
blocked or withheld with type="rdeNNDN:nameState" and isRequired="true". See < <dt>&lt;csvNNDN:fNameState&gt;</dt>
xref target="ndn_object"/> for a description <dd>State of the NNDN: blocked or withheld with type="rdeNNDN:na
of the possible values for the &lt;rdeNNDN:nameState&gt; meState" and isRequired="true". See <xref target="ndn_object" format="default"/
element.</t> > for a description
</list></t> of the possible values for the &lt;rdeNNDN:nameState&gt;
<t>The following field elements MAY be used in the "NNDN" element.</dd>
</dl>
<t>The following field elements <bcp14>MAY</bcp14> be used in the
"NNDN"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element: &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <dl newline="false" spacing="normal">
<t hangText="&lt;csvNNDN:fOriginalName&gt;">Domain name used <dt>&lt;csvNNDN:fOriginalName&gt;</dt>
to generate the IDN variant with type="eppcom:labelType".</t> <dd>Domain name used to generate the IDN variant with type="eppc
<t hangText="&lt;csvNNDN:fMirroringNS&gt;">Defines whether t om:labelType".</dd>
he "mirroring" &lt;csvNNDN:fNameState&gt; uses the NS mirror mechanism, as descr <dt>&lt;csvNNDN:fMirroringNS&gt;</dt>
ibed for the &lt;rdeNNDN:nameState&gt; "mirroringNS" attribute in <xref target=" <dd>Defines whether the "mirroring" &lt;csvNNDN:fNameState&gt; u
ndn_object"/>, with type="boolean". ses the NS mirror mechanism, as described for the &lt;rdeNNDN:nameState&gt; "mir
If the field element is not defined the default value is " roringNS" attribute in <xref target="ndn_object" format="default"/>, with type="
true".</t> boolean".
</list></t> If the field element is not defined the default value is "
<t>The following "rdeCsv" fields, defined in section <xref tar true".</dd>
get="csvCommonFieldElements">CSV common field elements</xref>, </dl>
MAY be used in the "NNDN" &lt;rdeCsv:csv&gt; &lt;rdeCsv:fiel <t>The following "rdeCsv" fields, defined in <xref target="csvComm
ds&gt; element: onFieldElements" format="default">'CSV Common Field Elements'</xref>,
</t> <bcp14>MAY</bcp14> be used in the "NNDN" &lt;rdeCsv:csv&gt;
<t><list style="hanging"> &lt;rdeCsv:fields&gt; element:
<t hangText="&lt;rdeCsv:fCrDate&gt;">Created date and time o </t>
f the NNDN object.</t> <dl newline="false" spacing="normal">
<t hangText="&lt;rdeCsv:fUName&gt;">Name of the NNDN in Unic <dt>&lt;rdeCsv:fCrDate&gt;</dt>
ode character set for the &lt;csvNNDN:fAName&gt; field element.</t> <dd>Date and time of the NNDN object creation.</dd>
<t hangText="&lt;rdeCsv:fIdnTableId&gt;">IDN Table Identifie <dt>&lt;rdeCsv:fUName&gt;</dt>
r for the NNDN that matches an IDN Table Reference Object record, as defined in <dd>Name of the NNDN in the Unicode character set for the &lt;cs
<xref target="idnCsvModel"/>.</t> vNNDN:fAName&gt; field element.</dd>
</list></t> <dt>&lt;rdeCsv:fIdnTableId&gt;</dt>
<t> <dd>IDN table identifier for the NNDN that matches an IDN table
<figure> reference object record, as defined in <xref target="idnCsvModel" format="defaul
<preamble> t"/>.</dd>
Example of an "NNDN" &lt;csvNNDN:contents&gt; &lt;rdeCsv </dl>
:csv&gt; element: <t keepWithNext="true">
</preamble> The following is an example of an "NNDN" &lt;csvNNDN:con
<artwork><![CDATA[ tents&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvNNDN:contents> <csvNNDN:contents>
... ...
<rdeCsv:csv name="NNDN" sep=","> <rdeCsv:csv name="NNDN" sep=",">
<rdeCsv:fields> <rdeCsv:fields>
<csvNNDN:fAName/> <csvNNDN:fAName/>
<rdeCsv:fIdnTableId/> <rdeCsv:fIdnTableId/>
<csvNNDN:fOriginalName/> <csvNNDN:fOriginalName/>
<csvNNDN:fNameState/> <csvNNDN:fNameState/>
<csvNNDN:fMirroringNS/> <csvNNDN:fMirroringNS/>
skipping to change at line 3802 skipping to change at line 3570
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="085A7CE4"> cksum="085A7CE4">
NNDN-YYYYMMDD.csv NNDN-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvNNDN:contents> </csvNNDN:contents>
... ...
]]> ]]></sourcecode>
</artwork> <t keepWithNext="true">
</figure> The following is an example of the corresponding NNDN-
</t> YYYYMMDD.csv file.
<t>
<figure>
<preamble>
Example of the corresponding NNDN-YYYYMMDD.csv file.
The file contains two NNDN records for an IDN with The file contains two NNDN records for an IDN with
one blocked variant and one mirrored variant. one blocked variant and one mirrored variant:
</preamble> </t>
<artwork><![CDATA[ <artwork name="" type="" align="left" alt=""><![CDATA[
xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example,
blocked,,2005-04-23T11:49:00.0Z blocked,,2005-04-23T11:49:00.0Z
xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example, xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example,
mirrored,1,2005-04-23T11:49:00.0Z]]> mirrored,1,2005-04-23T11:49:00.0Z
</artwork> ]]></artwork>
</figure> </section>
</t> </section>
</section> <section anchor="csvNNDNDeletes" numbered="true" toc="default">
</section> <name>&lt;csvNNDN:deletes&gt;</name>
<t>
<section title="&lt;csvNNDN:deletes&gt;" anchor="csvNNDNDeletes">
<t>
The &lt;csvNNDN:deletes&gt; is used to hold the deleted NNDN o bjects in a Differential or Incremental Deposit. The &lt;csvNNDN:deletes&gt; is used to hold the deleted NNDN o bjects in a Differential or Incremental Deposit.
The &lt;csvNNDN:deletes&gt; is split into The &lt;csvNNDN:deletes&gt; is split into
separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute. separate CSV file definitions using named &lt;rdeCsv:csv&gt; e lements with the "name" attribute.
The following section defines the supported NNDN deletes CSV f ile definition. The following section defines the supported NNDN deletes CSV f ile definition.
</t>
<section title="&quot;NNDN&quot; Deletes CSV File Definition"
anchor="csvNNDNDeletesDefinition">
<t>
The following "NNDN" field elements MUST be used in the dele
tes "NNDN"
&lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
</t> </t>
<t><list style="hanging"> <section anchor="csvNNDNDeletesDefinition" numbered="true" toc="defa
<t hangText="&lt;csvNNDN:fAName&gt;">Fully-qualified nam ult">
e of the NNDN with type="eppcom:labelType" and isRequired="true". <name>"NNDN" Deletes CSV File Definition</name>
</t> <t>
</list></t> The following "NNDN" field elements <bcp14>MUST</bcp14> be u
<t> sed in the deletes "NNDN"
<figure> &lt;rdeCsv:csv&gt; &lt;rdeCsv:fields&gt; element:
<preamble> </t>
Example of an "NNDN" &lt;csvNNDN:deletes&gt; &lt;rdeCs <dl newline="false" spacing="normal">
v:csv&gt; element. <dt>&lt;csvNNDN:fAName&gt;</dt>
</preamble> <dd>Fully qualified name of the NNDN with type="eppcom:labelType
<artwork><![CDATA[ " and isRequired="true".
</dd>
</dl>
<t keepWithNext="true">
The following is an example of an "NNDN" &lt;csvNNDN:d
eletes&gt; &lt;rdeCsv:csv&gt; element:
</t>
<sourcecode name="" type="xml" markers="false"><![CDATA[
... ...
<csvNNDN:deletes> <csvNNDN:deletes>
... ...
<rdeCsv:csv name="NNDN"> <rdeCsv:csv name="NNDN">
<rdeCsv:fields> <rdeCsv:fields>
<csvNNDN:fAName/> <csvNNDN:fAName/>
</rdeCsv:fields> </rdeCsv:fields>
<rdeCsv:files> <rdeCsv:files>
<rdeCsv:file <rdeCsv:file
cksum="A41F1D9B"> cksum="A41F1D9B">
NNDN-delete-YYYYMMDD.csv NNDN-delete-YYYYMMDD.csv
</rdeCsv:file> </rdeCsv:file>
</rdeCsv:files> </rdeCsv:files>
</rdeCsv:csv> </rdeCsv:csv>
... ...
</csvNNDN:deletes> </csvNNDN:deletes>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of the corresponding NNDN-
<t> delete-YYYYMMDD.csv file.
<figure> The file contains one NNDN records:
<preamble> </t>
Example of the corresponding NNDN-delete-YYYYMMDD.csv <artwork name="" type="" align="left" alt=""><![CDATA[
file. xn--bc456-3ve.example
The file contains one NNDN records. ]]></artwork>
</preamble>
<artwork><![CDATA[
xn--bc456-3ve.example]]>
</artwork>
</figure>
</t>
</section>
</section>
</section>
</section> </section>
</section>
</section>
</section>
<section anchor="eppParams" numbered="true" toc="default">
<name>EPP Parameters Object</name>
<t>
The EPP parameters object is a pseudo-object that defines the
set of object and object extension services
supported by the registry, as defined in <xref target="RFC57
30" format="default"/>. The
EPP parameters object is only defined as XML but could be used
in either the XML model or CSV model.
<section title="EPP Parameters Object" anchor="eppParams"> The EPP parameters object is defined using the
<t>
The EPP Parameters Object is a pseudo-object that defines the
set of object and object extension services
supported by the registry, as defined in <xref target="RFC57
30"/>. The
EPP Parameters Object is only defined as XML but could be used
in the XML model or CSV model.
The EPP Parameters Object is defined using the
&lt;rdeEppParams:eppParams&gt; element. &lt;rdeEppParams:eppParams&gt; element.
The EPP Parameters Object SHOULD be included if the registry The EPP parameters object <bcp14>SHOULD</bcp14> be included
supports EPP. if the registry supports EPP.
A maximum of one EPP Parameters Object MUST exist at a certa A maximum of one EPP parameters object <bcp14>MUST</bcp14> e
in point in time (watermark). xist at a certain point in time (Time Watermark).
</t> </t>
<t> <t>
The syntax and content of the &lt;rdeEppParams:eppParams&gt; The syntax and content of the &lt;rdeEppParams:eppParams&gt;
children elements is as explained in section children elements is as explained in
2.4 of <xref target="RFC5730"/>. The children of the &lt;epp <xref target="RFC5730" section="2.4" sectionFormat="of" form
Params&gt; are as follows: at="default"/>. The children of the &lt;eppParams&gt; are as follows:
</t> </t>
<t> <ul spacing="normal">
<list style="symbols"> <li>
<t>
One or more &lt;version&gt; elements that indicate t he EPP versions supported by the One or more &lt;version&gt; elements that indicate t he EPP versions supported by the
registry. registry.
</t> </li>
<t> <li>
One or more &lt;lang&gt; elements that indicate the identifiers of the text response One or more &lt;lang&gt; elements that indicate the identifiers of the text response
languages supported by the registry's EPP server. languages supported by the registry's EPP server.
</t> </li>
<t> <li>
One or more &lt;objURI&gt; elements that contain nam espace URIs representing the objects One or more &lt;objURI&gt; elements that contain nam espace URIs representing the objects
that the registry's EPP server is capable of managin g. that the registry's EPP server is capable of managin g.
</t> </li>
<t> <li>
An OPTIONAL &lt;svcExtension&gt; element that contai An <bcp14>OPTIONAL</bcp14> &lt;svcExtension&gt; elem
ns one or more &lt;extURI&gt; ent that contains one or more &lt;extURI&gt;
elements that contain namespace URIs representing ob ject extensions supported by the elements that contain namespace URIs representing ob ject extensions supported by the
registry's EPP server. registry's EPP server.
</t> </li>
<t> <li>
A &lt;dcp&gt; element that contains child elements u sed to describe the server's privacy A &lt;dcp&gt; element that contains child elements u sed to describe the server's privacy
policy for data collection and management. See secti on 2.4 of <xref target="RFC5730"/> policy for data collection and management. See <xref target="RFC5730" section="2.4" sectionFormat="of" format="default"/>
for more details. for more details.
</t> </li>
</list> </ul>
</t> <t keepWithNext="true">
The following is an example of &lt;eppParams&gt; element
<t> object:
<figure> </t>
<preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
Example of &lt;eppParams&gt; element object:
</preamble>
<artwork><![CDATA[
... ...
<rdeEppParams:eppParams> <rdeEppParams:eppParams>
<rdeEppParams:version>1.0</rdeEppParams:version> <rdeEppParams:version>1.0</rdeEppParams:version>
<rdeEppParams:lang>en</rdeEppParams:lang> <rdeEppParams:lang>en</rdeEppParams:lang>
<rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0 <rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0
</rdeEppParams:objURI> </rdeEppParams:objURI>
<rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0 <rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0
</rdeEppParams:objURI> </rdeEppParams:objURI>
<rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0 <rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0
</rdeEppParams:objURI> </rdeEppParams:objURI>
skipping to change at line 3963 skipping to change at line 3711
<epp:recipient> <epp:recipient>
<epp:ours/> <epp:ours/>
<epp:public/> <epp:public/>
</epp:recipient> </epp:recipient>
<epp:retention> <epp:retention>
<epp:stated/> <epp:stated/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> <section numbered="true" toc="default">
<name>Policy Object</name>
</section> <t>
The policy object is a pseudo-object that is used to specify
<section title="Policy Object"> which <bcp14>OPTIONAL</bcp14> elements
<t> from the XML model are <bcp14>REQUIRED</bcp14> based on the
The Policy object is a pseudo-object that is used to specify business model of the registry. For the CSV model, the
which OPTIONAL elements <bcp14>OPTIONAL</bcp14> "isRequired" attribute of the &lt;rd
from the XML Model are REQUIRED based on the business model eCsv:field&gt; elements, defined in
of the registry. For the CSV Model, the <xref target="rdeCsv-csv" format="default"/>, is used to spe
OPTIONAL "isRequired" attribute of the &lt;rdeCsv:field&gt; cify which <bcp14>OPTIONAL</bcp14> fields are <bcp14>REQUIRED</bcp14>
elements, defined in
<xref target="rdeCsv-csv"/>, is used to specify which OPTION
AL fields are REQUIRED
based on the business model of the registry. based on the business model of the registry.
</t> </t>
<section anchor="policy_object" numbered="true" toc="default">
<section title="&lt;rdePolicy:policy&gt; object" anchor="policy_ <name>&lt;rdePolicy:policy&gt; Object</name>
object"> <t>
<t> The <bcp14>OPTIONAL</bcp14> &lt;policy&gt; contains the
The OPTIONAL &lt;policy&gt; contains the following attri following attributes:
butes: </t>
</t> <ul spacing="normal">
<t> <li>
<list style="symbols"> An &lt;element&gt; that defines that the referen
<t> ced &lt;element&gt; is <bcp14>REQUIRED</bcp14>.
An &lt;element&gt; that defines that the referen </li>
ced &lt;element&gt; is REQUIRED. <li>
</t> &lt;scope&gt; that defines the XPath (see <xref targ
<t> et="W3C.REC-xpath-31-20170321" format="default"/>) of the element referenced by
&lt;scope&gt; that defines the XPath (see, <xref tar &lt;element&gt;.
get='W3C.REC-xpath-31-20170321' />) of the element referenced by &lt;element&gt; </li>
. </ul>
</t> <t keepWithNext="true">
</list> The following is an example of &lt;rdePolicy:policy&
</t> gt; object:
</t>
<t> <sourcecode name="" type="xml" markers="false"><![CDATA[
<figure>
<preamble>
Example of &lt;rdePolicy:policy&gt; object:
</preamble>
<artwork><![CDATA[
... ...
<rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain"
element="rdeDomain:registrant" /> element="rdeDomain:registrant" />
...]]> ...
</artwork> ]]></sourcecode>
</figure> </section>
</t> </section>
</section> <section numbered="true" toc="default">
</section> <name>Header Object</name>
<t>
<section title="Header Object"> The header object is a pseudo-object that is used to specify
<t> the number
The Header Object is a pseudo-object that is used to specify of objects in the repository at a specific point in time (Ti
the number meline Watermark) regardless
of objects in the repository at a specific point in time (wa of the type of deposit: Differential, Full, or Incremental D
termark) regardless eposit.
of the type of deposit: Differential, Full or Incremental De The header object may also be used to provide additional inf
posit. ormation on the contents of the deposit.
The Header Object may also be used to provide additional inf The header object
ormation on the contents of the deposit. is only defined as XML but one header object <bcp14>MUST</bc
The Header Object p14> always be present
is only defined as XML but one header object MUST always be per escrow deposit regardless of using the XML model or CSV
present model.
per escrow deposit regardless of using XML Model or CSV Mode The header object is defined using the &lt;rdeHeader:header&
l. gt; element.
The Header Object is defined using the &lt;rdeHeader:header& </t>
gt; element. <section anchor="header_object" numbered="true" toc="default">
</t> <name>&lt;rdeHeader:header&gt; Object</name>
<t>
<section title="&lt;rdeHeader:header&gt; object" anchor="header_
object">
<t>
The &lt;rdeHeader:header&gt; contains the following elem ents: The &lt;rdeHeader:header&gt; contains the following elem ents:
</t> </t>
<t> <ul spacing="normal">
<list style="symbols"> <li>
<t> <t>
A choice of one of the elements defined in the &qu A choice of one of the elements defined in the "re
ot;repositoryTypeGroup&quot; group element that indicates the unique identifier positoryTypeGroup" group element that indicates the unique identifier for the re
for the repository being escrowed. Possible elements are: pository being escrowed. Possible elements are:
<list style="symbols"> </t>
<t> <ul spacing="normal">
A &lt;rdeHeader:tld&gt; element that defines T <li>
LD or the RCDN being escrowed in the case An &lt;rdeHeader:tld&gt; element that defines
of a Registry data escrow deposit. For IDNs th TLD or the RCDN being escrowed in the case
e A-Label is used (see <xref target="RFC5891"/>, Section 4.4). of a registry data escrow deposit. For IDNs, t
</t><t> he A-label is used (see <xref target="RFC5891" section="4.4" sectionFormat="comm
A &lt;rdeHeader:registrar&gt; element that def a" format="default"/>).
ines the Registrar ID corresponding to a Registrar data escrow deposit. </li>
In the case of an ICANN-accredited Registrar, <li>
the &lt;rdeHeader:registrar&gt; element MUST be the IANA Registrar ID assigned b An &lt;rdeHeader:registrar&gt; element that de
y ICANN. fines the Registrar ID corresponding to a registrar data escrow deposit.
</t> In the case of an ICANN-accredited registrar,
<t> the &lt;rdeHeader:registrar&gt; element <bcp14>MUST</bcp14> be the IANA Registra
A &lt;rdeHeader:ppsp&gt; element that defines r ID assigned by ICANN.
the provider ID corresponding to a Privacy and Proxy Services Provider data escr </li>
ow deposit. <li>
In the case of an ICANN-accredited Privacy and An &lt;rdeHeader:ppsp&gt; element that defines
Proxy Services Provider, the &lt;rdeHeader:ppsp&gt; element MUST be the unique the provider ID corresponding to a Privacy and Proxy Services Provider (PPSP) d
ID assigned by ICANN. ata escrow deposit.
</t> In the case of an ICANN-accredited PPSP, the &
<t> lt;rdeHeader:ppsp&gt; element <bcp14>MUST</bcp14> be the unique ID assigned by I
A &lt;rdeHeader:reseller&gt; element that defi CANN.
nes the provider ID corresponding to a Reseller data escrow deposit. </li>
</t> <li>
</list> An &lt;rdeHeader:reseller&gt; element that def
</t> ines the provider ID corresponding to a reseller data escrow deposit.
<t> </li>
</ul>
</li>
<li>
<t>
A &lt;count&gt; element that contains the number A &lt;count&gt; element that contains the number
of objects in the SRS at a specific point in time of objects in the SRS at a specific point in time
(watermark) regardless (Timeline Watermark) regardless
of the type of deposit: Differential, Full or Incr of the type of deposit: Differential, Full, or Inc
emental. remental.
The &lt;count&gt; element supports the following a ttributes: The &lt;count&gt; element supports the following a ttributes:
<list style="symbols"> </t>
<t> <ul spacing="normal">
A &quot;uri&quot; attribute <li>
A "uri" attribute
reflects the XML namespace URI of the primary ob jects for reflects the XML namespace URI of the primary ob jects for
the XML Model and CSV Model. For example, the " the XML model and CSV model. For example, the "
uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0"
for domain name objects using the XML Model, and for domain name objects using the XML model, and
the "uri" is set to "urn:ietf:params:xml:ns:csvDomain-1.0" the "uri" is set to "urn:ietf:params:xml:ns:csvDomain-1.0"
for domain name objects using the CSV Model. for domain name objects using the CSV model.
</t> </li>
<t> <li>
An OPTIONAL &quot;rcdn&quot; attribute indicat An <bcp14>OPTIONAL</bcp14> "rcdn" attribute in
es the RCDN of the objects included in the &lt;count&gt; element. For IDNs the A dicates the RCDN of the objects included in the &lt;count&gt; element. For IDNs,
-Label is used <xref target="RFC5891"/>, Section 4.4. If the &quot;rcdn&quot; at the A-label is used <xref target="RFC5891" section="4.4" sectionFormat="comma"
tribute is present, the value of the &lt;count&gt; element must include only obj format="default"/>. If the "rcdn" attribute is present, the value of the &lt;cou
ects related to registrations in the same and lower levels. For example in a dat nt&gt; element must include only objects related to registrations in the same an
a escrow deposit for the .EXAMPLE TLD, a value of &quot;example&quot; in the &qu d lower levels. For example in a data escrow deposit for the .EXAMPLE TLD, a val
ot;rcdn&quot; attribute within the &lt;count&gt; element indicates the number of ue of "example" in the "rcdn" attribute within the &lt;count&gt; element indicat
objects in the TLD including objects in other RCDNs within the TLD, whereas a v es the number of objects in the TLD including objects in other RCDNs within the
alue of &quot;com.example&quot; indicates the number of elements for objects und TLD, whereas a value of "com.example" indicates the number of elements for objec
er &quot;com.example&quot; and lower levels. Omitting the &quot;rcdn&quot; attri ts under "com.example" and lower levels. Omitting the "rcdn" attribute indicates
bute indicates that the total includes all objects of the specified &quot;uri&qu that the total includes all objects of the specified "uri" in the repository (e
ot; in the repository (e.g. the TLD, Registrar, or PPSP). .g., the TLD, Registrar, or PPSP).
</t> </li>
<t> <li>
An OPTIONAL &quot;registrarId&quot; attribute An <bcp14>OPTIONAL</bcp14> "registrarId" attri
indicates the identifier of the sponsoring Registrar of the objects included in bute indicates the identifier of the sponsoring registrar of the objects include
the &lt;count&gt; element. In the case of an ICANN-accredited Registrar, the val d in the &lt;count&gt; element. In the case of an ICANN-accredited registrar, th
ue MUST be the IANA Registrar ID assigned by ICANN. e value <bcp14>MUST</bcp14> be the IANA Registrar ID assigned by ICANN.
</t> </li>
</list> </ul>
</t> </li>
<t> <li>
An OPTIONAL &lt;contentTag&gt; element that con An <bcp14>OPTIONAL</bcp14> &lt;contentTag&gt; e
tains a tag that defines the expected content in the deposit. The producer and lement that contains a tag that defines the expected content in the deposit. Th
consumer of the deposits will coordinate the set of possible &lt;contentTag&gt; e producer and consumer of the deposits will coordinate the set of possible &lt;
element values. contentTag&gt; element values.
</t> </li>
</list> </ul>
</t> <t keepWithNext="true">
The following is an example of &lt;rdeHeader:header&
<t> gt; object referencing only the XML model objects:
<figure> </t>
<preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
Example of &lt;rdeHeader:header&gt; object referenci
ng only the XML Model objects:
</preamble>
<artwork><![CDATA[
... ...
<rdeHeader:header> <rdeHeader:header>
<rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:tld>test</rdeHeader:tld>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2</rdeHeader:count> uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeHost-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:rdeHost-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeContact-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:rdeContact-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1 uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
</rdeHeader:count> </rdeHeader:count>
</rdeHeader:header> </rdeHeader:header>
...]]> ...
</artwork> ]]></sourcecode>
</figure> <t keepWithNext="true">
</t> The following is an example of an &lt;rdeHeader:head
<t> er&gt; object referencing the CSV and XML model objects:
<figure> </t>
<preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
Example of &lt;rdeHeader:header&gt; object referenci
ng the CSV and XML Model objects:
</preamble>
<artwork><![CDATA[
... ...
<rdeHeader:header> <rdeHeader:header>
<rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:tld>test</rdeHeader:tld>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvDomain-1.0">2</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvDomain-1.0">2</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvHost-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvHost-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvContact-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvContact-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvRegistrar-1.0">1 uri="urn:ietf:params:xml:ns:csvRegistrar-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvIDN-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvIDN-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</rdeHeader:count> uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
</rdeHeader:count> </rdeHeader:count>
</rdeHeader:header> </rdeHeader:header>
...]]> ...
</artwork> ]]></sourcecode>
</figure>
</t>
</section>
</section>
<section title="DNRD Common Objects Collection">
<t>
The DNRD Common Objects Collection contains data structures
referenced by two or more of the main objects in the XML model.
</t>
</section>
</section> </section>
</section>
<section title="RDE IDN Variants handling"> <section numbered="true" toc="default">
<t> <name>DNRD Common Objects Collection</name>
Depending on the Registration Policy of the Registry, for a doma <t>
in name there may be The DNRD common objects collection contains data structures
multiple variant names. See <xref target="variantTLDsReport"/> f referenced by two or more of the main objects in the XML model.
or further detail on IDN variants. </t>
</t> </section>
<t> </section>
<section numbered="true" toc="default">
<name>RDE IDN Variants Handling</name>
<t>
Depending on the registration policy of the registry, for a doma
in name there may be
multiple variant names. See <xref target="variantTLDsReport" for
mat="default"/> for further details on IDN variants.
</t>
<t>
A registry could choose to escrow IDN variants as domains or NNDN objects. A specific IDN variant can be represented A registry could choose to escrow IDN variants as domains or NNDN objects. A specific IDN variant can be represented
in the escrow deposit, as a domain or as an NNDN object, but not b oth. in the escrow deposit, as a domain or as an NNDN object, but not b oth.
</t> </t>
<t> <t>
If using domain objects to represent IDN variants, the normal behavi or If using domain objects to represent IDN variants, the normal behavi or
during restoration of an SRS based on an escrow deposit is to restor e the during restoration of an SRS based on an escrow deposit is to restor e the
IDN variants as a mirrored variant. If the registration data of the IDN IDN variants as a mirrored variant. If the registration data of the IDN
variant is different from the original name, the details of this spe cific variant is different from the original name, the details of this spe cific
implementation MUST be described in the IDN policy document. implementation <bcp14>MUST</bcp14> be described in the IDN policy do
</t> cument.
<t> </t>
An NNDN or a domain name are explicit representations of an IDN <t>
variant while an IDN variant An NNDN or a domain name are explicit representations of an IDN
variant while an IDN variant that is
computed based on an algorithm is an implicit representation. Ex plicit representation of an IDN variant computed based on an algorithm is an implicit representation. Ex plicit representation of an IDN variant
takes precedence over an implicit representation. takes precedence over an implicit representation.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Profile"> <name>Profile</name>
<t> <t>
Different business models of registries exist, therefore the reg istry is responsible for defining Different business models of registries exist, therefore the reg istry is responsible for defining
a profile that matches its particular business model. The profil e mechanism allows a registry a profile that matches its particular business model. The profil e mechanism allows a registry
to extend this specification. to extend this specification.
</t> </t>
<t> <t>
A profile is the process of: A profile is the process of the following:
<list style="numbers"> </t>
<t> <ol spacing="normal" type="1"><li>
<t>
Extending base objects with the mechanisms defined for X ML and CSV models. Extending base objects with the mechanisms defined for X ML and CSV models.
<list style="symbols"> </t>
<t> <ul spacing="normal">
In the case of the XML model, abstract elements co <li>
uld be use to extend the following objects: In the case of the XML model, abstract elements co
&lt;domain&gt;, &lt;host&gt;, &lt;contact&gt;, &lt uld be used to extend the following objects:
;NNDN&gt; and &lt;registrar&gt; using &lt;domain&gt;, &lt;host&gt;, &lt;contact&gt;, &lt
XML schema substitution groups feature. ;NNDN&gt;, and &lt;registrar&gt; using
</t> the XML schema substitution groups feature.
</list> </li>
</t> </ul>
<t> </li>
Defining a &lt;policy&gt; object to specify which OPTION <li>
AL elements of this base specification Defining a &lt;policy&gt; object to specify which <bcp14
is required based on the business model of the registry. >OPTIONAL</bcp14> elements of this base specification
An example is the &lt;registrant&gt; element are required based on the business model of the registry
that is usually REQUIRED but it is specified as OPTIONAL . An example is the &lt;registrant&gt; element
in this specification to support some existing that is usually <bcp14>REQUIRED</bcp14>, but it is speci
fied as <bcp14>OPTIONAL</bcp14> in this specification to support some existing
business models. business models.
</t> </li>
<t> <li>
Adding new escrowed objects using the &lt;rde:contents&g t; and &lt;rde:deletes&gt; elements. Adding new escrowed objects using the &lt;rde:contents&g t; and &lt;rde:deletes&gt; elements.
</t> </li>
<t> <li>
Providing the XML schemas to third parties that require them to validate the escrow deposits. Providing the XML schemas to third parties that require them to validate the escrow deposits.
</t> </li>
</list> </ol>
</t> </section>
</section> <section numbered="true" toc="default">
<name>Data Escrow Agent Extended Verification Process</name>
<section title="Data escrow agent extended verification process"> <t>
<t> A data escrow agent <bcp14>SHOULD</bcp14> perform an exte
A Data Escrow Agent SHOULD perform an extended verificati nded verification process
on process that starts by creating a dataset to be tested by followi
that starts by creating a dataset to be tested by followi ng <xref target="RFC8909" section="5.2" sectionFormat="of" format="default"/>.
ng section 5.2 in <xref target="I-D.ietf-regext-data-escrow"/>. </t>
</t> <t>
<t>
The following are the minimum suggested The following are the minimum suggested
tests on the dataset: tests on the dataset:
<list style="symbols"> </t>
<t> <ul spacing="normal">
<li>
<t>
Validate the escrow deposits using the definition agreed with the registry. Validate the escrow deposits using the definition agreed with the registry.
<list style="symbols"> </t>
<t> <ul spacing="normal">
In the case of the XML model, the contents of the escrow depos <li>
its MUST be validated In the case of the XML model, the contents of the escrow depos
its <bcp14>MUST</bcp14> be validated
using the XML schemas of the profile. using the XML schemas of the profile.
</t> </li>
</list> </ul>
</t> </li>
<t> <li>
Count the objects and validate that the number of objects is Count the objects and validate that the number of objects is
equal to the number objects reported in the &lt;header&gt; element of the equal to the number objects reported in the &lt;header&gt; element of the
escrow deposit of that point in time (watermark). escrow deposit of that point in time (Timeline Watermark).
</t> </li>
<t> <li>
All contact objects linked to domain names MUST be present. All contact objects linked to domain names <bcp14>MUST</bcp14> be
</t> present.
<t> </li>
All registrars objects linked to other objects MUST be present. <li>
</t> All registrar objects linked to other objects <bcp14>MUST</bcp14>
<t> be present.
</li>
<li>
No domain name exists as both a domain name and an NNDN. No domain name exists as both a domain name and an NNDN.
</t> </li>
<t> <li>
The elements listed as required in the &lt;policy&gt; element MUST The elements listed as required in the &lt;policy&gt; element <bcp
be present. 14>MUST</bcp14> be present.
</t> </li>
<t> <li>
All idnTableRef definitions linked from other objects MUST be pres All idnTableRef definitions linked from other objects <bcp14>MUST<
ent. /bcp14> be present.
</t> </li>
<t> <li>
If an EPP Parameters Object was escrowed in the past, one and only If an EPP parameters object was escrowed in the past, one and only
one EPP Parameters Object MUST one EPP parameters object <bcp14>MUST</bcp14>
be present. be present.
</t> </li>
<t> <li>
The watermark is not in the future. The Timeline Watermark is not in the future.
</t> </li>
</list> </ul>
</t> </section>
</section>
<section title="Formal Syntax" anchor="formalSyntax">
<t>This standard is specified in XML Schema notation. The forma <section anchor="formalSyntax" numbered="true" toc="default">
l syntax presented <name>Formal Syntax</name>
<t>This standard is specified in XML Schema notation. The formal syntax p
resented
here is a complete schema representation suitable for here is a complete schema representation suitable for
automated validation.</t> automated validation.</t>
<t>The &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; tags are not pa rt of the schema; they are used to note <t>The &lt;CODE BEGINS&gt; and &lt;CODE ENDS&gt; tags are not part of the schema; they are used to note
the beginning and ending of the schema for URI registrati on purposes.</t> the beginning and ending of the schema for URI registrati on purposes.</t>
<section anchor="xsdRdeCsv" numbered="true" toc="default">
<section title="RDE CSV Schema" anchor="xsdRdeCsv"> <name>RDE CSV Schema</name>
<sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
skipping to change at line 4303 skipping to change at line 4032
<element name="files" <element name="files"
type="rdeCsv:filesType" /> type="rdeCsv:filesType" />
</sequence> </sequence>
<attribute name="name" <attribute name="name"
type="token" type="token"
use="required" /> use="required" />
<attribute name="sep" <attribute name="sep"
type="rdeCsv:sepType" type="rdeCsv:sepType"
default="," /> default="," />
</complexType> </complexType>
<!-- field seperator must be a single character --> <!-- field separator must be a single character -->
<simpleType name="sepType"> <simpleType name="sepType">
<restriction base="string"> <restriction base="string">
<minLength value="1" /> <minLength value="1" />
<maxLength value="1" /> <maxLength value="1" />
</restriction> </restriction>
</simpleType> </simpleType>
<!-- Abstract field type --> <!-- Abstract field type -->
<element name="field" <element name="field"
type="rdeCsv:fieldType" type="rdeCsv:fieldType"
abstract="true" /> abstract="true" />
skipping to change at line 4346 skipping to change at line 4075
<attribute name="isRequired" <attribute name="isRequired"
type="boolean" type="boolean"
default="true" /> default="true" />
<attribute name="parent" <attribute name="parent"
type="boolean" type="boolean"
default="false" /> default="false" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Concrete field types --> <!-- Concrete field types -->
<!-- UTF-8 Name field (e.g. domain name) --> <!-- UTF-8 Name field (e.g., domain name) -->
<element name="fUName" <element name="fUName"
type="rdeCsv:fNameType" type="rdeCsv:fNameType"
substitutionGroup="rdeCsv:field" /> substitutionGroup="rdeCsv:field" />
<complexType name="fNameType"> <complexType name="fNameType">
<complexContent> <complexContent>
<extension base="rdeCsv:fieldOptionalType"> <extension base="rdeCsv:fieldOptionalType">
<sequence /> <sequence />
<attribute name="type" <attribute name="type"
type="token" type="token"
default="eppcom\:labelType" /> default="eppcom\:labelType" />
skipping to change at line 4720 skipping to change at line 4449
<attribute name="type" <attribute name="type"
type="token" type="token"
default="anyURI" /> default="anyURI" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeDomain" numbered="true" toc="default">
<name>RDE Domain Object</name>
<section title="RDE Domain Object" anchor="xsdRdeDomain"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0" /> <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
<import namespace="urn:ietf:params:xml:ns:secDNS-1.1" /> <import namespace="urn:ietf:params:xml:ns:secDNS-1.1" />
<import namespace="urn:ietf:params:xml:ns:rgp-1.0" /> <import namespace="urn:ietf:params:xml:ns:rgp-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeIDN-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Domain provisioning schema Registry Data Escrow Domain provisioning schema
skipping to change at line 4857 skipping to change at line 4583
<sequence> <sequence>
<element name="name" <element name="name"
type="eppcom:labelType" type="eppcom:labelType"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeCsvDomain" numbered="true" toc="default">
<name>CSV Domain Object</name>
<section title="CSV Domain Object" anchor="xsdRdeCsvDomain"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvDomain-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
skipping to change at line 5034 skipping to change at line 4757
<attribute name="type" <attribute name="type"
type="token" type="token"
default="domain\:statusValueType" /> default="domain\:statusValueType" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeHost" numbered="true" toc="default">
<name>RDE Host Object</name>
<section title="RDE Host Object" anchor="xsdRdeHost"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:host-1.0" /> <import namespace="urn:ietf:params:xml:ns:host-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Host provisioning schema Registry Data Escrow Host provisioning schema
</documentation> </documentation>
</annotation> </annotation>
<element name="abstractHost" <element name="abstractHost"
skipping to change at line 5121 skipping to change at line 4841
maxOccurs="unbounded"> maxOccurs="unbounded">
<element name="name" <element name="name"
type="eppcom:labelType" /> type="eppcom:labelType" />
<element name="roid" <element name="roid"
type="eppcom:roidType" /> type="eppcom:roidType" />
</choice> </choice>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeCsvHost" numbered="true" toc="default">
<name>CSV Host Object</name>
<section title="CSV Host Object" anchor="xsdRdeCsvHost"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvHost-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvHost-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
skipping to change at line 5233 skipping to change at line 4950
<attribute name="type" <attribute name="type"
type="token" type="token"
default="host\:statusValueType" /> default="host\:statusValueType" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeContact" numbered="true" toc="default">
<name>RDE Contact Object</name>
<section title="RDE Contact Object" anchor="xsdRdeContact"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- Import common element types. --> <!-- Import common element types. -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:contact-1.0" /> <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow contact provisioning schema Registry Data Escrow contact provisioning schema
</documentation> </documentation>
</annotation> </annotation>
skipping to change at line 5347 skipping to change at line 5061
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType" type="eppcom:clIDType"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeCsvContact" numbered="true" toc="default">
<name>CSV Contact Object</name>
<section title="CSV Contact Object" anchor="xsdRdeCsvContact"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvContact-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
skipping to change at line 5650 skipping to change at line 5361
<attribute name="type" <attribute name="type"
type="token" type="token"
default="contact\:statusValueType" /> default="contact\:statusValueType" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeRegistrar" numbered="true" toc="default">
<name>RDE Registrar Object</name>
<section title="RDE Registrar Object" anchor="xsdRdeRegistrar"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeRegistrar-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0" xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- Import common element types. --> <!-- Import common element types. -->
skipping to change at line 5821 skipping to change at line 5529
<sequence> <sequence>
<element name="id" <element name="id"
type="eppcom:clIDType" type="eppcom:clIDType"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeCsvRegistrar" numbered="true" toc="default">
<name>CSV Registrar Object</name>
<section title="CSV Registrar Object" anchor="xsdRdeCsvRegistrar"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvRegistrar-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types. Import common element types.
--> -->
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:domain-1.0" /> <import namespace="urn:ietf:params:xml:ns:domain-1.0" />
<import namespace="urn:ietf:params:xml:ns:contact-1.0" /> <import namespace="urn:ietf:params:xml:ns:contact-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registar Comma-Separated Values (CSV) Object Registrar Comma-Separated Values (CSV) Object
</documentation> </documentation>
</annotation> </annotation>
<!-- <!--
Child elements of the <rde:contents> object Child elements of the <rde:contents> object
--> -->
<element name="contents" <element name="contents"
type="csvRegistrar:contentType" type="csvRegistrar:contentType"
substitutionGroup="rde:content" /> substitutionGroup="rde:content" />
<complexType name="contentType"> <complexType name="contentType">
<complexContent> <complexContent>
skipping to change at line 5952 skipping to change at line 5657
</restriction> </restriction>
</simpleType> </simpleType>
<!-- Whois URL field --> <!-- Whois URL field -->
<element name="fWhoisUrl" <element name="fWhoisUrl"
type="rdeCsv:anyURIType" type="rdeCsv:anyURIType"
substitutionGroup="rdeCsv:field" /> substitutionGroup="rdeCsv:field" />
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeIdn" numbered="true" toc="default">
<name>RDE IDN Table Reference Objects</name>
<section title="RDE IDN Table Reference Objects" anchor="xsdRdeIdn"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeIDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow IDN provisioning schema Registry Data Escrow IDN provisioning schema
skipping to change at line 6012 skipping to change at line 5714
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Simple Types --> <!-- Simple Types -->
<simpleType name="idType"> <simpleType name="idType">
<restriction base="token"> <restriction base="token">
<minLength value="1" /> <minLength value="1" />
<maxLength value="64" /> <maxLength value="64" />
</restriction> </restriction>
</simpleType> </simpleType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeCsvIdn" numbered="true" toc="default">
<name>CSV IDN Language Object</name>
<section title="CSV IDN Language Object" anchor="xsdRdeCsvIdn"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvIDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvIDN-1.0"
xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
--> -->
skipping to change at line 6073 skipping to change at line 5772
<element ref="rdeCsv:csv" <element ref="rdeCsv:csv"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeEpp" numbered="true" toc="default">
<name>EPP Parameters Object</name>
<section title="EPP Parameters Object" anchor="xsdRdeEpp"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeEppParams-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeEppParams-1.0"
xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:epp-1.0" /> <import namespace="urn:ietf:params:xml:ns:epp-1.0" />
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
skipping to change at line 6128 skipping to change at line 5824
<element name="svcExtension" <element name="svcExtension"
type="epp:extURIType" type="epp:extURIType"
minOccurs="0" /> minOccurs="0" />
<element name="dcp" <element name="dcp"
type="epp:dcpType" /> type="epp:dcpType" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeNndn" numbered="true" toc="default">
<name>NNDN Object</name>
<section title="NNDN Object" anchor="xsdRdeNndn"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeNNDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
skipping to change at line 6216 skipping to change at line 5909
<sequence> <sequence>
<element name="aName" <element name="aName"
type="eppcom:labelType" type="eppcom:labelType"
minOccurs="0" minOccurs="0"
maxOccurs="unbounded" /> maxOccurs="unbounded" />
</sequence> </sequence>
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeCsvNndn" numbered="true" toc="default">
<name>CSV NNDN Object</name>
<section title="CSV NNDN Object" anchor="xsdRdeCsvNndn"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:csvNNDN-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:csvNNDN-1.0"
xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0" xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<!-- <!--
Import common element types Import common element types
skipping to change at line 6305 skipping to change at line 5995
</complexContent> </complexContent>
</complexType> </complexType>
<!-- Mirroring uses NS mirror mechanism? --> <!-- Mirroring uses NS mirror mechanism? -->
<element name="fMirroringNS" <element name="fMirroringNS"
type="rdeCsv:fBooleanType" type="rdeCsv:fBooleanType"
substitutionGroup="rdeCsv:field" /> substitutionGroup="rdeCsv:field" />
<!-- <!--
End of schema. End of schema.
--> -->
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdePolicy" numbered="true" toc="default">
<name>Policy Object</name>
<section title="Policy Object" anchor="xsdRdePolicy"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdePolicy-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdePolicy-1.0"
xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0" xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<annotation> <annotation>
<documentation> <documentation>
Registry Data Escrow Policy schema Registry Data Escrow Policy schema
</documentation> </documentation>
skipping to change at line 6341 skipping to change at line 6028
<attribute name="scope" <attribute name="scope"
type="token" type="token"
use="required" /> use="required" />
<attribute name="element" <attribute name="element"
type="anyURI" type="anyURI"
use="required" /> use="required" />
</extension> </extension>
</complexContent> </complexContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeHeader" numbered="true" toc="default">
<name>Header Object</name>
<section title="Header Object" anchor="xsdRdeHeader"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeHeader-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" />
<annotation> <annotation>
skipping to change at line 6409 skipping to change at line 6093
type="anyURI" type="anyURI"
use="required" /> use="required" />
<attribute name="rcdn" <attribute name="rcdn"
type="eppcom:labelType" /> type="eppcom:labelType" />
<attribute name="registrarId" <attribute name="registrarId"
type="positiveInteger" /> type="positiveInteger" />
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section anchor="xsdRdeDnrdMisc" numbered="true" toc="default">
<name>DNRD Common Objects</name>
<section title="DNRD Common Objects" anchor="xsdRdeDnrdMisc"> <sourcecode name="" type="xml" markers="true"><![CDATA[
<t>
<figure><artwork><![CDATA[<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" <schema targetNamespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns="http://www.w3.org/2001/XMLSchema" xmlns="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"> elementFormDefault="qualified">
<import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" />
<annotation> <annotation>
<documentation> <documentation>
Data Escrow Deposit Common Objects schema Data Escrow Deposit Common Objects schema
</documentation> </documentation>
</annotation> </annotation>
<complexType name="rrType"> <complexType name="rrType">
<simpleContent> <simpleContent>
<extension base="eppcom:clIDType"> <extension base="eppcom:clIDType">
<attribute name="client" <attribute name="client"
type="eppcom:clIDType" /> type="eppcom:clIDType" />
</extension> </extension>
</simpleContent> </simpleContent>
</complexType> </complexType>
</schema> </schema>
<CODE ENDS>]]></artwork></figure> ]]></sourcecode>
</t> </section>
</section> </section>
<section numbered="true" toc="default">
</section> <name>Internationalization Considerations</name>
<t>
<section title="Internationalization Considerations"> Data escrow deposits are represented in XML, which provides nati
<t> ve support for encoding information
Data Escrow deposits are represented in XML, which provides nati
ve support for encoding information
using the Unicode character set and its more compact representat ions including UTF-8. Conformant XML using the Unicode character set and its more compact representat ions including UTF-8. Conformant XML
processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other
character encodings through use of an "encoding" attribute in an character encodings through use of an "encoding" attribute in an
&lt;?xml?&gt; declaration, use of UTF-8 &lt;?xml?&gt; declaration, the use of UTF-8
is RECOMMENDED. is <bcp14>RECOMMENDED</bcp14>.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="IANA Considerations"> <name>IANA Considerations</name>
<t> <t>
This document uses URNs to describe XML namespaces and XML schem as This document uses URNs to describe XML namespaces and XML schem as
conforming to a registry mechanism described in <xref target="RF conforming to a registry mechanism described in <xref target="RF
C3688"/>. C3688" format="default"/>.
The following URI assignments is requested of IANA. The following URIs have been assigned by IANA.
</t> </t>
<t>Registration request for the RDE CSV namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeCsv-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE CSV XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeCsv-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeCsv"/> of this document.</t>
</list>
</t>
<t>Registration request for the RDE domain namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeDomain-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE domain XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeDomain-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeDomain"/> of this document.</t>
</list>
</t>
<t>Registration request for the CSV domain namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:csvDomain-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the CSV domain XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:csvDomain-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeCsvDomain"/> of this document.</t
>
</list>
</t>
<t>Registration request for the RDE host namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeHost-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE host XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeHost-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeHost"/> of this document.</t>
</list>
</t>
<t>Registration request for the CSV host namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:csvHost-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the CSV host XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:csvHost-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeCsvHost"/> of this document.</t>
</list>
</t>
<t>Registration request for the RDE contact namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeContact-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE contact XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeContact-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeContact"/> of this document.</t>
</list>
</t>
<t>Registration request for the CSV contact namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:csvContact-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the CSV contact XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:csvContact-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeCsvContact"/> of this document.</
t>
</list>
</t>
<t>Registration request for the RDE registrar namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE registrar XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeRegistrar"/> of this document.</t
>
</list>
</t>
<t>Registration request for the CSV registrar namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:csvRegistrar-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the CSV registrar XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:csvRegistrar-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeCsvRegistrar"/> of this document.
</t>
</list>
</t>
<t>Registration request for the RDE IDN namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeIDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE IDN XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeIDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeIdn"/> of this document.</t>
</list>
</t>
<t>Registration request for the CSV IDN namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:csvIDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the CSV IDN XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:csvIDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeCsvIdn"/> of this document.</t>
</list>
</t>
<t>Registration request for the RDE EPP parameters namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeEppParams-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE EPP parameters XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeEppParams-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeEpp"/> of this document.</t>
</list>
</t>
<t>Registration request for the RDE NNDN namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeNNDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE NNDN XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:rdeNNDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeNndn"/> of this document.</t>
</list>
</t>
<t>Registration request for the CSV NNDN namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:csvNNDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the CSV NNDN XML schema:
<list>
<t>URI: urn:ietf:params:xml:schema:csvNNDN-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeCsvNndn"/> of this document.</t>
</list>
</t>
<t>Registration request for the RDE Policy namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdePolicy-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE Policy XML schema:
<list>
<t>URI: urn:ietf:params:xml:ns:rdePolicy-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdePolicy"/> of this document.</t>
</list>
</t>
<t>Registration request for the RDE Header namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeHeader-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE Header XML schema:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeHeader-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeHeader"/> of this document.</t>
</list>
</t>
<t>Registration request for the RDE Common Objects namespace:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>XML: None. Namespace URIs do not represent an XML specif
ication.</t>
</list>
</t>
<t>Registration request for the RDE Common Objects XML schema:
<list>
<t>URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0</t>
<t>Registrant Contact: IESG &lt;regext@ietf.org&g
t;</t>
<t>Note to RFC Editor: Please remove the email ad
dress from the RFC after IANA records it.</t>
<t>See <xref target="xsdRdeDnrdMisc"/> of this document.</t>
</list>
</t>
</section>
<section anchor="ImplementationStatus" title="Implementation Status"> <t>RDE CSV namespace:
<t>Note to RFC Editor: Please remove this section and the reference to R </t>
FC 7942 <xref target="RFC7942"/> before publication.</t> <dl spacing="compact">
<t> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeCsv-1.0</dd>
This section records the status of known implementations of the protoc <dt>Registrant Contact:</dt><dd>IESG</dd>
ol defined by this specification at the time of posting of this Internet-Draft, <dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
and is based on a proposal described in RFC 7942 <xref target="RFC7942"/>. The tion.</dd>
description of implementations in this section is intended to assist the IETF in </dl>
its decision processes in progressing drafts to RFCs. Please note that the lis <t>RDE CSV XML schema:
ting of any individual implementation here does not imply endorsement by the IET </t>
F. Furthermore, no effort has been spent to verify the information presented he <dl spacing="compact">
re that was supplied by IETF contributors. This is not intended as, and must not <dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeCsv-1.0</dd>
be construed to be, a catalog of available implementations or their features. <dt>Registrant Contact:</dt><dd>IESG</dd>
Readers are advised to note that other implementations may exist. </dl>
</t> <t>See <xref target="xsdRdeCsv" format="default"/> of this document.</t>
<t> <t>RDE domain namespace:
According to RFC 7942 <xref target="RFC7942"/>, "this will allow revie </t>
wers and working groups to assign due consideration to documents that have the b <dl spacing="compact">
enefit of running code, which may serve as evidence of valuable experimentation <dt>URI: </dt><dd>urn:ietf:params:xml:ns:rdeDomain-1.0</dd>
and feedback that have made the implemented protocols more mature. It is up to <dt>Registrant Contact:</dt><dd> IESG</dd>
the individual working groups to use this information as they see fit". <dt>XML: </dt><dd>None. Namespace URIs do not represent an XML specific
</t> ation.</dd>
<section title="Implementation in the gTLD space"> </dl>
<t>Organization: ICANN</t> <t>RDE domain XML schema:
<t>Name: ICANN Registry Agreement</t> </t>
<t>Description: the ICANN Base Registry Agreement requires Registries, <dl spacing="compact">
Data Escrow Agents, and ICANN to implement this specification. ICANN receives d <dt>URI:</dt><dd> urn:ietf:params:xml:schema:rdeDomain-1.0</dd>
aily notifications from Data Escrow Agents confirming that more than 1,200 gTLDs <dt>Registrant Contact:</dt><dd> IESG</dd>
are sending deposits that comply with this specification. ICANN receives on a w </dl>
eekly basis per gTLD, from more than 1,200 gTLD registries, a Bulk Registration <t>See <xref target="xsdRdeDomain" format="default"/> of this document.<
Data Access file that also complies with this specification. In addition, ICANN /t>
is aware of Registry Service Provider transitions using data files that conform <t>CSV domain namespace:
to this specification.</t> </t>
<t>Level of maturity: production.</t> <dl spacing="compact">
<t>Coverage: all aspects of this specification are implemented.</t> <dt>URI:</dt><dd> urn:ietf:params:xml:ns:csvDomain-1.0</dd>
<t>Version compatibility: versions 03 - 09 are known to be implemented <dt>Registrant Contact:</dt><dd> IESG</dd>
.</t> <dt>XML:</dt><dd> None. Namespace URIs do not represent an XML specific
<t>Contact: gustavo.lozano@icann.org</t> ation.</dd>
<t>URL: https://www.icann.org/resources/pages/registries/registries-ag </dl>
reements-en</t> <t>CSV domain XML schema:
</section> </t>
</section> <dl spacing="compact">
<dt>URI:</dt><dd> urn:ietf:params:xml:schema:csvDomain-1.0</dd>
<dt>Registrant Contact:</dt><dd> IESG</dd>
</dl>
<t>See <xref target="xsdRdeCsvDomain" format="default"/> of this documen
t.</t>
<t>RDE host namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeHost-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG </dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE host XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd> urn:ietf:params:xml:schema:rdeHost-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeHost" format="default"/> of this document.</t
>
<t>CSV host namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:csvHost-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>CSV host XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:csvHost-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeCsvHost" format="default"/> of this document.
</t>
<t>RDE contact namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeContact-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE contact XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeContact-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeContact" format="default"/> of this document.
</t>
<t>CSV contact namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:csvContact-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>CSV contact XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd> urn:ietf:params:xml:schema:csvContact-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeCsvContact" format="default"/> of this document
.</t>
<t>RDE registrar namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeRegistrar-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE registrar XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeRegistrar-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeRegistrar" format="default"/> of this document.
</t>
<t>CSV registrar namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:csvRegistrar-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>CSV registrar XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:csvRegistrar-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeCsvRegistrar" format="default"/> of this docume
nt.</t>
<t>RDE IDN namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeIDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE IDN XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeIDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeIdn" format="default"/> of this document.</t>
<t>CSV IDN namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:csvIDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>CSV IDN XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:csvIDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeCsvIdn" format="default"/> of this document.</t
>
<t>RDE EPP parameters namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeEppParams-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd> None. Namespace URIs do not represent an XML specific
ation.</dd>
</dl>
<t>RDE EPP parameters XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeEppParams-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeEpp" format="default"/> of this document.</t>
<t>RDE NNDN namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeNNDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE NNDN XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeNNDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeNndn" format="default"/> of this document.</t>
<t>CSV NNDN namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:csvNNDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>CSV NNDN XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:csvNNDN-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeCsvNndn" format="default"/> of this document.</
t>
<t>RDE Policy namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdePolicy-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE Policy XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd> urn:ietf:params:xml:schema:rdePolicy-1.0</dd>
<dt>Registrant Contact:</dt><dd> IESG</dd>
</dl>
<t>See <xref target="xsdRdePolicy" format="default"/> of this document.</t
>
<t>RDE Header namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd> urn:ietf:params:xml:ns:rdeHeader-1.0</dd>
<dt>Registrant Contact:</dt><dd> IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE Header XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd> urn:ietf:params:xml:schema:rdeHeader-1.0</dd>
<dt>Registrant Contact:</dt><dd> IESG</dd>
</dl>
<t>See <xref target="xsdRdeHeader" format="default"/> of this document.</t
>
<t>RDE Common Objects namespace:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeDnrdCommon-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
<dt>XML:</dt><dd>None. Namespace URIs do not represent an XML specifica
tion.</dd>
</dl>
<t>RDE Common Objects XML schema:
</t>
<dl spacing="compact">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeDnrdCommon-1.0</dd>
<dt>Registrant Contact:</dt><dd>IESG</dd>
</dl>
<t>See <xref target="xsdRdeDnrdMisc" format="default"/> of this document.<
/t>
</section>
<section title="Security Considerations"> <section numbered="true" toc="default">
<t> <name>Security Considerations</name>
<t>
This specification does not define the security mechanisms to be used in the transmission of the data escrow This specification does not define the security mechanisms to be used in the transmission of the data escrow
deposits, since it only specifies the minimum necessary to enabl e the rebuilding of a registry from deposits, since it only specifies the minimum necessary to enabl e the rebuilding of a registry from
deposits without intervention from the original registry. deposits without intervention from the original registry.
</t> </t>
<t> <t>
Depending on local policies, some elements, or, most likely, the Depending on local policies, some elements, or, most likely, the
whole deposit will be considered confidential. As such, the parties SHOULD take whole deposit will be considered confidential. As such, the parties <bcp14>SHOU
all the necessary precautions such as encrypting the data at rest and in transi LD</bcp14> take all the necessary precautions such as encrypting the data at res
t to avoid inadvertent disclosure of private data. Regardless of the precautions t and in transit to avoid inadvertent disclosure of private data. Regardless of
taken by the parties regarding data at rest and in transit, authentication cred the precautions taken by the parties regarding data at rest and in transit, auth
entials MUST NOT be escrowed. entication credentials <bcp14>MUST NOT</bcp14> be escrowed.
</t> </t>
<t> <t>
Authentication of the parties passing data escrow deposit files Authentication of the parties passing data escrow deposit files
is also of the utmost importance. The escrow agent MUST properly authenticate th is also of the utmost importance. The escrow agent <bcp14>MUST</bcp14> properly
e registry's identity before accepting data escrow deposits. The registry MUST a authenticate the registry's identity before accepting data escrow deposits. The
uthenticate the escrow agent's identity before submitting any data, and the data registry <bcp14>MUST</bcp14> authenticate the escrow agent's identity before sub
escrow agent MUST authenticate the identity of the party receiving the data esc mitting any data, and the data escrow agent <bcp14>MUST</bcp14> authenticate the
row deposits for the purposes deemed appropriate. identity of the party receiving the data escrow deposits for the purposes deeme
</t> d appropriate.
<t> </t>
Additionally, the registry and the escrow agent MUST use integri <t>
ty checking mechanisms to ensure the data transmitted is what the source intende Additionally, the registry and the escrow agent <bcp14>MUST</bcp
d. Validation of the contents by the parties is RECOMMENDED to ensure that the f 14> use integrity checking mechanisms to ensure the data transmitted is what the
ile was transmitted correctly from the registry or escrow agent and that the con source intended. Validation of the contents by the parties is <bcp14>RECOMMENDE
tents are &quot;meaningful&quot;. D</bcp14> to ensure that the file was transmitted correctly from the registry or
</t> escrow agent and that the contents are "meaningful".
<t>A few elements in this specification contain URLs, the use of HTT </t>
P over TLS (Transport Layer Security), <xref target="RFC2818"/> is RECOMMENDED o <t>A few elements in this specification contain URLs; the use of HTTP over
n the URLs. </t> TLS (Transport Layer Security) <xref target="RFC2818" format="default"/> is <bc
<t>The various data structures in the document include a few places p14>RECOMMENDED</bcp14> on the URLs. </t>
that have internal redundancy, and if the values become inconsistent there can b <t>The various data structures in the document include a few places that h
e harmful consequences, such as different entities using different fields as the ave internal redundancy, and if the values become inconsistent there can be harm
ir reference.</t> ful consequences, such as different entities using different fields as their ref
<t>Note: if Transport Layer Security (TLS) is used when providing an erence.</t>
escrow services, the recommendations in <xref target="BCP195"/> MUST be impleme <aside><t>Note: if TLS is used when providing an escrow service, the recom
nted.</t> mendations in <xref target="BCP195" format="default"/> <bcp14>MUST</bcp14> be im
plemented.</t></aside>
</section> </section>
<section numbered="true" toc="default">
<section title="Privacy Considerations"> <name>Privacy Considerations</name>
<t> <t>
This specification defines a format that may be used to escrow personal data. T This specification defines a format that may be used to escrow personal data. T
he process of data escrow is governed by a legal document agreed by the parties, he process of data escrow is governed by a legal document that is agreed to by t
and such legal document must ensure that privacy-sensitive and/or personal data he parties, and such a legal document must ensure that privacy-sensitive and/or
receives the required protection. personal data receives the required protection.
</t> </t>
</section> </section>
<section title="Acknowledgments">
<t>
Parts of this document are based on EPP <xref target="RFC5730"/>
and related RFCs by Scott Hollenbeck.
</t>
<t>
Special suggestions that have been incorporated into this docume
nt
were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy,
Marc Groeneweg,
Michael Young, Chris Wright, Patrick Mevzek, Stephen Morris, Sco
tt Hollenbeck, Stephane Bortzmeyer,
Warren Kumari, Paul Hoffman, Vika Mpisane, Bernie Hoeneisen, Jim
Galvin, Andrew Sullivan, Hiro Hotta,
Christopher Browne, Daniel Kalchev, David Conrad, James Mitchell
, Francisco Obispo, Bhadresh Modi,
Alexander Mayrhofer and Benjamin Kaduk.
</t>
<t>
Shoji Noguchi and Francisco Arias participated
as co-authors until version 05 providing invaluable support for th
is
document.
</t>
</section>
<section title="Change History">
<t>
[[RFC Editor: Please remove this section.]]
</t>
<section title="Changes from draft-arias-noguchi-registry-data-escro
w-02 to -dnrd-objects-mapping-00">
<t>
<list style="numbers">
<t>Added definition for child elements under the &lt;dom
ain&gt; element.</t>
<t>Added definition for child elements under the &lt;hos
t&gt; element.</t>
<t>Added definition for child elements under the &lt;con
tact&gt; element.</t>
<t>
Rewrote the IDN Variants Handling section to use the
variant states as described in ICANN's
Study of Issues Related to the Management of IDN Var
iant TLDs.
</t>
<t>Renamed &lt;icannID&gt; to &lt;gurid&gt; in the &lt;r
deRegistrar&gt;.</t>
<t>Renamed &lt;dnssec&gt; to &lt;secDNS&gt; in the &lt;d
omain&gt; element.</t>
<t>Renamed &lt;transfData&gt; to &lt;trnData&gt; in the
&lt;domain&gt; element.</t>
<t>Added &lt;whoisInfo&gt; element under &lt;rdeRegistra
r&gt; element.</t>
<t>Fixed some typographical errors and omissions.</t>
</list>
</t>
</section>
<section title="Changes from 00 to 01">
<t>
<list style="numbers">
<t>Specify OPTIONAL elements in the draft.</t>
<t>Added NNDN object to support list of reserved names a
nd different IDN variants models.</t>
<t>Removed subordinated host element from the domain obj
ect.</t>
<t>Added eppParams object.</t>
<t>Added variantGenerator element to the domain object.<
/t>
<t>Added lgr to the IDN table object.</t>
</list>
</t>
</section>
<section title="Changes from 01 to 02">
<t>
<list style="numbers">
<t>Updates to the all objects based on feedback from the
list.</t>
<t>Start of XML and CSV drafts merge.</t>
<t>Added header object.</t>
<t>Added report object.</t>
<t>Added notification object.</t>
<t>Added Data Escrow Agent Extended Verification Process
section.</t>
<t>Added Notifications from Registries to Third Parties.
</t>
<t>Added Notifications from Data Escrow Agents to Third
Parties.</t>
<t>Added FULL, DIFF deposit examples using the XML model
only.</t>
</list>
</t>
</section>
<section title="Changes from 02 to 03">
<t>
<list style="numbers">
<t>Remove authinfo from the XML Schema.</t>
<t>Resend attribute is now an element </t>
<t>Scope attribute added to policy object.</t>
</list>
</t>
</section>
<section title="Changes from 03 to 04">
<t>
<list style="numbers">
<t>Merged draft-gould-thippeswamy-dnrd-csv-mapping-03 in
to draft-arias-noguchi-dnrd-objects-mapping-02.</t>
<t>Changed the cksum attribute of &lt;rdeCsv:file&gt; to
use CRC32 and changed all of the sample cksum values to use CRC32, based on fee
dback from David Kipling.</t>
<t>Changed the optional &lt;rdeCsv:sep&gt; element to be
an optional "sep" attribute value of the &lt;rdeCsv:csv&gt; element with a defa
ult value of "," based on feedback from David Kipling.</t>
<t>Added support for the optional "parent" attribute for
the to the CSV fields to indicate a field as a reference to a parent object, ba
sed on feedback from David Kipling.</t>
<t>Added support for the CSV model for the NNDN.</t>
<t>Added support to delete hosts based on roid.</t>
<t>Added mirrored state to NNDN</t>
<t>Minor fixes to XML XSDs.</t>
<t>The Report and Notification objects were moved to draft
-lozano-icann-registry-interfaces</t>
<t>The section Data escrow notifications was moved to draf
t-lozano-icann-registry-interfaces</t>
<t>Removed references to the &lt;rdeCsv:fCrRr&gt;, &lt;rde
Csv:fCrID&gt;, and &lt;rdeCsv:fCrDate&gt; from the "hostStatuses" and "hostAddre
sses" CSV files.</t>
<t>Removed references to the &lt;rdeCsv:fCrRr&gt;, &lt;rde
Csv:fCrID&gt;, and &lt;rdeCsv:fCrDate&gt; from the "contactStatuses" CSV file.</
t>
<t>Removed references to the &lt;rdeCsv:fCrRr&gt;, &lt;rde
Csv:fCrID&gt;, and &lt;rdeCsv:fCrDate&gt; from the "domainContacts", "domainStat
uses", and "domainNameServers" CSV files.</t>
<t>Changed &lt;rdeCsv:fLanguage&gt; to &lt;rdeCsv:fLang&gt
;.</t>
<t>Replaced use of &lt;rdeCsv:fLang&gt; to new &lt;rdeCsv:
fIdnTableId&gt; field in the "domain", "idnLanguage", and "NNDN" CSV files.</t>
<t>Replaced use of &lt;csvHost:fName&gt; with &lt;rdeCsv:f
Roid&gt; in the "host" &lt;csvHost:deletes&gt; &lt;rdeCsv:csv&gt; element.</t>
<t>Changed the foreign key of the hosts to use &lt;rdeCsv:
fRoid&gt; instead of &lt;csvHost:fName&gt; and removed use of &lt;csvHost:fName&
gt; in the "domainNameServers", "hostStatuses", and "hostAddresses" CSV files.</
t>
<t>Added use of the MUST keyword for CSV fields that are r
equired to be supported in an EPP based system.</t>
<t>Removed use of the &lt;rdeCsv:fRoid&gt; field element f
or the "registrar" CSV file.</t>
<t>Added definition of &lt;csvNNDN:fMirroringNS&gt; field
element.</t>
</list>
</t>
</section>
<section title="Changes from 04 to 05">
<t>
<list style="numbers">
<t>Updated the examples of the full and differential deposits us
ing the CSV and XML model.</t>
<t>Made &lt;rdeCsv:fExDate&gt; optional for the "domainTransfer"
CSV file to match the XML definition.</t>
<t>Made &lt;csvDomain:fOriginalName&gt; optional for the "domain
" CSV file to match the XML definition.</t>
<t>Made &lt;rdeCsv:fTrDate&gt; optional for the "domain" and "co
ntact" CSV files to match the XML definition.</t>
<t>Change &lt;idnTableId&gt; from IDREF to idType.</t>
<t>Minor editorial changes.</t>
</list>
</t>
</section>
<section title="Changes from 05 to 06">
<t>
<list style="numbers">
<t>Revised the differential and incremental deposits for the CSV
format to use cascade update / replace and delete
from the parent object to be consistent with the XML format.</
t>
<t>Revised the structure of the CSV format sections to utilize s
ub-sections instead of a list for the CSV file definitions.</t>
<t>Added the "CSV Parent Child Relationship" section to describe
the concept of parent child relationships across CSV file definitions.</t>
<t>Added the "domainNameServersAddresses" CSV File Definition se
ction to support the domain host attributes model of <xref target="RFC5731"/>.</
t>
<t>Made the required fields in the CSV format consistent with th
e XML format. The CSV fields updated to be required include:
&lt;rdeCsv:fCrDate&gt;, &lt;csvDomain:fContactType&gt;, &lt;cs
vDomain:fStatus&gt;, &lt;csvDomain:fKeyTag&gt;, &lt;csvDomain:fDsAlg&gt;,
&lt;csvDomain:fDigestType&gt;, &lt;csvDomain:fDigest&gt;, &lt;
csvDomain:fFlags&gt;, &lt;csvDomain:fProtocol&gt;,
&lt;csvDomain:fKeyAlg&gt;, &lt;csvDomain:fPubKey&gt;, &lt;rdeC
sv:fTrStatus&gt;, &lt;rdeCsv:fReRr&gt;, &lt;rdeCsv:fReDate&lt;,
&lt;rdeCsv:fAcRr&gt;, &lt;rdeCsv:fAcDate&gt;, &lt;csvHost:fSta
tus&gt;, &lt;csvContact:fCc&gt;, &lt;csvContact:fStatus&gt;, &lt;csvContact:fPos
talType&gt;,
&lt;csvRegistrar:fStatus&gt;, and &lt;csvNNDN:fNameState&gt;.<
/t>
<t>Revised the CSV examples to use a more realistic set of recor
ds.</t>
</list>
</t>
</section>
<section title="Changes from 06 to 07">
<t>
<list style="numbers">
<t>Created &quot;repositoryTypeGroup&quot; group element in the
rdeHeader including the &lt;rdeHeader:registrar&gt;, &lt;rdeHeader:ppsp&gt; and
&lt;rdeHeader:tld&gt; elements.</t>
<t>Added the optional &quot;rcdn&quot; and &quot;registrarId&quo
t; attributes to the &lt;rdeHeader:count&gt; element</t>
</list>
</t>
</section>
<section title="Changes from 07 to 08">
<t>
<list style="numbers">
<t>The following registrar elements were made optional to suppor
t greater flexibility for the implementation of policies: status, postalInfo, em
ail and crDate.</t>
<t>The following domain name elements were made optional to supp
ort greater flexibility for the implementation of policies: crRr.</t>
</list>
</t>
</section>
<section title="Changes from 08 to 09">
<t>
<list style="numbers">
<t>Implementation Status section was added</t>
</list>
</t>
</section>
<section title="Changes from 09 to 10">
<t>
<list style="numbers">
<t>Editorial changes in section <xref target="csvDnssecDefinitio
n"/>.</t>
<t>Added MAY clause when the DS Data Interface is used in sectio
n <xref target="csvDnssecDefinition"/>.</t>
</list>
</t>
</section>
<section title="Changes from 10 to REGEXT 00">
<t>
<list style="numbers">
<t>Internet Draft (I-D) adopted by the REGEXT WG.</t>
</list>
</t>
</section>
<section title="Changes REGEXT 00 to REGEXT 01">
<t>
<list style="numbers">
<t>Added the &lt;rdeHeader:reseller&gt; element to the &quot;rep
ositoryTypeGroup&quot; group element in the rdeHeader.</t>
<t>Privacy consideration section was added</t>
<t>Updates on section 8</t>
</list>
</t>
</section>
<section title="Changes REGEXT 01 to REGEXT 02">
<t>
<list style="numbers">
<t>Added a choice between the use of the &lt;rdeCsv:fClID&gt; or
&lt;csvRegistrar:fGurid&gt;
fields in the CSV "domain", "host", and "contact" definitions.</
t>
<t>Added a choice between the use of the &lt;rdeCsv:fRoid&gt; or
&lt;csvHost:fName&gt;
fields in the CSV "domainNameServers" definition.</t>
<t>Changed "of client" to "of the client" throughout the documen
t.</t>
<t>Modified all references of 'The attribute isRequired MUST equ
al "true".' to
'The attribute "isRequired" MUST equal "true".'</t>
<t>Combined the &lt;csvDomain:fName&gt; and &lt;csvDomain:fConta
ctType&gt; fields
in a single required list for the CSV "domainContacts" definitio
n.</t>
<t>Combined the &lt;csvDomain:fName&gt;, &lt;csvDomain:fStatus&g
t;, and &lt;csvDomain:fRgpStatus&gt; fields
in a single required list for the CSV "domainStatuses" definitio
n.</t>
<t>Moved the &lt;rdeCsv:fCrRr&gt; the &lt;rdeCsv:fUpRr&gt; field
s to the MAY list for the CSV
"domain", "host", and "contact" definitions.</t>
<t>Made the order of the &lt;rdeCsv:fCrRr&gt;, &l
t;rdeCsv:crID&gt;, &lt;rdeCsv:UpRr&gt;, and &lt;rdeCsv:UpID&gt; fields more cons
istent in the CSV lists.</t>
<t>Fixed an error in the order of the &lt;contact&gt; object exa
mple.</t>
<t>Changed &lt;rdeCsv:fCrDate&gt; to be optional to match &lt;cr
Date&gt; being optional in the XML model, by
having it use type rdeCsv:fDateTimeType instead of rdeCsv:fRequi
redDateTimeType and ensuring that
&lt;rdeCsv:fCrDate&gt; is included in the MAY field lists and no
t the MUST field lists.</t>
<t>Made &lt;rdeCsv:fExDate&gt; optional for the "domain" CSV def
inition to be consistent with the XML model,
by removing the sentence 'The attribute "isRequired" MUST equal
"true".' from the description and moving the
field to the MAY field list.</t>
<t>Made &lt;rdeCsv:fUpDate&gt; optional for the "domain" and "co
ntact" CSV definitions to be consistent with the XML model, by
moving the field to the MAY field list.</t>
<t>Made &lt;rdeCsv:fCrRr&gt; optional to be consistent with the
XML model, by having it use type rdeCsv:fClIDType instead
of rdeCsv:fClIDRequiredType.</t>
<t>Made &lt;rdeCsv:fReRr&gt; required to be consistent with the
XML model,
by having it use type rdeCsv:fClIDRequiredType instead of rdeCsv
:fClIDType.</t>
<t>Made the &lt;csvRegistrar:fGurid&gt; field in the "host", "co
ntact", and "registrar" CSV definitions required explicitly by removing 'and isR
equired="true"'
and adding the sentence 'The attribute isRequired MUST equal "tr
ue".', when it is chosen as the primary field.</t>
<t>Removed extra '/>.' at the end of the &lt;csvHost:fStatus&gt;
field description in the "hostStatuses" CSV definition.</t>
<t>Made the &lt;csvRegistrar:fStatus&gt; field optional to be co
nsistent with the XML model, by having csvRegistrar:fStatusType extend
rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType.</t>
<t>Made the &lt;csvContact:fEmail&gt; field for the "registrar"
CSV definition explicitly optional to be consistent with the XML model,
by adding the sentence 'The attribute isRequired MUST equal "fal
se".' to the field description and including the definition of isRequired="false
" in
the "registrar" CSV definition examples.</t>
<t>Added the choice between the use of the &lt;csvRegistrar:fId&
gt; and &lt;csvRegistrar:fGurid&gt; fields in the deletes "registrar" CSV defini
tion
to be consistent with the "registrar" CSV definition.</t>
<t>Made the &lt;crRr&gt; and &lt;crDate&gt; elements optional fo
r the host and contact objects in the XML model to be consistent with the domain
object.</t>
</list>
</t>
</section>
<section title="Changes REGEXT 02 to REGEXT 03">
<t>
<list style="numbers">
<t>Added the optional element contentTag in the header object.</
t>
<t>Editorial updates.</t>
</list>
</t>
</section>
<section title="Changes REGEXT 03 to REGEXT 04">
<t>
<list style="numbers">
<t>Note: Updates from version REGEXT 03 to REGEXT
04 attend the feedback provided during the document shepherd review.</t>
<t>Editorial updates.</t>
<t>Examples now use domain names from the .exampl
e TLD.</t>
<t>The introduction was enhanced by explaining th
e need for data escrow and the proposed solution.</t>
<t>Explanation regarding NNDN was improved.</t>
<t>Explanation regarding the CSV and XML model wa
s improved.</t>
<t>Section 4.5 updated to make the text clearer.<
/t>
<t>draft-arias-noguchi-registry-data-escrow is no
w referenced from the I-D repository.</t>
<t>The XML prefix "rdeDomain" is now consistently
used.</t>
<t>The prevID attribute was removed from the exam
ples of full deposits.</t>
<t>The examples were updated to use present dates
.</t>
</list>
</t>
</section>
<section title="Changes REGEXT 04 to REGEXT 05">
<t>
<list style="numbers">
<t>draft-ietf-regext-data-escrow (version 04) is
now referenced from the I-D repository.</t>
<t>The example in idnLanguage CSV file definition
updated to use the sep attribute.</t>
<t>The reference in the example in hostAddresses
CSV file definition was updated.</t>
<t>Moved <xref target="RFC0791"/> and <xref targe
t="RFC5952"/> to the Normative References section.</t>
</list>
</t>
</section>
<section title="Changes REGEXT 05 to REGEXT 06">
<t>
<list style="numbers">
<t>Changes based on the feedback provided here: h
ttps://mailarchive.ietf.org/arch/msg/regext/nA8eTYIrXJ44_6ullQlRLW6T74s</t>
</list>
</t>
</section>
<section title="Changes REGEXT 06 to REGEXT 07">
<t>
<list style="numbers">
<t>Changes based on the feedback provided here: h
ttps://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm-QJ8FzaxxE</t>
<t>Changes based on the feedback provided here: h
ttps://mailarchive.ietf.org/arch/msg/regext/780Xw-z1RMRb79nmZ6ABmRTo1fU</t>
</list>
</t>
</section>
<section title="Changes REGEXT 07 to REGEXT 08">
<t>
<list style="numbers">
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/UaMNvl1xh60ldjpqHHYc3TNsfhg</t>
<t>Changes based on the feedback provided here: h
ttps://mailarchive.ietf.org/arch/msg/regext/B3QTxUCWUE4R_QharAQlA3041j0</t>
</list>
</t>
</section>
<section title="Changes REGEXT 08 to REGEXT 09">
<t>
<list style="numbers">
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/EmKW32exlPgLbBUIbS8OjdYUJWc</t>
</list>
</t>
</section>
<section title="Changes REGEXT 09 to REGEXT 10">
<t>
<list style="numbers">
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/tmoKLAV6jhh2zp4JczjeWdr_jJE</t>
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/m7gyDTjHuRqIQCuKMHF-OLSS99k</t>
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/3Acx5KHfeUdxZbx6A7zgoZHxIto</t>
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/3Acx5KHfeUdxZbx6A7zgoZHxIto</t>
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/7JiP2fzOr8KCnzI2rwoP-_KlxZY</t>
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/dbuyW5YTYj4VcFHUQYC-D8OMv_g</t>
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/ExUZenwC81ZQe9x24-8IKT_FWm8</t>
</list>
</t>
</section>
<section title="Changes REGEXT 10 to REGEXT 11">
<t>
<list style="numbers">
<t>Changes based on the feedback provided here: https://
mailarchive.ietf.org/arch/msg/regext/ghEr55r7CVdwUSvkvMGpol4aSh0</t>
</list>
</t>
</section>
</section>
<section title="Example of a Full Deposit using the XML model"> <section numbered="true" toc="default">
<t> <name>Example of a Full Deposit Using the XML Model</name>
<figure> <t keepWithNext="true">
<preamble> The following is an example of a Full Deposit using the XML
Example of a Full Deposit using the XML model: model:
</preamble> </t>
<artwork><![CDATA[ <sourcecode name="" type="xml" markers="false"><![CDATA[
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="FULL" id="20191017001" <rde:deposit type="FULL" id="20191017001"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
skipping to change at line 7439 skipping to change at line 6666
<epp:retention> <epp:retention>
<epp:stated/> <epp:stated/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
<rdePolicy:policy <rdePolicy:policy
scope="//rde:deposit/rde:contents/rdeDomain:domain" scope="//rde:deposit/rde:contents/rdeDomain:domain"
element="rdeDomain:registrant" /> element="rdeDomain:registrant" />
</rde:contents> </rde:contents>
</rde:deposit>]]> </rde:deposit>
</artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section numbered="true" toc="default">
<name>Example of a Differential Deposit Using the XML Model</name>
<section title="Example of Differential Deposit using the XML model"> <t keepWithNext="true">
<t> The following is an example of a Differential Deposit using
<figure> the XML model:
<preamble> </t>
Example of a Differential Deposit using the XML model: <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit type="DIFF" id="20191017002" prevId="20191017001" <rde:deposit type="DIFF" id="20191017002" prevId="20191017001"
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0"
xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0"
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0"
xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0"
xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0"
xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0"
skipping to change at line 7523 skipping to change at line 6747
uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1 uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1 uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1
</rdeHeader:count> </rdeHeader:count>
<rdeHeader:count <rdeHeader:count
uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1
</rdeHeader:count> </rdeHeader:count>
</rdeHeader:header> </rdeHeader:header>
</rde:contents> </rde:contents>
</rde:deposit>]]> </rde:deposit>
</artwork></figure> ]]></sourcecode>
</t> </section>
<section numbered="true" toc="default">
</section> <name>Example of a Full Deposit Using the CSV Model</name>
<t keepWithNext="true">
<section title="Example of a Full Deposit using the CSV model"> The following is an example of a Full Deposit using the CSV
<t> model:
<figure> </t>
<preamble> <sourcecode name="" type="xml" markers="false"><![CDATA[
Example of a Full Deposit using the CSV model:
</preamble>
<artwork><![CDATA[
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit <rde:deposit
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
skipping to change at line 7965 skipping to change at line 7185
<epp:public/> <epp:public/>
<epp:unrelated/> <epp:unrelated/>
</epp:recipient> </epp:recipient>
<epp:retention> <epp:retention>
<epp:indefinite/> <epp:indefinite/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
</rde:contents> </rde:contents>
</rde:deposit>]]> </rde:deposit>
</artwork></figure> ]]></sourcecode>
</t> </section>
</section> <section numbered="true" toc="default">
<name>Example of a Differential Deposit Using the CSV Model</name>
<section title="Example of Differential Deposit using the CSV model"> <t keepWithNext="true">
<t> The following is an example of a Differential Deposit using
<figure> the CSV model:
<preamble> </t>
Example of a Differential Deposit using the CSV model: <sourcecode name="" type="xml" markers="false"><![CDATA[
</preamble>
<artwork><![CDATA[
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<rde:deposit <rde:deposit
xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0"
xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0"
xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0"
xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0"
xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0"
skipping to change at line 8484 skipping to change at line 7701
<epp:public/> <epp:public/>
<epp:unrelated/> <epp:unrelated/>
</epp:recipient> </epp:recipient>
<epp:retention> <epp:retention>
<epp:indefinite/> <epp:indefinite/>
</epp:retention> </epp:retention>
</epp:statement> </epp:statement>
</rdeEppParams:dcp> </rdeEppParams:dcp>
</rdeEppParams:eppParams> </rdeEppParams:eppParams>
</rde:contents> </rde:contents>
</rde:deposit>]]> </rde:deposit>
</artwork></figure> ]]></sourcecode>
</t> </section>
</middle>
</section> <back>
</middle>
<back>
<references title='Normative References'>
&RFC0791;
&RFC2119;
&RFC3339;
&RFC3915;
&RFC5730;
&RFC5731;
&RFC5732;
&RFC5733;
&RFC5891;
&RFC5910;
&RFC5952;
&RFC6234;
&RFC8174;
&RFC8499;
&I-D.ietf-regext-data-escrow; <references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.0791.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.2119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.3339.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.3915.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5730.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5731.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5732.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5733.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5891.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5910.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.5952.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.6234.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8174.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8499.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.8909.xml"/>
<reference anchor="BCP195" target="https://www.rfc-editor.org/info/bcp195 <referencegroup anchor="BCP195" target="https://www.rfc-editor.org/info/bcp195">
"> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
<front> FC.7525.xml"/>
<title>Recommendations for Secure Use of Transport Layer </referencegroup>
Security (TLS) and Datagram Transport Layer Security (DTLS)</title>
<author initials="Y." surname="Sheffer" fullname="Y. Shef
fer">
<organization/>
</author>
<author initials="R." surname="Holz" fullname="R. Holz">
<organization/>
</author>
<author initials="P." surname="Saint-Andre" fullname="P.
Saint-Andre">
<organization/>
</author>
<date year="2015" month="May"/>
</front>
<seriesInfo name="BCP" value="195"/>
<seriesInfo name="RFC" value="7525"/>
<seriesInfo name="DOI" value="10.17487/RFC7525"/>
</reference>
<reference anchor="ISO-3166-1"> <reference anchor="ISO-3166-1">
<front> <front>
<title> Codes for the representation of names of countries a <title> Codes for the representation of names of countries and their
nd their
subdivisions -- Part 1: Country codes subdivisions -- Part 1: Country codes
</title> </title>
<author fullname="ISO Standard 3166"> <author>
<organization>International Organization for Standardiza <organization>International Organization for Standardization</orga
tion</organization> nization>
</author> </author>
<date month="November" year="2006"/> <date month="August" year="2020"/>
</front> </front>
<seriesInfo name="ISO Standard" value="3166"/> <seriesInfo name="ISO Standard" value="3166"/>
</reference> </reference>
<reference anchor="ITU-E164"> <reference anchor="ITU-E164">
<front> <front>
<title> <title>
The international public telecommunication numbering pla n The international public telecommunication numbering pla n
</title> </title>
<author> <author>
<organization>International Telecommunication Union</org <organization>International Telecommunication Union</organization>
anization> </author>
</author> <date month="February" year="2005"/>
<date month="February" year="2005"/> </front>
</front> <seriesInfo name="ITU-T Recommendation" value="E.164"/>
<seriesInfo name="ITU-T Recommendation" value="E.164"/> </reference>
</reference>
<reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/200
8/REC-xml-20081126/">
<front>
<title abbrev='Extensible Markup Language (XML) 1.0 (Fifth Edition) RE
C-xml-20081126'>Extensible Markup Language (XML) 1.0 (Fifth Edition) REC-xml-200
81126</title>
<author initials="T." surname="Bray" fullname="Tim Bray" />
<author initials="J." surname="Paoli" fullname="Jean Paoli" />
<author initials="C. M." surname="Sperberg-McQueen" fullname="C. M.
Sperberg-McQueen" />
<author initials="E." surname="Maler" fullname="Eve Maler" />
<author initials="F." surname="Yergeau" fullname="François Yergeau"
/>
<date year='2008' month='November' />
<keyword>W3C.xml</keyword>
</front>
</reference>
<reference anchor="W3C.REC-xmlschema-1-20041028" target="https://www.w3.or
g/TR/2004/REC-xmlschema-1-20041028/">
<front>
<title abbrev='XML Schema Part 1: Structures Second Edition REC-xmlsch
ema-1-20041028'>XML Schema Part 1: Structures Second Edition REC-xmlschema-1-200
41028</title>
<author initials="H. S." surname="Thompson" fullname="Henry S. Thompson
" />
<author initials="D." surname="Beech" fullname="David Beech" />
<author initials="M." surname="Maloney" fullname="Murray Maloney" /
>
<author initials="N." surname="Mendelsohn" fullname="Noah Mendelsoh
n" />
<date year='2004' month='October' />
<keyword>W3C.xmlschema-1</keyword>
</front>
</reference>
<reference anchor="W3C.REC-xmlschema-2-20041028" target="https://www.w3.or
g/TR/2004/REC-xmlschema-2-20041028/">
<front>
<title abbrev='XML Schema Part 2: Datatypes Second Edition REC-xmlsche
ma-2-20041028'>XML Schema Part 2: Datatypes Second Edition REC-xmlschema-2-20041
028</title>
<author initials="P. V." surname="Biron" fullname="Paul V. Biron" />
<author initials="A." surname="Malhotra" fullname="Ashok Malhotra"
/>
<date year='2004' month='October' />
<keyword>W3C.xmlschema-2</keyword>
</front>
</reference>
<reference anchor="W3C.REC-xpath-31-20170321" target="https://www.w3.org/T
R/2017/REC-xpath-31-20170321/">
<front>
<title abbrev='XML Path Language (XPath) 3.1'>XML Path Language (XPath
) 3.1</title>
<author initials="J. R." surname="Robie" fullname="Jonathan Robie" />
<author initials="M. D." surname="Dyck" fullname="Michael Dyck" />
<author initials="J. S." surname="Spiegel" fullname="Josh Spiegel"
/>
<date year='2017' month='March' />
<keyword>W3C.xpath-31</keyword>
</front>
</reference>
<reference anchor="V42" target="https://www.itu.int/rec/T-REC-V.42/en">
<front>
<title>V.42 : Error-correcting procedures for DCEs using asynchronous-
to-synchronous conversion</title>
<author>
<organization>International Telecommunication Union</organization>
</author>
<date month="March" year="2002" />
</front>
</reference>
</references> <reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2
008/REC-xml-20081126/">
<front>
<title>Extensible Markup Language (XML) 1.0 (Fifth Edition) REC-xml-
20081126</title>
<author initials="T." surname="Bray" fullname="Tim Bray"/>
<author initials="J." surname="Paoli" fullname="Jean Paoli"/>
<author initials="C. M." surname="Sperberg-McQueen" fullname="C. M.
Sperberg-McQueen"/>
<author initials="E." surname="Maler" fullname="Eve Maler"/>
<author initials="F." surname="Yergeau" fullname="François Yergeau"/
>
<date year="2008" month="November"/>
</front>
<seriesInfo name="W3C" value="Recommendation"/>
</reference>
<references title='Informative References'> <reference anchor="W3C.REC-xmlschema-1-20041028" target="https://www.w3.
&RFC1952; org/TR/2004/REC-xmlschema-1-20041028/">
&RFC2818; <front>
&RFC3688; <title>XML Schema Part 1: Structures Second Edition REC-xmlschema-1-
&RFC3912; 20041028</title>
&RFC4180; <author initials="H. S." surname="Thompson" fullname="Henry S. Thomp
&RFC7942; son"/>
<author initials="D." surname="Beech" fullname="David Beech"/>
<author initials="M." surname="Maloney" fullname="Murray Maloney"/>
<author initials="N." surname="Mendelsohn" fullname="Noah Mendelsohn
"/>
<date year="2004" month="October"/>
</front>
<seriesInfo name="W3C" value="Recommendation"/>
</reference>
<reference anchor="variantTLDsReport" <reference anchor="W3C.REC-xmlschema-2-20041028" target="https://www.w3.
target="http://www.icann.org/en/topics/idn/idn-vip-integrated-is org/TR/2004/REC-xmlschema-2-20041028/">
sues-final-clean-20feb12-en.pdf"> <front>
<front> <title>XML Schema Part 2: Datatypes Second Edition REC-xmlschema-2-2
<title>A Study of Issues Related to the Management of IDN Va 0041028</title>
riant TLDs</title> <author initials="P. V." surname="Biron" fullname="Paul V. Biron"/>
<author> <author initials="A." surname="Malhotra" fullname="Ashok Malhotra"/>
<organization abbrev="ICANN">Internet Corporation for As <date year="2004" month="October"/>
signed Names and Numbers (ICANN)</organization> </front>
</author> <seriesInfo name="W3C" value="Recommendation" />
<date day="20" month="February" year="2012"/> </reference>
</front>
</reference>
<reference anchor="ICANN-GTLD-RA-20170731" target="https://new <reference anchor="W3C.REC-xpath-31-20170321" target="https://www.w3.org
gtlds.icann.org/sites/default/files/agreements/agreement-approved-31jul17-en.pdf /TR/2017/REC-xpath-31-20170321/">
"> <front>
<front> <title>XML Path Language (XPath) 3.1</title>
<title>Base Registry Agreement 2017-07-31</title> <author initials="J." surname="Robie" fullname="Jonathan Robie"/>
<author> <author initials="M." surname="Dyck" fullname="Michael Dyck"/>
<organization>ICANN</organization> <author initials="J." surname="Spiegel" fullname="Josh Spiegel"/>
</author> <date year="2017" month="March"/>
<date day="31" month="July" year="2017" /> </front>
</front> <seriesInfo name="W3C" value="Recommendation"/>
</reference> </reference>
<reference anchor="ICANN-GTLD-AGB-20120604" target="http://new <reference anchor="V42" target="https://www.itu.int/rec/T-REC-V.42/en">
gtlds.icann.org/en/applicants/agb/guidebook-full-04jun12-en.pdf"> <front>
<front> <title>V.42 : Error-correcting procedures for DCEs using asynchronou
<title>gTLD Applicant Guidebook Version 2012-06-04</title> s-to-synchronous conversion</title>
<author> <author>
<organization>ICANN</organization> <organization>International Telecommunication Union</organization>
</author> </author>
<date day="4" month="June" year="2012" /> <date month="March" year="2002"/>
</front> </front>
</reference> <seriesInfo name="ITU-T Recommendation" value="V.42" />
</reference>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.1952.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.2818.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.3688.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.3912.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.4180.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.R
FC.6672.xml"/>
</references> <reference anchor="variantTLDsReport" target="https://www.icann.org/en/s
ystem/files/files/idn-vip-integrated-issues-final-clean-20feb12-en.pdf">
<front>
<title>A Study of Issues Related to the Management of IDN Variant TL
Ds</title>
<author>
<organization abbrev="ICANN">Internet Corporation for Assigned Nam
es and Numbers (ICANN)</organization>
</author>
<date day="20" month="February" year="2012"/>
</front>
</reference>
</back> <reference anchor="ICANN-GTLD-RA-20170731" target="https://newgtlds.ican
n.org/sites/default/files/agreements/agreement-approved-31jul17-en.pdf">
<front>
<title>Base Registry Agreement 2017-07-31</title>
<author>
<organization>ICANN</organization>
</author>
<date day="31" month="July" year="2017"/>
</front>
</reference>
<reference anchor="ICANN-GTLD-AGB-20120604" target="http://newgtlds.ican
n.org/en/applicants/agb/guidebook-full-04jun12-en.pdf">
<front>
<title>gTLD Applicant Guidebook Version 2012-06-04</title>
<author>
<organization>ICANN</organization>
</author>
<date day="4" month="June" year="2012"/>
</front>
</reference>
</references>
</references>
<section numbered="false" toc="default">
<name>Acknowledgments</name>
<t>
Parts of this document are based on EPP <xref target="RFC5730" f
ormat="default"/> and related RFCs by <contact fullname="Scott Hollenbeck"/>.
</t>
<t>
Special suggestions that have been incorporated into this docume
nt
were provided by <contact fullname="Edward Lewis"/>, <contact fu
llname="Jaap Akkerhuis"/>, <contact fullname="Lawrence Conroy"/>, <contact fulln
ame="Marc Groeneweg"/>,
<contact fullname="Michael Young"/>, <contact fullname="Chris Wr
ight"/>, <contact fullname="Patrick Mevzek"/>, <contact fullname="Stephen Morris
"/>, <contact fullname="Scott Hollenbeck"/>, <contact fullname="Stephane Bortzme
yer"/>,
<contact fullname="Warren Kumari"/>, <contact fullname="Paul Hof
fman"/>, <contact fullname="Vika Mpisane"/>, <contact fullname="Bernie Hoeneisen
"/>, <contact fullname="Jim Galvin"/>, <contact fullname="Andrew Sullivan"/>, <c
ontact fullname="Hiro Hotta"/>,
<contact fullname="Christopher Browne"/>, <contact fullname="Dan
iel Kalchev"/>, <contact fullname="David Conrad"/>, <contact fullname="James Mit
chell"/>, <contact fullname="Francisco Obispo"/>, <contact fullname="Bhadresh Mo
di"/>,
<contact fullname="Alexander Mayrhofer"/>, and <contact fullname
="Benjamin Kaduk"/>.
</t>
<t>
<contact fullname="Shoji Noguchi"/> and <contact fullname="Francis
co Arias"/> participated
as coauthors through version 05 of earlier drafts of this document
and provided invaluable support.
</t>
</section>
</back>
</rfc> </rfc>
 End of changes. 417 change blocks. 
5067 lines changed or deleted 4052 lines changed or added

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