IETF Logo Mail Archive

Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00

Christian Hopps <chopps@chopps.org> Sun, 29 July 2018 05:07 UTC

Return-Path: <chopps@chopps.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDA0130DCC for <netmod@ietfa.amsl.com>; Sat, 28 Jul 2018 22:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 3HbyvuomRMFG for <netmod@ietfa.amsl.com>; Sat, 28 Jul 2018 22:07:19 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id C58A01274D0 for <netmod@ietf.org>; Sat, 28 Jul 2018 22:07:19 -0700 (PDT)
Received: from [192.168.2.5] (47-50-69-38.static.klmz.mi.charter.com [47.50.69.38]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 00BB4635D3; Sun, 29 Jul 2018 05:07:18 +0000 (UTC)
From: Christian Hopps <chopps@chopps.org>
Message-Id: <D56FEDDE-6078-41DF-94F2-9B1B43EEA4FC@chopps.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_D058B0C7-EAFB-4E75-84E7-ACC0DD8393F1"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Sun, 29 Jul 2018 01:07:17 -0400
In-Reply-To: <CABCOCHQdwqB78JgNdB_UvhDTz5W-RM3XHajrhCQAgogj4T2VHQ@mail.gmail.com>
Cc: Christian Hopps <chopps@chopps.org>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, NetMod WG <netmod@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <CABCOCHQ47ztJTPaZMZK7FWHsRPk1jN6SuuAWtg08rmtVgUPEWw@mail.gmail.com> <87va981svk.fsf@chopps.org> <CABCOCHSkpn_=04qJP9m6TUA+doCjk0=BFG6jX9T4awj+CO-QdA@mail.gmail.com> <87tvos1cse.fsf@chopps.org> <20180724092908.ed36loiv3zrivs5d@anna.jacobs.jacobs-university.de> <CABCOCHQdwqB78JgNdB_UvhDTz5W-RM3XHajrhCQAgogj4T2VHQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/tWOxl_ULTT5WFTznAYFz-NlumTY>
Subject: Re: [netmod] backward compatibility requirements in draft-verdt-netmod-yang-versioning-reqs-00
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Jul 2018 05:07:21 -0000

One answer to a slightly more general version of this question (why is OK for the clients to do nothing while the servers do the work) is that the client developers are often the server developers customers, they pay the bills.

Also in general there is a one to many mapping from a server to it's clients, the overall cost of updating a server and of it supporting multiple versions or transforming or whatever is much less than the overall cost of all the users of that server updating their client software.

I'm not advocating for clients never updating, but I think it's unreasonable to think that clients will be updating as fast as servers, or to design a versioning scheme that assumes anything like that.

Thanks,
Chris.

> On Jul 24, 2018, at 11:11 AM, Andy Bierman <andy@yumaworks.com> wrote:
> 
> Why is it OK for the client developer to decide "we are sticking with the
> defective version of the module and not going to upgrade to
> the fixed version like the server developers have done."
>

v2.23.0 | Report a Bug | By Email