idnits 2.17.1
draft-sattler-premium-domain-fee-report-03.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 :
----------------------------------------------------------------------------
== 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 (September 26, 2019) is 1674 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 (~~), 2 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: March 25, 2020 GoDaddy Inc.
5 September 26, 2019
7 Premium Domain Fee Report
8 draft-sattler-premium-domain-fee-report-03
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 March 25, 2020.
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 . . . . . . . . . . . . . 3
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 A.5. Change from PREMIUMFEE 01 to PREMIUMFEE 02 . . . . . . . 7
73 A.6. Change from PREMIUMFEE 02 to PREMIUMFEE 03 . . . . . . . 7
74 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 7
75 Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . . 7
77 1. Introduction
79 Modern top-level domain registries provide many detailed reports and
80 documents that their registrars require on a daily, weekly and
81 monthly basis. These most commonly include transaction reports, as
82 well as lists containing currently unavailable domains and current
83 premium domain fees. These reports are critical for registrars'
84 businesses and play an important role in accounting and operations
85 processes as well as in sales and marketing activities. In the
86 current set-up, registrars must download these reports from each
87 registry's intranet differently according to each registry's document
88 management set up.
90 This document describes the content of a Premium Domain Fee Report
91 based on the [I-D.mcpherson-sattler-report-structure] and delivered
92 by the [I-D.mcpherson-sattler-reporting-repository].
94 2. Terminology and Definitions
96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
98 document are to be interpreted as described in [RFC2119] when
99 specified in their uppercase forms.
101 2.1. Internationalized Domain Names
103 MUST be as defined in
104 [I-D.mcpherson-sattler-report-structure].
106 2.2. Dates and Times
108 MUST be as defined in
109 [I-D.mcpherson-sattler-report-structure].
111 2.3. Character Encoding
113 MUST be as defined in
114 [I-D.mcpherson-sattler-report-structure].
116 2.4. Currency
118 MUST be as defined in
119 [I-D.mcpherson-sattler-report-structure].
121 3. Report Headings
123 The first row MUST be the column headings in the following order:
125 TLD It MUST contain the top-level domain name and
126 formatted according to section 2.1 of this
127 document.
129 DOMAIN It MUST contain the domain name formatted according
130 to section 2.1 of this document.
132 STATUS It MUST contain the status of the domain name. It
133 MUST either be 'REGISTRY REGISTERED', 'REGISTERED',
134 'AVAILABLE', 'REGISTRY RESERVED' or 'POLICY
135 RESERVED'.
137 DESCRIPTION It MUST contain the descriptive name of the premium
138 tier to which the domain is allocated.
140 CURRENCY It MUST contain the currency of the following fees
141 according to section 2.4 of this document.
143 CREATE It MUST contain the fee for a domain create.
145 RENEW It MUST contain the fee for a domain renew.
147 TRANSFER It MUST contain the fee for a domain transfer.
149 RESTORE It MUST contain the fee for a domain restore.
151 EFFECTIVE DATE It MUST contain the date and time the fee listed
152 will go into effect and formatted according to
153 section 2.2 of this document.
155 4. Fees
157 Fees MUST either be whole numbers or rounded to two decimal places.
158 The dividing point is a period (.).
160 5. Examples
162 5.1. Single TLD File Example
164 This is an example of a domain fee report for a single top-level
165 domain .example with non-standard fees.
167 Filename: example_premium-domains_2018-11-01.csv.gz
169 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
170 EFFECTIVE DATE
171 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40,
172 2018-11-08T00:00:00Z
173 example,test2.example,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40,
174 2018-11-08T00:00:00Z
175 example,test3.example,AVAILABLE,B,USD,10000,10000,10000,40,
176 2018-12-01T00:00:00Z
177 example,xn--4gqvdy3r.example,AVAILABLE,A,USD,50,50,50,40,
178 2018-12-01T06:00:00Z
180 5.2. Multiple TLDs File Example
182 This is an example of a domain fee report for multiple top-level
183 domains from example registry with non-standard fees.
185 Filename: example-registry_premium-domains_2018-11.csv.gz
187 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
188 EFFECTIVE DATE
189 example1,test1.example1,REGISTRY RESERVED,A,USD,200,200,200,40,
190 2018-11-08T00:00:00Z
191 example2,test1.example2,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40,
192 2018-11-08T00:00:00Z
193 example3,test2.example3,AVAILABLE,B,USD,10000,10000,10000,40,
194 2018-12-01T00:00:00Z
195 xn--zckzah,xn--r8jz45g.xn--zckzah,AVAILABLE,A,USD,50,50,50,40,
196 2018-12-01T06:00:00Z
198 5.3. Fee Change File Example
200 If the fee for a domain name is changing or moving to reserved or
201 unreserved in the future, there MUST be two entries for the domain.
203 One entry for the current fee and status of the name, this entry MUST
204 be removed once the change takes place, and one entry for the future
205 price of the domain name with its effective date.
207 Example of a file that contains a future fee change for a single top-
208 level domain .example.
210 Filename: example_premium-domains_2018-11-01.csv.gz
212 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
213 EFFECTIVE DATE
214 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40,
215 2018-11-01T00:00:00Z
216 example,test1.example,REGISTRY RESERVED,DD,USD,75.50,75.50,75.50,40,
217 2018-12-01T00:00:00Z
219 6. IANA Considerations
221 This document has no IANA actions.
223 7. Security Considerations
225 The Premium Domain Fee Report described in this document does not
226 provide any security services.
228 8. Implementation Status
230 Note to RFC Editor: Please remove this section and the reference to
231 [RFC7942] before publication.
233 This section records the status of known implementations of the
234 protocol defined by this specification at the time of posting of this
235 Internet-Draft, and is based on a proposal described in [RFC7942].
236 The description of implementations in this section is intended to
237 assist the IETF in its decision processes in progressing drafts to
238 RFCs. Please note that the listing of any individual implementation
239 here does not imply endorsement by the IETF. Furthermore, no effort
240 has been spent to verify the information presented here that was
241 supplied by IETF contributors. This is not intended as, and must not
242 be construed to be, a catalog of available implementations or their
243 features. Readers are advised to note that other implementations may
244 exist.
246 According to [RFC7942], "this will allow reviewers and working groups
247 to assign due consideration to documents that have the benefit of
248 running code, which may serve as evidence of valuable experimentation
249 and feedback that have made the implemented protocols more mature. It
250 is up to the individual working groups to use this information as
251 they see fit".
253 Add implementation details once available.
255 9. References
257 9.1. Normative References
259 [I-D.mcpherson-sattler-report-structure]
260 McPherson, N. and Sattler, T., "Report Strucutre",
261 (work in progress), January 2019
264 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
265 Requirement Levels", BCP 14, RFC 2119, March 1997,
266 .
268 9.2. Informative References
270 [I-D.mcpherson-sattler-reporting-repository]
271 McPherson, N. and Sattler, T., "Reporting Repository",
272 (work in progress), January 2019
275 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of
276 Running Code: The Implementation Status Section", RFC
277 7942, July 2016,
278 .
280 Appendix A. Change History
282 A.1. Change from 00 to 01
284 Fixed minor typos. Clarified example file name in section 5.3.
286 A.2. Change from 01 to 02
288 Clarified the Period. Fixed numerous typos.
290 A.3. Change from 02 to PREMIUMFEE 00
292 Changed draft name. Added Roger Carney as additional author.
294 A.4. Change from PREMIUMFEE 00 to PREMIUMFEE 01
296 Editorial changes.
298 A.5. Change from PREMIUMFEE 01 to PREMIUMFEE 02
300 Editorial changes.
302 A.6. Change from PREMIUMFEE 02 to PREMIUMFEE 03
304 Editorial changes.
306 Appendix B. Acknowledgements
308 The authors wish to thank the following persons for their feedback
309 and suggestions (sorted alphabetically by company):
311 o Neal McPherson, 1&1 IONOS
312 o James Galvin, Afilias
313 o Jody Kolker, GoDaddy
315 Authors' Addresses
317 Tobias Sattler
319 Email: tobias.sattler@me.com
320 URI: https://tobiassattler.com
322 Roger Carney
323 GoDaddy Inc.
324 14455 N. Hayden Rd. #219
325 Scottsdale, AZ 85260
326 US
328 Email: rcarney@godaddy.com
329 URI: http://www.godaddy.com