[regext] Murray Kucherawy's No Objection on draft-ietf-regext-rdap-sorting-and-paging-17: (with COMMENT)

Murray Kucherawy via Datatracker <noreply@ietf.org> Thu, 24 September 2020 07:57 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 877EF3A08EC; Thu, 24 Sep 2020 00:57:34 -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-rdap-sorting-and-paging@ietf.org, regext-chairs@ietf.org, regext@ietf.org, Tom Harrison <tomh@apnic.net>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Murray Kucherawy <superuser@gmail.com>
Message-ID: <160093425412.24146.10179577207442958709@ietfa.amsl.com>
Date: Thu, 24 Sep 2020 00:57:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/HIRKWEHWSEuTVyEilLZuGsfd5fU>
Subject: [regext] Murray Kucherawy's No Objection on draft-ietf-regext-rdap-sorting-and-paging-17: (with 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, 24 Sep 2020 07:57:35 -0000

Murray Kucherawy has entered the following ballot position for
draft-ietf-regext-rdap-sorting-and-paging-17: 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:


I support Roman's DISCUSS point about resolving the JSONPath reference.  I'm
working the chartering of the proposed "jsonpath" working group, so I'm happy
to contribute to resolving this.  And a "thank you" to the document shepherd
for including this in the writeup.  Another possible option is to cite
draft-goessner-dispatch-jsonpath, marking it as "work in progress", though I
think that's still tricky because we don't know for sure that changes produced
by the proposed working group will be fully backward-compatible with what this
document requires.

I also support Ben's DISCUSS point about multi-sorts.

Section 1:

A totally minor nit, but I think the reference to RFC 7230 should be up where
HTTP is first used.

Section 2.2:

The ABNF here reminds me that string literals in ABNF are case-insensitive (RFC
5234, Section 2.3).  Just wanted to check that "COUNT=fAlSe" is fine here, for