Domain Name Registration Data (DNRD) .NAME Object Mapping

Object Description This section describes the objects supported by this specification:

Email Forwarding Object The email forwarding object is based on the EPP email forwarding mapping specified in . The email forwarding object supports both the XML Model and the CSV Model, defined in the Models section. The elements used for both models are defined in the following sections.

XML Model 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.

<rdeEmailFwd:emailFwd> object The <emailFwd> element is based on the EPP email forwarding <info> response for an authorized client (see Section 3.1.2. of ) with additional data from an EPP <transfer> Query Response, see Section 3.1.3. of . 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:

A <name> element that contains the fully qualified name of the email forwarding object.
A <roid> element that contains the repository object identifier assigned to the email forwarding object when it was created.
One or more <status> elements that contain the current status descriptors associated with the email forwarding object.
An OPTIONAL <registrant> element that contain the identifier for the individual or organizational social information object associated as the holder of the email forwarding object.
Zero or more OPTIONAL <contact> elements that contain identifiers for the individual or organizational social information objects associated with the email forwarding object.
An <fwdTo> element that contains the forward to email address associated with the email forwarding object.
A <clID> element that contains the identifier of the sponsoring registrar.
An OPTIONAL <crRr> element that contains the identifier of the registrar that created the email forwarding object. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
An OPTIONAL <crDate> element that contains the date and time of the email forwarding object creation.
An OPTIONAL <exDate> element that contains the date and time identifying the end (expiration) of the email forwarding object's registration period.
An OPTIONAL <upRr> element that contains the identifier of the registrar that last updated the email forwarding object. This element MUST NOT be present if the email forwarding object has never been modified. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
An OPTIONAL <upDate> element that contains the date and time of the most recent email forwarding object modification. This element MUST NOT be present if the email forwarding object has never been modified.
An OPTIONAL <trDate> element that contains the date and time of the most recent successful transfer of the email forwarding object. This element MUST NOT be present if the email forwarding object has never been transferred.
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.
- A <trStatus> element that contains the state of the most recent transfer request.
- A <reRr> element that contains the identifier of the registrar that requested the email forwarding object transfer. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
- A <reDate> element that contains the date and time that the transfer was requested.
- An <acRr> element that contains the identifier of the registrar that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the registrar that took the indicated action. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
- An <acDate> element that contains the date and time of a required or completed response. For a PENDING 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.
- An OPTIONAL <exDate> element that contains the end of the email forwarding object's validity period (expiry date) if the transfer caused or causes a change in the validity period.

Example of an email forwarding object: chris@doe.name EXAMPLE1_EMAILFWD-VRSN jd1234 sh8013 sh8013 cdoe@example.com RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2021-04-03T22:00:00.0Z pending registrarY 2020-03-03T22:00:00.0Z RegistrarX 2020-03-08T22:00:00.0Z 2022-04-03T22:00:00.0Z ...]]>

<rdeEmailFwd:delete> object The <rdeEmailFwd:delete> element contains the fully qualified email forwarding object that was deleted and purged. Example of <rdeEmailFwd:delete> object: ... chris@doe.name kris@doe.name ... ...]]>

CSV Model 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 using all of the email forwarding CSV files starting with the parent "emailFwd" CSV File Definition. 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 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 starting from the "emailFwd" Deletes CSV File Definition.

<csvEmailFwd:contents> 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:

"emailFwd" CSV File Definition 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:

<csvEmailFwd:fName>: Email forwarding name field that contains the fully qualified name of the email forwarding object with type="emailFwd:emailAddrType" and isRequired="true".
<csvEmailFwd:fFwdTo>: Email forwarding forward to field that contains the forward to email address associated with the email forwarding object with type="emailFwd:emailAddrType" and isRequired="true".

The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>

Registry Object IDentifier (ROID) for the email forwarding object with isRequired="true".

<rdeCsv:fClID> or <csvRegistrar:fGurid>

A choice of:

