[netmod] Genart telechat review of draft-ietf-netmod-yang-data-ext-04

Brian Carpenter via Datatracker <noreply@ietf.org> Sat, 19 October 2019 22:44 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: netmod@ietf.org
Delivered-To: netmod@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C1BBC12008F; Sat, 19 Oct 2019 15:44:46 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter via Datatracker <noreply@ietf.org>
To: gen-art@ietf.org
Cc: netmod@ietf.org, draft-ietf-netmod-yang-data-ext.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.106.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Brian Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <157152508672.5327.14252287111930747824@ietfa.amsl.com>
Date: Sat, 19 Oct 2019 15:44:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/CxRf-mXx0V1_rfKN7CGnbcc05kI>
Subject: [netmod] Genart telechat review of draft-ietf-netmod-yang-data-ext-04
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Oct 2019 22:44:47 -0000

Reviewer: Brian Carpenter
Review result: Ready with Nits

Gen-ART Last Call & telechat review of draft-ietf-netmod-yang-data-ext-04

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

Document: draft-ietf-netmod-yang-data-ext-04.txt
Reviewer: Brian Carpenter
Review Date: 2019-10-20
IESG Telechat date: 2019-10-31

Summary: Ready with nits


This was accidentally put on the IESG agenda without an IETF Last Call,
so this review serves both purposes.

The draft seems very clear and I have no technical comments.


> Updates: 8340 (if approved)
> Intended status: Standards Track

RFC 8340 is a BCP, so can this really be Standards Track?
Shouldn't it also be BCP, extending BCP 215? It's tricky,
because it also effectively extends RFC 8040, which is
Standards Track rather than BCP. Sadly it doesn't seem that
a document can be both BCP and Standards Track.

Also, this draft says:

>   The "yang-data" extension from [RFC8040] has been copied here,
>   renamed to "structure", and updated to be more flexible.

That reads as if RFC 8040 is also updated, and it leaves the
status of "yang-data" unclear. Is it now deprecated? Perhaps the
sentence would be clearer like this:

  This document defines a new YANG extension statement called
  "structure", which is similar to but more flexible than the
  "yang-data" extension from [RFC8040].