Re: [netconf] WGLC for draft-ietf-netconf-notification-capabilities

Kent Watsen <kent+ietf@watsen.net> Fri, 01 November 2019 15:37 UTC

Return-Path: <0100016e279d85c9-ed769315-a2e4-4553-8819-81297009f2af-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 0144F120227 for <netconf@ietfa.amsl.com>; Fri, 1 Nov 2019 08:37:52 -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 sXWed4vEe8ad for <netconf@ietfa.amsl.com>; Fri, 1 Nov 2019 08:37:50 -0700 (PDT)
Received: from a8-64.smtp-out.amazonses.com (a8-64.smtp-out.amazonses.com [54.240.8.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A48EF12016E for <netconf@ietf.org>; Fri, 1 Nov 2019 08:37:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1572622665; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID; bh=CVeX0CpJmqStOu6ZsP76qRQop3fL8XUTXp9gkOmjdmk=; b=gsORF4wUVFCzjRiXHMX1LtqAg+J0Y9pdDM6giVT3h6BGMn7au3UHguKYICgsfumv 7QJYXLfcd6eQDmxTD/a1gOW8Rw5vXTlZH9Cr7gWvcn7izQM3DXejb+A5+TYwpE6tTiC nPUwtuHVKnSIgYI8zDImHNs6uBwe2HpzjVraIKb8=
From: Kent Watsen <kent+ietf@watsen.net>
Message-ID: <0100016e279d85c9-ed769315-a2e4-4553-8819-81297009f2af-000000@email.amazonses.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B84CE54B-0F5B-41B8-B0CB-5615C8F05C35"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 1 Nov 2019 15:37:45 +0000
In-Reply-To: <VI1PR0701MB228663740326DD0F34863856F0940@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@ericsson.com>
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> <0100016d83c486c9-83aece79-684a-4999-b382-dd9c09f24c62-000000@email.amazonses.com> <VI1PR0701MB2286C0363CD0AA085F2B9CC1F09F0@VI1PR0701MB2286.eurprd07.prod.outlook.com> <0100016db140fe70-7564d937-87d1-450c-9267-2e1235e3fbb4-000000@email.amazonses.com> <VI1PR0701MB228663740326DD0F34863856F0940@VI1PR0701MB2286.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.11.01-54.240.8.64
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/PgbIAiQo5tO9pPFH6oLictN0Nxo>
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: Fri, 01 Nov 2019 15:37:52 -0000

Hi Balazs,

> Hello,
> I added  your comments to the upcoming next version of the draft.
> Regards Balazs

Your update missed a couple nits (see below).

Kent // contributor




> BALAZS2: OK,  Updated with first part, but Rob has asked for an extra sentence about the dangers of revealing read-only data, I added that too.
> “All protocol-accessible data are read-only and cannot be modified. 
>         The data in this module is not security sensitive.
>         Access control may be configured, to avoid exposing 
>         the read-only data.”
>  
> Okay.  s/protocol-accessible data/protocol-accessible data nodes/




> BALAZS2: Agreed. This is part of normal file handling, transport. So I reworded this to:
> “When that data is in file format, data should be protected against 
>         modification or unauthorized access using normal file handling and 
>         secure and mutually authenticated file transport mechanisms.”
>  
> Okay.  The end can be shortened, i.e., just "file handling mechanisms".




Kent