<rdeCsv:fClID>: Identifier of the sponsoring client with isRequired="true".
<csvRegistrar:fGurid>: Contains the ID assigned by ICANN with type="positiveInteger". The attribute "isRequired" MUST equal "true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fCrRr>: Identifier of the registrar, defined in , of the client that created the email forwarding object.
<rdeCsv:fCrID>: Identifier of the client that created the email forwarding object.
<rdeCsv:fUpRr>: Identifier of the registrar, defined in , of the client that updated the email forwarding object.
<rdeCsv:fUpID>: Identifier of the client that last updated the email forwarding object.
<rdeCsv:fRegistrant>: Registrant contact identifier for the email forwarding object.
<rdeCsv:fCrDate>: Created date and time of the email forwarding object.
<rdeCsv:fUpDate>: Date and time of the last update to the email forwarding object.
<rdeCsv:fExDate>: Expiration date and time for the email forwarding object.
<rdeCsv:fTrDate>: Date and time of the last successful transfer for the email forwarding object.

Example of a "emailFwd" <csvEmailFwd:contents> <rdeCsv:csv> element. ... emailFwd-YYYYMMDD.csv ... ...]]> Example of the corresponding emailFwd-YYYYMMDD.csv file. The file contains one record.

"emailFwdContacts" CSV File Definition 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. The following "csvEmailFwd" field elements, defined for the "emailFwd" CSV File Definition, MUST be used in the "emailFwdContacts" <rdeCsv:csv> <rdeCsv:fields> element:

<csvEmailFwd:fName>: The name of the email forwarding object that is linked to the contact object with isRequired="true".
<csvEmailFwd:fContactType>: The contact type for the contact object link with type="emailFwd: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.

The following "csvContact" fields, defined for the "contact" CSV File Definition, MUST be used in the "emailFwdContacts" <rdeCsv:csv> <rdeCsv:fields> element:

<csvContact:fId>: The server-unique contact identifier with isRequired="true".

Example of a "emailFwdContacts" <csvEmailFwd:contents> <rdeCsv:csv> element. ... emailFwdContacts-YYYYMMDD.csv ... ...]]> Example of the corresponding emailFwdContacts-YYYYMMDD.csv file. The file contains an admin and tech contact for the email forwarding object chris@doe.name.

"emailFwdStatuses" CSV File Definition 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, MUST be used in the "emailFwdStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<csvEmailFwd:fName>: Email forwarding name field that contains the fully qualified name of the email forwarding object with type="emailFwd:emailAddrType" and isRequired="true".
<csvEmailFwd:fStatus>: The status of the email forwarding with type="emailFwd:statusValueType" and isRequired="true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "emailFwdStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fStatusDescription>: Email forwarding object status description which is free-form text describing the rationale for the status.
<rdeCsv:fLang>: Language of the <rdeCsv:fStatusDescription> field.

Example of a "emailFwdStatuses" <csvEmailFwd:contents> <rdeCsv:csv> element. ... emailFwdStatuses-YYYYMMDD.csv ... ... ]]> Example of the corresponding emailFwdStatuses-YYYYMMDD.csv file. The file contains the statuses for the email forwarding object chris@doe.name.

"emailFwdTransfer" CSV File Definition 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, MUST be used in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fTrStatus>: State of the most recent transfer request with isRequired="true".
<rdeCsv:fReRr>: Identifier of the registrar, defined in , of the client that requested the transfer with isRequired="true".
<rdeCsv:fReDate>: Date and time that the transfer was requested with isRequired="true".
<rdeCsv:fAcRr>: Identifier of the registrar, defined in , of the client that should take or took action with isRequired="true".
<rdeCsv:fAcDate>: Date and time that the transfer action should be taken or has been taken with isRequired="true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fExDate>: Expiration date if the transfer command caused or causes a change in the validity period.
<rdeCsv:fReID>: Identifier of the client that requested the transfer.
<rdeCsv:fAcID>: Identifier of the client that should take or took action for transfer.

The following "csvEmailFwd" fields, defined for the "emailFwd" CSV File Definition, MUST be used in the "emailFwdTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

<csvEmailFwd:fName>: The name of the email forwarding object with isRequired="true".

Example of a "emailFwdTransfer" <csvEmailFwd:contents> <rdeCsv:csv> element. ... emailFwdTransfer-YYYYMMDD.csv ... ...]]> Example of the corresponding emailFwdTransfer-YYYYMMDD.csv file. The file contains one email forwarding transfer record with a pending status.

<csvEmailFwd:deletes> 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. 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.

