Re: [netconf] WGLC for draft-ietf-netconf-notification-capabilities
Kent Watsen <kent+ietf@watsen.net> Mon, 30 September 2019 20:02 UTC
Return-Path: <0100016d83c486c9-83aece79-684a-4999-b382-dd9c09f24c62-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 54C6A12012C
for <netconf@ietfa.amsl.com>; Mon, 30 Sep 2019 13:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
header.d=amazonses.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id s99RSf5_yx-6 for <netconf@ietfa.amsl.com>;
Mon, 30 Sep 2019 13:02:39 -0700 (PDT)
Received: from a8-96.smtp-out.amazonses.com (a8-96.smtp-out.amazonses.com
[54.240.8.96])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 980BE12008C
for <netconf@ietf.org>; Mon, 30 Sep 2019 13:02:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1569873758;
h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID;
bh=DUNyQgIBYTSkYnl2UshnU+eXIfIXiSO/xuwR+ZxTWqU=;
b=DiPMIWDePjf/1ghTLBDqblhFhy/NkevYBDw3uTEPYApvlf9RFgrQoxz6wnR/svWt
NP+63pOYmM4frW4lv/zjc/YxcjB3U7ozLvNjxWPr8Q6DVdXDH/snQMVtAgVLwathAb/
dcPC+DTn+XM7u+kjJrvWpQr+PFX2d4SA0wCnRnsE=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016d83c486c9-83aece79-684a-4999-b382-dd9c09f24c62-000000@email.amazonses.com>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_C6AEA442-CB56-4F4E-8EBE-5CB504FF6F0F"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 30 Sep 2019 20:02:38 +0000
In-Reply-To: <VI1PR0701MB22864F116F517E960EC32A0AF0810@VI1PR0701MB2286.eurprd07.prod.outlook.com>
Cc: "Eric Voit (evoit)" <evoit@cisco.com>,
Mahesh Jethanandani <mjethanandani@gmail.com>,
Alexander Clemm <ludwig@clemm.org>, Benoit Claise <bclaise@cisco.com>,
"netconf@ietf.org" <netconf@ietf.org>
To: =?utf-8?Q?Bal=C3=A1zs_Lengyel?=
<balazs.lengyel=40ericsson.com@dmarc.ietf.org>
References: <D3B39347-DFB7-4BEE-8B22-0EE07AEB1F5A@gmail.com>
<4F49DF08-B7FC-4EBD-9D6B-7BC329E50334@gmail.com>
<BN7PR11MB262749DCC86F32F725D1C67AA1840@BN7PR11MB2627.namprd11.prod.outlook.com>
<VI1PR0701MB22864F116F517E960EC32A0AF0810@VI1PR0701MB2286.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.09.30-54.240.8.96
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/e28I39HPdXIH1IjPSOHJxcmrD4w>
Subject: Re: [netconf] WGLC for draft-ietf-netconf-notification-capabilities
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>,
<mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>,
<mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Sep 2019 20:02:41 -0000
In reviewing the draft, I don't see where the file format is defined. I understand the module defining a 'container' for protocol-accessible nodes, but shouldn't it define an 'sx:structure' for the file format? I suggest moving the contents of the "datastore-subscription-capabilities" container to a 'grouping' and then have both the container and an 'sx:structure' use that grouping. On the below: > I suspect that you will need to do a security analysis per YANG object. This has been done the other YANG push family. > BALAZS: The full module is readOnly and not sensitive or private in any manner. The security text for the readOnly parts of YangPush is the exact same text: not very informative, but gives you the illusion of security awareness. > > I suspect that manipulating the reporting intervals could have some security implications. E.g., a hacker could push up the damping period or periodic interval to a level where the information they are changing then becomes invisible to a monitoring system. > BALAZS: The full YAM is read-only so manipulating the data is not a concern. The draft should say something like: 1. All protocol-accessible are read-only and cannot be modified. The nature of the read-only data is not deemed to be sensitive in a way necessitating access-control restrictions (e.g., NACM) beyond the client being authenticated. 2. When a file format, the protection afforded by a mutually authenticated transport protocol. Protection of the data must be performed manually, so as to ensure that the data is neither seen nor modified in transit. Reword as needed. Kent // contributor
- [netconf] WGLC for draft-ietf-netconf-notificatio… Mahesh Jethanandani
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Qin Wu
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Reshad Rahman (rrahman)
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Mahesh Jethanandani
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Eric Voit (evoit)
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Eric Voit (evoit)
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Rob Wilton (rwilton)
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Kent Watsen
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Mahesh Jethanandani
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Joe Clarke (jclarke)
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Mahesh Jethanandani
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Rob Wilton (rwilton)
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Kent Watsen
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Mahesh Jethanandani
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Kent Watsen
- Re: [netconf] WGLC for draft-ietf-netconf-notific… Balázs Lengyel