<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?><!DOCTYPE rfc SYSTEM"rfc2629.dtd" [ <!-- 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" ?>"rfc2629-xhtml.ent"> <rfccategory="std"xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902"docName="draft-ietf-regext-dnrd-objects-mapping-11">docName="draft-ietf-regext-dnrd-objects-mapping-11" number="9022" obsoletes="" updates="" submissionType="IETF" category="std" consensus="true" xml:lang="en" tocInclude="true" tocDepth="2" symRefs="true" sortRefs="true" version="3"> <!-- xml2rfc v2v3 conversion 3.5.0 --> <front> <title abbrev="DNRD Objects Mapping"> Domain Name Registration Data (DNRD) Objects Mapping </title> <seriesInfo name="RFC" value="9022"/> <author initials="G." surname="Lozano" fullname="Gustavo Lozano"> <organization abbrev="ICANN"> Internet Corporation for Assigned Names and Numbers </organization> <address> <postal> <extaddr>Suite 300</extaddr> <street>12025 WaterfrontDrive, Suite 300</street>Drive</street> <city>Los Angeles</city> <region>CA</region> <code>90292</code> <country>United States of America</country><code>90292</code> <city>Los Angeles</city></postal> <phone>+1.310.823.9358</phone> <email>gustavo.lozano@icann.org</email> </address> </author> <author initials="J." surname="Gould" fullname="James Gould"> <organization abbrev="VeriSign"> VeriSign, Inc. </organization> <address> <postal> <street>12061 Bluemont Way</street> <city>Reston</city> <region>VA</region> <code>20190</code> <country>United States of America</country><code>20190</code> <city>Reston</city></postal> <email>jgould@verisign.com</email> </address> </author> <author initials="C." surname="Thippeswamy" fullname="Chethan Thippeswamy"> <organization abbrev="VeriSign"> VeriSign, Inc. </organization> <address> <postal> <street>12061 Bluemont Way</street> <city>Reston</city> <region>VA</region> <code>20190</code> <country>United States of America</country><code>20190</code> <city>Reston</city></postal> <email>cthippeswamy@verisign.com</email> </address> </author> <dateday="16" month="Dec" year="2020"/>month="May" year="2021"/> <area> Applications </area> <keyword>data escrow</keyword> <keyword>registry</keyword> <keyword>domain name</keyword> <keyword>domain name registration data</keyword> <abstract> <t> This document specifies the format,contentscontents, and semantics of Domain Name Registration Data (DNRD)Escrowescrow deposits for aDomain Name Registry.domain name registry. </t> </abstract> </front> <middle> <sectiontitle="Introduction">numbered="true" toc="default"> <name>Introduction</name> <t> Registry Data Escrow (RDE) is the process by which a registry periodically submits data deposits to athird-partythird party called an escrow agent. These deposits comprise the minimum data needed by athird-partythird party to resume operations if the registry cannot function and is unable or unwilling to facilitate an orderly transfer of service. For example, for a domain name registry or registrar, the data to be deposited would include all the objects related to registered domain names, e.g., names, contacts, name servers, etc. </t> <t> The goal of data escrow is higher resiliency of registrationservices,services for the benefit of Internet users. The beneficiaries of a registry are not just those registering information there, but also the users of services relying on the registry data. </t> <t> In the context of domain name registries, registration data escrow is a requirement for generic top-level domains (e.g., Specification 2 of the ICANN Base Registry Agreement, see <xreftarget='ICANN-GTLD-RA-20170731' />)target="ICANN-GTLD-RA-20170731" format="default"/>) and some country code top-level domain managers are also currently escrowing data. There is also a similar requirement for ICANN-accredited domain registrars. </t> <t> This document defines the standard set of objects for aDomain Name Registrydomain name registry that uses the Registry Data Escrow Specification described in <xreftarget="I-D.ietf-regext-data-escrow"/>target="RFC8909" format="default"/> for escrow. The set of objects include: </t><t> <list style="symbols"> <t> Domain: Internet<dl spacing="normal"> <dt> Domain:</dt><dd>Internet domain names that are typically provisioned in aDomain Name Registrydomain name registry using theEPPExtensible Provisioning Protocol (EPP) domain name mapping <xreftarget="RFC5731"/>.target="RFC5731" format="default"/>. The attributes defined in the EPP domain name mapping <xreftarget="RFC5731"/>target="RFC5731" format="default"/> are fully supported by this document.</t> <t> Host: Internet</dd> <dt> Host:</dt><dd>Internet host names that are typically provisioned in aDomain Name Registrydomain name registry using the EPP host mapping <xreftarget="RFC5732"/>.target="RFC5732" format="default"/>. The attributes defined in the EPP host mapping <xreftarget="RFC5732"/>target="RFC5732" format="default"/> are fully supported by this document.</t> <t> Contact: Individual</dd> <dt> Contact:</dt><dd>Individual or organization social information provisioned in aDomain Name Registrydomain name registry using the EPP contact mapping <xreftarget="RFC5733"/>.target="RFC5733" format="default"/>. The attributes defined in the EPP contact mapping <xreftarget="RFC5733"/>target="RFC5733" format="default"/> are fully supported by this document.</t> <t> Registrar: The</dd> <dt> Registrar:</dt><dd>The organization that sponsors objects like domains, hosts, and contacts in aDomain Name Registry. </t> <t>domain name registry. </dd> <dt> NNDN(NNDN's(NNDN's not domainname): Domainname):</dt><dd>Domain Name Registries may maintain domain names without being persisted as domain objects in the registry system, for example, a list of reserved names not available for registration. The NNDN is a lightweight domain-like object that is used to escrow domain names not maintained as domain name objects.</t> </list> </t></dd> </dl> <t> This document defines the following pseudo-objects: </t><t> <list style="symbols"> <t><dl spacing="normal"> <dt> IDNTable Reference: Internationalizedtable reference:</dt><dd>Internationalized Domain Names (IDN) included in theDomain Object Data Escrowdomain object data escrow include references to the IDNTabletable andPolicypolicy used in IDN registration.</t> <t></dd> <dt> EPPparameters: Containsparameters:</dt><dd>Contains the EPP parameters supported by theRegistry Operator. </t> <t> Header: Usedregistry operator. </dd> <dt> Header:</dt><dd>Used to specify counters of objects in the database at a certain point in time(watermark). </t> <t> Policy: Used(Timeline Watermark). </dd> <dt> Policy:</dt><dd>Used to specifyOPTIONAL<bcp14>OPTIONAL</bcp14> elements from this specification that areREQUIRED<bcp14>REQUIRED</bcp14> based on the business model of the registry.</t> </list> </t></dd> </dl> <t>Extensible Markup Language (XML) 1.0 as described in <xreftarget='W3C.REC-xml-20081126' />target="W3C.REC-xml-20081126" format="default"/> and XML Schema notation as described in <xreftarget='W3C.REC-xmlschema-1-20041028' />target="W3C.REC-xmlschema-1-20041028" format="default"/> and <xreftarget='W3C.REC-xmlschema-2-20041028' />target="W3C.REC-xmlschema-2-20041028" format="default"/> are used in this specification. </t> </section> <sectiontitle="Models" anchor="models">anchor="models" numbered="true" toc="default"> <name>Models</name> <t> This document defines two different models that can be used to deposit data escrow objects: XML andCSV.CSV (comma-separated values). </t> <t> The data escrow depositMAY<bcp14>MAY</bcp14> contain a mix of bothmodelsmodels, but an objectMUST<bcp14>MUST</bcp14> be escrowed only in one model. </t> <t> This document does not suggest the use of a particular model, and both are equivalent. ADomain Name Registrydomain name registry may choose the model that is more appropriate 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; therefore, the CSV model may be more appropriate. Another registry may use the code developed for EPP to implement escrow. </t> <sectiontitle="XML Model">numbered="true" toc="default"> <name>XML Model</name> <t>XML:The XML model includes all the deposit information(meta-data(metadata 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 using the XML model are referenced using RDE and an XML namespace that is prefixed with "rde". For example, the Domain Name object represented using the XML model can be referred to as the RDE Domain Name with the XML namespace including rdeDomain (urn:ietf:params:xml:ns:rdeDomain-1.0). </t> </section> <sectiontitle="CSV Model">numbered="true" toc="default"> <name>CSV Model</name> <t>CSV:The CSV model uses XML to define the data escrow format of the data contained in referencedComma-Separated Values (CSV)CSV files. As a convention, the objects represented using the CSV model is referenced using CSV and an XML namespace that is prefixed with "csv". For example, theDomain Namedomain name object represented using the CSV model can be referred to as the CSV Domain Name with the XML namespace including csvDomain (urn:ietf:params:xml:ns:csvDomain-1.0). </t> </section> </section> <sectiontitle="Terminology">numbered="true" toc="default"> <name>Terminology</name> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</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"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 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">numbered="true" toc="default"> <name>Glossary</name> <t> In the following section, the most common terms are briefly explained:<list style='symbols'> <t> Allocated: a</t> <dl spacing="normal"> <dt> Allocated:</dt><dd>A status of some label with respect to a zone, whereby the label is associated administratively to some entity that has requested the label. This term (and its cognates“allocation”"allocation" and“to allocate”)"to allocate") may represent the first step on the way to delegation in the DNS.</t> <t></dd> <dt> Comma-Separated Values(CSV), see(CSV): </dt><dd> See <xreftarget='RFC4180' />. </t> <t>target="RFC4180" format="default"/>. </dd> <dt> Domainname: seeName:</dt><dd>See the definition of DomainnameName in <xreftarget='RFC8499' />. </t> <t>target="RFC8499" section="2" sectionFormat="of" format="default"/>. </dd> <dt> Extensible Provisioning Protocol(EPP), see(EPP): </dt><dd>See the definition of the Extensible Provisioning Protocol in <xreftarget='RFC8499' />. </t> <t>target="RFC8499" section="9" sectionFormat="of" format="default"/>. </dd> <dt> Fully-Qualified Domain Name(FQDN), see(FQDN): </dt><dd>See the definition of FQDN in <xreftarget='RFC8499' />. </t> <t>target="RFC8499" section="2" sectionFormat="of" format="default"/>. </dd> <dt> Internationalized Domain Name(IDN), see(IDN): </dt><dd>See the definition of Internationalized Domain Name in <xreftarget='RFC8499' />. </t> <t> Label: seetarget="RFC8499" section="2" sectionFormat="of" format="default"/>. </dd> <dt> Label</dt><dd>See the definition of Label in <xreftarget='RFC8499' />. </t> <t> Registrant: seetarget="RFC8499" section="2" sectionFormat="of" format="default"/>. </dd> <dt> Registrant:</dt><dd>See the definition of Registrant in <xreftarget='RFC8499' />. </t> <t> Registrar: seetarget="RFC8499" section="9" sectionFormat="of" format="default"/>. </dd> <dt> Registrar:</dt><dd>See the definition of Registrar in <xreftarget='RFC8499' />. </t> <t> Registry: seetarget="RFC8499" section="9" sectionFormat="of" format="default"/>. </dd> <dt> Registry:</dt><dd>See the definition of Registry in <xreftarget='RFC8499' />. </t> <t> Registry-class domain name (RCDN): referstarget="RFC8499" section="9" sectionFormat="of" format="default"/>. </dd> <dt> Registry-Class Domain Name (RCDN):</dt><dd>Refers to a top-level domain (TLD) or any other domain name at any level in the DNS tree for which aRegistryregistry (either directly or through an affiliate company) provides Registry Services for other organizations or individuals. For example: .COM, .ORG, .BIZ, .CO.JP, .B.BR.</t> <t></dd> <dt> Registry Data Escrow(RDE): registry data escrow(RDE):</dt><dd>Registry Data Escrow is the process by which a registry periodically submits data deposits to athird-partythird party called an escrow agent. These deposits comprise the minimum data needed by athird-partythird party to resume operations if the registry cannot function and is unable or unwilling to facilitate an orderly transfer of service.</t> <t></dd> <dt> Registryservices: servicesServices:</dt><dd>Services offered by theRegistryregistry critical to the following tasks: the provisioning of domain names on receipt of requests and data from registrars; responding to registrar queries for status information relating to the DNS servers for the RCDN; dissemination of RCDN zone files; operation of theRegistryregistry DNS servers; responding to queries for contact and other information concerning DNS registrations in the RCDN; and any other products or services that only aRegistryregistry is capable of providing, by reason of its designation as theRegistry.registry. Typical examples of Registry Services are DNS resolution for the RCDN,WHOISWHOIS, and EPP.</t> <t> SRS: Shared</dd> <dt> SRS:</dt><dd>Shared Registration System, see also <xreftarget='ICANN-GTLD-AGB-20120604' />. </t> <t>target="ICANN-GTLD-AGB-20120604" format="default"/>. </dd> <dt> Top-Level Domain Name(TLD), see(TLD): </dt><dd>See the definition of Top-Level Domain in <xreftarget='RFC8499' />. </t> <t> UTC: Coordinatedtarget="RFC8499" section="2" sectionFormat="of" format="default"/>. </dd> <dt> UTC:</dt><dd>Coordinated Universal Time, as maintained by the Bureau International des Poids et Mesures(BIPM);(BIPM), see also <xreftarget='RFC3339' />. </t> </list> </t>target="RFC3339" format="default"/>. </dd> </dl> </section> </section> <sectiontitle="Conventionsnumbered="true" toc="default"> <name>Conventions Used in ThisDocument">Document</name> <sectiontitle="Datenumbered="true" toc="default"> <name>Date andTime">Time</name> <t> Numerous fields indicate "dates", such as the creation and expiry dates for domain names. These fieldsSHALL<bcp14>SHALL</bcp14> contain timestamps indicating the date and time in UTC as specified in <xreftarget="RFC3339"/>,target="RFC3339" format="default"/>, with no offset from the zero meridian. </t> </section> <sectiontitle="Country names">numbered="true" toc="default"> <name>Country Names</name> <t> Country identifiersSHALL<bcp14>SHALL</bcp14> be represented using two character identifiers as specified in <xreftarget="ISO-3166-1"/>.target="ISO-3166-1" format="default"/>. </t> </section> <sectiontitle="Telephone numbers">numbered="true" toc="default"> <name>Telephone Numbers</name> <t> Telephone numbers (both voice and facsimile)SHALL<bcp14>SHALL</bcp14> be formatted based on structures defined in <xreftarget="ITU-E164"/>.target="ITU-E164" format="default"/>. Telephone numbers described in this specification are character strings thatMUST<bcp14>MUST</bcp14> begin with a plus sign ("+", ASCII value 0x2B), followed by a country code defined in <xreftarget="ITU-E164"/>,target="ITU-E164" format="default"/>, followed by a dot (".", ASCII value 0x2E), followed by a sequence of digits representing the telephone number. </t> </section> <sectiontitle="CSVanchor="checksum" numbered="true" toc="default"> <name>CSV IntegrityCheck" anchor="checksum">Check</name> <t> A checksumMAY<bcp14>MAY</bcp14> be used to verify the integrity of the CSV files, for example, if another layer (i.e., encryption of an archive containing the deposit files) does not provide integrity. Bydefaultdefault, the CRC32 algorithm(see,(see Section 8.1.1.6.2 of <xreftarget="V42"/>)target="V42" format="default"/>) is used. A stronger algorithm, such as SHA-256(see,(see <xreftarget="RFC6234"/>) MAYtarget="RFC6234" format="default"/>) <bcp14>MAY</bcp14> be used for enhanced security if required. </t> </section> <sectiontitle="IP addresses">numbered="true" toc="default"> <name>IP Addresses</name> <t> The syntax of IP addressesMUST<bcp14>MUST</bcp14> conform to the text representation of either Internet Protocol Version 4 <xreftarget="RFC0791"/>target="RFC0791" format="default"/> or Internet Protocol Version 6 <xreftarget="RFC5952"/>.target="RFC5952" format="default"/>. </t> </section> <sectiontitle="Conventions applicablenumbered="true" toc="default"> <name>Conventions Applicable to the CSVModel">Model</name> <sectiontitle="CSVanchor="csvParentChildRelationship" numbered="true" toc="default"> <name>CSV Parent ChildRelationship" anchor="csvParentChildRelationship">Relationship</name> <t> The CSV model represents a relationalmodel,model where the CSV files represent 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 foreign keys in the child CSV file definitions for a1-to-manyone-to-many relationship. The primary keys are not explicitly defined, but the foreign keys are using the boolean "parent" field attribute in the child CSV file. The relationships 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 (see <xreftarget="I-D.ietf-regext-data-escrow"/>).target="RFC8909" format="default"/>). </t><t> <figure> <preamble><t keepWithNext="true"> The following is an example of the CSV file definitions, using the element <rdeCsv:csv> (see <xreftarget="rdeCsv-csv"/>),target="rdeCsv-csv" format="default"/>), for a Sample object consisting of a parent "sample" CSV File Definition and a child "sampleStatuses" CSV File Definition. The primary key for the Sample object is the field <csvSample:fName> that is used as the foreign key in the "sampleStatuses" CSV File Definition by specifying the "parent=true" attribute. If a Sample record is updated or deleted in a Differential or Incremental 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, respectively.</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ <csvSample:contents> ... <rdeCsv:csv name="sample" sep=","> <rdeCsv:fields> <csvSample:fName/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fExDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="75E2D22F"> sample-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="sampleStatuses" sep=","> <rdeCsv:fields> <csvSample:fName parent="true"/> <csvSample:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="EB9C558E"> sampleStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ...</csvSample:contents>]]> </artwork> </figure> </t></csvSample:contents> ]]></sourcecode> </section> <sectiontitle="CSV elements" anchor="csvElements"> <section title="<rdeCsv:csv> element" anchor="rdeCsv-csv">anchor="csvElements" numbered="true" toc="default"> <name>CSV Elements</name> <section anchor="rdeCsv-csv" numbered="true" toc="default"> <name><rdeCsv:csv> Element</name> <t> To support the CSV model, an element is defined for each object that substitutes for the <rde:content> element and for the <rde:delete> element, that contains one or more <rdeCsv:csv> elements. For example, the <xreftarget="domainNameObject">Domaintarget="domainNameObject" format="default">'Domain NameObject</xref>Object'</xref> defines the <csvDomain:contents> element, that substitutes for the <rde:content> element, and the <csvDomain:deletes> element, that substitutes for the <rde:delete> element. Both the <csvDomain:contents> element and the <csvDomain:deletes> elements contain one or more <rdeCsv:csv> elements. The <rdeCsv:csv> element has the following child elements:</t><t><list style="hanging"> <t hangText="<rdeCsv:fields>">Ordered<dl newline="false" spacing="normal"> <dt><rdeCsv:fields></dt> <dd>Ordered list of CSV fields used in the CSV files. There are one or more child elements that substitute for the <rdeCsv:field> abstract element. Each element defines the format of the CSV field contained in the CSV files. The <rdeCsv:field> elements support the "type" attribute that defines the XML simple data type of the field element. The <rdeCsv:field> elements support the "isRequired" attribute,withwhich has a default value of"false", when"false". When set to"true""true", this indicates that the field must be non-empty in the CSVfilesfiles, and when set to"false""false", this indicates that the fieldMAY<bcp14>MAY</bcp14> be empty in the CSV files. The "isRequired" attributeMAY<bcp14>MAY</bcp14> be specifically set for the field elements within the XML schema andMAY<bcp14>MAY</bcp14> be overridden when specifying the fields under the <rdeCsv:fields> element. The <rdeCsv:field> element supports anOPTIONAL<bcp14>OPTIONAL</bcp14> "parent" attribute that identifies the field as a reference to a parent object, as defined in the <xreftarget="csvParentChildRelationship">CSVtarget="csvParentChildRelationship" format="default">'CSV Parent ChildRelationship</xref>.Relationship'</xref>. For example, the <rdeCsv:csv name="domainStatuses"> <csvDomain:fName> fieldSHOULD<bcp14>SHOULD</bcp14> set the "parent" attribute to "true" to identify it as the parent domain name of the domainstatus.</t> <t hangText="<rdeCsv:files>">Astatus.</dd> <dt><rdeCsv:files></dt> <dd><t>A list of one or more CSV files using the <rdeCsv:file> child element. The <rdeCsv:file> child element defines a reference to the CSV file name and has the following optional attributes:</t><t><list style="hanging"> <t hangText="compression">If<dl newline="false" spacing="normal"> <dt>compression</dt> <dd>If the CSV file is compressed, the "compression" attribute defines the compression format. For example, setting this attribute to "gzip" signals that the CSV file is compressed using the GZIP file format(see,(see <xreftarget="RFC1952"/>).target="RFC1952" format="default"/>). The supported compression formats are negotiatedout-of-band. </t> <t hangText="encoding">Definesout of band. </dd> <dt>encoding</dt> <dd>Defines the encoding of the CSV file with the default encoding of "UTF-8".</t> <t hangText="cksum">Defines</dd> <dt>cksum</dt> <dd>Defines the checksum of the CSV file, as described in <xreftarget="checksum"/>,target="checksum" format="default"/>, using the algorithm defined by the "cksumAlg" attribute. If the "cksumAlg" attribute is not present, the checksum is calculated using "CRC32".</t> <t hangText="cksumAlg">Defines</dd> <dt>cksumAlg</dt> <dd>Defines the checksum algorithm used to calculate the "cksum" attribute, with the default value of "CRC32". If the value "SHA256" is specified, the SHA-256 algorithm(see,(see <xreftarget="RFC6234"/>) MUSTtarget="RFC6234" format="default"/>) <bcp14>MUST</bcp14> be used to calculate the "cksum" attribute. Parties receiving and processing data escrow depositsMUST<bcp14>MUST</bcp14> support CRC32 and SHA-256. If this attribute is present, the "cksum" attributeMUST<bcp14>MUST</bcp14> also be present. Additional checksum algorithms are negotiatedout-of-band. </t> </list></t> </list></t>out of band. </dd> </dl> </dd> </dl> <t>The <rdeCsv:csv> element requires a "name" attribute that defines the purpose of the CSV file with values like "domain", "host", "contact". The supported "name" attribute values are defined for each object type. TheOPTIONAL<bcp14>OPTIONAL</bcp14> "sep" attribute defines the CSV separator character with the default separator character of ",". The need forquoting/escapingquoting or escaping of the CSV data could be avoided by choosing a separator character that is not in the data set of the CSV files. </t><t> <figure> <preamble><t keepWithNext="true"> The following is an example of the <csvDomain:contents> <rdeCsv:csv> element for domain name records where the <rdeCsv:fRegistrant> is set as required with isRequired="true".</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ <csvDomain:contents> ... <rdeCsv:csv name="domain" sep=","> <rdeCsv:fields> <csvDomain:fName/> <rdeCsv:fRoid/> <rdeCsv:fIdnTableId/> <csvDomain:fOriginalName/> <rdeCsv:fRegistrant isRequired="true"/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fExDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="75E2D01F"> domain-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ...</csvDomain:contents>]]> </artwork> </figure> </t> <t> <figure> <preamble></csvDomain:contents> ]]></sourcecode> <t keepWithNext="true"> The following is an example of the"domain-YYYYMMDD.csv"domain-YYYYMMDD.csv file with one record matching the <rdeCsv:fields> definition.</preamble> <artwork><![CDATA[</t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z]]> </artwork> </figure> </t> <t> <figure> <preamble>2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z ]]></artwork> <t keepWithNext="true"> The following is an example of the <csvDomain:deletes> <rdeCsv:csv> element for domain name records.</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ <csvDomain:deletes> ... <rdeCsv:csv name="domain"> <rdeCsv:fields> <csvDomain:fName/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="6F2B988F"> domain-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ...</csvDomain:deletes>]]> </artwork> </figure> </t> <t> <figure> <preamble></csvDomain:deletes> ]]></sourcecode> <t keepWithNext="true"> The following is example of the"domain-delete-YYYYMMDD.csv"domain-delete-YYYYMMDD.csv file with three records that matches the single <csvDomain:fName> field.</preamble> <artwork><![CDATA[</t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example domain2.exampledomainN.example]]> </artwork> </figure> </t>domainN.example ]]></artwork> </section> <sectiontitle="CSV common field elements" anchor="csvCommonFieldElements">anchor="csvCommonFieldElements" numbered="true" toc="default"> <name>CSV Common Field Elements</name> <t>The <rdeCsv:fields> element defined in the <xreftarget="rdeCsv-csv"><rdeCsv:csv> element</xref> sectiontarget="rdeCsv-csv" format="default">'<rdeCsv:csv> Element'</xref> has child elements that substitute for the abstract <rdeCsv:field> element. Byconventionconvention, <rdeCsv:field> elements include an'f'"f" prefix to identify them as field definition elements. There are a set of common field elements that are used across multiple data escrow objects. The common field elements are defined using the "urn:ietf:params:xml:ns:rdeCsv-1.0" namespace and using the "rdeCsv" sample namespace prefix. The CSV common field elements include: </t><t><list style="hanging"> <t hangText="<rdeCsv:fUName>">UTF-8<dl newline="false" spacing="normal"> <dt><rdeCsv:fUName></dt> <dd>UTF-8 encoded name field with type="eppcom:labelType".</t> <t hangText="<rdeCsv:fRoid>">Repository</dd> <dt><rdeCsv:fRoid></dt> <dd>Repository Object IDentifier (ROID) field with type="eppcom:roidType" and isRequired="true".</t> <t hangText="<rdeCsv:fRegistrant>">Registrant</dd> <dt><rdeCsv:fRegistrant></dt> <dd>Registrant contact identifier with type="eppcom:clIDType".</t> <t hangText="<rdeCsv:fStatusDescription>">The</dd> <dt><rdeCsv:fStatusDescription></dt> <dd>The object status description, which isfree formfree-form text describing the rationale for the status, with type="normalizedString".</t> <t hangText="<rdeCsv:fClID>">Identifier</dd> <dt><rdeCsv:fClID></dt> <dd>Identifier of the client (registrar) that sponsors the object with type="eppcom:clIDType" and isRequired="true".</t> <t hangText="<rdeCsv:fCrRr>">Identifier</dd> <dt><rdeCsv:fCrRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that created the object with type="eppcom:clIDType".</t> <t hangText="<rdeCsv:fCrID>">Identifier</dd> <dt><rdeCsv:fCrID></dt> <dd>Identifier of the client that created the object with type="eppcom:clIDType".</t> <t hangText="<rdeCsv:fUpRr>">Identifier</dd> <dt><rdeCsv:fUpRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that last updated the object with type="eppcom:clIDType".</t> <t hangText="<rdeCsv:fUpID>">Identifier</dd> <dt><rdeCsv:fUpID></dt> <dd>Identifier of the client that last updated the object with type="eppcom:clIDType".</t> <t hangText="<rdeCsv:fReRr>">Identifier</dd> <dt><rdeCsv:fReRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that requested the transfer with type="eppcom:clIDType" and isRequired="true".</t> <t hangText="<rdeCsv:fReID>">Identifier</dd> <dt><rdeCsv:fReID></dt> <dd>Identifier of the client that requested the transfer with type="eppcom:clIDType".</t> <t hangText="<rdeCsv:fAcRr>">Identifier</dd> <dt><rdeCsv:fAcRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that should take or took action with type="eppcom:clIDType" and isRequired="true".</t> <t hangText="<rdeCsv:fAcID>">Identifier</dd> <dt><rdeCsv:fAcID></dt> <dd>Identifier of the client that should take or took action for transfer with type="eppcom:clIDType".</t> <t hangText="<rdeCsv:fCrDate>">Created</dd> <dt><rdeCsv:fCrDate></dt> <dd>Created date of object with type="dateTime".</t> <t hangText="<rdeCsv:fUpDate>">Updated</dd> <dt><rdeCsv:fUpDate></dt> <dd>Updated date of object with type="dateTime".</t> <t hangText="<rdeCsv:fExDate>">Expiration</dd> <dt><rdeCsv:fExDate></dt> <dd>Expiration date of object with type="dateTime".</t> <t hangText="<rdeCsv:fReDate>">Date</dd> <dt><rdeCsv:fReDate></dt> <dd>Date that transfer was requested with type="dateTime" and isRequired="true".</t> <t hangText="<rdeCsv:fAcDate>">Date</dd> <dt><rdeCsv:fAcDate></dt> <dd>Date that transfer action should be taken or has been taken with type="dateTime" and isRequired="true".</t> <t hangText="<rdeCsv:fTrDate>">Date</dd> <dt><rdeCsv:fTrDate></dt> <dd>Date of last transfer with type="dateTime".</t> <t hangText="<rdeCsv:fTrStatus>">State</dd> <dt><rdeCsv:fTrStatus></dt> <dd>State of the most recent transfer request with type="eppcom:trStatusType" and isRequired="true".</t> <t hangText="<rdeCsv:fTokenType>">General</dd> <dt><rdeCsv:fTokenType></dt> <dd>General token field with type="token".</t> <t hangText="<rdeCsv:fLang>">General</dd> <dt><rdeCsv:fLang></dt> <dd>General language field with type="language".</t> <t hangText="<rdeCsv:fIdnTableId>">IDN Table Identifier</dd> <dt><rdeCsv:fIdnTableId></dt> <dd>IDN table identifier used for IDN domain names with type="token".</t> <t hangText="<rdeCsv:fPositiveIntegerType>">General</dd> <dt><rdeCsv:fPositiveIntegerType></dt> <dd>General positive integer field with type="positiveInteger".</t> <t hangText="<rdeCsv:fUrl>">Contains</dd> <dt><rdeCsv:fUrl></dt> <dd>Contains the URL of an object like a registrar object with type="anyURI".</t> <t hangText="<rdeCsv:fCustom>">Custom</dd> <dt><rdeCsv:fCustom></dt> <dd>Custom field with name attribute that defines the custom fieldname"name with type="token".</t> </list></t></dd> </dl> </section> </section> <sectiontitle="Internationalizedanchor="intandloc" numbered="true" toc="default"> <name>Internationalized and LocalizedElements" anchor="intandloc">Elements</name> <t> Some elementsMAY<bcp14>MAY</bcp14> be provided in either internationalized form ("int") or localized form ("loc"). Those elements use a field value or "isLoc" attribute to specify the form used. If an "isLoc" attribute is used, a value of "true" indicates the use of the localizedformform, and a value of "false" indicates the use of the internationalized form. ThisMAY<bcp14>MAY</bcp14> override the form specified for a parent element. A value of "int" is used to indicate the internationalizedformform, and a value of "loc" is used to indicate the localized form. When the internalized form ("int") is provided, the field valueMUST<bcp14>MUST</bcp14> be represented in a subset of UTF-8 that can be represented in the 7-bit US-ASCII character set. When the localized form ("loc") is provided, the field valueMAY<bcp14>MAY</bcp14> be represented in unrestricted UTF-8. </t><t> <figure> <preamble><t keepWithNext="true"> The field elements below of the "registrar"<rdeCsv:csv"><rdeCsv:csv> <rdeCsv:fields> element specify the internationalized form with the isLoc="false" attribute.</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ ... <csvRegistrar:contents> ... <rdeCsv:csv name="registrar" sep=","> <rdeCsv:fields> <csvRegistrar:fId/> <rdeCsv:fRoid/> <csvRegistrar:fName isLoc="false"/> <csvRegistrar:fGurid/> <csvRegistrar:fStatus/> <csvContact:fStreet isLoc="false" index="0"/> <csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="2"/> <csvContact:fCity isLoc="false" /> <csvContact:fSp isLoc="false" /> <csvContact:fPc isLoc="false" /> <csvContact:fCc isLoc="false" /> <csvContact:fVoice/> <csvContact:fVoiceExt/> <csvContact:fFax/> <csvContact:fFaxExt/> <csvContact:fEmail isRequired="false"/> <rdeCsv:fUrl/> <csvRegistrar:fWhoisUrl/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="306178BB"> registrar-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvRegistrar:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble>... ]]></sourcecode> <t keepWithNext="true"> The following is an example of using the <csvContact:fPostalType> field value to define the internationalized or localized form of the remainder of the "contactPostal" field values.</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ ... <csvContact:contents> ... <rdeCsv:csv name="contactPostal"> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fPostalType/> <csvContact:fName/> <csvContact:fOrg/> <csvContact:fStreet index="0"/> <csvContact:fStreet index="1"/> <csvContact:fStreet index="2"/> <csvContact:fCity/> <csvContact:fSp/> <csvContact:fPc/> <csvContact:fCc/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="02CC2504"> contactPostal-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvContact:contents>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> </section> <sectiontitle="Object Description" anchor="Object_Description">anchor="Object_Description" numbered="true" toc="default"> <name>Object Description</name> <t> This section describes the base objects supported by this specification: </t> <sectiontitle="Domainanchor="domainNameObject" numbered="true" toc="default"> <name>Domain NameObject" anchor="domainNameObject">Object</name> <t> The domain name object is based on the EPP domain name mapping specified in <xreftarget="RFC5731"/>.target="RFC5731" format="default"/>. The domain name object supports both the XMLModelmodel and the CSVModel,model, defined inthe<xreftarget="models">Models</xref> section.target="models" format="default">'Models'</xref>. The elements used for both models are defined in the following sections. </t> <sectiontitle="XML Model" anchor="domainXmlModel">anchor="domainXmlModel" numbered="true" toc="default"> <name>XML Model</name> <t>There are two elements used in the data escrow of the domain name objects for the XMLmodelmodel, including the<rdeDomain:domain>,<rdeDomain:domain> element, under the <rde:contents> element, and the <rdeDomain:delete> element, under the <rde:deletes> element. </t> <sectiontitle="<rdeDomain:domain> object" anchor="rdeDomainElement">anchor="rdeDomainElement" numbered="true" toc="default"> <name><rdeDomain:domain> Object</name> <t> The domain element is based on the EPP domain <info> response for an authorized client (seeSection 3.1.2. of<xreftarget="RFC5731"/>)target="RFC5731" section="3.1.2" sectionFormat="of" format="default"/>) with additional data from an EPP <transfer>Query Response,query response, seeSection 3.1.3. of<xreftarget="RFC5731"/>,target="RFC5731" section="3.1.3" sectionFormat="of" format="default"/>, Registry Grace Period (RGP) status from <xreftarget="RFC3915"/>,target="RFC3915" format="default"/>, and data from the EPP<secDns:create><secDNS:create> command, seeSection 5.2.1. of<xreftarget="RFC5910"/>.target="RFC5910" section="5.2.1" sectionFormat="of" format="default"/>. </t> <t> A <domain> element substitutes for the <abstractDomain> abstract element todefinecreate a concrete definition of a domain. The <abstractDomain> element can be replaced by other domain definitions using the XML schema substitution groups feature. </t> <t> The <domain> element contains the following child elements: </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> A <name> element that contains thefully-qualifiedfully qualified name of the domain name object. ForIDNsIDNs, theA-LabelA-label is used (see <xreftarget="RFC5891"/>, Section 4.4). </t> <t>target="RFC5891" section="4.4" sectionFormat="comma" format="default"/>). </li> <li> A <roid> element that contains therepository object identifierROID assigned to the domain name object when it was created.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <uName> element that contains thefully-qualified domain nameFQDN in the Unicode character set. ItMUST<bcp14>MUST</bcp14> be provided if available.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <idnTableId> element that references the IDNTabletable used for the IDN. This corresponds to the"id""id" attribute of the <idnTableRef> element. This elementMUST<bcp14>MUST</bcp14> be present if the domain name is an IDN.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <originalName> element is used to indicate that the domain name is an IDN variant. This element contains the domain name used to generate the IDN variant.</t> <t></li> <li> One or more <status> elements that contain the current status descriptors associated with the domain name.</t> <t></li> <li> Zero or moreOPTIONAL<bcp14>OPTIONAL</bcp14> <rgpStatus> elements to represent "pendingDelete" sub-statuses, including "redemptionPeriod", "pendingRestore", and "pendingDelete", that a domain name can be in as a result of grace period processing as specified in <xreftarget="RFC3915"/>. </t> <t>target="RFC3915" format="default"/>. </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <registrant> element that contains the identifier for the human or the organizational social information object associatedaswith the holder of the domain name object.</t> <t></li> <li> Zero or moreOPTIONAL<bcp14>OPTIONAL</bcp14> <contact> elements that contain identifiers for the human or organizational social information objects associated with the domain name object.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <ns> element that contains thefully-qualifiedfully qualified names of the delegated host objects or host attributes (name servers) associated with the domain name object. SeeSection 1.1 of<xreftarget="RFC5731"/>target="RFC5731" section="1.1" sectionFormat="of" format="default"/> for a description of the elements used to specify host objects or host attributes.</t> <t></li> <li> A <clID> element that contains the identifier of the sponsoring registrar.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crRr> element that contains the identifier of the registrar that created the domain name object. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crDate> element that contains the date and time of the domain name object creation. This elementMUST<bcp14>MUST</bcp14> be present if the domain name has been allocated.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <exDate> element that contains the date and time identifying the end (expiration) of the domain name object's registration period. This elementMUST<bcp14>MUST</bcp14> be present if the domain name has been allocated.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <upRr> element that contains the identifier of the registrar that last updated the domain name object. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the domain has never been modified. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <upDate> element that contains the date and time of the most recentdomain-name-object modification.modification of the domain name object. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the domain name object has never been modified.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <secDNS> element that contains the public key information associated with Domain Name System security (DNSSEC) extensions for the domain name as specified in <xreftarget="RFC5910"/>. </t> <t>target="RFC5910" format="default"/>. </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <trDate> element that contains the date and time of the most recent successful transfer of a domain nameobject successful transfer.object. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the domain name object has never been transferred.</t></li> <li> <t> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <trnData> element that contains the following child elements related to the last transfer request of the domain name object. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if a transfer request for the domain name has never been created.<list style="symbols"> <t></t> <ul spacing="normal"> <li> A <trStatus> element that contains the state of the most recent transfer request.</t> <t></li> <li> A <reRr> element that contains the identifier of the registrar that requested the domain name object transfer. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> A <reDate> element that contains the date and time that the transfer was requested.</t> <t></li> <li> An <acRr> element that contains the identifier of the registrar that should act upon aPENDINGpending transfer request. For all other status types, the value identifies the registrar that took the indicated action. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> An <acDate> element that contains the date and time of a required or completed response. For aPENDINGpending request, the value identifies the date and time by which a response is required before an automated response action will be taken by the registry. For all other status types, the value identifies the date and time when the request was completed.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <exDate> element that contains the end of the domain name object's validity period (expiry date) if the transfer caused or causes a change in the validity period.</t> </list> </t> </list> </t> <t> <figure> <preamble> Example of a</li> </ul> </li> </ul> <t keepWithNext="true"> The following is an example of a domain name object:</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ ... <rdeDomain:domain> <rdeDomain:name>xn--exampl-gva.example</rdeDomain:name> <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid> <rdeDomain:idnTableId>pt-BR</rdeDomain:idnTableId> <rdeDomain:originalName>example.example</rdeDomain:originalName> <rdeDomain:status s="ok"/> <rdeDomain:registrant>jd1234</rdeDomain:registrant> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact> <rdeDomain:ns> <domain:hostObj>ns1.example.com</domain:hostObj> <domain:hostObj>ns1.example1.example</domain:hostObj> </rdeDomain:ns> <rdeDomain:clID>RegistrarX</rdeDomain:clID> <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate> <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate> </rdeDomain:domain>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> <sectiontitle="<rdeDomain:delete> object" anchor="rdeDomainDeleteElement">anchor="rdeDomainDeleteElement" numbered="true" toc="default"> <name><rdeDomain:delete> Object</name> <t> The <rdeDomain:delete> element contains thefully-qualified domain nameFQDN that was deleted and purged. </t><t> <figure> <preamble> Example<t keepWithNext="true"> The following is an example of an <rdeDomain:delete> object:</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ ... <rde:deletes> ... <rdeDomain:delete> <rdeDomain:name>foo.example</rdeDomain:name> <rdeDomain:name>bar.example</rdeDomain:name> </rdeDomain:delete> ... </rde:deletes>...]]> </artwork></figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="CSV Model" anchor="domainCsvModel">anchor="domainCsvModel" numbered="true" toc="default"> <name>CSV Model</name> <t>For the CSVModelmodel of the domain name object, the <csvDomain:contents> child element of the <rde:contents> element is used to hold the new or updated domain name objects for the deposit. The <csvDomain:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged domain name objects for the deposit. Both the <csvDomain:contents> and <csvDomain:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute. </t> <t> Differential and Incremental Deposits are based on changes to the domain name objects. The updated domain name object data under the <csvDomain:contents> element is a cascade replace down all of the domain name CSV files starting with the parent <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>.Definition'</xref>. The child CSV file definitions include a <csvDomain:fName parent="true"> field. All the child CSV file definition data for the domain name objects in the parent <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref> MUSTDefinition'</xref> <bcp14>MUST</bcp14> first be deleted and then set using the data in the child CSV files. The deleted domain name object data under the <csvDomain:deletes> element is a cascade delete starting from the <xreftarget="csvDomainDeletesDefinition">"domain"target="csvDomainDeletesDefinition" format="default">'"domain" Deletes CSV FileDefinition</xref>.Definition'</xref>. </t> <sectiontitle="<csvDomain:contents>" anchor="csvDomainContents">anchor="csvDomainContents" numbered="true" toc="default"> <name><csvDomain:contents></name> <t>The <csvDomain:contents> is used to hold the new or updated domain name object information for the deposit. The <csvDomain:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported domain name CSV filedefinitions:definitions. </t> <sectiontitle=""domain"anchor="csvDomainDefinition" numbered="true" toc="default"> <name>"domain" CSV FileDefinition" anchor="csvDomainDefinition">Definition</name> <t>The "domain" CSV File Definition defines the fields and CSV file references used for the parent domain name object records. All the other domain name CSV file definitions are child CSV files based on the inclusion of the <csvDomain:fName parent="true"> field.</t> <t>The following "csvDomain" field elementsMUST<bcp14>MUST</bcp14> be used in the "domain" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">Domain<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>Domain name field with type="eppcom:labelType" and isRequired="true".</t> </list></t></dd> </dl> <t>The following "csvDomain" field elementsMAY<bcp14>MAY</bcp14> be used in the "domain" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fOriginalName>">Fully-qualified<dl newline="false" spacing="normal"> <dt><csvDomain:fOriginalName></dt> <dd>Fully qualified name of the original IDN domain name object related to the variant domain name object with type="eppcom:labelType".</t> </list></t></dd> </dl> <t>The following "rdeCsv" and "csvRegistrar" fields,MUST<bcp14>MUST</bcp14> be used in the "domain" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fRoid>">Registry Object IDentifier (ROID)<dl newline="false" spacing="normal"> <dt><rdeCsv:fRoid></dt> <dd>ROID for the domain name object withisRequired="true".</t> <t hangText="<rdeCsv:fClID>isRequired="true".</dd> <dt><rdeCsv:fClID> or<csvRegistrar:fGurid>">A<csvRegistrar:fGurid></dt> <dd> <t>A choiceof: <list style="hanging"> <t hangText="<rdeCsv:fClID>">Identifierof the following: </t> <dl newline="false" spacing="normal"> <dt><rdeCsv:fClID></dt> <dd>Identifier of the sponsoring client with isRequired="true".</t> <t hangText="<csvRegistrar:fGurid>">Contains</dd> <dt><csvRegistrar:fGurid></dt> <dd>Contains the Globally Unique Registrar Identifier (GURID) assigned by ICANN with type="positiveInteger" and isRequired="true".</t> </list></t> </list></t></dd> </dl> </dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "domain" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fCrRr>">Identifier<dl newline="false" spacing="normal"> <dt><rdeCsv:fCrRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that created the domain nameobject.</t> <t hangText="<rdeCsv:fCrID>">Identifierobject.</dd> <dt><rdeCsv:fCrID></dt> <dd>Identifier of the client that created the domain nameobject.</t> <t hangText="<rdeCsv:fUpRr>">Identifierobject.</dd> <dt><rdeCsv:fUpRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that last updated the domain nameobject.</t> <t hangText="<rdeCsv:fUpID>">Identifierobject.</dd> <dt><rdeCsv:fUpID></dt> <dd>Identifier of the client that last updated the domain nameobject.</t> <t hangText="<rdeCsv:fUName>">UTF8object.</dd> <dt><rdeCsv:fUName></dt> <dd>UTF-8 encoded domain name for the <csvDomain:fName> fieldelement.</t> <t hangText="<rdeCsv:fIdnTableId>">IDN Table Identifierelement.</dd> <dt><rdeCsv:fIdnTableId></dt> <dd>IDN table identifier used for the IDN domain name object thatMUST<bcp14>MUST</bcp14> matchaan <rdeCsv:fIdnTableId> field element in the "idnLanguage" CSV files, as defined in <xreftarget="idnCsvModel"/>.</t> <t hangText="<rdeCsv:fRegistrant>">Registranttarget="idnCsvModel" format="default"/>.</dd> <dt><rdeCsv:fRegistrant></dt> <dd>Registrant contact identifier for the domain nameobject.</t> <t hangText="<rdeCsv:fCrDate>">Created dateobject.</dd> <dt><rdeCsv:fCrDate></dt> <dd>Date and time of the domain nameobject.</t> <t hangText="<rdeCsv:fUpDate>">Dateobject creation.</dd> <dt><rdeCsv:fUpDate></dt> <dd>Date and time of the last update to the domain name object. This fieldMUST NOT<bcp14>MUST NOT</bcp14> be set if the domain name object has never beenmodified.</t> <t hangText="<rdeCsv:fExDate>">Expirationmodified.</dd> <dt><rdeCsv:fExDate></dt> <dd>Expiration date and time for the domain nameobject.</t> <t hangText="<rdeCsv:fTrDate>">Dateobject.</dd> <dt><rdeCsv:fTrDate></dt> <dd>Date and time of the last transfer for the domain name object. This fieldMUST NOT<bcp14>MUST NOT</bcp14> be set if the domain name object has never beentransferred.</t> </list></t> <t> <figure> <preamble> Exampletransferred.</dd> </dl> <t keepWithNext="true"> The following is an example of a "domain" <csvDomain:contents> <rdeCsv:csv> element.</preamble> <artwork><![CDATA[</t> <sourcecode markers="false" name="" type="xml"><![CDATA[ ... <csvDomain:contents> ... <rdeCsv:csv name="domain"> <rdeCsv:fields> <csvDomain:fName/> <rdeCsv:fRoid/> <rdeCsv:fIdnTableId/> <csvDomain:fOriginalName/> <rdeCsv:fRegistrant/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fExDate isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="5E403BD6"> domain-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding domain-YYYYMMDD.csv file. The file contains four records (two active ASCII domains, original IDN with LANG-1 language rules, and variant IDN with LANG-1 language rules).</preamble> <artwork><![CDATA[</t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,Ddomain1-TEST,,,registrantid,registrarX,registrarX, clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z domain2.example,Ddomain2-TEST,,,registrantid,registrarX,registrarX, clientY,1999-04-03T22:00:00.0Z,registrarX,clientY, 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z xn--bc123-3ve.example,Dxnabc123-TEST,LANG-1,,registrantid,registrarX, registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY, 2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z xn--bc321-3ve.example,Dxnabc321-TEST,LANG-1,xn--bc123-3ve.example, registrantid,registrarX,registrarX,clientY,2009-04-03T22:00:00.0Z,registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z]]> </artwork> </figure> </t>registrarX,clientY,2009-12-03T09:05:00.0Z,2025-04-03T22:00:00.0Z ]]></artwork> </section> <sectiontitle=""domainContacts"anchor="csvDomainContactsDefinition" numbered="true" toc="default"> <name>"domainContacts" CSV FileDefinition" anchor="csvDomainContactsDefinition">Definition</name> <t>The "domainContacts" CSV File Definition defines the fields and CSV file references used for the domain name object link records to contact objects, as described in <xreftarget="contactObject">Contact Object</xref>.</t>target="contactObject" format="default">'Contact Object'</xref>.</t> <t>The following "csvDomain" field elements, defined for the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "domainContacts" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">The<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>The name of the domain object that is linked to the contact object withisRequired="true".</t> <t hangText="<csvDomain:fContactType>">TheisRequired="true".</dd> <dt><csvDomain:fContactType></dt> <dd>The contact type for the contact object link with type="domain:contactAttrType" and isRequired="true". The supported contact type values include "admin" for the administration contact, "billing" for the billing contact, and "tech" for the technical contact.</t> </list></t></dd> </dl> <t>The following "csvContact" fields, defined for the <xreftarget="csvContactDefinition">"contact"target="csvContactDefinition" format="default">'"contact" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "domainContacts" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fId>">The<dl newline="false" spacing="normal"> <dt><csvContact:fId></dt> <dd>The server-unique contact identifier withisRequired="true".</t> </list></t> <t> <figure> <preamble> ExampleisRequired="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "domainContacts" <csvDomain:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvDomain:contents> ... <rdeCsv:csv name="domainContacts"> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvContact:fId/> <csvDomain:fContactType/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="6B976A6C"> domainContacts-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork></figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding domainContacts-YYYYMMDD.csv file. The file contains an admin, tech, and billing contact for the four domain names domain1.example, domain2.example,xn--bc123-3ve.examplexn--bc123-3ve.example, andxn--bc321-3ve.example. </preamble> <artwork><![CDATA[xn--bc321-3ve.example: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,domain1admin,admin domain1.example,domain1tech,tech domain1.example,domain1billing,billing domain2.example,domain2admin,admin domain2.example,domain2tech,tech domain2.example,domain2billing,billing xn--bc123-3ve.example,xnabc123admin,admin xn--bc123-3ve.example,xnabc123tech,tech xn--bc123-3ve.example,xnabc123billing,billing xn--bc321-3ve.example,xnabc123admin,admin xn--bc321-3ve.example,xnabc123tech,techxn--bc321-3ve.example,xnabc123billing,billing]]> </artwork> </figure> </t>xn--bc321-3ve.example,xnabc123billing,billing ]]></artwork> </section> <sectiontitle=""domainStatuses"anchor="csvDomainStatusesDefinition" numbered="true" toc="default"> <name>"domainStatuses" CSV FileDefinition" anchor="csvDomainStatusesDefinition">Definition</name> <t>The "domainStatuses" CSV File Definition defines the fields and CSV file references used for the domain name object statuses.</t> <t>The following "csvDomain" fields, defined for the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "domainStatuses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">Domain<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>Domain name of status withisRequired="true".</t> <t hangText="<csvDomain:fStatus>">TheisRequired="true".</dd> <dt><csvDomain:fStatus></dt> <dd>The status of the domain name with type="domain:statusValueType" and isRequired="true".</t> <t hangText="<csvDomain:fRgpStatus>">The</dd> <dt><csvDomain:fRgpStatus></dt> <dd>The RGP status, as a sub-status of the <csvDomain:fStatus> "pendingDelete" status value, with type="rgp:statusValueType" as defined in <xreftarget="RFC3915"/>. </t> </list></t>target="RFC3915" format="default"/>. </dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "domainStatuses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fStatusDescription>">Domain<dl newline="false" spacing="normal"> <dt><rdeCsv:fStatusDescription></dt> <dd>Domain name object statusdescriptiondescription, which isfree formfree-form text describing the rationale for thestatus.</t> <t hangText="<rdeCsv:fLang>">Languagestatus.</dd> <dt><rdeCsv:fLang></dt> <dd>Language of the <rdeCsv:fStatusDescription>field.</t> </list></t> <t> <figure> <preamble> Examplefield.</dd> </dl> <t keepWithNext="true"> The following is an example of a "domainStatuses" <csvDomain:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvDomain:contents> ... <rdeCsv:csv name="domainStatuses"> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> <csvDomain:fRgpStatus/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="98D139A3"> domainStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding domainStatuses-YYYYMMDD.csv file. The file contains the statuses for the four domain names domain1.example, domain2.example,xn--bc123-3ve.examplexn--bc123-3ve.example, andxn--bc321-3ve.example. </preamble> <artwork><![CDATA[xn--bc321-3ve.example: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,clientUpdateProhibited,"Disallow update", en, domain1.example,clientDeleteProhibited,"Disallow delete", en, domain2.example,ok,,, xn--bc123-3ve.example,ok,,,xn--bc321-3ve.example,ok,,,]]> </artwork> </figure> </t>xn--bc321-3ve.example,ok,,, ]]></artwork> </section> <sectiontitle=""domainNameServers"anchor="csvDomainNameServersDefinition" numbered="true" toc="default"> <name>"domainNameServers" CSV FileDefinition" anchor="csvDomainNameServersDefinition">Definition</name> <t>The "domainNameServers" CSV File Definition defines the fields and CSV file references used for the domain name delegated hosts (name servers). The "domainNameServers" CSV files define the relationship between a domain name object and a delegated host. The "domainNameServers" CSV File is used to support the <domain:hostObj> model, defined in <xreftarget="RFC5731"/>.target="RFC5731" format="default"/>. </t> <t>The following "csvDomain" fields, defined for the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "domainNameServers" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">Domain<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>Domain name using the delegated host withisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "csvHost" and "rdeCsv" field elementsMUST<bcp14>MUST</bcp14> be used in the "domainNameServers" <rdeCsv:csv> <rdeCsv:fields> element: </t><t> <list style="hanging"> <t hangText="<csvHost:fName><dl newline="false" spacing="normal"> <dt><csvHost:fName> or<rdeCsv:fRoid>">A<rdeCsv:fRoid></dt> <dd> <t>A choiceof: <list style="hanging"> <t hangText="<csvHost:fName>">Hostof the following: </t> <dl newline="false" spacing="normal"> <dt><csvHost:fName></dt> <dd>Host name field with type="eppcom:labelType" and isRequired="true".</t> <t hangText="<rdeCsv:fRoid>">Host</dd> <dt><rdeCsv:fRoid></dt> <dd>Host objectRegistry Object IDentifier (ROID)ROID assigned to the host object with isRequired="true".</t> </list></t> </list> </t> <t> <figure> <preamble> Example</dd> </dl> </dd> </dl> <t keepWithNext="true"> The following is an example of a "domainNameServers" <csvDomain:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvDomain:contents> ... <rdeCsv:csv name="domainNameServers"> <rdeCsv:fields> <csvDomain:fName parent="true"/> <rdeCsv:fRoid/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="8FE6E9E1"> domainNameServers-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding domainNameServers-YYYYMMDD.csv file. The file contains the delegated hosts (name servers) for the four domain names domain1.example, domain2.example,xn--bc123-3ve.examplexn--bc123-3ve.example, and xn--bc321-3ve.example referenced via the <rdeCsv:fRoid> fieldelement. </preamble> <artwork><![CDATA[element: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,Hns1_domain1_test-TEST domain1.example,Hns2_domain1_test-TEST domain2.example,Hns1_domain2_test-TEST domain2.example,Hns2_domain2_test-TEST xn--bc123-3ve.example,Hns1_example_test-TEST xn--bc123-3ve.example,Hns2_example_test-TEST xn--bc321-3ve.example,Hns1_example_test-TESTxn--bc321-3ve.example,Hns2_example_test-TEST]]> </artwork> </figure> </t>xn--bc321-3ve.example,Hns2_example_test-TEST ]]></artwork> </section> <sectiontitle=""domainNameServersAddresses"anchor="csvDomainNameServersAddressesDefinition" numbered="true" toc="default"> <name>"domainNameServersAddresses" CSV FileDefinition" anchor="csvDomainNameServersAddressesDefinition">Definition</name> <t>The "domainNameServersAddresses" CSV File Definition defines the fields and CSV file references used for supporting the domain host attributes model. </t> <t>The following "csvDomain" fields, defined for the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "domainNameServersAddresses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">Domain<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>Domain name using the delegated host with host <csvHost:fName> andisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="hostCsvModel">Host CSV model elements</xref>, MUSTtarget="hostCsvModel" format="default">'CSV Model'</xref>, <bcp14>MUST</bcp14> be used in the "domainNameServersAddresses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvHost:fName>">Host<dl newline="false" spacing="normal"> <dt><csvHost:fName></dt> <dd>Host name field with type="eppcom:labelType" and isRequired="true".</t> </list></t></dd> </dl> <t>The following "csvHost" fields, defined insection<xreftarget="hostCsvModel">Host CSV model elements</xref>, MAYtarget="hostCsvModel" format="default">'CSV Model'</xref>, <bcp14>MAY</bcp14> be used in the "domainNameServersAddresses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvHost:fAddr>">IP<dl newline="false" spacing="normal"> <dt><csvHost:fAddr></dt> <dd>IP addresses associated with the host object with type="host:addrStringType".</t> <t hangText="<csvHost:fAddrVersion>">IP</dd> <dt><csvHost:fAddrVersion></dt> <dd>IP addresses version associated with the host object with type="host:ipType". "host:ipType" has the enumerated values of "v4" or "v6".</t> </list></t> <t> <figure> <preamble> Example</dd> </dl> <t keepWithNext="true"> The following is an example of a "domainNameServersAddresses" <csvDomain:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvDomain:contents> ... <rdeCsv:csv name="domainNameServersAddresses"> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvHost:fName/> <csvHost:fAddr/> <csvHost:fAddrVersion/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D3B77438"> domainNameServersAddresses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding domainNameServersAddresses-YYYYMMDD.csv file. The file contains the delegated hosts (name servers) for the four domain names domain1.example, domain2.example,xn--bc123-3ve.examplexn--bc123-3ve.example, andxn--bc321-3ve.example. </preamble> <artwork><![CDATA[xn--bc321-3ve.example: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,ns1.domain1.example,192.0.2.1,v4 domain1.example,ns2.domain1.example,2001:DB8::1,v6 domain2.example,ns1.example.net,, domain2.example,ns2.example.net,, xn--bc123-3ve.example,ns1.example.net,, xn--bc123-3ve.example,ns2.example.net,, xn--bc321-3ve.example,ns1.example.net,,xn--bc321-3ve.example,ns2.example.net,,]]> </artwork> </figure> </t>xn--bc321-3ve.example,ns2.example.net,, ]]></artwork> </section> <sectiontitle=""dnssec"anchor="csvDnssecDefinition" numbered="true" toc="default"> <name>"dnssec" CSV FileDefinition" anchor="csvDnssecDefinition">Definition</name> <t>The "dnssec" CSV File Definition defines the fields and CSV file references used for the domain name object DNSSEC records(DS(Delegation Signer (DS) orKey Data).</t>key data).</t> <t>The following "csvDomain" field elementsMUST<bcp14>MUST</bcp14> be used in the "dnssec" <rdeCsv:csv> <rdeCsv:fields> element when the DS Data Interface per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> is used: </t><t><list style="hanging"> <t hangText="<csvDomain:fKeyTag>">Contains<dl newline="false" spacing="normal"> <dt><csvDomain:fKeyTag></dt> <dd>Contains the DS key tag value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="unsignedShort" and isRequired="true".</t> <t hangText="<csvDomain:fDsAlg>">Contains</dd> <dt><csvDomain:fDsAlg></dt> <dd>Contains the DS algorithm value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="unsignedByte" and isRequired="true".</t> <t hangText="<csvDomain:fDigestType>">Contains</dd> <dt><csvDomain:fDigestType></dt> <dd>Contains the DS digest type value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="unsignedByte" and isRequired="true".</t> <t hangText="<csvDomain:fDigest>">Contains</dd> <dt><csvDomain:fDigest></dt> <dd>Contains the DS digest value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="hexBinary" and isRequired="true".</t> </list></t></dd> </dl> <t>The following "csvDomain" field elementsMUST<bcp14>MUST</bcp14> be used in the "dnssec" <rdeCsv:csv> <rdeCsv:fields> element when the Key Data Interface per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> is used andMAY<bcp14>MAY</bcp14> be used in the "dnssec" <rdeCsv:csv> <rdeCsv:fields> element when the DS Data Interface per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> is used: </t><t><list style="hanging"> <t hangText="<csvDomain:fFlags>">Contains<dl newline="false" spacing="normal"> <dt><csvDomain:fFlags></dt> <dd>Contains the flags field value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="unsignedShort" and isRequired="true".</t> <t hangText="<csvDomain:fProtocol>">Contains</dd> <dt><csvDomain:fProtocol></dt> <dd>Contains theKeykey protocol value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="unsignedByte" and isRequired="true".</t> <t hangText="<csvDomain:fKeyAlg>">Contains</dd> <dt><csvDomain:fKeyAlg></dt> <dd>Contains theKeykey algorithm value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="unsignedByte" and isRequired="true".</t> <t hangText="<csvDomain:fPubKey>">Contains</dd> <dt><csvDomain:fPubKey></dt> <dd>Contains the public key value per <xreftarget="RFC5910"/>target="RFC5910" format="default"/> with type="secDNS:keyType" and isRequired="true".</t> </list></t></dd> </dl> <t>The following "csvDomain" field elementsMAY<bcp14>MAY</bcp14> be used in the "dnssec" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fMaxSigLife>">Indicates<dl newline="false" spacing="normal"> <dt><csvDomain:fMaxSigLife></dt> <dd>Indicates a child's preference for the number of seconds after signature generation when the parent's signature on the DS information provided by the child will expire with type="secDNS:maxSigLifeType" defined in <xreftarget="RFC5910"/>. </t> </list></t>target="RFC5910" format="default"/>. </dd> </dl> <t>The following "domain" fields, defined for the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "dnssec" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">Domain<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>Domain name of the domain name object associated with the DNSSEC record andisRequired="true".</t> </list></t> <t> <figure> <preamble> ExampleisRequired="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with the DS Data Interface of <xreftarget="RFC5910"/>: </preamble> <artwork><![CDATA[target="RFC5910" format="default"/>: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ <csvDomain:contents> ... <rdeCsv:csv name="dnssec"> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fMaxSigLife/> <csvDomain:fKeyTag/> <csvDomain:fDsAlg/> <csvDomain:fDigestType/> <csvDomain:fDigest/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="10ED6C42"> dnssec-ds-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding dnssec-ds-YYYYMMDD.csv file. The file contains two DS records fordomain1.example. </preamble> <artwork><![CDATA[ domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55 domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3]]> </artwork> </figure>domain1.example: </t><t> <figure> <preamble> Example<artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,604800,30730,8,2,91C9B176EB////F1C46F6A55 domain1.example,604800,61882,8,2,9F8FEAC94B////1272AF09F3 ]]></artwork> <t keepWithNext="true"> The following is an example of a "dnssec" <csvDomain:contents> <rdeCsv:csv> element with the Key Data Interface of <xreftarget="RFC5910"/>: </preamble> <artwork><![CDATA[target="RFC5910" format="default"/>: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ <csvDomain:contents> ... <rdeCsv:csv name="dnssec"> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fMaxSigLife/> <csvDomain:fFlags/> <csvDomain:fProtocol/> <csvDomain:fKeyAlg/> <csvDomain:fPubKey/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="183C3F79"> dnssec-key-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding dnssec-key-YYYYMMDD.csv file. The file contains two key records fordomain1.example. </preamble> <artwork><![CDATA[ domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c= domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940=]]> </artwork> </figure>domain1.example: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,604800,257,3,8,AwEAAZD1+z////G1jqviK8c= domain1.example,604800,257,3,8,AwEAAbntWP////vwDitt940= ]]></artwork> </section> <sectiontitle=""domainTransfer"anchor="csvDomainTransferDefinition" numbered="true" toc="default"> <name>"domainTransfer" CSV FileDefinition" anchor="csvDomainTransferDefinition">Definition</name> <t>The "domainTransfer" CSV File Definition defines the fields and CSV file references used for the domain name object pending and completed transfer records. No additional field elements were added for use in the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element.</t> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MUSTtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MUST</bcp14> be used in the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fTrStatus>">State<dl newline="false" spacing="normal"> <dt><rdeCsv:fTrStatus></dt> <dd>State of the most recent transfer request withisRequired="true".</t> <t hangText="<rdeCsv:fReRr>">IdentifierisRequired="true".</dd> <dt><rdeCsv:fReRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that requested the transfer withisRequired="true".</t> <t hangText="<rdeCsv:fReDate>">DateisRequired="true".</dd> <dt><rdeCsv:fReDate></dt> <dd>Date and time that the transfer was requested withisRequired="true".</t> <t hangText="<rdeCsv:fAcRr>">IdentifierisRequired="true".</dd> <dt><rdeCsv:fAcRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that should take or took action withisRequired="true".</t> <t hangText="<rdeCsv:fAcDate>">DateisRequired="true".</dd> <dt><rdeCsv:fAcDate></dt> <dd>Date and time that the transfer action should be taken or has been taken withisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fExDate>">Expiration<dl newline="false" spacing="normal"> <dt><rdeCsv:fExDate></dt> <dd>Expiration date if the transfer command caused or causes a change in the validityperiod.</t> <t hangText="<rdeCsv:fReID>">Identifierperiod.</dd> <dt><rdeCsv:fReID></dt> <dd>Identifier of the client that requested thetransfer.</t> <t hangText="<rdeCsv:fAcID>">Identifiertransfer.</dd> <dt><rdeCsv:fAcID></dt> <dd>Identifier of the client that should take or took action fortransfer.</t> </list></t>transfer.</dd> </dl> <t>The following "csvDomain" fields, defined for the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "domainTransfer" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">Domain<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>Domain name of the domain name object involved in the transfer withisRequired="true".</t> </list></t> <t> <figure> <preamble> ExampleisRequired="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "domainTransfer" <csvDomain:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvDomain:contents> ... <rdeCsv:csv name="domainTransfer"> <rdeCsv:fields> <csvDomain:fName parent="true"/> <rdeCsv:fTrStatus/> <rdeCsv:fReRr/> <rdeCsv:fReID/> <rdeCsv:fReDate/> <rdeCsv:fAcRr/> <rdeCsv:fAcID/> <rdeCsv:fAcDate/> <rdeCsv:fExDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="2E5A9ACD"> domainTransfer-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding domainTransfer-YYYYMMDD.csv file. The file contains one domain transfer record with a pendingstatus. </preamble> <artwork><![CDATA[status: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example,pending,registrarX,clientY, 2011-03-08T19:38:00.0Z,registrarY,,2011-03-13T23:59:59.0Z,2025-04-03T22:00:00.0Z]]> </artwork> </figure> </t>2025-04-03T22:00:00.0Z ]]></artwork> </section> </section> <sectiontitle="<csvDomain:deletes>" anchor="csvDomainDeletes">anchor="csvDomainDeletes" numbered="true" toc="default"> <name><csvDomain:deletes></name> <t> The <csvDomain:deletes> is used to hold the deleted domain name objects in a Differential or Incremental Deposit. All the domain name object data is deleted as part of a cascade delete. The <csvDomain:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported domain name deletes CSV file definition. </t> <sectiontitle=""domain"anchor="csvDomainDeletesDefinition" numbered="true" toc="default"> <name>"domain" Deletes CSV FileDefinition" anchor="csvDomainDeletesDefinition">Definition</name> <t> The following "csvDomain" field elementsMUST<bcp14>MUST</bcp14> be used in the deletes "domain" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvDomain:fName>">Domain<dl newline="false" spacing="normal"> <dt><csvDomain:fName></dt> <dd>Domain name field with type="eppcom:labelType" and isRequired="true".</t> </list></t> <t> <figure> <preamble> Example</dd> </dl> <t keepWithNext="true"> The following is an example of a "domain" <csvDomain:deletes> <rdeCsv:csv> element:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvDomain:deletes> ... <rdeCsv:csv name="domain"> <rdeCsv:fields> <csvDomain:fName/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="A06D8194"> domain-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvDomain:deletes>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding domain-delete-YYYYMMDD.csv file. The file contains two domain namerecords. </preamble> <artwork><![CDATA[ domain1.example domain2.example]]> </artwork> </figure>records: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1.example domain2.example ]]></artwork> </section> </section> </section> </section> <sectiontitle="Host Object" anchor="hostObject">anchor="hostObject" numbered="true" toc="default"> <name>Host Object</name> <t> The host object is based on the EPP host name mapping in <xreftarget="RFC5732"/>.target="RFC5732" format="default"/>. The host object supports both the XMLModelmodel and the CSVModel,model, defined in <xreftarget="models">Models</xref> section.target="models" format="default">'Models'</xref>. The elements used for both models are defined in the following sections. Both the <csvHost:contents> and <csvHost:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute. </t> <sectiontitle="XML Model" anchor="hostXmlModel">anchor="hostXmlModel" numbered="true" toc="default"> <name>XML Model</name> <t>There are two elements used in the data escrow of the host objects for the XML model including the<rdeHost:host>,<rdeHost:host> element, under the <rdeHost:contents> element, and the <rdeHost:delete> element, under the <rde:deletes> element. </t> <t>AAn <rdeHost:host> element substitutes for the <rdeHost:abstractHost> abstract element todefinecreate a concrete definition of a host. The <rdeHost:abstractHost> element can be replaced by other host definitions using the XML schema substitution groups feature. </t> <sectiontitle="<rdeHost:host> element" anchor="rdeHostElement">anchor="rdeHostElement" numbered="true" toc="default"> <name><rdeHost:host> Element</name> <t> The RDE host object is based on the EPP host <info> response for an authorized client(Section 3.1.2. of <xref target="RFC5732"/>).(<xref target="RFC5732" section="3.1.2" sectionFormat="of" format="default"/>). </t> <t> TheOPTIONAL<bcp14>OPTIONAL</bcp14> <host> element contains the following child elements: </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> A <name> element that contains thefully-qualifiedfully qualified name of the host object.</t> <t></li> <li> A <roid> element that contains therepository object identifierROID assigned to the host object when the object was created.</t> <t></li> <li> One or more <status> elements that describe the status of the host object.</t> <t></li> <li> Zero or more <addr> elements that contain the IP addresses associated with the host object.</t> <t></li> <li> A <clID> element that contains the identifier of the sponsoring registrar.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crRr> element that contains the identifier of the registrar that created the host object. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crDate> element that contains the date and time ofhost-objecthost object creation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <upRr> element that contains the identifier of the registrar that last updated the host object. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the host object has never been modified. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <upDate> element that contains the date and time of the most recenthost-objecthost object modification. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the host object has never been modified.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <trDate> element that contains the date and time of the most recent host object successful transfer. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the domain name object has never beentransfered. </t> </list> </t> <t> <figure> <preamble> Exampletransferred. </li> </ul> <t keepWithNext="true"> The following is an example of a <host> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeHost:host> <rdeHost:name>ns1.example1.example</rdeHost:name> <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid> <rdeHost:status s="ok"/> <rdeHost:status s="linked"/> <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr> <rdeHost:addr ip="v6">2001:DB8:1::1</rdeHost:addr> <rdeHost:clID>RegistrarX</rdeHost:clID> <rdeHost:crRr>RegistrarX</rdeHost:crRr> <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate> <rdeHost:upRr>RegistrarX</rdeHost:upRr> <rdeHost:upDate>2009-10-03T09:34:00.0Z</rdeHost:upDate> </rdeHost:host>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> <sectiontitle="<rdeHost:delete> object" anchor="del_host_object">anchor="del_host_object" numbered="true" toc="default"> <name><rdeHost:delete> Object</name> <t> The <rdeHost:delete> element contains thefully-qualified domain nameFQDN of a host that was deleted. The <rdeHost:delete> element also supports host removal based onroidROID to support SRS systems in which different hosts with the samefully-qualified domain nameFQDN are active at the same time. </t><t> <figure> <preamble> Example<t keepWithNext="true"> The following is an example of an <rdeHost:delete> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rde:deletes> ... <rdeHost:delete> <rdeHost:name>ns1.example.example</rdeHost:name> </rdeHost:delete> ... </rde:deletes>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="CSV Model" anchor="hostCsvModel">anchor="hostCsvModel" numbered="true" toc="default"> <name>CSV Model</name> <t>For the CSVModelmodel of the host object, the <csvHost:contents> child element of the <rde:contents> element is used to hold the new or updated host objects for the deposit. The <csvHost:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged host objects for the deposit. </t> <t> Differential and Incremental Deposits are based on changes to the host objects. The updated host object data under the <csvHost:contents> element is a cascade replace down all of the host CSV files starting with the parent <xreftarget="csvHostDefinition">"host"target="csvHostDefinition" format="default">'"host" CSV FileDefinition</xref>.Definition'</xref>. The child CSV file definitions includeaan <rdeCsv:fRoid parent="true"> field. All the child CSV file definition data for the host objects in the parent <xreftarget="csvHostDefinition">"host"target="csvHostDefinition" format="default">'"host" CSV FileDefinition</xref> MUSTDefinition'</xref> <bcp14>MUST</bcp14> first be deleted and then set using the data in the child CSV files. The deleted host object data under the <csvHost:deletes> element is a cascade delete starting from the <xreftarget="csvHostDeletesDefinition">"host"target="csvHostDeletesDefinition" format="default">'"host" Deletes CSV FileDefinition</xref>.Definition'</xref>. </t> <sectiontitle="<csvHost:contents>" anchor="csvHostContents">anchor="csvHostContents" numbered="true" toc="default"> <name><csvHost:contents></name> <t>The <csvHost:contents> is used to hold the new or updated host object information for the deposit. The <csvHost:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported host CSV file definitions. </t> <sectiontitle=""host"anchor="csvHostDefinition" numbered="true" toc="default"> <name>"host" CSV FileDefinition" anchor="csvHostDefinition">Definition</name> <t>The "host" CSV File Definition defines the fields and CSV file references used for the host object records.</t> <t>The following "csvHost" field elementsMUST<bcp14>MUST</bcp14> be used in the "host" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvHost:fName>">Host<dl newline="false" spacing="normal"> <dt><csvHost:fName></dt> <dd>Host name field with type="eppcom:labelType" and isRequired="true".</t> </list></t></dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MUSTtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MUST</bcp14> be used in the "host" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fRoid>">Repository Object IDentifier (ROID)<dl newline="false" spacing="normal"> <dt><rdeCsv:fRoid></dt> <dd>ROID assigned to the host object withisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "rdeCsv" and "csvRegistrar"fields, MAYfields <bcp14>MAY</bcp14> be used in the "host" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fClID><dl newline="false" spacing="normal"> <dt><rdeCsv:fClID> or<csvRegistrar:fGurid>">A<csvRegistrar:fGurid></dt> <dd> <t>A choiceof: <list style="hanging"> <t hangText="<rdeCsv:fClID>">Identifierof the following: </t> <dl newline="false" spacing="normal"> <dt><rdeCsv:fClID></dt> <dd>Identifier of the sponsoring client with isRequired="true".</t> <t hangText="<csvRegistrar:fGurid>">Contains</dd> <dt><csvRegistrar:fGurid></dt> <dd>Contains theGlobally Unique Registrar Identifier (GURID)GURID assigned by ICANN with type="positiveInteger" and isRequired="true".</t> </list></t> <t hangText="<rdeCsv:fCrRr>">Identifier</dd> </dl> </dd> <dt><rdeCsv:fCrRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that created the hostobject.</t> <t hangText="<rdeCsv:fCrID>">Identifierobject.</dd> <dt><rdeCsv:fCrID></dt> <dd>Identifier of the client that created the hostobject.</t> <t hangText="<rdeCsv:fUpRr>">Identifierobject.</dd> <dt><rdeCsv:fUpRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that last updated the hostobject.</t> <t hangText="<rdeCsv:fUpID>">Identifierobject.</dd> <dt><rdeCsv:fUpID></dt> <dd>Identifier of the client that last updated the hostobject.</t> <t hangText="<rdeCsv:fCrDate>">Dateobject.</dd> <dt><rdeCsv:fCrDate></dt> <dd>Date and time that the host object wascreated.</t> <t hangText="<rdeCsv:fUpDate>">Datecreated.</dd> <dt><rdeCsv:fUpDate></dt> <dd>Date and time that the host object was last updated. This fieldMUST NOT<bcp14>MUST NOT</bcp14> be set if the domain name object has never beenmodified.</t> <t hangText="<rdeCsv:fTrDate>">Datemodified.</dd> <dt><rdeCsv:fTrDate></dt> <dd>Date and time that the host object was last transferred. This fieldMUST NOT<bcp14>MUST NOT</bcp14> be set if the domain name object has never beentransferred.</t> </list></t> <t> <figure> <preamble>Exampletransferred.</dd> </dl> <t keepWithNext="true">The following is an example of a "host" <csvHost:contents> <rdeCsv:csv>element.</preamble> <artwork><![CDATA[element:</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvHost:contents> ... <rdeCsv:csv name="host"> <rdeCsv:fields> <csvHost:fName/> <rdeCsv:fRoid/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fTrDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="6F1E58E5"> host-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvHost:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding host-YYYYMMDD.csv file. The file contains six host records with four being internal hosts and two being externalhosts. </preamble> <artwork><![CDATA[hosts: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ ns1.domain1.example,Hns1_example_test-TEST,registrarX,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z ns2.domain1.example,Hns2_domain1_test-TEST,registrarX,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z ns1.domain2.example,Hns1_domain2_test-TEST,registrarX,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z ns2.domain2.example,Hns2_domain2_test-TEST,registrarX,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z ns1.example.net,Hns1_example_test-TEST,registrarX,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX, clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z ns2.example.net,Hns2_example_test-TEST,registrarX,registrarX, clientY,1999-05-08T12:10:00.0Z,registrarX,clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z]]> </artwork> </figure> </t>clientY,2009-10-03T09:34:00.0Z,2007-01-08T09:19:00.0Z ]]></artwork> </section> <sectiontitle=""hostStatuses"anchor="csvHostStatusesDefinition" numbered="true" toc="default"> <name>"hostStatuses" CSV FileDefinition" anchor="csvHostStatusesDefinition">Definition</name> <t>The "hostStatuses" CSV File Definition defines the fields and CSV file references used for the host object statuses. </t> <t>The following "csvHost" fields, defined for the <xreftarget="csvHostDefinition">"host"target="csvHostDefinition" format="default">'"host" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "hostStatuses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvHost:fStatus>">The<dl newline="false" spacing="normal"> <dt><csvHost:fStatus></dt> <dd>The status of the host with type="host:statusValueType" andisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MUSTtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MUST</bcp14> be used in the "hostStatuses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fRoid>">Host<dl newline="false" spacing="normal"> <dt><rdeCsv:fRoid></dt> <dd>Host objectRegistry Object IDentifier (ROID)ROID assigned to the host object withisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "hostStatuses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fStatusDescription>">Host<dl newline="false" spacing="normal"> <dt><rdeCsv:fStatusDescription></dt> <dd>Host object statusdescriptiondescription, which isfree formfree-form text describing the rationale for thestatus.</t> <t hangText="<rdeCsv:fLang>">Languagestatus.</dd> <dt><rdeCsv:fLang></dt> <dd>Language of the <rdeCsv:fStatusDescription>field.</t> </list></t> <t> <figure> <preamble> Examplefield.</dd> </dl> <t keepWithNext="true"> The following is an example of a "hostStatuses" <csvHost:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvHost:contents> ... <rdeCsv:csv name="hostStatuses"> <rdeCsv:fields> <rdeCsv:fRoid parent="true"/> <csvHost:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="0DAE0583"> hostStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvHost:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding hostStatuses-YYYYMMDD.csv file. The file contains the statuses for the six host names ns1.domain1.example, ns2.domain1.example, ns1.domain2.example, ns2.domain2.example,ns1.example.netns1.example.net, andns2.example.net. </preamble> <artwork><![CDATA[ns2.example.net: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ Hns1_domain1_test-TEST,ok,, Hns2_domain1_test-TEST,ok,, Hns1_domain2_test-TEST,ok,, Hns2_domain2_test-TEST,ok,, Hns1_example_test-TEST,ok,,Hns2_example_test-TEST,ok,,]]> </artwork> </figure> </t>Hns2_example_test-TEST,ok,, ]]></artwork> </section> <sectiontitle=""hostAddresses"anchor="csvHostAddressesDefinition" numbered="true" toc="default"> <name>"hostAddresses" CSV FileDefinition" anchor="csvHostAddressesDefinition">Definition</name> <t>The "hostAddresses" CSV File Definition defines the fields and CSV file references used for the host object IP addresses.</t> <t>The following "csvHost" field elementsMUST<bcp14>MUST</bcp14> be used in the "hostAddresses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvHost:fAddr>">IP<dl newline="false" spacing="normal"> <dt><csvHost:fAddr></dt> <dd>IP addresses associated with the host object with type="host:addrStringType". The attribute "isRequired"MUST<bcp14>MUST</bcp14> equal "true".</t> <t hangText="<csvHost:fAddrVersion>">IP</dd> <dt><csvHost:fAddrVersion></dt> <dd>IP addresses version associated with the host object with type="host:ipType". "host:ipType" has the enumerated values of "v4" or "v6". The attribute "isRequired"MUST<bcp14>MUST</bcp14> equal "true".</t> </list></t></dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MUSTtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MUST</bcp14> be used in the "hostAddresses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fRoid>">Host<dl newline="false" spacing="normal"> <dt><rdeCsv:fRoid></dt> <dd>Host objectRegistry Object IDentifier (ROID)ROID assigned to the host object withisRequired="true".</t> </list></t> <t> <figure> <preamble> ExampleisRequired="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "hostAddresses" <csvHost:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvHost:contents> ... <rdeCsv:csv name="hostAddresses"> <rdeCsv:fields> <rdeCsv:fRoid parent="true"/> <csvHost:fAddr isRequired="true"/> <csvHost:fAddrVersion isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="28B194B0"> hostAddresses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvHost:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding hostAddresses-YYYYMMDD.csv file. The file contains the IP addresses for the host names ns1.domain1.example, ns2.domain1.example,ns1.domain2.examplens1.domain2.example, andns2.domain2.example. </preamble> <artwork><![CDATA[ns2.domain2.example: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ Hns1_domain1_test-TEST,192.0.2.1,v4 Hns2_domain1_test-TEST,2001:DB8::1,v6 Hns1_domain2_test-TEST,192.0.2.2,v4Hns2_domain2_test-TEST,2001:DB8::2,v6]]> </artwork> </figure> </t>Hns2_domain2_test-TEST,2001:DB8::2,v6 ]]></artwork> </section> </section> <sectiontitle="<csvHost:deletes>" anchor="csvHostDeletes">anchor="csvHostDeletes" numbered="true" toc="default"> <name><csvHost:deletes></name> <t> The <csvHost:deletes> is used to hold the deleted host objects in a Differential or Incremental Deposit. All the host object data is deleted as part of a cascade delete. The <csvHost:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported host deletes CSV file definition. </t> <sectiontitle=""host"anchor="csvHostDeletesDefinition" numbered="true" toc="default"> <name>"host" Deletes CSV FileDefinition" anchor="csvHostDeletesDefinition">Definition</name> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MUSTtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MUST</bcp14> be used in the "host" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fRoid>">Repository Object IDentifier (ROID)<dl newline="false" spacing="normal"> <dt><rdeCsv:fRoid></dt> <dd>ROID assigned to the host object withisRequired="true".</t> </list></t> <t> <figure> <preamble> ExampleisRequired="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "host" <csvHost:deletes> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvHost:deletes> ... <rdeCsv:csv name="host"> <rdeCsv:fields> <rdeCsv:fRoid/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="777F5F0E"> host-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvHost:deletes>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the host-delete-YYYYMMDD.csv file. The file contains four hostrecords. </preamble> <artwork><![CDATA[records: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ Hns1_domain1_test-TEST Hns2_domain1_test-TEST Hns1_domain2_test-TESTHns2_domain2_test-TEST]]> </artwork> </figure> </t>Hns2_domain2_test-TEST ]]></artwork> </section> </section> </section> </section> <sectiontitle="Contact Object" anchor="contactObject">anchor="contactObject" numbered="true" toc="default"> <name>Contact Object</name> <t> The contact object is based on the EPP contact name mapping in <xreftarget="RFC5733"/>.target="RFC5733" format="default"/>. The contact object supports both the XMLModelmodel and the CSVModel,model, defined in <xreftarget="models">Models</xref> section.target="models" format="default">'Models'</xref>. The elements used for both models are defined in the following sections. </t> <sectiontitle="XML Model" anchor="contactXmlModel">anchor="contactXmlModel" numbered="true" toc="default"> <name>XML Model</name> <t>There are two elements used in the data escrow of the contact objects for the XML model including the<rdeContact:contact>,<rdeContact:contact> element, under the <rdeContact:contents> element, and the <rdeContact:delete> element, under the <rde:deletes> element. </t> <t> A <contact> element substitutes for the <abstractContact> abstract element todefinecreate a concrete definition of a contact. The <abstractContact> element can be replaced by other contact definitions using the XML schema substitution groups feature. </t> <sectiontitle="<rdeContact:contact> object" anchor="rdeContactElement">anchor="rdeContactElement" numbered="true" toc="default"> <name><rdeContact:contact> Object</name> <t> The contact object is based on the EPP contact <info> response for an authorized client(Section 3.1.2. of <xref target="RFC5733"/>)(<xref target="RFC5733" section="3.1.2" sectionFormat="of" format="default"/>) with some additions including the data from an EPP <transfer>Query Response,query response, seeSection 3.1.3. of<xreftarget="RFC5733"/>.target="RFC5733" section="3.1.3" sectionFormat="of" format="default"/>. </t> <t> TheOPTIONAL<bcp14>OPTIONAL</bcp14> <contact> element contains the following child elements: </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> A <id> element that contains the server-unique identifier of the contactobject </t> <t>object. </li> <li> A <roid> element that contains theRepository Object IDentifierROID assigned to the contact object when the object was created.</t> <t></li> <li> One or more <status> elements that describe the status of the contact object.</t></li> <li> <t> One or two <postalInfo> elements that contain postal-address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, element contentMUST<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, element contentMAY<bcp14>MAY</bcp14> be represented in unrestricted UTF-8. The <postalInfo> element contains the following child elements:<list style="symbols"> <t></t> <ul spacing="normal"> <li> A <name> element that contains the name of the individual or role represented by the contact.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <org> element that contains the name of the organization with which the contact is affiliated.</t></li> <li> <t> An <addr> element that contains address information associated with the contact. An <addr> element contains the following child elements:<list style="symbols"> <t></t> <ul spacing="normal"> <li> One, two, or threeOPTIONAL<bcp14>OPTIONAL</bcp14> <street> elements that contain the contact's street address.</t> <t></li> <li> A <city> element that contains the contact's city.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <sp> element that contains the contact's state or province.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <pc> element that contains the contact's postal code.</t> <t></li> <li> A <cc> element that contains the contact's two-letter country code.</t> </list> </t> </list> </t> <t></li> </ul> </li> </ul> </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <voice> element that contains the contact's voice telephone number.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <fax> element that contains the contact's facsimile telephone number.</t> <t></li> <li> An <email> element that contains the contact's email address.</t> <t></li> <li> A <clID> element that contains the identifier of the sponsoring registrar.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crRr> element that contains the identifier of the registrar that created the contact object. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crDate> element that contains the date and time ofcontact-objectcontact object creation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <upRr> element that contains the identifier of the registrar that last updated the contact object. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the contact has never been modified. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <upDate> element that contains the date and time of the most recentcontact-objectcontact object modification. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the contact object has never been modified.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <trDate> element that contains the date and time of the most recent contact object successful transfer. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if the contact object has never been transferred.</t></li> <li> <t> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <trnData> element that contains the following child elements related to the last transfer request of the contact object:<list style="symbols"> <t></t> <ul spacing="normal"> <li> A <trStatus> element that contains the state of the most recent transfer request.</t> <t> A</li> <li> An <reRr> element that contains the identifier of the registrar that requested the domain name object transfer. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t></li> <li> An <acRr> element that contains the identifier of the registrar that should act upon aPENDINGpending transfer request. For all other status types, the value identifies the registrar that took the indicated action. AnOPTIONAL client<bcp14>OPTIONAL</bcp14> "client" attribute is used to specify the client that performed the operation.</t> <t> A</li> <li> An <reDate> element that contains the date and time that the transfer was requested.</t> <t></li> <li> An <acDate> element that contains the date and time of a required or completed response. For aPENDINGpending request, the value identifies the date and time by which a response is required before an automated response action will be taken by the registry. For all other status types, the value identifies the date and time when the request was completed.</t> </list> </t> <t></li> </ul> </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <disclose> element that identifies elements that requiring exceptional server-operator handling to allow or restrict disclosure to third parties. SeeSection 2.9 of<xreftarget="RFC5733"/>target="RFC5733" section="2.9" sectionFormat="of" format="default"/> for a description of the child elements contained within the <disclose> element.</t> </list> </t> <t> <figure> <preamble> Example</li> </ul> <t keepWithNext="true"> The following is an example of a <contact> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeContact:contact> <rdeContact:id>sh8013</rdeContact:id> <rdeContact:roid>Csh8013-TEST</rdeContact:roid> <rdeContact:status s="linked"/> <rdeContact:status s="clientDeleteProhibited"/> <rdeContact:postalInfo type="int"> <contact:name>John Doe</contact:name> <contact:org>Example Inc.</contact:org> <contact:addr> <contact:street>123 Example Dr.</contact:street> <contact:street>Suite 100</contact:street> <contact:city>Dulles</contact:city> <contact:sp>VA</contact:sp> <contact:pc>20166-6503</contact:pc> <contact:cc>US</contact:cc> </contact:addr> </rdeContact:postalInfo> <rdeContact:voice x="1234">+1.7035555555</rdeContact:voice> <rdeContact:fax>+1.7035555556</rdeContact:fax> <rdeContact:email>jdoe@example.example</rdeContact:email> <rdeContact:clID>RegistrarX</rdeContact:clID> <rdeContact:crRr client="jdoe">RegistrarX</rdeContact:crRr> <rdeContact:crDate>2009-09-13T08:01:00.0Z</rdeContact:crDate> <rdeContact:upRr client="jdoe">RegistrarX</rdeContact:upRr> <rdeContact:upDate>2009-11-26T09:10:00.0Z</rdeContact:upDate> <rdeContact:trDate>2009-12-03T09:05:00.0Z</rdeContact:trDate> <rdeContact:trnData> <rdeContact:trStatus>pending</rdeContact:trStatus> <rdeContact:reRr client="jstiles">clientW</rdeContact:reRr> <rdeContact:reDate>2011-03-08T19:38:00.0Z</rdeContact:reDate> <rdeContact:acRr client="rmiles">RegistrarX</rdeContact:acRr> <rdeContact:acDate>2011-03-13T23:59:59.0Z</rdeContact:acDate> </rdeContact:trnData> <rdeContact:disclose flag="0"> <contact:voice/> <contact:email/> </rdeContact:disclose> </rdeContact:contact>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> <sectiontitle="<rdeContact:delete> object" anchor="del_contact_object">anchor="del_contact_object" numbered="true" toc="default"> <name><rdeContact:delete> Object</name> <t> The <rdeContact:delete> element contains the id of a contact that was deleted. </t><t> <figure> <preamble> Example<t keepWithNext="true"> The following is an example of an <rdeContact:delete> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rde:deletes> ... <rdeContact:delete> <rdeContact:id>sh8013-TEST</rdeContact:id> <rdeContact:id>co8013-TEST</rdeContact:id> </rdeContact:delete> ... </rde:deletes>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="CSV Model" anchor="contactCsvModel">anchor="contactCsvModel" numbered="true" toc="default"> <name>CSV Model</name> <t>For the CSVModelmodel of the contact object, the <csvContact:contents> child element of the <rde:contents> element is used to hold the new or updated contacts objects for the deposit. The <csvContact:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged contact objects for the deposit. Both the <csvContact:contents> and <csvContact:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute. </t> <t> Differential and Incremental Deposits are based on changes to the contact objects. The updated contact object data under the <csvContact:contents> element is a cascade replace down all of the contact CSV files starting with the parent <xreftarget="csvContactDefinition">"contact"target="csvContactDefinition" format="default">'"contact" CSV FileDefinition</xref>.Definition'</xref>. The child CSV file definitions include a <csvContact:fId parent="true"> field. All the child CSV file definition data for the contact objects in the parent <xreftarget="csvContactDefinition">"contact"target="csvContactDefinition" format="default">'"contact" CSV FileDefinition</xref> MUSTDefinition'</xref> <bcp14>MUST</bcp14> first be deleted and then set using the data in the child CSV files. The deleted contact object data under the <csvContact:deletes> element is a cascade delete starting from the <xreftarget="csvContactDeletesDefinition">"contact"target="csvContactDeletesDefinition" format="default">'"contact" Deletes CSV FileDefinition</xref>.Definition'</xref>. </t> <sectiontitle="<csvContact:contents>" anchor="csvContactContents">anchor="csvContactContents" numbered="true" toc="default"> <name><csvContact:contents></name> <t>The <csvContact:contents> is used to hold the new or updated contact object information for the deposit. The <csvContact:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported contact CSV file definitions. </t> <sectiontitle=""contact"anchor="csvContactDefinition" numbered="true" toc="default"> <name>"contact" CSV FileDefinition" anchor="csvContactDefinition">Definition</name> <t>The "contact" CSV File Definition defines the fields and CSV file references used for the contact object records. </t> <t>The following "csvContact" field elementsMUST<bcp14>MUST</bcp14> be used in the "contact" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fId>">Contains<dl newline="false" spacing="normal"> <dt><csvContact:fId></dt> <dd>Contains the server-unique contact identifier with type="eppcom:clIDType" and isRequired="true".</t> <t hangText="<csvContact:fEmail>">Contains</dd> <dt><csvContact:fEmail></dt> <dd>Contains the contact's email address with type="eppcom:minTokenType" and isRequired="true".</t> </list></t></dd> </dl> <t>The following field elementsMAY<bcp14>MAY</bcp14> be used in the "contact" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fVoice>">Contains<dl newline="false" spacing="normal"> <dt><csvContact:fVoice></dt> <dd>Contains the contact's voice telephone number with type="contact:e164StringType".</t> <t hangText="<csvContact:fVoiceExt>">Contains</dd> <dt><csvContact:fVoiceExt></dt> <dd>Contains the contact's voice telephone number extension with type="token".</t> <t hangText="<csvContact:fFax>">Contains</dd> <dt><csvContact:fFax></dt> <dd>Contains the contact's facsimile telephone number with type="contact:e164StringType".</t> <t hangText="<csvContact:fFaxExt>">Contains</dd> <dt><csvContact:fFaxExt></dt> <dd>Contains the contact's facsimile telephone number extension with type="token".</t> </list></t></dd> </dl> <t>The following "rdeCsv" and "csvRegistrar"fields, MUSTfields <bcp14>MUST</bcp14> be used in the "contact" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fRoid>">The Registry Object IDentifier (ROID)<dl newline="false" spacing="normal"> <dt><rdeCsv:fRoid></dt> <dd>The ROID for the contact object withisRequired="true".</t> <t hangText="<rdeCsv:fClID>isRequired="true".</dd> <dt><rdeCsv:fClID> or<csvRegistrar:fGurid>">A<csvRegistrar:fGurid></dt> <dd> <t>A choiceof: <list style="hanging"> <t hangText="<rdeCsv:fClID>">Identifierof the following: </t> <dl newline="false" spacing="normal"> <dt><rdeCsv:fClID></dt> <dd>Identifier of the sponsoring client with isRequired="true".</t> <t hangText="<csvRegistrar:fGurid>">Contains</dd> <dt><csvRegistrar:fGurid></dt> <dd>Contains theGlobally Unique Registrar Identifier (GURID)GURID assigned by ICANN with type="positiveInteger" and isRequired="true".</t> </list></t> </list></t></dd> </dl> </dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "contact" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fCrRr>">Identifier<dl newline="false" spacing="normal"> <dt><rdeCsv:fCrRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that created the contactobject.</t> <t hangText="<rdeCsv:fCrID>">Identifierobject.</dd> <dt><rdeCsv:fCrID></dt> <dd>Identifier of the client that created the contactobject.</t> <t hangText="<rdeCsv:fUpRr>">Identifierobject.</dd> <dt><rdeCsv:fUpRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that last updated the contactobject.</t> <t hangText="<rdeCsv:fUpID>">Identifierobject.</dd> <dt><rdeCsv:fUpID></dt> <dd>Identifier of the client that last updated the contactobject.</t> <t hangText="<rdeCsv:fCrDate>">Created dateobject.</dd> <dt><rdeCsv:fCrDate></dt> <dd>Date and time of the contactobject.</t> <t hangText="<rdeCsv:fUpDate>">Dateobject creation.</dd> <dt><rdeCsv:fUpDate></dt> <dd>Date and time of the last update to the contact object. This fieldMUST NOT<bcp14>MUST NOT</bcp14> be set if the domain name object has never beenmodified.</t> <t hangText="<rdeCsv:fTrDate>">Datemodified.</dd> <dt><rdeCsv:fTrDate></dt> <dd>Date and time of the last transfer for the contact object. This fieldMUST NOT<bcp14>MUST NOT</bcp14> be set if the domain name object has never beentransferred.</t> </list></t> <t> <figure> <preamble> Exampletransferred.</dd> </dl> <t keepWithNext="true"> The following is an example of a "contact" <csvContact:contacts> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvContact:contents> ... <rdeCsv:csv name="contact"> <rdeCsv:fields> <csvContact:fId/> <rdeCsv:fRoid/> <csvContact:fVoice/> <csvContact:fVoiceExt/> <csvContact:fFax/> <csvContact:fFaxExt/> <csvContact:fEmail/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="8587AA49"> contact-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvContact:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the contact-YYYYMMDD.csv file. The file contains nine object contactrecords. </preamble> <artwork><![CDATA[records: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1admin,Cdomain1admin-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z domain1tech,Cdomain1tech-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z domain1billing,Cdomain1billing-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z domain2admin,Cdomain2admin-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z domain2tech,Cdomain2tech-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z domain2billing,Cdomain2billing-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z xnabc123admin,Cxnabc123admin-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z xnabc123tech,Cxnabc123tech-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY,+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z xnabc123billing,Cxnabc123billing-TEST,+1.7035555555,1234,+1.7035555556,,jdoe@example.example,registrarX,registarX, clientY,2009-09-13T08:01:00.0Z,registarX,clientY, 2009-11-26T09:10:00.0Z]]> </artwork> </figure> </t>+1.7035555556,,jdoe@example.example,registrarX,registrarX, clientY,2009-09-13T08:01:00.0Z,registrarX,clientY, 2009-11-26T09:10:00.0Z ]]></artwork> </section> <sectiontitle=""contactStatuses"anchor="csvContactStatusesDefinition" numbered="true" toc="default"> <name>"contactStatuses" CSV FileDefinition" anchor="csvContactStatusesDefinition">Definition</name> <t>The "contactStatuses" CSV File Definition defines the fields and CSV file references used for the contact object statuses. </t> <t>The following "csvContact" field elements, definedforin the <xreftarget="csvContactDefinition">"contact"target="csvContactDefinition" format="default">'"contact" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "contactStatuses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fId>">Server-unique<dl newline="false" spacing="normal"> <dt><csvContact:fId></dt> <dd>Server-unique contact identifier of status with isRequired="true" andparent=”true".</t> <t hangText="<csvContact:fStatus>">Theparent="true".</dd> <dt><csvContact:fStatus></dt> <dd>The status of the contact with type="contact:statusValueType" andisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "contactStatuses" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fStatusDescription>">The<dl newline="false" spacing="normal"> <dt><rdeCsv:fStatusDescription></dt> <dd>The contact object statusdescriptiondescription, which isfree formfree-form text describing the rationale for thestatus.</t> <t hangText="<rdeCsv:fLang>">Languagestatus.</dd> <dt><rdeCsv:fLang></dt> <dd>Language of the <rdeCsv:fStatusDescription>field.</t> </list></t> <t> <figure> <preamble> Examplefield.</dd> </dl> <t keepWithNext="true"> The following is an example of a "contactStatuses" <csvContact:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvContact:contents> ... <rdeCsv:csv name="contactStatuses"> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="137E13EC"> contactStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvContact:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding contactStatuses-YYYYMMDD.csv file. The file contains the statuses for the nine contactidentifiers. </preamble> <artwork><![CDATA[identifiers: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1admin,ok,, domain1tech,ok,, domain1billing,ok,, domain2admin,ok,, domain2tech,ok,, domain2billing,ok,, xnabc123admin,ok,, xnabc123tech,ok,,xnabc123billing,ok,,]]> </artwork> </figure> </t>xnabc123billing,ok,, ]]></artwork> </section> <sectiontitle=""contactPostal"anchor="csvContactPostalDefinition" numbered="true" toc="default"> <name>"contactPostal" CSV FileDefinition" anchor="csvContactPostalDefinition">Definition</name> <t>The "contactPostal" CSV File Definition defines the fields and CSV file references used for the contact postal info object records. </t> <t>The following "csvContact" field elementsMUST<bcp14>MUST</bcp14> be used in the "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fPostalType>">Contains<dl newline="false" spacing="normal"> <dt><csvContact:fPostalType></dt> <dd>Contains the form of thepostal-addresspostal address information with type="contact:postalLineType" and isRequired="true". This field specifies the form ("int" or "loc"), as defined in <xreftarget="intandloc"/>,target="intandloc" format="default"/>, of the <csvContact:fName>, <csvContact:fOrg>, <csvContact:fStreet>, <csvContact:fCity>, <csvContact:fSp>, <csvContact:fPc>, and <csvContact:fCc> fields.</t> <t hangText="<csvContact:fName>">Contains</dd> <dt><csvContact:fName></dt> <dd>Contains the contact's name of the individual or role represented by the contact with type="contact:postalLineType" and isRequired="true". AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to indicate the localized or internationalized form as defined in <xreftarget="intandloc"/>. </t> <t hangText="<csvContact:fStreet>">Containstarget="intandloc" format="default"/>. </dd> <dt><csvContact:fStreet></dt> <dd>Contains the contact's street address line with type="contact:fPostalLineType". Anindex"index" attribute is required to indicate which street address line the field represents withindex "0"index="0" for the first line and incrementing for each line up toindex "2"index="2" for the third line. AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to indicate the localized or internationalized form as defined in <xreftarget="intandloc"/>. </t> <t hangText="<csvContact:fCity>">Containstarget="intandloc" format="default"/>. </dd> <dt><csvContact:fCity></dt> <dd>Contains the contact's city with type="contact:postalLineType" and isRequired="true". AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to indicate the localized or internationalized form as defined in <xreftarget="intandloc"/>. </t> <t hangText="<csvContact:fCc>">Containstarget="intandloc" format="default"/>. </dd> <dt><csvContact:fCc></dt> <dd>Contains the contact's country code with type="contact:ccType" and isRequired="true". AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to indicate the localized or internationalized form as defined in <xreftarget="intandloc"/>. </t> </list></t>target="intandloc" format="default"/>. </dd> </dl> <t>The following "csvContact" field elementsMAY<bcp14>MAY</bcp14> be used in the "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fOrg>">Contains<dl newline="false" spacing="normal"> <dt><csvContact:fOrg></dt> <dd>Contains the name of the organization with which the contact is affiliated with type="contact:optPostalLineType". AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to indicate the localized or internationalized form as defined in <xreftarget="intandloc"/>. </t> <t hangText="<csvContact:fSp>">Containstarget="intandloc" format="default"/>. </dd> <dt><csvContact:fSp></dt> <dd>Contains the contact's state or province with type="contact:optPostalLineType". AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to indicate the localized or internationalized form as defined in <xreftarget="intandloc"/>. </t> <t hangText="<csvContact:fPc>">Containstarget="intandloc" format="default"/>. </dd> <dt><csvContact:fPc></dt> <dd>Contains the contact's postal code with type="contact:pcType". AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute is used to indicate the localized or internationalized form as defined in <xreftarget="intandloc"/>. </t> </list></t>target="intandloc" format="default"/>. </dd> </dl> <t>The following "csvContact" fields, definedforin the <xreftarget="csvContactDefinition">"contact"target="csvContactDefinition" format="default">'"contact" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "contactPostal" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fId>">Server-unique<dl newline="false" spacing="normal"> <dt><csvContact:fId></dt> <dd>Server-unique contact identifier for the contact object with isRequired="true" andparent=”true".</t> </list></t> <t> <figure> <preamble> Exampleparent="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "contactPostal" <csvContact:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvContact:contents> ... <rdeCsv:csv name="contactPostal"> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fPostalType/> <csvContact:fName/> <csvContact:fOrg/> <csvContact:fStreet index="0"/> <csvContact:fStreet index="1"/> <csvContact:fStreet index="2"/> <csvContact:fCity/> <csvContact:fSp/> <csvContact:fPc/> <csvContact:fCc/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="1456A89C"> contactPostal-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvContact:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the contactPostal-YYYYMMDD.csv file. The file contains nine contact postalrecords. </preamble> <artwork><![CDATA[records: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1admin,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US domain1tech,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US domain1billing,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US domain2admin,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US domain2tech,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US domain2billing,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US xnabc123admin,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US xnabc123tech,int,"John Doe","Example Inc.", "123 Example Dr.","Suite 100",,Reston,VA,20190,US xnabc123billing,int,"John Doe","Example Inc.", "123 Example Dr.","Suite100",,Reston,VA,20190,US]]> </artwork> </figure> </t>100",,Reston,VA,20190,US ]]></artwork> </section> <sectiontitle=""contactTransfer"anchor="csvContactTransferDefinition" numbered="true" toc="default"> <name>"contactTransfer" CSV FileDefinition" anchor="csvContactTransferDefinition">Definition</name> <t>The "contactTransfer" CSV File Definition defines the fields and CSV file references used for the contact object pending and completed transfer records. No additional field elements were added for use in the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element. The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MUSTtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MUST</bcp14> be used in the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fTrStatus>">State<dl newline="false" spacing="normal"> <dt><rdeCsv:fTrStatus></dt> <dd>State of the most recent transfer request withisRequired="true".</t> <t hangText="<rdeCsv:fReRr>">IdentifierisRequired="true".</dd> <dt><rdeCsv:fReRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that requested the transfer withisRequired="true".</t> <t hangText="<rdeCsv:fReDate>">DateisRequired="true".</dd> <dt><rdeCsv:fReDate></dt> <dd>Date and time that the transfer was requested withisRequired="true".</t> <t hangText="<rdeCsv:fAcRr>">IdentifierisRequired="true".</dd> <dt><rdeCsv:fAcRr></dt> <dd>Identifier of the registrar, defined in <xreftarget="registrarObject"/>,target="registrarObject" format="default"/>, of the client that should take or took action withisRequired="true".</t> <t hangText="<rdeCsv:fAcDate>">DateisRequired="true".</dd> <dt><rdeCsv:fAcDate></dt> <dd>Date and time that the transfer action should be taken or has been taken withisRequired="true".</t> </list></t>isRequired="true".</dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fReID>">Identifier<dl newline="false" spacing="normal"> <dt><rdeCsv:fReID></dt> <dd>Identifier of the client that requested thetransfer.</t> <t hangText="<rdeCsv:fAcID>">Identifiertransfer.</dd> <dt><rdeCsv:fAcID></dt> <dd>Identifier of the client that should take or took action fortransfer.</t> </list></t>transfer.</dd> </dl> <t>The following "csvContact" fields, defined for the <xreftarget="csvContactDefinition">"contact"target="csvContactDefinition" format="default">'"contact" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "contactTransfer" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fId>">Server-unique<dl newline="false" spacing="normal"> <dt><csvContact:fId></dt> <dd>Server-unique contact identifier for the contact object withisRequired="true".</t> </list></t> <t> <figure> <preamble> ExampleisRequired="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "contactTransfer" <csvContact:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvContact:contents> ... <rdeCsv:csv name="contactTransfer"> <rdeCsv:fields> <csvContact:fId parent="true"/> <rdeCsv:fTrStatus/> <rdeCsv:fReRr/> <rdeCsv:fReID/> <rdeCsv:fReDate/> <rdeCsv:fAcRr/> <rdeCsv:fAcID/> <rdeCsv:fAcDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="788D308E"> contactTransfer-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvContact:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the contactTransfer-YYYYMMDD.csv file. The file contains one contact transfer record in pendingstatus. </preamble> <artwork><![CDATA[ xnabc123admin,clientApproved,registrarX,clientX, 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z]]> </artwork> </figure>status: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ xnabc123admin,clientApproved,registrarX,clientX, 2011-04-08T19:38:00.0Z,registrarY,clientY,2011-04-09T20:38:00.0Z ]]></artwork> </section> <sectiontitle=""contactDisclose"anchor="csvContactDiscloseDefinition" numbered="true" toc="default"> <name>"contactDisclose" CSV FileDefinition" anchor="csvContactDiscloseDefinition">Definition</name> <t>The "contactDisclose" CSV File Definition defines the fields and CSV file references used for the contact disclose object records.</t> <t>The following "csvContact" field elementsMAY<bcp14>MAY</bcp14> be used in the "contactDisclose" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fDiscloseFlag>">Contains<dl newline="false" spacing="normal"> <dt><csvContact:fDiscloseFlag></dt> <dd>Contains flag with a value of "true" or "1" (one) notes the preference to allow disclosure of the specified elements as an exception to the stated data-collection policy. A value of "false" or "0" (zero) notes a client preference 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 preferences based on the <csvContact:fDiscloseFlag> field.</t> <t hangText="<csvContact:fDiscloseNameLoc>">Exceptional</dd> <dt><csvContact:fDiscloseNameLoc></dt> <dd>Exceptional disclosure preference flag for the localized form of the contact name with type="boolean".</t> <t hangText="<csvContact:fDiscloseNameInt>">Exceptional</dd> <dt><csvContact:fDiscloseNameInt></dt> <dd>Exceptional disclosure preference flag for the internationalized form of the contact name with type="boolean".</t> <t hangText="<csvContact:fDiscloseOrgLoc>">Exceptional</dd> <dt><csvContact:fDiscloseOrgLoc></dt> <dd>Exceptional disclosure preference flag for the localized form of the contact organization with type="boolean".</t> <t hangText="<csvContact:fDiscloseOrgInt>">Exceptional</dd> <dt><csvContact:fDiscloseOrgInt></dt> <dd>Exceptional disclosure preference flag for the internationalized form of the contact organization with type="boolean".</t> <t hangText="<csvContact:fDiscloseAddrLoc>">Exceptional</dd> <dt><csvContact:fDiscloseAddrLoc></dt> <dd>Exceptional disclosure preference flag for the localized form of the contact address with type="boolean".</t> <t hangText="<csvContact:fDiscloseAddrInt>">Exceptional</dd> <dt><csvContact:fDiscloseAddrInt></dt> <dd>Exceptional disclosure preference flag for the internationalized form of the contact address with type="boolean".</t> <t hangText="<csvContact:fDiscloseVoice>">Exceptional</dd> <dt><csvContact:fDiscloseVoice></dt> <dd>Exceptional disclosure preference flag of the contact voice telephone number with type="boolean".</t> <t hangText="<csvContact:fDiscloseFax>">Exceptional</dd> <dt><csvContact:fDiscloseFax></dt> <dd>Exceptional disclosure preference flag of the contact facsimile telephone number with type="boolean".</t> <t hangText="<csvContact:fDiscloseEmail>">Exceptional</dd> <dt><csvContact:fDiscloseEmail></dt> <dd>Exceptional disclosure preference flag of the contact email address with type="boolean".</t> </list></t></dd> </dl> <t>The following "csvContact" fields, defined for the <xreftarget="csvContactDefinition">"contact"target="csvContactDefinition" format="default">'"contact" CSV FileDefinition</xref>, MUSTDefinition'</xref>, <bcp14>MUST</bcp14> be used in the "contactDisclose" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fId>">Server-unique<dl newline="false" spacing="normal"> <dt><csvContact:fId></dt> <dd>Server-unique contact identifier for the contact object withisRequired="true".</t> </list></t> <t> <figure> <preamble> ExampleisRequired="true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "contactDisclose" <csvContact:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvContact:contents> ... <rdeCsv:csv name="contactDisclose"> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fDiscloseFlag/> <csvContact:fDiscloseNameLoc/> <csvContact:fDiscloseNameInt/> <csvContact:fDiscloseOrgLoc/> <csvContact:fDiscloseOrgInt/> <csvContact:fDiscloseAddrLoc/> <csvContact:fDiscloseAddrInt/> <csvContact:fDiscloseVoice/> <csvContact:fDiscloseFax/> <csvContact:fDiscloseEmail/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="1141EFD4"> contactDisclose-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvContact:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the contactDisclose-YYYYMMDD.csv file. The file contains one disclosure records, disabling disclosure of voice, fax, andemail. </preamble> <artwork><![CDATA[ xnabc123admin,0,0,0,0,0,0,0,1,1,1]]> </artwork> </figure>email: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ xnabc123admin,0,0,0,0,0,0,0,1,1,1 ]]></artwork> </section> </section> <sectiontitle="<csvContact:deletes>" anchor="csvContactDeletes">anchor="csvContactDeletes" numbered="true" toc="default"> <name><csvContact:deletes></name> <t> The <csvContact:deletes> is used to hold the deleted contact objects in a Differential or Incremental Deposit. All the contact object data is deleted as part of a cascade delete. The <csvContact:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported contact deletes CSV file definition. </t> <sectiontitle=""contact"anchor="csvContactDeletesDefinition" numbered="true" toc="default"> <name>"contact" Deletes CSV FileDefinition" anchor="csvContactDeletesDefinition">Definition</name> <t> The following "csvContact" field elementsMUST<bcp14>MUST</bcp14> be used in the deletes "contact" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fId>">Contains<dl newline="false" spacing="normal"> <dt><csvContact:fId></dt> <dd>Contains the server-unique contact identifier with type="eppcom:clIDType" and isRequired="true".</t> </list></t> <t> <figure> <preamble> Example</dd> </dl> <t keepWithNext="true"> The following is an example of a "contact" <csvContact:deletes> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvContact:deletes> ... <rdeCsv:csv name="contact"> <rdeCsv:fields> <csvContact:fId/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="0C4B70DC"> contact-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvContact:deletes>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the contact-delete-YYYYMMDD.csv file. The file contains six contactrecords. </preamble> <artwork><![CDATA[records: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ domain1admin domain1tech domain1billing domain2admin domain2techdomain2billing]]> </artwork> </figure> </t>domain2billing ]]></artwork> </section> </section> </section> </section> <sectiontitle="Registrar Object" anchor="registrarObject">anchor="registrarObject" numbered="true" toc="default"> <name>Registrar Object</name> <t> The registrar object represents the sponsoring client for otherobjects,objects and is typically referred to as the sponsoring registrar. The registrar object supports both the XMLModelmodel and the CSVModel,model, defined in <xreftarget="models"/>.target="models" format="default"/>. The elements used for both models are defined in the following sections. </t> <sectiontitle="XML Model" anchor="registrarXmlModel">anchor="registrarXmlModel" numbered="true" toc="default"> <name>XML Model</name> <t>There are two elements used in the data escrow of the registrar objects for the XML model including the<rdeRegistrar:registrar>,<rdeRegistrar:registrar> element, under the <rdeRegistrar:contents> element, and the <rdeRegistrar:delete> element, under the <rde:deletes> element. </t> <t>AAn <rdeRegistrar:registrar> element substitutes for the <rdeRegistrar:abstractRegistrar> abstract element todefinecreate a concrete definition of a registrar. The <rdeRegistrar:abstractRegistrar> element can be replaced by other domain definitions using the XML schema substitution groups feature. </t> <sectiontitle="<rdeRegistrar:registrar> element" anchor="rdeRegistrarElement">anchor="rdeRegistrarElement" numbered="true" toc="default"> <name><rdeRegistrar:registrar> Element</name> <t> The <registrar> element contains the following child elements: </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> An <id> element that contains theRegistry-uniqueregistry-unique identifier of the registrar object. This <id> has a superordinate relationship to a subordinate <clID>,<crRr><crRr>, or <upRr> of domain,contactcontact, and host objects.</t> <t></li> <li> An <name> element that contains the name of the registrar.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <gurid> element that contains theGlobally Unique Registrar Identifier (GURID)GURID assigned by ICANN.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <status> element that contains the operational status of the registrar. Possible values are: ok,readonlyreadonly, and terminated.</t></li> <li> <t> One or twoOPTIONAL<bcp14>OPTIONAL</bcp14> <postalInfo> elements that containpostal-postal address information. Two elements are provided so that address information can be provided in both internationalized and localized forms; a "type" attribute is used to identify the two forms. If an internationalized form (type="int") is provided, element contentMUST<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, element contentMAY<bcp14>MAY</bcp14> be represented in unrestricted UTF-8. The <postalInfo> element contains the following child elements:<list style="symbols"></t> <ul spacing="normal"> <li> <t> A <addr> element that contains address information associated with the registrar. The <addr> element contains the following child elements:<list style="symbols"> <t></t> <ul spacing="normal"> <li> One, two, or threeOPTIONAL<bcp14>OPTIONAL</bcp14> <street> elements that contain theregistrar'sregistrar's street address.</t> <t></li> <li> A <city> element that contains theregistrar'sregistrar's city.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <sp> element that contains theregistrar'sregistrar's state or province.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <pc> element that contains theregistrar'sregistrar's postal code.</t> <t></li> <li> A <cc> element that contains theregistrar'sregistrar's country code.</t> </list> </t> </list> </t> <t></li> </ul> </li> </ul> </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <voice> element that contains theregistrar'sregistrar's voice telephone number.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <fax> element that contains theregistrar'sregistrar's facsimile telephone number.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <email> element that contains theregistrar'sregistrar's email address.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <url> element that contains theregistrar'sregistrar's URL.</t></li> <li> <t> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <whoisInfo>elementselement that containswhoisWHOIS information. The <whoisInfo> element contains the following child elements:<list style="symbols"> <t></t> <ul spacing="normal"> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <name> element that contains the name of the registrar WHOIS server listening on TCP port 43 as specified in <xreftarget="RFC3912"/>. </t> <t>target="RFC3912" format="default"/>. </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <url> element that contains the name of the registrar WHOIS server listening on TCP port 80/443.</t> </list> </t> <t></li> </ul> </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crDate> element that contains the creation date and time ofregistrar-object creation. </t> <t>the registrar object. </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <upDate> element that contains the date and time of the most recentregistrar-object modification.modification of the registrar object. This elementMUST NOT<bcp14>MUST NOT</bcp14> be present if theregistrar-objectregistrar object has never been modified.</t> </list> </t> <t> <figure> <preamble> Example</li> </ul> <t keepWithNext="true"> The following is an example of a <registrar> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeRegistrar:registrar> <rdeRegistrar:id>RegistrarX</rdeRegistrar:id> <rdeRegistrar:name>Registrar X</rdeRegistrar:name> <rdeRegistrar:gurid>8</rdeRegistrar:gurid> <rdeRegistrar:status>ok</rdeRegistrar:status> <rdeRegistrar:postalInfo type="int"> <rdeRegistrar:addr> <rdeRegistrar:street>123 Example Dr.</rdeRegistrar:street> <rdeRegistrar:street>Suite 100</rdeRegistrar:street> <rdeRegistrar:city>Dulles</rdeRegistrar:city> <rdeRegistrar:sp>VA</rdeRegistrar:sp> <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc> <rdeRegistrar:cc>US</rdeRegistrar:cc> </rdeRegistrar:addr> </rdeRegistrar:postalInfo> <rdeRegistrar:voice x="1234">+1.7035555555</rdeRegistrar:voice> <rdeRegistrar:fax>+1.7035555556</rdeRegistrar:fax> <rdeRegistrar:email>jdoe@example.example</rdeRegistrar:email> <rdeRegistrar:url>http://www.example.example</rdeRegistrar:url> <rdeRegistrar:whoisInfo> <rdeRegistrar:name>whois.example.example</rdeRegistrar:name> <rdeRegistrar:url>http://whois.example.example</rdeRegistrar:url> </rdeRegistrar:whoisInfo> <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z</rdeRegistrar:crDate> <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z</rdeRegistrar:upDate> </rdeRegistrar:registrar>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> <sectiontitle="<rdeRegistrar:delete> object" anchor="del_registrar_object">anchor="del_registrar_object" numbered="true" toc="default"> <name><rdeRegistrar:delete> Object</name> <t> The <rdeRegistrar:delete> element contains the id of a registrar that was deleted. </t><t> <figure> <preamble> Example<t keepWithNext="true"> The following is an example of <rdeRegistrar:delete> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rde:deletes> ... <rdeRegistrar:delete> <rdeRegistrar:id>agnt0001-TEST</rdeRegistrar:id> </rdeRegistrar:delete> ... </rde:deletes>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="CSV Model" anchor="registrarCsvModel">anchor="registrarCsvModel" numbered="true" toc="default"> <name>CSV Model</name> <t>For the CSVModelmodel of the registrar object, the <csvRegistrar:contents> child element of the <rde:contents> element is used to hold the new or updated registrar objects for the deposit. The <csvRegistrar:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged registrar objects for the deposit. Both the <csvRegistrar:contents> and <csvRegistrar:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute. </t> <t> Differential and Incremental Deposits are based on changes to the registrar objects. The updated registrar object data under the <csvContact:contents> element is a cascade replace down all of the registrar CSV files starting with the parent <xreftarget="csvRegistrarDefinition">"registrar"target="csvRegistrarDefinition" format="default">'"registrar" CSV FileDefinition</xref>.Definition'</xref>. The child CSV file definitions include a <csvRegistrar:fId parent="true"> field. All the child CSV file definition data for the registrar objects in the parent <xreftarget="csvRegistrarDefinition">"registrar"target="csvRegistrarDefinition" format="default">'"registrar" CSV FileDefinition</xref> MUSTDefinition'</xref> <bcp14>MUST</bcp14> first be deleted and then set using the data in the child CSV files. The deleted registrar object data under the <csvRegistrar:deletes> element is a cascade delete starting from the <xreftarget="csvRegistrarDeletesDefinition">"registrar"target="csvRegistrarDeletesDefinition" format="default">'"registrar" Deletes CSV FileDefinition</xref>.Definition'</xref>. </t> <sectiontitle="<csvRegistrar:contents>" anchor="csvRegistrarContents">anchor="csvRegistrarContents" numbered="true" toc="default"> <name><csvRegistrar:contents></name> <t>The <csvRegistrar:contents> is used to hold the new or updated registrar object information for the deposit. The <csvRegistrar:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supportedcontactregistrar CSV file definitions. </t> <sectiontitle=""registrar"anchor="csvRegistrarDefinition" numbered="true" toc="default"> <name>"registrar" CSV FileDefinition" anchor="csvRegistrarDefinition">Definition</name> <t>The "registrar" CSV File Definition defines the fields and CSV file references used for the registrar object records.</t> <t>The following "csvRegistrar" field elementsMUST<bcp14>MUST</bcp14> be used in the "registrar" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvRegistrar:fId><dl newline="false" spacing="normal"> <dt><csvRegistrar:fId> or<csvRegistrar:fGurid>">A<csvRegistrar:fGurid></dt> <dd> <t>A choiceof: <list style="hanging"> <t hangText="<csvRegistrar:fId>">Containsof the following: </t> <dl newline="false" spacing="normal"> <dt><csvRegistrar:fId></dt> <dd>Contains the server-unique registrar identifier with type="eppcom:clIDType" and isRequired="true".</t> <t hangText="<csvRegistrar:fGurid>">Contains</dd> <dt><csvRegistrar:fGurid></dt> <dd>Contains theGlobally Unique Registrar Identifier (GURID)GURID assigned by ICANN with type="positiveInteger" and isRequired="true".</t> </list></t> <t hangText="<csvRegistrar:fName>">Contains</dd> </dl> </dd> <dt><csvRegistrar:fName></dt> <dd>Contains the name of the registrar with type="normalizedString" and isRequired="true".</t> </list></t></dd> </dl> <t>The following field elementsMAY<bcp14>MAY</bcp14> be used in the "registrar" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvRegistrar:fStatus>">Contains<dl newline="false" spacing="normal"> <dt><csvRegistrar:fStatus></dt> <dd>Contains the status of the registrar with type="csvRegistrar:statusValueType".</t> <t hangText="<csvRegistrar:fGurid>">Contains</dd> <dt><csvRegistrar:fGurid></dt> <dd>Contains the ID assigned by ICANN with type="positiveInteger". This field is included in this section in addition to the section above to support optionally providing the <csvRegistrar:fGurid> field when the <csvRegistrar:fId> field isused.</t> <t hangText="<csvRegistrar:fWhoisUrl>">Containsused.</dd> <dt><csvRegistrar:fWhoisUrl></dt> <dd>Contains the Whois URL of the registrar with type="anyURI".</t> </list></t></dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "registrar" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fCrDate>">Created date<dl newline="false" spacing="normal"> <dt><rdeCsv:fCrDate></dt> <dd>Date and time of the registrarobject.</t> <t hangText="<rdeCsv:fUpDate>">Dateobject creation.</dd> <dt><rdeCsv:fUpDate></dt> <dd>Date and time of the last update to the registrar object. This fieldMUST NOT<bcp14>MUST NOT</bcp14> be set if the domain name object has never beenmodified.</t> <t hangText="<rdeCsv:fUrl>">URLmodified.</dd> <dt><rdeCsv:fUrl></dt> <dd>URL for the registrar web homepage.</t> </list></t>page.</dd> </dl> <t>The following "csvContact" fields, defined insection<xreftarget="contactObject">Contact Object</xref>, MAYtarget="contactObject" format="default">'Contact Object'</xref>, <bcp14>MAY</bcp14> be used in the "registrar" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvContact:fStreet>">Registrar<dl newline="false" spacing="normal"> <dt><csvContact:fStreet></dt> <dd>Registrar street address line with an "index" attribute that represents the order of the street address line from "0" to "2". AnOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in <xreftarget="intandloc"/>.</t> <t hangText="<csvContact:fCity>">Registrartarget="intandloc" format="default"/>.</dd> <dt><csvContact:fCity></dt> <dd>Registrar city with anOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in <xreftarget="intandloc"/>.</t> <t hangText="<csvContact:fCc>">Registrartarget="intandloc" format="default"/>.</dd> <dt><csvContact:fCc></dt> <dd>Registrar country code with anOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in <xreftarget="intandloc"/>.</t> <t hangText="<csvContact:fEmail>">Registrartarget="intandloc" format="default"/>.</dd> <dt><csvContact:fEmail></dt> <dd>Registrar email address. The attribute "isRequired"MUST<bcp14>MUST</bcp14> equal"false".</t> <t hangText="<csvContact:fSp>">Registrar"false".</dd> <dt><csvContact:fSp></dt> <dd>Registrar state or province with anOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in <xreftarget="intandloc"/>.</t> <t hangText="<csvContact:fPc>">Registrartarget="intandloc" format="default"/>.</dd> <dt><csvContact:fPc></dt> <dd>Registrar postal code with anOPTIONAL<bcp14>OPTIONAL</bcp14> "isLoc" attribute that is used to indicate the localized or internationalized form, as defined in <xreftarget="intandloc"/>.</t> <t hangText="<csvContact:fVoice>">Registrartarget="intandloc" format="default"/>.</dd> <dt><csvContact:fVoice></dt> <dd>Registrar voice telephonenumber.</t> <t hangText="<csvContact:fVoiceExt>">Registrarnumber.</dd> <dt><csvContact:fVoiceExt></dt> <dd>Registrar voice telephone numberextension.</t> <t hangText="<csvContact:fFax>">Registrarextension.</dd> <dt><csvContact:fFax></dt> <dd>Registrar facsimile telephonenumber.</t> <t hangText="<csvContact:fFaxExt>">Registrarnumber.</dd> <dt><csvContact:fFaxExt></dt> <dd>Registrar facsimile telephone numberextension.</t> </list></t> <t> <figure> <preamble> Exampleextension.</dd> </dl> <t keepWithNext="true"> The following is an example of a "registrar" <csvRegistrar:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvRegistrar:contents> ... <rdeCsv:csv name="registrar"> <rdeCsv:fields> <csvRegistrar:fId/> <csvRegistrar:fName isLoc="false"/> <csvRegistrar:fGurid/> <csvRegistrar:fStatus/> <csvContact:fStreet isLoc="false" index="0"/> <csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="2"/> <csvContact:fCity isLoc="false"/> <csvContact:fSp isLoc="false" /> <csvContact:fPc isLoc="false" /> <csvContact:fCc isLoc="false"/> <csvContact:fVoice/> <csvContact:fVoiceExt/> <csvContact:fFax/> <csvContact:fFaxExt/> <csvContact:fEmail isRequired="false"/> <rdeCsv:fUrl/> <csvRegistrar:fWhoisUrl/> <rdeCsv:fCrDate/> <rdeCsv:fUpDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="57F6856F"> registrar-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvRegistrar:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the registrar-YYYYMMDD.csv file. The file contains one registrarrecord. </preamble> <artwork><![CDATA[record: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ registrarX,"Example Inc.",8,ok,"123 Example Dr.", "Suite 100",,Dulles,VA,20166-6503,US,+1.7035555555,1234, +1.7035555556,,jdoe@example.example,http://www.example.example, http://whois.example.example,2005-04-23T11:49:00.0Z,2009-02-17T17:51:00.0Z]]> </artwork> </figure> </t>2009-02-17T17:51:00.0Z ]]></artwork> </section> </section> <sectiontitle="<csvRegistrar:deletes>" anchor="csvRegistrarDeletes">anchor="csvRegistrarDeletes" numbered="true" toc="default"> <name><csvRegistrar:deletes></name> <t> The <csvRegistrar:deletes> is used to hold the deleted registrar objects in a Differential or Incremental Deposit. All the registrar object data is deleted as part of a cascade delete. The <csvRegistrar:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported registrar deletes CSV file definition. </t> <sectiontitle=""registrar"anchor="csvRegistrarDeletesDefinition" numbered="true" toc="default"> <name>"registrar" Deletes CSV FileDefinition" anchor="csvRegistrarDeletesDefinition">Definition</name> <t> The following "csvRegistrar" field elementsMUST<bcp14>MUST</bcp14> be used in the deletes "registrar" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvRegistrar:fId><dl newline="false" spacing="normal"> <dt><csvRegistrar:fId> or<csvRegistrar:fGurid>">A<csvRegistrar:fGurid></dt> <dd> <t>A choiceof: <list style="hanging"> <t hangText="<csvRegistrar:fId>">Containsof the following: </t> <dl newline="false" spacing="normal"> <dt><csvRegistrar:fId></dt> <dd>Contains the server-unique registrar identifier with type="eppcom:clIDType" and isRequired="true".</t> <t hangText="<csvRegistrar:fGurid>">Contains</dd> <dt><csvRegistrar:fGurid></dt> <dd>Contains theGlobally Unique Registrar Identifier (GURID)GURID assigned by ICANN with type="positiveInteger". The attribute "isRequired"MUST<bcp14>MUST</bcp14> equal "true".</t> </list></t> </list></t> <t> <figure> <preamble> Example</dd> </dl> </dd> </dl> <t keepWithNext="true"> The following is an example of a "registrar" <csvRegistrar:deletes> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvRegistrar:deletes> ... <rdeCsv:csv name="registrar"> <rdeCsv:fields> <csvRegistrar:fId/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="5CB20A52"> registrar-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvRegistrar:deletes>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the registrar-delete-YYYYMMDD.csv file. The file contains one registrarrecord. </preamble> <artwork><![CDATA[ registrarZ]]> </artwork> </figure>record: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ registrarZ ]]></artwork> </section> </section> </section> </section> <sectiontitle="IDNnumbered="true" toc="default"> <name>IDN Table ReferenceObject">Object</name> <t> The Internationalized Domain Names (IDN) table reference object is a pseudo-object that is used to provide a short reference to the IDNTabletable andPolicypolicy used in IDN registrations. The IDN reference object supports both the XML and the CSVModel,model, defined inthe<xreftarget="models">Models</xref> section.target="models" format="default">'Models'</xref>. The elements used for both models are defined in the following sections. </t> <sectiontitle="XML Model" anchor="idnXmlModel">anchor="idnXmlModel" numbered="true" toc="default"> <name>XML Model</name> <t>There is one element used in the data escrow of the IDN table reference objects for the XMLmodelmodel, and that is the <rdeIDN:idnTableRef>, under the <rde:contents> element. </t> <sectiontitle="<rdeIDN:idnTableRef> object" anchor="idnTableRef_object">anchor="idnTableRef_object" numbered="true" toc="default"> <name><rdeIDN:idnTableRef> Object</name> <t> The <rdeIDN:idnTableRef> contains the following elements. An "id" attribute is used to specify an identifier for the IDN table. </t><t> <list style="symbols"> <t> An<ul spacing="normal"> <li> A <url> element that contains the URL of the IDN table that is being referenced.</t> <t></li> <li> A <urlPolicy> element that contains the URL of the IDN policy document. If IDN variants are generated algorithmically, the policy documentMUST<bcp14>MUST</bcp14> define the algorithm and the state of theimplicitimplicitly generated IDN variants. For a list of suggested states for implicit IDN variants, please see <xreftarget="variantTLDsReport"/>. </t> </list> </t> <t> <figure> <preamble> Exampletarget="variantTLDsReport" format="default"/>. </li> </ul> <t keepWithNext="true"> The following is an example of <idnTableRef> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeIDN:idnTableRef id="pt-BR"> <rdeIDN:url> http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html </rdeIDN:url> <rdeIDN:urlPolicy> http://registro.br/dominio/regras.html </rdeIDN:urlPolicy> </rdeIDN:idnTableRef>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="CSV Model" anchor="idnCsvModel">anchor="idnCsvModel" numbered="true" toc="default"> <name>CSV Model</name> <t> The IDN domain names, defined in <xreftarget="domainNameObject"/>, MAYtarget="domainNameObject" format="default"/>, <bcp14>MAY</bcp14> have references to the IDN language identifier using the <rdeCsv:fIdnTableId> field element. The IDN table reference object defines the mapping of a language identifier to a language table URL. 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 objectisare defined in this section. The <csvIDN:contents> child element of the <rde:contents> element is used to hold the new or updated IDN table reference objects for the deposit. The <csvIDN:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged IDN table reference objects for the deposit. Both the <csvIDN:contents> and <csvIDN:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute. </t> <sectiontitle="<csvIDN:contents>" anchor="csvIDNContents">anchor="csvIDNContents" numbered="true" toc="default"> <name><csvIDN:contents></name> <t>The <csvIDN:contents> is used to hold the new or updated IDN table reference object information for the deposit. The <csvIDN:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported IDN table reference CSV file definitions. </t> <sectiontitle=""idnLanguage"anchor="csvIDNDefinition" numbered="true" toc="default"> <name>"idnLanguage" CSV FileDefinition" anchor="csvIDNDefinition">Definition</name> <t>The "idnLanguage" CSV File Definition defines the fields and CSV file references used for the IDN table reference object records. </t> <t>The following "rdeCsv" fields, defined in <xreftarget="csvCommonFieldElements"/>, MUSTtarget="csvCommonFieldElements" format="default"/>, <bcp14>MUST</bcp14> be used in the "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fIdnTableId>">The<dl newline="false" spacing="normal"> <dt><rdeCsv:fIdnTableId></dt> <dd>The language identifier that matches the values for the <rdeCsv:fIdnTableId> field element in the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>Definition'</xref> files. The attribute "isRequired"MUST<bcp14>MUST</bcp14> equal"true".</t> <t hangText="<rdeCsv:fUrl>">URL"true".</dd> <dt><rdeCsv:fUrl></dt> <dd>URL that defines the character code points that can be used for <csvDomain:fName> field in the"domain"<xref target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition <xref target="csvDomainDefinition"/>Definition'</xref> files. The attribute "isRequired"MUST<bcp14>MUST</bcp14> equal"true".</t> </list></t> <t> <figure> <preamble> Example"true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "idnLanguage" <csvIDN:contents> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvIDN:contents> ... <rdeCsv:csv name="idnLanguage" sep=","> <rdeCsv:fields> <rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fUrl isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D6B0424F"> idnLanguage-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvIDN:contents>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding idnLanguage-YYYYMMDD.csv file. The file contains two IDN languagerecords. </preamble> <artwork><![CDATA[records: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ LANG-1, http://www.iana.org/domains/idn-tables/tables/test_tab1_1.1.txt LANG-2,http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt]]> </artwork></figure> </t>http://www.iana.org/domains/idn-tables/tables/test_tab2_1.1.txt ]]></artwork> </section> </section> <sectiontitle="<csvIDN:deletes>" anchor="csvIDNDeletes">anchor="csvIDNDeletes" numbered="true" toc="default"> <name><csvIDN:deletes></name> <t> The <csvIDN:deletes> is used to hold the deleted IDN table reference objects in a Differential or Incremental Deposit. The <csvIDN:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported IDN table reference deletes CSV file definition. </t> <sectiontitle=""idnLanguage"anchor="csvIDNDeletesDefinition" numbered="true" toc="default"> <name>"idnLanguage" Deletes CSV FileDefinition" anchor="csvIDNDeletesDefinition">Definition</name> <t> The following "idnLanguage" field elementsMUST<bcp14>MUST</bcp14> be used in the deletes "idnLanguage" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fIdnTableId>">The<dl newline="false" spacing="normal"> <dt><rdeCsv:fIdnTableId></dt> <dd>The language identifier that matches the values for the <rdeCsv:fIdnTableId> field element in the <xreftarget="csvDomainDefinition">"domain"target="csvDomainDefinition" format="default">'"domain" CSV FileDefinition</xref>Definition'</xref> files. The attribute "isRequired"MUST<bcp14>MUST</bcp14> equal"true".</t> </list></t> <t> <figure> <preamble> Example"true".</dd> </dl> <t keepWithNext="true"> The following is an example of a "idnLanguage" <csvIDN:deletes> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvIDN:deletes> ... <rdeCsv:csv name="idnLanguage"> <rdeCsv:fields> <rdeCsv:fIdnTableId isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="4A28A569"> idnLanguage-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvIDN:deletes>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the idnLanguage-delete-YYYYMMDD.csv file. The file contains one IDN languagerecord. </preamble> <artwork><![CDATA[ LANG-2]]> </artwork> </figure>record: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ LANG-2 ]]></artwork> </section> </section> </section> </section> <sectiontitle="NNDN Object">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,withheldwithheld, or mirrored) IDN variants. </t> <t> DomainName Registriesname registries may maintain domain names without their being persisted as domain objects in the registry system, for example, a list of reserved names not available for registration. The NNDN is a lightweight domain-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 object, but not both. </t> <t> The NNDN object supports both the XML and the CSVModel,model, defined inthe<xreftarget="models">Models</xref> section.target="models" format="default">'Models'</xref>. The elements used for both models are defined in the following sections. </t> <sectiontitle="XML Model" anchor="nndnXmlModel">anchor="nndnXmlModel" numbered="true" toc="default"> <name>XML Model</name> <t>There are two elements used in the data escrow of the NNDN objects for the XML model including the<rdeNNDN:NNDN>,<rdeNNDN:NNDN> element, under the <rde:contents> element, and the <rdeNNDN:delete> element, under the <rde:deletes> element. </t> <t>AAn <rdeNNDN:NNDN> element substitutes for the <rdeNNDN:abstractNNDN> abstract element todefinecreate a concrete definition of an NNDN. The <rdeNNDN:abstractDomain> element can be replaced by other NNDN definitions using the XML schema substitution groups feature. </t> <sectiontitle="<rdeNNDN:NNDN> object" anchor="ndn_object">anchor="ndn_object" numbered="true" toc="default"> <name><rdeNNDN:NNDN> Object</name> <t> The <rdeNNDN:NNDN> element contains the following child elements: </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> An <aName> element that contains thefully-qualifiedfully qualified name of the NNDN. ForIDNsIDNs, theA-LabelA-label is used (see <xreftarget="RFC5891"/>, Section 4.4). </t> <t>target="RFC5891" section="4.4" sectionFormat="comma" format="default"/>). </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <uName> element that contains thefully-qualifiedfully qualified name of the NNDN in the Unicode character set. ItMUST<bcp14>MUST</bcp14> be provided if available.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <idnTableId> element that references the IDNTabletable used for the NNDN. This corresponds to the"id""id" attribute of the <idnTableRef> element. This elementMUST<bcp14>MUST</bcp14> be present if the NNDN is an IDN.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <originalName> element is used to indicate that the NNDN is used for an IDN variant. This element contains the domain name used to generate the IDN variant.</t></li> <li> <t> A <nameState> element that indicates the state of the NNDN: blocked,withheldwithheld, or mirrored.<list style="symbols"> <t></t> <ul spacing="normal"> <li> If an NNDN is considered undesirable for registration (i.e., unavailable for allocation to anyone), then the NNDN will be tagged as "blocked".</t> <t></li> <li> If an NNDN is considered a potential registration 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 IDN variant.</t> <t></li> <li> If an NNDN is considered a mirrored IDN variant of a domain name object, then the NNDN will be tagged as "mirrored". AmirroringNS"mirroringNS" attribute is used to specify if the mirrored IDN variant uses the NS mirror mechanism, meaning that the activated variant domain name (i.e., NNDN) is delegated in the DNS using the same NS records as in the <originalName>. The default value ofmirroringNS"mirroringNS" is true. If another mechanism such as DNAME <xref target="RFC6672" format="default"/> is used, the value ofmirroringNSthe "mirroringNS" attributeMUST<bcp14>MUST</bcp14> be false.</t> </list> </t> <t></li> </ul> </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <crDate> element that contains the date and time of the NNDN object creation.</t> </list> </t> <t> <figure> <preamble> Example</li> </ul> <t keepWithNext="true"> The following is an example of an <rdeNNDN:NNDN> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeNNDN:NNDN> <rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName> <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId> <rdeNNDN:originalName>example.example</rdeNNDN:originalName> <rdeNNDN:nameState>withheld</rdeNNDN:nameState> <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate> </rdeNNDN:NNDN>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> <sectiontitle="<rdeNNDN:delete> object" anchor="delNDNObject">anchor="delNDNObject" numbered="true" toc="default"> <name><rdeNNDN:delete> Object</name> <t> The <rdeNNDN:delete> element contains the NNDN that was deleted, i.e., the <aName>. </t><t> <figure> <preamble> Example<t keepWithNext="true"> The following is an example of an <rdeNNDN::delete> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rde:deletes> ... <rdeNNDN:delete> <rdeNNDN:aName>xn--pingino-q2a.example</rdeNNDN:aName> </rdeNNDN:delete> ... </rde:deletes>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="CSV Model" anchor="nndnCsvModel">anchor="nndnCsvModel" numbered="true" toc="default"> <name>CSV Model</name> <t>For the CSVModelmodel of the NNDN object, the <csvNNDN:contents> child element of the <rde:contents> element is used to hold the new or updated NNDN objects for the deposit. The <csvNNDN:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged NNDN objects for the deposit. Both the <csvNNDN:contents> and <csvNNDN:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute. </t> <sectiontitle="<csvNNDN:contents>" anchor="csvNNDNContents">anchor="csvNNDNContents" numbered="true" toc="default"> <name><csvNNDN:contents></name> <t>The <csvNNDN:contents> is used to hold the new or updated NNDN object information for the deposit. The <csvNNDN:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported NNDN CSV file definitions. </t> <sectiontitle=""NNDN"anchor="csvNNDNDefinition" numbered="true" toc="default"> <name>"NNDN" CSV FileDefinition" anchor="csvNNDNDefinition">Definition</name> <t>The "NNDN" CSV File Definition defines the fields and CSV file references used for the NNDN object records.</t> <t>The following "csvNNDN" field elementsMUST<bcp14>MUST</bcp14> be used in the "NNDN" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvNNDN:fAName>">Fully-qualified<dl newline="false" spacing="normal"> <dt><csvNNDN:fAName></dt> <dd>Fully qualified name of the NNDN with type="eppcom:labelType" and isRequired="true". ForIDNsIDNs, theA-LabelA-label is used (see <xreftarget="RFC5891"/>, Section 4.4). </t> <t hangText="<csvNNDN:fNameState>">Statetarget="RFC5891" section="4.4" sectionFormat="comma" format="default"/>). </dd> <dt><csvNNDN:fNameState></dt> <dd>State of the NNDN: blocked or withheld with type="rdeNNDN:nameState" and isRequired="true". See <xreftarget="ndn_object"/>target="ndn_object" format="default"/> for a description of the possible values for the <rdeNNDN:nameState>element.</t> </list></t>element.</dd> </dl> <t>The following field elementsMAY<bcp14>MAY</bcp14> be used in the "NNDN" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvNNDN:fOriginalName>">Domain<dl newline="false" spacing="normal"> <dt><csvNNDN:fOriginalName></dt> <dd>Domain name used to generate the IDN variant withtype="eppcom:labelType".</t> <t hangText="<csvNNDN:fMirroringNS>">Definestype="eppcom:labelType".</dd> <dt><csvNNDN:fMirroringNS></dt> <dd>Defines whether the "mirroring" <csvNNDN:fNameState> uses the NS mirror mechanism, as described for the <rdeNNDN:nameState> "mirroringNS" attribute in <xreftarget="ndn_object"/>,target="ndn_object" format="default"/>, with type="boolean". If the field element is not defined the default value is"true".</t> </list></t>"true".</dd> </dl> <t>The following "rdeCsv" fields, defined insection<xreftarget="csvCommonFieldElements">CSV common field elements</xref>, MAYtarget="csvCommonFieldElements" format="default">'CSV Common Field Elements'</xref>, <bcp14>MAY</bcp14> be used in the "NNDN" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<rdeCsv:fCrDate>">Created date<dl newline="false" spacing="normal"> <dt><rdeCsv:fCrDate></dt> <dd>Date and time of the NNDNobject.</t> <t hangText="<rdeCsv:fUName>">Nameobject creation.</dd> <dt><rdeCsv:fUName></dt> <dd>Name of the NNDN in the Unicode character set for the <csvNNDN:fAName> fieldelement.</t> <t hangText="<rdeCsv:fIdnTableId>">IDN Table Identifierelement.</dd> <dt><rdeCsv:fIdnTableId></dt> <dd>IDN table identifier for the NNDN that matches an IDNTable Reference Objecttable reference object record, as defined in <xreftarget="idnCsvModel"/>.</t> </list></t> <t> <figure> <preamble> Exampletarget="idnCsvModel" format="default"/>.</dd> </dl> <t keepWithNext="true"> The following is an example of an "NNDN" <csvNNDN:contents> <rdeCsv:csv> element:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvNNDN:contents> ... <rdeCsv:csv name="NNDN" sep=","> <rdeCsv:fields> <csvNNDN:fAName/> <rdeCsv:fIdnTableId/> <csvNNDN:fOriginalName/> <csvNNDN:fNameState/> <csvNNDN:fMirroringNS/> <rdeCsv:fCrDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="085A7CE4"> NNDN-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvNNDN:contents> ...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding NNDN-YYYYMMDD.csv file. The file contains two NNDN records for an IDN with one blocked variant and one mirroredvariant. </preamble> <artwork><![CDATA[variant: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ xn--bc456-3ve.example,LANG-1,xn--bc123-3ve.example, blocked,,2005-04-23T11:49:00.0Z xn--bc789-3ve.example,LANG-1,xn--bc123-3ve.example,mirrored,1,2005-04-23T11:49:00.0Z]]> </artwork> </figure> </t>mirrored,1,2005-04-23T11:49:00.0Z ]]></artwork> </section> </section> <sectiontitle="<csvNNDN:deletes>" anchor="csvNNDNDeletes">anchor="csvNNDNDeletes" numbered="true" toc="default"> <name><csvNNDN:deletes></name> <t> The <csvNNDN:deletes> is used to hold the deleted NNDN objects in a Differential or Incremental Deposit. The <csvNNDN:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported NNDN deletes CSV file definition. </t> <sectiontitle=""NNDN"anchor="csvNNDNDeletesDefinition" numbered="true" toc="default"> <name>"NNDN" Deletes CSV FileDefinition" anchor="csvNNDNDeletesDefinition">Definition</name> <t> The following "NNDN" field elementsMUST<bcp14>MUST</bcp14> be used in the deletes "NNDN" <rdeCsv:csv> <rdeCsv:fields> element: </t><t><list style="hanging"> <t hangText="<csvNNDN:fAName>">Fully-qualified<dl newline="false" spacing="normal"> <dt><csvNNDN:fAName></dt> <dd>Fully qualified name of the NNDN with type="eppcom:labelType" and isRequired="true".</t> </list></t> <t> <figure> <preamble> Example</dd> </dl> <t keepWithNext="true"> The following is an example of an "NNDN" <csvNNDN:deletes> <rdeCsv:csv>element. </preamble> <artwork><![CDATA[element: </t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <csvNNDN:deletes> ... <rdeCsv:csv name="NNDN"> <rdeCsv:fields> <csvNNDN:fAName/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="A41F1D9B"> NNDN-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> ... </csvNNDN:deletes>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of the corresponding NNDN-delete-YYYYMMDD.csv file. The file contains one NNDNrecords. </preamble> <artwork><![CDATA[ xn--bc456-3ve.example]]> </artwork> </figure>records: </t> <artwork name="" type="" align="left" alt=""><![CDATA[ xn--bc456-3ve.example ]]></artwork> </section> </section> </section> </section> <sectiontitle="EPPanchor="eppParams" numbered="true" toc="default"> <name>EPP ParametersObject" anchor="eppParams">Object</name> <t> The EPPParameters Objectparameters object is a pseudo-object that defines the set of object and object extension services supported by the registry, as defined in <xreftarget="RFC5730"/>.target="RFC5730" format="default"/>. The EPPParameters Objectparameters object is only defined as XML but could be used in either the XML model or CSV model. The EPPParameters Objectparameters object is defined using the <rdeEppParams:eppParams> element. The EPPParameters Object SHOULDparameters object <bcp14>SHOULD</bcp14> be included if the registry supports EPP. A maximum of one EPPParameters Object MUSTparameters object <bcp14>MUST</bcp14> exist at a certain point in time(watermark).(Time Watermark). </t> <t> The syntax and content of the <rdeEppParams:eppParams> children elements is as explained insection 2.4 of<xreftarget="RFC5730"/>.target="RFC5730" section="2.4" sectionFormat="of" format="default"/>. The children of the <eppParams> are as follows: </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> One or more <version> elements that indicate the EPP versions supported by the registry.</t> <t></li> <li> One or more <lang> elements that indicate the identifiers of the text response languages supported by the registry's EPP server.</t> <t></li> <li> One or more <objURI> elements that contain namespace URIs representing the objects that the registry's EPP server is capable of managing.</t> <t></li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <svcExtension> element that contains one or more <extURI> elements that contain namespace URIs representing object extensions supported by the registry's EPP server.</t> <t></li> <li> A <dcp> element that contains child elements used to describe the server's privacy policy for data collection and management. Seesection 2.4 of<xreftarget="RFC5730"/>target="RFC5730" section="2.4" sectionFormat="of" format="default"/> for more details.</t> </list> </t> <t> <figure> <preamble> Example</li> </ul> <t keepWithNext="true"> The following is an example of <eppParams> element object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeEppParams:eppParams> <rdeEppParams:version>1.0</rdeEppParams:version> <rdeEppParams:lang>en</rdeEppParams:lang> <rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0 </rdeEppParams:objURI> <rdeEppParams:svcExtension> <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0</epp:extURI> <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1</epp:extURI> </rdeEppParams:svcExtension> <rdeEppParams:dcp> <epp:access><epp:all/></epp:access> <epp:statement> <epp:purpose> <epp:admin/> <epp:prov/> </epp:purpose> <epp:recipient> <epp:ours/> <epp:public/> </epp:recipient> <epp:retention> <epp:stated/> </epp:retention> </epp:statement> </rdeEppParams:dcp> </rdeEppParams:eppParams>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> <sectiontitle="Policy Object">numbered="true" toc="default"> <name>Policy Object</name> <t> ThePolicypolicy object is a pseudo-object that is used to specify whichOPTIONAL<bcp14>OPTIONAL</bcp14> elements from the XMLModelmodel areREQUIRED<bcp14>REQUIRED</bcp14> based on the business model of the registry. For the CSVModel,model, theOPTIONAL<bcp14>OPTIONAL</bcp14> "isRequired" attribute of the <rdeCsv:field> elements, defined in <xreftarget="rdeCsv-csv"/>,target="rdeCsv-csv" format="default"/>, is used to specify whichOPTIONAL<bcp14>OPTIONAL</bcp14> fields areREQUIRED<bcp14>REQUIRED</bcp14> based on the business model of the registry. </t> <sectiontitle="<rdePolicy:policy> object" anchor="policy_object">anchor="policy_object" numbered="true" toc="default"> <name><rdePolicy:policy> Object</name> <t> TheOPTIONAL<bcp14>OPTIONAL</bcp14> <policy> contains the following attributes: </t><t> <list style="symbols"> <t><ul spacing="normal"> <li> An <element> that defines that the referenced <element> isREQUIRED. </t> <t><bcp14>REQUIRED</bcp14>. </li> <li> <scope> that defines the XPath(see,(see <xreftarget='W3C.REC-xpath-31-20170321' />)target="W3C.REC-xpath-31-20170321" format="default"/>) of the element referenced by <element>.</t> </list> </t> <t> <figure> <preamble> Example</li> </ul> <t keepWithNext="true"> The following is an example of <rdePolicy:policy> object:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" element="rdeDomain:registrant" />...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="Header Object">numbered="true" toc="default"> <name>Header Object</name> <t> TheHeader Objectheader object is a pseudo-object that is used to specify the number of objects in the repository at a specific point in time(watermark)(Timeline Watermark) regardless of the type of deposit: Differential,FullFull, or Incremental Deposit. TheHeader Objectheader object may also be used to provide additional information on the contents of the deposit. TheHeader Objectheader object is only defined as XML but one header objectMUST<bcp14>MUST</bcp14> always be present per escrow deposit regardless of using the XMLModelmodel or CSVModel.model. TheHeader Objectheader object is defined using the <rdeHeader:header> element. </t> <sectiontitle="<rdeHeader:header> object" anchor="header_object">anchor="header_object" numbered="true" toc="default"> <name><rdeHeader:header> Object</name> <t> The <rdeHeader:header> contains the following elements: </t><t> <list style="symbols"><ul spacing="normal"> <li> <t> A choice of one of the elements defined in the"repositoryTypeGroup""repositoryTypeGroup" group element that indicates the unique identifier for the repository being escrowed. Possible elements are:<list style="symbols"> <t> A</t> <ul spacing="normal"> <li> An <rdeHeader:tld> element that defines TLD or the RCDN being escrowed in the case of aRegistryregistry data escrow deposit. ForIDNsIDNs, theA-LabelA-label is used (see <xreftarget="RFC5891"/>, Section 4.4). </t><t> Atarget="RFC5891" section="4.4" sectionFormat="comma" format="default"/>). </li> <li> An <rdeHeader:registrar> element that defines the Registrar ID corresponding to aRegistrarregistrar data escrow deposit. In the case of an ICANN-accreditedRegistrar,registrar, the <rdeHeader:registrar> elementMUST<bcp14>MUST</bcp14> be the IANA Registrar ID assigned by ICANN.</t> <t> A</li> <li> An <rdeHeader:ppsp> element that defines the provider ID corresponding to a Privacy and Proxy Services Provider (PPSP) data escrow deposit. In the case of an ICANN-accreditedPrivacy and Proxy Services Provider,PPSP, the <rdeHeader:ppsp> elementMUST<bcp14>MUST</bcp14> be the unique ID assigned by ICANN.</t> <t> A</li> <li> An <rdeHeader:reseller> element that defines the provider ID corresponding to aResellerreseller data escrow deposit.</t> </list> </t></li> </ul> </li> <li> <t> A <count> element that contains the number of objects in the SRS at a specific point in time(watermark)(Timeline Watermark) regardless of the type of deposit: Differential,FullFull, or Incremental. The <count> element supports the following attributes:<list style="symbols"> <t></t> <ul spacing="normal"> <li> A"uri""uri" attribute reflects the XML namespace URI of the primary objects for the XMLModelmodel and CSVModel.model. For example, the "uri" is set to "urn:ietf:params:xml:ns:rdeDomain-1.0" for domain name objects using the XMLModel,model, and the "uri" is set to "urn:ietf:params:xml:ns:csvDomain-1.0" for domain name objects using the CSVModel. </t> <t>model. </li> <li> AnOPTIONAL "rcdn"<bcp14>OPTIONAL</bcp14> "rcdn" attribute indicates the RCDN of the objects included in the <count> element. ForIDNsIDNs, theA-LabelA-label is used <xreftarget="RFC5891"/>, Section 4.4.target="RFC5891" section="4.4" sectionFormat="comma" format="default"/>. If the"rcdn""rcdn" attribute is present, the value of the <count> element must include only objects related to registrations in the same and lower levels. For example in a data escrow deposit for the .EXAMPLE TLD, a value of"example""example" in the"rcdn""rcdn" attribute within the <count> element indicates the number of objects in the TLD including objects in other RCDNs within the TLD, whereas a value of"com.example""com.example" indicates the number of elements for objects under"com.example""com.example" and lower levels. Omitting the"rcdn""rcdn" attribute indicates that the total includes all objects of the specified"uri""uri" in the repository(e.g.(e.g., the TLD, Registrar, or PPSP).</t> <t></li> <li> AnOPTIONAL "registrarId"<bcp14>OPTIONAL</bcp14> "registrarId" attribute indicates the identifier of the sponsoringRegistrarregistrar of the objects included in the <count> element. In the case of an ICANN-accreditedRegistrar,registrar, the valueMUST<bcp14>MUST</bcp14> be the IANA Registrar ID assigned by ICANN.</t> </list> </t> <t></li> </ul> </li> <li> AnOPTIONAL<bcp14>OPTIONAL</bcp14> <contentTag> element that contains a tag that defines the expected content in the deposit. The producer and consumer of the deposits will coordinate the set of possible <contentTag> element values.</t> </list> </t> <t> <figure> <preamble> Example</li> </ul> <t keepWithNext="true"> The following is an example of <rdeHeader:header> object referencing only the XMLModelmodel objects:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeHeader:header> <rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeHost-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeContact-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 </rdeHeader:count> </rdeHeader:header>...]]> </artwork> </figure> </t> <t> <figure> <preamble> Example... ]]></sourcecode> <t keepWithNext="true"> The following is an example of an <rdeHeader:header> object referencing the CSV and XMLModelmodel objects:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ ... <rdeHeader:header> <rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvDomain-1.0">2</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvHost-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvContact-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvRegistrar-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvIDN-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvNNDN-1.0">1</rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 </rdeHeader:count> </rdeHeader:header>...]]> </artwork> </figure> </t>... ]]></sourcecode> </section> </section> <sectiontitle="DNRDnumbered="true" toc="default"> <name>DNRD Common ObjectsCollection">Collection</name> <t> The DNRDCommon Objects Collectioncommon objects collection contains data structures referenced by two or more of the main objects in the XML model. </t> </section> </section> <sectiontitle="RDEnumbered="true" toc="default"> <name>RDE IDN Variantshandling">Handling</name> <t> Depending on theRegistration Policyregistration policy of theRegistry,registry, for a domain name there may be multiple variant names. See <xreftarget="variantTLDsReport"/>target="variantTLDsReport" format="default"/> for furtherdetaildetails 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 in the escrow deposit, as a domain or as an NNDN object, but not both. </t> <t> If using domain objects to represent IDN variants, the normal behavior during restoration of an SRS based on an escrow deposit is to restore the IDN variants as a mirrored variant. If the registration data of the IDN variant is different from the original name, the details of this specific implementationMUST<bcp14>MUST</bcp14> be described in the IDN policy document. </t> <t> 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. Explicit representation of an IDN variant takes precedence over an implicit representation. </t> </section> <sectiontitle="Profile">numbered="true" toc="default"> <name>Profile</name> <t> Different business models of registries exist, therefore the registry is responsible for defining a profile that matches its particular business model. The profile mechanism allows a registry to extend this specification. </t> <t> A profile is the processof: <list style="numbers">of the following: </t> <ol spacing="normal" type="1"><li> <t> Extending base objects with the mechanisms defined for XML and CSV models.<list style="symbols"> <t></t> <ul spacing="normal"> <li> In the case of the XML model, abstract elements could beuseused to extend the following objects: <domain>, <host>, <contact>,<NNDN><NNDN>, and <registrar> using the XML schema substitution groups feature.</t> </list> </t> <t></li> </ul> </li> <li> Defining a <policy> object to specify whichOPTIONAL<bcp14>OPTIONAL</bcp14> elements of this base specificationisare required based on the business model of the registry. An example is the <registrant> element that is usuallyREQUIRED<bcp14>REQUIRED</bcp14>, but it is specified asOPTIONAL<bcp14>OPTIONAL</bcp14> in this specification to support some existing business models.</t> <t></li> <li> Adding new escrowed objects using the <rde:contents> and <rde:deletes> elements.</t> <t></li> <li> Providing the XML schemas to third parties that require them to validate the escrow deposits.</t> </list> </t></li> </ol> </section> <sectiontitle="Data escrow agent extended verification process"> <t> A Datanumbered="true" toc="default"> <name>Data Escrow AgentSHOULDExtended Verification Process</name> <t> A data escrow agent <bcp14>SHOULD</bcp14> perform an extended verification process that starts by creating a dataset to be tested by followingsection 5.2 in<xreftarget="I-D.ietf-regext-data-escrow"/>.target="RFC8909" section="5.2" sectionFormat="of" format="default"/>. </t> <t> The following are the minimum suggested tests on the dataset:<list style="symbols"></t> <ul spacing="normal"> <li> <t> Validate the escrow deposits using the definition agreed with the registry.<list style="symbols"> <t></t> <ul spacing="normal"> <li> In the case of the XML model, the contents of the escrow depositsMUST<bcp14>MUST</bcp14> be validated using the XML schemas of the profile.</t> </list> </t> <t></li> </ul> </li> <li> Count the objects and validate that the number of objects is equal to the number objects reported in the <header> element of the escrow deposit of that point in time(watermark). </t> <t>(Timeline Watermark). </li> <li> All contact objects linked to domain namesMUST<bcp14>MUST</bcp14> be present.</t> <t></li> <li> Allregistrarsregistrar objects linked to other objectsMUST<bcp14>MUST</bcp14> be present.</t> <t></li> <li> No domain name exists as both a domain name and an NNDN.</t> <t></li> <li> The elements listed as required in the <policy> elementMUST<bcp14>MUST</bcp14> be present.</t> <t></li> <li> All idnTableRef definitions linked from other objectsMUST<bcp14>MUST</bcp14> be present.</t> <t></li> <li> If an EPPParameters Objectparameters object was escrowed in the past, one and only one EPPParameters Object MUSTparameters object <bcp14>MUST</bcp14> be present.</t> <t></li> <li> ThewatermarkTimeline Watermark is not in the future.</t> </list> </t></li> </ul> </section> <sectiontitle="Formal Syntax" anchor="formalSyntax">anchor="formalSyntax" numbered="true" toc="default"> <name>Formal Syntax</name> <t>This standard is specified in XML Schema notation. The formal syntax presented here is a complete schema representation suitable for automated validation.</t> <t>The <CODE BEGINS> and <CODE ENDS> tags are not part of the schema; they are used to note the beginning and ending of the schema for URI registration purposes.</t> <sectiontitle="RDE CSV Schema" anchor="xsdRdeCsv"> <t> <figure><artwork><![CDATA[<CODE BEGINS>anchor="xsdRdeCsv" numbered="true" toc="default"> <name>RDE CSV Schema</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types --> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <annotation> <documentation> Registry Data Escrow Comma-Separated Values (CSV) </documentation> </annotation> <!-- csv content element --> <element name="csv" type="rdeCsv:csvType" /> <!-- Definition of CSV file --> <complexType name="csvType"> <sequence> <element name="fields" type="rdeCsv:fieldsType" /> <element name="files" type="rdeCsv:filesType" /> </sequence> <attribute name="name" type="token" use="required" /> <attribute name="sep" type="rdeCsv:sepType" default="," /> </complexType> <!-- fieldseperatorseparator must be a single character --> <simpleType name="sepType"> <restriction base="string"> <minLength value="1" /> <maxLength value="1" /> </restriction> </simpleType> <!-- Abstract field type --> <element name="field" type="rdeCsv:fieldType" abstract="true" /> <complexType name="fieldType"> <sequence /> </complexType> <!-- fieldType with optional value (isRequired=false) --> <complexType name="fieldOptionalType"> <complexContent> <extension base="rdeCsv:fieldType"> <sequence /> <attribute name="isRequired" type="boolean" default="false" /> <attribute name="parent" type="boolean" default="false" /> </extension> </complexContent> </complexType> <!-- fieldType with required value (isRequired=false) --> <complexType name="fieldRequiredType"> <complexContent> <extension base="rdeCsv:fieldType"> <sequence /> <attribute name="isRequired" type="boolean" default="true" /> <attribute name="parent" type="boolean" default="false" /> </extension> </complexContent> </complexType> <!-- Concrete field types --> <!-- UTF-8 Name field(e.g.(e.g., domain name) --> <element name="fUName" type="rdeCsv:fNameType" substitutionGroup="rdeCsv:field" /> <complexType name="fNameType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="eppcom\:labelType" /> </extension> </complexContent> </complexType> <complexType name="fNameRequiredType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="eppcom\:labelType" /> </extension> </complexContent> </complexType> <!-- Registry Object IDentifier (roid) field --> <element name="fRoid" type="rdeCsv:fRoidType" substitutionGroup="rdeCsv:field" /> <complexType name="fRoidType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="eppcom\:roidType" /> </extension> </complexContent> </complexType> <!-- Registrant field --> <element name="fRegistrant" type="rdeCsv:fRegistrantType" substitutionGroup="rdeCsv:field" /> <complexType name="fRegistrantType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="eppcom\:clIDType" /> </extension> </complexContent> </complexType> <!-- Object Status Description --> <element name="fStatusDescription" type="rdeCsv:fNormalizedStringType" substitutionGroup="rdeCsv:field" /> <!-- clID fields (fClID, fCrID, fUpID) --> <!-- Identifier of the client that sponsors the object --> <element name="fClID" type="rdeCsv:fClIDRequiredType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of registrar of client that created the object --> <element name="fCrRr" type="rdeCsv:fClIDType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of the client that created the object --> <element name="fCrID" type="rdeCsv:fClIDType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of registrar of client that updated the object --> <element name="fUpRr" type="rdeCsv:fClIDType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of the client that updated the object --> <element name="fUpID" type="rdeCsv:fClIDType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of registrar of client that requested the transfer --> <element name="fReRr" type="rdeCsv:fClIDRequiredType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of the client that requested the transfer --> <element name="fReID" type="rdeCsv:fClIDType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of registrar client that should take or took action --> <element name="fAcRr" type="rdeCsv:fClIDRequiredType" substitutionGroup="rdeCsv:field" /> <!-- Identifier of the client that should take or took action --> <element name="fAcID" type="rdeCsv:fClIDType" substitutionGroup="rdeCsv:field" /> <complexType name="fClIDType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="eppcom\:clIDType" /> </extension> </complexContent> </complexType> <complexType name="fClIDRequiredType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="eppcom\:clIDType" /> </extension> </complexContent> </complexType> <!-- dateTime fields (fCrDate, fUpDate, fExDate) --> <element name="fCrDate" type="rdeCsv:fDateTimeType" substitutionGroup="rdeCsv:field" /> <element name="fUpDate" type="rdeCsv:fDateTimeType" substitutionGroup="rdeCsv:field" /> <element name="fExDate" type="rdeCsv:fDateTimeType" substitutionGroup="rdeCsv:field" /> <!-- Date and time that transfer was requested --> <element name="fReDate" type="rdeCsv:fRequiredDateTimeType" substitutionGroup="rdeCsv:field" /> <!-- Date and time of a required or completed response --> <element name="fAcDate" type="rdeCsv:fRequiredDateTimeType" substitutionGroup="rdeCsv:field" /> <element name="fTrDate" type="rdeCsv:fDateTimeType" substitutionGroup="rdeCsv:field" /> <complexType name="fDateTimeType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="dateTime" /> </extension> </complexContent> </complexType> <complexType name="fRequiredDateTimeType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="dateTime" /> </extension> </complexContent> </complexType> <!-- boolean type --> <complexType name="fBooleanType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="boolean" /> </extension> </complexContent> </complexType> <complexType name="fRequiredBooleanType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="boolean" /> </extension> </complexContent> </complexType> <!-- unsignedByte type --> <complexType name="fUnsignedByteType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="unsignedByte" /> </extension> </complexContent> </complexType> <complexType name="fRequiredUnsignedByteType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="unsignedByte" /> </extension> </complexContent> </complexType> <!-- unsignedShort type --> <complexType name="fUnsignedShortType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="unsignedShort" /> </extension> </complexContent> </complexType> <complexType name="fRequiredUnsignedShortType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="unsignedShort" /> </extension> </complexContent> </complexType> <!-- hexBinary type --> <complexType name="fHexBinaryType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="hexBinary" /> </extension> </complexContent> </complexType> <complexType name="fRequiredHexBinaryType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="hexBinary" /> </extension> </complexContent> </complexType> <!-- language type --> <element name="fLang" type="rdeCsv:fLangType" substitutionGroup="rdeCsv:field" /> <complexType name="fLangType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="language" /> </extension> </complexContent> </complexType> <!-- IDN Table Identifier --> <element name="fIdnTableId" type="rdeCsv:fTokenType" substitutionGroup="rdeCsv:field" /> <!-- State of the most recent transfer request --> <element name="fTrStatus" type="rdeCsv:fTrStatusType" substitutionGroup="rdeCsv:field" /> <complexType name="fTrStatusType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="eppcom\:trStatusType" /> </extension> </complexContent> </complexType> <!-- General token type --> <complexType name="fTokenType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="token" /> </extension> </complexContent> </complexType> <!-- General normalizedString type --> <complexType name="fNormalizedStringType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="normalizedString" /> </extension> </complexContent> </complexType> <!-- positive integer type --> <complexType name="fPositiveIntegerType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="positiveInteger" /> </extension> </complexContent> </complexType> <!-- Custom / extension field type --> <element name="fCustom" type="rdeCsv:fCustomType" substitutionGroup="rdeCsv:field" /> <complexType name="fCustomType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="name" type="token" /> <attribute name="type" type="token" default="token" /> </extension> </complexContent> </complexType> <!-- Ordered list of field definitions for the csv --> <complexType name="fieldsType"> <sequence maxOccurs="unbounded"> <element ref="rdeCsv:field" /> </sequence> </complexType> <!-- List of files --> <complexType name="filesType"> <sequence> <element name="file" type="rdeCsv:fileType" maxOccurs="unbounded" /> </sequence> </complexType> <!-- File definition --> <complexType name="fileType"> <simpleContent> <extension base="token"> <attribute name="compression" type="token" /> <attribute name="encoding" type="token" default="UTF-8" /> <attribute name="cksum" type="token" /> <attribute name="cksumAlg" type="token" default="CRC32" /> </extension> </simpleContent> </complexType> <!-- URL fields --> <element name="fUrl" type="rdeCsv:anyURIType" substitutionGroup="rdeCsv:field" /> <complexType name="anyURIType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="anyURI" /> </extension> </complexContent> </complexType> <!-- End of schema. --> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="RDEanchor="xsdRdeDomain" numbered="true" toc="default"> <name>RDE DomainObject" anchor="xsdRdeDomain"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <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:secDNS-1.1" /> <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:rdeIDN-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" /> <annotation> <documentation> Registry Data Escrow Domain provisioning schema </documentation> </annotation> <element name="abstractDomain" type="rdeDomain:abstractContentType" substitutionGroup="rde:content" abstract="true" /> <element name="domain" substitutionGroup="rdeDomain:abstractDomain" /> <element name="delete" type="rdeDomain:deleteType" substitutionGroup="rde:delete" /> <!-- Content Type --> <complexType name="abstractContentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element name="name" type="eppcom:labelType" /> <element name="roid" type="eppcom:roidType" /> <element name="uName" type="eppcom:labelType" minOccurs="0" /> <element name="idnTableId" type="rdeIDN:idType" minOccurs="0" /> <element name="originalName" type="eppcom:labelType" minOccurs="0" /> <element name="status" type="domain:statusType" maxOccurs="11" /> <element name="rgpStatus" type="rgp:statusType" minOccurs="0" maxOccurs="unbounded" /> <element name="registrant" type="eppcom:clIDType" minOccurs="0" /> <element name="contact" type="domain:contactType" minOccurs="0" maxOccurs="unbounded" /> <element name="ns" type="domain:nsType" minOccurs="0" /> <element name="clID" type="eppcom:clIDType" /> <element name="crRr" type="rdeDnrdCommon:rrType" minOccurs="0" /> <element name="crDate" type="dateTime" minOccurs="0" /> <element name="exDate" type="dateTime" minOccurs="0" /> <element name="upRr" type="rdeDnrdCommon:rrType" minOccurs="0" /> <element name="upDate" type="dateTime" minOccurs="0" /> <element name="secDNS" type="secDNS:dsOrKeyType" minOccurs="0" /> <element name="trDate" type="dateTime" minOccurs="0" /> <element name="trnData" type="rdeDomain:transferDataType" minOccurs="0" /> </sequence> </extension> </complexContent> </complexType> <complexType name="transferDataType"> <sequence> <element name="trStatus" type="eppcom:trStatusType" /> <element name="reRr" type="rdeDnrdCommon:rrType" /> <element name="reDate" type="dateTime" /> <element name="acRr" type="rdeDnrdCommon:rrType" /> <element name="acDate" type="dateTime" /> <element name="exDate" type="dateTime" minOccurs="0" /> </sequence> </complexType> <!-- Delete Type --> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element name="name" type="eppcom:labelType" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="CSVanchor="xsdRdeCsvDomain" numbered="true" toc="default"> <name>CSV DomainObject" anchor="xsdRdeCsvDomain"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rgp="urn:ietf:params:xml:ns:rgp-1.0" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types --> <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:secDNS-1.1" /> <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:rdeCsv-1.0" /> <annotation> <documentation> Domain Name Comma-Separated Values (CSV) Object </documentation> </annotation> <!-- Child elements of the <rde:contents> object --> <element name="contents" type="csvDomain:contentType" substitutionGroup="rde:content" /> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Child elements of the <rde:deletes> object --> <element name="deletes" type="csvDomain:deleteType" substitutionGroup="rde:delete" /> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Domain name field --> <element name="fName" type="rdeCsv:fNameRequiredType" substitutionGroup="rdeCsv:field" /> <!-- RGP status field --> <element name="fRgpStatus" type="csvDomain:fRgpStatusType" substitutionGroup="rdeCsv:field" /> <complexType name="fRgpStatusType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="rgp\:statusValueType" /> </extension> </complexContent> </complexType> <!-- Contact type field --> <element name="fContactType" type="csvDomain:fContactsTypeType" substitutionGroup="rdeCsv:field" /> <complexType name="fContactsTypeType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="domain\:contactAttrType" /> </extension> </complexContent> </complexType> <!-- DNSSEC field types --> <!-- Maximum signature lifetime field --> <element name="fMaxSigLife" type="csvDomain:fMaxSigLifeType" substitutionGroup="rdeCsv:field" /> <complexType name="fMaxSigLifeType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="secDNS\:maxSigLifeType" /> </extension> </complexContent> </complexType> <!-- Key tag field --> <element name="fKeyTag" type="rdeCsv:fRequiredUnsignedShortType" substitutionGroup="rdeCsv:field" /> <!-- DS Algorithm field --> <element name="fDsAlg" type="rdeCsv:fRequiredUnsignedByteType" substitutionGroup="rdeCsv:field" /> <!-- Digest type field --> <element name="fDigestType" type="rdeCsv:fRequiredUnsignedByteType" substitutionGroup="rdeCsv:field" /> <!-- Digest field --> <element name="fDigest" type="rdeCsv:fRequiredHexBinaryType" substitutionGroup="rdeCsv:field" /> <!-- Flags field --> <element name="fFlags" type="rdeCsv:fRequiredUnsignedShortType" substitutionGroup="rdeCsv:field" /> <!-- Protocol field --> <element name="fProtocol" type="rdeCsv:fRequiredUnsignedByteType" substitutionGroup="rdeCsv:field" /> <!-- Key Algorithm field --> <element name="fKeyAlg" type="rdeCsv:fRequiredUnsignedByteType" substitutionGroup="rdeCsv:field" /> <!-- Public Key field --> <element name="fPubKey" type="csvDomain:fPubKeyType" substitutionGroup="rdeCsv:field" /> <complexType name="fPubKeyType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="secDNS\:keyType" /> </extension> </complexContent> </complexType> <!-- Original Domain Name for Variant field --> <element name="fOriginalName" type="rdeCsv:fNameType" substitutionGroup="rdeCsv:field" /> <!-- Domain status field --> <element name="fStatus" type="csvDomain:fStatusType" substitutionGroup="rdeCsv:field" /> <!-- Domain status based on domain-1.0.xsd --> <complexType name="fStatusType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="domain\:statusValueType" /> </extension> </complexContent> </complexType> <!-- End of schema. --> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="RDEanchor="xsdRdeHost" numbered="true" toc="default"> <name>RDE HostObject" anchor="xsdRdeHost"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:host="urn:ietf:params:xml:ns:host-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <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:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" /> <annotation> <documentation> Registry Data Escrow Host provisioning schema </documentation> </annotation> <element name="abstractHost" type="rdeHost:abstractContentType" substitutionGroup="rde:content" abstract="true" /> <element name="host" substitutionGroup="rdeHost:abstractHost" /> <element name="delete" type="rdeHost:deleteType" substitutionGroup="rde:delete" /> <!-- Content Type --> <complexType name="abstractContentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element name="name" type="eppcom:labelType" /> <element name="roid" type="eppcom:roidType" /> <element name="status" type="host:statusType" maxOccurs="7" /> <element name="addr" type="host:addrType" minOccurs="0" maxOccurs="unbounded" /> <element name="clID" type="eppcom:clIDType" /> <element name="crRr" type="rdeDnrdCommon:rrType" minOccurs="0" /> <element name="crDate" type="dateTime" minOccurs="0" /> <element name="upRr" type="rdeDnrdCommon:rrType" minOccurs="0" /> <element name="upDate" type="dateTime" minOccurs="0" /> <element name="trDate" type="dateTime" minOccurs="0" /> </sequence> </extension> </complexContent> </complexType> <!-- Delete Type --> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <choice minOccurs="0" maxOccurs="unbounded"> <element name="name" type="eppcom:labelType" /> <element name="roid" type="eppcom:roidType" /> </choice> </extension> </complexContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="CSVanchor="xsdRdeCsvHost" numbered="true" toc="default"> <name>CSV HostObject" anchor="xsdRdeCsvHost"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:host="urn:ietf:params:xml:ns:host-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types --> <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:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" /> <annotation> <documentation> Host Comma-Separated Values (CSV) Object </documentation> </annotation> <!-- Child elements of the <rde:contents> object --> <element name="contents" type="csvHost:contentType" substitutionGroup="rde:content" /> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Child elements of the <rde:deletes> object --> <element name="deletes" type="csvHost:deleteType" substitutionGroup="rde:delete" /> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Host name field --> <element name="fName" type="rdeCsv:fNameRequiredType" substitutionGroup="rdeCsv:field" /> <!-- IP address field --> <element name="fAddr" type="csvHost:fAddrType" substitutionGroup="rdeCsv:field" /> <complexType name="fAddrType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="host\:addrStringType" /> </extension> </complexContent> </complexType> <!-- IP address version field --> <element name="fAddrVersion" type="csvHost:fAddrVersionType" substitutionGroup="rdeCsv:field" /> <complexType name="fAddrVersionType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="host\:ipType" /> </extension> </complexContent> </complexType> <!-- Host status field --> <element name="fStatus" type="csvHost:fStatusType" substitutionGroup="rdeCsv:field" /> <!-- Host status based on host-1.0.xsd --> <complexType name="fStatusType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="host\:statusValueType" /> </extension> </complexContent> </complexType> <!-- End of schema. --> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="RDEanchor="xsdRdeContact" numbered="true" toc="default"> <name>RDE ContactObject" anchor="xsdRdeContact"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns:rdeDnrdCommon="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types. --> <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:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeDnrdCommon-1.0" /> <annotation> <documentation> Registry Data Escrow contact provisioning schema </documentation> </annotation> <element name="abstractContact" type="rdeContact:abstractContentType" substitutionGroup="rde:content" abstract="true" /> <element name="contact" substitutionGroup="rdeContact:abstractContact" /> <element name="delete" type="rdeContact:deleteType" substitutionGroup="rde:delete" /> <!-- Contact Type --> <complexType name="abstractContentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element name="id" type="eppcom:clIDType" /> <element name="roid" type="eppcom:roidType" /> <element name="status" type="contact:statusType" maxOccurs="7" /> <element name="postalInfo" type="contact:postalInfoType" maxOccurs="2" /> <element name="voice" type="contact:e164Type" minOccurs="0" /> <element name="fax" type="contact:e164Type" minOccurs="0" /> <element name="email" type="eppcom:minTokenType" /> <element name="clID" type="eppcom:clIDType" /> <element name="crRr" type="rdeDnrdCommon:rrType" minOccurs="0" /> <element name="crDate" type="dateTime" minOccurs="0" /> <element name="upRr" type="rdeDnrdCommon:rrType" minOccurs="0" /> <element name="upDate" type="dateTime" minOccurs="0" /> <element name="trDate" type="dateTime" minOccurs="0" /> <element name="trnData" type="rdeContact:transferDataType" minOccurs="0" /> <element name="disclose" type="contact:discloseType" minOccurs="0" /> </sequence> </extension> </complexContent> </complexType> <complexType name="transferDataType"> <sequence> <element name="trStatus" type="eppcom:trStatusType" /> <element name="reRr" type="rdeDnrdCommon:rrType" /> <element name="reDate" type="dateTime" /> <element name="acRr" type="rdeDnrdCommon:rrType" /> <element name="acDate" type="dateTime" /> </sequence> </complexType> <!-- Delete Type --> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element name="id" type="eppcom:clIDType" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="CSVanchor="xsdRdeCsvContact" numbered="true" toc="default"> <name>CSV ContactObject" anchor="xsdRdeCsvContact"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types. --> <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:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" /> <annotation> <documentation> Contact Comma-Separated Values (CSV) Object </documentation> </annotation> <!-- Child elements of the <rde:contents> object --> <element name="contents" type="csvContact:contentType" substitutionGroup="rde:content" /> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Child elements of the <rde:deletes> object --> <element name="deletes" type="csvContact:deleteType" substitutionGroup="rde:delete" /> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Server-unique contact identifier field --> <element name="fId" type="csvContact:fIdType" substitutionGroup="rdeCsv:field" /> <complexType name="fIdType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="eppcom\:clIDType" /> </extension> </complexContent> </complexType> <!-- Is Registrar Contact field --> <element name="fIsRegistrarContact" type="rdeCsv:fBooleanType" substitutionGroup="rdeCsv:field" /> <!-- voice and fax telephone number fields --> <element name="fVoice" type="csvContact:fE164StringType" substitutionGroup="rdeCsv:field" /> <element name="fFax" type="csvContact:fE164StringType" substitutionGroup="rdeCsv:field" /> <complexType name="fE164StringType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="contact\:e164StringType" /> </extension> </complexContent> </complexType> <!-- voice and fax telephone extension fields --> <element name="fVoiceExt" type="rdeCsv:fTokenType" substitutionGroup="rdeCsv:field" /> <element name="fFaxExt" type="rdeCsv:fTokenType" substitutionGroup="rdeCsv:field" /> <!-- contact email address field --> <element name="fEmail" type="csvContact:fEmailType" substitutionGroup="rdeCsv:field" /> <complexType name="fEmailType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="eppcom\:minTokenType" /> </extension> </complexContent> </complexType> <!-- Postal type field ("loc" = localized, "int" = internationalized) --> <element name="fPostalType" type="csvContact:fPostalTypeType" substitutionGroup="rdeCsv:field" /> <complexType name="fPostalTypeType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="contact\:postalInfoEnumType" /> </extension> </complexContent> </complexType> <!-- Standard postal line field --> <complexType name="fPostalLineType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="contact\:postalLineType" /> <attribute name="isLoc" type="boolean" /> </extension> </complexContent> </complexType> <!-- Standard optional postal line field --> <complexType name="fOptPostalLineType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="contact\:optPostalLineType" /> <attribute name="isLoc" type="boolean" /> </extension> </complexContent> </complexType> <!-- Name of the individual or role field --> <element name="fName" type="csvContact:fPostalLineType" substitutionGroup="rdeCsv:field" /> <!-- Name organization field --> <element name="fOrg" type="csvContact:fOptPostalLineType" substitutionGroup="rdeCsv:field" /> <!-- Street address line field with required index attribute --> <!-- starting with index 0. --> <element name="fStreet" type="csvContact:fStreetType" substitutionGroup="rdeCsv:field" /> <complexType name="fStreetType"> <complexContent> <extension base="csvContact:fOptPostalLineType"> <sequence /> <attribute name="index" type="int" use="required" /> </extension> </complexContent> </complexType> <!-- Contact's city field --> <element name="fCity" type="csvContact:fPostalLineType" substitutionGroup="rdeCsv:field" /> <!-- Contact's state or province field --> <element name="fSp" type="csvContact:fOptPostalLineType" substitutionGroup="rdeCsv:field" /> <!-- Contact's postal code field --> <element name="fPc" type="csvContact:fPcType" substitutionGroup="rdeCsv:field" /> <complexType name="fPcType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="contact\:pcType" /> <attribute name="isLoc" type="boolean" /> </extension> </complexContent> </complexType> <!-- Contact's country code field --> <element name="fCc" type="csvContact:fCcType" substitutionGroup="rdeCsv:field" /> <complexType name="fCcType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="contact\:ccType" /> <attribute name="isLoc" type="boolean" /> </extension> </complexContent> </complexType> <!-- Disclosure element fields --> <!-- Flag of "1" to allow disclosure and "0" to disallow disclosure --> <element name="fDiscloseFlag" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure of localized name based on fDiscloseFlag? --> <element name="fDiscloseNameLoc" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure of internationalized name based on fDiscloseFlag? --> <element name="fDiscloseNameInt" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure of localized org based on fDiscloseFlag? --> <element name="fDiscloseOrgLoc" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure of internationalized org based on fDiscloseFlag? --> <element name="fDiscloseOrgInt" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure of localized address based on fDiscloseFlag? --> <element name="fDiscloseAddrLoc" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure of internationalized address based on fDiscloseFlag? --> <element name="fDiscloseAddrInt" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure voice telephone number based on fDiscloseFlag? --> <element name="fDiscloseVoice" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure facsimile telephone number based on fDiscloseFlag? --> <element name="fDiscloseFax" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <!-- Disclosure email address based on fDiscloseFlag? --> <element name="fDiscloseEmail" type="csvContact:fBoolean" substitutionGroup="rdeCsv:field" /> <complexType name="fBoolean"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="boolean" /> </extension> </complexContent> </complexType> <!-- Contact status field --> <element name="fStatus" type="csvContact:fStatusType" substitutionGroup="rdeCsv:field" /> <!-- Host status based on contact-1.0.xsd --> <complexType name="fStatusType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="contact\:statusValueType" /> </extension> </complexContent> </complexType> <!-- End of schema. --> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="RDEanchor="xsdRdeRegistrar" numbered="true" toc="default"> <name>RDE RegistrarObject" anchor="xsdRdeRegistrar"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types. --> <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:contact-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <annotation> <documentation> Registry Data Escrow registrar provisioning schema </documentation> </annotation> <element name="abstractRegistrar" type="rdeRegistrar:abstractContentType" substitutionGroup="rde:content" abstract="true" /> <element name="registrar" substitutionGroup="rdeRegistrar:abstractRegistrar" /> <element name="delete" type="rdeRegistrar:deleteType" substitutionGroup="rde:delete" /> <!-- Content Type --> <complexType name="abstractContentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element name="id" type="eppcom:clIDType" /> <element name="name" type="rdeRegistrar:nameType" /> <element name="gurid" type="positiveInteger" minOccurs="0" /> <element name="status" type="rdeRegistrar:statusType" minOccurs="0" /> <element name="postalInfo" type="rdeRegistrar:postalInfoType" minOccurs="0" maxOccurs="2" /> <element name="voice" type="contact:e164Type" minOccurs="0" /> <element name="fax" type="contact:e164Type" minOccurs="0" /> <element name="email" type="eppcom:minTokenType" minOccurs="0" /> <element name="url" type="anyURI" minOccurs="0" /> <element name="whoisInfo" type="rdeRegistrar:whoisInfoType" minOccurs="0" /> <element name="crDate" type="dateTime" minOccurs="0" /> <element name="upDate" type="dateTime" minOccurs="0" /> </sequence> </extension> </complexContent> </complexType> <simpleType name="nameType"> <restriction base="normalizedString"> <minLength value="1" /> <maxLength value="255" /> </restriction> </simpleType> <simpleType name="statusType"> <restriction base="token"> <enumeration value="ok" /> <enumeration value="readonly" /> <enumeration value="terminated" /> </restriction> </simpleType> <complexType name="postalInfoType"> <sequence> <element name="addr" type="rdeRegistrar:addrType" /> </sequence> <attribute name="type" type="rdeRegistrar:postalInfoEnumType" use="required" /> </complexType> <simpleType name="postalInfoEnumType"> <restriction base="token"> <enumeration value="loc" /> <enumeration value="int" /> </restriction> </simpleType> <complexType name="addrType"> <sequence> <element name="street" type="rdeRegistrar:optPostalLineType" minOccurs="0" maxOccurs="3" /> <element name="city" type="rdeRegistrar:postalLineType" /> <element name="sp" type="rdeRegistrar:optPostalLineType" minOccurs="0" /> <element name="pc" type="rdeRegistrar:pcType" minOccurs="0" /> <element name="cc" type="rdeRegistrar:ccType" /> </sequence> </complexType> <simpleType name="postalLineType"> <restriction base="normalizedString"> <minLength value="1" /> <maxLength value="255" /> </restriction> </simpleType> <simpleType name="optPostalLineType"> <restriction base="normalizedString"> <maxLength value="255" /> </restriction> </simpleType> <simpleType name="pcType"> <restriction base="token"> <maxLength value="16" /> </restriction> </simpleType> <simpleType name="ccType"> <restriction base="token"> <length value="2" /> </restriction> </simpleType> <complexType name="whoisInfoType"> <sequence> <element name="name" type="eppcom:labelType" minOccurs="0" /> <element name="url" type="anyURI" minOccurs="0" /> </sequence> </complexType> <!-- Delete Type --> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element name="id" type="eppcom:clIDType" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="CSVanchor="xsdRdeCsvRegistrar" numbered="true" toc="default"> <name>CSV RegistrarObject" anchor="xsdRdeCsvRegistrar"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types. --> <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:contact-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" /> <annotation> <documentation>RegistarRegistrar Comma-Separated Values (CSV) Object </documentation> </annotation> <!-- Child elements of the <rde:contents> object --> <element name="contents" type="csvRegistrar:contentType" substitutionGroup="rde:content" /> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Child elements of the <rde:deletes> object --> <element name="deletes" type="csvRegistrar:deleteType" substitutionGroup="rde:delete" /> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Registrar unique identifier (short name / id) --> <element name="fId" type="rdeCsv:fClIDRequiredType" substitutionGroup="rdeCsv:field" /> <!-- Registrar name (full name) --> <element name="fName" type="csvRegistrar:fNameType" substitutionGroup="rdeCsv:field" /> <!-- Registrar name field --> <complexType name="fNameType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="normalizedString" /> <attribute name="isLoc" type="boolean" default="false" /> </extension> </complexContent> </complexType> <!-- Registrar GURID field --> <element name="fGurid" type="rdeCsv:fPositiveIntegerType" substitutionGroup="rdeCsv:field" /> <!-- Registrar status field --> <element name="fStatus" type="csvRegistrar:fStatusType" substitutionGroup="rdeCsv:field" /> <element name="fStatusName" type="rdeCsv:fTokenType" substitutionGroup="rdeCsv:field" /> <complexType name="fStatusType"> <complexContent> <extension base="rdeCsv:fieldOptionalType"> <sequence /> <attribute name="type" type="token" default="csvRegistrar\:statusType" /> </extension> </complexContent> </complexType> <!-- Registrar status type with optional name attr --> <complexType name="statusType"> <simpleContent> <extension base="csvRegistrar:statusValueType"> <attribute name="name" type="token" /> </extension> </simpleContent> </complexType> <!-- Registrar status enumerated values --> <simpleType name="statusValueType"> <restriction base="token"> <enumeration value="ok" /> <enumeration value="readonly" /> <enumeration value="terminated" /> </restriction> </simpleType> <!-- Whois URL field --> <element name="fWhoisUrl" type="rdeCsv:anyURIType" substitutionGroup="rdeCsv:field" /> <!-- End of schema. --> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="RDEanchor="xsdRdeIdn" numbered="true" toc="default"> <name>RDE IDN Table ReferenceObjects" anchor="xsdRdeIdn"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Objects</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <annotation> <documentation> Registry Data Escrow IDN provisioning schema </documentation> </annotation> <element name="idnTableRef" type="rdeIDN:contentType" substitutionGroup="rde:content" /> <element name="delete" type="rdeIDN:deleteType" substitutionGroup="rde:delete" /> <!-- Content Types --> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element name="url" type="anyURI" /> <element name="urlPolicy" type="anyURI" /> </sequence> <attribute name="id" type="rdeIDN:idType" use="required" /> </extension> </complexContent> </complexType> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element name="id" type="rdeIDN:idType" /> </sequence> </extension> </complexContent> </complexType> <!-- Simple Types --> <simpleType name="idType"> <restriction base="token"> <minLength value="1" /> <maxLength value="64" /> </restriction> </simpleType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="CSVanchor="xsdRdeCsvIdn" numbered="true" toc="default"> <name>CSV IDN LanguageObject" anchor="xsdRdeCsvIdn"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types --> <import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0" /> <annotation> <documentation> IDN Language Comma-Separated Values (CSV) Object </documentation> </annotation> <!-- Child elements of the <rde:contents> object --> <element name="contents" type="csvIDN:contentType" substitutionGroup="rde:content" /> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Child elements of the <rde:deletes> object --> <element name="deletes" type="csvIDN:deleteType" substitutionGroup="rde:delete" /> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- End of schema. --> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="EPPanchor="xsdRdeEpp" numbered="true" toc="default"> <name>EPP ParametersObject" anchor="xsdRdeEpp"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <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:rde-1.0" /> <annotation> <documentation> Registry Data Escrow EPP Parameters schema </documentation> </annotation> <!-- Content Type --> <element name="eppParams" substitutionGroup="rdeEppParams:abstractEppParams" /> <!-- Abstract Content Type --> <element name="abstractEppParams" type="rdeEppParams:abstractContentType" substitutionGroup="rde:content" abstract="true" /> <complexType name="abstractContentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element name="version" type="epp:versionType" maxOccurs="unbounded" /> <element name="lang" type="language" maxOccurs="unbounded" /> <element name="objURI" type="anyURI" maxOccurs="unbounded" /> <element name="svcExtension" type="epp:extURIType" minOccurs="0" /> <element name="dcp" type="epp:dcpType" /> </sequence> </extension> </complexContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="NNDN Object" anchor="xsdRdeNndn"> <t> <figure><artwork><![CDATA[<CODE BEGINS>anchor="xsdRdeNndn" numbered="true" toc="default"> <name>NNDN Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <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:rdeIDN-1.0" /> <annotation> <documentation> Registry Data Escrow NNDN provisioning schema </documentation> </annotation> <element name="abstractNNDN" type="rdeNNDN:abstractContentType" substitutionGroup="rde:content" abstract="true" /> <element name="NNDN" substitutionGroup="rdeNNDN:abstractNNDN" /> <element name="delete" type="rdeNNDN:deleteType" substitutionGroup="rde:delete" /> <!-- Content Type --> <complexType name="abstractContentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element name="aName" type="eppcom:labelType" /> <element name="uName" type="eppcom:labelType" minOccurs="0" /> <element name="idnTableId" type="rdeIDN:idType" minOccurs="0" /> <element name="originalName" type="eppcom:labelType" minOccurs="0" /> <element name="nameState" type="rdeNNDN:nameState" /> <element name="crDate" type="dateTime" minOccurs="0" /> </sequence> </extension> </complexContent> </complexType> <simpleType name="nameStateValue"> <restriction base="token"> <enumeration value="withheld" /> <enumeration value="blocked" /> <enumeration value="mirrored" /> </restriction> </simpleType> <complexType name="nameState"> <simpleContent> <extension base="rdeNNDN:nameStateValue"> <attribute name="mirroringNS" type="boolean" default="true" /> </extension> </simpleContent> </complexType> <!-- Delete Type --> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element name="aName" type="eppcom:labelType" minOccurs="0" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="CSVanchor="xsdRdeCsvNndn" numbered="true" toc="default"> <name>CSV NNDNObject" anchor="xsdRdeCsvNndn"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- Import common element types --> <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:rdeNNDN-1.0" /> <annotation> <documentation> NNDN (NNDN's not domain name) (CSV) Object </documentation> </annotation> <!-- Child elements of the <rde:contents> object --> <element name="contents" type="csvNNDN:contentType" substitutionGroup="rde:content" /> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- Child elements of the <rde:deletes> object --> <element name="deletes" type="csvNNDN:deleteType" substitutionGroup="rde:delete" /> <complexType name="deleteType"> <complexContent> <extension base="rde:deleteType"> <sequence> <element ref="rdeCsv:csv" maxOccurs="unbounded" /> </sequence> </extension> </complexContent> </complexType> <!-- A-Label format name field --> <element name="fAName" type="rdeCsv:fNameRequiredType" substitutionGroup="rdeCsv:field" /> <!-- domain name used to generate the IDN variant field --> <element name="fOriginalName" type="rdeCsv:fNameType" substitutionGroup="rdeCsv:field" /> <!-- RGP status field --> <element name="fNameState" type="csvNNDN:fNameStateType" substitutionGroup="rdeCsv:field" /> <complexType name="fNameStateType"> <complexContent> <extension base="rdeCsv:fieldRequiredType"> <sequence /> <attribute name="type" type="token" default="rdeNNDN\:nameState" /> </extension> </complexContent> </complexType> <!-- Mirroring uses NS mirror mechanism? --> <element name="fMirroringNS" type="rdeCsv:fBooleanType" substitutionGroup="rdeCsv:field" /> <!-- End of schema. --> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="Policy Object" anchor="xsdRdePolicy"> <t> <figure><artwork><![CDATA[<CODE BEGINS>anchor="xsdRdePolicy" numbered="true" toc="default"> <name>Policy Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <annotation> <documentation> Registry Data Escrow Policy schema </documentation> </annotation> <import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <element name="policy" type="rdePolicy:policyType" substitutionGroup="rde:content" /> <complexType name="policyType"> <complexContent> <extension base="rde:contentType"> <attribute name="scope" type="token" use="required" /> <attribute name="element" type="anyURI" use="required" /> </extension> </complexContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="Header Object" anchor="xsdRdeHeader"> <t> <figure><artwork><![CDATA[<CODE BEGINS>anchor="xsdRdeHeader" numbered="true" toc="default"> <name>Header Object</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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:eppcom="urn:ietf:params:xml:ns:eppcom-1.0" xmlns="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <import namespace="urn:ietf:params:xml:ns:rde-1.0" /> <annotation> <documentation> Data Escrow Deposit Header schema </documentation> </annotation> <!-- Root Element --> <element name="header" type="rdeHeader:contentType" substitutionGroup="rde:content" /> <!-- Content Type --> <complexType name="contentType"> <complexContent> <extension base="rde:contentType"> <sequence> <group ref="rdeHeader:repositoryTypeGroup" /> <element name="count" type="rdeHeader:countType" maxOccurs="unbounded" /> <element name="contentTag" type="token" minOccurs="0" /> </sequence> </extension> </complexContent> </complexType> <group name="repositoryTypeGroup"> <choice> <element name="tld" type="eppcom:labelType" /> <element name="registrar" type="positiveInteger" /> <element name="ppsp" type="token" /> <element name="reseller" type="token" /> </choice> </group> <complexType name="countType"> <simpleContent> <extension base="long"> <attribute name="uri" type="anyURI" use="required" /> <attribute name="rcdn" type="eppcom:labelType" /> <attribute name="registrarId" type="positiveInteger" /> </extension> </simpleContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> <sectiontitle="DNRDanchor="xsdRdeDnrdMisc" numbered="true" toc="default"> <name>DNRD CommonObjects" anchor="xsdRdeDnrdMisc"> <t> <figure><artwork><![CDATA[<CODE BEGINS>Objects</name> <sourcecode name="" type="xml" markers="true"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace="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="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <import namespace="urn:ietf:params:xml:ns:eppcom-1.0" /> <annotation> <documentation> Data Escrow Deposit Common Objects schema </documentation> </annotation> <complexType name="rrType"> <simpleContent> <extension base="eppcom:clIDType"> <attribute name="client" type="eppcom:clIDType" /> </extension> </simpleContent> </complexType> </schema><CODE ENDS>]]></artwork></figure> </t>]]></sourcecode> </section> </section> <sectiontitle="Internationalization Considerations">numbered="true" toc="default"> <name>Internationalization Considerations</name> <t> DataEscrowescrow deposits are represented in XML, which provides native support for encoding information using the Unicode character set and its more compact representations including UTF-8. Conformant XML processors recognize both UTF-8 and UTF-16. Though XML includes provisions to identify and use other character encodings through use of an "encoding" attribute in an <?xml?> declaration, the use of UTF-8 isRECOMMENDED.<bcp14>RECOMMENDED</bcp14>. </t> </section> <sectiontitle="IANA Considerations">numbered="true" toc="default"> <name>IANA Considerations</name> <t> This document uses URNs to describe XML namespaces and XML schemas conforming to a registry mechanism described in <xreftarget="RFC3688"/>.target="RFC3688" format="default"/>. The followingURI assignments is requested ofURIs have been assigned by IANA. </t><t>Registration request for the RDE<t>RDE CSV namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeCsv-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</t> <dl spacing="compact"> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:rdeCsv-1.0</dd> <dt>Registrant Contact:</dt><dd>IESG</dd> <dt>XML:</dt><dd>None. Namespace URIs do not represent an XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE CSV XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeCsv-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></t> <dl spacing="compact"> <dt>URI:</dt><dd>urn:ietf:params:xml:schema:rdeCsv-1.0</dd> <dt>Registrant Contact:</dt><dd>IESG</dd> </dl> <t>See <xreftarget="xsdRdeCsv"/>target="xsdRdeCsv" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE domain namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeDomain-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</t> <dl spacing="compact"> <dt>URI: </dt><dd>urn:ietf:params:xml:ns:rdeDomain-1.0</dd> <dt>Registrant Contact:</dt><dd> IESG</dd> <dt>XML: </dt><dd>None. Namespace URIs do not represent an XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE domain XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeDomain-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></t> <dl spacing="compact"> <dt>URI:</dt><dd> urn:ietf:params:xml:schema:rdeDomain-1.0</dd> <dt>Registrant Contact:</dt><dd> IESG</dd> </dl> <t>See <xreftarget="xsdRdeDomain"/>target="xsdRdeDomain" format="default"/> of this document.</t></list> </t> <t>Registration request for the CSV<t>CSV domain namespace:<list> <t>URI: urn:ietf:params:xml:ns:csvDomain-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML:</t> <dl spacing="compact"> <dt>URI:</dt><dd> urn:ietf:params:xml:ns:csvDomain-1.0</dd> <dt>Registrant Contact:</dt><dd> IESG</dd> <dt>XML:</dt><dd> None. Namespace URIs do not represent an XMLspecification.</t> </list> </t> <t>Registration request for the CSVspecification.</dd> </dl> <t>CSV domain XML schema:<list> <t>URI: urn:ietf:params:xml:schema:csvDomain-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></t> <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 <xreftarget="xsdRdeCsvDomain"/>target="xsdRdeCsvDomain" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE host namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeHost-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE host XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeHost-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeHost"/>target="xsdRdeHost" format="default"/> of this document.</t></list> </t> <t>Registration request for the CSV<t>CSV host namespace:<list> <t>URI: urn:ietf:params:xml:ns:csvHost-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the CSVspecification.</dd> </dl> <t>CSV host XML schema:<list> <t>URI: urn:ietf:params:xml:schema:csvHost-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeCsvHost"/>target="xsdRdeCsvHost" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE contact namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeContact-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE contact XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeContact-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeContact"/>target="xsdRdeContact" format="default"/> of this document.</t></list> </t> <t>Registration request for the CSV<t>CSV contact namespace:<list> <t>URI: urn:ietf:params:xml:ns:csvContact-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the CSVspecification.</dd> </dl> <t>CSV contact XML schema:<list> <t>URI: urn:ietf:params:xml:schema:csvContact-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeCsvContact"/>target="xsdRdeCsvContact" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE registrar namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeRegistrar-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE registrar XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeRegistrar-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeRegistrar"/>target="xsdRdeRegistrar" format="default"/> of this document.</t></list> </t> <t>Registration request for the CSV<t>CSV registrar namespace:<list> <t>URI: urn:ietf:params:xml:ns:csvRegistrar-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the CSVspecification.</dd> </dl> <t>CSV registrar XML schema:<list> <t>URI: urn:ietf:params:xml:schema:csvRegistrar-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeCsvRegistrar"/>target="xsdRdeCsvRegistrar" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE IDN namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeIDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE IDN XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeIDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeIdn"/>target="xsdRdeIdn" format="default"/> of this document.</t></list> </t> <t>Registration request for the CSV<t>CSV IDN namespace:<list> <t>URI: urn:ietf:params:xml:ns:csvIDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the CSVspecification.</dd> </dl> <t>CSV IDN XML schema:<list> <t>URI: urn:ietf:params:xml:schema:csvIDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeCsvIdn"/>target="xsdRdeCsvIdn" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE EPP parameters namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeEppParams-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML:</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE EPP parameters XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeEppParams-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeEpp"/>target="xsdRdeEpp" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE NNDN namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeNNDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE NNDN XML schema:<list> <t>URI: urn:ietf:params:xml:schema:rdeNNDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeNndn"/>target="xsdRdeNndn" format="default"/> of this document.</t></list> </t> <t>Registration request for the CSV<t>CSV NNDN namespace:<list> <t>URI: urn:ietf:params:xml:ns:csvNNDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the CSVspecification.</dd> </dl> <t>CSV NNDN XML schema:<list> <t>URI: urn:ietf:params:xml:schema:csvNNDN-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeCsvNndn"/>target="xsdRdeCsvNndn" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE Policy namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdePolicy-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE Policy XML schema:<list> <t>URI: urn:ietf:params:xml:ns:rdePolicy-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdePolicy"/>target="xsdRdePolicy" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE Header namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeHeader-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE Header XML schema:<list> <t>URI: urn:ietf:params:xml:ns:rdeHeader-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeHeader"/>target="xsdRdeHeader" format="default"/> of this document.</t></list> </t> <t>Registration request for the RDE<t>RDE Common Objects namespace:<list> <t>URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t> <t>XML: None.</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 XMLspecification.</t> </list> </t> <t>Registration request for the RDEspecification.</dd> </dl> <t>RDE Common Objects XML schema:<list> <t>URI: urn:ietf:params:xml:ns:rdeDnrdCommon-1.0</t> <t>Registrant Contact: IESG <regext@ietf.org></t> <t>Note to RFC Editor: Please remove the email address from the RFC after IANA records it.</t></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 <xreftarget="xsdRdeDnrdMisc"/>target="xsdRdeDnrdMisc" format="default"/> of this document.</t></list> </t></section> <sectionanchor="ImplementationStatus" title="Implementation Status"> <t>Note to RFC Editor: Please remove this section and the reference to RFC 7942 <xref target="RFC7942"/> before publication.</t>numbered="true" toc="default"> <name>Security Considerations</name> <t> Thissection records the status of known implementations of the protocol defined by thisspecificationatdoes not define thetime of posting of this Internet-Draft, and is based on a proposal described in RFC 7942 <xref target="RFC7942"/>. The description of implementations in this section is intendedsecurity mechanisms toassist the IETF in its decision processesbe used inprogressing drafts to RFCs. Please note thatthelisting of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. </t> <t> According to RFC 7942 <xref target="RFC7942"/>, "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". </t> <section title="Implementation in the gTLD space"> <t>Organization: ICANN</t> <t>Name: ICANN Registry Agreement</t> <t>Description: the ICANN Base Registry Agreement requires Registries, Data Escrow Agents, and ICANN to implement this specification. ICANN receives daily notifications from Data Escrow Agents confirming that more than 1,200 gTLDs are sending deposits that comply with this specification. ICANN receives on a weekly basis per gTLD, from more than 1,200 gTLD registries, a Bulk Registration Data Access file that also complies with this specification. In addition, ICANN is aware of Registry Service Provider transitions using data files that conform to this specification.</t> <t>Level of maturity: production.</t> <t>Coverage: all aspects of this specification are implemented.</t> <t>Version compatibility: versions 03 - 09 are known to be implemented.</t> <t>Contact: gustavo.lozano@icann.org</t> <t>URL: https://www.icann.org/resources/pages/registries/registries-agreements-en</t> </section> </section> <section title="Security Considerations"> <t> This specification does not define the security mechanisms to be used in the transmissiontransmission of the data escrow deposits, since it only specifies the minimum necessary to enable the rebuilding of a registry from deposits without intervention from the original registry. </t> <t> Depending on local policies, some elements, or, most likely, the whole deposit will be considered confidential. As such, the partiesSHOULD<bcp14>SHOULD</bcp14> take all the necessary precautions such as encrypting the data at rest and in transit to avoid inadvertent disclosure of private data. Regardless of the precautions taken by the parties regarding data at rest and in transit, authentication credentialsMUST NOT<bcp14>MUST NOT</bcp14> be escrowed. </t> <t> Authentication of the parties passing data escrow deposit files is also of the utmost importance. The escrow agentMUST<bcp14>MUST</bcp14> properly authenticate the registry's identity before accepting data escrow deposits. The registryMUST<bcp14>MUST</bcp14> authenticate the escrow agent's identity before submitting any data, and the data escrow agentMUST<bcp14>MUST</bcp14> authenticate the identity of the party receiving the data escrow deposits for the purposes deemed appropriate. </t> <t> Additionally, the registry and the escrow agentMUST<bcp14>MUST</bcp14> use integrity checking mechanisms to ensure the data transmitted is what the source intended. Validation of the contents by the parties isRECOMMENDED<bcp14>RECOMMENDED</bcp14> to ensure that the file was transmitted correctly from the registry or escrow agent and that the contents are"meaningful"."meaningful". </t> <t>A few elements in this specification containURLs,URLs; the use of HTTP over TLS (Transport LayerSecurity),Security) <xreftarget="RFC2818"/>target="RFC2818" format="default"/> isRECOMMENDED<bcp14>RECOMMENDED</bcp14> on the URLs. </t> <t>The various data structures in the document include a few places that have internal redundancy, and if the values become inconsistent there can be harmful consequences,such as different entities using different fields as their reference.</t> <t>Note: if Transport Layer Security (TLS) is used when providing an escrow services, the recommendations in <xref target="BCP195"/> MUST be implemented.</t> </section> <section title="Privacy Considerations"> <t> This specification defines a format that may be used to escrow personal data. The process of data escrow is governed by a legal document agreed by the parties, and such legal document must ensure that privacy-sensitive and/or personal data receives the required protection. </t> </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 document were provided by Edward Lewis, Jaap Akkerhuis, Lawrence Conroy, Marc Groeneweg, Michael Young, Chris Wright, Patrick Mevzek, Stephen Morris, Scott 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 this document. </t> </section> <section title="Change History"> <t> [[RFC Editor: Please remove this section.]] </t> <section title="Changes from draft-arias-noguchi-registry-data-escrow-02 to -dnrd-objects-mapping-00"> <t> <list style="numbers"> <t>Added definition for child elements under the <domain> element.</t> <t>Added definition for child elements under the <host> element.</t> <t>Added definition for child elements under the <contact> 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 Variant TLDs. </t> <t>Renamed <icannID> to <gurid> in the <rdeRegistrar>.</t> <t>Renamed <dnssec> to <secDNS> in the <domain> element.</t> <t>Renamed <transfData> to <trnData> in the <domain> element.</t> <t>Added <whoisInfo> element under <rdeRegistrar> 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 and different IDN variants models.</t> <t>Removed subordinated host element from the domain object.</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 into draft-arias-noguchi-dnrd-objects-mapping-02.</t> <t>Changed the cksum attribute of <rdeCsv:file> to use CRC32 and changed all of the sample cksum values to use CRC32, based on feedback from David Kipling.</t> <t>Changed the optional <rdeCsv:sep> element to be an optional "sep" attribute value of the <rdeCsv:csv> element with a default 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, based 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 draft-lozano-icann-registry-interfaces</t> <t>Removed references to the <rdeCsv:fCrRr>, <rdeCsv:fCrID>, and <rdeCsv:fCrDate> from the "hostStatuses" and "hostAddresses" CSV files.</t> <t>Removed references to the <rdeCsv:fCrRr>, <rdeCsv:fCrID>, and <rdeCsv:fCrDate> from the "contactStatuses" CSV file.</t> <t>Removed references to the <rdeCsv:fCrRr>, <rdeCsv:fCrID>, and <rdeCsv:fCrDate> from the "domainContacts", "domainStatuses", and "domainNameServers" CSV files.</t> <t>Changed <rdeCsv:fLanguage> to <rdeCsv:fLang>.</t> <t>Replaced use of <rdeCsv:fLang> to new <rdeCsv:fIdnTableId> field in the "domain", "idnLanguage", and "NNDN" CSV files.</t> <t>Replaced use of <csvHost:fName> with <rdeCsv:fRoid> in the "host" <csvHost:deletes> <rdeCsv:csv> element.</t> <t>Changed the foreign key of the hosts to use <rdeCsv:fRoid> instead of <csvHost:fName> and removed use of <csvHost:fName> in the "domainNameServers", "hostStatuses", and "hostAddresses" CSV files.</t> <t>Added use of the MUST keyword for CSV fields that are required to be supported in an EPP based system.</t> <t>Removed use of the <rdeCsv:fRoid> field element for the "registrar" CSV file.</t> <t>Added definition of <csvNNDN:fMirroringNS> 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 using the CSV and XML model.</t> <t>Made <rdeCsv:fExDate> optional for the "domainTransfer" CSV file to match the XML definition.</t> <t>Made <csvDomain:fOriginalName> optional for the "domain" CSV file to match the XML definition.</t> <t>Made <rdeCsv:fTrDate> optional for the "domain" and "contact" CSV files to match the XML definition.</t> <t>Change <idnTableId> 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 sub-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 section to support the domain host attributes model of <xref target="RFC5731"/>.</t> <t>Made the required fields in the CSV format consistent with the XML format. The CSV fields updated to be required include: <rdeCsv:fCrDate>, <csvDomain:fContactType>, <csvDomain:fStatus>, <csvDomain:fKeyTag>, <csvDomain:fDsAlg>, <csvDomain:fDigestType>, <csvDomain:fDigest>, <csvDomain:fFlags>, <csvDomain:fProtocol>, <csvDomain:fKeyAlg>, <csvDomain:fPubKey>, <rdeCsv:fTrStatus>, <rdeCsv:fReRr>, <rdeCsv:fReDate<, <rdeCsv:fAcRr>, <rdeCsv:fAcDate>, <csvHost:fStatus>, <csvContact:fCc>, <csvContact:fStatus>, <csvContact:fPostalType>, <csvRegistrar:fStatus>, and <csvNNDN:fNameState>.</t> <t>Revised the CSV examples to use a more realistic set of records.</t> </list> </t> </section> <section title="Changes from 06 to 07"> <t> <list style="numbers"> <t>Created "repositoryTypeGroup" group element in the rdeHeader including the <rdeHeader:registrar>, <rdeHeader:ppsp> and <rdeHeader:tld> elements.</t> <t>Added the optional "rcdn" and "registrarId" attributes to the <rdeHeader:count> 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 support greater flexibility for the implementation of policies: status, postalInfo, email and crDate.</t> <t>The following domain name elements were made optional to support 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="csvDnssecDefinition"/>.</t> <t>Added MAY clause when the DS Data Interface is used in section <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 <rdeHeader:reseller> element to the "repositoryTypeGroup" 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 <rdeCsv:fClID> or <csvRegistrar:fGurid> fields in the CSV "domain", "host", and "contact" definitions.</t> <t>Added a choice between the use of the <rdeCsv:fRoid> or <csvHost:fName> fields in the CSV "domainNameServers" definition.</t> <t>Changed "of client" to "of the client" throughout the document.</t> <t>Modified all references of 'The attribute isRequired MUST equal "true".' to 'The attribute "isRequired" MUST equal "true".'</t> <t>Combined the <csvDomain:fName> and <csvDomain:fContactType> fields in a single required list for the CSV "domainContacts" definition.</t> <t>Combined the <csvDomain:fName>, <csvDomain:fStatus>, and <csvDomain:fRgpStatus> fields in a single required list for the CSV "domainStatuses" definition.</t> <t>Moved the <rdeCsv:fCrRr> the <rdeCsv:fUpRr> fields to the MAY list for the CSV "domain", "host", and "contact" definitions.</t> <t>Made the order of the <rdeCsv:fCrRr>, <rdeCsv:crID>, <rdeCsv:UpRr>, and <rdeCsv:UpID> fields more consistent in the CSV lists.</t> <t>Fixed an error in the order of the <contact> object example.</t> <t>Changed <rdeCsv:fCrDate> to be optional to match <crDate> being optional in the XML model, by having it use type rdeCsv:fDateTimeType instead of rdeCsv:fRequiredDateTimeType and ensuring that <rdeCsv:fCrDate> is included in the MAY field lists and not the MUST field lists.</t> <t>Made <rdeCsv:fExDate> optional for the "domain" CSV definition 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 <rdeCsv:fUpDate> optional for the "domain" and "contact" CSV definitions to be consistent with the XML model, by moving the field to the MAY field list.</t> <t>Made <rdeCsv:fCrRr> optional to be consistent with the XML model, by having it use type rdeCsv:fClIDType instead of rdeCsv:fClIDRequiredType.</t> <t>Made <rdeCsv:fReRr> required to be consistent with the XML model, by having it use type rdeCsv:fClIDRequiredType instead of rdeCsv:fClIDType.</t> <t>Made the <csvRegistrar:fGurid> field in the "host", "contact", and "registrar" CSV definitions required explicitly by removing 'and isRequired="true"' and adding the sentence 'The attribute isRequired MUST equal "true".', when it is chosen as the primary field.</t> <t>Removed extra '/>.' at the end of the <csvHost:fStatus> field description in the "hostStatuses" CSV definition.</t> <t>Made the <csvRegistrar:fStatus> field optional to be consistent with the XML model, by having csvRegistrar:fStatusType extend rdeCsv:fieldOptionalType instead of rdeCsv:fRequiredType.</t> <t>Made the <csvContact:fEmail> field for the "registrar" CSV definition explicitly optional to be consistent with the XML model, by adding the sentence 'The attribute isRequired MUST equal "false".' 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 <csvRegistrar:fId> and <csvRegistrar:fGurid> fields in the deletes "registrar" CSV definition to be consistent with the "registrar" CSV definition.</t> <t>Made the <crRr> and <crDate> elements optional for 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 .example TLD.</t> <t>The introduction was enhanced by explaining the need for data escrow and the proposed solution.</t> <t>Explanation regarding NNDN was improved.</t> <t>Explanation regarding the CSV and XML model was improved.</t> <t>Section 4.5 updated to make the text clearer.</t> <t>draft-arias-noguchi-registry-data-escrow is now 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 examples 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 target="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: https://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: https://mailarchive.ietf.org/arch/msg/regext/hDLz2ym4oR-ukA4Fm-QJ8FzaxxE</t> <t>Changes based on the feedback provided here: https://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: https://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 onsuch as different entities using different fields as their reference.</t> <aside><t>Note: if TLS is used when providing an escrow service, thefeedback provided here: https://mailarchive.ietf.org/arch/msg/regext/ExUZenwC81ZQe9x24-8IKT_FWm8</t> </list> </t>recommendations in <xref target="BCP195" format="default"/> <bcp14>MUST</bcp14> be implemented.</t></aside> </section> <sectiontitle="Changes REGEXT 10 to REGEXT 11">numbered="true" toc="default"> <name>Privacy Considerations</name> <t><list style="numbers"> <t>Changes based onThis specification defines a format that may be used to escrow personal data. The process of data escrow is governed by a legal document that is agreed to by thefeedback provided here: https://mailarchive.ietf.org/arch/msg/regext/ghEr55r7CVdwUSvkvMGpol4aSh0</t> </list>parties, and such a legal document must ensure that privacy-sensitive and/or personal data receives the required protection. </t> </section></section><sectiontitle="Examplenumbered="true" toc="default"> <name>Example of a Full DepositusingUsing the XMLmodel"> <t> <figure> <preamble> ExampleModel</name> <t keepWithNext="true"> The following is an example of a Full Deposit using the XML model:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <rde:deposit type="FULL" id="20191017001" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:rdePolicy="urn:ietf:params:xml:ns:rdePolicy-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <rde:watermark>2019-10-17T00:00:00Z</rde:watermark> <rde:rdeMenu> <rde:version>1.0</rde:version> <rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeRegistrar-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeIDN-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeNNDN-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0 </rde:objURI> </rde:rdeMenu> <!-- Contents --> <rde:contents> <!-- Header --> <rdeHeader:header> <rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeDomain-1.0">2 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeHost-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeContact-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 </rdeHeader:count> </rdeHeader:header> <!-- Domain: example1.example --> <rdeDomain:domain> <rdeDomain:name>example1.example</rdeDomain:name> <rdeDomain:roid>Dexample1-TEST</rdeDomain:roid> <rdeDomain:status s="ok"/> <rdeDomain:registrant>jd1234</rdeDomain:registrant> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact> <rdeDomain:ns> <domain:hostObj>ns1.example.com</domain:hostObj> <domain:hostObj>ns1.example1.example</domain:hostObj> </rdeDomain:ns> <rdeDomain:clID>RegistrarX</rdeDomain:clID> <rdeDomain:crRr client="jdoe">RegistrarX</rdeDomain:crRr> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate> <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate> </rdeDomain:domain> <!-- Domain: example2.example --> <rdeDomain:domain> <rdeDomain:name>example2.example</rdeDomain:name> <rdeDomain:roid>Dexample2-TEST</rdeDomain:roid> <rdeDomain:status s="ok"/> <rdeDomain:status s="clientUpdateProhibited"/> <rdeDomain:registrant>jd1234</rdeDomain:registrant> <rdeDomain:contact type="admin">sh8013</rdeDomain:contact> <rdeDomain:contact type="tech">sh8013</rdeDomain:contact> <rdeDomain:clID>RegistrarX</rdeDomain:clID> <rdeDomain:crRr>RegistrarX</rdeDomain:crRr> <rdeDomain:crDate>1999-04-03T22:00:00.0Z</rdeDomain:crDate> <rdeDomain:exDate>2025-04-03T22:00:00.0Z</rdeDomain:exDate> </rdeDomain:domain> <!-- Host: ns1.example.example --> <rdeHost:host> <rdeHost:name>ns1.example1.example</rdeHost:name> <rdeHost:roid>Hns1_example_test-TEST</rdeHost:roid> <rdeHost:status s="ok"/> <rdeHost:status s="linked"/> <rdeHost:addr ip="v4">192.0.2.2</rdeHost:addr> <rdeHost:addr ip="v4">192.0.2.29</rdeHost:addr> <rdeHost:addr ip="v6">2001:DB8:1::1</rdeHost:addr> <rdeHost:clID>RegistrarX</rdeHost:clID> <rdeHost:crRr>RegistrarX</rdeHost:crRr> <rdeHost:crDate>1999-05-08T12:10:00.0Z</rdeHost:crDate> <rdeHost:upRr>RegistrarX</rdeHost:upRr> <rdeHost:upDate>2009-10-03T09:34:00.0Z</rdeHost:upDate> </rdeHost:host> <!-- Contact: sh8013 --> <rdeContact:contact> <rdeContact:id>sh8013</rdeContact:id> <rdeContact:roid>Csh8013-TEST</rdeContact:roid> <rdeContact:status s="linked"/> <rdeContact:status s="clientDeleteProhibited"/> <rdeContact:postalInfo type="int"> <contact:name>John Doe</contact:name> <contact:org>Example Inc.</contact:org> <contact:addr> <contact:street>123 Example Dr.</contact:street> <contact:street>Suite 100</contact:street> <contact:city>Dulles</contact:city> <contact:sp>VA</contact:sp> <contact:pc>20166-6503</contact:pc> <contact:cc>US</contact:cc> </contact:addr> </rdeContact:postalInfo> <rdeContact:voice x="1234">+1.7035555555 </rdeContact:voice> <rdeContact:fax>+1.7035555556 </rdeContact:fax> <rdeContact:email>jdoe@example.example </rdeContact:email> <rdeContact:clID>RegistrarX</rdeContact:clID> <rdeContact:crRr client="jdoe">RegistrarX </rdeContact:crRr> <rdeContact:crDate>2009-09-13T08:01:00.0Z </rdeContact:crDate> <rdeContact:upRr client="jdoe">RegistrarX </rdeContact:upRr> <rdeContact:upDate>2009-11-26T09:10:00.0Z </rdeContact:upDate> <rdeContact:trDate>2009-12-03T09:05:00.0Z </rdeContact:trDate> <rdeContact:disclose flag="0"> <contact:voice/> <contact:email/> </rdeContact:disclose> </rdeContact:contact> <!-- Registrar: RegistrarX --> <rdeRegistrar:registrar> <rdeRegistrar:id>RegistrarX</rdeRegistrar:id> <rdeRegistrar:name>Registrar X</rdeRegistrar:name> <rdeRegistrar:gurid>8</rdeRegistrar:gurid> <rdeRegistrar:status>ok</rdeRegistrar:status> <rdeRegistrar:postalInfo type="int"> <rdeRegistrar:addr> <rdeRegistrar:street>123 Example Dr. </rdeRegistrar:street> <rdeRegistrar:street>Suite 100 </rdeRegistrar:street> <rdeRegistrar:city>Dulles</rdeRegistrar:city> <rdeRegistrar:sp>VA</rdeRegistrar:sp> <rdeRegistrar:pc>20166-6503</rdeRegistrar:pc> <rdeRegistrar:cc>US</rdeRegistrar:cc> </rdeRegistrar:addr> </rdeRegistrar:postalInfo> <rdeRegistrar:voice x="1234">+1.7035555555 </rdeRegistrar:voice> <rdeRegistrar:fax>+1.7035555556 </rdeRegistrar:fax> <rdeRegistrar:email>jdoe@example.example </rdeRegistrar:email> <rdeRegistrar:url>http://www.example.example </rdeRegistrar:url> <rdeRegistrar:whoisInfo> <rdeRegistrar:name>whois.example.example </rdeRegistrar:name> <rdeRegistrar:url>http://whois.example.example </rdeRegistrar:url> </rdeRegistrar:whoisInfo> <rdeRegistrar:crDate>2005-04-23T11:49:00.0Z </rdeRegistrar:crDate> <rdeRegistrar:upDate>2009-02-17T17:51:00.0Z </rdeRegistrar:upDate> </rdeRegistrar:registrar> <!-- IDN Table --> <rdeIDN:idnTableRef id="pt-BR"> <rdeIDN:url> http://www.iana.org/domains/idn-tables/tables/br_pt-br_1.0.html </rdeIDN:url> <rdeIDN:urlPolicy> http://registro.br/dominio/regras.html </rdeIDN:urlPolicy> </rdeIDN:idnTableRef> <!-- NNDN: pinguino.example --> <rdeNNDN:NNDN> <rdeNNDN:aName>xn--exampl-gva.example</rdeNNDN:aName> <rdeNNDN:idnTableId>pt-BR</rdeNNDN:idnTableId> <rdeNNDN:originalName>example1.example</rdeNNDN:originalName> <rdeNNDN:nameState>withheld</rdeNNDN:nameState> <rdeNNDN:crDate>2005-04-23T11:49:00.0Z</rdeNNDN:crDate> </rdeNNDN:NNDN> <!-- EppParams --> <rdeEppParams:eppParams> <rdeEppParams:version>1.0</rdeEppParams:version> <rdeEppParams:lang>en</rdeEppParams:lang> <rdeEppParams:objURI> urn:ietf:params:xml:ns:domain-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI> urn:ietf:params:xml:ns:contact-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI> urn:ietf:params:xml:ns:host-1.0 </rdeEppParams:objURI> <rdeEppParams:svcExtension> <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0 </epp:extURI> <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1 </epp:extURI> </rdeEppParams:svcExtension> <rdeEppParams:dcp> <epp:access><epp:all/></epp:access> <epp:statement> <epp:purpose> <epp:admin/> <epp:prov/> </epp:purpose> <epp:recipient> <epp:ours/> <epp:public/> </epp:recipient> <epp:retention> <epp:stated/> </epp:retention> </epp:statement> </rdeEppParams:dcp> </rdeEppParams:eppParams> <rdePolicy:policy scope="//rde:deposit/rde:contents/rdeDomain:domain" element="rdeDomain:registrant" /> </rde:contents></rde:deposit>]]> </artwork></figure> </t></rde:deposit> ]]></sourcecode> </section> <sectiontitle="Examplenumbered="true" toc="default"> <name>Example of a Differential DepositusingUsing the XMLmodel"> <t> <figure> <preamble> ExampleModel</name> <t keepWithNext="true"> The following is an example of a Differential Deposit using the XML model:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <rde:deposit type="DIFF" id="20191017002" prevId="20191017001" xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" xmlns:contact="urn:ietf:params:xml:ns:contact-1.0" xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:rdeDomain="urn:ietf:params:xml:ns:rdeDomain-1.0" xmlns:rdeHost="urn:ietf:params:xml:ns:rdeHost-1.0" xmlns:rdeContact="urn:ietf:params:xml:ns:rdeContact-1.0" xmlns:rdeRegistrar="urn:ietf:params:xml:ns:rdeRegistrar-1.0" xmlns:rdeIDN="urn:ietf:params:xml:ns:rdeIDN-1.0" xmlns:rdeNNDN="urn:ietf:params:xml:ns:rdeNNDN-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" xmlns:epp="urn:ietf:params:xml:ns:epp-1.0"> <rde:watermark>2019-10-17T00:00:00Z</rde:watermark> <rde:rdeMenu> <rde:version>1.0</rde:version> <rde:objURI>urn:ietf:params:xml:ns:rdeHeader-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeContact-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeHost-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeDomain-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeRegistrar-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeIDN-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeNNDN-1.0 </rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0 </rde:objURI> </rde:rdeMenu> <!-- Deletes --> <rde:deletes> <rdeDomain:delete> <rdeDomain:name>example2.example</rdeDomain:name> </rdeDomain:delete> </rde:deletes> <!-- Contents --> <rde:contents> <!-- Header --> <rdeHeader:header> <rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeDomain-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeHost-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeContact-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeRegistrar-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeIDN-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeNNDN-1.0">1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0">1 </rdeHeader:count> </rdeHeader:header> </rde:contents></rde:deposit>]]> </artwork></figure> </t></rde:deposit> ]]></sourcecode> </section> <sectiontitle="Examplenumbered="true" toc="default"> <name>Example of a Full DepositusingUsing the CSVmodel"> <t> <figure> <preamble> ExampleModel</name> <t keepWithNext="true"> The following is an example of a Full Deposit using the CSV model:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <rde:deposit xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" type="FULL" id="20191017001"> <rde:watermark>2019-10-18T00:00:00Z</rde:watermark> <rde:rdeMenu> <rde:version>1.0</rde:version> <rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvNNDN-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:rdeEppParams-1.0</rde:objURI> </rde:rdeMenu> <rde:contents> <rdeHeader:header> <rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvDomain-1.0"> 4 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvHost-1.0"> 6 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvContact-1.0"> 9 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvRegistrar-1.0"> 3 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvIDN-1.0"> 2 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvNNDN-1.0"> 2 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0"> 1 </rdeHeader:count> </rdeHeader:header> <csvDomain:contents> <rdeCsv:csv name="domain" sep=","> <rdeCsv:fields> <csvDomain:fName/> <rdeCsv:fRoid/> <rdeCsv:fIdnTableId/> <csvDomain:fOriginalName/> <rdeCsv:fRegistrant/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fExDate isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="75E2D01F"> domain-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainContacts" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvContact:fId/> <csvDomain:fContactType/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="70A7C17B"> domainContacts-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainStatuses" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> <csvDomain:fRgpStatus/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="EB8C548E"> domainStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainNameServers" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvHost:fName parent="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="984C3097"> domainNameServers-name-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainNameServers" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <rdeCsv:fRoid/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="569D4638"> domainNameServers-roid-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="dnssec" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fMaxSigLife/> <csvDomain:fKeyTag/> <csvDomain:fDsAlg/> <csvDomain:fDigestType/> <csvDomain:fDigest/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="AA15CB43"> dnssec-ds-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="dnssec" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fMaxSigLife/> <csvDomain:fFlags/> <csvDomain:fProtocol/> <csvDomain:fKeyAlg/> <csvDomain:fPubKey/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="1B16F334"> dnssec-key-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainTransfer" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <rdeCsv:fTrStatus/> <rdeCsv:fReRr/> <rdeCsv:fReID/> <rdeCsv:fReDate/> <rdeCsv:fAcRr/> <rdeCsv:fAcID/> <rdeCsv:fAcDate/> <rdeCsv:fExDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="71170194"> domainTransfer-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvDomain:contents> <csvHost:contents> <rdeCsv:csv name="host" sep=","> <rdeCsv:fields> <csvHost:fName/> <rdeCsv:fRoid/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fTrDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="120938E3"> host-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="hostStatuses" sep=","> <rdeCsv:fields> <rdeCsv:fRoid parent="true"/> <csvHost:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="0BA504FC"> hostStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="hostAddresses" sep=","> <rdeCsv:fields> <rdeCsv:fRoid parent="true"/> <csvHost:fAddr isRequired="true"/> <csvHost:fAddrVersion isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="17888F02"> hostAddresses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvHost:contents> <csvContact:contents> <rdeCsv:csv name="contact" sep=","> <rdeCsv:fields> <csvContact:fId/> <rdeCsv:fRoid/> <csvContact:fVoice/> <csvContact:fVoiceExt/> <csvContact:fFax/> <csvContact:fFaxExt/> <csvContact:fEmail/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D7F106A5"> contact-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactStatuses" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="2AAF99D4"> contactStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactPostal" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fPostalType/> <csvContact:fName/> <csvContact:fOrg/> <csvContact:fStreet index="0"/> <csvContact:fStreet index="1"/> <csvContact:fStreet index="2"/> <csvContact:fCity/> <csvContact:fSp/> <csvContact:fPc/> <csvContact:fCc/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="02CC2504"> contactPostal-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactTransfer" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <rdeCsv:fTrStatus/> <rdeCsv:fReRr/> <rdeCsv:fReID/> <rdeCsv:fReDate/> <rdeCsv:fAcRr/> <rdeCsv:fAcID/> <rdeCsv:fAcDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D0929632"> contactTransfer-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactDisclose" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fDiscloseFlag/> <csvContact:fDiscloseNameLoc/> <csvContact:fDiscloseNameInt/> <csvContact:fDiscloseOrgLoc/> <csvContact:fDiscloseOrgInt/> <csvContact:fDiscloseAddrLoc/> <csvContact:fDiscloseAddrInt/> <csvContact:fDiscloseVoice/> <csvContact:fDiscloseFax/> <csvContact:fDiscloseEmail/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="89043A90"> contactDisclose-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvContact:contents> <csvRegistrar:contents> <rdeCsv:csv name="registrar" sep=","> <rdeCsv:fields> <csvRegistrar:fId/> <csvRegistrar:fName isLoc="false"/> <csvRegistrar:fGurid/> <csvRegistrar:fStatus/> <csvContact:fStreet isLoc="false" index="0"/> <csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="2"/> <csvContact:fCity isLoc="false" /> <csvContact:fSp isLoc="false" /> <csvContact:fPc isLoc="false" /> <csvContact:fCc isLoc="false" /> <csvContact:fVoice/> <csvContact:fVoiceExt/> <csvContact:fFax/> <csvContact:fFaxExt/> <csvContact:fEmail isRequired="false"/> <rdeCsv:fUrl/> <csvRegistrar:fWhoisUrl/> <rdeCsv:fCrDate/> <rdeCsv:fUpDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="306178BB"> registrar-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvRegistrar:contents> <csvIDN:contents> <rdeCsv:csv name="idnLanguage" sep=","> <rdeCsv:fields> <rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fUrl isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D462EAD0"> idnLanguage-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvIDN:contents> <csvNNDN:contents> <rdeCsv:csv name="NNDN" sep=","> <rdeCsv:fields> <csvNNDN:fAName/> <rdeCsv:fIdnTableId/> <csvNNDN:fOriginalName/> <csvNNDN:fNameState/> <csvNNDN:fMirroringNS/> <rdeCsv:fCrDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="11C80D60"> NNDN-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvNNDN:contents> <rdeEppParams:eppParams> <rdeEppParams:version>1.0</rdeEppParams:version> <rdeEppParams:lang>en</rdeEppParams:lang> <rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0 </rdeEppParams:objURI> <rdeEppParams:svcExtension> <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1 </epp:extURI> <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0 </epp:extURI> </rdeEppParams:svcExtension> <rdeEppParams:dcp> <epp:access> <epp:all/> </epp:access> <epp:statement> <epp:purpose> <epp:admin/> <epp:other/> <epp:prov/> </epp:purpose> <epp:recipient> <epp:ours/> <epp:public/> <epp:unrelated/> </epp:recipient> <epp:retention> <epp:indefinite/> </epp:retention> </epp:statement> </rdeEppParams:dcp> </rdeEppParams:eppParams> </rde:contents></rde:deposit>]]> </artwork></figure> </t></rde:deposit> ]]></sourcecode> </section> <sectiontitle="Examplenumbered="true" toc="default"> <name>Example of a Differential DepositusingUsing the CSVmodel"> <t> <figure> <preamble> ExampleModel</name> <t keepWithNext="true"> The following is an example of a Differential Deposit using the CSV model:</preamble> <artwork><![CDATA[</t> <sourcecode name="" type="xml" markers="false"><![CDATA[ <?xml version="1.0" encoding="UTF-8"?> <rde:deposit xmlns:epp="urn:ietf:params:xml:ns:epp-1.0" xmlns:rde="urn:ietf:params:xml:ns:rde-1.0" xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0" xmlns:csvDomain="urn:ietf:params:xml:ns:csvDomain-1.0" xmlns:csvHost="urn:ietf:params:xml:ns:csvHost-1.0" xmlns:csvContact="urn:ietf:params:xml:ns:csvContact-1.0" xmlns:csvRegistrar="urn:ietf:params:xml:ns:csvRegistrar-1.0" xmlns:csvIDN="urn:ietf:params:xml:ns:csvIDN-1.0" xmlns:rdeHeader="urn:ietf:params:xml:ns:rdeHeader-1.0" xmlns:csvNNDN="urn:ietf:params:xml:ns:csvNNDN-1.0" xmlns:rdeEppParams="urn:ietf:params:xml:ns:rdeEppParams-1.0" type="DIFF" id="20191017001" prevId="20191010001"> <rde:watermark>2019-10-18T00:00:00Z</rde:watermark> <rde:rdeMenu> <rde:version>1.0</rde:version> <rde:objURI>urn:ietf:params:xml:ns:csvDomain-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvHost-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvContact-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvRegistrar-1.0</rde:objURI> <rde:objURI>urn:ietf:params:xml:ns:csvIDN-1.0</rde:objURI> </rde:rdeMenu> <rde:deletes> <csvDomain:deletes> <rdeCsv:csv name="domain"> <rdeCsv:fields> <csvDomain:fName/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="6F2B988F"> domain-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvDomain:deletes> <csvHost:deletes> <rdeCsv:csv name="host"> <rdeCsv:fields> <rdeCsv:fRoid/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="E3408F5E"> host-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvHost:deletes> <csvContact:deletes> <rdeCsv:csv name="contact"> <rdeCsv:fields> <csvContact:fId/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="6F2B988F"> contact-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvContact:deletes> <csvRegistrar:deletes> <rdeCsv:csv name="registrar"> <rdeCsv:fields> <csvRegistrar:fId/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="307B87AE"> registrar-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvRegistrar:deletes> <csvIDN:deletes> <rdeCsv:csv name="idnLanguage"> <rdeCsv:fields> <rdeCsv:fIdnTableId/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="757B573A"> idnLanguage-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvIDN:deletes> <csvNNDN:deletes> <rdeCsv:csv name="NNDN"> <rdeCsv:fields> <csvNNDN:fAName/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="FF104E83"> NNDN-delete-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvNNDN:deletes> </rde:deletes> <rde:contents> <rdeHeader:header> <rdeHeader:tld>test</rdeHeader:tld> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvDomain-1.0"> 2 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvHost-1.0"> 2 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvContact-1.0"> 3 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvRegistrar-1.0"> 1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvIDN-1.0"> 1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:csvNNDN-1.0"> 1 </rdeHeader:count> <rdeHeader:count uri="urn:ietf:params:xml:ns:rdeEppParams-1.0"> 1 </rdeHeader:count> </rdeHeader:header> <csvDomain:contents> <rdeCsv:csv name="domain" sep=","> <rdeCsv:fields> <csvDomain:fName/> <rdeCsv:fRoid/> <rdeCsv:fIdnTableId/> <csvDomain:fOriginalName/> <rdeCsv:fRegistrant/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fExDate isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="75E2D01F"> domain-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainContacts" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvContact:fId/> <csvDomain:fContactType/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="70A7C17B"> domainContacts-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainStatuses" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> <csvDomain:fRgpStatus/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="EB8C548E"> domainStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainNameServers" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvHost:fName parent="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="984C3097"> domainNameServers-name-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainNameServers" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <rdeCsv:fRoid/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="569D4638"> domainNameServers-roid-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="dnssec" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fMaxSigLife/> <csvDomain:fKeyTag/> <csvDomain:fDsAlg/> <csvDomain:fDigestType/> <csvDomain:fDigest/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="AA15CB43"> dnssec-ds-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="dnssec" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <csvDomain:fMaxSigLife/> <csvDomain:fFlags/> <csvDomain:fProtocol/> <csvDomain:fKeyAlg/> <csvDomain:fPubKey/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="1B16F334"> dnssec-key-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="domainTransfer" sep=","> <rdeCsv:fields> <csvDomain:fName parent="true"/> <rdeCsv:fTrStatus/> <rdeCsv:fReRr/> <rdeCsv:fReID/> <rdeCsv:fReDate/> <rdeCsv:fAcRr/> <rdeCsv:fAcID/> <rdeCsv:fAcDate/> <rdeCsv:fExDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="71170194"> domainTransfer-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvDomain:contents> <csvHost:contents> <rdeCsv:csv name="host" sep=","> <rdeCsv:fields> <csvHost:fName/> <rdeCsv:fRoid/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> <rdeCsv:fTrDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="120938E3"> host-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="hostStatuses" sep=","> <rdeCsv:fields> <rdeCsv:fRoid parent="true"/> <csvHost:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="0BA504FC"> hostStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="hostAddresses" sep=","> <rdeCsv:fields> <rdeCsv:fRoid parent="true"/> <csvHost:fAddr isRequired="true"/> <csvHost:fAddrVersion isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="17888F02"> hostAddresses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvHost:contents> <csvContact:contents> <rdeCsv:csv name="contact" sep=","> <rdeCsv:fields> <csvContact:fId/> <rdeCsv:fRoid/> <csvContact:fVoice/> <csvContact:fVoiceExt/> <csvContact:fFax/> <csvContact:fFaxExt/> <csvContact:fEmail/> <rdeCsv:fClID/> <rdeCsv:fCrRr/> <rdeCsv:fCrID/> <rdeCsv:fCrDate/> <rdeCsv:fUpRr/> <rdeCsv:fUpID/> <rdeCsv:fUpDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D7F106A5"> contact-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactStatuses" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fStatus/> <rdeCsv:fStatusDescription/> <rdeCsv:fLang/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="2AAF99D4"> contactStatuses-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactPostal" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fPostalType/> <csvContact:fName/> <csvContact:fOrg/> <csvContact:fStreet index="0"/> <csvContact:fStreet index="1"/> <csvContact:fStreet index="2"/> <csvContact:fCity/> <csvContact:fSp/> <csvContact:fPc/> <csvContact:fCc/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="02CC2504"> contactPostal-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactTransfer" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <rdeCsv:fTrStatus/> <rdeCsv:fReRr/> <rdeCsv:fReID/> <rdeCsv:fReDate/> <rdeCsv:fAcRr/> <rdeCsv:fAcID/> <rdeCsv:fAcDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D0929632"> contactTransfer-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> <rdeCsv:csv name="contactDisclose" sep=","> <rdeCsv:fields> <csvContact:fId parent="true"/> <csvContact:fDiscloseFlag/> <csvContact:fDiscloseNameLoc/> <csvContact:fDiscloseNameInt/> <csvContact:fDiscloseOrgLoc/> <csvContact:fDiscloseOrgInt/> <csvContact:fDiscloseAddrLoc/> <csvContact:fDiscloseAddrInt/> <csvContact:fDiscloseVoice/> <csvContact:fDiscloseFax/> <csvContact:fDiscloseEmail/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="89043A90"> contactDisclose-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvContact:contents> <csvRegistrar:contents> <rdeCsv:csv name="registrar" sep=","> <rdeCsv:fields> <csvRegistrar:fId/> <csvRegistrar:fName isLoc="false"/> <csvRegistrar:fGurid/> <csvRegistrar:fStatus/> <csvContact:fStreet isLoc="false" index="0"/> <csvContact:fStreet isLoc="false" index="1"/> <csvContact:fStreet isLoc="false" index="2"/> <csvContact:fCity isLoc="false" /> <csvContact:fSp isLoc="false" /> <csvContact:fPc isLoc="false" /> <csvContact:fCc isLoc="false" /> <csvContact:fVoice/> <csvContact:fVoiceExt/> <csvContact:fFax/> <csvContact:fFaxExt/> <csvContact:fEmail isRequired="false"/> <rdeCsv:fUrl/> <csvRegistrar:fWhoisUrl/> <rdeCsv:fCrDate/> <rdeCsv:fUpDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="306178BB"> registrar-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvRegistrar:contents> <csvIDN:contents> <rdeCsv:csv name="idnLanguage" sep=","> <rdeCsv:fields> <rdeCsv:fIdnTableId isRequired="true"/> <rdeCsv:fUrl isRequired="true"/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="D462EAD0"> idnLanguage-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvIDN:contents> <csvNNDN:contents> <rdeCsv:csv name="NNDN" sep=","> <rdeCsv:fields> <csvNNDN:fAName/> <rdeCsv:fIdnTableId/> <csvNNDN:fOriginalName/> <csvNNDN:fNameState/> <csvNNDN:fMirroringNS/> <rdeCsv:fCrDate/> </rdeCsv:fields> <rdeCsv:files> <rdeCsv:file cksum="11C80D60"> NNDN-YYYYMMDD.csv </rdeCsv:file> </rdeCsv:files> </rdeCsv:csv> </csvNNDN:contents> <rdeEppParams:eppParams> <rdeEppParams:version>1.0</rdeEppParams:version> <rdeEppParams:lang>en</rdeEppParams:lang> <rdeEppParams:objURI>urn:ietf:params:xml:ns:domain-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI>urn:ietf:params:xml:ns:host-1.0 </rdeEppParams:objURI> <rdeEppParams:objURI>urn:ietf:params:xml:ns:contact-1.0 </rdeEppParams:objURI> <rdeEppParams:svcExtension> <epp:extURI>urn:ietf:params:xml:ns:secDNS-1.1 </epp:extURI> <epp:extURI>urn:ietf:params:xml:ns:rgp-1.0 </epp:extURI> </rdeEppParams:svcExtension> <rdeEppParams:dcp> <epp:access> <epp:all/> </epp:access> <epp:statement> <epp:purpose> <epp:admin/> <epp:other/> <epp:prov/> </epp:purpose> <epp:recipient> <epp:ours/> <epp:public/> <epp:unrelated/> </epp:recipient> <epp:retention> <epp:indefinite/> </epp:retention> </epp:statement> </rdeEppParams:dcp> </rdeEppParams:eppParams> </rde:contents></rde:deposit>]]> </artwork></figure> </t></rde:deposit> ]]></sourcecode> </section> </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; <reference<references> <name>References</name> <references> <name>Normative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.0791.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3339.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3915.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5730.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5731.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5732.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5733.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5891.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5910.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5952.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6234.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8499.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8909.xml"/> <referencegroup anchor="BCP195" target="https://www.rfc-editor.org/info/bcp195"><front> <title>Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)</title> <author initials="Y." surname="Sheffer" fullname="Y. Sheffer"> <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><xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7525.xml"/> </referencegroup> <reference anchor="ISO-3166-1"> <front> <title> Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes </title><author fullname="ISO Standard 3166"><author> <organization>International Organization for Standardization</organization> </author> <datemonth="November" year="2006"/>month="August" year="2020"/> </front> <seriesInfo name="ISO Standard" value="3166"/> </reference> <reference anchor="ITU-E164"> <front> <title> The international public telecommunication numbering plan </title> <author> <organization>International Telecommunication Union</organization> </author> <date month="February" year="2005"/> </front> <seriesInfo name="ITU-T Recommendation" value="E.164"/> </reference> <reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2008/REC-xml-20081126/"> <front><title abbrev='Extensible Markup Language (XML) 1.0 (Fifth Edition) REC-xml-20081126'>Extensible<title>Extensible Markup Language (XML) 1.0 (Fifth Edition) REC-xml-20081126</title> <author initials="T." surname="Bray" fullname="TimBray" />Bray"/> <author initials="J." surname="Paoli" fullname="JeanPaoli" />Paoli"/> <author initials="C. M." surname="Sperberg-McQueen" fullname="C. M.Sperberg-McQueen" />Sperberg-McQueen"/> <author initials="E." surname="Maler" fullname="EveMaler" />Maler"/> <author initials="F." surname="Yergeau" fullname="FrançoisYergeau" />Yergeau"/> <dateyear='2008' month='November' /> <keyword>W3C.xml</keyword>year="2008" month="November"/> </front> <seriesInfo name="W3C" value="Recommendation"/> </reference> <reference anchor="W3C.REC-xmlschema-1-20041028" target="https://www.w3.org/TR/2004/REC-xmlschema-1-20041028/"> <front><title abbrev='XML Schema Part 1: Structures Second Edition REC-xmlschema-1-20041028'>XML<title>XML Schema Part 1: Structures Second Edition REC-xmlschema-1-20041028</title> <author initials="H. S." surname="Thompson" fullname="Henry S.Thompson" />Thompson"/> <author initials="D." surname="Beech" fullname="DavidBeech" />Beech"/> <author initials="M." surname="Maloney" fullname="MurrayMaloney" />Maloney"/> <author initials="N." surname="Mendelsohn" fullname="NoahMendelsohn" />Mendelsohn"/> <dateyear='2004' month='October' /> <keyword>W3C.xmlschema-1</keyword>year="2004" month="October"/> </front> <seriesInfo name="W3C" value="Recommendation"/> </reference> <reference anchor="W3C.REC-xmlschema-2-20041028" target="https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/"> <front><title abbrev='XML Schema Part 2: Datatypes Second Edition REC-xmlschema-2-20041028'>XML<title>XML Schema Part 2: Datatypes Second Edition REC-xmlschema-2-20041028</title> <author initials="P. V." surname="Biron" fullname="Paul V.Biron" />Biron"/> <author initials="A." surname="Malhotra" fullname="AshokMalhotra" />Malhotra"/> <dateyear='2004' month='October' /> <keyword>W3C.xmlschema-2</keyword>year="2004" month="October"/> </front> <seriesInfo name="W3C" value="Recommendation" /> </reference> <reference anchor="W3C.REC-xpath-31-20170321" target="https://www.w3.org/TR/2017/REC-xpath-31-20170321/"> <front><title abbrev='XML Path Language (XPath) 3.1'>XML<title>XML Path Language (XPath) 3.1</title> <authorinitials="J. R."initials="J." surname="Robie" fullname="JonathanRobie" />Robie"/> <authorinitials="M. D."initials="M." surname="Dyck" fullname="MichaelDyck" />Dyck"/> <authorinitials="J. S."initials="J." surname="Spiegel" fullname="JoshSpiegel" />Spiegel"/> <dateyear='2017' month='March' /> <keyword>W3C.xpath-31</keyword>year="2017" month="March"/> </front> <seriesInfo name="W3C" value="Recommendation"/> </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" />year="2002"/> </front> <seriesInfo name="ITU-T Recommendation" value="V.42" /> </reference> </references><references title='Informative References'> &RFC1952; &RFC2818; &RFC3688; &RFC3912; &RFC4180; &RFC7942;<references> <name>Informative References</name> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.1952.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2818.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.3912.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.4180.xml"/> <xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6672.xml"/> <reference anchor="variantTLDsReport"target="http://www.icann.org/en/topics/idn/idn-vip-integrated-issues-final-clean-20feb12-en.pdf">target="https://www.icann.org/en/system/files/files/idn-vip-integrated-issues-final-clean-20feb12-en.pdf"> <front> <title>A Study of Issues Related to the Management of IDN Variant TLDs</title> <author> <organization abbrev="ICANN">Internet Corporation for Assigned Names and Numbers (ICANN)</organization> </author> <date day="20" month="February" year="2012"/> </front> </reference> <reference anchor="ICANN-GTLD-RA-20170731" target="https://newgtlds.icann.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" />year="2017"/> </front> </reference> <reference anchor="ICANN-GTLD-AGB-20120604" target="http://newgtlds.icann.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" />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" format="default"/> and related RFCs by <contact fullname="Scott Hollenbeck"/>. </t> <t> Special suggestions that have been incorporated into this document were provided by <contact fullname="Edward Lewis"/>, <contact fullname="Jaap Akkerhuis"/>, <contact fullname="Lawrence Conroy"/>, <contact fullname="Marc Groeneweg"/>, <contact fullname="Michael Young"/>, <contact fullname="Chris Wright"/>, <contact fullname="Patrick Mevzek"/>, <contact fullname="Stephen Morris"/>, <contact fullname="Scott Hollenbeck"/>, <contact fullname="Stephane Bortzmeyer"/>, <contact fullname="Warren Kumari"/>, <contact fullname="Paul Hoffman"/>, <contact fullname="Vika Mpisane"/>, <contact fullname="Bernie Hoeneisen"/>, <contact fullname="Jim Galvin"/>, <contact fullname="Andrew Sullivan"/>, <contact fullname="Hiro Hotta"/>, <contact fullname="Christopher Browne"/>, <contact fullname="Daniel Kalchev"/>, <contact fullname="David Conrad"/>, <contact fullname="James Mitchell"/>, <contact fullname="Francisco Obispo"/>, <contact fullname="Bhadresh Modi"/>, <contact fullname="Alexander Mayrhofer"/>, and <contact fullname="Benjamin Kaduk"/>. </t> <t> <contact fullname="Shoji Noguchi"/> and <contact fullname="Francisco Arias"/> participated as coauthors through version 05 of earlier drafts of this document and provided invaluable support. </t> </section> </back> </rfc>