idnits 2.17.1
draft-sattler-unavailable-domain-report-03.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 1666 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: March 25, 2020 GoDaddy Inc.
5 September 26, 2019
7 Unavailable Domain Report
8 draft-sattler-unavailable-domain-report-03
10 Abstract
12 This document describes the content of an Unavailable Domain Report
13 based on the Report Structure and delivered by the Reporting
14 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 March 25, 2020.
33 Copyright Notice
35 Copyright (c) 2019 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 3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3
55 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3
56 4.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3
57 4.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 3
58 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
59 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4
60 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 4
61 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
62 8.1. Normative References . . . . . . . . . . . . . . . . . . 4
63 8.2. Informative References . . . . . . . . . . . . . . . . . 5
64 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 5
65 A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 5
66 A.2. Change from 00 to UNAVBL 00 . . . . . . . . . . . . . . . 5
67 A.3. Change from UNAVBL 00 to UNAVBL 01 . . . . . . . . . . . 5
68 A.4. Change from UNAVBL 01 to UNAVBL 02 . . . . . . . . . . . 5
69 A.5. Change from UNAVBL 02 to UNAVBL 03 . . . . . . . . . . . 5
70 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 6
71 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
73 1. Introduction
75 Modern top-level domain registries provide many detailed reports and
76 documents that their registrars require on a daily, weekly and
77 monthly basis. These most commonly include transaction reports, as
78 well as lists containing currently unavailable domains and current
79 premium domain fees. These reports are critical for registrars'
80 businesses and play an important role in accounting and operations
81 processes as well as in sales and marketing activities. In the
82 current set-up, registrars must download these reports from each
83 registry's intranet differently according to each registry's document
84 management set up.
86 This document describes the content of an Unavailable Domain 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 STATUS It MUST contain the status of the domain name. It
124 MUST either be 'REGISTRY REGISTERED', 'REGISTERED',
125 'REGISTRY RESERVED' or 'POLICY RESERVED'.
127 4. Examples
129 4.1. Single TLD File Example
131 This is an example of a domain fee report for a single top-level
132 domain .example with non-standard fees.
134 Filename: example_unavailable-domains_2018-11-01.csv.gz
136 TLD,DOMAIN,STATUS
137 example,test1.example,REGISTRY RESERVED
138 example,test2.example,POLICY RESERVED
139 example,test3.example,REGISTERED
140 example,xn--4gqvdy3r.example,REGISTERED
142 4.2. Multiple TLDs File Example
144 This is an example of a domain fee report for multiple top-level
145 domains from example registry with non-standard fees.
147 Filename: example-registry_unavailable-domains_2018-11.csv.gz
149 TLD,DOMAIN,STATUS
150 example1,test1.example1,REGISTRY RESERVED
151 example2,test1.example2,POLICY RESERVED
152 example3,test2.example3,REGISTERED
153 xn--zckzah,xn--r8jz45g.xn--zckzah,POLICY RESERVED
155 5. IANA Considerations
157 This document has no IANA actions.
159 6. Security Considerations
161 The registry unavailable domain report described in this document
162 does not provide any security services.
164 7. Implementation Status
166 Note to RFC Editor: Please remove this section and the reference to
167 [RFC7942] before publication.
169 This section records the status of known implementations of the
170 protocol defined by this specification at the time of posting of this
171 Internet-Draft, and is based on a proposal described in [RFC7942].
172 The description of implementations in this section is intended to
173 assist the IETF in its decision processes in progressing drafts to
174 RFCs. Please note that the listing of any individual implementation
175 here does not imply endorsement by the IETF. Furthermore, no effort
176 has been spent to verify the information presented here that was
177 supplied by IETF contributors. This is not intended as, and must not
178 be construed to be, a catalog of available implementations or their
179 features. Readers are advised to note that other implementations may
180 exist.
182 According to [RFC7942], "this will allow reviewers and working groups
183 to assign due consideration to documents that have the benefit of
184 running code, which may serve as evidence of valuable experimentation
185 and feedback that have made the implemented protocols more mature. It
186 is up to the individual working groups to use this information as
187 they see fit".
189 Add implementation details once available.
191 8. References
193 8.1. Normative References
195 [I-D.mcpherson-sattler-report-structure]
196 McPherson, N. and Sattler, T., "Report Strucutre",
197 (work in progress), January 2019
200 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
201 Requirement Levels", BCP 14, RFC 2119, March 1997,
202 .
204 8.2. Informative References
206 [I-D.mcpherson-sattler-reporting-repository]
207 McPherson, N. and Sattler, T., "Reporting Repository",
208 (work in progress), January 2019
211 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of
212 Running Code: The Implementation Status Section", RFC
213 7942, July 2016,
214 .
216 Appendix A. Change History
218 A.1. Change from 00 to 01
220 Minor fixes
222 A.2. Change from 00 to UNAVBL 00
224 Changed draft name. Added Roger Carney as additional author. Added
225 acknowledgement.
227 A.3. Change from UNAVBL 00 to UNAVBL 01
229 Editorial changes.
231 A.4. Change from UNAVBL 01 to UNAVBL 02
233 Editorial changes.
235 A.5. Change from UNAVBL 02 to UNAVBL 03
237 Editorial changes.
239 Appendix B. Acknowledgements
241 The authors wish to thank the following persons for their feedback
242 and suggestions (sorted alphabetically by company):
244 o Neal McPherson, 1&1 IONOS
245 o James Galvin, Afilias
246 o Jody Kolker, GoDaddy
248 Authors' Addresses
250 Tobias Sattler
252 Email: tobias.sattler@me.com
253 URI: https://tobiassattler.com
255 Roger Carney
256 GoDaddy Inc.
257 14455 N. Hayden Rd. #219
258 Scottsdale, AZ 85260
259 US
261 Email: rcarney@godaddy.com
262 URI: http://www.godaddy.com