Re: [netconf] Defaults and NP containers in YangPush

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 13 December 2019 11:04 UTC

Return-Path: <rwilton@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 DF4EE12009E for <netconf@ietfa.amsl.com>; Fri, 13 Dec 2019 03:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 header.b=j07IIilD; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=Z39lumZv
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 JNSl6mbwFrNn for <netconf@ietfa.amsl.com>; Fri, 13 Dec 2019 03:04:25 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C4B712007C for <netconf@ietf.org>; Fri, 13 Dec 2019 03:04:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3322; q=dns/txt; s=iport; t=1576235065; x=1577444665; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=/iY4t3SRm42Bz4JuKdsZTcOLIWigPIDPHO7Bv5xtcqY=; b=j07IIilDP3I7Ev04mcBeFxbMZEHF3njHJRDINp0ZOxWsFx6VPpqlv5r9 bXJpsDxB/foeQ/uijPxKuEJdg27tXYXR/rXWsC88D62bieyblhNU0jRTK AEFBMOUjM/PN6aLF6mIdGpIrp8z5G0p6Kgi56v8rjMIEPx0zzQyfG52se 0=;
IronPort-PHdr: 9a23:trhMIR8n9JsWff9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUERoMiMEYhQslVdSaCEnnK/jCZC0hF8MEX1hgrDm2
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DiAQDZbvNd/5hdJa1lGwEBAQEBAQEFAQEBEQEBAwMBAQGBfoFLUAVsWCAECyoKg3mDRgOLC4JfmAaCUgNUCQEBAQwBARgLCgIBAYN7RQIXgXckOBMCAw0BAQQBAQECAQUEbYU3DIVeAQEBAQMBARAREQwBASwLAQsEAgEIDgMEAQEBAgImAgICJQsVCAgBAQQBDQUIGoMBgkYDLgECDKIJAoE4iGF1gTKCfgEBBYUJGIIXAwaBDiiFHIZ8GoFBP4FYgh4uPoJkAQECgUsYgw4ygiyQLo8rjxoKgjCMV4k9mkGOS5o9AgQCBAUCDgEBBYFpIiqBLnAVO4JsUBEUig2DBYNzhRSFP3QBAYEmjWMBgQ8BAQ
X-IronPort-AV: E=Sophos;i="5.69,309,1571702400"; d="scan'208";a="686323316"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Dec 2019 11:04:23 +0000
Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id xBDB4N2c016982 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 13 Dec 2019 11:04:24 GMT
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Dec 2019 05:04:23 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Dec 2019 05:04:23 -0600
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 13 Dec 2019 05:04:23 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EfuAkCjKqtunGTjl1wU5I8k1TILslgXIRES441/mAJAxbj82h/OSWB73kxH7Armt6tAke3YJ3L88WrqQaLfiExbRo7rKrR/R1aHN0K09FAyQN+JWeM+vM1YyusaddySvlDXk9e05K6zwgGXV4s1mETb0H4UMQemR5mAIZQZsDyCDYlGfyA9OCoBNt4nGvsVQ1rmASP280KEWJ15kOVQ0sCDkkHqKnm5Ta2/g7Myzx3ESttbx9O1XkVa7WL0FjCP67H3Trzlwa0Ymkkt+D9LXVjDBCFpNTzBxCfhN0hdNJxDnRo/pnS+3Acta6kMScZeL4xVXd1kyUlq8MeKGbx+Yag==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/iY4t3SRm42Bz4JuKdsZTcOLIWigPIDPHO7Bv5xtcqY=; b=oJjBpVjuVmlCJBXUkHYYXa/bIjD5XQi0CA5nH4EeAIm//ubcCUxqi/ZCxvj//Xf2TAiK4uv2+XRs0uW1olvq09mxPIbv7VJNbkGJkdrXJ00PXrdi9qWAoKOKqzwaBYRg1iYqFq+IVqTmXlbm/GngOI4mB7g2Qpd4gCC3h929TH4f4Ow7LFLThy1ghcbpFvivoNT4vJvbwaQ1wIyXOUvzWcHSROEi+JQr7seMllQgf553a37KuSeoIDYgp/VRANnmFIPBzaZMTy2hYISZZczqkEt4M68kE+SCkka/rK7T3eyy12Lj9tQDzokXS8ZhcKmJvoqEJNCUtqBvpwxOqfjkoA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/iY4t3SRm42Bz4JuKdsZTcOLIWigPIDPHO7Bv5xtcqY=; b=Z39lumZvqkxGbAHOHhf+Jzj/Y7ISCjhsm/eGnL81oxAD3bitEUgF2xY72w9o9P3A4iushejMW6+BhEPiTv44Db/R0+meC+fGiOv2kXYrZc07pU951tD2IPqx2LE1eu+Sr6U1kyHzGeE8YwreqlB0bILr8PAeMkqwgNfhZNnwHt4=
Received: from MN2PR11MB4366.namprd11.prod.outlook.com (52.135.38.209) by MN2PR11MB3664.namprd11.prod.outlook.com (20.178.252.76) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2516.17; Fri, 13 Dec 2019 11:04:22 +0000
Received: from MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::8106:b538:2920:a44f]) by MN2PR11MB4366.namprd11.prod.outlook.com ([fe80::8106:b538:2920:a44f%5]) with mapi id 15.20.2538.017; Fri, 13 Dec 2019 11:04:22 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Martin Bjorklund <mbj@tail-f.com>, "balazs.lengyel=40ericsson.com@dmarc.ietf.org" <balazs.lengyel=40ericsson.com@dmarc.ietf.org>
CC: "netconf@ietf.org" <netconf@ietf.org>, "mark.hollmann@ericsson.com" <mark.hollmann@ericsson.com>
Thread-Topic: [netconf] Defaults and NP containers in YangPush
Thread-Index: AdWwKvL6aozHIMuqTaiIXpVkNDUIvAAny/CAADZogNA=
Date: Fri, 13 Dec 2019 11:04:21 +0000
Message-ID: <MN2PR11MB436633FB55726A8F3AC62BEFB5540@MN2PR11MB4366.namprd11.prod.outlook.com>
References: <VI1PR0702MB3680D83DEA1B90619678013DF05A0@VI1PR0702MB3680.eurprd07.prod.outlook.com> <20191212.095709.2123523251711416815.mbj@tail-f.com>
In-Reply-To: <20191212.095709.2123523251711416815.mbj@tail-f.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=rwilton@cisco.com;
x-originating-ip: [173.38.220.62]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0f244c1c-6039-4662-271c-08d77fbc3542
x-ms-traffictypediagnostic: MN2PR11MB3664:
x-microsoft-antispam-prvs: <MN2PR11MB3664B34683B29AEB21615181B5540@MN2PR11MB3664.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0250B840C1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(366004)(396003)(39860400002)(376002)(136003)(13464003)(189003)(199004)(76116006)(66446008)(8936002)(26005)(86362001)(66476007)(52536014)(81156014)(64756008)(66556008)(66946007)(8676002)(2906002)(5660300002)(33656002)(966005)(54906003)(81166006)(53546011)(186003)(71200400001)(66574012)(9686003)(478600001)(7696005)(55016002)(110136005)(316002)(6506007)(4326008); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3664; H:MN2PR11MB4366.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kmLSO61LCBS3Ib5lwpo/bpwyiAsEf9Qwklj9/PDcfeTKnnJK+B0r6xPLS6Ec0Tw9zLTGGXzv954y1+iMAnfHxCyl8TBDcGT6JyfBvtZStYLPdhWZNvq41bTS/gczIi59+6ReaWL0rLcuJX1DrdtD0p7LRkpAT4FruLLQbrK1FiZMlLZmR5DnVlfW2hOjL8arKMQXVl55taf3/gguFpvVks9Z8Y4pFxKvbQPT36aaXyoKf1xV2+iUE5B/cGDZ651vv5UWOponLxPtrlto8MIRRStbG0I9qdKD/2NIBXWTf1cobXdKKlgvrF7P+Z0pw2dVKEmTGOZesiXTy3M0+VblIHo8AC/EQDAW+o1Xg73oBr7sPA3mwGlECDpazFIE6I4l7FG8XmmdK8LJVXbh1zxQsR0V4tRjGuDrqfpU79J2cnlkpwyHBNwQCuHZDTR4vLvRVTtcIW3dpFsvbPqfm/9j9DyQ+Bp+vcrTIbys7lGLGf7aDJ7BabucF7Lx/o+G37O/tDF5UC6cnNQS8MqUBvqliXKnoEqMcbmcYYzzKIf35S0=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0f244c1c-6039-4662-271c-08d77fbc3542
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Dec 2019 11:04:21.9062 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: se9Sjcl4LdLGHys4HakB8fCS0st5QqIaa3h3QF9X0V3y2UhAyTHb/jw/wrDnOqwGSuyX2ESacn84fIEvRmkfWg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3664
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.20, xch-aln-010.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/URxpVwCtKWGeZ97G3KX4RJdY_m8>
Subject: Re: [netconf] Defaults and NP containers in YangPush
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, 13 Dec 2019 11:04:28 -0000

