Re: [netmod] Comment on draft-clacla-netmod-yang-model-update-02

Martin Bjorklund <mbj@tail-f.com> Wed, 15 November 2017 11:17 UTC

Return-Path: <mbj@tail-f.com>
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 6B9DE12711E for <netmod@ietfa.amsl.com>; Wed, 15 Nov 2017 03:17:20 -0800 (PST)
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 DIf_vaKCt-0v for <netmod@ietfa.amsl.com>; Wed, 15 Nov 2017 03:17:18 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id E32BF126B6E for <netmod@ietf.org>; Wed, 15 Nov 2017 03:17:17 -0800 (PST)
Received: from localhost (h-40-225.A165.priv.bahnhof.se [94.254.40.225]) by mail.tail-f.com (Postfix) with ESMTPSA id 0F14A1AE0311; Wed, 15 Nov 2017 12:17:17 +0100 (CET)
Date: Wed, 15 Nov 2017 12:17:16 +0100
Message-Id: <20171115.121716.454716475078719607.mbj@tail-f.com>
To: balazs.lengyel@ericsson.com
Cc: jclarke@cisco.com, netmod@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <55fcf67e-6e27-4bd9-cdd6-62f3fbe11bff@ericsson.com>
References: <9094b945-366f-145d-fbc1-5cf116f4a3bc@cisco.com> <20171115.095341.1585161898755400575.mbj@tail-f.com> <55fcf67e-6e27-4bd9-cdd6-62f3fbe11bff@ericsson.com>
X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/K0NryNuaFxGXd5V1212_QHkTL4Y>
Subject: Re: [netmod] Comment on draft-clacla-netmod-yang-model-update-02
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 15 Nov 2017 11:17:20 -0000

Balazs Lengyel <balazs.lengyel@ericsson.com> wrote:
> The server MAY implement obsoleted nodes or MAY NOT. This may or may
> not  is not good enough as a contract for the management client.  My
> problem is that the current solution is just not good enough. IMHO we
> need to change it.

Note that if a server implements version 1 of a module, and then the
module doesn't change, but the server in the next sw version drops
support for the module, the client will also be unhappy.  We (the
IETF) can't have rules for these kinds of things.

> Even after semver you can still obsolete the old stuff and provide the
> new stuff with a new name, although that might not be the common
> practice.  Which is a good thing, as I believe it is sometimes better
> to correct existing definitions then to replace them.

But you still want to require servers to implement even obsolete
nodes?


/martin


> 
> regards Balazs
> 
> 
> On 2017-11-15 16:53, Martin Bjorklund wrote:
> > Exactly.  With the current solution, the sever can still implement the
> > deprecated or obsolete nodes in order to support old clients.
> >
> > With a MAJOR update in a semver world, it means that the old nodes are
> > removed (or rather, possibly, that the old nodes have new syntax
> > and/or semantics).
> >
> >
> >
> 
> -- 
> Balazs Lengyel                       Ericsson Hungary Ltd.
> Senior Specialist
> Mobile: +36-70-330-7909 email: Balazs.Lengyel@ericsson.com
>