IETF Logo Mail Archive

Re: [Netconf] yang push: push-change-update for leaf-lists

"Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com> Tue, 03 April 2018 13:25 UTC

Return-Path: <jason.sterne@nokia.com>
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 022C512E8E6 for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 06:25:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nokia.onmicrosoft.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 sxVZXv3-5GnV for <netconf@ietfa.amsl.com>; Tue, 3 Apr 2018 06:25:09 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10112.outbound.protection.outlook.com [40.107.1.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9FE912E8E8 for <netconf@ietf.org>; Tue, 3 Apr 2018 06:25:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=50LOFzG/XaRxor5BYVjse+PO2Klq0r/2BOgLpsacCj0=; b=g44rgC3QxnqJf53+yBWCblpNuKlIBXca9+TOG9VP+H5bAbI6torYYbzF012YYGMxkhMzL2x+QQfBJvFlejwDk8WcTIytjewImZCfnE6LSfkEJ/5Nv1wBEoPjgokr7JjCznd0p6XXwUFu0Vv4aTQ6nW1C8ztLJcvJfCgOCHOUewU=
Received: from AM3PR07MB1124.eurprd07.prod.outlook.com (10.163.187.158) by AM3PR07MB1154.eurprd07.prod.outlook.com (10.163.188.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.653.5; Tue, 3 Apr 2018 13:25:06 +0000
Received: from AM3PR07MB1124.eurprd07.prod.outlook.com ([fe80::c88d:cbe7:1cfc:7399]) by AM3PR07MB1124.eurprd07.prod.outlook.com ([fe80::c88d:cbe7:1cfc:7399%5]) with mapi id 15.20.0653.011; Tue, 3 Apr 2018 13:25:06 +0000
From: "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com>
To: "Eric Voit (evoit)" <evoit@cisco.com>, Alexander Clemm <alexander.clemm@huawei.com>
CC: "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: yang push: push-change-update for leaf-lists
Thread-Index: AdPHfSkN6uaNBRQGRWOKN13QYQvWBwA/Z2YAALT9geA=
Date: Tue, 03 Apr 2018 13:25:05 +0000
Message-ID: <AM3PR07MB1124E1BC8D79BF81829732439BA50@AM3PR07MB1124.eurprd07.prod.outlook.com>
References: <AM3PR07MB11245CC980B73FFD8DEE24289BA20@AM3PR07MB1124.eurprd07.prod.outlook.com> <1cb9b579b9ed48a9b082d97224c594d5@XCH-RTP-013.cisco.com>
In-Reply-To: <1cb9b579b9ed48a9b082d97224c594d5@XCH-RTP-013.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jason.sterne@nokia.com;
x-originating-ip: [135.245.20.30]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1154; 7:UkYz1MIcGAVYN6QZXaEvAB0W2smZ9T6G7u7kgZfxv2Fy39/AJpHlC82SyIZckUG+fy9/OPVuYDu60OeMpvH2Cm3lbj9zkvHZPlLbOtnBLaka2/URAwOrnH4oWvcxgFuvjhcuu/ZuKjdX9q+dyhztSW8XYL2R1YEikvVldDexmA8qrFQ7cwRJVeP0T59fMrRnNMX7Iw6rtD2jFOHTZoPhbbzNCw1tUbDeOEGLnW7WgdIy0Y7pTDyanGmlT2ViIPSz
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 59ad2d68-2a26-4ec8-4568-08d599665091
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7193020); SRVR:AM3PR07MB1154;
x-ms-traffictypediagnostic: AM3PR07MB1154:
x-microsoft-antispam-prvs: <AM3PR07MB1154844F48482E6AB65A39879BA50@AM3PR07MB1154.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(50582790962513)(82608151540597)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231221)(11241501184)(806099)(944501327)(52105095)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041310)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:AM3PR07MB1154; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1154;
x-forefront-prvs: 0631F0BC3D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(366004)(376002)(39380400002)(396003)(199004)(189003)(13464003)(4326008)(25786009)(86362001)(26005)(6246003)(53936002)(186003)(2906002)(14454004)(6436002)(11346002)(15650500001)(2900100001)(229853002)(5660300001)(6116002)(55016002)(9686003)(66066001)(3846002)(486005)(476003)(106356001)(8936002)(102836004)(99286004)(486005)(478600001)(81166006)(3660700001)(74316002)(68736007)(76176011)(7696005)(59450400001)(81156014)(110136005)(53546011)(6506007)(3280700002)(305945005)(97736004)(7736002)(8676002)(105586002)(5250100002)(316002)(446003)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR07MB1154; H:AM3PR07MB1124.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 33IsZkKW4xCBRM82CzxnTy8VsqJlErItGWb9yQm+T63aQaV9gYBtTIcemB2yrlEbHc30cuteZeGm+oHrTEkz7CuLL/VpZWK3SFBLRJZUDr3qaSMN4ZLjWBy0yi+mZp+WDGJxyNhboxdb+Hqnliov/CYowTfvVhXjLwHAou7QOetaBlf6w4MKbogxSwYY+RqJtxZ1+GXrqjM9RL3Ns0xXmLmd4r2CpjpwmmRUDNokU4XyJIocH8Tg5HeuzDyH6DOcKZeiFiZ7rb1DWd77glhKzwyxdi9OeiWax8Xpei6Jp+LBuTPlaecJI79uphV9a9RiW8vDsF5zh/vki31cZbK26vTK60bdfn4Xi2Qt8bOjW4tao0yU5mmvQs/lZy3ua3IFjg7KiYY+s45f0iHuSns61c4hlmgNTcynguaJDyZudczWrfhYDLJt6Jjhn4F99UAZ4nFkHUyxK15gaNMqmQ/EZg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 59ad2d68-2a26-4ec8-4568-08d599665091
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Apr 2018 13:25:05.9164 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1154
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/GtXhmFbNp7uVH4JPzE69EhlxmYo>
Subject: Re: [Netconf] yang push: push-change-update for leaf-lists
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing 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: Tue, 03 Apr 2018 13:25:11 -0000

