IETF Logo Mail Archive

Re: [Rtg-yang-coord] Operational State Modeling

Ladislav Lhotka <lhotka@nic.cz> Fri, 15 May 2015 13:56 UTC

Return-Path: <lhotka@nic.cz>
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 464B01A90A5 for <rtg-yang-coord@ietfa.amsl.com>; Fri, 15 May 2015 06:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.661
X-Spam-Level:
X-Spam-Status: No, score=-0.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904, T_RP_MATCHES_RCVD=-0.01] autolearn=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 PmeMW8n797Ie for <rtg-yang-coord@ietfa.amsl.com>; Fri, 15 May 2015 06:56:32 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B6131A8F48 for <Rtg-yang-coord@ietf.org>; Fri, 15 May 2015 06:56:31 -0700 (PDT)
Received: from birdie.labs.nic.cz (unknown [195.113.220.110]) by mail.nic.cz (Postfix) with ESMTPSA id EC37B140AE0; Fri, 15 May 2015 15:56:28 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nic.cz; s=default; t=1431698189; bh=Nwzb/zZwVkrjwuOpw+uHP0Dkh0MS+q/4WbfaxjhYSEU=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=jm36THhPQ5KlXaBkCBpKZQa5S6Ttwubbf+etc/656DYgFFSX2Rm1syssR6cXs2Utr bvjNKet3ZMx/rMjPF08a5UYpfHPSnIQgbUoTx9zjeL5i0PL3aQbc8FP7W6NkEvvAfL 2R3/0Mspt4Fp+xchwooD/X8UMYNNt9dbqVnqHeic=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <87h9revub1.fsf@chopps.org>
Date: Fri, 15 May 2015 15:56:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E69983B-7B42-4F35-B46E-832E7576DBA9@nic.cz>
References: <D177E7E1.1AC4C%acee@cisco.com> <CAJK7ZqLp4_dOVMcSMXP3juZHHeQJ6iLGkryJ8t6gs2Mcn=Ez5Q@mail.gmail.com> <20150513103509.GA59689@elstar.local> <D481ED34-84C4-455D-8CE5-36D01A5264CC@lucidvision.com> <20150515085228.GA4024@elstar.local> <87h9revub1.fsf@chopps.org>
To: Christian Hopps <chopps@chopps.org>
X-Mailer: Apple Mail (2.2098)
X-Virus-Scanned: clamav-milter 0.98.6 at mail
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/MZ6ooyygwAvVXw4ys3dA_ze36Gk>
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, Thomas Nadeau <tnadeau@lucidvision.com>, Anees Shaikh <aashaikh@google.com>, =?utf-8?Q?J=C3=BCrgen_Sch=C3=B6nw=C3=A4lder?= <j.schoenwaelder@jacobs-university.de>, "Acee Lindem \(acee\)" <acee@cisco.com>, 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: Fri, 15 May 2015 13:56:34 -0000

> On 15 May 2015, at 15:34, Christian Hopps <chopps@chopps.org> wrote:
> 
> 
> Juergen Schoenwaelder writes:
> 
>> On Wed, May 13, 2015 at 09:13:37AM -0400, Thomas D. Nadeau wrote:
>>> 
>>> 	Speaking as an individual, while what Juergen says is true, that does not mean that existing models can never be refactored. 
>>> 
>> 
>> Refactoring for the sake of 'it looks nicer' (for some definition of
>> nice) likely does not meet the bar. We are talking about APIs here
>> with multiple independent implementations and applications sitting on
>> top of these APIs.
> 
> 
> Isn't the idea to create a common standard way to access state and
> config? If so I don't think that qualifies as "it looks nicer", rather
> it allows for creating generic code one time that works on any model
> including as yet unwritten ones vs. custom code for each model.

Well, the existing modules do propose a way to access state and config. It’s not perfect and perhaps some changes in YANG are needed as well in order to better support the interaction of config and state.

However, I agree with Juergen that the arguments presented so far in favour of leaf-level duplication aren’t very convincing. 

Lada

> 
> Thanks,
> Chris.
> 
> 
>> 
>> /js
> 
> _______________________________________________
> Rtg-yang-coord mailing list
> Rtg-yang-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/rtg-yang-coord

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: E74E8C0C

v2.8.7 | Report a Bug | By Email