[regext] Opsdir last call review of draft-ietf-regext-rdap-object-tag-03

Tim Chown <tim.chown@jisc.ac.uk> Sun, 15 July 2018 16:15 UTC

Return-Path: <tim.chown@jisc.ac.uk>
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 F3CFF130E9E; Sun, 15 Jul 2018 09:15:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Tim Chown <tim.chown@jisc.ac.uk>
To: ops-dir@ietf.org
Cc: draft-ietf-regext-rdap-object-tag.all@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.82.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <153167131093.21320.16840396606540719429@ietfa.amsl.com>
Date: Sun, 15 Jul 2018 09:15:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/NGeEvLDOwWhU6mAfzUfuJYakDZ4>
Subject: [regext] Opsdir last call review of draft-ietf-regext-rdap-object-tag-03
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.27
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: Sun, 15 Jul 2018 16:15:11 -0000

Reviewer: Tim Chown
Review result: Ready

Hi,

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 draft extends RFC 7484 to describe an operational (best) practice to allow
Registration Data Access Protocol (RDAP) identifiers to be structured such that
they can convey the authoritative server to use for additional RDAP queries.

The concept of the draft is described well including examples. Two early stage
implementations (Verisign Labs and OpenRDAP) are listed in the document.

The draft is Ready for publication.

One minor nit - the RFC 2119 text should probably be in its own section rather
than within the introduction.