[regext] Murray Kucherawy's Discuss on draft-ietf-regext-data-escrow-07: (with DISCUSS and COMMENT)

Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 09 April 2020 03:08 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 E8F333A080C; Wed, 8 Apr 2020 20:08:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Murray Kucherawy via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-regext-data-escrow@ietf.org, regext-chairs@ietf.org, regext@ietf.org, James Gould <jgould@verisign.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.125.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <158640169839.8818.1279086565967125626@ietfa.amsl.com>
Date: Wed, 08 Apr 2020 20:08:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/x5SPewIwzRbnqtzGs9pXeM47TmI>
Subject: [regext] Murray Kucherawy's Discuss on draft-ietf-regext-data-escrow-07: (with DISCUSS and COMMENT)
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: Thu, 09 Apr 2020 03:08:19 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-regext-data-escrow-07: Discuss

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:


I had originally included these just as comments, but since another AD brought
up the same point I'd like to discuss them:

Section 5.1.3: "This element SHOULD be present in deposits of type Incremental
or Differential."  This makes it sound like a deposit of those two types not
using this element might be non-compliant.  I suggest instead "This element is
only used in Incremental and Differential deposits."  (Or instead of "used",
maybe "meaningful".)

Section 5.1.4: " It SHOULD be present in all type of deposits."  Same issue. 
Maybe "It is valid for use in all types of deposits."


Roman took many of my ideas, so I support his DISCUSS position and his comments.

Some of the BCP14 language in this document feels mushy.  "SHOULD/MUST take all
necessary precautions" isn't very precise, while normally
interoperability/normative language is supposed to be pretty crisp.

"gTLD" and "ccTLD" could stand to be included in the definitions section,
either by prose or by reference if there is one.

This may reveal a weak point in my understanding of XML, but Section 5.1 says
that the type of the deposit is FULL, INCR or DIFF.   Is this case-sensitive?

Section 5.1.1: Should "data-time" be "date-time"?

Section 5.1.2: About "version", although I think this is made explicit in the
XML schema in Section 6.1, I suggest a sentence be added making it clear that
this document specifies version "1.0".

Section 5.1.4, last paragraph: When would you not apply that SHOULD?  That
strikes me as MUST territory.