[Last-Call] Opsdir last call review of draft-ietf-core-dev-urn-08

Dan Romascanu via Datatracker <noreply@ietf.org> Mon, 30 November 2020 09:01 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: last-call@ietf.org
Delivered-To: last-call@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3B1D3A116F; Mon, 30 Nov 2020 01:01:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dan Romascanu via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: last-call@ietf.org, core@ietf.org, draft-ietf-core-dev-urn.all@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160672688076.4884.18269575790406202908@ietfa.amsl.com>
Reply-To: Dan Romascanu <dromasca@gmail.com>
Date: Mon, 30 Nov 2020 01:01:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/jEIARJcc-AL4cogvynhOLX9jYVU>
Subject: [Last-Call] Opsdir last call review of draft-ietf-core-dev-urn-08
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.29
List-Id: IETF Last Calls <last-call.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/last-call>, <mailto:last-call-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/last-call/>
List-Post: <mailto:last-call@ietf.org>
List-Help: <mailto:last-call-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/last-call>, <mailto:last-call-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2020 09:01:21 -0000

Reviewer: Dan Romascanu
Review result: Ready

This informational document describes a new Uniform Resource Name (URN)
namespace for hardware device identifiers. URNs can be easily passed along in
an application that needs the information, as it fits in protocols mechanisms
that are designed to carry URNs. This URNs usage is  an alternative to
Universally Unique IDentifiers (UUIDs) for cases where it is important that the
identifiers are as simple as possible and where additional requirements on
stable storage, real-time clocks, and identifier length can be prohibitive.

The document is short and clear. There is no significant impact form an
operational or manageability point of view. It is useful for network operators
to read Section 4 (DEV URN Subtypes) which can provide useful information for
operational actions or troubleshooting.

This document is READY from an OPS-DIR perspective.