Internet Engineering Task Force T. Sattler, Editor Internet-Draft Intended status: Best Current Practice Expires: March 25, 2020 September 26, 2019 Domain Drop List Report draft-sattler-domain-drop-list-report-02 Abstract This document describes the content of a Domain Drop List Report based on the Report Structure and delivered by the Reporting Repository. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress". This Internet-Draft will expire on March 25, 2020. Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Sattler Expires March 25, 2020 [Page 1]
Internet-Draft Domain Drop List Report September 2019 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Terminology and Definitions . . . . . . . . . . . . . . . . . 2 2.1. Internationalized Domain Names . . . . . . . . . . . . . 2 2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3 2.3. Character Encoding . . . . . . . . . . . . . . . . . . . 3 3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3 4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Single TLD File Example . . . . . . . . . . . . . . . . . 3 4.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 3 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 6. Security Considerations . . . . . . . . . . . . . . . . . . . 4 7. Implementation Status . . . . . . . . . . . . . . . . . . . . 4 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . 5 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 5 A.1. Change from 00 to DROPLIST 00 . . . . . . . . . . . . . . 5 A.2. Change from DROPLIST 00 to DROPLIST 01 . . . . . . . . . 5 A.3. Change from DROPLIST 01 to DROPLIST 02 . . . . . . . . . 5 Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction Modern top-level domain registries provide many detailed reports and documents that their registrars require on a daily, weekly and monthly basis. These most commonly include transaction reports, as well as lists containing currently unavailable domains and current premium domain fees. These reports are critical for registrars' businesses and play an important role in accounting and operations processes as well as in sales and marketing activities. In the current set-up, registrars must download these reports from each registry's intranet differently according to each registry's document management set up. Some domain name registries provide a list containing the expired domain names that will be deleted/purged shortly. This document describes the content of a Domain Drop List Report based on the [I-D.mcpherson-sattler-report-structure] and delivered by the [I-D.mcpherson-sattler-reporting-repository]. 2. Terminology and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] when specified in their uppercase forms. 2.1. Internationalized Domain Names MUST be as defined in [I-D.mcpherson-sattler-report-structure]. Sattler Expires March 25, 2020 [Page 2]
Internet-Draft Domain Drop List Report September 2019 2.2. Dates and Times MUST be as defined in [I-D.mcpherson-sattler-report-structure]. 2.3. Character Encoding MUST be as defined in [I-D.mcpherson-sattler-report-structure]. 3. Report Headings The first row MUST be the column headings in the following order: TLD It MUST contain the top-level domain name and formatted according to section 2.1 of this document. DOMAIN It MUST contain the domain name formatted according to section 2.1 of this document. EXPIRED It MUST contain the date and time when the domain name expired formatted according to section 2.2 of this document. PURGED It MUST contain the date and time when the domain name will be purged from the registry system formatted according to section 2.2 of this document. 4. Examples 4.1. Single TLD File Example This is an example of a domain drop list for a single top-level domain .example. Filename: example_domain-drop-list_2018-11-01.csv.gz TLD,DOMAIN,EXPIRED,PURGED example,test1.example,2018-11-20T08:49:48Z,2018-11-25T08:49:48Z example,test2.example,2018-11-20T08:49:50Z,2018-11-25T08:49:50Z example,test3.example,2018-11-20T08:49:52Z,2018-11-25T08:49:52Z example,xn--4gqvdy3r.example,2018-11-20T18:05:09Z, 2018-11-25T18:05:09Z 4.2. Multiple TLDs File Example This is an example of a domain drop list for multiple top-level domains from example-registry. Filename: example-registry_domain-drop-list_2018-11.csv.gz Sattler Expires March 25, 2020 [Page 3]
Internet-Draft Domain Drop List Report September 2019 TLD,DOMAIN,EXPIRED,PURGED example1,test1.example1,2018-11-21T09:36:10Z,2018-11-26T09:36:10Z example2,test1.example2,2018-11-21T09:36:11Z,2018-11-26T09:36:11Z example3,test2.example3,2018-11-21T12:06:13Z,2018-11-26T12:06:13Z xn--zckzah,xn--r8jz45g.xn--zckzah,2018-11-21T12:06:14Z, 2018-11-26T12:06:14Z 5. IANA Considerations This document has no IANA actions. 6. Security Considerations The domain drop report described in this document does not provide any security services. 7. Implementation Status Note to RFC Editor: Please remove this section and the reference to [RFC7942] before publication. This section records the status of known implementations of the protocol defined by this specification at the time of posting of this Internet-Draft, and is based on a proposal described in [RFC7942]. The description of implementations in this section is intended to assist the IETF in its decision processes in progressing drafts to RFCs. Please note that the listing of any individual implementation here does not imply endorsement by the IETF. Furthermore, no effort has been spent to verify the information presented here that was supplied by IETF contributors. This is not intended as, and must not be construed to be, a catalog of available implementations or their features. Readers are advised to note that other implementations may exist. According to [RFC7942], "this will allow reviewers and working groups to assign due consideration to documents that have the benefit of running code, which may serve as evidence of valuable experimentation and feedback that have made the implemented protocols more mature. It is up to the individual working groups to use this information as they see fit". Add implementation details once available. Sattler Expires March 25, 2020 [Page 4]
Internet-Draft Domain Drop List Report September 2019 8. References 8.1. Normative References [I-D.mcpherson-sattler-report-structure] McPherson, N. and Sattler, T., "Report Strucutre", <https://datatracker.ietf.org/doc/draft-mcpherson-sattler- report-structure/> (work in progress), January 2019 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>. 8.2. Informative References [I-D.mcpherson-sattler-reporting-repository] McPherson, N. and Sattler, T., "Reporting Repository", <https://datatracker.ietf.org/doc/draft-mcpherson-sattler- reporting-repository/> (work in progress), January 2019 [RFC7942] Sheffer, Y. and Farrel, A., "Improving Awareness of Running Code: The Implementation Status Section", RFC 7942, July 2016, <https://www.rfc-editor.org/info/rfc7942>. Appendix A. Change History A.1. Change from 00 to DROPLIST 00 Changed draft name. Editorial changes and minor fixes. A.2. Change from DROPLIST 00 to DROPLIST 01 Editorial changes. A.3. Change from DROPLIST 01 to DROPLIST 02 Editorial changes. Appendix B. Acknowledgements The author wishes to thank the following persons for their feedback and suggestions (sorted alphabetically by company): Author's Address Tobias Sattler Email: tobias.sattler@me.com URI: https://tobiassattler.com Sattler Expires March 25, 2020 [Page 5]