Re: [netmod] Clarification Question on draft-dsdt-nmda-guidelines-01

Robert Wilton <rwilton@cisco.com> Wed, 14 June 2017 15:10 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 BE40B126CBF; Wed, 14 Jun 2017 08:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 Oy6N-Zfw4eew; Wed, 14 Jun 2017 08:10:44 -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 4B4A012420B; Wed, 14 Jun 2017 08:10:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2725; q=dns/txt; s=iport; t=1497453044; x=1498662644; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=fLzm11HY377SQtJ+offTHN3LKyfgyTM2UNT3d/MxAyw=; b=WMr25Iocrsp3Rm2Mm4D+ujnF+Inf2ub/e6rMRIrS5v42PsaVmm6PtQz2 JWWbRzuOqEbdwEUGekV1VxnyyLHWcPXkfRzl5o5gHBsYTMZG+LWYfA/C4 q9WXM2pdwAilnJQ3FtZfEC9WaPU/+6JMPnHyg6X7yn5xvA+wWw3RLEo6j w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CMAACoUUFZ/xbLJq1bAxkBAQEBAQEBAQEBAQcBAQEBAYQ6gQ2ODnORA5YGghEohXwCgw4YAQIBAQEBAQEBayiFGAEBAQECAThBDAICCxABBAEBAScHGysJCAYBDAYCAQGKIAiwV4s/AQEBAQEBAQEBAQEBAQEBAQEBAQEBHQWGXYFgK4J2hQsmhSwBBJ5Hk1KLFoZzjDmIQR84gQowIQgbFYdXPzaJewEBAQ
X-IronPort-AV: E=Sophos;i="5.39,340,1493683200"; d="scan'208";a="653599217"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Jun 2017 15:10:33 +0000
Received: from [10.63.23.55] (dhcp-ensft1-uk-vla370-10-63-23-55.cisco.com [10.63.23.55]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v5EFAWOG007025; Wed, 14 Jun 2017 15:10:32 GMT
To: Xufeng Liu <Xufeng_Liu@jabil.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
References: <BN3PR0201MB0867C18E5FF7239EE991F720F1C20@BN3PR0201MB0867.namprd02.prod.outlook.com> <20170613200928.GA55527@elstar.local> <CY1PR0201MB0875F3203D6D4DFD606061FAF1C30@CY1PR0201MB0875.namprd02.prod.outlook.com>
Cc: "draft-dsdt-nmda-guidelines@ietf.org" <draft-dsdt-nmda-guidelines@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <2513fdd0-a8b3-b547-8c37-c736c575c4bc@cisco.com>
Date: Wed, 14 Jun 2017 16:10:32 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CY1PR0201MB0875F3203D6D4DFD606061FAF1C30@CY1PR0201MB0875.namprd02.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/mSGbhXhtCBVAzaqqrWHkRCkhyM0>
Subject: Re: [netmod] Clarification Question on draft-dsdt-nmda-guidelines-01
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, 14 Jun 2017 15:10:47 -0000

Hi Xufeng,


On 14/06/2017 14:01, Xufeng Liu wrote:
> Hi Juergen,
>
> Thanks for the confirmation.
> As for the distinction between applied configuration and operational, I think that it has been determined to be useful in some use cases. We can create a separate leaf in such a case.
Yes, I think that this is exactly the right approach.

In the general case, a single leaf for applied configuration and the 
operational value is normally sufficient.

But in some cases (e.g. where a value could be configured and/or 
negotiated via protocol) then it sometimes useful to both see the input 
into the protocol negotiation and also the resultant output value.

Here, there is a choice to be made to decide whether the extra config 
false leaf represents the input value into the negotiation, or the 
output value.  I think that the decision probably depends on the 
protocol semantics, but all things being equal, there is a benefit if 
the configured value and actual operational value end up being 
represented by the same leaf/path (since this in the case in the 
mainline case where extra config false leaves are not required).

Thanks,
Rob


>
> Regards,
> - Xufeng
>
>> -----Original Message-----
>> From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de]
>> Sent: Tuesday, June 13, 2017 4:10 PM
>> To: Xufeng Liu <Xufeng_Liu@jabil.com>
>> Cc: draft-dsdt-nmda-guidelines@ietf.org; netmod@ietf.org
>> Subject: Re: Clarification Question on draft-dsdt-nmda-guidelines-01
>>
>> Hi,
>>
>> the typical -state tree consists of config false nodes and hence it represents
>> operational state. This is not a transitioning period question, this is how -state
>> trees were designed. Note also that the applied configuration is part of the
>> operational state in NMDA - for config true objects, there is no difference
>> between the applied configuration value and the operationally used value - they
>> are the same.
>>
>> /js
>>
>> On Tue, Jun 13, 2017 at 07:53:32PM +0000, Xufeng Liu wrote:
>>> During discussing the adoption of this guidelines, a question came up w.r.t. the
>> semantics of the non-NMDA "-state" module during the transitioning period:
>>> What kind of state do the leaves in the "-state" module represent? The applied
>> configuration or the actually used operational data?
>>> Since only of the two types can be represented, what is the guideline to model
>> the other type?
>>> Thanks,
>>> - Xufeng
>> --
>> 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/>
> .
>