idnits 2.17.1 draft-sattler-domain-inventory-report-04.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 (October 15, 2019) is 1653 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: April 15, 2020 October 15, 2019 6 Domain Inventory Report 7 draft-sattler-domain-inventory-report-04 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 April 15, 2020. 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 8.1. united-domains Reselling . . . . . . . . . . . . . . . . 4 62 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 9.1. Normative References . . . . . . . . . . . . . . . . . . 5 64 9.2. Informative References . . . . . . . . . . . . . . . . . 5 65 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 6 66 A.1. Change from 00 to DOMAININV 00 . . . . . . . . . . . . . 6 67 A.2. Change from DOMAININV 00 to DOMAININV 01 . . . . . . . . 6 68 A.3. Change from DOMAININV 01 to DOMAININV 02 . . . . . . . . 6 69 A.4. Change from DOMAININV 02 to DOMAININV 03 . . . . . . . . 6 70 A.5. Change from DOMAININV 03 to DOMAININV 04 . . . . . . . . 6 71 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 6 72 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 74 1. Introduction 76 Modern top-level domain registries provide many detailed reports and 77 documents that their registrars require on a daily, weekly and 78 monthly basis. These most commonly include transaction reports, as 79 well as lists containing currently unavailable domains and current 80 premium domain fees. These reports are critical for registrars' 81 businesses and play an important role in accounting and operations 82 processes as well as in sales and marketing activities. In the 83 current set-up, registrars must download these reports from each 84 registry's intranet differently according to each registry's document 85 management set up. 87 A domain inventory comparison between the domains that are on an 88 accreditation/account and the domain names that a registrar/reseller 89 has in its system is therefore useful. 91 This document describes the content of a Domain Inventory Report 92 based on the [I-D.mcpherson-sattler-report-structure] and delivered 93 by the [I-D.mcpherson-sattler-reporting-repository]. 95 2. Terminology and Definitions 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in [RFC2119] when 100 specified in their uppercase forms. 102 2.1. Internationalized Domain Names 104 MUST be as defined in 105 [I-D.mcpherson-sattler-report-structure]. 107 2.2. Character Encoding 109 MUST be as defined in 110 [I-D.mcpherson-sattler-report-structure]. 112 2.3. Dates and Times 114 MUST be as defined in 115 [I-D.mcpherson-sattler-report-structure]. 117 3. Report Headings 119 The first row MUST be the column headings in the following order: 121 TLD It MUST contain the top-level domain name and 122 formatted according to section 2.1 of this 123 document. 125 DOMAIN It MUST contain the domain name formatted according 126 to section 2.1 of this document. 128 UPDATED It MUST contain the date and time of the most 129 recent domain-object modification. If the domain 130 object has never been modified, then the date and 131 time of domain-object creation have to be used. 132 Formatting in both cases according to section 2.3 133 of this document. 135 ID It MUST contain a unique ID according to section 4 136 of this document. 138 4. Unique ID 140 A unique ID MUST either be according to the IANA registrar IDs 141 (https://www.iana.org/assignments/registrar-ids/registrar-ids.xhtml) 142 where applicable or another unique registrar or reseller ID MUST be 143 used. 145 5. Examples 147 5.1. Single TLD File Example 149 This is an example of a domain inventory report for a single 150 top-level domain .example. 152 Filename: example_domain-inventory_2018-11-01.csv.gz 153 TLD,DOMAIN,UPDATED,ID 154 example,test1.example,2018-12-30T07:00:00Z,1 155 example,test2.example,2018-12-30T09:00:15Z,1 156 example,test3.example,2018-12-31T09:03:22Z,1 157 example,xn--4gqvdy3r.example,2018-12-31T10:18:56Z,1 159 5.2. Multiple TLDs File Example 161 This is an example of a domain inventory report for multiple 162 top-level domains from example registry. 164 Filename: example-registry_domain-inventory_2018-11.csv.gz 166 TLD,DOMAIN,UPDATED,ID 167 example1,test1.example1,2018-12-30T07:00:00Z,1 168 example2,test1.example2,2018-12-30T09:00:15Z,1 169 example3,test2.example3,2018-12-31T09:03:22Z,1 170 xn--zckzah,xn--r8jz45g.xn--zckzah,2018-12-31T10:18:56Z,1 172 6. IANA Considerations 174 This document has no IANA actions. 176 7. Security Considerations 178 The Domain Inventory Report described in this document does not 179 provide any security services. 181 8. Implementation Status 183 Note to RFC Editor: Please remove this section and the reference to 184 [RFC7942] before publication. 186 This section records the status of known implementations of the 187 protocol defined by this specification at the time of posting of this 188 Internet-Draft, and is based on a proposal described in [RFC7942]. 189 The description of implementations in this section is intended to 190 assist the IETF in its decision processes in progressing drafts to 191 RFCs. Please note that the listing of any individual implementation 192 here does not imply endorsement by the IETF. Furthermore, no effort 193 has been spent to verify the information presented here that was 194 supplied by IETF contributors. This is not intended as, and must not 195 be construed to be, a catalog of available implementations or their 196 features. Readers are advised to note that other implementations may 197 exist. 199 According to [RFC7942], "this will allow reviewers and working groups 200 to assign due consideration to documents that have the benefit of 201 running code, which may serve as evidence of valuable experimentation 202 and feedback that have made the implemented protocols more mature. It 203 is up to the individual working groups to use this information as 204 they see fit". 206 8.1. united-domains Reselling 208 Organization: united-domains Reselling GmbH 210 Name: Reseller Reporting System 212 Description: Domain Reseller Platform 214 Level of maturity: Deployed in production. 216 Version compatibility: Version DOMAININV 03 is implemented. 218 Coverage: All aspects of this document are implemented. 220 Licensing: Proprietary In-House software 222 Contact: Tim Ettel 224 URL: https://www.ud-reselling.com/en/ 226 9. References 228 9.1. Normative References 230 [I-D.mcpherson-sattler-report-structure] 231 McPherson, N. and Sattler, T., "Report Strucutre", 232 (work in progress), January 2019 235 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 236 Requirement Levels", BCP 14, RFC 2119, March 1997, 237 . 239 9.2. Informative References 241 [I-D.mcpherson-sattler-reporting-repository] 242 McPherson, N. and Sattler, T., "Reporting Repository", 243 (work in progress), January 2019 246 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 247 Running Code: The Implementation Status Section", RFC 248 7942, July 2016, 249 . 251 Appendix A. Change History 253 A.1. Change from 00 to DOMAININV 00 255 Changed draft name. Registrar ID renamed to Unique ID to make the 256 report available to resellers as well. 258 A.2. Change from DOMAININV 00 to DOMAININV 01 260 Editorial changes. Added column UPDATED. Clarified Unique ID. 262 A.3. Change from DOMAININV 01 to DOMAININV 02 264 Editorial changes. 266 A.4. Change from DOMAININV 02 to DOMAININV 03 268 Added implementation reference. Added acknowledgement. 270 A.5. Change from DOMAININV 03 to DOMAININV 04 272 Editorial changes. 274 Appendix B. Acknowledgements 276 The author wishes to thank the following persons for their feedback 277 and suggestions (sorted alphabetically by company): 279 o Neal McPherson, 1&1 IONOS 280 o Tim Ettel, united-domains 282 Author's Address 284 Tobias Sattler 286 Email: tobias.sattler@me.com 287 URI: https://tobiassattler.com