[Last-Call] Opsdir last call review of draft-ietf-homenet-naming-architecture-dhc-options-20

Al Morton via Datatracker <noreply@ietf.org> Wed, 28 September 2022 20:35 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 5ABBCC15DD74; Wed, 28 Sep 2022 13:35:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Al Morton via Datatracker <noreply@ietf.org>
To: ops-dir@ietf.org
Cc: draft-ietf-homenet-naming-architecture-dhc-options.all@ietf.org, homenet@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 8.17.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <166439733536.39868.17453929161853606828@ietfa.amsl.com>
Reply-To: Al Morton <acmorton@att.com>
Date: Wed, 28 Sep 2022 13:35:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/last-call/VbRNsnGwR7fsiF04PiQTiCIKdt0>
Subject: [Last-Call] Opsdir last call review of draft-ietf-homenet-naming-architecture-dhc-options-20
X-BeenThere: last-call@ietf.org
X-Mailman-Version: 2.1.39
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: Wed, 28 Sep 2022 20:35:35 -0000

Reviewer: Al Morton
Review result: Ready

>From the draft:
This document defines DHCPv6 options so an Homenet Naming Authority (HNA) can
automatically proceed to the appropriate configuration and outsource the
authoritative naming service for the home network. In most cases, the
outsourcing mechanism is transparent for the end user. The document describes
how a network can provision the HNA with a specific DOI. This could be
particularly useful for a DOI partly managed by an ISP, or to make home
networks resilient to HNA replacement. The ISP delegates an IP prefix to the
home network as well as the associated reverse zone. It appears that the
document accomplishes these goals (although I'm not an expert in homenet
topics). The Shepherd's form says that this and a companion draft are the last
items to complete before closing homenet (interest is waning). The protocol
details seem to be well-considered.

It appears that the Scenarios were moved to Appendices, rather than as
normative section and subsections:

 Appendix A. Scenarios and impact on the End User

    This *section* details various scenarios and discuss their impact on the
    end user. This section is not normative and limits the description of a
    limited scope of scenarios that are assumed to be representative. Many
    other scenarios may be derived from these.

s/section/Appendix/g   and other fixes.