Re: [netmod] WG Last Call: draft-ietf-netmod-revised-datastores-04 inactive

Robert Wilton <rwilton@cisco.com> Wed, 18 October 2017 16:48 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 EC6141329B5 for <netmod@ietfa.amsl.com>; Wed, 18 Oct 2017 09:48:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 haKXtBVwBvDT for <netmod@ietfa.amsl.com>; Wed, 18 Oct 2017 09:48:43 -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 8F1CC132031 for <netmod@ietf.org>; Wed, 18 Oct 2017 09:48:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4380; q=dns/txt; s=iport; t=1508345322; x=1509554922; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=/HiI3gKdq0XayW/RCGe457dwlH0UPeCAh0F3bSFlkvg=; b=RM/IfPN6NJWyAxHmoPYoJTUv+Hz9Y2KBfT5RTjJLdrni7r2yWYgKP4zj wesqPfJSRFfHkDPhWwfKv8RrgJPLbMXQ+oNXcxT+vFS9gumvgLdnXaeUf pZp8UDS6+bteFH69KffSBpA9jzoL6L0i3na9wOnCb1sdHNvwwWtwsPzxY g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DOAAD8hOdZ/xbLJq1ZAxkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYRDbieDeoofdJAYJZYzEIIEChgLhElPAoU4GAECAQEBAQEBAWs?= =?us-ascii?q?ohR0BAQEEAQEhDwEFNhcCAgkCEAUBAgICJgICGwwwBgEMBgIBAYocEI0RnWeCJ?= =?us-ascii?q?4snAQEBAQEBAQEBAQEBAQEBAQEBAQEBHQWBCoIgg1iCFQuCeYRtOSaCTIJhBZh?= =?us-ascii?q?PiHyUbYIUhXaDXIFUhV6OEYdigTkfOIFbNCEIHRVJgmQJhFc/NohLLIIWAQEB?=
X-IronPort-AV: E=Sophos;i="5.43,397,1503360000"; d="scan'208";a="656427311"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Oct 2017 16:48:38 +0000
Received: from [10.63.23.135] (dhcp-ensft1-uk-vla370-10-63-23-135.cisco.com [10.63.23.135]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v9IGmcmf027788; Wed, 18 Oct 2017 16:48:38 GMT
To: "t.petch" <ietfc@btconnect.com>, netmod WG <netmod@ietf.org>
References: <511deba5-34ca-dde2-6637-ceaf4c4af125@labn.net> <000901d32e3e$883fa9c0$4001a8c0@gateway.2wire.net> <20170915170959.q5bfwoqoaqaq4o5b@elstar.local> <009e01d32ff4$345b4a00$4001a8c0@gateway.2wire.net>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <83feada1-5e1e-5389-ec61-6724bd1fd183@cisco.com>
Date: Wed, 18 Oct 2017 17:48:38 +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: <009e01d32ff4$345b4a00$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/IxtUvuyyHXk4apaymXdXPi_ouuU>
Subject: Re: [netmod] WG Last Call: draft-ietf-netmod-revised-datastores-04 inactive
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, 18 Oct 2017 16:48:45 -0000

Hi Tom,

Regarding the issue on the definition of inactive configuration, in the 
end we think that we don't need to define it for the following reasons:

1) Juergen's new objectives contains a brief description of inactive 
configuration (without defining it).
2) Inactive has been removed from the normative text, instead the 
normative text more generically refers to "configuration 
transformations" and just uses inactive as an example of such a 
transformation.
3) Configuration transformation is defined as:

    o  configuration transformation: The addition, modification or
       removal of configuration between the <running> and <intended>
       datastores.  Examples of configuration transformations include the
       removal of inactive configuration and the configuration produced
       through the expansion of templates.

OK?

Validating that this is sufficient to address your concern maybe easier 
when we post an updated revision with all WG LC markups applied.

Thanks,
Rob


On 17/09/2017 21:21, t.petch wrote:
> ----- Original Message -----
> From: "Juergen Schoenwaelder" <j.schoenwaelder@jacobs-university.de>
> Sent: Friday, September 15, 2017 6:09 PM
>
>
>> Two comments:
>>
>> - Obviously, inactive can be in <candidate> and I would not rule out
>>    that inactive configuration can be in any other or future
>>    configuration datastores.
>>
>> - Whether protocols support inactive or not does not belong into a
>>    definition of what inactive configuration is. The same for backwards
>>    compatibility considerations etc.
>>
>> So if we define inactive configuration, the definition should be
>> something like this:
>>
>> * inactive configuration: Configuration held in a configuration
>>    datastore that is marked to be inactive. Inactive configuration is
>>    ignored during validation and never applied and actively used by
>>    a device.
>>
>> Yes, we should use 'inactive configuration' everywhere to be
> consistent.
>
> Juergen
>
> Yes, your definition is better than mine; let's add it.
>
> Tom Petch
>
>> /js
>>
>> On Fri, Sep 15, 2017 at 05:20:15PM +0100, t.petch wrote:
>>> Inactive appears a dozen times but is not defined, except in the
> course
>>> of those appearances it effectively is, but is sometimes 'inactive',
>>> sometimes 'inactive configuration', sometimes 'inactive data'.
>>>
>>> I would find it clearer if the term was used consistently and if
> there
>>> was an explicit definition amongst the other definitions in section
> 2
>>> such as
>>>
>>> inactve configuration: Configuration that is present in <running>
> which
>>> is not in use by the device and which plays no part in validation.
> It
>>> cannot appear in any other datastore.  The protocols that are
> currently
>>> standardised do not support inactive configuration but a number of
>>> proprietary protocols do. Inactive configuration is only exposed to
>>> clients that indicate support for inactive configuration; clients
> not
>>> indicating support for  inactive configuration receive the contents
> of
>>> <running> with the inactive configuration removed.
>>>
>>> This would put a stake in the ground for as and when the concept is
>>> standardised and may reduce the proliferation of the term with
> multiple
>>> meanings.
>>>
>>> Tom Petch
>>>
>>>
>>> ----- Original Message -----
>>> From: "Lou Berger" <lberger@labn.net>
>>> Sent: Friday, September 01, 2017 10:02 PM
>>>
>>>> This starts a two week working group last call on
>>>> draft-ietf-netmod-revised-datastores-04.
>>>>
>>>> The working group last call ends on September 17.
>>>> Please send your comments to the netmod mailing list.
>>>>
>>>> Positive comments, e.g., "I've reviewed this document and
>>>> believe it is ready for publication", are welcome!
>>>> This is useful and important, even from authors.
>>>>
>>>> Thank you,
>>>> Netmod Chairs
>>>>
>>>> _______________________________________________
>>>> netmod mailing list
>>>> netmod@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/netmod
>> --
>> 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/>
> .
>