[Iot-directorate] Iotdir last call review of draft-rosen-rfcefdp-update-2026-01

Ines Robles via Datatracker <noreply@ietf.org> Fri, 11 February 2022 14:44 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: iot-directorate@ietf.org
Delivered-To: iot-directorate@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 60C2A3A10DF; Fri, 11 Feb 2022 06:44:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ines Robles via Datatracker <noreply@ietf.org>
To: iot-directorate@ietf.org
Cc: draft-rosen-rfcefdp-update-2026.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164459065724.31789.8214749119811254406@ietfa.amsl.com>
Reply-To: Ines Robles <mariainesrobles@googlemail.com>
Date: Fri, 11 Feb 2022 06:44:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-directorate/lg3lG49ou_0OqIwOl-bwx8Y73WA>
Subject: [Iot-directorate] Iotdir last call review of draft-rosen-rfcefdp-update-2026-01
X-BeenThere: iot-directorate@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Mailing list for the IoT Directorate Members <iot-directorate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-directorate/>
List-Post: <mailto:iot-directorate@ietf.org>
List-Help: <mailto:iot-directorate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-directorate>, <mailto:iot-directorate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Feb 2022 14:44:18 -0000

Reviewer: Ines Robles
Review result: Ready with Nits

Document: draft-rosen-rfcefdp-update-2026-01
Reviewer: Ines Robles
Date: 11-02-2022

Summary:

The document does not include technical details or major issues.

Minor suggestion for a better understanding:

""In [reference], the responsibility for the RFC series is moved to the RFC
Series Working Group [reference if applicable] and to the RFC Series Approval
Board [reference if applicable].

The RFC publication is no longer the responsibility of the RFC Editor and the
role of the IAB in the RFC Series is altered.  Accordingly, in [reference], the
sentence "RFC publication is the direct responsibility of the RFC Editor, under
the general direction of the IAB" is deleted"".

Thanks for this document,

Ines