"emailFwd" Deletes CSV File Definition The following "csvEmailFwd" field elements MUST be used in the deletes "emailFwd" <rdeCsv:csv> <rdeCsv:fields> element:

<csvEmailFwd:fName>: The name of the email forwarding object with isRequired="true".

Example of a "emailFwd" <csvEmailFwd:deletes> <rdeCsv:csv> element: ... emailfwd-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding emailfwd-delete-YYYYMMDD.csv file. The file contains two email forwarding records.

Defensive Registration Object The defensive registration object is based on the EPP defensive registration mapping specified in . The defensive registration object supports both the XML Model and the CSV Model, defined in the Models 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.

XML Model 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.

<rdeDefReg:defReg> object The <defReg> element is based on the EPP defensive registration <info> response for an authorized client (see Section 3.1.2. of ) with additional data from an EPP <transfer> Query Response, see Section 3.1.3. of . 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:

A <roid> element that contains the repository object identifier assigned to the defensive registration object when it was created.
A <name> element that contains the name of the defensive registration object with the "level" attribute of "standard" for a Standard Defensive Registration or "premium" for a Premium Defensive Registration.
An OPTIONAL <registrant> element that contain the identifier for the individual or organizational social information object associated as the holder of the defensive registration object.
An OPTIONAL <tm> element that contain the Trademark Identifier (ID) associated with the defensive registration.
An OPTIONAL <tmCountry> element that contain the Country which issued the Trademark associated with the defensive registration.
An OPTIONAL <tmDate> element that contain the date when the Trademark was issued.
An OPTIONAL <adminContact> element that contain the identifier for the administrator associated with the defensive registration object.
One or more <status> elements that contain the current status descriptors associated with the defensive registration object.
A <clID> element that contains the identifier of the sponsoring registrar.
An OPTIONAL <crRr> element that contains the identifier of the registrar that created the defensive registration object. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
An OPTIONAL <crDate> element that contains the date and time of the defensive registration object creation.
An OPTIONAL <exDate> element that contains the date and time identifying the end (expiration) of the defensive registration object's registration period.
An OPTIONAL <upRr> element that contains the identifier of the registrar that last updated the defensive registration object. This element MUST NOT be present if the defensive registration has never been modified. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
An OPTIONAL <upDate> element that contains the date and time of the most recent defensive registration object modification. This element MUST NOT be present if the defensive registration object has never been modified.
An OPTIONAL <trDate> element that contains the date and time of the most recent successful transfer of the defensive registration object. This element MUST NOT be present if the defensive registration object has never been transferred.
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.
- A <trStatus> element that contains the state of the most recent transfer request.
- A <reRr> element that contains the identifier of the registrar that requested the defensive registration object transfer. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
- A <reDate> element that contains the date and time that the transfer was requested.
- An <acRr> element that contains the identifier of the registrar that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the registrar that took the indicated action. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
- An <acDate> element that contains the date and time of a required or completed response. For a PENDING 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.
- An OPTIONAL <exDate> element that contains the end of the defensive registration object's validity period (expiry date) if the transfer caused or causes a change in the validity period.

Example of a defensive registration object: EXAMPLE3_DEFREG-REP doe jd1234 XYZ-123 US 1990-04-03 sh8013 RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2000-04-03T22:00:00.0Z ...]]>

<rdeDefReg:delete> object The <rdeDefReg:delete> element contains the defensive registration repository object identifier that was deleted and purged. Example of <rdeDefReg:delete> object: ... EXAMPLE1_DEFREG-REP EXAMPLE2_DEFREG-REP ... ...]]>

CSV Model 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 using all of the defensive registration CSV files starting with the parent "defReg" CSV File Definition. 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 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 starting from the "defReg" Deletes CSV File Definition.

<csvDefReg:contents> 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:

"defReg" CSV File Definition 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:

<csvDefReg:fName>: Defensive registration name field for the defensive registration object with type="defReg:nameType" and isRequired="true".
<csvDefReg:fLevel>: Defensive registration level to identify it as a Standard Defensive Registration ("standard") or a Premium Defensive Registration ("premium") with type="defReg:levelType" and isRequired="true".

The following "csvDefReg" field elements MAY be used in the "defReg" <rdeCsv:csv> <rdeCsv:fields> element:

