Re: [netconf] leafrefed data item in YANG Push

"Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com> Fri, 13 December 2019 19:20 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 F373C12011C for <netconf@ietfa.amsl.com>; Fri, 13 Dec 2019 11:20:21 -0800 (PST)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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 DB195t2NfCRc for <netconf@ietfa.amsl.com>; Fri, 13 Dec 2019 11:20:20 -0800 (PST)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-ve1eur02on0722.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe06::722]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE413120013 for <netconf@ietf.org>; Fri, 13 Dec 2019 11:20:19 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PmPhV0Ixn+3QCjaLz9Fhu0Ycq6+BSRLLVr07oPW5pjRVtHep25sNGKykmmyGpB8am5PDYxU3sw3mitETt1xuq91qbKmQYjdNpMJoM6cy06PSk1pAolOYWLTXkNE+euhPTGkD1wE8qBazxN/b0Q9atPTDIeGeHqM+MQfUaeOp3GOha8wSSFhFkISTjIdsa49taQYjEkSKAvfDyaxjbwG1VGKgkkD8AffaFwLZCBFwk65wj5MygGUwelnX8SEwfoyEWCffL29BCPQcpZ4i+U/rFDgcOZcSuWhDcvIgP9u8rMHOIlUNW/LOTf2JKjgwZnaRgE8ZgMR9uXuqwU9W06TKZQ==
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=UAhIkDUN470+dFN4ZDPP2f8uemRfXgHBzHyEhd5DOMk=; b=MJWyZ4FBjZS4xcWfFNC6bNbk6ax/q8tkD/FOrzpJtPLKkDAfjXl2dTWqjdJViuRR0hRNBEcnGZxQu4qyOLfskDF6kzeKpOzfF08PlgYOd7/GrF2j2Xc3woWhRbu43ZgieSm4GKGHe5T5xH7ZKlqhBhT8TPL6ku3fwa+hcHB7IDQcmNvCqngOi3htcJytL50I28JH27G6jFteSqoNmwix02U/5fUBEHTG5B7ikMt5Muh2KNji7kXQ9lhjmN65tEMBHSbpubpoEX7n+BcNxUU8oVA49QFB48kHwIgXo6/c7gAw1DNohUNO+ox3V8YwLYe1IIHBM1eBpKTGkRahsGb/CA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia.com; dmarc=pass action=none header.from=nokia.com; dkim=pass header.d=nokia.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com; s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UAhIkDUN470+dFN4ZDPP2f8uemRfXgHBzHyEhd5DOMk=; b=OVha134SheLSgvNwXRzLmapCQb5VnTaTcFJGvlPm3/hA862x5cVVbzNVQOhDaJ4w/O0FCeL1/n/Qt8wJNuhi7rLuoc74DRFo9ksYCpgv50Brh09MVVvSA3D/xjBIG9ID8FQZhZFpDi9OeO7D1FUkxpi5/5hCm/ABziR9I8s8Qd0=
Received: from VI1PR07MB3981.eurprd07.prod.outlook.com (52.134.29.24) by VI1PR07MB5069.eurprd07.prod.outlook.com (20.177.203.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.9; Fri, 13 Dec 2019 19:20:17 +0000
Received: from VI1PR07MB3981.eurprd07.prod.outlook.com ([fe80::f4ac:1bfd:a5a1:aadf]) by VI1PR07MB3981.eurprd07.prod.outlook.com ([fe80::f4ac:1bfd:a5a1:aadf%6]) with mapi id 15.20.2538.017; Fri, 13 Dec 2019 19:20:17 +0000
From: "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com>
To: Qin Wu <bill.wu@huawei.com>, "netconf@ietf.org" <netconf@ietf.org>
Thread-Topic: leafrefed data item in YANG Push
Thread-Index: AdWxao/3v1bQh2UwS9WylLxsfb909wAf2aEg
Date: Fri, 13 Dec 2019 19:20:17 +0000
Message-ID: <VI1PR07MB3981154AEA5CFBE7DA6DCBD29B540@VI1PR07MB3981.eurprd07.prod.outlook.com>
References: <B8F9A780D330094D99AF023C5877DABAA94F7D0F@dggeml511-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABAA94F7D0F@dggeml511-mbx.china.huawei.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.12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 15d0f04f-ba30-497e-6077-08d780017cb9
x-ms-traffictypediagnostic: VI1PR07MB5069:
x-microsoft-antispam-prvs: <VI1PR07MB5069FE685FBDD0242E6C65DB9B540@VI1PR07MB5069.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0250B840C1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(136003)(39860400002)(376002)(366004)(189003)(199004)(8936002)(186003)(9326002)(5660300002)(26005)(9686003)(81156014)(55016002)(8676002)(71200400001)(81166006)(86362001)(6506007)(110136005)(7696005)(52536014)(478600001)(316002)(64756008)(66556008)(66476007)(66446008)(53546011)(33656002)(2906002)(66946007)(76116006); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB5069; H:VI1PR07MB3981.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: rCFm/k5Buih0G6PvEL5mhT82VPpSxuIx0ZklNTvpq/Lzn6vT3vXfbEGRskQ8vm/p++OmYeHs/X2jvjrWu128nwv0C+cIXML4QEFyni3agZ6pWTSzq9lOfPLZDtUDymjio9adQw07MuHVAPpJIxshg0ZD8vWlaWsIAGUrH/McxuaZfsSLT2lPq3mektHvAeSdariAFfad7IHvDhJD7oAXaxuGaOtebwfHr1Zn6S70FmgtKxDo0JxaJXeWjJ5eI/g1qnxT84HiWtbCd7QcKP5hXkzNmnenDRTzF8dl0d9zaofwa70Mvd7JDYBJAIadOqihZL8aTXh8M/0na8mBGkOuEIdSQeuJ5LSLokZghYEbqCcLNZAKWSvHlBOvrNQsDkLipC//jFfNL0Km1Do9+x8qiJe296X3rCSXDP2y8+45m8WnizZTZTKTxVP1pbUksAAQ
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_VI1PR07MB3981154AEA5CFBE7DA6DCBD29B540VI1PR07MB3981eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 15d0f04f-ba30-497e-6077-08d780017cb9
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Dec 2019 19:20:17.1011 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: XrX0JZ9CWc8bbzvfM1vp5/6j7ld5TcS5AGtTo6bcMlICXQ5ArRi2WfSDDrItJZj7BpyZULUERMXHk+s8K/EGnw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5069
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/4PHiS7EYqehZOz3lIxFMaLZ6rAo>
Subject: Re: [netconf] leafrefed data item in YANG Push
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 19:20:22 -0000

Hi Qin,

For subscriptions, I don't think it matters if 2 leafs are associated with each other via a leafref.  When you subscribe to each of those leafs, it is just like subscribing to any other 2 leafs (that aren't associated with eachother).

About the 'dangling reference': that should be accepted into the running datastore. It would fail validation. So it can only exist in the candidate.

Jason

From: netconf <netconf-bounces@ietf.org>; On Behalf Of Qin Wu
Sent: Thursday, December 12, 2019 11:09 PM
To: netconf@ietf.org
Subject: [netconf] leafrefed data item in YANG Push

Hello:
Can I subscribe to specific data item that refer to data item in another YANG module with other data item in the same subscription?
Module bar {
import foo {prefix ex;}
     leaf cc{type int8;}
     leaf bb {
       type leafref {
         path "../ex:aa";
       }
     }
}

Module foo {
     leaf aa {
       type int8;
     }
}
In addition, If there is dangling reference, e.g., leaf bb refer to leaf aa which doesn't exist, how this failure is handled by the server
and exposed to the client?

-Qin