[regext] Éric Vyncke's No Objection on draft-ietf-regext-dnrd-objects-mapping-09: (with COMMENT)

Éric Vyncke via Datatracker <noreply@ietf.org> Tue, 25 August 2020 18:50 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A13EB3A0826; Tue, 25 Aug 2020 11:50:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-regext-dnrd-objects-mapping@ietf.org, regext-chairs@ietf.org, regext@ietf.org, Scott Hollenbeck <shollenbeck@verisign.com>, shollenbeck@verisign.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <159838145911.3803.10916709398554015085@ietfa.amsl.com>
Date: Tue, 25 Aug 2020 11:50:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/3Acx5KHfeUdxZbx6A7zgoZHxIto>
Subject: [regext] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ie?= =?utf-8?q?tf-regext-dnrd-objects-mapping-09=3A_=28with_COMMENT=29?=
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Aug 2020 18:51:00 -0000

Éric Vyncke has entered the following ballot position for
draft-ietf-regext-dnrd-objects-mapping-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-regext-dnrd-objects-mapping/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put into this document. Due to my heavy workload, I did
not review in details the model itself.

Please find below a couple of non-blocking COMMENTs (a reply to  my COMMENTs
will be welcome).

I hope that this helps to improve the document,

Regards,

-éric

== COMMENTS ==

A generic question about the point (5) of the document shepherd write-up:
"The AD is asking for further review from the Internationalization
Directorate, specifically on Section 10, which RECOMMENDS UTF-8 but allows
UTF-16.  The working group cites RFC 5730, Section 5, and aligns with that.
The AD would prefer to deprecate UTF-16, and notes that RFC 5730, is now
well over 10 years old.  Other opinions will be useful."

Did the WG receive any other opinions ? It is not clear from the write-up.

-- Section 4.3 --
Just curious here, why are the ASCII code expressed as a 16-bit unit while
ASCII codes are 7-bit long ? E.g., '("+", ASCII value 0x002B)'

-- Section 4.4 --
Are you sure that CRC32 and SHA-256 belongs to a section named 'checksum' ?
Those 2 techniques are different than checksums and much stronger for integrity
checks. Suggest to renamed this section.

In addition, should the algorithm be identified ?

-- Section 4.5 --
RFC 4291 is about the addressing structure of IPv6 (i.e., semantic), please
replace this reference to RFC 5952 that is about how to write an IPv6 address
(i.e., syntax).

-- Section 4.6.1 --
Just curious again... why not using plain SQL data definition language 'create
table()' statements rather than using XML to describe relational tables? Of
course, the XML file contains other information than the SQL data definition
language but it is lacking some information from SQL.

Also, it seems that using XML rather than SQL forces the primary key and
foreign key to have the same name (e.g., <csvSample:fName/>)

-- Section 5.3.2.1.3 --
Should the postal ZIP code be included ?

== NITS ==

-- Section 5.1.1.1 --
Really cosmetic, but, having an expiration date in 2015 in the example in a
document published in 2020 ;-)