idnits 2.17.1
draft-sattler-registry-domain-fee-report-02.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 3, 2018) is 1971 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
4 Expires: June 2, 2019 December 3, 2018
6 Registry Domain Fee Report
7 draft-sattler-registry-domain-fee-report-02
9 Abstract
11 This document describes the content of a domain name fee report based
12 on the registry report structure and delivered by the registry
13 reporting repository.
15 Status of This Memo
17 This Internet-Draft is submitted in full conformance with the
18 provisions of BCP 78 and BCP 79.
20 Internet-Drafts are working documents of the Internet Engineering
21 Task Force (IETF). Note that other groups may also distribute
22 working documents as Internet-Drafts. The list of current Internet-
23 Drafts is at https://datatracker.ietf.org/drafts/current/.
25 Internet-Drafts are draft documents valid for a maximum of six months
26 and may be updated, replaced, or obsoleted by other documents at any
27 time. It is inappropriate to use Internet-Drafts as reference
28 material or to cite them other than as "work in progress".
30 This Internet-Draft will expire on June 2, 2019.
32 Copyright Notice
34 Copyright (c) 2018 IETF Trust and the persons identified as the
35 document authors. All rights reserved.
37 This document is subject to BCP 78 and the IETF Trust's Legal
38 Provisions Relating to IETF Documents
39 (https://trustee.ietf.org/license-info) in effect on the date of
40 publication of this document. Please review these documents
41 carefully, as they describe your rights and restrictions with respect
42 to this document. Code Components extracted from this document must
43 include Simplified BSD License text as described in Section 4.e of
44 the Trust Legal Provisions and are provided without warranty as
45 described in the Simplified BSD License.
47 Table of Contents
48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
49 2. Terminology and Definitions . . . . . . . . . . . . . . . . . 2
50 2.1. Internationalized Domain Names . . . . . . . . . . . . . 2
51 2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3
52 2.3. Character Encoding . . . . . . . . . . . . . . . . . . . 3
53 2.4. Currency . . . . . . . . . . . . . . . . . . . . . . . . 3
54 3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3
55 4. Fees . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
56 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 4
57 5.1. Single TLD File Example . . . . . . . . . . . . . . . . . 4
58 5.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 4
59 5.3. Fee Change File Example . . . . . . . . . . . . . . . . . 5
60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
61 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
62 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 5
63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
64 9.1. Normative References . . . . . . . . . . . . . . . . . . 6
65 9.2. Informative References . . . . . . . . . . . . . . . . . 6
66 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 7
67 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 7
68 A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 7
69 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 7
70 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 7
72 1. Introduction
74 Modern top-level domain registries provide a number of detailed
75 reports and documents that their registrars require on a daily,
76 weekly and monthly basis. These most commonly include transaction
77 reports, as well as lists containing currently unavailable domains
78 and current premium domains. These reports are critical for
79 registrars' businesses and play an important role in accounting and
80 operations processes as well as in sales and marketing activities.
81 In the current set-up registrars must download these reports from
82 each registry's intranet in a different manner according to each
83 registry's own document management set up.
85 This document describes the content of a domain fee report based on
86 the [I-D.mcpherson-sattler-registry-report-structure] and delivered
87 by the [I-D.mcpherson-sattler-registry-reporting-repo].
89 2. Terminology and Definitions
91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
93 document are to be interpreted as described in [RFC2119] when
94 specified in their uppercase forms.
96 2.1. Internationalized Domain Names
98 MUST be as defined in
99 [I-D.mcpherson-sattler-registry-report-structure].
101 2.2. Dates and Times
103 MUST be as defined in
104 [I-D.mcpherson-sattler-registry-report-structure].
106 2.3. Character Encoding
108 MUST be as defined in
109 [I-D.mcpherson-sattler-registry-report-structure].
111 2.4. Currency
113 MUST be as defined in
114 [I-D.mcpherson-sattler-registry-report-structure].
116 3. Report Headings
118 The first row MUST be the column headings in the following order:
120 TLD It MUST contain the top-level domain name and
121 formatted according to section 2.1 of this
122 document.
124 DOMAIN It MUST contain the domain name formatted according
125 to section 2.1 of this document.
127 STATUS It MUST contain the status of the domain name. It
128 MUST either be 'REGISTRY REGISTERED', 'REGISTERED',
129 'AVAILABLE', 'REGISTRY RESERVED' or 'POLICY
130 RESERVED'.
132 DESCRIPTION It MUST contain the descriptive name of the premium
133 tier to which the domain is allocated.
135 CURRENCY It MUST contain the currency of the following fees
136 according to section 2.4 of this document.
138 CREATE It MUST contain the fee for a domain create.
140 RENEW It MUST contain the fee for a domain renew.
142 TRANSFER It MUST contain the fee for a domain transfer.
144 RESTORE It MUST contain the fee for a domain restore.
146 EFFECTIVE DATE It MUST contain the date and time the fee listed
147 will go into effect and formatted according to
148 section 2.2 of this document.
150 4. Fees
152 Fees MUST either be whole numbers or rounded to two decimal places.
153 A period (.) is used as the dividing point.
155 5. Examples
157 5.1. Single TLD File Example
159 This is an example of a domain fee report for a single top-level
160 domain .example with non-standard fees.
162 Filename: example_premium-domains_2018-11-01.csv.gz
164 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
165 EFFECTIVE DATE
166 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40,
167 2018-11-08T00:00:00Z
168 example,test2.example,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40,
169 2018-11-08T00:00:00Z
170 example,test3.example,AVAILABLE,B,USD,10000,10000,10000,40,
171 2018-12-01T00:00:00Z
172 example,xn--4gqvdy3r.example,AVAILABLE,A,USD,50,50,50,40,
173 2018-12-01T06:00:00Z
175 5.2. Multiple TLDs File Example
177 This is an example of a domain fee report for multiple top-level
178 domains from example registry with non-standard fees.
180 Filename: example-registry_premium-domains_2018-11.csv.gz
182 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
183 EFFECTIVE DATE
184 example1,test1.example1,REGISTRY RESERVED,A,USD,200,200,200,40,
185 2018-11-08T00:00:00Z
186 example2,test1.example2,POLICY RESERVED,DD,USD,75.50,75.50,75.50,40,
187 2018-11-08T00:00:00Z
188 example3,test2.example3,AVAILABLE,B,USD,10000,10000,10000,40,
189 2018-12-01T00:00:00Z
190 xn--zckzah,xn--r8jz45g.xn--zckzah,AVAILABLE,A,USD,50,50,50,40,
191 2018-12-01T06:00:00Z
193 5.3. Fee Change File Example
195 If the fee for a domain name is changing or moving to reserved or
196 unreserved in the future, there MUST be two entries for the name.
198 One entry for the current fee and status of the name, this entry MUST
199 be removed once the change takes place, and one entry for the future
200 fee of the name with its effective date.
202 Example of a file that contains a future fee change for a single top-
203 level domain .example.
205 Filename: example_premium-domains_2018-11-01.csv.gz
207 TLD,DOMAIN,STATUS,DESCRIPTION,CURRENCY,CREATE,RENEW,TRANSFER,RESTORE,
208 EFFECTIVE DATE
209 example,test1.example,REGISTRY RESERVED,A,USD,200,200,200,40,
210 2018-11-01T00:00:00Z
211 example,test1.example,REGISTRY RESERVED,DD,USD,75.50,75.50,75.50,40,
212 2018-12-01T00:00:00Z
214 6. IANA Considerations
216 This document has no IANA actions.
218 7. Security Considerations
220 The registry domain fee report described in this document does not
221 provide any security services.
223 8. Implementation Status
225 Note to RFC Editor: Please remove this section and the reference to
226 [RFC7942] before publication.
228 This section records the status of known implementations of the
229 protocol defined by this specification at the time of posting of this
230 Internet-Draft, and is based on a proposal described in [RFC7942].
231 The description of implementations in this section is intended to
232 assist the IETF in its decision processes in progressing drafts to
233 RFCs. Please note that the listing of any individual implementation
234 here does not imply endorsement by the IETF. Furthermore, no effort
235 has been spent to verify the information presented here that was
236 supplied by IETF contributors. This is not intended as, and must not
237 be construed to be, a catalog of available implementations or their
238 features. Readers are advised to note that other implementations may
239 exist.
241 According to [RFC7942], "this will allow reviewers and working groups
242 to assign due consideration to documents that have the benefit of
243 running code, which may serve as evidence of valuable experimentation
244 and feedback that have made the implemented protocols more mature. It
245 is up to the individual working groups to use this information as
246 they see fit".
248 Add implementation details once available.
250 9. References
252 9.1. Normative References
254 [I-D.mcpherson-sattler-registry-report-structure]
255 McPherson, N. and Sattler, T., "Registry Report Strucutre"
256 , (work in
258 progress), November 2018
260 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
261 Requirement Levels", BCP 14, RFC 2119, March 1997,
262 .
264 9.2. Informative References
266 [I-D.mcpherson-sattler-registry-reporting-repo]
267 McPherson, N. and Sattler, T., "Registry Reporting
268 Repository", (work in
270 progress), November 2018
272 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of
273 Running Code: The Implementation Status Section", RFC
274 7942, July 2016,
275 .
277 Appendix A. Change History
279 A.1. Change from 00 to 01
281 Fixed minor typos. Clarified example file name in section 5.3.
283 A.2. Change from 01 to 02
285 Clarified the Period. Fixed numerous typos.
287 Appendix B. Acknowledgements
289 The author wishes to thank the following persons for their feedback
290 and suggestions (sorted alphabetically by company):
292 o Neal McPherson, 1&1 IONOS
293 o James Galvin, Afilias
294 o Roger Carney, GoDaddy
296 Author's Address
298 Tobias Sattler
300 Email: tobias.sattler@me.com
301 URI: https://tobiassattler.com