[Gen-art] Genart last call review of draft-ietf-regext-bundling-registration-09

Joel Halpern via Datatracker <noreply@ietf.org> Thu, 07 March 2019 23:33 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ABAC130F82; Thu, 7 Mar 2019 15:33:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: draft-ietf-regext-bundling-registration.all@ietf.org, ietf@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.93.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <155200161246.5468.7896585235201756105@ietfa.amsl.com>
Date: Thu, 07 Mar 2019 15:33:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6Je5QFSuE7EPHwne-mGt6BTPR3U>
Subject: [Gen-art] Genart last call review of draft-ietf-regext-bundling-registration-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Mar 2019 23:33:33 -0000

Reviewer: Joel Halpern
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-regext-bundling-registration-09
Reviewer: Joel Halpern
Review Date: 2019-03-07
IETF LC End Date: 2019-03-15
IESG Telechat date: Not scheduled for a telechat

Summary: This document is almost ready for publication as some form of RFC

Major issues:
    This document defines protocol extensions and mandatory procedures to go
    with them.  As such, it seems it is either Experimental or Proposed
    Standard, but not Informational.

Minor issues:
    Section 5 consists of a list of behavioral requirements that appear
    normative, but do not use RFC 2119 language.  If these are indeed normative
    behavioral requirements, the document should use RFC 2119 language to be
    clear.  (And therefore, should also include the text explaining and citing
    RFC 2119.)

   The description in 7.2.1 of the EPP <create> command seems lacking.  After
   saying that it needs an extension element, it says:
        The <extension> element SHOULD contain a child <b-dn:create> element
        that identifies the bundle namespace and the location of the bundle
        name schema.
It is unclear when it is reasonable to omit this <b-dn:create> element.  (We
normally include with "SHOULD" explanations of this sort.) It is unspecified
what format of the information in the <b-dn:create> element has.  I suspect
that it is assumed to be the same as some other piece of EPP information, but
it does not say so.  The only child element for <b-dn:create> given in the
schema is the <b-dn:rdn> which is neither a namespace identifier nor a location
of the bundle name schema.

    Again in 7.2.2 on the EPP <delete> command, when discussing the addition to
    the response, it is a SHOULD with no explanation of when it is okay to omit
    it.  The same applies to the 7.2.3 EPP <renew> command, the 7.2.4 EPP
    <transfer> command, and the 7.2.5 EPP <update> command.

Nits/editorial comments: