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

Martin Björklund <mbj+ietf@4668.se> Wed, 18 May 2022 06:05 UTC

Return-Path: <mbj+ietf@4668.se>
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 9F815C15E6F1 for <netmod@ietfa.amsl.com>; Tue, 17 May 2022 23:05:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=4668.se header.b=J/4ENNgc; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=z4mlSXzU
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 5o0DnjJV5yJK for <netmod@ietfa.amsl.com>; Tue, 17 May 2022 23:05:51 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 0164AC147921 for <netmod@ietf.org>; Tue, 17 May 2022 23:05:46 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 83D105C0056; Wed, 18 May 2022 02:05:45 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 18 May 2022 02:05:45 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=4668.se; h=cc:cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm2; t=1652853945; x= 1652940345; bh=s985zugsxEhKnTTtDxrU0clW4NV4xhxfCdZFQ8+8Ve8=; b=J /4ENNgcIY6iEZYveC4HFt3MrkTGmA/2sszJJ4PhlTWLryV7y2I/2f9QxyiWcaI6L +ZY5cF3SxaVretdP97c7hxPitOyAG2LboO5k+OQXjgyUGW8sCLVJ1qqDmvP0OytG IlJM3e0gitE4QWpAAbusN7r7pC4dk904XsRqyLyDHCAy4tlIpdtmaoK1n/O0+H/m eiRsdUhWyz6BStENlIvoWgU33o3L85sz4KD87AGjPbZpEXZ9ObEvU80lcKaBkV9W PRvJ6fT9YMVCs88fw4kFhJaExOAS8dq1T1t2ogc2Z1gHyzQIdr703bIJBBDEQ7nY rzx1hvvnHC4CdoFzKvfXw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1652853945; x= 1652940345; bh=s985zugsxEhKnTTtDxrU0clW4NV4xhxfCdZFQ8+8Ve8=; b=z 4mlSXzUBBoy8TtfAkOiksKpDNitrmwz6/OxcAChpjXRG9YSa2uQ8dcXpAieeEbT2 0B8lLiFyO9i6IB4z6OdiXJ0yEn7vSgif5TmCMfriq70q9mJAGSdQj3a3/UymqbZi /HcMP7/ZyCIJvEUgcK+PX94Txa1ofhNZwPbxm0j3S/n7TVpSDh7/WxoRj82wIuBz 5Rb9rNGAOBsRJBerAjDAxK7e+nEoFynOqmd32fYUcrOf4A5G06iSUk/JKfbixsXw c4VJd0VgjQo97VgqK85HOXCXy0e7cLeQORQzenXnLac+7VnHxqWETfQ0wTm5eYk6 +xyFiCxV3zCKQg3fzqSWQ==
X-ME-Sender: <xms:uYyEYuhHtJtWOQIT6DLVdv5m-vxGrL8kYVN2k79KpRfK3oqfy-VajQ> <xme:uYyEYvApMwb-o594-TsAYZcKDCpr2DNxl50ZyPhxyYqkjk7OPI_Ld2IKNuXOkDEbM bVB4KafjeWWTLc0I9I>
X-ME-Received: <xmr:uYyEYmHTFlwWcruayhmIviq85hoL4GBV0VHVMJLCBBc3UxOX3ew7PrZLH5werAb2RW8f9s0MiISdPgj7t2ba9sZ-oh7PfXzzuA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrheekgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffkffvvefuhfgjfhfogggtgfesth ejredtredtvdenucfhrhhomhepofgrrhhtihhnuceujhpnrhhklhhunhguuceomhgsjhdo ihgvthhfseegieeikedrshgvqeenucggtffrrghtthgvrhhnpeekfeekudefgeeutdfgve evvdeikeeiudekffegtedtkeejteekteekiedtfeegieenucffohhmrghinhepvgigrghm phhlvgdrnhgvthdpihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepmhgsjhdoihgvthhfseegieeikedrshgv
X-ME-Proxy: <xmx:uYyEYnSS8PdiM9RaPq6Q4EoxImiES6-8O7gL_rtkgk1iMK8obYs6Og> <xmx:uYyEYrxXNowri6IuWZ-Ej4lzWRXBIjLDE6zBT6fM2_zUCXZaPbA5rg> <xmx:uYyEYl7fLPBxvE8ILOmnS-wF5oHzehM4oAyKlQquGDy3Ulf70Qc_cw> <xmx:uYyEYpabjADkLPq19lcXKvX0EB9nvTAAXe_2gaRVR7AzY_o8qx95wg>
Feedback-ID: icc614784:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 18 May 2022 02:05:44 -0400 (EDT)
Date: Wed, 18 May 2022 08:05:43 +0200
Message-Id: <20220518.080543.825575420363032441.id@4668.se>
To: kent+ietf@watsen.net
Cc: netmod@ietf.org
From: Martin Björklund <mbj+ietf@4668.se>
In-Reply-To: <01000180a9eb37cb-85b9c576-c1eb-425a-b42c-b3cabe548fbb-000000@email.amazonses.com>
References: <01000180a9eb37cb-85b9c576-c1eb-425a-b42c-b3cabe548fbb-000000@email.amazonses.com>
X-Mailer: Mew version 6.8 on Emacs 26.3
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/cJzPYUWH-HymV5DASEwRY3R-0AI>
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: Wed, 18 May 2022 06:05:55 -0000

Hi,

Kent Watsen <kent+ietf@watsen.net> wrote:
> YANG Doctors, 
> 
> 
> Does "foo" need to be "implemented", in order for its feature to be
> define?
> 
> 	module foo {
> 	  yang-version 1.1;
> 	  namespace "https://example.net/foo";
> 	  prefix "f";
> 
> 	  feature foo-feature;
> 
>           ...
> 	}
> 
> 
> Specifically, using the previous YANG Library (RFC 7895), would this
> be possible:
> 
>       {
>         "name": "foo",
>         "feature": [
>           "foo-feature"
>         ],
>         "namespace": "https://example.net/foo",
>         "conformance-type": "import"
>       },
> 
> 
> Or does "foo" also need to be "implemented", in order for its feature
> to be defined?
> 
> 
> PS: the answer to this impacts the "crypto-types and friends" drafts
> in the NETCONF WG, where it is assumed (and various tools agreed, sans
> a recent change in `yanglint`) that the implementation-status of a
> module is orthogonal to what features supported.

Can you show a specific example where this is a problem?


/martin



> 
> Thanks,
> Kent
> 
> 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod