Re: [netmod] FW: New Version Notification for draft-chairs-netmod-opstate-reqs-00.txt - REQ 6 clarification

Benoit Claise <bclaise@cisco.com> Mon, 14 September 2015 12:43 UTC

Return-Path: <bclaise@cisco.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 0A2831B4AFF for <netmod@ietfa.amsl.com>; Mon, 14 Sep 2015 05:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 NbPxHVnRBxe7 for <netmod@ietfa.amsl.com>; Mon, 14 Sep 2015 05:43:31 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C9081B531D for <netmod@ietf.org>; Mon, 14 Sep 2015 05:43:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7516; q=dns/txt; s=iport; t=1442234609; x=1443444209; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=o3ZGD4RFCkrvE6sEmrAS2on1NyEcr0HQOHXO0SAH+Qk=; b=ZZQrFhrWo7/MqtUzUYZUw6uaP+AspsJ6LSxPbCVUepSg7tR7f6tEFLAt 15iKilfW6UCl9nYpZx+kXgo+2uLTQq2p2ljLMVfDmSFw83EtNyMht3d+B 65WRltwfKKXNJdm2ZrkXcgdYMfRL3gwibxwF7OMFL3WKLkmmbn1qTT0tH g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DKAQCVwPZV/xbLJq1dg3dpvT4BDYFuAQuFLUoCgW0UAQEBAQEBAYEKhCMBAQEEAQEBawkBEQsOCgkWBAsJAwIBAgEVJwkGAQwGAgEBiCoNygMBAQEBAQEBAQEBAQEBAQEBAQEahnOEfYQqEQFYhCwBBIx4iF+FDYdxgUxGg22CfpIBHwEBQoIRHBaBQDwzAYk9gT8BAQE
X-IronPort-AV: E=Sophos;i="5.17,528,1437436800"; d="scan'208,217";a="611596071"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 14 Sep 2015 12:43:27 +0000
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t8EChQEL027646; Mon, 14 Sep 2015 12:43:27 GMT
To: Kent Watsen <kwatsen@juniper.net>, "netmod@ietf.org" <netmod@ietf.org>
References: <20150911213636.11309.79529.idtracker@ietfa.amsl.com> <D218C74A.D7BAC%kwatsen@juniper.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <55F6C0EE.4010404@cisco.com>
Date: Mon, 14 Sep 2015 14:43:26 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <D218C74A.D7BAC%kwatsen@juniper.net>
Content-Type: multipart/alternative; boundary="------------060402000907050800020003"
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/n_pWsij3BRSJ3MxJYzDWlHHyNiw>
Subject: Re: [netmod] FW: New Version Notification for draft-chairs-netmod-opstate-reqs-00.txt - REQ 6 clarification
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: Mon, 14 Sep 2015 12:43:33 -0000

Dear all,

I have a clarification question wrt the requirement 6

   6.  Ability to relate configuration with its corresponding
        operational state

        A.  Ability to map intended config nodes to corresponding applied
            config nodes

        B.  Ability to map intended config nodes to associated derived
            state nodes

        C.  The mappings needs to be programmatically consumable

 From the appendix A, we can see that this requirement comes from 
draft-openconfig-netmod-opstate-01 
<https://tools.ietf.org/html/draft-openconfig-netmod-opstate-01>, 
Section 4.5 
<https://tools.ietf.org/html/draft-chairs-netmod-opstate-reqs-00#section-4.5>
Re-reading this section 4.5, I understand 6A and 6C, but is 6B also 
required?
Do we need to make the link between a config node and all the derived 
counters/statistics it influences, which might be in different YANG 
models btw?

Regards, Benoit
> The AD and chairs thought it best to formalize the consensus on the
> requirements a bit more.  So we created the I-D listed below to track and
> capture final consensus.
>
> Additionally, we want to use this GitHub issue tracker to track issues:
>
> 	https://github.com/netmod-wg/opstate-reqs/issues
>
> Consistent with Tom's earlier email, we want to collect any issues with
> these requirements before EOB Monday, September 14, 2015 at 5PM EST.  If
> you have an issue, in addition to posting it to the list, please consider
> adding it to the GitHub tracker, and let people know you did so.   Our
> goal is to close the issues as quickly as possible, some will go to DEAD
> while others may remain OPEN, based on WG consensus.
>
> Thanks,
> Kent & Tom
>
>
> On 9/11/15, 5:36 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
>
>> A new version of I-D, draft-chairs-netmod-opstate-reqs-00.txt
>> has been successfully submitted by Kent Watsen and posted to the
>> IETF repository.
>>
>> Name:		draft-chairs-netmod-opstate-reqs
>> Revision:	00
>> Title:		NETMOD Operational State Requirements
>> Document date:	2015-09-11
>> Group:		Individual Submission
>> Pages:		5
>> URL:
>> https://www.ietf.org/internet-drafts/draft-chairs-netmod-opstate-reqs-00.t
>> xt
>> Status:
>> https://datatracker.ietf.org/doc/draft-chairs-netmod-opstate-reqs/
>> Htmlized:
>> https://tools.ietf.org/html/draft-chairs-netmod-opstate-reqs-00
>>
>>
>> Abstract:
>>    This document captures consensus on operational state requirements by
>>    the NETMOD working group.
>>
>>                   
>>         
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
>