Re: [Rtg-yang-coord] naive question ??
Loa Andersson <loa@pi.nu> Fri, 06 February 2015 05:07 UTC
Return-Path: <loa@pi.nu>
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 8E8FF1A0393
for <rtg-yang-coord@ietfa.amsl.com>; Thu, 5 Feb 2015 21:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 wHRm18O3cICv for <rtg-yang-coord@ietfa.amsl.com>;
Thu, 5 Feb 2015 21:07:40 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141])
(using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 004F41A039C
for <Rtg-yang-coord@ietf.org>; Thu, 5 Feb 2015 21:07:39 -0800 (PST)
Received: from [192.168.1.12] (unknown [49.149.205.111])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested) (Authenticated sender: loa@pi.nu)
by pipi.pi.nu (Postfix) with ESMTPSA id A78EB18013E4;
Fri, 6 Feb 2015 06:07:36 +0100 (CET)
Message-ID: <54D44C11.2080902@pi.nu>
Date: Fri, 06 Feb 2015 13:07:29 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64;
rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Thomas D. Nadeau" <tnadeau@lucidvision.com>
References: <54D34B47.1050507@pi.nu>
<D907FC42-80C2-48EB-B756-8F19195ECF39@lucidvision.com>
In-Reply-To: <D907FC42-80C2-48EB-B756-8F19195ECF39@lucidvision.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-yang-coord/LQS_YTVZnYBljuGjw2wyg400zgE>
Cc: Rtg-yang-coord@ietf.org
Subject: Re: [Rtg-yang-coord] naive question ??
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, 06 Feb 2015 05:07:44 -0000
Tom, On 2015-02-05 20:27, Thomas D. Nadeau wrote: > >> On Feb 5, 2015:5:51 AM, at 5:51 AM, Loa Andersson <loa@pi.nu> wrote: >> >> Folks, >> >> I have what might be a naive question. >> >> People have told me that in Yang we want to separate functionality from >> technology, i.e. we will look at OAM, management, routing, signaling >> and traffic engineering as aggregate functions and build our tree based >> on that. >> >> Now if we are to model thing that are closely related e.g. MPLS OAM, >> signaling, routing and traffic engineering, does that mean that we have >> to work at separate pieces of the yang tree and repeat this for every >> piece of the technology? > > I think you can do a model dedicated to MPLS OAM. The analogy is > pretty much similar to how MIBs are created. You can import bits or > objects from all over the place to create things, or you can recreate them > in place. There is a trade-off about modularity versus time-to-completion > here and I very much am not in favor of being zealous one way or the other. > > We also need to very much take an iterative process around these models: > they are not set in stone, and we should iterate on them to modify, adapt > and update them as necessary. With that in mind, we've been encouraging people to > just starting writing them as best as possible and implementing either prototype > code or actually putting them into products so that we can see how they actually > operate in the wild. I thought there were activities going on to define an overall IETF yang model, right? If we say we approach this in an iterative way would the overall yang-model be the outcome of that process, rather than an input to it. Or do I miss something? /Loa > > --Tom > > >> First, is this correctly understood or do I have to go back and discuss >> this again with the people proposing it? >> >> If it is correct why is it superior to what we did for SNMP, one MIB-module for each protocol? >> >> Are the decisions taken or is the jury still out? >> >> /Loa >> -- >> >> >> Loa Andersson email: loa@mail01.huawei.com >> Senior MPLS Expert loa@pi.nu >> Huawei Technologies (consultant) phone: +46 739 81 21 64 >> >> _______________________________________________ >> Rtg-yang-coord mailing list >> Rtg-yang-coord@ietf.org >> https://www.ietf.org/mailman/listinfo/rtg-yang-coord >> > -- Loa Andersson email: loa@mail01.huawei.com Senior MPLS Expert loa@pi.nu Huawei Technologies (consultant) phone: +46 739 81 21 64
- Re: [Rtg-yang-coord] naive question ?? Loa Andersson
- Re: [Rtg-yang-coord] naive question ?? Thomas D. Nadeau
- Re: [Rtg-yang-coord] naive question ?? Loa Andersson
- [Rtg-yang-coord] naive question ?? Loa Andersson
- Re: [Rtg-yang-coord] naive question ?? Thomas D. Nadeau
- Re: [Rtg-yang-coord] naive question ?? t.petch
- Re: [Rtg-yang-coord] naive question ?? Dean Bogdanovic
- Re: [Rtg-yang-coord] naive question ?? Thomas D. Nadeau
- Re: [Rtg-yang-coord] naive question ?? Qin Wu