Opsdir last call review of draft-arkko-trip-registry-update-00

Carlos Pignataro <cpignata@cisco.com> Mon, 03 December 2018 17:58 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38CF6124BE5; Mon, 3 Dec 2018 09:58:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carlos Pignataro <cpignata@cisco.com>
To: ops-dir@ietf.org
Cc: draft-arkko-trip-registry-update.all@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-arkko-trip-registry-update-00
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154385988812.4946.9954294611401947565@ietfa.amsl.com>
Date: Mon, 03 Dec 2018 09:58:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W0Kem0oF62Kk1SSbMrXa4EoOJIY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2018 17:58:08 -0000

Reviewer: Carlos Pignataro
Review result: Has Issues

In reviewing this document as part of the Ops Directorate, I wanted to raise a
couple of minor issues -- more than nits, less than issues.

First, this is a focused well-written document, and I've no concerns and no
operational or manageability issues.

Issues:
1. [RFC8126] is referenced but not cited.
2. The interesting thing here is that, while this document is updating the IANA
rules for a specific registration, RFC 8126 says:
 "However, requests must
   include a minimal amount of clerical information, such as a point of
   contact (including an email address, and sometimes a postal address)
   and a brief description of how the value will be used.  "

So the main question I have is: is there a need or desire to take a broader
position or a deeper fix?

I do not know the history that triggered the writing of this I-D -- but the
authors should discuss and introspect on whether those reasons apply more
broadly beyond these two registries.

Thanks,

Carlos.