Re: [netmod] new YANG 1.1 Issue Y61: I2RS support

Martin Bjorklund <mbj@tail-f.com> Thu, 30 July 2015 18:19 UTC

Return-Path: <mbj@tail-f.com>
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 CCA131B2E1E for <netmod@ietfa.amsl.com>; Thu, 30 Jul 2015 11:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 I4zB5iGBT0yI for <netmod@ietfa.amsl.com>; Thu, 30 Jul 2015 11:19:17 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3079E1B2D35 for <netmod@ietf.org>; Thu, 30 Jul 2015 11:19:14 -0700 (PDT)
Received: from localhost (h-85-24-195-9.na.cust.bahnhof.se [85.24.195.9]) by mail.tail-f.com (Postfix) with ESMTPSA id 2B6B91AE046E; Thu, 30 Jul 2015 20:19:13 +0200 (CEST)
Date: Thu, 30 Jul 2015 20:19:12 +0200
Message-Id: <20150730.201912.763525508503943000.mbj@tail-f.com>
To: andy@yumaworks.com
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <CABCOCHQrZqxKM6cBzij6hWzMUa8DbKSAULr5gW3fhBBV_OZjRw@mail.gmail.com>
References: <CABCOCHSPZQMJ2dt1AWLWdx0zfukn+qJ3RUzd_P5X=-BEYyyTfw@mail.gmail.com> <20150730.194130.1378875555824248389.mbj@tail-f.com> <CABCOCHQrZqxKM6cBzij6hWzMUa8DbKSAULr5gW3fhBBV_OZjRw@mail.gmail.com>
X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/PGJPBTNJXt_8YkJn-U6INff1PjY>
Cc: netmod@ietf.org
Subject: Re: [netmod] new YANG 1.1 Issue Y61: I2RS support
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: Thu, 30 Jul 2015 18:19:19 -0000

Andy Bierman <andy@yumaworks.com> wrote:
> On Thu, Jul 30, 2015 at 10:41 AM, Martin Bjorklund <mbj@tail-f.com> wrote:
> 
> > Andy Bierman <andy@yumaworks.com> wrote:
> > > On Wed, Jul 29, 2015 at 10:51 AM, Martin Bjorklund <mbj@tail-f.com>
> > wrote:
> > >
> > > > Andy Bierman <andy@yumaworks.com> wrote:
> > > > > Hi,
> > > > >
> > > > > I understand the intent is that an implementation of NACM
> > > > > has to understand these NACM extensions.  I agree with Lada
> > > > > that the YANG text about MAY ignore extensions casts doubt whether
> > > > > this sort of NACM rule is enforceable or specified correctly.
> > > >
> > > > So do you agree that it would be a good idea to clarify this
> > > > according to Juergen's suggestion?
> > > >
> > > >
> > > >
> > > Not really.
> > > Pretending the extension is just another description-stmt
> > > does not really fix anything.
> > >
> > > A real YANG statement like config-stmt or a new statement
> > > called ephemeral-stmt can be modified with refine-stmt
> > > or deviate-stmt.   This can never happen for
> > > an external statement.
> >
> > There are two separate issues here:
> >
> > 1) It seems we are in agreement that if a model uses an extension
> >    statement, it is normative (like ietf-system's usage of nacm:*).
> >
> >    Should we somehow clarify this in 6020bis?
> >
> >
> No -- I agree that was the intent, but it is not achievable
> because tools MAY ignore extensions.

But as have been said several times, this was clearly not the
intention.  So we should clarify this in 6020bis.

> > 2) Extensions cannot be refined or deviated.
> >
> >    Actually, the *syntax* rules allows things like:
> >
> >      deviation /x:foo {
> >        deviate replace {
> >          i2rs:ephemeral true;
> >        }
> >      }
> >
> >    I agree that it not clear what this means, but we could also
> >    clarify this in 6020bis.
> >
> >
> > > IMO ephemeral data support needs to be a real statement
> > > that can be used with refine-stmt and  deviate-stmt.
> > > It is a real property of a data node.
> >
> > Note: it is still not clear that such a statement (base or extension)
> > is needed at all.
> >
> >
> 
> I do not understand why you are so opposed to using real YANG statements
> to support ephemeral state.

If this solution was already well defined and agreed upon by everyone,
then it could be done as a YANG statement.  But I am worried that
adding this will take quite some time, and will thus delay YANG 1.1;
and since IMO extensions can be used just as well, there is no real
reason for adding this delay.

> Do you have a better solution that the
> proposal from draft-haas-i2rs-ephermal-state-reqs-00?

Use a separate ephemeral datastore.

> I don't see it.
> I am opposed to using extensions to ephemeral state because
> they are poorly defined in YANG.

Then we should fix this.


/martin

> This is OK since they are for
> defining statements outside the YANG standard.  Normal mechanisms
> like uses/refine and deviate must be supported.
> 
> I do see any advantages whatsoever for using external statements
> instead of YANG statements.