Re: [regext] I-D Action: draft-ietf-regext-simple-registration-reporting-02.txt

Tobias Sattler <> Tue, 03 November 2020 13:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7702A3A0876 for <>; Tue, 3 Nov 2020 05:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Pkwy1dECUaS2 for <>; Tue, 3 Nov 2020 05:43:28 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B15F33A0A9B for <>; Tue, 3 Nov 2020 05:43:27 -0800 (PST)
From: Tobias Sattler <>
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=ud20150520; t=1604411006; bh=k0f/rpXZtkcwohhi1k+FG0Wt6u9zZ00ZVzOn9zeKqFc=; h=From:Subject:Date:References:To:In-Reply-To; b=SKoNKH1vkN9OkunKFEXMpdyddU98ql9eaur7spOTWHUUKfHrNGfXlv6dvwzqM+O1E BTya71Ii0lAH2P0PErHbPDgo4mo1UCn2GWpNBFYQHqK9KSLyhxMe40G+nb/6hC8baD 6S+RYbmH0X9nYomnSJQreQtcE4xnx7XaLWWiyZBhikAn/mc0VqgB/pZnwNV1UiE87W +zjpvvcBIRsEvGKrcfBJZyuaiR9ajBoYpy9DhO/nlI5ZIZotpXvudM27vEDRveTLS3 LQB7CUHnqHoKrP9qfB77jrQj2KtNF6SIQ5S2LAjagYsb2DdHTfmxw0I4Rk6l6Ydfx3 QS0slHY77NWvQ==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Tue, 03 Nov 2020 14:43:24 +0100
References: <>
To: regext <>
In-Reply-To: <>
Message-Id: <>
X-Mailer: Apple Mail (2.3608.
Authentication-Results:; auth=pass smtp.auth=sattler
Archived-At: <>
Subject: Re: [regext] I-D Action: draft-ietf-regext-simple-registration-reporting-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 03 Nov 2020 13:43:31 -0000

Hi Joseph,
Hi Jim,

Thanks for updating this draft.

Some thoughts and comments from my side:

General thoughts
This document is intended to be informational. Therefore, I think it is better to avoid the word “standard” in the text. Because it would seem to be a de facto standard. I think that someone might be irritated by this later.

I would open it up and write about Registries, Registrars, and Resellers.

1. Introduction
I would define “the producer” and “the consumer” by using the example Registries and Registrars as well as Registrars and Resellers. And reference later on only to producer and consumer.

2. Data Element Specification
I am missing the character encoding. You are mentioning it in section 7. I would add a reference in section 2 to 7.

2.1.11 Registrar
If you open it up to Resellers, then I would rename it to Consumer.

2.2.5. Trade
I would add the field trade here, which is not uncommon in the ccTLD world. Just to have it right from the start.

2.4.1. Registrar_ID
If you open it up to Resellers, then I would rename it to Consumer_ID

3. Report Definition Specification
After reading it, it is not 100% clear to me, what the delimiter is and if the values should be enclosed with (single or double) quotes.

Appendix A. Acknowledgment
There is a typo in It is without a “s".


> On 2. Nov 2020, at 23:21, wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Registration Protocols Extensions WG of the IETF.
>        Title           : Simple Registration Reporting
>        Authors         : Joseph Yee
>                          James Galvin
> 	Filename        : draft-ietf-regext-simple-registration-reporting-02.txt
> 	Pages           : 33
> 	Date            : 2020-11-02
> Abstract:
>   Domain name registries and registrars report to each other by sharing
>   bulk information through files.  This document creates two IANA
>   registries to establish a standard reporting mechanism between domain
>   name registries and registrars.  The first IANA registry lists
>   standard data elements and their syntax for inclusion in the files.
>   The second IANA registry lists standard reports based on the standard
>   data elements.  Each report is a file formatted as a CSV file.  The
>   advantage of this reporting mechanism is that report, each file, can
>   be imported by recipients without any prior knowledge of their
>   contents, although reporting is enhanced with a minimum of knowledge
>   about the files.  The mechanism for the transmission and reception of
>   the files is a matter of local policy.
> The IETF datatracker status page for this draft is:
> There is also an HTML version available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> regext mailing list