Re: [netmod] yang-data-ext issues

Andy Bierman <andy@yumaworks.com> Mon, 23 April 2018 19:58 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 B04E012D7E4 for <netmod@ietfa.amsl.com>; Mon, 23 Apr 2018 12:58:08 -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 FMWe22t8Hjud for <netmod@ietfa.amsl.com>; Mon, 23 Apr 2018 12:58:06 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 64682126B6E for <netmod@ietf.org>; Mon, 23 Apr 2018 12:58:06 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id y15-v6so8685255lfj.0 for <netmod@ietf.org>; Mon, 23 Apr 2018 12:58:06 -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=4H43MuOENaF8QMThU9AyxcZw6jywt1FSgGjAelml4dk=; b=bn8ia2yiAf4MRGx2WjR+JPPS7QxXPXliraX/qkj4FKCNmHEHI9q7o7/TYWwRM4v8BN 5tCkTz2VESJOfT60w1F46v+x//jphLffQZdL/sbNuG1h2tTiqiKV1Aa9kSn2p4eYts5p Nz42Q8RxBBAmDY0SnBNm+rpNYXTjaGGlE9mpt8VeyW3vMiLHWTYlRBe578aeJwgVnv/A 8LYXxWxVtS5gjF2mTVm5UTalAJjRDX4IMYeguwUMWt/42OndQnxQUIeCm5KTf53/A1B9 OT5V9uHtl5jr4XhS1CXPvUMe+LDV6rlI56THqm5FrFOe5PTAjNn5CmOU4GrzzcuoYPru zh6w==
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=4H43MuOENaF8QMThU9AyxcZw6jywt1FSgGjAelml4dk=; b=scZo3RhR7TWEPtLngSd9sInVVukYi6Ac8PXoN111VXn7zxvha7R25PLEFgNBAaBQRM GrUMDi1wHwlVyeBDi05yS6Cq9Oe9pjY0ep9PjqYK88nDc+rHLpNS7VMFyeCxfOzrpgx1 JbFbwBWI5IjJNHQQmcK8SHGznqZfkJqCtNM5/QiS2IazOQPEZtgNAmKAsQNt5BPL1o14 kRpUTBk1ub62Awcx/Rc3eaURKnj/f7b4rjE165VblrJU8SlFFt/zTT1X9hjgHIHBOgc0 Cm/Ibqn8VtxCoxGg1pcQDuiMJam/Men7fzeaNPVJ4Tcc7mACYeUnVqcM7vpcR9fjl72a 12hQ==
X-Gm-Message-State: ALQs6tBOxuQ6sY7BoGzw3W9pr9EZ6abGOwVLhyaU5GTQvvHYxhh0ekD6 znCAvhN2AK1h+ir86GcXkefWlCRCMzd9Maeb3aBMkw==
X-Google-Smtp-Source: AIpwx4+3qLpMZFIp09V9loIpeI1I7GG9R1NNN1FtJRFrBwrKHcWC//Ir2xCWydLsK93qWf2E8mwsjkui0RNYG8JLfms=
X-Received: by 10.46.151.206 with SMTP id m14mr15400780ljj.102.1524513484591; Mon, 23 Apr 2018 12:58:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:d8c6:0:0:0:0:0 with HTTP; Mon, 23 Apr 2018 12:58:03 -0700 (PDT)
In-Reply-To: <20180423.214923.1209533731960312602.mbj@tail-f.com>
References: <CABCOCHQukqRLz1Q-W0wNsV0ZOkBpm9gzXG0JqsUhj8voyPC6BQ@mail.gmail.com> <20180423.132830.1432860273167614403.mbj@tail-f.com> <CABCOCHQXqPpXT031qaZ5psPr4C8rsC6E2PkaL2nNLB7K-H_37g@mail.gmail.com> <20180423.214923.1209533731960312602.mbj@tail-f.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Mon, 23 Apr 2018 12:58:03 -0700
Message-ID: <CABCOCHTwdBbo_qtBu=_OunOtLNBXmWCWVZ8ajr0LFZPDFpNEFg@mail.gmail.com>
To: Martin Bjorklund <mbj@tail-f.com>
Cc: Kent Watsen <kwatsen@juniper.net>, NetMod WG <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="883d24f22e14b463b3056a89747e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5RjU6Yl6YDdFcY9FCORBaIVOKOc>
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: Mon, 23 Apr 2018 19:58:09 -0000

> ....
> >
> > I do not understand the need for a yang-data structure that represents
> data
> > that can be instantiated anywhere and everywhere.
>
> AFAIK noone is proposing that.
>
> > I do not want to break
> > existing tools that expect sibling data nodes in the same module
> namespace
> > to
> > be unique local-names.
> >
> > I would rather stick with the yang-data in RFC 8040 than introduce a new
> > extension
> > with no restrictions.  Standard YANG extensions should be interoperable
> and
> > have
> > a clear purpose.
>
> Of course.
>
> > If we do not need to define what a YANG extension does in
> > a way that can be observed somehow, then it does not need to be a
> standard.
>
> Agreed.
>
> Not sure how any of this helps with the original issue though.
>
>

You proposed that duplicate nodes were OK:

module X {
prefix x;

x:yang-data A {
   list foo { ... }
}

x:yang-data B {
  container foo { ... }
}

}


I do not want to allow any duplicates.
There are no encoding and parsing rules for instance data
that support this sort of duplicate.

yang-data definitions define conceptual data nodes (e.g, /x:foo)
Only one data-def-stmt (in yang-data or otherwise) can define a data node
/x:foo.
The descriptive names for the yang-data (A or B) do not define namespaces.



> /martin
>
>
Andy