<csvDefReg:fTm>: Trademark Identifier (ID) associated with the defensive registration with type="defReg:tmType".
<csvDefReg:fTmCountry>: Country which issued the Trademark associated with the defensive registration with type="defReg:ccType".
<csvDefReg:fTmDate>: Date when the Trademark associated with the defensive registration was issued with type="date".
<csvDefReg:fAdminContact>: Administrator contact identifier for the defensive registration object with type="eppcom:clIDType".

The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "defReg" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>

Registry Object IDentifier (ROID) for the defensive registration object with isRequired="true".

<rdeCsv:fClID> or <csvRegistrar:fGurid>

A choice of:

<rdeCsv:fClID>: Identifier of the sponsoring client with isRequired="true".
<csvRegistrar:fGurid>: Contains the ID assigned by ICANN with type="positiveInteger". The attribute "isRequired" MUST equal "true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "defReg" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fCrRr>: Identifier of the registrar, defined in , of the client that created the object.
<rdeCsv:fCrID>: Identifier of the client that created the defensive registration object.
<rdeCsv:fUpRr>: Identifier of the registrar, defined in , of the client that updated the object.
<rdeCsv:fUpID>: Identifier of the client that last updated the defensive registration object.
<rdeCsv:fRegistrant>: Registrant contact identifier for the defensive registration object.
<rdeCsv:fCrDate>: Created date and time of the defensive registration object.
<rdeCsv:fUpDate>: Date and time of the last update to the defensive registration object.
<rdeCsv:fExDate>: Expiration date and time for the defensive registration object.
<rdeCsv:fTrDate>: Date and time of the last successful transfer for the defensive registration object.

Example of a "defReg" <csvDefReg:contents> <rdeCsv:csv> element. ... defReg-YYYYMMDD.csv ... ...]]> Example of the corresponding defReg-YYYYMMDD.csv file. The file contains one record.

"defRegStatuses" CSV File Definition 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, MUST be used in the "defRegStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<csvDefReg:fStatus>: The status of the defensive registration with type="defReg:statusValueType" and isRequired="true".

The following "rdeCsv" fields, defined for the CSV common field elements, MUST be used in the "defRegStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>: Registry Object IDentifier (ROID) for the defensive registration object with isRequired="true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "defRegStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fStatusDescription>: Defensive registration object status description which is free-form text describing the rationale for the status.
<rdeCsv:fLang>: Language of the <rdeCsv:fStatusDescription> field.

Example of a "defRegStatuses" <csvDefReg:contents> <rdeCsv:csv> element. ... csvDefRegStatuses-YYYYMMDD.csv ... ...]]> Example of the corresponding defRegStatuses-YYYYMMDD.csv file. The file contains the statuses for the defensive registration object EXAMPLE1_DEFREG-REP.

"defRegTransfer" CSV File Definition 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, MUST be used in the "defRegTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>: Registry Object IDentifier (ROID) for the defensive registration object with isRequired="true".
<rdeCsv:fTrStatus>: State of the most recent transfer request with isRequired="true".
<rdeCsv:fReRr>: Identifier of the registrar, defined in , of the client that requested the transfer with isRequired="true".
<rdeCsv:fReDate>: Date and time that the transfer was requested with isRequired="true".
<rdeCsv:fAcRr>: Identifier of the registrar, defined in , of the client that should take or took action with isRequired="true".
<rdeCsv:fAcDate>: Date and time that the transfer action should be taken or has been taken with isRequired="true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "defRegTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fExDate>: Expiration date if the transfer command caused or causes a change in the validity period.
<rdeCsv:fReID>: Identifier of the client that requested the transfer.
<rdeCsv:fAcID>: Identifier of the client that should take or took action for transfer.

Example of a "defRegTransfer" <csvDefReg:contents> <rdeCsv:csv> element. ... defRegTransfer-YYYYMMDD.csv ... ...]]> Example of the corresponding defRegTransfer-YYYYMMDD.csv file. The file contains one defensive registration transfer record with a pending status.

<csvDefReg:deletes> 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. 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.

"defReg" Deletes CSV File Definition The following "rdeCsv" field elements MUST be used in the deletes "defReg" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>: Registry Object IDentifier (ROID) for the defensive registration object with isRequired="true".

