idnits 2.17.1 draft-sattler-unavailable-domain-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 (January 29, 2019) is 1914 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: July 28, 2019 GoDaddy Inc. 5 January 29, 2019 7 Unavailable Domain Report 8 draft-sattler-unavailable-domain-report-01 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 July 28, 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 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5 69 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 71 1. Introduction 73 Modern top-level domain registries provide a number of detailed 74 reports and documents that their registrars require on a daily, 75 weekly and monthly basis. These most commonly include transaction 76 reports, as well as lists containing currently unavailable domains 77 and current premium domain fees. These reports are critical for 78 registrars' businesses and play an important role in accounting and 79 operations processes as well as in sales and marketing activities. 80 In the current set-up registrars must download these reports from 81 each registry's intranet in a different manner according to each 82 registry's own document management set up. 84 This document describes the content of an Unavailable Domain Report 85 based on the [I-D.mcpherson-sattler-report-structure] and delivered 86 by the [I-D.mcpherson-sattler-reporting-repository]. 88 2. Terminology and Definitions 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in [RFC2119] when 93 specified in their uppercase forms. 95 2.1. Internationalized Domain Names 97 MUST be as defined in 98 [I-D.mcpherson-sattler-report-structure]. 100 2.2. Dates and Times 102 MUST be as defined in 103 [I-D.mcpherson-sattler-report-structure]. 105 2.3. Character Encoding 107 MUST be as defined in 108 [I-D.mcpherson-sattler-report-structure]. 110 3. Report Headings 112 The first row MUST be the column headings in the following order: 114 TLD It MUST contain the top-level domain name and 115 formatted according to section 2.1 of this 116 document. 118 DOMAIN It MUST contain the domain name formatted according 119 to section 2.1 of this document. 121 STATUS It MUST contain the status of the domain name. It 122 MUST either be 'REGISTRY REGISTERED', 'REGISTERED', 123 'REGISTRY RESERVED' or 'POLICY RESERVED'. 125 4. Examples 127 4.1. Single TLD File Example 129 This is an example of a domain fee report for a single top-level 130 domain .example with non-standard fees. 132 Filename: example_unavailable-domains_2018-11-01.csv.gz 134 TLD,DOMAIN,STATUS 135 example,test1.example,REGISTRY RESERVED 136 example,test2.example,POLICY RESERVED 137 example,test3.example,REGISTERED 138 example,xn--4gqvdy3r.example,REGISTERED 140 4.2. Multiple TLDs File Example 142 This is an example of a domain fee report for multiple top-level 143 domains from example registry with non-standard fees. 145 Filename: example-registry_unavailable-domains_2018-11.csv.gz 147 TLD,DOMAIN,STATUS 148 example1,test1.example1,REGISTRY RESERVED 149 example2,test1.example2,POLICY RESERVED 150 example3,test2.example3,REGISTERED 151 xn--zckzah,xn--r8jz45g.xn--zckzah,POLICY RESERVED 153 5. IANA Considerations 155 This document has no IANA actions. 157 6. Security Considerations 159 The registry unavailable domain report described in this document 160 does not provide any security services. 162 7. Implementation Status 164 Note to RFC Editor: Please remove this section and the reference to 165 [RFC7942] before publication. 167 This section records the status of known implementations of the 168 protocol defined by this specification at the time of posting of this 169 Internet-Draft, and is based on a proposal described in [RFC7942]. 170 The description of implementations in this section is intended to 171 assist the IETF in its decision processes in progressing drafts to 172 RFCs. Please note that the listing of any individual implementation 173 here does not imply endorsement by the IETF. Furthermore, no effort 174 has been spent to verify the information presented here that was 175 supplied by IETF contributors. This is not intended as, and must not 176 be construed to be, a catalog of available implementations or their 177 features. Readers are advised to note that other implementations may 178 exist. 180 According to [RFC7942], "this will allow reviewers and working groups 181 to assign due consideration to documents that have the benefit of 182 running code, which may serve as evidence of valuable experimentation 183 and feedback that have made the implemented protocols more mature. It 184 is up to the individual working groups to use this information as 185 they see fit". 187 Add implementation details once available. 189 8. References 191 8.1. Normative References 193 [I-D.mcpherson-sattler-report-structure] 194 McPherson, N. and Sattler, T., "Report Strucutre", 195 (work in progress), January 2019 198 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 199 Requirement Levels", BCP 14, RFC 2119, March 1997, 200 . 202 8.2. Informative References 204 [I-D.mcpherson-sattler-reporting-repository] 205 McPherson, N. and Sattler, T., "Reporting Repository", 206 (work in progress), January 2019 209 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 210 Running Code: The Implementation Status Section", RFC 211 7942, July 2016, 212 . 214 Appendix A. Change History 216 A.1. Change from 00 to 01 218 Minor fixes 220 A.2. Change from 00 to UNAVBL 00 222 Changed draft name. Added Roger Carney as additional author. Added 223 acknowledgement. 225 A.3. Change from UNAVBL 00 to UNAVBL 01 227 Editorial changes. 229 Appendix B. Acknowledgements 231 The authors wish to thank the following persons for their feedback 232 and suggestions (sorted alphabetically by company): 234 o Neal McPherson, 1&1 IONOS 235 o James Galvin, Afilias 236 o Jody Kolker, GoDaddy 238 Authors' Addresses 240 Tobias Sattler 242 Email: tobias.sattler@me.com 243 URI: https://tobiassattler.com 245 Roger Carney 246 GoDaddy Inc. 247 14455 N. Hayden Rd. #219 248 Scottsdale, AZ 85260 249 US 251 Email: rcarney@godaddy.com 252 URI: http://www.godaddy.com