Re: [netmod] questions about draft-rtgyangdt-rtgwg-device-model-00

Nadeau Thomas <> Wed, 26 August 2015 11:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4A0151B2BBD; Wed, 26 Aug 2015 04:35:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Status: No, score=-2.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id haUUOFyhpekj; Wed, 26 Aug 2015 04:35:21 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id F07C51B2B87; Wed, 26 Aug 2015 04:35:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=default; t=1440588857; bh=yi+pMUw/GEuLDSXalIKxeYNHADfUFG52Js0uf72qoBk=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=TwmUL18qcsNDCEBuV77GUc/aEZi/gxuXONIt1xifOKWbx5nn1/JQwsNc6V3C8laY8 kQ2xPcII0QXp5OUET69Nv9MPPDTAXTRC6jHe76z1U1wZCE8IB3+JJVcjt9LY0tqYOE 0rI5yoIfF3fGiZRGmFzpnV4wJTGaFpdDKgbffdbc=
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=;
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: [netmod] questions about draft-rtgyangdt-rtgwg-device-model-00
From: Nadeau Thomas <>
In-Reply-To: <>
Date: Wed, 26 Aug 2015 07:35:21 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <20150826064030.GB84416@elstar.local> <> <>
To: Martin Bjorklund <>
X-Mailer: Apple Mail (2.2104)
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=4 Stars=0 Good=0 Friend=0 Surbl=0 Catch=0 r=0 ip=
X-IP-stats: Notspam Incoming Last 0, First 103, in=1145, out=0, spam=0 Known=true ip=
Archived-At: <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 26 Aug 2015 11:35:23 -0000

> On Aug 26, 2015:6:26 AM, at 6:26 AM, Martin Bjorklund <>; wrote:
> "Acee Lindem (acee)" <>; wrote:
>> On 8/26/15, 2:40 AM, "Juergen Schoenwaelder"
>> <>; wrote:
>>> On Tue, Aug 25, 2015 at 10:53:55PM -0400, Lou Berger wrote:
>>>>> Hopefully, a decision to change all existing models (including vendor
>>>>> models!) will be based on something more technical than the fact that
>>>>> a group of people "really like it" some other way.
>>>> I'm equally unsure that having an argument of "I got there first" is a
>>>> compelling argument given the number of folks (including vendors) who
>>>> have stated willingness (or even support) for change.  I think having a
>>>> major class of users stand up and say this is important should garner
>>>> some notice.
>>> Please keep in mind that we are talking about several published
>>> proposed standards that have been implemented and deployed. I think
>>> there must be convincing technical reasons to declare them broken and
>>> to redo them.
>> Other than adding /device at the top, we are not obsoleting RFC
>> 7223.
> This doesn't make sense.  The YANG model is the contract.  You are
> proposing changing the contract.  The fact is that you will be
> obsoleting 7223 (and the other RFCs).  Existing devices and
> applications will have to change in order to handle this new top-level
> node (which will be in some other namespace I presume, unless your
> proposal is one gigantic monolithic model).
> /martin

	Again I will ask: why is this bad?  Obviously the implementation will have to 
evolve to the new models, but is this relatively static model where we really want to 
get to simply because some device vendors/server vendors find it a pain to iterate
models to support the latest versions?  Again, others have figured out how to do this
much more rapidly.  In the past we have seen what happens to things that cannot evolve
fast enough...


> _______________________________________________
> netmod mailing list