Re: [netmod] yang-data-ext issues

Andy Bierman <andy@yumaworks.com> Wed, 25 April 2018 15:04 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309DB124239 for <netmod@ietfa.amsl.com>; Wed, 25 Apr 2018 08:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 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_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 IzkT4Eo08uPA for <netmod@ietfa.amsl.com>; Wed, 25 Apr 2018 08:04:43 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AA03127286 for <netmod@ietf.org>; Wed, 25 Apr 2018 08:04:42 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id q5-v6so25940635lff.12 for <netmod@ietf.org>; Wed, 25 Apr 2018 08:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yRzhk0MRtZDCLIXdx0zJbQWRZoIlErpFcl1TZTb0aYg=; b=Af+hPHE+BV00l8d5Mnw0EQgp7/yYn01M+P4ksEzsxPi0YNBE/qVhtpUXJyNg3iaajM wpVExF6reSZaMwSrit9SELJ3IRuPLODDT3Swe1JItkoIYpKPbTD7OVt6PowxS0PXYUw1 k9jFO73CH0JsVaYGNPm5GmwQuzYJEDqaBB2WXA73M9nbDVehOtpqzoawkwl7kz8Vop7k qlzgViUurXAlbbrACKSWS16VNw24GMGOr0LD6tEFbrXK2Jc8pdHoTvBlAB8ULCkix9E6 26O0Ae/vixc2WNL9+3sBnirijXORZwexz1RyukuG72z8uk1JMis/QO22+nomng0ieE0P 0jAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yRzhk0MRtZDCLIXdx0zJbQWRZoIlErpFcl1TZTb0aYg=; b=FFz3q8VDXAoB6a4zG2DLKamRYhbhCFx0MkCCMkVRm9QROONqNq97E4DYMeWnp8nKiq JB/8C5w95SdlbRtQo8AOi43i8DHnznUx8XAArO86ihgOr/LNXpHUzcSzKKSabXV+VvU6 ux3nHLaP9v6EweSrSgb+GCCjNHkjdIKVrvRHWkvc6Poh5Ujgn0UgorSBAwSxwJnYS2qz mtjHMG47yjIkGJn6DcqvdaYTAJp+PdV9/tQJbY9VEBxwyPgpp/Rg0XQ6PFWVaJLiAY1X CSumXACMvvifwIP/lkdM9OO6CTLnXKZdtEpz+Evgerg6C5cpyXqnlQjKMGWUwB4bUzor 6dVQ==
X-Gm-Message-State: ALQs6tClHD+1n2/n4B/TAxZQnbbDRSU4KGStlpOrObDjTiEW37XoOWb1 TPOZb9D5EBOPeCVu1dsjZRKdYylOBrhnO7Kuo96xYw==
X-Google-Smtp-Source: AB8JxZrpwaaMNgDyXW7b1smFGiudtm2pzmCFxhM/jNWF41fxXVEvyTbB/qWTPxuxrnVi4dgHPaaLYFiHaZPr7pJZAhg=
X-Received: by 10.46.151.206 with SMTP id m14mr770456ljj.102.1524668680936; Wed, 25 Apr 2018 08:04:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:d8c6:0:0:0:0:0 with HTTP; Wed, 25 Apr 2018 08:04:39 -0700 (PDT)
In-Reply-To: <3f6631298f1f7e0c752d7300585962b04ddc49cc.camel@nic.cz>
References: <20180423165104.zi7g75tifhekmezh@elstar.local> <20180423.215110.441857992070858100.mbj@tail-f.com> <87wowwr826.fsf@nic.cz> <20180424.163601.648085760139600532.mbj@tail-f.com> <20180425135550.jwwbwtpofd7vz52z@elstar.local> <3f6631298f1f7e0c752d7300585962b04ddc49cc.camel@nic.cz>
From: Andy Bierman <andy@yumaworks.com>
Date: Wed, 25 Apr 2018 08:04:39 -0700
Message-ID: <CABCOCHT9RH5f+ryecVJvE-03__XmHR8CaamLUfEdy7bTa9aMsw@mail.gmail.com>
To: Ladislav Lhotka <lhotka@nic.cz>
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Martin Bjorklund <mbj@tail-f.com>, NetMod WG <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="883d24f22e1420e4ae056aad976d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/vOcDz0tf_DEkiEG0A5_sMKwtlUY>
Subject: Re: [netmod] yang-data-ext issues
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2018 15:04:46 -0000

On Wed, Apr 25, 2018 at 7:05 AM, Ladislav Lhotka <lhotka@nic.cz>; wrote:

> On Wed, 2018-04-25 at 15:55 +0200, Juergen Schoenwaelder wrote:
> > On Tue, Apr 24, 2018 at 04:36:01PM +0200, Martin Bjorklund wrote:
> > > Ladislav Lhotka <lhotka@nic.cz>; wrote:
> > > > Martin Bjorklund <mbj@tail-f.com>; writes:
> > > >
> > > > > Hi,
> > > > >
> > > > > I am not sure what this statement tells us re. the issue in this
> email
> > > > > thread.
> > > >
> > > > It tells us that, in my view, the approach taken in this document is
> a
> > > > bad idea.
> > >
> > > Do you mean that the WG shoud drop this document?  And people that
> > > need yang-data should continue to use the version in 8040?  Or that
> > > people that need yang-data do not have a valid use case and they
> > > should do something else?
> >
> > One option is that people use yang-data as defined in RFC 8040 until
>
> IMO, people should use plain YANG. With the new YANG library it will be
> possible
> to confine such non-NM schemas in a special datastore so that the intention
> should be clear and multi-module schemas with all the additional data
> (versions,
>  features, deviations) can be used.
>
>
I don't see how yang-data interferes with "plain YANG" at all.
It is for data that is not in scope for plain YANG.
A plain client can ignore yang-data and not affect and RPC, notification,
or data
definitions in plain YANG.



> Lada
>
>
Andy


> > there is a version of YANG that has a proper and complete integrated
> > solution. (If for example yang-data is used to declare error content
> > for RPCs, then more extensions are needed or a proper integration into
> > YANG. Is it really good to introduce augment-yang-data (instead of
> > making augment work with say 'data' in YANG 1.2)? And then we do
> > uses-yang-data etc.
> >
> > /js
> >
> --
> Ladislav Lhotka
> Head, CZ.NIC Labs
> PGP Key ID: 0xB8F92B08A9F76C67
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>