Example of a "defReg" <csvDefReg:deletes> <rdeCsv:csv> element: ... defReg-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding defReg-delete-YYYYMMDD.csv file. The file contains two defensive registration records.

NameWatch Object The NameWatch object is based on the EPP NameWatch mapping specified in . The NameWatch object supports both the XML Model and the CSV Model, defined in the Models section. The elements used for both models are defined in the following sections.

XML Model 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.

<rdeNameWatch:nameWatch> object The <nameWatch> element is based on the EPP NameWatch <info> response for an authorized client (see Section 3.1.2. of ) with additional data from an EPP <transfer> Query Response, see Section 3.1.3. of . 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:

A <roid> element that contains the repository object identifier assigned to the NameWatch object when it was created.
A <name> element that contains the name of the NameWatch object.
An OPTIONAL <registrant> element that contain the identifier for the individual or organizational social information object associated as the holder of the NameWatch object.
An OPTIONAL <rptTo> element that contain the e-mail address to receive the NameWatch reports with the REQUIRED "freq" attribute whose value indicates the report frequency. The "freq" attribute value MUST be "daily", "weekly", or "monthly".
One or more <status> elements that contain the current status descriptors associated with the NameWatch object.
A <clID> element that contains the identifier of the sponsoring registrar.
An OPTIONAL <crRr> element that contains the identifier of the registrar that created the NameWatch object. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
An OPTIONAL <crDate> element that contains the date and time of the NameWatch object creation.
An OPTIONAL <exDate> element that contains the date and time identifying the end (expiration) of the NameWatch object's registration period.
An OPTIONAL <upRr> element that contains the identifier of the registrar that last updated the NameWatch object. This element MUST NOT be present if the NameWatch has never been modified. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
An OPTIONAL <upDate> element that contains the date and time of the most recent successful transfer of the NameWatch object. This element MUST NOT be present if the NameWatch object has never been modified.
An OPTIONAL <trDate> element that contains the date and time of the most recent NameWatch object successful transfer. This element MUST NOT be present if the NameWatch object has never been transferred.
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.
- A <trStatus> element that contains the state of the most recent transfer request.
- A <reRr> element that contains the identifier of the registrar that requested the NameWatch object transfer. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
- A <reDate> element that contains the date and time that the transfer was requested.
- An <acRr> element that contains the identifier of the registrar that SHOULD act upon a PENDING transfer request. For all other status types, the value identifies the registrar that took the indicated action. An OPTIONAL "client" attribute is used to specify the client that performed the operation.
- An <acDate> element that contains the date and time of a required or completed response. For a PENDING 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.
- An OPTIONAL <exDate> element that contains the end of the NameWatch object's validity period (expiry date) if the transfer caused or causes a change in the validity period.

Example of a NameWatch object: EXAMPLE3_NAMEWATCH-VRSN doe jd1234 cdoe@example.com RegistrarX RegistrarX 1999-04-03T22:00:00.0Z 2021-04-03T22:00:00.0Z ...]]>

<rdeNameWatch:delete> object The <rdeNameWatch:delete> element contains the NameWatch repository object identifier that was deleted and purged. Example of <rdeNameWatch:delete> object: ... EXAMPLE1_NAMEWATCH-REP EXAMPLE2_NAMEWATCH-REP ... ...]]>

CSV Model 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 using all of the NameWatch CSV files starting with the parent "nameWatch" CSV File Definition. 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 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 starting from the "nameWatch" Deletes CSV File Definition.

<csvNameWatch:contents> 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:

"nameWatch" CSV File Definition 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:

<csvNameWatch:fName>: NameWatch name field with type="nameWatch:nameType" and isRequired="true".

The following "csvNameWatch" field elements MAY be used in the "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:

<csvNameWatch:rptTo>: Report to field that contains the e-mail address to receive the NameWatch reports with type="nameWatch:emailAddrType".
<csvNameWatch:fRptToFreqType>: Report to frequency for sending of the NameWatch reports to the <csvNameWatch:rptTo> e-mail address with type="nameWatch:freqType" and the possible values of "daily", "weekly", or "monthly".

The following "rdeCsv" and "csvRegistrar" fields, MUST be used in the "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>

Registry Object IDentifier (ROID) for the NameWatch object with isRequired="true".

