[regext] Opsdir last call review of draft-ietf-regext-org-11

Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de> Fri, 19 October 2018 08:26 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 87CC6130E51; Fri, 19 Oct 2018 01:26:38 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de>
To: ops-dir@ietf.org
Cc: draft-ietf-regext-org.all@ietf.org, ietf@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.87.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153993759849.31736.12600379615328737051@ietfa.amsl.com>
Date: Fri, 19 Oct 2018 01:26:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/01Q4m4qw8XgXvGEcxUs42JCkaNU>
Subject: [regext] Opsdir last call review of draft-ietf-regext-org-11
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: Fri, 19 Oct 2018 08:26:39 -0000

Reviewer: Jürgen Schönwälder
Review result: Has Nits

Thanks for a concise and well written document. I have not run tools
to validate the XSD and the XML artefacts but the definitions all look
reasonable.

Comment:

- What does the following mean in the definition of e164StringType?

        <attribute name="x" type="token" />

  It is indeed the intention to use "x"? What is the reason for having
  e164Type, why not use e164StringType?

Nits:

- What are "Organization transform commands"? This phrase appears
  several times in 3.4 an it seems this refers to what section 4.2
  describes later on. Well, if you read the document sequentially,
  things are a bit confusing. Perhaps define upfront what transform
  commands are? It might also be that EPP people are used to
  "transform commands" and this just shows my lack of familiarity with
  EPP.

- s/ement/element/

- s/Zero of more <org:status> element/Zero of more <org:status> elements/