[netmod] Action and RPC statements [was Re: augment YANG 1.0 with YANG 1.1 OK?]

Robert Wilton <rwilton@cisco.com> Thu, 26 October 2017 17:45 UTC

Return-Path: <rwilton@cisco.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 27AB4138BE7 for <netmod@ietfa.amsl.com>; Thu, 26 Oct 2017 10:45:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 7RCL-CIbaldP for <netmod@ietfa.amsl.com>; Thu, 26 Oct 2017 10:45:04 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 677B413F3C7 for <netmod@ietf.org>; Thu, 26 Oct 2017 10:45:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7732; q=dns/txt; s=iport; t=1509039903; x=1510249503; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=LpG0AggKqGWVXu4HCNjNa82XcUG1zRjbvdj3atUqaIA=; b=JZKWh3wO3emMwuVtKpUrGDXuFbwpBd7zBvs8UH5lPaqw7hS+bqx7SEGF 4b4e4fZx4UI1O/ncpbG8AftVweMgSWaVvOMKZSh7LoSqTSQTrRmz+SFYO H6xPOVICBZM6Aq2V+zK4TbILKZxKLSlQCvkzQtX42JAUicwgGO/GSts5n 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B3AQC6HvJZ/xbLJq1ZAxkBAQEBAQEBAQEBAQcBAQEBAYRDboQhixOQF5B8h1UKH4M+gV4ChQMVAQIBAQEBAQEBayiFHgEFI1YOAgkSCCoCAhs8BgEMCAEBihyLap1ngicmik8BAQEBAQEBAQEBAQEBAQEBAQEBAQEdBYMpg1eBaSmHcDcmgk2CYQWhe4FukwuLcoc5jiKHaIE5NSKBaDQhCB0Vgy4Igho5HIFoQIx8AQEB
X-IronPort-AV: E=Sophos;i="5.44,301,1505779200"; d="scan'208,217";a="656600367"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Oct 2017 17:44:53 +0000
Received: from [10.61.199.20] ([10.61.199.20]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v9QHirVA021489; Thu, 26 Oct 2017 17:44:53 GMT
To: Andy Bierman <andy@yumaworks.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <20171015.095206.5556973134711466.mbj@tail-f.com> <CABCOCHR_q8DTF2agDi_VH9pSL8DWV1ttuX=ZZDO9OmNXhAeEsg@mail.gmail.com> <20171018143651.kdsf77r65ptlu4mq@elstar.local> <CABCOCHRVdkjV5PgQ+UtwJMKPLeFRKs_=ogAfTaCGZsWEdgP5uw@mail.gmail.com> <20171018213601.hdkt2qtqsno6vr4u@elstar.local> <CABCOCHS72TVrurJ1mTRi4eGQR3=G1=bx3wk_NK07NOB8OaZfKg@mail.gmail.com> <bacb34ef-d3d9-babd-467e-188146c1084d@cisco.com> <CABCOCHR6tSg9RRW7gZ50qp6F5frWGm-P1qK_0xEEQdiNursB7A@mail.gmail.com> <20171024172125.l6l3yhocakfkcoh2@elstar.local> <CABCOCHQ8nbf_H6eJxGFqwr=LHrdxyFWc3a4FfhLwR45bs-J19Q@mail.gmail.com> <20171025110851.wdoj2dbrqmxz5shd@elstar.local> <CABCOCHR22Ehryxu374a_-F6PFYayTgizReHuC0EaY4uBC7+vyg@mail.gmail.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <4d2030ca-3d75-72db-1afd-76a8597b615c@cisco.com>
Date: Thu, 26 Oct 2017 18:44:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CABCOCHR22Ehryxu374a_-F6PFYayTgizReHuC0EaY4uBC7+vyg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------36B587DBD20BEC11677F3BFA"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ksLWIwU2RiwH-6AOz7Pa1TPyJ-0>
Subject: [netmod] Action and RPC statements [was Re: augment YANG 1.0 with YANG 1.1 OK?]
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: Thu, 26 Oct 2017 17:45:06 -0000

Hi ,

Separating out the issue regarding which datastore action and RPC apply 
to, we propose the following NEW text to the datastores draft:

6.2 Invocation of Actions and RPC Operations

   This section updates section 7.15. of RFC 7950.

   In YANG data models, the "action" statement may appear under "config
   true" and "config false" schema nodes.  While instances of both
   schema nodes may appear in <operational>, instances of "config true"
   schema nodes may also appear in other datastores.

   An NMDA compliant server MUST execute all actions in the context of
   <operational>.  Likewise, an NMDA compliant server MUST invoke all RPC
   operations in the context of <operational>, unless the RPC is explicitly
   defined as affecting other datastores (e.g., <edit-config>).

OK?

Thanks,
Rob


On 25/10/2017 16:54, Andy Bierman wrote:
>
>     > >
>     > > > (2) Define <action2>:
>     > > > >
>     > > > > I'm not convinced that this is really required/helpful,
>     given that most
>     > > > > actions are likely to only apply to operational.  If it
>     turns out that
>     > > this
>     > > > > is particularly useful then I would propose that this is
>     deferred
>     > > until a
>     > > > > future revision of NETCONF, particularly because we are
>     trying to keep
>     > > the
>     > > > > NETCONF NMDA and RESTCONF NMDA drafts as small as possible.
>     > > > >
>     > > > > Is this OK?
>     > > > >
>     > > >
>     > > > The NMDA theme has been to declare things that are possible
>     in pre-NMDA
>     > > > but not supported in post-NMDA to be not useful, so this can
>     be left to
>     > > > vendors I guess.
>     > >
>     > > Not sure I understand this either.
>     > >
>     > > If you have a concrete change proposal, perhaps the discussion
>     becomes
>     > > more concrete and productive.
>     > >
>     >
>     >
>     > I already said to declare that <action> is invoked in
>     <operational>. Period.
>     > No description-stmt exceptions.
>     >
>     > If another datastore is needed, use rpc-stmt instead of action-stmt.
>
>     So you are fine if for RPCs description statements can define which
>     datastores are affected by an RPC? I probably did not get that you
>     make a distinction between actions and RPCs here.
>
>     /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/
>     <http://www.jacobs-university.de/>>
>
>