Re: [Rtg-yang-coord] Operational State Modeling
aldrin ietf <aldrin.ietf@gmail.com> Thu, 14 May 2015 18:07 UTC
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: rtg-yang-coord@ietfa.amsl.com
Delivered-To: rtg-yang-coord@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id BA6EB1A902B
for <rtg-yang-coord@ietfa.amsl.com>; Thu, 14 May 2015 11:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 JPeARajVWcnm for <rtg-yang-coord@ietfa.amsl.com>;
Thu, 14 May 2015 11:07:37 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com
[IPv6:2607:f8b0:4001:c05::236])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id D326C1A8ACC
for <Rtg-yang-coord@ietf.org>; Thu, 14 May 2015 11:07:36 -0700 (PDT)
Received: by igbyr2 with SMTP id yr2so174146495igb.0
for <Rtg-yang-coord@ietf.org>; Thu, 14 May 2015 11:07:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=content-type:mime-version:subject:from:in-reply-to:date:cc
:content-transfer-encoding:message-id:references:to;
bh=/2j+pJPteqAb8NeQ/H7irP045/t4o2omlQHB3BepKAA=;
b=E81PU+pQKDA/UxnHy9a2FdL9Aefry8N3xw0PyuUtDThQym+eCFRGJ0fBHFNJaigcva
UT8u6EObmeGieJ9BKMqgxzjhhuDAJ7Xnt2iyrD4orxNzemMbaLV/atTegGUL0XHtJnBp
ptABSTHCcf2gnhYcl9fCAtab/woYHNFEg++ub447lrgXSb61cUoDYs9aplEsVHM0csmt
+PrbE/fX6BXCM0UowT2OFWmekZGWuUQU8kjcI15ojGHsE941Zb5x/fZY/0auUNUKOIAQ
Q8/tPVtF4u82Ep0cdM6kfei4aUNKsN7lZ8G5Z6bk4Ker/bCt1sb02SW4xTOI/ng8m9Ky
0BRA==
X-Received: by 10.43.39.1 with SMTP id tk1mr14399508icb.26.1431626856345;
Thu, 14 May 2015 11:07:36 -0700 (PDT)
Received: from ?IPv6:2620::1000:3202:94a5:c8:2f94:7c5d?
([2620:0:1000:3202:94a5:c8:2f94:7c5d])
by mx.google.com with ESMTPSA id p74sm16980534ioe.27.2015.05.14.11.07.35
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Thu, 14 May 2015 11:07:35 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: aldrin ietf <aldrin.ietf@gmail.com>
In-Reply-To: <D481ED34-84C4-455D-8CE5-36D01A5264CC@lucidvision.com>
Date: Thu, 14 May 2015 11:07:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2C72B0F-C0EE-4700-B89D-F895EBAE9A4F@gmail.com>
References: <D177E7E1.1AC4C%acee@cisco.com>
<CAJK7ZqLp4_dOVMcSMXP3juZHHeQJ6iLGkryJ8t6gs2Mcn=Ez5Q@mail.gmail.com>
<20150513103509.GA59689@elstar.local>
<D481ED34-84C4-455D-8CE5-36D01A5264CC@lucidvision.com>
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/-TvPIpNPRC40cmJfb9RSdtsoAIk>
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>,
"Acee Lindem \(acee\)" <acee@cisco.com>, Anees Shaikh <aashaikh@google.com>,
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>,
Xufeng Liu <xufeng.liu@ericsson.com>
Subject: Re: [Rtg-yang-coord] Operational State Modeling
X-BeenThere: rtg-yang-coord@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "\"List to discuss coordination between the Routing related YANG
models\"" <rtg-yang-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-yang-coord>,
<mailto:rtg-yang-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-yang-coord/>
List-Post: <mailto:rtg-yang-coord@ietf.org>
List-Help: <mailto:rtg-yang-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-yang-coord>,
<mailto:rtg-yang-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2015 18:07:38 -0000
That is the case we are making with openconfig model. Details are in the draft on why it is helpful from operational perspective. One do not want to create standards which are not operationally effective. -sam > On May 13, 2015, at 6:13 AM, Thomas D. Nadeau <tnadeau@lucidvision.com> wrote: > > > Speaking as an individual, while what Juergen says is true, that does not mean that existing models can never be refactored. > > —Tom > > >> On May 13, 2015:6:35 AM, at 6:35 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote: >> >> On Wed, May 13, 2015 at 12:51:41AM -0700, Anees Shaikh wrote: >>> >>> Regarding compatibility with existing models, I really don't agree at all >>> that the existing RFC models should constrain what we do when trying to >>> meet the requirements of people trying to build real systems that use YANG >>> models. With all respect to the authors of those few models (which we >>> leverage considerably in our models), YANG models are software code, and >>> should be treated as such IMO. We don't say that software is "done" and >>> can't change -- it evolves and improves over time, sometimes in >>> non-backward-compatible ways. And we don't issue a final version of >>> software without considerable experience using and testing it in production. >>> >> >> Standards and software are not the same. The value of standards is >> that they provide a stable basis. In other words, the value of >> standards is that they do not change every other day. Yes, you can >> rewrite standardized data models but the cost of doing so is high and >> hence the benefit of rewriting something must be high. I do not see >> this here - not even remotely. >> >> /js >> >> -- >> 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/> >> >> _______________________________________________ >> Rtg-yang-coord mailing list >> Rtg-yang-coord@ietf.org >> https://www.ietf.org/mailman/listinfo/rtg-yang-coord >> > > _______________________________________________ > Rtg-yang-coord mailing list > Rtg-yang-coord@ietf.org > https://www.ietf.org/mailman/listinfo/rtg-yang-coord
- [Rtg-yang-coord] Operational State Modeling Xufeng Liu
- Re: [Rtg-yang-coord] Operational State Modeling Russ White
- Re: [Rtg-yang-coord] Operational State Modeling Juergen Schoenwaelder
- Re: [Rtg-yang-coord] Operational State Modeling Acee Lindem (acee)
- Re: [Rtg-yang-coord] Operational State Modeling Anees Shaikh
- Re: [Rtg-yang-coord] Operational State Modeling Juergen Schoenwaelder
- Re: [Rtg-yang-coord] Operational State Modeling Thomas D. Nadeau
- Re: [Rtg-yang-coord] Operational State Modeling Andy Bierman
- Re: [Rtg-yang-coord] Operational State Modeling Xufeng Liu
- Re: [Rtg-yang-coord] Operational State Modeling Xufeng Liu
- Re: [Rtg-yang-coord] Operational State Modeling aldrin ietf
- Re: [Rtg-yang-coord] Operational State Modeling Anees Shaikh
- Re: [Rtg-yang-coord] Operational State Modeling Juergen Schoenwaelder
- Re: [Rtg-yang-coord] Operational State Modeling Christian Hopps
- Re: [Rtg-yang-coord] Operational State Modeling Ladislav Lhotka
- Re: [Rtg-yang-coord] Operational State Modeling Juergen Schoenwaelder
- Re: [Rtg-yang-coord] Operational State Modeling Acee Lindem (acee)
- Re: [Rtg-yang-coord] Operational State Modeling Nadeau Thomas
- Re: [Rtg-yang-coord] Operational State Modeling Andy Bierman
- Re: [Rtg-yang-coord] Operational State Modeling aldrin ietf
- Re: [Rtg-yang-coord] Operational State Modeling Juergen Schoenwaelder
- Re: [Rtg-yang-coord] Operational State Modeling Nadeau Thomas
- Re: [Rtg-yang-coord] Operational State Modeling aldrin ietf