[6lo] Opsdir last call review of draft-ietf-6lo-plc-05

Dan Romascanu via Datatracker <noreply@ietf.org> Fri, 12 February 2021 10:01 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: 6lo@ietf.org
Delivered-To: 6lo@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B4763A14F1; Fri, 12 Feb 2021 02:01:08 -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: 6lo@ietf.org, draft-ietf-6lo-plc.all@ietf.org, last-call@ietf.org, dromasca@gmail.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.25.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <161312406846.4387.15224651257821067404@ietfa.amsl.com>
Reply-To: Dan Romascanu <dromasca@gmail.com>
Date: Fri, 12 Feb 2021 02:01:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/xzDiiUWAyMRJSa4-GxTKLqEPpO8>
Subject: [6lo] Opsdir last call review of draft-ietf-6lo-plc-05
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2021 10:01:09 -0000

Reviewer: Dan Romascanu
Review result: Has Issues

This document describes how IPv6 packets are transported over constrained Power
Line Communication (PLC) networks. It is a clear and well-written document and
its content is relevant for all operators that will have such networks under
their administration. I have however one concern that I would suggest the OPS
AD to clarify before approving this document. There is no mention in the
document of the operational and manageability aspects. How will these networks
be managed, monitored, troubleshooted?  Which existing OAM protocols and
procedures apply and will extensions be needed? Are there / will there be any
new new interface types ("ifType" values) required as per RFC 8892? Maybe other
documents exist in the IEEE or ITU-T that document these aspects - if so it
would be useful to reference them. If other documents are in planning in the
IETF on this respect - please clarify.