[regext] Opsdir last call review of draft-ietf-regext-unhandled-namespaces-07

Qin Wu via Datatracker <noreply@ietf.org> Sat, 06 February 2021 11:58 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 4301E3A1185; Sat, 6 Feb 2021 03:58:46 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Qin Wu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-regext-unhandled-namespaces.all@ietf.org, last-call@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161261272623.7409.2976861581090203237@ietfa.amsl.com>
Reply-To: Qin Wu <bill.wu@huawei.com>
Date: Sat, 06 Feb 2021 03:58:46 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/fUsfbDd_9oD0eqNyy30xGxXzPXI>
Subject: [regext] Opsdir last call review of draft-ietf-regext-unhandled-namespaces-07
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: Sat, 06 Feb 2021 11:58:46 -0000

Reviewer: Qin Wu
Review result: Has Issues

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

This document defines Extensible Provison Protocol (EPP) extension for
unhandled namespace information conveyed to the client. It allow the server
return unhandled namespace information that the client can process later. I
think this document is well documented, however I do have a few questions for
clarification. Major issue: Not found Minor issues: 1.Section 1: I am not sure
how unhandled namespace information exchanging between the client and the
service is compliant with the negotiated services defined in [RFC5730]. Why
error response is not best choice to return this unhandled namespace
information for later handling.

2. Section 3.1/Section 3.2
For Unhandled Object-Level Extension in section 3.1 and Unhandled
Command-Response Extension in section 3.2, I see Template unhandled namespace
response example for an unsupported command-response extension is same as
Template unhandled namespace response example for an unsupported object-level
extension, which make me confused, I am wondering how do we distinguish
Unhandled Object-Level Extension from Unhandled Command-Response Extension in
the XML snippet example. Can you clarify this?

3. When we say converting from an object response to a general EPP response by
the server, does it mean the [NAMESPACE-XML] variable should be replaced by the
object-level extension XML. Where these [NAMESPACE-XML] variable are stored in
the server? Do we need to maintain the mapping between [NAMESPACE-XML] variable
and object-level extension XML? Can you clarify this?