Registration Protocols Extensions R. Carney
Internet-Draft GoDaddy Inc.
Intended status: Standards Track J. Galvin
Expires: December 11, 2016 Afilias USA
June 9, 2016
Non-standard Domain Fees File Format Specification
draft-carney-regext-domain-fees-00
Abstract
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.
Status of This Memo
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 http://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 December 11, 2016.
Copyright Notice
Copyright (c) 2016 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
(http://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 Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Carney & Galvin Expires December 11, 2016 [Page 1]
Internet-Draft Domain Fees June 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Conventions Used in This Document . . . . . . . . . . . . 2
2. General File Format Elements . . . . . . . . . . . . . . . . 2
3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3
3.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 4
3.3. Fee Change File Example . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4
6. Change History . . . . . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
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.
1.1. Conventions Used in This Document
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].
2. General File Format Elements
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.
Carney & Galvin Expires December 11, 2016 [Page 2]
Internet-Draft Domain Fees June 2016
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).
3. Examples
3.1. Single TLD File Example
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-1
1-03T00:00:00.0Z
Carney & Galvin Expires December 11, 2016 [Page 3]
Internet-Draft Domain Fees June 2016
3.2. Multiple TLDs File Example
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,
3.3. Fee Change File Example
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,
4. Security Considerations
The file format described in this document does not provide any
security services.
5. Acknowledgements
The authors wish to thank the following persons for their feedback
and suggestions:
o Christine Turner of GoDaddy Inc.
o Jody Kolker of GoDaddy Inc.
Carney & Galvin Expires December 11, 2016 [Page 4]
Internet-Draft Domain Fees June 2016
o Richard Merdinger of GoDaddy Inc.
o Mike Runcieman of Afilias Canada
o Wayne Beaver of Afilias USA
6. Change History
7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma-
Separated Values (CSV) Files", RFC 4180,
DOI 10.17487/RFC4180, October 2005,
<http://www.rfc-editor.org/info/rfc4180>.
[RFC7111] Hausenblas, M., Wilde, E., and J. Tennison, "URI Fragment
Identifiers for the text/csv Media Type", RFC 7111,
DOI 10.17487/RFC7111, January 2014,
<http://www.rfc-editor.org/info/rfc7111>.
Authors' Addresses
Roger Carney
GoDaddy Inc.
14455 N. Hayden Rd. #219
Scottsdale, AZ 85260
US
Email: rcarney@godaddy.com
URI: http://www.godaddy.com
James Galvin
Afilias USA
300 Welsh Road, Building 3, Suite 105
Horsham, PA 19044
US
Email: jgalvin@afilias.info
URI: http://www.afilias.info
Carney & Galvin Expires December 11, 2016 [Page 5]