idnits 2.17.1 draft-sattler-unavailable-domain-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 (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 R. Carney 4 Expires: September 26, 2019 GoDaddy Inc. 5 March 27, 2019 7 Unavailable Domain Report 8 draft-sattler-unavailable-domain-report-02 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 September 26, 2019. 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 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 6 70 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 72 1. Introduction 74 Modern top-level domain registries provide many detailed reports and 75 documents that their registrars require on a daily, weekly and 76 monthly basis. These most commonly include transaction reports, as 77 well as lists containing currently unavailable domains and current 78 premium domain fees. These reports are critical for registrars' 79 businesses and play an important role in accounting and operations 80 processes as well as in sales and marketing activities. In the 81 current set-up, registrars must download these reports from each 82 registry's intranet differently according to each registry's document 83 management set up. 85 This document describes the content of an Unavailable Domain 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 STATUS It MUST contain the status of the domain name. It 123 MUST either be 'REGISTRY REGISTERED', 'REGISTERED', 124 'REGISTRY RESERVED' or 'POLICY RESERVED'. 126 4. Examples 128 4.1. Single TLD File Example 130 This is an example of a domain fee report for a single top-level 131 domain .example with non-standard fees. 133 Filename: example_unavailable-domains_2018-11-01.csv.gz 135 TLD,DOMAIN,STATUS 136 example,test1.example,REGISTRY RESERVED 137 example,test2.example,POLICY RESERVED 138 example,test3.example,REGISTERED 139 example,xn--4gqvdy3r.example,REGISTERED 141 4.2. Multiple TLDs File Example 143 This is an example of a domain fee report for multiple top-level 144 domains from example registry with non-standard fees. 146 Filename: example-registry_unavailable-domains_2018-11.csv.gz 148 TLD,DOMAIN,STATUS 149 example1,test1.example1,REGISTRY RESERVED 150 example2,test1.example2,POLICY RESERVED 151 example3,test2.example3,REGISTERED 152 xn--zckzah,xn--r8jz45g.xn--zckzah,POLICY RESERVED 154 5. IANA Considerations 156 This document has no IANA actions. 158 6. Security Considerations 160 The registry unavailable domain report described in this document 161 does not provide any security services. 163 7. Implementation Status 165 Note to RFC Editor: Please remove this section and the reference to 166 [RFC7942] before publication. 168 This section records the status of known implementations of the 169 protocol defined by this specification at the time of posting of this 170 Internet-Draft, and is based on a proposal described in [RFC7942]. 171 The description of implementations in this section is intended to 172 assist the IETF in its decision processes in progressing drafts to 173 RFCs. Please note that the listing of any individual implementation 174 here does not imply endorsement by the IETF. Furthermore, no effort 175 has been spent to verify the information presented here that was 176 supplied by IETF contributors. This is not intended as, and must not 177 be construed to be, a catalog of available implementations or their 178 features. Readers are advised to note that other implementations may 179 exist. 181 According to [RFC7942], "this will allow reviewers and working groups 182 to assign due consideration to documents that have the benefit of 183 running code, which may serve as evidence of valuable experimentation 184 and feedback that have made the implemented protocols more mature. It 185 is up to the individual working groups to use this information as 186 they see fit". 188 Add implementation details once available. 190 8. References 192 8.1. Normative References 194 [I-D.mcpherson-sattler-report-structure] 195 McPherson, N. and Sattler, T., "Report Strucutre", 196 (work in progress), January 2019 199 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 200 Requirement Levels", BCP 14, RFC 2119, March 1997, 201 . 203 8.2. Informative References 205 [I-D.mcpherson-sattler-reporting-repository] 206 McPherson, N. and Sattler, T., "Reporting Repository", 207 (work in progress), January 2019 210 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 211 Running Code: The Implementation Status Section", RFC 212 7942, July 2016, 213 . 215 Appendix A. Change History 217 A.1. Change from 00 to 01 219 Minor fixes 221 A.2. Change from 00 to UNAVBL 00 223 Changed draft name. Added Roger Carney as additional author. Added 224 acknowledgement. 226 A.3. Change from UNAVBL 00 to UNAVBL 01 228 Editorial changes. 230 A.4. Change from UNAVBL 01 to UNAVBL 02 232 Editorial changes. 234 Appendix B. Acknowledgements 236 The authors wish to thank the following persons for their feedback 237 and suggestions (sorted alphabetically by company): 239 o Neal McPherson, 1&1 IONOS 240 o James Galvin, Afilias 241 o Jody Kolker, GoDaddy 243 Authors' Addresses 245 Tobias Sattler 247 Email: tobias.sattler@me.com 248 URI: https://tobiassattler.com 250 Roger Carney 251 GoDaddy Inc. 252 14455 N. Hayden Rd. #219 253 Scottsdale, AZ 85260 254 US 256 Email: rcarney@godaddy.com 257 URI: http://www.godaddy.com