idnits 2.17.1 draft-sattler-domain-inventory-report-00.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 (December 28, 2018) is 1940 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: June 27, 2019 December 28, 2018 6 Domain Inventory Report 7 draft-sattler-domain-inventory-report-00 9 Abstract 11 This document describes the content of a domain inventory report 12 based on the registry report structure and delivered by the registry 13 reporting 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 June 27, 2019. 32 Copyright Notice 34 Copyright (c) 2018 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 . . . . . . . . . . . . . 2 51 2.2. Character Encoding . . . . . . . . . . . . . . . . . . . 3 52 3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3 53 4. Unique ID . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 5.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3 56 5.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 3 57 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 58 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 59 8. Implementation Status . . . . . . . . . . . . . . . . . . . . 4 60 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 9.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 9.2. Informative References . . . . . . . . . . . . . . . . . 5 63 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 5 64 A.1. Change from 00 to DOMAININV 00 . . . . . . . . . . . . . 5 65 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 68 1. Introduction 70 Modern top-level domain registries provide a number of detailed 71 reports and documents that their registrars require on a daily, 72 weekly and monthly basis. These most commonly include transaction 73 reports, as well as lists containing currently unavailable domains 74 and current premium domains. These reports are critical for 75 registrars' businesses and play an important role in accounting and 76 operations processes as well as in sales and marketing activities. 77 In the current set-up registrars must download these reports from 78 each registry's intranet in a different manner according to each 79 registry's own document management set up. 81 A domain inventory comparison between the domains that are on an 82 accreditation and the domains that a registrar has in its system 83 is therefore useful. 85 This document describes the content of a domain inventory report 86 based on the [I-D.mcpherson-sattler-registry-report-structure] and 87 delivered by the [I-D.mcpherson-sattler-registry-reporting-repo]. 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-registry-report-structure]. 101 2.2. Character Encoding 103 MUST be as defined in 104 [I-D.mcpherson-sattler-registry-report-structure]. 106 3. Report Headings 108 The first row MUST be the column headings in the following order: 110 TLD It MUST contain the top-level domain name and 111 formatted according to section 2.1 of this 112 document. 114 DOMAIN It MUST contain the domain name formatted according 115 to section 2.1 of this document. 117 ID It MUST contain an unique ID of the succesful 118 transaction according to section 4 of this 119 document. 121 4. Unique ID 123 A unique ID MUST be listed, with each transaction. Those IDs MUST be 124 according the IANA registrar IDs (https://www.iana.org/assignments/ 125 registrar-ids/registrar-ids.xhtml) where applicable, otherwise 126 another unique registrar or reseller ID MUST be used. 128 5. Examples 130 5.1. Single TLD File Example 132 This is an example of a domain inventory report for a single 133 top-level domain .example. 135 Filename: example_domain-inventory_2018-11-01.csv.gz 137 TLD,DOMAIN,ID 138 example,test1.example,1 139 example,test2.example,1 140 example,test3.example,1 141 example,xn--4gqvdy3r.example,1 143 5.2. Multiple TLDs File Example 145 This is an example of a domain inventory report for multiple 146 top-level domains from example registry. 148 Filename: example-registry_domain-inventory_2018-11.csv.gz 150 TLD,DOMAIN,ID 151 example1,test1.example1,1 152 example2,test1.example2,1 153 example3,test2.example3,1 154 xn--zckzah,xn--r8jz45g.xn--zckzah,1 156 6. IANA Considerations 158 This document has no IANA actions. 160 7. Security Considerations 162 The registry domain inventory report described in this document do 163 not provide any security services. 165 8. Implementation Status 167 Note to RFC Editor: Please remove this section and the reference to 168 [RFC7942] before publication. 170 This section records the status of known implementations of the 171 protocol defined by this specification at the time of posting of this 172 Internet-Draft, and is based on a proposal described in [RFC7942]. 173 The description of implementations in this section is intended to 174 assist the IETF in its decision processes in progressing drafts to 175 RFCs. Please note that the listing of any individual implementation 176 here does not imply endorsement by the IETF. Furthermore, no effort 177 has been spent to verify the information presented here that was 178 supplied by IETF contributors. This is not intended as, and must not 179 be construed to be, a catalog of available implementations or their 180 features. Readers are advised to note that other implementations may 181 exist. 183 According to [RFC7942], "this will allow reviewers and working groups 184 to assign due consideration to documents that have the benefit of 185 running code, which may serve as evidence of valuable experimentation 186 and feedback that have made the implemented protocols more mature. It 187 is up to the individual working groups to use this information as 188 they see fit". 190 Add implementation details once available. 192 9. References 194 9.1. Normative References 196 [I-D.mcpherson-sattler-registry-report-structure] 197 McPherson, N. and Sattler, T., "Registry Report Strucutre" 198 , (work in 200 progress), November 2018 202 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 203 Requirement Levels", BCP 14, RFC 2119, March 1997, 204 . 206 9.2. Informative References 208 [I-D.mcpherson-sattler-registry-reporting-repo] 209 McPherson, N. and Sattler, T., "Registry Reporting 210 Repository", (work in 212 progress), November 2018 214 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of 215 Running Code: The Implementation Status Section", RFC 216 7942, July 2016, 217 . 219 Appendix A. Change History 221 A.1. Change from 00 to DOMAININV 00 223 Changed draft name. Registrar ID renamed to Unique ID to make the 224 report available to resellers as well. 226 Appendix B. Acknowledgements 228 The author wishes to thank the following persons for their feedback 229 and suggestions (sorted alphabetically by company): 231 o Neal McPherson, 1&1 IONOS 233 Author's Address 235 Tobias Sattler 237 Email: tobias.sattler@me.com 238 URI: https://tobiassattler.com