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

Benoit Claise <bclaise@cisco.com> Mon, 14 September 2015 12:41 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 5B4D81B4FB2 for <netmod@ietfa.amsl.com>; Mon, 14 Sep 2015 05:41:00 -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 zMA69sp13rgT for <netmod@ietfa.amsl.com>; Mon, 14 Sep 2015 05:40:58 -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 93D6A1B3BC2 for <netmod@ietf.org>; Mon, 14 Sep 2015 05:40:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10585; q=dns/txt; s=iport; t=1442234457; x=1443444057; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=Ob/2FPZcRMUiwzPwbmMxVk1rTxUIlxxPF8hgWbSXmOc=; b=BE8BysaVOFij6v2PFnzd7eK4q8cTh05Sc9p/QhNLBVTnqEXzhxPVnkxO 7CXovWUEjEjXYanNO9Pjr70zXzXLkYAlR9Jzqi2loeVsl4Kk2C2aEGb8k pgc7loS1Koe5WFpe45sB3X5AyTLZr68hv9SNaMqaGNUX2esOHX0YvtPoS 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DKAQBBv/ZV/xbLJq1dg3dpvT4BDYFuAQuFLUoCgW0UAQEBAQEBAYEKhCMBAQEEAQEBawQFAQ0ECxEEAQEBCRYPCQMCAQIBFScBCAYBDAYCAQGIKg3JfwEBAQEBAQEBAQEBAQEBAQEBAQEBAReGc4R9hCoLBgFYBoQmAQSMeIhfhQ2HcYFMRoNtgn6SAR8BAUKCERwWgUA8MwGJNQgXgSgBAQE
X-IronPort-AV: E=Sophos;i="5.17,527,1437436800"; d="scan'208,217";a="611596008"
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:40:55 +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 t8ECesk7027026; Mon, 14 Sep 2015 12:40:54 GMT
To: Jonathan Hansford <jonathan@hansfords.net>, Kent Watsen <kwatsen@juniper.net>, netmod@ietf.org
References: <086460742009f24c7cb566cc4652d26bc9dcd52b@webmail.hansfords.net>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <55F6C056.5040802@cisco.com>
Date: Mon, 14 Sep 2015 14:40:54 +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: <086460742009f24c7cb566cc4652d26bc9dcd52b@webmail.hansfords.net>
Content-Type: multipart/alternative; boundary="------------020302040803060409050904"
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/yyXqFMpfKzOtDf_EO__Ws1v8r7A>
Subject: Re: [netmod] FW: New Version Notification for draft-chairs-netmod-opstate-reqs-00.txt
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:41:00 -0000

Jonathan,
> Looking in from outside the current problem domain I'm not sure I'm 
> sufficiently informed to comment, however I have a couple of queries:
>
>  1. The requirements talk about both synchronous and asynchronous
>     systems (1(D), 3, 3(A)) but really only address the behaviour for
>     asynchronous systems. Would it not be worth clarifying the
>     relationship between the intended and applied configurations for
>     synchronous systems (i.e. they are the same), hence there is no
>     need for synchronous requirements equivalent to 1(D) and 3(A)?
>  2. Why does 7(A) limit the scope to IETF-defined modules of others
>     are now defining YANG modules?
>
Good point. We need to provide guidance for the other SDOs.

Regards, Benoit
> Thanks,
>
> Jonathan
>
>
>     ----- Original Message -----
>     From:
>     "Kent Watsen" <kwatsen@juniper.net>
>
>     To:
>     "netmod@ietf.org" <netmod@ietf.org>
>     Cc:
>
>     Sent:
>     Fri, 11 Sep 2015 22:16:40 +0000
>     Subject:
>     [netmod] FW: New Version Notification for
>     draft-chairs-netmod-opstate-reqs-00.txt
>
>
>
>     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
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod