Non-standard Domain Fees File Format Specification

This document defines the file format for the storage of non-standard domain name fees and related details for a top level domain name registry, designed to facilitate interoperability and reusability among domain name registries and registrars. The increased number of domain name registries and registrars, the greater number of registration fees for domain names in a single Top Level Domain (TLD), and to make accommodations for possible real-time communications issues between registries and registrars has driven the need for this standard sharable file.

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.

File format will be a comma separated values (CSV) file and MUST use the US-ASCII character set. See informational RFC 4180 and RFC 7111 for details on the CSV file format. Filename has two forms depending on content. For a file containing only a list of domain names in one Top Level Domain (TLD) the filename MUST be <TLD>-nonstandardnames-<YYYY-MM-DDThhmmss>.csv. For a file containing a list of domain names in multiple Top Level Domains (TLDs) the filename MUST be nonstandardnames-<YYYY-MM-DDThhmmss>.csv. For an IDN TLD <TLD> MUST be ace-encoded (i.e. in the "xn--" format). Additionally, <YYYY-MM-DDThhmmss> MUST be the date and time (in UTC) the file was created. The first row MUST be the column headings: TLD, Domain Name, Status, Description, Currency, Domain Create Fee (Yearly), Domain Renew Fee (Yearly), Domain Transfer Fee (Yearly), Domain Restore Fee (per Restore), Effective Date. The remaining rows will contain the data (all unavailable names) from the registry in the following structure: <TLD>, <Domain Name>, <Status>, <Description>, <Currency>, <Domain Create Fee (Yearly)>, <Domain Renew Fee (Yearly)>, <Domain Transfer Fee (Yearly)>, <Domain Restore Fee (per Restore)>, <Effective Date>. Where <TLD> is the TLD of the domain name, <Domain Name> is the string of characters that represent the domain name, <Status> is one of five values (REGISTRY REGISTERED, REGISTERED, AVAILABLE, REGISTRY RESERVED, POLICY RESERVED), <Description> is the descriptive name for the premium tier to which the name is allocated, <Currency> is the ISO 4217 Alpha Currency Code for the currency required by the EPP commands used with the SRS, <Domain Create Fee (Yearly)> is the 1-year Initial Registration fee to the Registrar incurred on a 1-year domain create EPP command and does not reflect any marketing or rebate reductions, <Domain Renew Fee (Yearly)> is the 1-year renewal fee to the Registrar incurred on a 1-year domain renewal EPP command and does not reflect any marketing or rebate reductions, <Domain Transfer Fee (Yearly)> is the fee to the Registrar that is incurred when the domain is transferred between Registrars, <Domain Restore Fee (per Restore)> is the fee to the Registrar to restore a domain that is in the Redemption Period, <Effective Date> is the date and time the fee listed will go into effect in UTC time using the combined date/time format from ISO 8601 (YYYY-MM-DDThh:mm:ss.sZ). If the <TLD> and/or <Domain Name> is an IDN it MUST be ace-encoded (i.e. in the "xn--" format).

Example of a file that contains domain names from a single TLD with non-standard fees. FileName: example-nonstandardnames-2016-05-01T010000.csv TLD,Domain Name,Status,Description,Currency,Domain Create Fee (Yearly),Domain Renew Fee (Yearly),Domain Transfer Fee (Yearly),Domain Restore Fee (per Restore),Effective Date example,e.example,REGISTRY RESERVED,A,USD,200,200,200,40,2016-02-05T09:31:40.2Z example,ex.example,POLICY RESERVED,A,USD,200,200,200,40, example,example.example,AVAILABLE,B,USD,500.75,500.75,500.75,40, example,xn--4gqvdy3r.example,AVAILABLE,A,USD,200,200,200,40,2016-11-03T00:00:00.0Z

Example of a file that contains domain names from multiple TLDs with non-standard fees. FileName: nonstandardnames-2016-05-01T010000.csv TLD,Domain Name,Status,Description,Currency,Domain Create Fee (Yearly),Domain Renew Fee (Yearly),Domain Transfer Fee (Yearly),Domain Restore Fee (per Restore),Effective Date example,e.example,REGISTRY RESERVED,A,USD,200,200,200,40,2016-02-05T09:31:40.2Z test,ex.test,POLICY RESERVED,A,USD,200,200,200,40, another, xn--4gqvdy3r.another,AVAILABLE,B,USD,500.75,500.75,500.75,40,

If the fee for a domain name is changing or moving to reserved or unreserved in the future, there SHOULD be two entries for the name: an entry for the current fee and status of the name (This entry will be removed once the change takes place.) and an entry for the future fee of the name with the effective date in YYYY-MM-DDThh:mm:ss.sZ format. Example of a file that contains a future fee change. FileName: nonstandardnames-2016-05-01T010000.csv TLD,Domain Name,Status,Description,Currency,Domain Create Fee (Yearly),Domain Renew Fee (Yearly),Domain Transfer Fee (Yearly),Domain Restore Fee (per Restore),Effective Date example,e.example,REGISTRY RESERVED,A,USD,200,200,200,40,2016-02-05T09:31:40.2Z example,e.example,REGISTRY RESERVED,B,USD,100,100,100,40,

The file format described in this document does not provide any security services.

The authors wish to thank the following persons for their feedback and suggestions: Christine Turner of GoDaddy Inc. Jody Kolker of GoDaddy Inc. Richard Merdinger of GoDaddy Inc. Mike Runcieman of Afilias Canada Wayne Beaver of Afilias USA