idnits 2.17.1 draft-sattler-domain-inventory-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 1911 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: July 28, 2019 January 29, 2019 6 Domain Inventory Report 7 draft-sattler-domain-inventory-report-01 9 Abstract 11 This document describes the content of a Domain Inventory 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 July 28, 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 . . . . . . . . . . . . . 3 51 2.2. Character Encoding . . . . . . . . . . . . . . . . . . . 3 52 2.3. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3 53 3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3 54 4. Unique ID . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 5.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3 57 5.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 4 58 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 59 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 60 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 4 61 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 9.1. Normative References . . . . . . . . . . . . . . . . . . 5 63 9.2. Informative References . . . . . . . . . . . . . . . . . 5 64 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 5 65 A.1. Change from 00 to DOMAININV 00 . . . . . . . . . . . . . 5 66 A.2. Change from DOMAININV 00 to DOMAININV 01 . . . . . . . . 5 67 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5 68 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 70 1. Introduction 72 Modern top-level domain registries provide a number of detailed 73 reports and documents that their registrars require on a daily, 74 weekly and monthly basis. These most commonly include transaction 75 reports, as well as lists containing currently unavailable domains 76 and current premium domain fees. These reports are critical for 77 registrars' businesses and play an important role in accounting and 78 operations processes as well as in sales and marketing activities. 79 In the current set-up registrars must download these reports from 80 each registry's intranet in a different manner according to each 81 registry's own document management set up. 83 A domain inventory comparison between the domains that are on an 84 accreditation / account and the domains that a registrar / reseller 85 has in its system is therefore useful. 87 This document describes the content of a Domain Inventory Report 88 based on the [I-D.mcpherson-sattler-report-structure] and delivered 89 by the [I-D.mcpherson-sattler-reporting-repository]. 91 2. Terminology and Definitions 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in [RFC2119] when 96 specified in their uppercase forms. 98 2.1. Internationalized Domain Names 100 MUST be as defined in 101 [I-D.mcpherson-sattler-report-structure]. 103 2.2. Character Encoding 105 MUST be as defined in 106 [I-D.mcpherson-sattler-report-structure]. 108 2.3. Dates and Times 110 MUST be as defined in 111 [I-D.mcpherson-sattler-report-structure]. 113 3. Report Headings 115 The first row MUST be the column headings in the following order: 117 TLD It MUST contain the top-level domain name and 118 formatted according to section 2.1 of this 119 document. 121 DOMAIN It MUST contain the domain name formatted according 122 to section 2.1 of this document. 124 UPDATED It MUST contain the date and time of the most 125 recent domain-object modification. If the domain 126 object has never been modified, then the date and 127 time of domain-object creation has to be used. 128 Formatting in both cases according to section 2.3 129 of this document. 131 ID It MUST contain an unique ID according to section 4 132 of this document. 134 4. Unique ID 136 A unique ID MUST either be according the IANA registrar IDs 137 (https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml) 138 where applicable or another unique registrar or reseller ID MUST be 139 used. 141 5. Examples 143 5.1. Single TLD File Example 145 This is an example of a domain inventory report for a single 146 top-level domain .example. 148 Filename: example_domain-inventory_2018-11-01.csv.gz 149 TLD,DOMAIN,UPDATED,ID 150 example,test1.example,2018-12-30T07:00:00Z,1 151 example,test2.example,2018-12-30T09:00:15Z,1 152 example,test3.example,2018-12-31T09:03:22Z,1 153 example,xn--4gqvdy3r.example,2018-12-31T10:18:56Z,1 155 5.2. Multiple TLDs File Example 157 This is an example of a domain inventory report for multiple 158 top-level domains from example registry. 160 Filename: example-registry_domain-inventory_2018-11.csv.gz 162 TLD,DOMAIN,UPDATED,ID 163 example1,test1.example1,2018-12-30T07:00:00Z,1 164 example2,test1.example2,2018-12-30T09:00:15Z,1 165 example3,test2.example3,2018-12-31T09:03:22Z,1 166 xn--zckzah,xn--r8jz45g.xn--zckzah,2018-12-31T10:18:56Z,1 168 6. IANA Considerations 170 This document has no IANA actions. 172 7. Security Considerations 174 The Domain Inventory Report described in this document does not 175 provide any security services. 177 8. Implementation Status 179 Note to RFC Editor: Please remove this section and the reference to 180 [RFC7942] before publication. 182 This section records the status of known implementations of the 183 protocol defined by this specification at the time of posting of this 184 Internet-Draft, and is based on a proposal described in [RFC7942]. 185 The description of implementations in this section is intended to 186 assist the IETF in its decision processes in progressing drafts to 187 RFCs. Please note that the listing of any individual implementation 188 here does not imply endorsement by the IETF. Furthermore, no effort 189 has been spent to verify the information presented here that was 190 supplied by IETF contributors. This is not intended as, and must not 191 be construed to be, a catalog of available implementations or their 192 features. Readers are advised to note that other implementations may 193 exist. 195 According to [RFC7942], "this will allow reviewers and working groups 196 to assign due consideration to documents that have the benefit of 197 running code, which may serve as evidence of valuable experimentation 198 and feedback that have made the implemented protocols more mature. It 199 is up to the individual working groups to use this information as 200 they see fit". 202 Add implementation details once available. 204 9. References 206 9.1. Normative References 208 [I-D.mcpherson-sattler-report-structure] 209 McPherson, N. and Sattler, T., "Report Strucutre", 210 (work in progress), January 2019 213 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 214 Requirement Levels", BCP 14, RFC 2119, March 1997, 215 . 217 9.2. Informative References 219 [I-D.mcpherson-sattler-reporting-repository] 220 McPherson, N. and Sattler, T., "Reporting Repository", 221 (work in progress), January 2019 224 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 225 Running Code: The Implementation Status Section", RFC 226 7942, July 2016, 227 . 229 Appendix A. Change History 231 A.1. Change from 00 to DOMAININV 00 233 Changed draft name. Registrar ID renamed to Unique ID to make the 234 report available to resellers as well. 236 A.2. Change from DOMAININV 00 to DOMAININV 01 238 Editorial changes. Added column UPDATED. Clarified Unique ID. 240 Appendix B. Acknowledgements 242 The author wishes to thank the following persons for their feedback 243 and suggestions (sorted alphabetically by company): 245 o Neal McPherson, 1&1 IONOS 247 Author's Address 249 Tobias Sattler 251 Email: tobias.sattler@me.com 252 URI: https://tobiassattler.com