idnits 2.17.1
draft-sattler-registry-domain-drop-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 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 (November 29, 2018) is 1973 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: May 28, 2019 November 29, 2018
6 Registry Domain Drop Report
7 draft-sattler-registry-domain-drop-report-00
9 Abstract
11 This document describes the content of a domain drop list based on
12 the registry report structure and delivered by the registry 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 May 28, 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 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 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5
65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
67 1. Introduction
69 Modern top-level domain registries provide a number of detailed
70 reports and documents that their registrars require on a daily,
71 weekly and monthly basis. These most commonly include transaction
72 reports, as well as lists containing currently unavailable domains
73 and current premium domains. These reports are critical for
74 registrars' businesses and play an important role in accounting and
75 operations processes as well as in sales and marketing activities.
76 In the current set-up registrars must download these reports from
77 each registry's intranet in a different manner according to each
78 registry's own document management set up.
80 Some domain name registries provide a list containing the expired
81 domain names that will be deleted in the near future.
83 This document describes the content of a domain drop list based on
84 the [I-D.mcpherson-sattler-registry-report-structure] and delivered
85 by the [I-D.mcpherson-sattler-registry-reporting-repo].
87 2. Terminology and Definitions
89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
90 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
91 document are to be interpreted as described in [RFC2119] when
92 specified in their uppercase forms.
94 2.1. Internationalized Domain Names
96 MUST be as defined in
97 [I-D.mcpherson-sattler-registry-report-structure].
99 2.2. Dates and Times
101 MUST be as defined in
102 [I-D.mcpherson-sattler-registry-report-structure].
104 2.3. Character Encoding
106 MUST be as defined in
107 [I-D.mcpherson-sattler-registry-report-structure].
109 3. Report Headings
111 The first row MUST be the column headings in the following order:
113 TLD It MUST contain the top-level domain name and
114 formatted according to section 2.1 of this
115 document.
117 DOMAIN It MUST contain the domain name formatted according
118 to section 2.1 of this document.
120 EXPIRED It MUST contain the date and time when the domain
121 name expired formatted according to section 2.2 of
122 this document.
124 PURGED It MUST contain the date and time when the domain
125 name will be purged from the registry system
126 formatted according to section 2.2 of this
127 document.
129 4. Examples
131 4.1. Single TLD File Example
133 This is an example of a domain drop list for a single top-level
134 domain .example.
136 Filename: example_domain-drop-list_2018-11-01.csv.gz
138 TLD,DOMAIN,EXPIRED,PURGED
139 example,test1.example,2018-11-20T08:49:48Z,2018-11-25T08:49:48Z
140 example,test2.example,2018-11-20T08:49:50Z,2018-11-25T08:49:50Z
141 example,test3.example,2018-11-20T08:49:52Z,2018-11-25T08:49:52Z
142 example,xn--4gqvdy3r.example,2018-11-20T18:05:09Z,
143 2018-11-25T18:05:09Z
145 4.2. Multiple TLDs File Example
147 This is an example of a domain drop list for multiple top-level
148 domains from example registry.
150 Filename: example-registry_domain-drop-list_2018-11.csv.gz
151 TLD,DOMAIN,EXPIRED,PURGED
152 example1,test1.example1,2018-11-21T09:36:10Z,2018-11-26T09:36:10Z
153 example2,test1.example2,2018-11-21T09:36:11Z,2018-11-26T09:36:11Z
154 example3,test2.example3,2018-11-21T12:06:13Z,2018-11-26T12:06:13Z
155 xn--zckzah,xn--r8jz45g.xn--zckzah,2018-11-21T12:06:14Z,
156 2018-11-26T12:06:14Z
158 5. IANA Considerations
160 This document has no IANA actions.
162 6. Security Considerations
164 The registry domain inventory report described in this document do
165 not provide any security services.
167 7. Implementation Status
169 Note to RFC Editor: Please remove this section and the reference to
170 [RFC7942] before publication.
172 This section records the status of known implementations of the
173 protocol defined by this specification at the time of posting of this
174 Internet-Draft, and is based on a proposal described in [RFC7942].
175 The description of implementations in this section is intended to
176 assist the IETF in its decision processes in progressing drafts to
177 RFCs. Please note that the listing of any individual implementation
178 here does not imply endorsement by the IETF. Furthermore, no effort
179 has been spent to verify the information presented here that was
180 supplied by IETF contributors. This is not intended as, and must not
181 be construed to be, a catalog of available implementations or their
182 features. Readers are advised to note that other implementations may
183 exist.
185 According to [RFC7942], "this will allow reviewers and working groups
186 to assign due consideration to documents that have the benefit of
187 running code, which may serve as evidence of valuable experimentation
188 and feedback that have made the implemented protocols more mature. It
189 is up to the individual working groups to use this information as
190 they see fit".
192 Add implementation details once available.
194 8. References
196 8.1. Normative References
198 [I-D.mcpherson-sattler-registry-report-structure]
199 McPherson, N. and Sattler, T., "Registry Report Strucutre"
200 , (work in
202 progress), November 2018
204 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
205 Requirement Levels", BCP 14, RFC 2119, March 1997,
206 .
208 8.2. Informative References
210 [I-D.mcpherson-sattler-registry-reporting-repo]
211 McPherson, N. and Sattler, T., "Registry Reporting
212 Repository", (work in
214 progress), November 2018
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 Appendix B. Acknowledgements
225 The authors wish to thank the following persons for their feedback
226 and suggestions (sorted alphabetically by company):
228 Author's Address
230 Tobias Sattler
232 Email: tobias.sattler@me.com
233 URI: https://tobiassattler.com