idnits 2.17.1
draft-sattler-domain-drop-list-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 2 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 1671 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: March 25, 2020 September 26, 2019
6 Domain Drop List Report
7 draft-sattler-domain-drop-list-report-02
9 Abstract
11 This document describes the content of a Domain Drop List Report
12 based on the Report Structure and delivered by the Reporting
13 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 March 25, 2020.
32 Copyright Notice
34 Copyright (c) 2019 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 3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3
54 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3
55 4.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3
56 4.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 3
57 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
58 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
59 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 4
60 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
61 8.1. Normative References . . . . . . . . . . . . . . . . . . 5
62 8.2. Informative References . . . . . . . . . . . . . . . . . 5
63 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 5
64 A.1. Change from 00 to DROPLIST 00 . . . . . . . . . . . . . . 5
65 A.2. Change from DROPLIST 00 to DROPLIST 01 . . . . . . . . . 5
66 A.3. Change from DROPLIST 01 to DROPLIST 02 . . . . . . . . . 5
67 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5
68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
70 1. Introduction
72 Modern top-level domain registries provide many detailed reports and
73 documents that their registrars require on a daily, weekly and
74 monthly basis. These most commonly include transaction reports, as
75 well as lists containing currently unavailable domains and current
76 premium domain fees. These reports are critical for registrars'
77 businesses and play an important role in accounting and operations
78 processes as well as in sales and marketing activities. In the
79 current set-up, registrars must download these reports from each
80 registry's intranet differently according to each registry's document
81 management set up.
83 Some domain name registries provide a list containing the expired
84 domain names that will be deleted/purged shortly.
86 This document describes the content of a Domain Drop List Report
87 based on the [I-D.mcpherson-sattler-report-structure] and delivered
88 by the [I-D.mcpherson-sattler-reporting-repository].
90 2. Terminology and Definitions
92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
93 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
94 document are to be interpreted as described in [RFC2119] when
95 specified in their uppercase forms.
97 2.1. Internationalized Domain Names
99 MUST be as defined in
100 [I-D.mcpherson-sattler-report-structure].
102 2.2. Dates and Times
104 MUST be as defined in
105 [I-D.mcpherson-sattler-report-structure].
107 2.3. Character Encoding
109 MUST be as defined in
110 [I-D.mcpherson-sattler-report-structure].
112 3. Report Headings
114 The first row MUST be the column headings in the following order:
116 TLD It MUST contain the top-level domain name and
117 formatted according to section 2.1 of this
118 document.
120 DOMAIN It MUST contain the domain name formatted according
121 to section 2.1 of this document.
123 EXPIRED It MUST contain the date and time when the domain
124 name expired formatted according to section 2.2 of
125 this document.
127 PURGED It MUST contain the date and time when the domain
128 name will be purged from the registry system
129 formatted according to section 2.2 of this
130 document.
132 4. Examples
134 4.1. Single TLD File Example
136 This is an example of a domain drop list for a single top-level
137 domain .example.
139 Filename: example_domain-drop-list_2018-11-01.csv.gz
141 TLD,DOMAIN,EXPIRED,PURGED
142 example,test1.example,2018-11-20T08:49:48Z,2018-11-25T08:49:48Z
143 example,test2.example,2018-11-20T08:49:50Z,2018-11-25T08:49:50Z
144 example,test3.example,2018-11-20T08:49:52Z,2018-11-25T08:49:52Z
145 example,xn--4gqvdy3r.example,2018-11-20T18:05:09Z,
146 2018-11-25T18:05:09Z
148 4.2. Multiple TLDs File Example
150 This is an example of a domain drop list for multiple top-level
151 domains from example-registry.
153 Filename: example-registry_domain-drop-list_2018-11.csv.gz
154 TLD,DOMAIN,EXPIRED,PURGED
155 example1,test1.example1,2018-11-21T09:36:10Z,2018-11-26T09:36:10Z
156 example2,test1.example2,2018-11-21T09:36:11Z,2018-11-26T09:36:11Z
157 example3,test2.example3,2018-11-21T12:06:13Z,2018-11-26T12:06:13Z
158 xn--zckzah,xn--r8jz45g.xn--zckzah,2018-11-21T12:06:14Z,
159 2018-11-26T12:06:14Z
161 5. IANA Considerations
163 This document has no IANA actions.
165 6. Security Considerations
167 The domain drop report described in this document does not provide
168 any security services.
170 7. Implementation Status
172 Note to RFC Editor: Please remove this section and the reference to
173 [RFC7942] before publication.
175 This section records the status of known implementations of the
176 protocol defined by this specification at the time of posting of this
177 Internet-Draft, and is based on a proposal described in [RFC7942].
178 The description of implementations in this section is intended to
179 assist the IETF in its decision processes in progressing drafts to
180 RFCs. Please note that the listing of any individual implementation
181 here does not imply endorsement by the IETF. Furthermore, no effort
182 has been spent to verify the information presented here that was
183 supplied by IETF contributors. This is not intended as, and must not
184 be construed to be, a catalog of available implementations or their
185 features. Readers are advised to note that other implementations may
186 exist.
188 According to [RFC7942], "this will allow reviewers and working groups
189 to assign due consideration to documents that have the benefit of
190 running code, which may serve as evidence of valuable experimentation
191 and feedback that have made the implemented protocols more mature. It
192 is up to the individual working groups to use this information as
193 they see fit".
195 Add implementation details once available.
197 8. References
199 8.1. Normative References
201 [I-D.mcpherson-sattler-report-structure]
202 McPherson, N. and Sattler, T., "Report Strucutre",
203 (work in progress), January 2019
206 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
207 Requirement Levels", BCP 14, RFC 2119, March 1997,
208 .
210 8.2. Informative References
212 [I-D.mcpherson-sattler-reporting-repository]
213 McPherson, N. and Sattler, T., "Reporting Repository",
214 (work in progress), January 2019
217 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of
218 Running Code: The Implementation Status Section", RFC
219 7942, July 2016,
220 .
222 Appendix A. Change History
224 A.1. Change from 00 to DROPLIST 00
226 Changed draft name. Editorial changes and minor fixes.
228 A.2. Change from DROPLIST 00 to DROPLIST 01
230 Editorial changes.
232 A.3. Change from DROPLIST 01 to DROPLIST 02
234 Editorial changes.
236 Appendix B. Acknowledgements
238 The author wishes to thank the following persons for their feedback
239 and suggestions (sorted alphabetically by company):
241 Author's Address
243 Tobias Sattler
245 Email: tobias.sattler@me.com
246 URI: https://tobiassattler.com