Transaction Report
draft-mcpherson-sattler-transaction-report-00
Internet Engineering Task Force N. McPherson
Internet-Draft 1&1 IONOS SE
Intended status: Best Current Practice T. Sattler, Editor
Expires: July 28, 2019 January 29, 2019
Transaction Report
draft-mcpherson-sattler-transaction-report-00
Abstract
This document describes the content of a Transaction 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 July 28, 2019.
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.
McPherson & Sattler Expires July 28, 2019 [Page 1]
Internet-Draft Transaction Report January 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology and Definitions . . . . . . . . . . . . . . . . . 2
2.1. Internationalized Domain Names . . . . . . . . . . . . . 3
2.2. Dates and Times . . . . . . . . . . . . . . . . . . . . . 3
2.3. Character Encoding . . . . . . . . . . . . . . . . . . . 3
2.4. Currency . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Report Headings . . . . . . . . . . . . . . . . . . . . . . . 3
4. Transaction Types . . . . . . . . . . . . . . . . . . . . . . 4
4.1. Standard Transaction Types . . . . . . . . . . . . . . . 4
4.2. Non-Standard Transaction Types . . . . . . . . . . . . . 4
5. Transaction Periods . . . . . . . . . . . . . . . . . . . . . 5
6. Transaction Fees . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Deviating Fees . . . . . . . . . . . . . . . . . . . . . 5
7. Registrar ID . . . . . . . . . . . . . . . . . . . . . . . . 5
8. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Single TLD File Example . . . . . . . . . . . . . . . . . 5
8.2. Multiple TLDs File Example . . . . . . . . . . . . . . . 6
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
10. Security Considerations . . . . . . . . . . . . . . . . . . . 6
11. Implementation Status . . . . . . . . . . . . . . . . . . . . 6
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
12.1. Normative References . . . . . . . . . . . . . . . . . 7
12.2. Informative References . . . . . . . . . . . . . . . . 7
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 8
A.1. Change from 00 to 01 . . . . . . . . . . . . . . . . . . 8
A.2. Change from 01 to 02 . . . . . . . . . . . . . . . . . . 8
A.3. Change from 02 to TXN 00 . . . . . . . . . . . . . . . . 8
Appendix B. Acknowledgements . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
Modern top-level domain registries provide a number of 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 in a different manner according to each
registry's own document management set up.
This document describes the content of a Transaction Report based on
Show full document text