idnits 2.17.1
draft-sattler-premium-domain-fee-report-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 :
----------------------------------------------------------------------------
== 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 (December 28, 2018) is 1945 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: June 27, 2019 GoDaddy Inc.
5 December 28, 2018
7 Premium Domain Fee Report
8 draft-sattler-premium-domain-fee-report-00
10 Abstract
12 This document describes the content of a premium domain name fee
13 report based on the registry report structure and delivered by the
14 registry reporting 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 27, 2019.
33 Copyright Notice
35 Copyright (c) 2018 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 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 7
72 Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . . 7
74 1. Introduction
76 Modern top-level domain registries provide a number of detailed
77 reports and documents that their registrars require on a daily,
78 weekly and monthly basis. These most commonly include transaction
79 reports, as well as lists containing currently unavailable domains
80 and current premium domains. These reports are critical for
81 registrars' businesses and play an important role in accounting and
82 operations processes as well as in sales and marketing activities.
83 In the current set-up registrars must download these reports from
84 each registry's intranet in a different manner according to each
85 registry's own document management set up.
87 This document describes the content of a premium domain fee report
88 based on the [I-D.mcpherson-sattler-registry-report-structure] and
89 delivered by the [I-D.mcpherson-sattler-registry-reporting-repo].
91 2. Terminology and Definitions
93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
95 document are to be interpreted as described in [RFC2119] when
96 specified in their uppercase forms.
98 2.1. Internationalized Domain Names
100 MUST be as defined in
101 [I-D.mcpherson-sattler-registry-report-structure].
103 2.2. Dates and Times
105 MUST be as defined in
106 [I-D.mcpherson-sattler-registry-report-structure].
108 2.3. Character Encoding
110 MUST be as defined in
111 [I-D.mcpherson-sattler-registry-report-structure].
113 2.4. Currency
115 MUST be as defined in
116 [I-D.mcpherson-sattler-registry-report-structure].
118 3. Report Headings
120 The first row MUST be the column headings in the following order:
122 TLD It MUST contain the top-level domain name and
123 formatted according to section 2.1 of this
124 document.
126 DOMAIN It MUST contain the domain name formatted according
127 to section 2.1 of this document.
129 STATUS It MUST contain the status of the domain name. It
130 MUST either be 'REGISTRY REGISTERED', 'REGISTERED',
131 'AVAILABLE', 'REGISTRY RESERVED' or 'POLICY
132 RESERVED'.
134 DESCRIPTION It MUST contain the descriptive name of the premium
135 tier to which the domain is allocated.
137 CURRENCY It MUST contain the currency of the following fees
138 according to section 2.4 of this document.
140 CREATE It MUST contain the fee for a domain create.
142 RENEW It MUST contain the fee for a domain renew.
144 TRANSFER It MUST contain the fee for a domain transfer.
146 RESTORE It MUST contain the fee for a domain restore.
148 EFFECTIVE DATE It MUST contain the date and time the fee listed
149 will go into effect and formatted according to
150 section 2.2 of this document.
152 4. Fees
154 Fees MUST either be whole numbers or rounded to two decimal places.
155 A period (.) is used as the dividing point.
157 5. Examples
159 5.1. Single TLD File Example
161 This is an example of a domain fee report for a single top-level
162 domain .example with non-standard fees.
164 Filename: example_premium-domains_2018-11-01.csv.gz
166 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
167 EFFECTIVE DATE
168 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40,
169 2018-11-08T00:00:00Z
170 example,test2.example,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40,
171 2018-11-08T00:00:00Z
172 example,test3.example,AVAILABLE,B,USD,10000,10000,10000,40,
173 2018-12-01T00:00:00Z
174 example,xn--4gqvdy3r.example,AVAILABLE,A,USD,50,50,50,40,
175 2018-12-01T06:00:00Z
177 5.2. Multiple TLDs File Example
179 This is an example of a domain fee report for multiple top-level
180 domains from example registry with non-standard fees.
182 Filename: example-registry_premium-domains_2018-11.csv.gz
184 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
185 EFFECTIVE DATE
186 example1,test1.example1,REGISTRY RESERVED,A,USD,200,200,200,40,
187 2018-11-08T00:00:00Z
188 example2,test1.example2,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40,
189 2018-11-08T00:00:00Z
190 example3,test2.example3,AVAILABLE,B,USD,10000,10000,10000,40,
191 2018-12-01T00:00:00Z
192 xn--zckzah,xn--r8jz45g.xn--zckzah,AVAILABLE,A,USD,50,50,50,40,
193 2018-12-01T06:00:00Z
195 5.3. Fee Change File Example
197 If the fee for a domain name is changing or moving to reserved or
198 unreserved in the future, there MUST be two entries for the name.
200 One entry for the current fee and status of the name, this entry MUST
201 be removed once the change takes place, and one entry for the future
202 fee of the name with its effective date.
204 Example of a file that contains a future fee change for a single top-
205 level domain .example.
207 Filename: example_premium-domains_2018-11-01.csv.gz
209 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
210 EFFECTIVE DATE
211 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40,
212 2018-11-01T00:00:00Z
213 example,test1.example,REGISTRY RESERVED,DD,USD,75.50,75.50,75.50,40,
214 2018-12-01T00:00:00Z
216 6. IANA Considerations
218 This document has no IANA actions.
220 7. Security Considerations
222 The Premium Domain Fee Report described in this document does not
223 provide any security services.
225 8. Implementation Status
227 Note to RFC Editor: Please remove this section and the reference to
228 [RFC7942] before publication.
230 This section records the status of known implementations of the
231 protocol defined by this specification at the time of posting of this
232 Internet-Draft, and is based on a proposal described in [RFC7942].
233 The description of implementations in this section is intended to
234 assist the IETF in its decision processes in progressing drafts to
235 RFCs. Please note that the listing of any individual implementation
236 here does not imply endorsement by the IETF. Furthermore, no effort
237 has been spent to verify the information presented here that was
238 supplied by IETF contributors. This is not intended as, and must not
239 be construed to be, a catalog of available implementations or their
240 features. Readers are advised to note that other implementations may
241 exist.
243 According to [RFC7942], "this will allow reviewers and working groups
244 to assign due consideration to documents that have the benefit of
245 running code, which may serve as evidence of valuable experimentation
246 and feedback that have made the implemented protocols more mature. It
247 is up to the individual working groups to use this information as
248 they see fit".
250 Add implementation details once available.
252 9. References
254 9.1. Normative References
256 [I-D.mcpherson-sattler-registry-report-structure]
257 McPherson, N. and Sattler, T., "Registry Report Strucutre"
258 , (work in
260 progress), November 2018
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-registry-reporting-repo]
269 McPherson, N. and Sattler, T., "Registry Reporting
270 Repository", (work in
272 progress), November 2018
274 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of
275 Running Code: The Implementation Status Section", RFC
276 7942, July 2016,
277 .
279 Appendix A. Change History
281 A.1. Change from 00 to 01
283 Fixed minor typos. Clarified example file name in section 5.3.
285 A.2. Change from 01 to 02
287 Clarified the Period. Fixed numerous typos.
289 A.2. Change from 02 to PREMIUMFEE 00
291 Changed draft name. Added Roger Carney as additional author.
293 Appendix B. Acknowledgements
295 The authors wish to thank the following persons for their feedback
296 and suggestions (sorted alphabetically by company):
298 o Neal McPherson, 1&1 IONOS
299 o James Galvin, Afilias
300 o Jody Kolker, GoDaddy
302 Authors' Addresses
304 Tobias Sattler
306 Email: tobias.sattler@me.com
307 URI: https://tobiassattler.com
309 Roger Carney
310 GoDaddy Inc.
311 14455 N. Hayden Rd. #219
312 Scottsdale, AZ 85260
313 US
315 Email: rcarney@godaddy.com
316 URI: http://www.godaddy.com