IETF Logo Mail Archive

Re: [netmod] Action and RPC statements

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 01 November 2017 19:28 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
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 0833B13F5F6 for <netmod@ietfa.amsl.com>; Wed, 1 Nov 2017 12:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 HUuMndc3JY7I for <netmod@ietfa.amsl.com>; Wed, 1 Nov 2017 12:28:24 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3AD713F58C for <netmod@ietf.org>; Wed, 1 Nov 2017 12:28:23 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 816D66A0; Wed, 1 Nov 2017 20:28:22 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id w9SryUGZPo_V; Wed, 1 Nov 2017 20:28:22 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Wed, 1 Nov 2017 20:28:22 +0100 (CET)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4E38B20116; Wed, 1 Nov 2017 20:28:22 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id UFW4KhcFKJHM; Wed, 1 Nov 2017 20:28:21 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 73F9A20114; Wed, 1 Nov 2017 20:28:21 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 44C1341477CA; Wed, 1 Nov 2017 20:26:55 +0100 (CET)
Date: Wed, 01 Nov 2017 20:26:54 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Alexander Clemm <alexander.clemm@huawei.com>
Cc: Robert Wilton <rwilton@cisco.com>, Martin Bjorklund <mbj@tail-f.com>, "andy@yumaworks.com" <andy@yumaworks.com>, "netmod@ietf.org" <netmod@ietf.org>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, Phil Shafer <phil@juniper.net>
Message-ID: <20171101192654.tn7cjntbxijfit6c@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Alexander Clemm <alexander.clemm@huawei.com>, Robert Wilton <rwilton@cisco.com>, Martin Bjorklund <mbj@tail-f.com>, "andy@yumaworks.com" <andy@yumaworks.com>, "netmod@ietf.org" <netmod@ietf.org>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, Phil Shafer <phil@juniper.net>
References: <4d2030ca-3d75-72db-1afd-76a8597b615c@cisco.com> <c544a19e-2534-9355-002e-18affd12ea5a@alumni.stanford.edu> <CABCOCHQdmMYObMBCxP=qWuH3RdCRi9q7Y6G0VsSnDeyg2qLc4w@mail.gmail.com> <20171027.103341.1048835221774842137.mbj@tail-f.com> <9645422a-05a2-9d24-e50e-799d964f021f@cisco.com> <644DA50AFA8C314EA9BDDAC83BD38A2E0EABACAD@sjceml521-mbx.china.huawei.com> <4679d0f6-d884-e0a9-94de-0099735a1172@cisco.com> <20171101115308.gxgns54u6qdmxkx2@elstar.local> <644DA50AFA8C314EA9BDDAC83BD38A2E0EABB25E@sjceml521-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <644DA50AFA8C314EA9BDDAC83BD38A2E0EABB25E@sjceml521-mbx.china.huawei.com>
User-Agent: NeoMutt/20170714 (1.8.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/dzKC7yzmMXGRKm5VcXIM52hhUNc>
Subject: Re: [netmod] Action and RPC statements
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, 01 Nov 2017 19:28:31 -0000

On Wed, Nov 01, 2017 at 06:00:15PM +0000, Alexander Clemm wrote:
> 
> > -----Original Message-----
> ...
> > > That is an interesting question.
> > >
> > > To describe this as a concrete example, if you have a single config
> > > true YANG list for dynamic/configuration subscriptions then a
> > > subscription can be created either via configuration or as an RPC operation.
> > >
> > > I would probably classify this as "learned", and I think that we could
> > > extend the definition of the "learned" origin to cover this case.
> > 
> > I do not think any changes are needed, section 5.3.4 is pretty clear that the
> > origin 'intended' applies to configuration provided by <intended>. If you at
> > the options, there is pretty much only 'learned' applicable.
> > 
> 
> It may be clear that "intended" may not be the right choice, but what is?  I think it does not hurt to be explicit about it.  This way, people don't have to guess if it should be learned, or maybe system, or possibly even unknown.  In its current definition, "learned" only talks about "protocol interactions with other systems ... such as routing protocols, DHCP, etc." If it is "learned" then update its definition to something like
> 
> learned: represents configuration that has been learned via
>       protocol interactions with other systems, including protocols such
>       as link-layer negotiations, routing protocols, DHCP, etc, or as a side effect of RPCs. 
>

I do think that the choice is clear enough if you read the origin
value definitions. The point is that we can't cover all cases. Even if
we name side effects of RPCs (which is BTW not correct since some RPCs
do as a side effect modify configuration datastores), the next person
is going to say we do not cover YANG actions or certain SNMP sets or.

/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/>

v2.23.0 | Report a Bug | By Email