Thanks Eric.

I assume that behavior (not sending test1 & test3) is generally true for YANG Patch (RFC8072) in general (even outside of this particular yang push application of yang patch).

Redundant operation indicators:

>     <operation>merge</operation>         <-----
>     <target>/foo-ns:foo</target>
>     <value>
>       <foo xmlns="urn:foo.com:foo"
>            nc:operation="merge"     <-------
>            yang:insert="after"
>            yang:value="test1">test2</foo>
>     </value>

Rgds,
Jason

> -----Original Message-----
> From: Eric Voit (evoit) [mailto:evoit@cisco.com]
> Sent: Friday, March 30, 2018 7:16 PM
> To: Sterne, Jason (Nokia - CA/Ottawa) <jason.sterne@nokia.com>;
> Alexander Clemm <alexander.clemm@huawei.com>
> Cc: netconf@ietf.org
> Subject: RE: yang push: push-change-update for leaf-lists
> 
> Hi Jason,
> 
> You are correct that test1 & test3 are not sent for the insert you describe
> below.
> 
> I am not exactly sure what you mean by "redundant operation indicators".
> Could you explain?
> 
> Eric
> 
> 
> -----------------------------
> From: Sterne, Jason, March 29, 2018 12:45 PM
> 
> Hi guys,
> 
> The yang push drafts reference the yang patch RFC for the format of a push-
> change-update (i.e. on-change).
> 
> If a user-ordered leaf-list (of strings) 'foo' (at the root) contains 2 entries
> 'test1' and 'test3', and a collector is subscribed to the configuration tree, and
> a client adds 'test2' to the leaf-list after 'test1', then I assume the push-
> change-update would contain just that one entry 'test2' right ?
> 
>     <operation>merge</operation>
>     <target>/foo-ns:foo</target>
>     <value>
>       <foo xmlns="urn:foo.com:foo"
>            nc:operation="merge"
>            yang:insert="after"
>            yang:value="test1">test2</foo>
>     </value>
> 
> From what I understand, the entire contents of the leaf-list (i.e. 'test1',
> 'test2' and 'test3' are *not* sent for an addition (or deletion) of a single
> entry.
> 
> As a secondary question/note -> don't we end up with redundant operation
> indicators (which could differ if an implementation had a bug) ?
> 
> Rgds,
> Jason

v2.23.0 | Report a Bug | By Email