idnits 2.17.1 draft-sattler-premium-domain-fee-report-01.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 3 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (January 29, 2019) is 1914 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force T. Sattler, Editor 2 Internet-Draft 3 Intended status: Best Current Practice R. Carney 4 Expires: July 28, 2019 GoDaddy Inc. 5 January 29, 2019 7 Premium Domain Fee Report 8 draft-sattler-premium-domain-fee-report-01 10 Abstract 12 This document describes the content of a Premium Domain Fee Report 13 based on the Report Structure and delivered by the Reporting 14 Repository. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress". 31 This Internet-Draft will expire on June 30, 2019. 33 Copyright Notice 35 Copyright (c) 2019 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Terminology and Definitions . . . . . . . . . . . . . . . . . 2 51 2.1. Internationalized Domain Names . . . . . . . . . . . . . 2 52 2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3 53 2.3. Character Encoding . . . . . . . . . . . . . . . . . . . 3 54 2.4. Currency . . . . . . . . . . . . . . . . . . . . . . . . 3 55 3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3 56 4. Fees . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5.1. Single TLD File Example . . . . . . . . . . . . . . . . . 4 59 5.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 4 60 5.3. Fee Change File Example . . . . . . . . . . . . . . . . . 5 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 62 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 63 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 5 64 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 9.1. Normative References . . . . . . . . . . . . . . . . . . 6 66 9.2. Informative References . . . . . . . . . . . . . . . . . 6 67 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 7 68 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 7 69 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 7 70 A.3. Change from 02 to PREMIUMFEE 00 . . . . . . . . . . . . 7 71 A.4. Change from PREMIUMFEE 00 to PREMIUMFEE 01 . . . . . . . 7 72 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 7 73 Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . . 7 75 1. Introduction 77 Modern top-level domain registries provide a number of detailed 78 reports and documents that their registrars require on a daily, 79 weekly and monthly basis. These most commonly include transaction 80 reports, as well as lists containing currently unavailable domains 81 and current premium domain fees. These reports are critical for 82 registrars' businesses and play an important role in accounting and 83 operations processes as well as in sales and marketing activities. 84 In the current set-up registrars must download these reports from 85 each registry's intranet in a different manner according to each 86 registry's own document management set up. 88 This document describes the content of a Premium Domain Fee Report 89 based on the [I-D.mcpherson-sattler-report-structure] and delivered 90 by the [I-D.mcpherson-sattler-reporting-repository]. 92 2. Terminology and Definitions 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 96 document are to be interpreted as described in [RFC2119] when 97 specified in their uppercase forms. 99 2.1. Internationalized Domain Names 101 MUST be as defined in 102 [I-D.mcpherson-sattler-report-structure]. 104 2.2. Dates and Times 106 MUST be as defined in 107 [I-D.mcpherson-sattler-report-structure]. 109 2.3. Character Encoding 111 MUST be as defined in 112 [I-D.mcpherson-sattler-report-structure]. 114 2.4. Currency 116 MUST be as defined in 117 [I-D.mcpherson-sattler-report-structure]. 119 3. Report Headings 121 The first row MUST be the column headings in the following order: 123 TLD It MUST contain the top-level domain name and 124 formatted according to section 2.1 of this 125 document. 127 DOMAIN It MUST contain the domain name formatted according 128 to section 2.1 of this document. 130 STATUS It MUST contain the status of the domain name. It 131 MUST either be 'REGISTRY REGISTERED', 'REGISTERED', 132 'AVAILABLE', 'REGISTRY RESERVED' or 'POLICY 133 RESERVED'. 135 DESCRIPTION It MUST contain the descriptive name of the premium 136 tier to which the domain is allocated. 138 CURRENCY It MUST contain the currency of the following fees 139 according to section 2.4 of this document. 141 CREATE It MUST contain the fee for a domain create. 143 RENEW It MUST contain the fee for a domain renew. 145 TRANSFER It MUST contain the fee for a domain transfer. 147 RESTORE It MUST contain the fee for a domain restore. 149 EFFECTIVE DATE It MUST contain the date and time the fee listed 150 will go into effect and formatted according to 151 section 2.2 of this document. 153 4. Fees 155 Fees MUST either be whole numbers or rounded to two decimal places. 156 A period (.) is used as the dividing point. 158 5. Examples 160 5.1. Single TLD File Example 162 This is an example of a domain fee report for a single top-level 163 domain .example with non-standard fees. 165 Filename: example_premium-domains_2018-11-01.csv.gz 167 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE, 168 EFFECTIVE DATE 169 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40, 170 2018-11-08T00:00:00Z 171 example,test2.example,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40, 172 2018-11-08T00:00:00Z 173 example,test3.example,AVAILABLE,B,USD,10000,10000,10000,40, 174 2018-12-01T00:00:00Z 175 example,xn--4gqvdy3r.example,AVAILABLE,A,USD,50,50,50,40, 176 2018-12-01T06:00:00Z 178 5.2. Multiple TLDs File Example 180 This is an example of a domain fee report for multiple top-level 181 domains from example registry with non-standard fees. 183 Filename: example-registry_premium-domains_2018-11.csv.gz 185 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE, 186 EFFECTIVE DATE 187 example1,test1.example1,REGISTRY RESERVED,A,USD,200,200,200,40, 188 2018-11-08T00:00:00Z 189 example2,test1.example2,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40, 190 2018-11-08T00:00:00Z 191 example3,test2.example3,AVAILABLE,B,USD,10000,10000,10000,40, 192 2018-12-01T00:00:00Z 193 xn--zckzah,xn--r8jz45g.xn--zckzah,AVAILABLE,A,USD,50,50,50,40, 194 2018-12-01T06:00:00Z 196 5.3. Fee Change File Example 198 If the fee for a domain name is changing or moving to reserved or 199 unreserved in the future, there MUST be two entries for the name. 201 One entry for the current fee and status of the name, this entry MUST 202 be removed once the change takes place, and one entry for the future 203 fee of the name with its effective date. 205 Example of a file that contains a future fee change for a single top- 206 level domain .example. 208 Filename: example_premium-domains_2018-11-01.csv.gz 210 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE, 211 EFFECTIVE DATE 212 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40, 213 2018-11-01T00:00:00Z 214 example,test1.example,REGISTRY RESERVED,DD,USD,75.50,75.50,75.50,40, 215 2018-12-01T00:00:00Z 217 6. IANA Considerations 219 This document has no IANA actions. 221 7. Security Considerations 223 The Premium Domain Fee Report described in this document does not 224 provide any security services. 226 8. Implementation Status 228 Note to RFC Editor: Please remove this section and the reference to 229 [RFC7942] before publication. 231 This section records the status of known implementations of the 232 protocol defined by this specification at the time of posting of this 233 Internet-Draft, and is based on a proposal described in [RFC7942]. 234 The description of implementations in this section is intended to 235 assist the IETF in its decision processes in progressing drafts to 236 RFCs. Please note that the listing of any individual implementation 237 here does not imply endorsement by the IETF. Furthermore, no effort 238 has been spent to verify the information presented here that was 239 supplied by IETF contributors. This is not intended as, and must not 240 be construed to be, a catalog of available implementations or their 241 features. Readers are advised to note that other implementations may 242 exist. 244 According to [RFC7942], "this will allow reviewers and working groups 245 to assign due consideration to documents that have the benefit of 246 running code, which may serve as evidence of valuable experimentation 247 and feedback that have made the implemented protocols more mature. It 248 is up to the individual working groups to use this information as 249 they see fit". 251 Add implementation details once available. 253 9. References 255 9.1. Normative References 257 [I-D.mcpherson-sattler-report-structure] 258 McPherson, N. and Sattler, T., "Report Strucutre", 259 (work in progress), January 2019 262 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 263 Requirement Levels", BCP 14, RFC 2119, March 1997, 264 . 266 9.2. Informative References 268 [I-D.mcpherson-sattler-reporting-repository] 269 McPherson, N. and Sattler, T., "Reporting Repository", 270 (work in progress), January 2019 273 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 274 Running Code: The Implementation Status Section", RFC 275 7942, July 2016, 276 . 278 Appendix A. Change History 280 A.1. Change from 00 to 01 282 Fixed minor typos. Clarified example file name in section 5.3. 284 A.2. Change from 01 to 02 286 Clarified the Period. Fixed numerous typos. 288 A.3. Change from 02 to PREMIUMFEE 00 290 Changed draft name. Added Roger Carney as additional author. 292 A.4. Change from PREMIUMFEE 00 to PREMIUMFEE 01 294 Editorial changes. 296 Appendix B. Acknowledgements 298 The authors wish to thank the following persons for their feedback 299 and suggestions (sorted alphabetically by company): 301 o Neal McPherson, 1&1 IONOS 302 o James Galvin, Afilias 303 o Jody Kolker, GoDaddy 305 Authors' Addresses 307 Tobias Sattler 309 Email: tobias.sattler@me.com 310 URI: https://tobiassattler.com 312 Roger Carney 313 GoDaddy Inc. 314 14455 N. Hayden Rd. #219 315 Scottsdale, AZ 85260 316 US 318 Email: rcarney@godaddy.com 319 URI: http://www.godaddy.com