Report Structure
draft-mcpherson-sattler-report-structure-00

Document Type Active Internet-Draft (individual)
Last updated 2019-01-29
Replaces draft-mcpherson-sattler-registry-report-structure
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
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

                             Report Structure
                draft-mcpherson-sattler-report-structure-00

Abstract
      
   This document describes the default Report Structure for Reports
   which can be provide via 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               Report Structure               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.  File Names  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  File Types  . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Delimiter . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Implementation Status . . . . . . . . . . . . . . . . . . . .   4
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change History . . . . . . . . . . . . . . . . . . .   5
     A.1.  Change from 00 to 01  . . . . . . . . . . . . . . . . . .   5
     A.2.  Change from 01 to 02  . . . . . . . . . . . . . . . . . .   5
     A.3.  Change from 02 to 03  . . . . . . . . . . . . . . . . . .   5
     A.4.  Change from 03 to 04  . . . . . . . . . . . . . . . . . .   6
     A.5.  Change from 04 to 05  . . . . . . . . . . . . . . . . . .   6
     A.6.  Change from 05 to 06  . . . . . . . . . . . . . . . . . .   6
     A.7.  Change from 06 to 07  . . . . . . . . . . . . . . . . . .   6
     A.8.  Change from 07 to REPORT 00 . . . . . . . . . . . . . . .   6
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

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 domains. 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 default Report Structure for Reports
   which can be provide via 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
Show full document text