idnits 2.17.1
draft-sattler-domain-drop-list-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:
----------------------------------------------------------------------------
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 (March 27, 2019) is 1857 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: September 26, 2019 March 27, 2019
6 Domain Drop List Report
7 draft-sattler-domain-drop-list-report-01
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 September 26, 2019.
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 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5
67 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
69 1. Introduction
71 Modern top-level domain registries provide many detailed reports and
72 documents that their registrars require on a daily, weekly and
73 monthly basis. These most commonly include transaction reports, as
74 well as lists containing currently unavailable domains and current
75 premium domain fees. These reports are critical for registrars'
76 businesses and play an important role in accounting and operations
77 processes as well as in sales and marketing activities. In the
78 current set-up, registrars must download these reports from each
79 registry's intranet differently according to each registry's document
80 management set up.
82 Some domain name registries provide a list containing the expired
83 domain names that will be deleted/purged shortly.
85 This document describes the content of a Domain Drop List Report
86 based on the [I-D.mcpherson-sattler-report-structure] and delivered
87 by the [I-D.mcpherson-sattler-reporting-repository].
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-report-structure].
101 2.2. Dates and Times
103 MUST be as defined in
104 [I-D.mcpherson-sattler-report-structure].
106 2.3. Character Encoding
108 MUST be as defined in
109 [I-D.mcpherson-sattler-report-structure].
111 3. Report Headings
113 The first row MUST be the column headings in the following order:
115 TLD It MUST contain the top-level domain name and
116 formatted according to section 2.1 of this
117 document.
119 DOMAIN It MUST contain the domain name formatted according
120 to section 2.1 of this document.
122 EXPIRED It MUST contain the date and time when the domain
123 name expired formatted according to section 2.2 of
124 this document.
126 PURGED It MUST contain the date and time when the domain
127 name will be purged from the registry system
128 formatted according to section 2.2 of this
129 document.
131 4. Examples
133 4.1. Single TLD File Example
135 This is an example of a domain drop list for a single top-level
136 domain .example.
138 Filename: example_domain-drop-list_2018-11-01.csv.gz
140 TLD,DOMAIN,EXPIRED,PURGED
141 example,test1.example,2018-11-20T08:49:48Z,2018-11-25T08:49:48Z
142 example,test2.example,2018-11-20T08:49:50Z,2018-11-25T08:49:50Z
143 example,test3.example,2018-11-20T08:49:52Z,2018-11-25T08:49:52Z
144 example,xn--4gqvdy3r.example,2018-11-20T18:05:09Z,
145 2018-11-25T18:05:09Z
147 4.2. Multiple TLDs File Example
149 This is an example of a domain drop list for multiple top-level
150 domains from example-registry.
152 Filename: example-registry_domain-drop-list_2018-11.csv.gz
153 TLD,DOMAIN,EXPIRED,PURGED
154 example1,test1.example1,2018-11-21T09:36:10Z,2018-11-26T09:36:10Z
155 example2,test1.example2,2018-11-21T09:36:11Z,2018-11-26T09:36:11Z
156 example3,test2.example3,2018-11-21T12:06:13Z,2018-11-26T12:06:13Z
157 xn--zckzah,xn--r8jz45g.xn--zckzah,2018-11-21T12:06:14Z,
158 2018-11-26T12:06:14Z
160 5. IANA Considerations
162 This document has no IANA actions.
164 6. Security Considerations
166 The domain drop report described in this document does not provide
167 any security services.
169 7. Implementation Status
171 Note to RFC Editor: Please remove this section and the reference to
172 [RFC7942] before publication.
174 This section records the status of known implementations of the
175 protocol defined by this specification at the time of posting of this
176 Internet-Draft, and is based on a proposal described in [RFC7942].
177 The description of implementations in this section is intended to
178 assist the IETF in its decision processes in progressing drafts to
179 RFCs. Please note that the listing of any individual implementation
180 here does not imply endorsement by the IETF. Furthermore, no effort
181 has been spent to verify the information presented here that was
182 supplied by IETF contributors. This is not intended as, and must not
183 be construed to be, a catalog of available implementations or their
184 features. Readers are advised to note that other implementations may
185 exist.
187 According to [RFC7942], "this will allow reviewers and working groups
188 to assign due consideration to documents that have the benefit of
189 running code, which may serve as evidence of valuable experimentation
190 and feedback that have made the implemented protocols more mature. It
191 is up to the individual working groups to use this information as
192 they see fit".
194 Add implementation details once available.
196 8. References
198 8.1. Normative References
200 [I-D.mcpherson-sattler-report-structure]
201 McPherson, N. and Sattler, T., "Report Strucutre",
202 (work in progress), January 2019
205 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
206 Requirement Levels", BCP 14, RFC 2119, March 1997,
207 .
209 8.2. Informative References
211 [I-D.mcpherson-sattler-reporting-repository]
212 McPherson, N. and Sattler, T., "Reporting Repository",
213 (work in progress), January 2019
216 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of
217 Running Code: The Implementation Status Section", RFC
218 7942, July 2016,
219 .
221 Appendix A. Change History
223 A.1. Change from 00 to DROPLIST 00
225 Changed draft name. Editorial changes and minor fixes.
227 A.2. Change from DROPLIST 00 to DROPLIST 01
229 Editorial changes.
231 Appendix B. Acknowledgements
233 The author wishes to thank the following persons for their feedback
234 and suggestions (sorted alphabetically by company):
236 Author's Address
238 Tobias Sattler
240 Email: tobias.sattler@me.com
241 URI: https://tobiassattler.com