IETF Logo Mail Archive

Re: [netmod] Y34

Ladislav Lhotka <lhotka@nic.cz> Tue, 21 July 2015 09:21 UTC

Return-Path: <lhotka@nic.cz>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7769E1A1A7D for <netmod@ietfa.amsl.com>; Tue, 21 Jul 2015 02:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.361
X-Spam-Level:
X-Spam-Status: No, score=-0.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, MIME_8BIT_HEADER=0.3, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 N5d53YPnpoI7 for <netmod@ietfa.amsl.com>; Tue, 21 Jul 2015 02:21:22 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E17FE1A1A57 for <netmod@ietf.org>; Tue, 21 Jul 2015 02:21:21 -0700 (PDT)
Received: from [IPv6:2001:67c:370:176:1a:249c:825e:9faf] (unknown [IPv6:2001:67c:370:176:1a:249c:825e:9faf]) by mail.nic.cz (Postfix) with ESMTPSA id 88429180ECA; Tue, 21 Jul 2015 11:21:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1437470479; bh=QoA515Pmk/8fTFr99XgneTcVqji/9K715d2Lyg604sE=; h=From:Date:To; b=me6mAlnWU+iUsQAWkP+Io7E3FX11DAPN7QO+OAUDKE2o9/nIx85TXsTUbs2jsvk5a 9y+yi7gg5W2xP8tWKWm+Ee1O6VbAFad+zKsXjoiKf+PyrShX45CHLdanr9mJTgzpUV cjBkWL1szykT5d4q5rgWq16USUG8meVbQAiOhR3w=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <20150721074428.GC18607@elstar.local>
Date: Tue, 21 Jul 2015 11:21:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6ECE8AED-0C40-43AF-A90F-779D8DC2CDA7@nic.cz>
References: <m2d1zn0zhm.fsf@dhcp-hotel-wired-13-fe.meeting.ietf.org> <D0153452-D5F5-4E3C-B3D7-7003ACC405EA@nic.cz> <CABCOCHSqbZfKRqGjT1rsphRnw0tYdR3uT=mFvTvJYXMwL3N2uw@mail.gmail.com> <5497CE3E-19A7-4AAC-AE32-AFC9BC2451F1@nic.cz> <CABCOCHRoA9-BP7=OvUGdvXNuowPUty4xy6iai6Q6dVOjD5iGbQ@mail.gmail.com> <06C8EE42-B70D-40A7-8B16-053D37378043@nic.cz> <CABCOCHRS-JF8UK+9fQ=yvZy9ttcj3j6oJn0n3Co6f7kB0tpFgA@mail.gmail.com> <F990644A-4CBE-43D5-AB2B-A20E54A91A65@nic.cz> <20150720210041.GA17614@elstar.local> <4D704311-D5B7-43F3-BD23-C13D5289CF46@nic.cz> <20150721074428.GC18607@elstar.local>
To: Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.2102)
X-Virus-Scanned: clamav-milter 0.98.7 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/xfwoCxNwfEo3EGIYNhvgj9_Il24>
Cc: NETMOD Working Group <netmod@ietf.org>
Subject: Re: [netmod] Y34
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 21 Jul 2015 09:21:23 -0000

> On 21 Jul 2015, at 09:44, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
> On Tue, Jul 21, 2015 at 09:16:46AM +0200, Ladislav Lhotka wrote:
>> 
>>> On 20 Jul 2015, at 23:00, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>>> 
>>> Lada,
>>> 
>>> Y34 is closed and I have not seen any new argument here that indicates
>>> we made a major mistake with the resolution of Y34. As such, Y34
>>> remains closed.
>> 
>> Of course, I was expecting this reaction. I think I did present *some* arguments, and I am leaving it to others to judge whether they are relevant or not. Even if it was a minor mistake, it is IMO still worth fixing.
>> 
>>> 
>>> If you want to discuss new ideas to relocate or "symlink" data models,
>>> please do so in a separate thread. (And no, we do not accept new
>>> issues for YANG 1.1 either at this point in time.)
>> 
>> It’s not about symlinks in the data tree but rather about a method for combining schemas that is complementary to “augment” - pull versus push.
>> 
>> There is sufficient evidence that it was one of the use cases for “anydata”, e.g. in configlets. The gap in “anydata” definition for similar use cases is that it cannot specify a schema for its contents.
>> 
> 
> Lada, you can't simply 'mount' a data model into a different place.
> Think about paths in must or when expressions, or think about paths
> contraints in leafrefs etc. And Y34 was not trying to solve this

This is a fair point but “anydata” where the schema is supplied somehow out of band faces the same issue.

Lada

> problem, so this discussion is IMHO under a misleading subject line.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C

v2.23.0 | Report a Bug | By Email