| Internet-Draft | DNRD .NAME Mapping | March 2023 |
| Gould | Expires 1 October 2023 | [Page] |
This document defines the data escrow structure of depositing objects specific to the .NAME Top Level Domain (TLD) as an extension to the objects deposited with DNRD Objects Mapping. The .NAME TLD-specific objects are Email Forwarding, Defensive Registration, and NameWatch.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 1 October 2023.¶
Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document may not be modified, and derivative works of it may not be created, except to format it for publication as an RFC or to translate it into languages other than English.¶
This document defines the data escrow structure of depositing .NAME Top Level Domain (TLD) specific objects as an extension to the objects deposited with [RFC9022]. The .NAME TLD specific objects include:¶
This document supports the two models (XML and CSV) defined in [RFC9022] for depositing the .NAME TLD specific objects.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].¶
XML is case sensitive. Unless stated otherwise, XML specifications and examples provided in this document MUST be interpreted in the character case presented in order to develop a conforming implementation.¶
The following XML namespace prefixes are used in this document based on the dependent specifications, but implementations MUST NOT depend on this use and instead employ a namespace-aware XML parser and serializer to interpret and output the XML documents:¶
The following XML namespace prefixes are used based on the dependent specifications, but implementations MUST NOT depend on it and instead employ a proper namespace-aware XML parser and serializer to interpret and output the XML documents:¶
Numerous fields include values that represent a calendar date/time, such as the creation and expiry dates for .NAME objects. These fields SHALL contain timestamps indicating the date and time in UTC as specified in [RFC3339], with no offset from the zero meridian.¶
Numerous fields reference the CSV common field elements, which are defined in [RFC9022]. For example, the <rdeCsv:fRoid> field is referenced for each of the .NAME objects.¶
Numerous fields reference the Contact Object, which is defined in [RFC9022]. For example, the <csvContact:fId> field is referenced to define the contact identifier for the linked Contact Object.¶
Numerous fields reference the Registrar Object, which is defined in [RFC9022]. For example, the <csvRegistrar:fGurid> field is referenced to define the registrar ID assigned by ICANN.¶
The "CSV Parent Child Relationship" convention described in [RFC9022], with support for cascade replace and cascade delete, applies to the CSV Model in this document.¶
This section describes the objects supported by this specification:¶
The email forwarding object is based on the EPP email forwarding mapping specified in https://www.verisign.com/assets/email-forwarding-mapping.pdf. The email forwarding object supports both the XML Model and the CSV Model, defined in the Models (Section 2) section. The elements used for both models are defined in the following sections.¶
There are two elements used in the data escrow of the email forwarding objects for the XML model including the <rdeEmailFwd:emailFwd>, under the <rde:contents> element, and the <rdeEmailFwd:delete> element, under the <rde:deletes> element.¶
The <emailFwd> element is based on the EPP email forwarding <info> response for an authorized client (see Section 3.1.2. of https://www.verisign.com/assets/email-forwarding-mapping.pdf) with additional data from an EPP <transfer> Query Response, see Section 3.1.3. of https://www.verisign.com/assets/email-forwarding-mapping.pdf.¶
A <emailFwd> element substitutes for the <abstractEmailFwd> abstract element to define a concrete definition of an email forwarding. The <abstractEmailFwd> element can be replaced by other email forwarding definitions using the XML schema substitution groups feature.¶
The <emailFwd> element contains the following child elements:¶
An OPTIONAL <trnData> element that contains the following child elements related to the last transfer request of the email forwarding object. This element MUST NOT be present if a transfer request for the email forwarding object has never been created.¶
Example of an email forwarding object:¶
...
<rdeEmailFwd:emailFwd>
<rdeEmailFwd:name>chris@doe.name</rdeEmailFwd:name>
<rdeEmailFwd:roid>EXAMPLE1_EMAILFWD-VRSN</rdeEmailFwd:roid>
<rdeEmailFwd:status s="ok" />
<rdeEmailFwd:registrant>jd1234</rdeEmailFwd:registrant>
<rdeEmailFwd:contact type="admin">sh8013</rdeEmailFwd:contact>
<rdeEmailFwd:contact type="tech">sh8013</rdeEmailFwd:contact>
<rdeEmailFwd:fwdTo>cdoe@example.com</rdeEmailFwd:fwdTo>
<rdeEmailFwd:clID>RegistrarX</rdeEmailFwd:clID>
<rdeEmailFwd:crRr client="cdoe">RegistrarX</rdeEmailFwd:crRr>
<rdeEmailFwd:crDate>1999-04-03T22:00:00.0Z</rdeEmailFwd:crDate>
<rdeEmailFwd:exDate>2021-04-03T22:00:00.0Z</rdeEmailFwd:exDate>
<rdeEmailFwd:trnData>
<rdeEmailFwd:trStatus>pending</rdeEmailFwd:trStatus>
<rdeEmailFwd:reRr>registrarY</rdeEmailFwd:reRr>
<rdeEmailFwd:reDate>2020-03-03T22:00:00.0Z</rdeEmailFwd:reDate>
<rdeEmailFwd:acRr>RegistrarX</rdeEmailFwd:acRr>
<rdeEmailFwd:acDate>2020-03-08T22:00:00.0Z</rdeEmailFwd:acDate>
<rdeEmailFwd:exDate>2022-04-03T22:00:00.0Z</rdeEmailFwd:exDate>
</rdeEmailFwd:trnData>
</rdeEmailFwd:emailFwd>
...¶
The <rdeEmailFwd:delete> element contains the fully qualified email forwarding object that was deleted and purged.¶
Example of <rdeEmailFwd:delete> object:¶
...
<rde:deletes>
...
<rdeEmailFwd:delete>
<rdeEmailFwd:name>chris@doe.name</rdeEmailFwd:name>
<rdeEmailFwd:name>kris@doe.name</rdeEmailFwd:name>
</rdeEmailFwd:delete>
...
</rde:deletes>
...¶
For the CSV Model of the email forwarding object, the <csvEmailFwd:contents> child element of the <rde:contents> element is used to hold the new or updated email forwarding objects for the deposit. The <csvEmailFwd:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged email forwarding objects for the deposit. Both the <csvEmailFwd:contents> and <csvEmailFwd:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute.¶
Differential and incremental deposits are based on changes to the email forwarding objects. The updated email forwarding object data under the <csvEmailFwd:contents> element is a cascade replace (Section 4.5) using all of the email forwarding CSV files starting with the parent "emailFwd" CSV File Definition (Section 5.1.2.1.1). The child CSV file definitions include a <csvEmailFwd:fName parent="true"> field. All the child CSV file definition data for the email forwarding objects in the parent "emailFwd" CSV File Definition (Section 5.1.2.1.1) MUST first be deleted and then set using the data in the child CSV files. The deleted email forwarding object data under the <csvEmailFwd:deletes> element is a cascade delete (Section 4.5) starting from the "emailFwd" Deletes CSV File Definition (Section 5.1.2.2.1).¶
The <csvEmailFwd:contents> is used to hold the new or updated email forwarding object information for the deposit. The <csvEmailFwd:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported email forwarding CSV file definitions:¶
The "emailFwd" CSV File Definition defines the fields and CSV file references used for the parent email forwarding object records. All the other email forwarding CSV file definitions are child CSV files based on the inclusion of the <csvEmailFwd:fName parent="true"> field.¶
The following "csvEmailFwd" field elements MUST be used in the "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:¶
A choice of:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "emailFwd" <csvEmailFwd:contents> <rdeCsv:csv> element.¶
...
<csvEmailFwd:contents>
...
<rdeCsv:csv name="emailFwd" sep=",">
<rdeCsv:fields>
<csvEmailFwd:fName/>
<rdeCsv:fRoid/>
<rdeCsv:fRegistrant/>
<csvEmailFwd:fFwdTo/>
<rdeCsv:fClID/>
<rdeCsv:fCrRr/>
<rdeCsv:fCrID/>
<rdeCsv:fCrDate/>
<rdeCsv:fUpRr/>
<rdeCsv:fUpID/>
<rdeCsv:fUpDate/>
<rdeCsv:fExDate/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="F72A19A8">
emailFwd-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvEmailFwd:contents>
...¶
Example of the corresponding emailFwd-YYYYMMDD.csv file. The file contains one record.¶
chris@doe.name,EXAMPLE1_EMAILFWD-VRSN,jd1234,cdoe@example.com, RegistrarX,RegistrarX,cdoe,1999-04-03T22:00:00.0Z,,,, 2021-04-03T22:00:00.0Z¶
The "emailFwdContacts" CSV File Definition defines the fields and CSV file references used for the email forwarding object link records to contact objects, as described in Contact Object (Section 4.3).¶
The following "csvEmailFwd" field elements, defined for the "emailFwd" CSV File Definition (Section 5.1.2.1.1), MUST be used in the "emailFwdContacts" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "csvContact" fields, defined for the "contact" CSV File Definition (Section 4.3), MUST be used in the "emailFwdContacts" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "emailFwdContacts" <csvEmailFwd:contents> <rdeCsv:csv> element.¶
...
<csvEmailFwd:contents>
...
<rdeCsv:csv name="emailFwdContacts" sep=",">
<rdeCsv:fields>
<csvEmailFwd:fName parent="true"/>
<csvContact:fId/>
<csvEmailFwd:fContactType/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="B3FBC311">
emailFwdContacts-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvEmailFwd:contents>
...¶
Example of the corresponding emailFwdContacts-YYYYMMDD.csv file. The file contains an admin and tech contact for the email forwarding object chris@doe.name.¶
chris@doe.name,sh8013,admin chris@doe.name,sh8013,tech¶
The "emailFwdStatuses" CSV File Definition defines the fields and CSV file references used for the email forwarding object statuses.¶
The following "csvEmailFwd" fields, defined for the "emailFwd" CSV File Definition (Section 5.1.2.1.1), MUST be used in the "emailFwdStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "emailFwdStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "emailFwdStatuses" <csvEmailFwd:contents> <rdeCsv:csv> element.¶
...
<csvEmailFwd:contents>
...
<rdeCsv:csv name="emailFwdStatuses" sep=",">
<rdeCsv:fields>
<csvEmailFwd:fName parent="true"/>
<csvEmailFwd:fStatus/>
<rdeCsv:fStatusDescription/>
<rdeCsv:fLang/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="A7A59EB0">
emailFwdStatuses-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvEmailFwd:contents>
...
¶
Example of the corresponding emailFwdStatuses-YYYYMMDD.csv file. The file contains the statuses for the email forwarding object chris@doe.name.¶
chris@doe.name,ok,¶
The "emailFwdTransfer" CSV File Definition defines the fields and CSV file references used for the email forwarding object pending and completed transfer records. No additional field elements were added for use in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element.¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MUST be used in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "csvEmailFwd" fields, defined for the "emailFwd" CSV File Definition (Section 5.1.2.1.1), MUST be used in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "emailFwdTransfer" <csvEmailFwd:contents> <rdeCsv:csv> element.¶
...
<csvEmailFwd:contents>
...
<rdeCsv:csv name="emailFwdTransfer" sep=",">
<rdeCsv:fields>
<csvEmailFwd: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="C71A9998">
emailFwdTransfer-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvEmailFwd:contents>
...¶
Example of the corresponding emailFwdTransfer-YYYYMMDD.csv file. The file contains one email forwarding transfer record with a pending status.¶
chris@doe.name,pending,registrarY,clientX,2020-03-03T22:00:00.0Z, RegistrarX,,2020-03-08T22:00:00.0Z,2022-04-03T22:00:00.0Z¶
The <csvEmailFwd:deletes> is used to hold the deleted email forwarding objects in a differential or incremental deposit. All the email forwarding object data is deleted as part of a cascade delete (Section 4.5). The <csvEmailFwd:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported email forwarding deletes CSV file definition.¶
The following "csvEmailFwd" field elements MUST be used in the deletes "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "emailFwd" <csvEmailFwd:deletes> <rdeCsv:csv> element:¶
...
<rde:deletes>
...
<csvEmailFwd:deletes>
<rdeCsv:csv name="emailFwd">
<rdeCsv:fields>
<csvEmailFwd:fName/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="6B23C283">
emailfwd-delete-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
</csvEmailFwd:deletes>
...
</rde:deletes>
...¶
Example of the corresponding emailfwd-delete-YYYYMMDD.csv file. The file contains two email forwarding records.¶
chris@doe.name kris@doe.name¶
The defensive registration object is based on the EPP defensive registration mapping specified in https://www.verisign.com/assets/defensive-registration-mapping.pdf. The defensive registration object supports both the XML Model and the CSV Model, defined in the Models (Section 2) section. The elements used for both models are defined in the following sections. There are two levels of defensive registration objects: Standard Defensive Registration and Premium Defensive Registration.¶
There are two elements used in the data escrow of the defensive registration objects for the XML model including the <rdeDefReg:defReg>, under the <rde:contents> element, and the <rdeDefReg:delete> element, under the <rde:deletes> element.¶
The <defReg> element is based on the EPP defensive registration <info> response for an authorized client (see Section 3.1.2. of https://www.verisign.com/assets/defensive-registration-mapping.pdf) with additional data from an EPP <transfer> Query Response, see Section 3.1.3. of https://www.verisign.com/assets/defensive-registration-mapping.pdf.¶
A <defReg> element substitutes for the <abstractDefReg> abstract element to define a concrete definition of a defensive registration. The <abstractDefReg> element can be replaced by other defensive registration definitions using the XML schema substitution groups feature.¶
The <defReg> element contains the following child elements:¶
An OPTIONAL <trnData> element that contains the following child elements related to the last transfer request of the defensive registration object. This element MUST NOT be present if a transfer request for the defensive registration has never been created.¶
Example of a defensive registration object:¶
... <rdeDefReg:defReg> <rdeDefReg:roid>EXAMPLE3_DEFREG-REP</rdeDefReg:roid> <rdeDefReg:name level="premium">doe</rdeDefReg:name> <rdeDefReg:registrant>jd1234</rdeDefReg:registrant> <rdeDefReg:tm>XYZ-123</rdeDefReg:tm> <rdeDefReg:tmCountry>US</rdeDefReg:tmCountry> <rdeDefReg:tmDate>1990-04-03</rdeDefReg:tmDate> <rdeDefReg:adminContact>sh8013</rdeDefReg:adminContact> <rdeDefReg:status s="ok"/> <rdeDefReg:clID>RegistrarX</rdeDefReg:clID> <rdeDefReg:crRr client="cdoe">RegistrarX</rdeDefReg:crRr> <rdeDefReg:crDate>1999-04-03T22:00:00.0Z</rdeDefReg:crDate> <rdeDefReg:exDate>2000-04-03T22:00:00.0Z</rdeDefReg:exDate> </rdeDefReg:defReg> ...¶
The <rdeDefReg:delete> element contains the defensive registration repository object identifier that was deleted and purged.¶
Example of <rdeDefReg:delete> object:¶
...
<rde:deletes>
...
<rdeDefReg:delete>
<rdeDefReg:roid>EXAMPLE1_DEFREG-REP
</rdeDefReg:roid>
<rdeDefReg:roid>EXAMPLE2_DEFREG-REP
</rdeDefReg:roid>
</rdeDefReg:delete>
...
</rde:deletes>
...¶
For the CSV Model of the defensive registration object, the <csvDefReg:contents> child element of the <rde:contents> element is used to hold the new or updated defensive registration objects for the deposit. The <csvDefReg:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged defensive registration objects for the deposit. Both the <csvDefReg:contents> and <csvDefReg:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute.¶
Differential and incremental deposits are based on changes to the defensive registration objects. The updated defensive registration object data under the <csvDefReg:contents> element is a cascade replace (Section 4.5) using all of the defensive registration CSV files starting with the parent "defReg" CSV File Definition (Section 5.2.2.1.1). The child CSV file definitions include a <rdeCsv:fRoid parent="true"> field. All the child CSV file definition data for the defensive registration objects in the parent "defReg" CSV File Definition (Section 5.2.2.1.1) MUST first be deleted and then set using the data in the child CSV files. The deleted defensive registration object data under the <csvDefReg:deletes> element is a cascade delete (Section 4.5) starting from the "defReg" Deletes CSV File Definition (Section 5.2.2.2.1).¶
The <csvDefReg:contents> is used to hold the new or updated defensive registration object information for the deposit. The <csvDefReg:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported defensive registration CSV file definitions:¶
The "defReg" CSV File Definition defines the fields and CSV file references used for the parent defensive registration object records. All the other defensive registration CSV file definitions are child CSV files based on the inclusion of the <rdeCsv:fRoid parent="true"> field.¶
The following "csvDefReg" field elements MUST be used in the "defReg" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "csvDefReg" field elements MAY be used in the "defReg" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "defReg" <rdeCsv:csv> <rdeCsv:fields> element:¶
A choice of:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "defReg" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "defReg" <csvDefReg:contents> <rdeCsv:csv> element.¶
...
<csvDefReg:contents>
...
<rdeCsv:csv name="defReg" sep=",">
<rdeCsv:fields>
<rdeCsv:fRoid/>
<csvDefReg:fName/>
<csvDefReg:fLevel/>
<rdeCsv:fRegistrant/>
<csvDefReg:fTm/>
<csvDefReg:fTmCountry/>
<csvDefReg:fTmDate/>
<csvDefReg:fAdminContact/>
<rdeCsv:fClID/>
<rdeCsv:fCrRr/>
<rdeCsv:fCrID/>
<rdeCsv:fCrDate/>
<rdeCsv:fUpRr/>
<rdeCsv:fUpID/>
<rdeCsv:fUpDate/>
<rdeCsv:fExDate/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="3019A23F">
defReg-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvDefReg:contents>
...¶
Example of the corresponding defReg-YYYYMMDD.csv file. The file contains one record.¶
EXAMPLE1_DEFREG-REP,doe,premium,jd1234,XYZ-123,US,1990-04-03, sh8013,1999-04-03T22:00:00.0Z,,,,2021-04-03T22:00:00.0Z¶
The "defRegStatuses" CSV File Definition defines the fields and CSV file references used for the defensive registration object statuses.¶
The following "csvDefReg" fields, defined for the "defReg" CSV File Definition (Section 5.2.2.1.1), MUST be used in the "defRegStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined for the CSV common field elements (Section 4.2), MUST be used in the "defRegStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "defRegStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "defRegStatuses" <csvDefReg:contents> <rdeCsv:csv> element.¶
...
<csvDefReg:contents>
...
<rdeCsv:csv name="defRegStatuses" sep=",">
<rdeCsv:fields>
<rdeCsv:fRoid parent="true"/>
<csvDefReg:fStatus/>
<rdeCsv:fStatusDescription/>
<rdeCsv:fLang/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="21D85E27">
csvDefRegStatuses-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvDefReg:contents>
...¶
Example of the corresponding defRegStatuses-YYYYMMDD.csv file. The file contains the statuses for the defensive registration object EXAMPLE1_DEFREG-REP.¶
EXAMPLE1_DEFREG-REP,ok,¶
The "defRegTransfer" CSV File Definition defines the fields and CSV file references used for the defensive registration object pending and completed transfer records. No additional field elements were added for use in the "defRegTransfer" <rdeCsv:csv> <rdeCsv:fields> element.¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MUST be used in the "defRegTransfer" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "defRegTransfer" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "defRegTransfer" <csvDefReg:contents> <rdeCsv:csv> element.¶
...
<csvDefReg:contents>
...
<rdeCsv:csv name="defRegTransfer" sep=",">
<rdeCsv:fields>
<rdeCsv:fRoid 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="6303FBAF">
defRegTransfer-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvDefReg:contents>
...¶
Example of the corresponding defRegTransfer-YYYYMMDD.csv file. The file contains one defensive registration transfer record with a pending status.¶
EXAMPLE1_DEFREG-REP,pending,registrarY,clientX, 2020-03-03T22:00:00.0Z,RegistrarX,,2020-03-08T22:00:00.0Z, 2022-04-03T22:00:00.0Z¶
The <csvDefReg:deletes> is used to hold the deleted defensive registration objects in a differential or incremental deposit. All the defensive registration object data is deleted as part of a cascade delete (Section 4.5). The <csvDefReg:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported defensive registration deletes CSV file definition.¶
The following "rdeCsv" field elements MUST be used in the deletes "defReg" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "defReg" <csvDefReg:deletes> <rdeCsv:csv> element:¶
...
<rde:deletes>
...
<csvDefReg:deletes>
<rdeCsv:csv name="defReg">
<rdeCsv:fields>
<rdeCsv:fRoid/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="B6ED701B">
defReg-delete-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
</csvDefReg:deletes>
...
</rde:deletes>
...¶
Example of the corresponding defReg-delete-YYYYMMDD.csv file. The file contains two defensive registration records.¶
EXAMPLE2_DEFREG-REP EXAMPLE3_DEFREG-REP¶
The NameWatch object is based on the EPP NameWatch mapping specified in https://www.verisign.com/assets/namewatch-mapping.pdf. The NameWatch object supports both the XML Model and the CSV Model, defined in the Models (Section 2) section. The elements used for both models are defined in the following sections.¶
There are two elements used in the data escrow of the NameWatch objects for the XML model including the <rdeNameWatch:nameWatch>, under the <rde:contents> element, and the <rdeNameWatch:delete> element, under the <rde:deletes> element.¶
The <nameWatch> element is based on the EPP NameWatch <info> response for an authorized client (see Section 3.1.2. of https://www.verisign.com/assets/namewatch-mapping.pdf) with additional data from an EPP <transfer> Query Response, see Section 3.1.3. of https://www.verisign.com/assets/namewatch-mapping.pdf.¶
A <nameWatch> element substitutes for the <abstractNameWatch> abstract element to define a concrete definition of a NameWatch. The <abstractNameWatch> element can be replaced by other NameWatch definitions using the XML schema substitution groups feature.¶
The <nameWatch> element contains the following child elements:¶
An OPTIONAL <trnData> element that contains the following child elements related to the last transfer request of the NameWatch object. This element MUST NOT be present if a transfer request for the NameWatch has never been created.¶
Example of a NameWatch object:¶
... <rdeNameWatch:nameWatch> <rdeNameWatch:roid>EXAMPLE3_NAMEWATCH-VRSN</rdeNameWatch:roid> <rdeNameWatch:name>doe</rdeNameWatch:name> <rdeNameWatch:registrant>jd1234</rdeNameWatch:registrant> <rdeNameWatch:rptTo freq="weekly">cdoe@example.com </rdeNameWatch:rptTo> <rdeNameWatch:status s="ok"/> <rdeNameWatch:clID>RegistrarX</rdeNameWatch:clID> <rdeNameWatch:crRr client="cdoe">RegistrarX</rdeNameWatch:crRr> <rdeNameWatch:crDate>1999-04-03T22:00:00.0Z</rdeNameWatch:crDate> <rdeNameWatch:exDate>2021-04-03T22:00:00.0Z</rdeNameWatch:exDate> </rdeNameWatch:nameWatch> ...¶
The <rdeNameWatch:delete> element contains the NameWatch repository object identifier that was deleted and purged.¶
Example of <rdeNameWatch:delete> object:¶
...
<rde:deletes>
...
<rdeNameWatch:delete>
<rdeNameWatch:roid>EXAMPLE1_NAMEWATCH-REP
</rdeNameWatch:roid>
<rdeNameWatch:roid>EXAMPLE2_NAMEWATCH-REP
</rdeNameWatch:roid>
</rdeNameWatch:delete>
...
</rde:deletes>
...¶
For the CSV Model of the NameWatch object, the <csvNameWatch:contents> child element of the <rde:contents> element is used to hold the new or updated NameWatch objects for the deposit. The <csvNameWatch:deletes> child element of the <rde:deletes> element is used to hold the deleted or purged NameWatch objects for the deposit. Both the <csvNameWatch:contents> and <csvNameWatch:deletes> elements contain one or more <rdeCsv:csv> elements with a set of named CSV file definitions using the <rdeCsv:csv> "name" attribute.¶
Differential and incremental deposits are based on changes to the NameWatch objects. The updated NameWatch object data under the <csvNameWatch:contents> element is a cascade replace (Section 4.5) using all of the NameWatch CSV files starting with the parent "nameWatch" CSV File Definition (Section 5.3.2.1.1). The child CSV file definitions include a <rdeCsv:fRoid parent="true"> field. All the child CSV file definition data for the NameWatch objects in the parent "nameWatch" CSV File Definition (Section 5.3.2.1.1) MUST first be deleted and then set using the data in the child CSV files. The deleted NameWatch object data under the <csvNameWatch:deletes> element is a cascade delete (Section 4.5) starting from the "nameWatch" Deletes CSV File Definition (Section 5.3.2.2.1).¶
The <csvNameWatch:contents> is used to hold the new or updated NameWatch object information for the deposit. The <csvNameWatch:contents> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following sections include the supported NameWatch CSV file definitions:¶
The "nameWatch" CSV File Definition defines the fields and CSV file references used for the parent NameWatch object records. All the other NameWatch CSV file definitions are child CSV files based on the inclusion of the <rdeCsv:fRoid parent="true"> field.¶
The following "csvNameWatch" field elements MUST be used in the "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "csvNameWatch" field elements MAY be used in the "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:¶
A choice of:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "nameWatch" <csvNameWatch:contents> <rdeCsv:csv> element.¶
...
<csvNameWatch:contents>
...
<rdeCsv:csv name="nameWatch" sep=",">
<rdeCsv:fields>
<rdeCsv:fRoid/>
<csvNameWatch:fName/>
<rdeCsv:fRegistrant/>
<csvNameWatch:fRptTo/>
<csvNameWatch:fRptToFreq/>
<rdeCsv:fClID/>
<rdeCsv:fCrRr/>
<rdeCsv:fCrID/>
<rdeCsv:fCrDate/>
<rdeCsv:fUpRr/>
<rdeCsv:fUpID/>
<rdeCsv:fUpDate/>
<rdeCsv:fExDate/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="75E2D01F">
nameWatch-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvNameWatch:contents>
...¶
Example of the corresponding nameWatch-YYYYMMDD.csv file. The file contains one record.¶
EXAMPLE1_NAMEWATCH-REP,doe,jd1234,cdoe@example.com, weekly,sh8013,1999-04-03T22:00:00.0Z,,,,2021-04-03T22:00:00.0Z¶
The "nameWatchStatuses" CSV File Definition defines the fields and CSV file references used for the NameWatch object statuses.¶
The following "csvNameWatch" fields, defined for the "nameWatch" CSV File Definition (Section 5.3.2.1.1), MUST be used in the "nameWatchStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined for the CSV common field elements (Section 4.2), MUST be used in the "nameWatchStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "nameWatchStatuses" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "nameWatchStatuses" <csvNameWatch:contents> <rdeCsv:csv> element.¶
...
<csvNameWatch:contents>
...
<rdeCsv:csv name="nameWatchStatuses" sep=",">
<rdeCsv:fields>
<rdeCsv:fRoid parent="true"/>
<csvNameWatch:fStatus/>
<rdeCsv:fStatusDescription/>
<rdeCsv:fLang/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="A2C261DC">
csvNameWatchStatuses-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvNameWatch:contents>
...¶
Example of the corresponding nameWatchStatuses-YYYYMMDD.csv file. The file contains the statuses for the NameWatch object EXAMPLE1_NAMEWATCH-REP.¶
EXAMPLE1_NAMEWATCH-REP,ok,¶
The "nameWatchTransfer" CSV File Definition defines the fields and CSV file references used for the NameWatch object pending and completed transfer records. No additional field elements were added for use in the "nameWatchTransfer" <rdeCsv:csv> <rdeCsv:fields> element.¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MUST be used in the "nameWatchTransfer" <rdeCsv:csv> <rdeCsv:fields> element:¶
The following "rdeCsv" fields, defined in section CSV common field elements (Section 4.2), MAY be used in the "nameWatchTransfer" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "nameWatchTransfer" <csvNameWatch:contents> <rdeCsv:csv> element.¶
...
<csvNameWatch:contents>
...
<rdeCsv:csv name="nameWatchTransfer" sep=",">
<rdeCsv:fields>
<rdeCsv:fRoid 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="FE25CA7B">
nameWatchTransfer-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
...
</csvNameWatch:contents>
...¶
Example of the corresponding nameWatchTransfer-YYYYMMDD.csv file. The file contains one NameWatch transfer record with a pending status.¶
EXAMPLE1_NAMEWATCH-REP,pending,registrarY,clientX, 2020-03-03T22:00:00.0Z,RegistrarX,, 2020-03-08T22:00:00.0Z,2022-04-03T22:00:00.0Z¶
The <csvNameWatch:deletes> is used to hold the deleted NameWatch objects in a differential or incremental deposit. All the NameWatch object data is deleted as part of a cascade delete (Section 4.5). The <csvNameWatch:deletes> is split into separate CSV file definitions using named <rdeCsv:csv> elements with the "name" attribute. The following section defines the supported NameWatch deletes CSV file definition.¶
The following "rdeCsv" field elements MUST be used in the deletes "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:¶
Example of a "nameWatch" <csvNameWatch:deletes> <rdeCsv:csv> element:¶
...
<rde:deletes>
...
<csvNameWatch:deletes>
<rdeCsv:csv name="nameWatch">
<rdeCsv:fields>
<rdeCsv:fRoid/>
</rdeCsv:fields>
<rdeCsv:files>
<rdeCsv:file
cksum="6D4BB372">
nameWatch-delete-YYYYMMDD.csv
</rdeCsv:file>
</rdeCsv:files>
</rdeCsv:csv>
</csvNameWatch:deletes>
...
</rde:deletes>
...¶
Example of the corresponding nameWatch-delete-YYYYMMDD.csv file. The file contains two NameWatch records.¶
EXAMPLE2_NAMEWATCH-REP EXAMPLE3_NAMEWATCH-REP¶
The formal syntax is specified in XML Schema notation that is a complete schema representation suitable for automated valudation. The <CODE BEGINS> and the <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.¶
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="http://www.nic.name/rde/rdeEmailFwd-1.0"
xmlns:rdeEmailFwd=
"http://www.nic.name/rde/rdeEmailFwd-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:emailFwd="http://www.nic.name/epp/emailFwd-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="http://www.nic.name/epp/emailFwd-1.0"/>
<annotation>
<documentation>
Registry Data Escrow Email Forwarding Data.
</documentation>
</annotation>
<element name="abstractEmailFwd"
type="rdeEmailFwd:abstractContentType"
substitutionGroup="rde:content" abstract="true"/>
<element name="emailFwd"
substitutionGroup="rdeEmailFwd:abstractEmailFwd"/>
<element name="delete"
type="rdeEmailFwd:deleteType"
substitutionGroup="rde:delete"/>
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent>
<extension base="rde:contentType">
<sequence>
<element name="name" type="emailFwd:emailAddrType"/>
<element name="roid" type="eppcom:roidType"/>
<element name="status" type="emailFwd:statusType"
minOccurs="0" maxOccurs="11"/>
<element name="registrant" type="emailFwd:contactType"
minOccurs="0"/>
<element name="contact" type="emailFwd:contactType"
minOccurs="0" maxOccurs="unbounded"/>
<element name="fwdTo" type="emailFwd:emailAddrType"
minOccurs="0"/>
<element name="clID" type="eppcom:clIDType"/>
<element name="crRr"
type="rde:rrType"/>
<element name="crDate" type="dateTime"
minOccurs="0"/>
<element name="upRr"
type="rde:rrType" minOccurs="0"/>
<element name="upDate" type="dateTime"
minOccurs="0"/>
<element name="exDate" type="dateTime"
minOccurs="0"/>
<element name="trDate" type="dateTime"
minOccurs="0"/>
<element name="trnData"
type="rdeEmailFwd:transferDataType"
minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="transferDataType">
<sequence>
<element name="trStatus"
type="eppcom:trStatusType"/>
<element name="reRr"
type="rde:rrType"/>
<element name="reDate"
type="dateTime"/>
<element name="acRr"
type="rde: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="emailFwd:emailAddrType" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
</schema>
<CODE ENDS>¶
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://www.nic.name/rde/csvEmailFwd-1.0"
xmlns:csvEmailFwd="http://www.nic.name/rde/csvEmailFwd-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:emailFwd="http://www.nic.name/epp/emailFwd-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="http://www.nic.name/epp/emailFwd-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<annotation>
<documentation>
Email Forwarding Comma-Separated Values (CSV) Object
</documentation>
</annotation>
<!--
Child elements of the <rde:contents> object
-->
<element name="contents" type="csvEmailFwd: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="csvEmailFwd:deleteType"
substitutionGroup="rde:delete"/>
<complexType name="deleteType">
<complexContent>
<extension base="rde:deleteType">
<sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<!-- EmailFwd name and fwdTo field -->
<element name="fName" type="csvEmailFwd:fEmailAddrType"
substitutionGroup="rdeCsv:field"/>
<element name="fFwdTo" type="csvEmailFwd:fEmailAddrType"
substitutionGroup="rdeCsv:field"/>
<!-- EmailFwd Address type -->
<complexType name="fEmailAddrType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="emailFwd\:emailAddrType"/>
</extension>
</complexContent>
</complexType>
<!-- Contact type field -->
<element name="fContactType" type="csvEmailFwd:fContactsTypeType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fContactsTypeType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="emailFwd\:contactAttrType"/>
</extension>
</complexContent>
</complexType>
<!-- EmailFwd status field -->
<element name="fStatus" type="csvEmailFwd:fStatusType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="emailFwd\:statusValueType"/>
</extension>
</complexContent>
</complexType>
<!--
End of schema.
-->
</schema>
<CODE ENDS>¶
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="http://www.nic.name/rde/rdeDefReg-1.0"
xmlns:rdeDefReg=
"http://www.nic.name/rde/rdeDefReg-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:defReg="http://www.nic.name/epp/defReg-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="http://www.nic.name/epp/defReg-1.0"/>
<annotation>
<documentation>
Registry Data Escrow Defensive Registration Data.
</documentation>
</annotation>
<element name="abstractDefReg"
type="rdeDefReg:abstractContentType"
substitutionGroup="rde:content" abstract="true"/>
<element name="defReg"
substitutionGroup="rdeDefReg:abstractDefReg"/>
<element name="delete"
type="rdeDefReg:deleteType"
substitutionGroup="rde:delete"/>
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent>
<extension base="rde:contentType">
<sequence>
<element name="roid" type="eppcom:roidType"/>
<element name="name" type="defReg:nameType"/>
<element name="registrant" type="eppcom:clIDType"
minOccurs="0"/>
<element name="tm" type="defReg:tmType"
minOccurs="0"/>
<element name="tmCountry" type="defReg:ccType"
minOccurs="0"/>
<element name="tmDate" type="date"
minOccurs="0"/>
<element name="adminContact" type="eppcom:clIDType"
minOccurs="0"/>
<element name="status" type="defReg:statusType"
minOccurs="0" maxOccurs="11"/>
<element name="clID" type="eppcom:clIDType"/>
<element name="crRr"
type="rde:rrType"/>
<element name="crDate" type="dateTime"
minOccurs="0"/>
<element name="upRr"
type="rde:rrType" minOccurs="0"/>
<element name="upDate" type="dateTime"
minOccurs="0"/>
<element name="exDate" type="dateTime"
minOccurs="0"/>
<element name="trDate" type="dateTime"
minOccurs="0"/>
<element name="trnData"
type="rdeDefReg:transferDataType"
minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="transferDataType">
<sequence>
<element name="trStatus"
type="eppcom:trStatusType"/>
<element name="reRr"
type="rde:rrType"/>
<element name="reDate"
type="dateTime"/>
<element name="acRr"
type="rde: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="roid"
type="eppcom:roidType" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
</schema>
<CODE ENDS>¶
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://www.nic.name/rde/csvDefReg-1.0"
xmlns:csvDefReg="http://www.nic.name/rde/csvDefReg-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:defReg="http://www.nic.name/epp/defReg-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="http://www.nic.name/epp/defReg-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<annotation>
<documentation>
Defensive Registration Comma-Separated Values (CSV) Object
</documentation>
</annotation>
<!--
Child elements of the <rde:contents> object
-->
<element name="contents" type="csvDefReg: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="csvDefReg:deleteType"
substitutionGroup="rde:delete"/>
<complexType name="deleteType">
<complexContent>
<extension base="rde:deleteType">
<sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<!-- DefReg name field -->
<element name="fName" type="csvDefReg:fNameType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fNameType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="defReg\:nameType"/>
</extension>
</complexContent>
</complexType>
<!-- DefReg level field -->
<element name="fLevel" type="csvDefReg:fLevelType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fLevelType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="defReg\:levelType"/>
</extension>
</complexContent>
</complexType>
<!-- DefReg status field -->
<element name="fStatus" type="csvDefReg:fStatusType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="defReg\:statusValueType"/>
</extension>
</complexContent>
</complexType>
<!-- DefReg tm field -->
<element name="fTm" type="csvDefReg:fTmType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fTmType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="defReg\:tmType"/>
</extension>
</complexContent>
</complexType>
<!-- DefReg tmCountry field -->
<element name="fTmCountry" type="csvDefReg:fTmCountryType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fTmCountryType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="defReg\:ccType"/>
</extension>
</complexContent>
</complexType>
<!-- DefReg tmDate field -->
<element name="fTmDate" type="csvDefReg:fTmDateType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fTmDateType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="date"/>
</extension>
</complexContent>
</complexType>
<!-- DefReg Admin Contact field -->
<element name="fAdminContact" type="csvDefReg:fAdminContactType"
substitutionGroup="rdeCsv:field" />
<complexType name="fAdminContactType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence />
<attribute name="type" type="token"
default="eppcom\:clIDType" />
</extension>
</complexContent>
</complexType>
<!--
End of schema.
-->
</schema>
<CODE ENDS>¶
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema
targetNamespace="http://www.nic.name/rde/rdeNameWatch-1.0"
xmlns:rdeNameWatch=
"http://www.nic.name/rde/rdeNameWatch-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:eppcom="urn:ietf:params:xml:ns:eppcom-1.0"
xmlns:nameWatch="http://www.nic.name/epp/nameWatch-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="http://www.nic.name/epp/nameWatch-1.0"/>
<annotation>
<documentation>
Registry Data Escrow NameWatch Data.
</documentation>
</annotation>
<element name="abstractnameWatch"
type="rdeNameWatch:abstractContentType"
substitutionGroup="rde:content" abstract="true"/>
<element name="nameWatch"
substitutionGroup="rdeNameWatch:abstractnameWatch"/>
<element name="delete"
type="rdeNameWatch:deleteType"
substitutionGroup="rde:delete"/>
<!-- Content Type -->
<complexType name="abstractContentType">
<complexContent>
<extension base="rde:contentType">
<sequence>
<element name="roid" type="eppcom:roidType"/>
<element name="name" type="nameWatch:nameType"/>
<element name="registrant" type="eppcom:clIDType"
minOccurs="0"/>
<element name="rptTo" type="nameWatch:rptToType"
minOccurs="0"/>
<element name="status" type="nameWatch:statusType"
minOccurs="0" maxOccurs="11"/>
<element name="clID" type="eppcom:clIDType"/>
<element name="crRr"
type="rde:rrType"/>
<element name="crDate" type="dateTime"
minOccurs="0"/>
<element name="upRr"
type="rde:rrType" minOccurs="0"/>
<element name="upDate" type="dateTime"
minOccurs="0"/>
<element name="exDate" type="dateTime"
minOccurs="0"/>
<element name="trDate" type="dateTime"
minOccurs="0"/>
<element name="trnData"
type="rdeNameWatch:transferDataType"
minOccurs="0"/>
</sequence>
</extension>
</complexContent>
</complexType>
<complexType name="transferDataType">
<sequence>
<element name="trStatus"
type="eppcom:trStatusType"/>
<element name="reRr"
type="rde:rrType"/>
<element name="reDate"
type="dateTime"/>
<element name="acRr"
type="rde: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="roid"
type="eppcom:roidType" minOccurs="0"
maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
</schema>
<CODE ENDS>¶
<CODE BEGINS>
<?xml version="1.0" encoding="UTF-8"?>
<schema targetNamespace="http://www.nic.name/rde/csvNameWatch-1.0"
xmlns:csvNameWatch="http://www.nic.name/rde/csvNameWatch-1.0"
xmlns:rde="urn:ietf:params:xml:ns:rde-1.0"
xmlns:rdeCsv="urn:ietf:params:xml:ns:rdeCsv-1.0"
xmlns:nameWatch="http://www.nic.name/epp/nameWatch-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"
s/>
<import namespace="http://www.nic.name/epp/nameWatch-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rde-1.0"/>
<import namespace="urn:ietf:params:xml:ns:rdeCsv-1.0"/>
<annotation>
<documentation>
NameWatch Comma-Separated Values (CSV) Object
</documentation>
</annotation>
<!--
Child elements of the <rde:contents> object
-->
<element name="contents" type="csvNameWatch: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="csvNameWatch:deleteType"
substitutionGroup="rde:delete"/>
<complexType name="deleteType">
<complexContent>
<extension base="rde:deleteType">
<sequence>
<element ref="rdeCsv:csv" maxOccurs="unbounded"/>
</sequence>
</extension>
</complexContent>
</complexType>
<!-- NameWatch name field -->
<element name="fName" type="csvNameWatch:fNameType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fNameType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="nameWatch\:nameType"/>
</extension>
</complexContent>
</complexType>
<!-- NameWatch rptTo field -->
<element name="fRptTo" type="csvNameWatch:fRptToType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fRptToType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="nameWatch\:emailAddrType"/>
</extension>
</complexContent>
</complexType>
<!-- NameWatch rptToFreq field -->
<element name="fRptToFreq" type="csvNameWatch:fRptToFreqType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fRptToFreqType">
<complexContent>
<extension base="rdeCsv:fieldRequiredType">
<sequence/>
<attribute name="type" type="token"
default="nameWatch\:freqType"/>
</extension>
</complexContent>
</complexType>
<!-- NameWatch status field -->
<element name="fStatus" type="csvNameWatch:fStatusType"
substitutionGroup="rdeCsv:field"/>
<complexType name="fStatusType">
<complexContent>
<extension base="rdeCsv:fieldOptionalType">
<sequence/>
<attribute name="type" type="token"
default="nameWatch\:statusValueType"/>
</extension>
</complexContent>
</complexType>
<!--
End of schema.
-->
</schema>
<CODE ENDS>¶
No actions¶
The extensions described in this document do not provide any security services beyond those described by [RFC8909] and [RFC9022]. The security considerations described in these specifications apply to this specification.¶
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 regulate the particularities regarding the protection of personal data.¶
The authors wish to thank the following persons for their feedback and suggestions: Scott Hollenbeck and Rick Wilhelm.¶
Ping update¶