Re: [netmod] Opstate solutions discussions: update and request for WG input
<stephane.litkowski@orange.com> Thu, 09 June 2016 09:23 UTC
Return-Path: <stephane.litkowski@orange.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 5421F12D1E0; Thu, 9 Jun 2016 02:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.345
X-Spam-Level:
X-Spam-Status: No, score=-3.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 KJRX7uyO_92V; Thu, 9 Jun 2016 02:23:29 -0700 (PDT)
Received: from relais-inet.orange.com (relais-nor35.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A80112D18D; Thu, 9 Jun 2016 02:23:29 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 23554180262; Thu, 9 Jun 2016 11:23:28 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.17]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id E95901A005B; Thu, 9 Jun 2016 11:23:27 +0200 (CEST)
Received: from OPEXCLILMA4.corporate.adroot.infra.ftgroup ([fe80::65de:2f08:41e6:ebbe]) by OPEXCLILM24.corporate.adroot.infra.ftgroup ([fe80::a1e6:3e6a:1f68:5f7e%19]) with mapi id 14.03.0294.000; Thu, 9 Jun 2016 11:23:28 +0200
From: stephane.litkowski@orange.com
To: Lou Berger <lberger@labn.net>, netmod WG <netmod@ietf.org>
Thread-Topic: [netmod] Opstate solutions discussions: update and request for WG input
Thread-Index: AQHRwMeryY8MgJBTQEykBoRF6CHPKJ/g3qSA
Date: Thu, 09 Jun 2016 09:23:27 +0000
Message-ID: <18419_1465464208_5759358F_18419_2226_1_9E32478DFA9976438E7A22F69B08FF921BC48871@OPEXCLILMA4.corporate.adroot.infra.ftgroup>
References: <63b1dc74-c60c-351d-8d6d-38c860a6476e@labn.net>
In-Reply-To: <63b1dc74-c60c-351d-8d6d-38c860a6476e@labn.net>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.5]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/nnL1HZ5ekDUj3QgBSVt0LJV_6TQ>
Cc: "netmod-chairs@ietf.org" <netmod-chairs@ietf.org>
Subject: Re: [netmod] Opstate solutions discussions: update and request for WG input
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 09 Jun 2016 09:23:31 -0000
I'm also in favor of B. I personally do not like the way state/config are expressed in [1] as it complexifies the way yang modules are written while a solution like [4] allows to have a more cleaner yang module while achieving the same goal. As expressed by others, B will also be faster with existing modules. Best Regards, Stephane -----Original Message----- From: netmod [mailto:netmod-bounces@ietf.org] On Behalf Of Lou Berger Sent: Tuesday, June 07, 2016 16:20 To: netmod WG Cc: netmod-chairs@ietf.org Subject: [netmod] Opstate solutions discussions: update and request for WG input All, We want to provide an update based on the off line discussions related to OpState Solutions that we have been having and solicit input from the WG. All authors of current solution drafts [1,2,3] together with those who helped conduct the solutions analysis* were invited to the these discussions -- with the objective of coming up with a single consolidated proposal to bring to the WG. (I/Lou acted as facilitator as Kent and Juergen were and are involved with the technical details.) The discussions have yielded some results but, unfortunately, not a single consolidated proposal as hoped, but rather two alternate directions -- and clearly we need to choose one: 1) Adopt the conventions for representing state/config based on Section 6 of [1]. From a model definition perspective, these conventions impact every model and every model writer. 2) Model OpState using a revised logical datastore definition as introduced in [4] and also covered in [5]. There is also a variant of this that we believe doesn't significantly impact this choice. With this approach, model definitions need no explicit changes to support applied configuration. >From a technology/WG standpoint, we believe an approach that doesn't impact every model written (i.e., #2) is superior. The counterpoint to this is that the conventions based approach (i.e., #1) is available today and being followed in OpenConfig defined models. We would like to hear opinions on this from the WG before declaring one of the following as the WG direction: A) models that wish to support applied configuration MUST follow conventions based on [1] -- and the WG needs to formalize these conventions. or B) no explicit support is required for models to support applied configuration -- and that the WG needs to formalize an opstate solution based on the approach discussed in [4] and [5]. We intend to close on this choice before Berlin. Thank you, Lou (and co-chairs) [1] https://tools.ietf.org/html/draft-openconfig-netmod-opstate-01 [2] https://tools.ietf.org/html/draft-kwatsen-netmod-opstate-02 [3] https://tools.ietf.org/html/draft-wilton-netmod-opstate-yang-02 [4] https://tools.ietf.org/html/draft-schoenw-netmod-revised-datastores-00 [5] https://tools.ietf.org/html/draft-wilton-netmod-refined-datastores-00 * - Chris H. and Acee L. _______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- Re: [netmod] Closing on an OpState Solution Direc… Benoit Claise
- Re: [netmod] Opstate solutions discussions: updat… Andy Bierman
- Re: [netmod] Opstate solutions discussions: updat… Andy Bierman
- Re: [netmod] Opstate solutions discussions: updat… Kent Watsen
- Re: [netmod] Opstate solutions discussions: updat… Andy Bierman
- Re: [netmod] Opstate solutions discussions: updat… Kent Watsen
- Re: [netmod] Opstate solutions discussions: updat… Kent Watsen
- Re: [netmod] Opstate solutions discussions: updat… Andy Bierman
- Re: [netmod] Opstate solutions discussions: updat… Lou Berger
- Re: [netmod] Opstate solutions discussions: updat… t.petch
- Re: [netmod] Opstate solutions discussions: updat… Juergen Schoenwaelder
- Re: [netmod] Opstate solutions discussions: updat… Kiran Koushik Agrahara Sreenivasa (kkoushik)
- Re: [netmod] Opstate solutions discussions: updat… Andy Bierman
- Re: [netmod] Opstate solutions discussions: updat… Lou Berger
- Re: [netmod] Opstate solutions discussions: updat… Acee Lindem (acee)
- Re: [netmod] Opstate solutions discussions: updat… t.petch
- Re: [netmod] Opstate solutions discussions: updat… Robert Wilton
- Re: [netmod] Opstate solutions discussions: updat… Lou Berger
- Re: [netmod] Opstate solutions discussions: updat… Nadeau Thomas
- Re: [netmod] Opstate solutions discussions: updat… Mahesh Jethanandani
- Re: [netmod] Opstate solutions discussions: updat… Xufeng Liu
- Re: [netmod] Opstate solutions discussions: updat… Jonathan Hansford
- Re: [netmod] Opstate solutions discussions: updat… Juergen Schoenwaelder
- Re: [netmod] Opstate solutions discussions: updat… stephane.litkowski
- Re: [netmod] Opstate solutions discussions: updat… Lou Berger
- Re: [netmod] Opstate solutions discussions: updat… stephane.litkowski
- Re: [netmod] Opstate solutions discussions: updat… Kent Watsen
- [netmod] Closing on an OpState Solution Direction… Lou Berger
- [netmod] Opstate solutions discussions: update an… Lou Berger
- Re: [netmod] Opstate solutions discussions: updat… Andy Bierman
- Re: [netmod] Opstate solutions discussions: updat… Martin Bjorklund
- Re: [netmod] Opstate solutions discussions: updat… Ladislav Lhotka
- Re: [netmod] Opstate solutions discussions: updat… chopps
- Re: [netmod] Opstate solutions discussions: updat… Acee Lindem (acee)
- Re: [netmod] Opstate solutions discussions: updat… stephane.litkowski