idnits 2.17.1 draft-carney-regext-domain-fees-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 9, 2016) is 2877 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC4180' is defined on line 208, but no explicit reference was found in the text == Unused Reference: 'RFC7111' is defined on line 213, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 4180 ** Downref: Normative reference to an Informational RFC: RFC 7111 Summary: 3 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Registration Protocols Extensions R. Carney 3 Internet-Draft GoDaddy Inc. 4 Intended status: Standards Track J. Galvin 5 Expires: December 11, 2016 Afilias USA 6 June 9, 2016 8 Non-standard Domain Fees File Format Specification 9 draft-carney-regext-domain-fees-00 11 Abstract 13 This document defines the file format for the storage of non-standard 14 domain name fees and related details for a top level domain name 15 registry. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on December 11, 2016. 34 Copyright Notice 36 Copyright (c) 2016 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Conventions Used in This Document . . . . . . . . . . . . 2 53 2. General File Format Elements . . . . . . . . . . . . . . . . 2 54 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3 56 3.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 4 57 3.3. Fee Change File Example . . . . . . . . . . . . . . . . . 4 58 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 59 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 60 6. Change History . . . . . . . . . . . . . . . . . . . . . . . 5 61 7. Normative References . . . . . . . . . . . . . . . . . . . . 5 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 64 1. Introduction 66 This document defines the file format for the storage of non-standard 67 domain name fees and related details for a top level domain name 68 registry, designed to facilitate interoperability and reusability 69 among domain name registries and registrars. 71 The increased number of domain name registries and registrars, the 72 greater number of registration fees for domain names in a single Top 73 Level Domain (TLD), and to make accommodations for possible real-time 74 communications issues between registries and registrars has driven 75 the need for this standard sharable file. 77 1.1. Conventions Used in This Document 79 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 80 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 81 document are to be interpreted as described in RFC 2119 [RFC2119]. 83 2. General File Format Elements 85 File format will be a comma separated values (CSV) file and MUST use 86 the US-ASCII character set. See informational RFC 4180 and RFC 7111 87 for details on the CSV file format. 89 Filename has two forms depending on content. For a file containing 90 only a list of domain names in one Top Level Domain (TLD) the 91 filename MUST be -nonstandardnames-.csv. For 92 a file containing a list of domain names in multiple Top Level 93 Domains (TLDs) the filename MUST be nonstandardnames-.csv. For an IDN TLD MUST be ace-encoded (i.e. in 95 the "xn--" format). Additionally, MUST be the 96 date and time (in UTC) the file was created. 98 The first row MUST be the column headings: TLD, Domain Name, Status, 99 Description, Currency, Domain Create Fee (Yearly), Domain Renew Fee 100 (Yearly), Domain Transfer Fee (Yearly), Domain Restore Fee (per 101 Restore), Effective Date. The remaining rows will contain the data 102 (all unavailable names) from the registry in the following structure: 103 , , , , , , , , , . 106 Where is the TLD of the domain name, is the 107 string of characters that represent the domain name, is one 108 of five values (REGISTRY REGISTERED, REGISTERED, AVAILABLE, REGISTRY 109 RESERVED, POLICY RESERVED), is the descriptive name for 110 the premium tier to which the name is allocated, is the 111 ISO 4217 Alpha Currency Code for the currency required by the EPP 112 commands used with the SRS, is the 113 1-year Initial Registration fee to the Registrar incurred on a 1-year 114 domain create EPP command and does not reflect any marketing or 115 rebate reductions, is the 1-year renewal 116 fee to the Registrar incurred on a 1-year domain renewal EPP command 117 and does not reflect any marketing or rebate reductions, is the fee to the Registrar that is incurred 119 when the domain is transferred between Registrars, is the fee to the Registrar to restore a domain 121 that is in the Redemption Period, is the date and 122 time the fee listed will go into effect in UTC time using the 123 combined date/time format from ISO 8601 (YYYY-MM-DDThh:mm:ss.sZ). If 124 the and/or is an IDN it MUST be ace-encoded (i.e. 125 in the "xn--" format). 127 3. Examples 129 3.1. Single TLD File Example 131 Example of a file that contains domain names from a single TLD with 132 non-standard fees. 134 FileName: example-nonstandardnames-2016-05-01T010000.csv 136 TLD,Domain Name,Status,Description,Currency,Domain Create Fee 137 (Yearly),Domain Renew Fee (Yearly),Domain Transfer Fee 138 (Yearly),Domain Restore Fee (per Restore),Effective Date 139 example,e.example,REGISTRY 140 RESERVED,A,USD,200,200,200,40,2016-02-05T09:31:40.2Z 141 example,ex.example,POLICY RESERVED,A,USD,200,200,200,40, 142 example,example.example,AVAILABLE,B,USD,500.75,500.75,500.75,40, 143 example,xn--4gqvdy3r.example,AVAILABLE,A,USD,200,200,200,40,2016-1 144 1-03T00:00:00.0Z 146 3.2. Multiple TLDs File Example 148 Example of a file that contains domain names from multiple TLDs with 149 non-standard fees. 151 FileName: nonstandardnames-2016-05-01T010000.csv 153 TLD,Domain Name,Status,Description,Currency,Domain Create Fee 154 (Yearly),Domain Renew Fee (Yearly),Domain Transfer Fee 155 (Yearly),Domain Restore Fee (per Restore),Effective Date 156 example,e.example,REGISTRY 157 RESERVED,A,USD,200,200,200,40,2016-02-05T09:31:40.2Z 158 test,ex.test,POLICY RESERVED,A,USD,200,200,200,40, 159 another, xn-- 160 4gqvdy3r.another,AVAILABLE,B,USD,500.75,500.75,500.75,40, 162 3.3. Fee Change File Example 164 If the fee for a domain name is changing or moving to reserved or 165 unreserved in the future, there SHOULD be two entries for the name: 166 an entry for the current fee and status of the name (This entry will 167 be removed once the change takes place.) and an entry for the future 168 fee of the name with the effective date in YYYY-MM-DDThh:mm:ss.sZ 169 format. 171 Example of a file that contains a future fee change. 173 FileName: nonstandardnames-2016-05-01T010000.csv 175 TLD,Domain Name,Status,Description,Currency,Domain Create Fee 176 (Yearly),Domain Renew Fee (Yearly),Domain Transfer Fee 177 (Yearly),Domain Restore Fee (per Restore),Effective Date 178 example,e.example,REGISTRY 179 RESERVED,A,USD,200,200,200,40,2016-02-05T09:31:40.2Z 180 example,e.example,REGISTRY RESERVED,B,USD,100,100,100,40, 182 4. Security Considerations 184 The file format described in this document does not provide any 185 security services. 187 5. Acknowledgements 189 The authors wish to thank the following persons for their feedback 190 and suggestions: 192 o Christine Turner of GoDaddy Inc. 193 o Jody Kolker of GoDaddy Inc. 195 o Richard Merdinger of GoDaddy Inc. 196 o Mike Runcieman of Afilias Canada 197 o Wayne Beaver of Afilias USA 199 6. Change History 201 7. Normative References 203 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 204 Requirement Levels", BCP 14, RFC 2119, 205 DOI 10.17487/RFC2119, March 1997, 206 . 208 [RFC4180] Shafranovich, Y., "Common Format and MIME Type for Comma- 209 Separated Values (CSV) Files", RFC 4180, 210 DOI 10.17487/RFC4180, October 2005, 211 . 213 [RFC7111] Hausenblas, M., Wilde, E., and J. Tennison, "URI Fragment 214 Identifiers for the text/csv Media Type", RFC 7111, 215 DOI 10.17487/RFC7111, January 2014, 216 . 218 Authors' Addresses 220 Roger Carney 221 GoDaddy Inc. 222 14455 N. Hayden Rd. #219 223 Scottsdale, AZ 85260 224 US 226 Email: rcarney@godaddy.com 227 URI: http://www.godaddy.com 229 James Galvin 230 Afilias USA 231 300 Welsh Road, Building 3, Suite 105 232 Horsham, PA 19044 233 US 235 Email: jgalvin@afilias.info 236 URI: http://www.afilias.info