Re: [netmod] Obsolete feature - what does it mean?
Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Wed, 27 February 2019 16:48 UTC
Return-Path: <j.schoenwaelder@jacobs-university.de>
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 A002E130EA7 for <netmod@ietfa.amsl.com>; Wed, 27 Feb 2019 08:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 A1iFaTQ66lxn for <netmod@ietfa.amsl.com>; Wed, 27 Feb 2019 08:48:21 -0800 (PST)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71C74130EE5 for <netmod@ietf.org>; Wed, 27 Feb 2019 08:48:19 -0800 (PST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 293617B7; Wed, 27 Feb 2019 17:48:18 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id LheQjPBYZACQ; Wed, 27 Feb 2019 17:48:18 +0100 (CET)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Wed, 27 Feb 2019 17:48:18 +0100 (CET)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by hermes.jacobs-university.de (Postfix) with ESMTP id 1271B20067; Wed, 27 Feb 2019 17:48:18 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10028) with ESMTP id z9W06yfXVjef; Wed, 27 Feb 2019 17:48:17 +0100 (CET)
Received: from exchange.jacobs-university.de (sxchmb04.jacobs.jacobs-university.de [10.70.0.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "exchange.jacobs-university.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by hermes.jacobs-university.de (Postfix) with ESMTPS id B4EBF20064; Wed, 27 Feb 2019 17:48:17 +0100 (CET)
Received: from anna.localdomain (10.50.218.117) by sxchmb03.jacobs.jacobs-university.de (10.70.0.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.1591.10; Wed, 27 Feb 2019 17:48:17 +0100
Received: by anna.localdomain (Postfix, from userid 501) id EBFCE3006D411F; Wed, 27 Feb 2019 17:48:16 +0100 (CET)
Date: Wed, 27 Feb 2019 17:48:16 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Kent Watsen <kent@watsen.net>
CC: Balázs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
Message-ID: <20190227164816.tlfqg4voabtdk7ey@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Kent Watsen <kent@watsen.net>, Balázs Lengyel <balazs.lengyel@ericsson.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <d0f6a34d-9218-b09b-5e9c-1747b1b780dc@ericsson.com> <20190227103303.emm3xj372rb7fx7t@anna.jacobs.jacobs-university.de> <2035f82c-bc0c-e5bb-40f2-efa6dcef6bde@ericsson.com> <010001692fb7a0c6-9a9ecc8c-f0b0-413c-92eb-30ea0d4b1834-000000@email.amazonses.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
In-Reply-To: <010001692fb7a0c6-9a9ecc8c-f0b0-413c-92eb-30ea0d4b1834-000000@email.amazonses.com>
User-Agent: NeoMutt/20180716
X-ClientProxiedBy: SXCHMB03.jacobs.jacobs-university.de (10.70.0.155) To sxchmb03.jacobs.jacobs-university.de (10.70.0.155)
X-Clacks-Overhead: GNU Terry Pratchett
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/OXvygOjFFzajr-dEuT2JdOSbs2Y>
Subject: Re: [netmod] Obsolete feature - what does it mean?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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, 27 Feb 2019 16:48:23 -0000
On Wed, Feb 27, 2019 at 04:09:17PM +0000, Kent Watsen wrote: > > > > On Feb 27, 2019, at 6:16 AM, Balázs Lengyel <balazs.lengyel@ericsson.com> wrote: > > > > feature oldFeature { > > status obsolete; > > } > > leaf myTimer { > > if-feature oldFeature ; > > mandatory true; > > config true; > > status current; > > type string; > > } > > So should I configure myTimer or not? I assume yes, correct? > > This issue is captured here: https://github.com/netmod-wg/yang-next/issues/27, which was updated as of this morning with this very example. > > Of course, the problem is in RFC 7950: > > o "obsolete" means that the definition is obsolete and SHOULD NOT be > implemented and/or can be removed from implementations. > > I recommend replacing "SHOULD NOT be implemented" with "is not implemented". When an IETF WG decides to obsolete something, I am forced to break old clients because of this decision? Note sure this makes business sense (says an academic). There is a huge difference between modules where the implementors have change control over the modules and modules where change control is far outside the implementors hands and where clients and servers are implemented by different organizations in an open and largely uncoordinated way. We always have to keep this in mind when we create rules. The SHOULD NOT allows a server implementor to take a well-informed decision that there are old clients you care about and that this makes a business case for supporting obsolete definitions on a server. Another aspect here is that we do not make a clear distinction between server and client. It can very well be that "deprecated" and "obsolete" mean slightly different things to servers and clients. (Servers tend to have a natural desire to not break clients unnecessarily.) /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
- [netmod] Obsolete feature - what does it mean? Balázs Lengyel
- Re: [netmod] Obsolete feature - what does it mean? Juergen Schoenwaelder
- Re: [netmod] Obsolete feature - what does it mean? Balázs Lengyel
- Re: [netmod] Obsolete feature - what does it mean? Juergen Schoenwaelder
- Re: [netmod] Obsolete feature - what does it mean? Kent Watsen
- Re: [netmod] Obsolete feature - what does it mean? Juergen Schoenwaelder
- Re: [netmod] Obsolete feature - what does it mean? Andy Bierman
- Re: [netmod] Obsolete feature - what does it mean? Kent Watsen
- Re: [netmod] Obsolete feature - what does it mean? Randy Presuhn
- Re: [netmod] Obsolete feature - what does it mean? Kent Watsen
- Re: [netmod] Obsolete feature - what does it mean? Rob Wilton (rwilton)
- Re: [netmod] Obsolete feature - what does it mean? Rob Wilton (rwilton)