Hi Martin,

I've not thought deeply about this, but I also probably agree with you.

However, I'm not sure that your position is necessarily obvious.  Hence, it might be nice if this was formally specified somewhere.  I also think that the "with-defaults" behaviours shouldn't necessary apply the same way to all datastores.  E.g. a server might want to choose "explicit" mode for <running>, but perhaps "trim" or "report-all" for <intended>.

Maybe there should be a bis version of RFC 6243 ... covering datastores and YANG push.

Thanks,
Rob


-----Original Message-----
From: netconf <netconf-bounces@ietf.org> On Behalf Of Martin Bjorklund
Sent: 12 December 2019 08:57
To: balazs.lengyel=40ericsson.com@dmarc.ietf.org
Cc: netconf@ietf.org; mark.hollmann@ericsson.com
Subject: Re: [netconf] Defaults and NP containers in YangPush

Hi,


Balázs Lengyel <balazs.lengyel=40ericsson.com@dmarc.ietf.org> wrote:
> Hello,
> 
> If I have the data model
> 
>  
> 
> container cont1 {
> 
> presence “xx”;
> 
>   container cont2 {
> 
>     leaf leaf1 {
> 
>       type string;
> 
>       default ddd;
> 
> }}}
> 
>  
> 
> And I create cont1
> 
> *	should Yang-Push report cont2 or leaf1 as created?
> *	Is this affected by with-default ?

Great question!

I think it must be affected by the server's basic-mode for with-defaults.

My assumption is that we want the subscriber to be able to keep a copy of the data on the publisher, and we must allow different default handling strategies in this copy - i.e., allow different implementation strategies.

[Another way of viewing this is that if we pass the data in the notif back to the server in an edit-config, it should effectively be a no-op.]

So, a 'report-all' server will send 'leaf1' in the notif, but an 'explicit' or 'trim' server will not send it.

Here's another case.  After your operation above, suppose a client sets 'leaf1' to 'ddd'.  A 'trim' server will not include 'leaf1' in the notis, but an 'explicit' will include it.  (And a 'report-all'
server will not see a change at all, since 'leaf1' already had 'ddd').

This means that the subscriber may need to be aware of the server's basic-mode, in order to be able to correctly interpret the notifs.


/martin
_______________________________________________
netconf mailing list
netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf