IETF Logo Mail Archive

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

"Eric Voit (evoit)" <evoit@cisco.com> Fri, 30 March 2018 23:16 UTC

Return-Path: <evoit@cisco.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 2716B126DC2 for <netconf@ietfa.amsl.com>; Fri, 30 Mar 2018 16:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.512
X-Spam-Level:
X-Spam-Status: No, score=-14.512 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 p4CeLMYpVg12 for <netconf@ietfa.amsl.com>; Fri, 30 Mar 2018 16:16:08 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 089D91272E1 for <netconf@ietf.org>; Fri, 30 Mar 2018 16:16:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1403; q=dns/txt; s=iport; t=1522451768; x=1523661368; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=Uun/Rzsx/LSdupKzVkBC5nY1frbhySAhZUNlKpMqJv8=; b=bjaRmTJgW20BgfCqEm9JX4Ys83BZVIcO7ToqpaqasWTtv4nBXUpkgr85 nsyJAiVbegpCgFfUOEHrR03L0PJiESOXRlYx9kpWRvGv2n/t88VYDbB3/ 9pK5eDwZ/fv7sBUhiWvFbRpzV7f/4N/VoJ9YpPf3bRW8iLVNJ/hnvLPhS 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BkAgBNxL5a/5xdJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYNCgVAymFSBdIEPlEwLhQQChCUhNxUBAgEBAQEBAQJrKIUkAQEBAQMnUhACAQgVMTIlAQEEAQ0NhQWwFDOIQIIrh2GBVD+DXDSEOIYLAocihQKLFAgCjiSBN4sFhyaILgIREwGBJAEyIoFScBU6gkSQTI1+gS+BFwEB
X-IronPort-AV: E=Sophos;i="5.48,383,1517875200"; d="scan'208";a="91336137"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Mar 2018 23:16:07 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w2UNG6XA003896 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 30 Mar 2018 23:16:07 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 30 Mar 2018 19:16:06 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1320.000; Fri, 30 Mar 2018 19:16:06 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.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/Z2YA
Date: Fri, 30 Mar 2018 23:16:06 +0000
Message-ID: <1cb9b579b9ed48a9b082d97224c594d5@XCH-RTP-013.cisco.com>
References: <AM3PR07MB11245CC980B73FFD8DEE24289BA20@AM3PR07MB1124.eurprd07.prod.outlook.com>
In-Reply-To: <AM3PR07MB11245CC980B73FFD8DEE24289BA20@AM3PR07MB1124.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.155.64.46]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/kh8ktJBvWY9iYDVCqeZsO0Ej18M>
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: Fri, 30 Mar 2018 23:16:10 -0000

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