Re: [netmod] Does defining a feature require the module be implemented?

Jan Lindblad <janl@tail-f.com> Thu, 19 May 2022 05:52 UTC

Return-Path: <janl@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 8EF3CC26D47E for <netmod@ietfa.amsl.com>; Wed, 18 May 2022 22:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZo_aWO-x-Ep for <netmod@ietfa.amsl.com>; Wed, 18 May 2022 22:52:54 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1F1DFC26D47F for <netmod@ietf.org>; Wed, 18 May 2022 22:52:53 -0700 (PDT)
Received: from smtpclient.apple (213-67-237-150-no99.tbcn.telia.com [213.67.237.150]) by mail.tail-f.com (Postfix) with ESMTPSA id 6A3F01AE0A76; Thu, 19 May 2022 07:52:51 +0200 (CEST)
From: Jan Lindblad <janl@tail-f.com>
Message-Id: <05CB1C91-1551-43AF-9D4B-725E998128E9@tail-f.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FD84B7FE-EA8E-4BAB-93DC-457C93DEA699"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Date: Thu, 19 May 2022 07:52:50 +0200
In-Reply-To: <CABCOCHT8URJeGJc_Jy7rePqVKjmSUuyPLCBh640WL7UiOpnPpQ@mail.gmail.com>
Cc: Kent Watsen <kent+ietf@watsen.net>, "netmod@ietf.org" <netmod@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <01000180a9eb37cb-85b9c576-c1eb-425a-b42c-b3cabe548fbb-000000@email.amazonses.com> <20220518.080543.825575420363032441.id@4668.se> <01000180d793d6ee-f82a4a03-28d8-4f8b-909e-7306a7fc565b-000000@email.amazonses.com> <CABCOCHT8URJeGJc_Jy7rePqVKjmSUuyPLCBh640WL7UiOpnPpQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/jsdhOm07qrgKdJLiTK38DYz3vrY>
Subject: Re: [netmod] Does defining a feature require the module be implemented?
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.34
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: Thu, 19 May 2022 05:52:58 -0000

Andy wrote:

> A server can support a module without any protocol-accessible objects in 3 ways
>    - implement the module with no features supported
>    - implement the module with features supported
>    - import the module without implementing it
> 
> To Martin's point, it is not clear that a client is harmed because a server lists a module in
> the 'module' list instead of the 'import-only-module' list.
> 
> 
> Andy

I just want to attest to the real world harm it causes when a server lists a module M in the modules list when it doesn't actually support it.

The client then has to believe it is reasonable to issue a get-config request for the contents of module M. But when it does, the server then responds with an error, and the automation breaks down. The problem is cured by the server listing the non-implemented module M as an import-only-module.

/Jan