<rdeCsv:fClID> or <csvRegistrar:fGurid>

A choice of:

<rdeCsv:fClID>: Identifier of the sponsoring client with isRequired="true".
<csvRegistrar:fGurid>: Contains the ID assigned by ICANN with type="positiveInteger". The attribute "isRequired" MUST equal "true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fCrRr>: Identifier of the registrar, defined in , of the client that created the NameWatch object.
<rdeCsv:fCrID>: Identifier of the client that created the NameWatch object.
<rdeCsv:fUpRr>: Identifier of the registrar, defined in , of the client that updated the NameWatch object.
<rdeCsv:fUpID>: Identifier of the client that last updated the NameWatch object.
<rdeCsv:fRegistrant>: Registrant contact identifier for the NameWatch object.
<rdeCsv:fCrDate>: Created date and time of the NameWatch object.
<rdeCsv:fUpDate>: Date and time of the last update to the NameWatch object.
<rdeCsv:fExDate>: Expiration date and time for the NameWatch object.
<rdeCsv:fTrDate>: Date and time of the last successful transfer for the NameWatch object.

Example of a "nameWatch" <csvNameWatch:contents> <rdeCsv:csv> element. ... nameWatch-YYYYMMDD.csv ... ...]]> Example of the corresponding nameWatch-YYYYMMDD.csv file. The file contains one record.

"nameWatchStatuses" CSV File Definition 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, MUST be used in the "nameWatchStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<csvNameWatch:fStatus>: The status of the NameWatch with type="nameWatch:statusValueType" and isRequired="true".

The following "rdeCsv" fields, defined for the CSV common field elements, MUST be used in the "nameWatchStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>: Registry Object IDentifier (ROID) for the NameWatch object with isRequired="true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "nameWatchStatuses" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fStatusDescription>: NameWatch object status description which is free-form text describing the rationale for the status.
<rdeCsv:fLang>: Language of the <rdeCsv:fStatusDescription> field.

Example of a "nameWatchStatuses" <csvNameWatch:contents> <rdeCsv:csv> element. ... csvNameWatchStatuses-YYYYMMDD.csv ... ...]]> Example of the corresponding nameWatchStatuses-YYYYMMDD.csv file. The file contains the statuses for the NameWatch object EXAMPLE1_NAMEWATCH-REP.

"nameWatchTransfer" CSV File Definition 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, MUST be used in the "nameWatchTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>: Registry Object IDentifier (ROID) for the NameWatch object with isRequired="true".
<rdeCsv:fTrStatus>: State of the most recent transfer request with isRequired="true".
<rdeCsv:fReRr>: Identifier of the registrar, defined in , of the client that requested the transfer with isRequired="true".
<rdeCsv:fReDate>: Date and time that the transfer was requested with isRequired="true".
<rdeCsv:fAcRr>: Identifier of the registrar, defined in , of the client that should take or took action with isRequired="true".
<rdeCsv:fAcDate>: Date and time that the transfer action should be taken or has been taken with isRequired="true".

The following "rdeCsv" fields, defined in section CSV common field elements, MAY be used in the "nameWatchTransfer" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fExDate>: Expiration date if the transfer command caused or causes a change in the validity period.
<rdeCsv:fReID>: Identifier of the client that requested the transfer.
<rdeCsv:fAcID>: Identifier of the client that should take or took action for transfer.

Example of a "nameWatchTransfer" <csvNameWatch:contents> <rdeCsv:csv> element. ... nameWatchTransfer-YYYYMMDD.csv ... ...]]> Example of the corresponding nameWatchTransfer-YYYYMMDD.csv file. The file contains one NameWatch transfer record with a pending status.

<csvNameWatch:deletes> 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. 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.

"nameWatch" Deletes CSV File Definition The following "rdeCsv" field elements MUST be used in the deletes "nameWatch" <rdeCsv:csv> <rdeCsv:fields> element:

<rdeCsv:fRoid>: Registry Object IDentifier (ROID) for the NameWatch object with isRequired="true".

Example of a "nameWatch" <csvNameWatch:deletes> <rdeCsv:csv> element: ... nameWatch-delete-YYYYMMDD.csv ... ...]]> Example of the corresponding nameWatch-delete-YYYYMMDD.csv file. The file contains two NameWatch records.