[netmod] Kathleen Moriarty's Discuss on draft-ietf-netmod-revised-datastores-09: (with DISCUSS)

Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com> Wed, 10 January 2018 19:21 UTC

Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
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 B5B1812DB6D; Wed, 10 Jan 2018 11:21:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-netmod-revised-datastores@ietf.org, Lou Berger <lberger@labn.net>, netmod-chairs@ietf.org, lberger@labn.net, netmod@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.68.3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151561207372.18313.8094240527199424975.idtracker@ietfa.amsl.com>
Date: Wed, 10 Jan 2018 11:21:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/Ar-Yb5DVTDaBK4ew5LhAtYl9Bqk>
Subject: [netmod] Kathleen Moriarty's Discuss on draft-ietf-netmod-revised-datastores-09: (with DISCUSS)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 10 Jan 2018 19:21:14 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-netmod-revised-datastores-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:



Thanks for your work on this draft.  I'm a little confused with some text in
the draft and have a few questions.

1. The introductions says,
"This architectural framework identifies a set of conceptual datastores but
   it does not mandate that all network management protocols expose all
   these conceptual datastores.  This architecture is agnostic with
   regard to the encoding used by network management protocols."

As such, the data stores could be exposed for some implementations, using
whatever network management protocol (likely NetCONF or RESTCONF).  If this is
the case, why doesn't at least some of the security considerations template
apply for at least secure transport?

2. Section 5.3.4 - Is there any integrity protection on the origin information?
 If not, can it be added or is there a good reason why it’s not possible?  I
realize these are conceptual models that may or may not be exposed, but if
exposed and used, wouldn’t some integrity protection on this be helpful?

Thanks in advance!