[netmod] Does defining a feature require the module be implemented?
Kent Watsen <kent+ietf@watsen.net> Mon, 09 May 2022 17:43 UTC
Return-Path: <01000180a9eb37cb-85b9c576-c1eb-425a-b42c-b3cabe548fbb-000000@amazonses.watsen.net>
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 B984EC14F73A for <netmod@ietfa.amsl.com>; Mon, 9 May 2022 10:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
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 MPQtIXx42NOn for <netmod@ietfa.amsl.com>; Mon, 9 May 2022 10:43:28 -0700 (PDT)
Received: from a48-110.smtp-out.amazonses.com (a48-110.smtp-out.amazonses.com [54.240.48.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D7767C14EB1C for <netmod@ietf.org>; Mon, 9 May 2022 10:43:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1652118206; h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Message-Id:Date:To:Feedback-ID; bh=3ZKvDLAis7QZQoY5X/b50yNlNOWlXTGw/RjxRE0zK4s=; b=ITgY4g1dA1H8J9K0LRcpdOTXZBjF2adgFLQ3EtQJPA70vV6F40SXleSGDnlhIpUo 3S9vfKq1ggHN1AAEswkT5gu2ydMba1/uKdztU2xpqyA9d2sw3HK/+liQDzUlUnxazzN f9VS4gvlhBCeJSTK9MIWeeertUsuS5dMw+lP9wRI=
From: Kent Watsen <kent+ietf@watsen.net>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Message-ID: <01000180a9eb37cb-85b9c576-c1eb-425a-b42c-b3cabe548fbb-000000@email.amazonses.com>
Date: Mon, 09 May 2022 17:43:26 +0000
To: "netmod@ietf.org" <netmod@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2022.05.09-54.240.48.110
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/_w0V47x8fmywvup_EGY0nlTRHII>
Subject: [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: Mon, 09 May 2022 17:43:29 -0000
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. Thanks, Kent
- [netmod] Does defining a feature require the modu… Kent Watsen
- Re: [netmod] Does defining a feature require the … Michal Vasko
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Robert Varga
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Martin Björklund
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Jan Lindblad
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Martin Björklund
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Andy Bierman
- Re: [netmod] Does defining a feature require the … Ladislav Lhotka
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Ladislav Lhotka
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Robert Varga
- Re: [netmod] Does defining a feature require the … Kent Watsen
- Re: [netmod] Does defining a feature require the … Robert Varga