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

Nadeau Thomas <tnadeau@lucidvision.com> Wed, 26 August 2015 13:19 UTC

Return-Path: <tnadeau@lucidvision.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A02E1A8AF4; Wed, 26 Aug 2015 06:19:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.012
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5soeHASOBg7F; Wed, 26 Aug 2015 06:19:47 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [64.71.170.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EEAD1AC41D; Wed, 26 Aug 2015 06:19:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucidvision.com; s=default; t=1440595118; bh=1uQO1Zi8/Qk7nDb8X7EPkeBAxFhVnEvKyXvYmH0bQvQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=yy6AD7j8EQ3liNOh5msAQ/HavXoTdfP7Rw3yfYANx365uHEiEnYbNE3DyIeoIoa6e 1K35Og+H45qBFjPZ1FTKbrp6q0xshxFAtMIBuFxOGT3EUD5nB4tMVkfTHvTA9H0CNB IXa/RuM7g7JtKjW3+idcO08NOzX+3D0BQtEQKxrU=
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.255.148.181;
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 <tnadeau@lucidvision.com>
In-Reply-To: <20150826.140918.2163222167742824482.mbj@tail-f.com>
Date: Wed, 26 Aug 2015 09:19:43 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1E22528-EE8A-4CC3-914F-6D7DED994416@lucidvision.com>
References: <D203014F.2CA9C%acee@cisco.com> <20150826.122600.1110046163132211535.mbj@tail-f.com> <19CCF9F5-87F1-4C41-8151-18AD36D98CE6@lucidvision.com> <20150826.140918.2163222167742824482.mbj@tail-f.com>
To: Martin Bjorklund <mbj@tail-f.com>
X-Mailer: Apple Mail (2.2104)
X-Authenticated-User: tnadeau@lucidvision.com
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-ShareWhite: 50.255.148.181
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=10 Stars=0 Good=0 Friend=0 Surbl=0 Catch=0 r=0 ip=50.255.148.181
X-IP-stats: Notspam Incoming Last 0, First 103, in=1151, out=0, spam=0 Known=true ip=50.255.148.181
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/X5MtQ2mtCHvDi4m18wga0wa8v5k>
Cc: netmod@ietf.org, draft-rtgyangdt-rtgwg-device-model@ietf.org, rtgwg@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Aug 2015 13:19:49 -0000

> On Aug 26, 2015:8:09 AM, at 8:09 AM, Martin Bjorklund <mbj@tail-f.com>; wrote:
> 
> Nadeau Thomas <tnadeau@lucidvision.com>; wrote:
>> 
>>> On Aug 26, 2015:6:26 AM, at 6:26 AM, Martin Bjorklund <mbj@tail-f.com>;
>>> wrote:
>>> 
>>> "Acee Lindem (acee)" <acee@cisco.com>; wrote:
>>>> 
>>>> 
>>>> On 8/26/15, 2:40 AM, "Juergen Schoenwaelder"
>>>> <j.schoenwaelder@jacobs-university.de>; 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?
> 
> My point above was in reply to the statement that "we are not
> obsoleting RFC 7223" [because the change is so small?] - you would in
> fact be obsoleting the model in 7223.
> 
> 
> /martin

	The flip side to this is that while you evolve the model 
in 7223, you evolve it rapidly and to conform to the newer model(s).
The older model does actually still exist, and if we have a way to
refer back to it its not really obsolete; its just an older revision.

	—Tom