IETF Logo Mail Archive

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

Andy Bierman <andy@yumaworks.com> Fri, 15 May 2015 16:28 UTC

Return-Path: <andy@yumaworks.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 4FA5B1A1B65 for <rtg-yang-coord@ietfa.amsl.com>; Fri, 15 May 2015 09:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level:
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, 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 6hfc1XHexSu0 for <rtg-yang-coord@ietfa.amsl.com>; Fri, 15 May 2015 09:28:45 -0700 (PDT)
Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) (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 718B51A1BC8 for <Rtg-yang-coord@ietf.org>; Fri, 15 May 2015 09:28:45 -0700 (PDT)
Received: by lagv1 with SMTP id v1so127425077lag.3 for <Rtg-yang-coord@ietf.org>; Fri, 15 May 2015 09:28:44 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=M/Ztv8ybH1RKglQ7TzrOjOr6aRhMEv/C7+G1NlFWeh8=; b=DQ/Ybm1lt0ISuaJ6XIgDbd1CVyZ/pF7Lj7cR8nKypOWD2PMc9Qb1uXnHBR4nNK11wU SJQGQOLkzOA7N8wxqnlG0dLYDYiBVqVAdjdp19IApweomdLyF9QBe4RfHfPAKc3U9s6V 6xbh3XsCJgobKX6ct+6Cn73hWxmI4PuwHDJfAW2AN40J+iO1k/28yCO/zQygAavz62F6 JEmMvaZx6361Rg84gzIoAu6hQNVsRqrRXZA6He4QCmQ/uEMUTrJpuQk6lcr1mjLz9RJG QKZ038D9F5rZ0FY8Me4UoWIgm6ApJTVtb3UXOWTDzmkzRGf4tomXs11AX/HCoqfGsXJ5 fVSQ==
X-Gm-Message-State: ALoCoQlKfnb2Gi9GekJ/xSLwgCeX4Z0R5gunH5qiZyTXXrhrjjrahzEBNI5L1bfnSJEmbNDrC/ES
MIME-Version: 1.0
X-Received: by 10.152.8.231 with SMTP id u7mr4252496laa.37.1431707323943; Fri, 15 May 2015 09:28:43 -0700 (PDT)
Received: by 10.112.200.102 with HTTP; Fri, 15 May 2015 09:28:43 -0700 (PDT)
In-Reply-To: <0EDEDDB6-40EA-47AF-AA5A-E7212445CCF8@lucidvision.com>
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> <0EDEDDB6-40EA-47AF-AA5A-E7212445CCF8@lucidvision.com>
Date: Fri, 15 May 2015 09:28:43 -0700
Message-ID: <CABCOCHQYr=-MV=5Mwsj1puDYU24pEnpmF-EcdYb-w-dj0=qTVw@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Nadeau Thomas <tnadeau@lucidvision.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/fg2sN9M3drbpqPYvP4-5ERlJXNA>
Cc: "Rtg-yang-coord@ietf.org" <Rtg-yang-coord@ietf.org>, "Acee Lindem \(acee\)" <acee@cisco.com>, Xufeng Liu <xufeng.liu@ericsson.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Anees Shaikh <aashaikh@google.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 16:28:47 -0000

On Fri, May 15, 2015 at 9:14 AM, Nadeau Thomas <tnadeau@lucidvision.com> wrote:
>
>         I don’t think the open config guys are asking for refactoring for purely aesthetic reasons. These guys operate some of the world’s largest networks with tens of thousands of devices, so I’d hope that their asking to move things around is in order to make interacting with those things at that scale better.
>


I think Juergen and I and others are pointing out that it
would be better to solve this problem by adding an
operation to NETCONF.  RESTCONF already has the
ability to retrieve just "content=nonconfig".

Replicating config as operational state in all the data models
is not a good idea.  Using arbitrary NP containers called
"config" and "state" (instead of the YANG config-stmt)
is not a good idea.


>         —Tom

Andy

>
>
>> On May 15, 2015:4:52 AM, at 4:52 AM, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
>>
>> 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.
>>
>> /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

v2.8.7 | Report a Bug | By Email