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

Robert Varga <nite@hq.sk> Tue, 31 May 2022 16:09 UTC

Return-Path: <nite@hq.sk>
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 BD3A9C157B43 for <netmod@ietfa.amsl.com>; Tue, 31 May 2022 09:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.985
X-Spam-Level:
X-Spam-Status: No, score=-3.985 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-1.876, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
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 drfP7mAeS2_m for <netmod@ietfa.amsl.com>; Tue, 31 May 2022 09:09:54 -0700 (PDT)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F2B5C157903 for <netmod@ietf.org>; Tue, 31 May 2022 09:09:53 -0700 (PDT)
Received: from [192.168.1.146] (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id 656132478EE; Tue, 31 May 2022 18:09:50 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1654013390; bh=Dy6QDHB9s3GNg5S71DqlKoRB3UdTAjftRF/UrqXCUO0=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=no9tlcy7+EI3gIGnc1RSnk7WhbYbiP2V9jNEqEihiqhV6MrUjov3kdTcnIzkPjS3k WTtCiR7vwiQX/ds9E/R5y3tkLRdSnYgeCjJnBkXtC47jznVBiqce6t12N7CEjCrI6P hw543UrF+psOIp00DdlqXjgMDCJO3+yW987BepZY=
Message-ID: <01a1b2f3-acc2-8378-ffea-9670e2d51b12@hq.sk>
Date: Tue, 31 May 2022 18:09:49 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.1
Content-Language: en-US
To: Kent Watsen <kent+ietf@watsen.net>, Martin Björklund <mbj+ietf@4668.se>
Cc: "netmod@ietf.org" <netmod@ietf.org>
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>
From: Robert Varga <nite@hq.sk>
In-Reply-To: <01000180d793d6ee-f82a4a03-28d8-4f8b-909e-7306a7fc565b-000000@email.amazonses.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------LUZ7xcH617xqA7G98fVW02kr"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/RjAxtrZa0X_cnjslg_kMCWwqp5A>
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: Tue, 31 May 2022 16:09:58 -0000

Hello Kent,

On 18/05/2022 16:30, Kent Watsen wrote:
> 
> 3) I wish more modules would following the pattern of having the global 
> protocol accessible tree be defined via a "uses" of a grouping defined 
> in the module.   In another recent project, I had to hack the topology 
> modules defined in RFC 8345 (to convert the containers to groupings) to 
> enable a multiplicity of "abstract network topologies" to be configured. 
>   The assumption that only a single global instance is ever needed is 
> proving to be invalid in my work time and again.

/me puts the co-author hat on.

The multiplicity is already built-in into the model by the fact that 
network topologies is a top-level list.

Would you mind sharing the use case what requires multiplicity of the 
built-in multiplicity?

I know this sort-of is a re-hash of the ietf-interfaces discussion, but 
while there the use-case is well understood, I wonder what equivalent is 
there for networks/topologies.

Thanks,
Robert