Re: [netmod] draft netmod charter update proposal

Ladislav Lhotka <lhotka@nic.cz> Tue, 21 March 2017 10:44 UTC

Return-Path: <lhotka@nic.cz>
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 75019129483 for <netmod@ietfa.amsl.com>; Tue, 21 Mar 2017 03:44:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level:
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 r_FSQoipjVmY for <netmod@ietfa.amsl.com>; Tue, 21 Mar 2017 03:44:17 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07EEF124217 for <netmod@ietf.org>; Tue, 21 Mar 2017 03:44:17 -0700 (PDT)
Received: from [IPv6:2001:718:1a02:1:d20:8e4d:8768:16f6] (unknown [IPv6:2001:718:1a02:1:d20:8e4d:8768:16f6]) by mail.nic.cz (Postfix) with ESMTPSA id 637AF6090C; Tue, 21 Mar 2017 11:44:15 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1490093055; bh=dg4YyYxGwK2JWLsA5WBO0nb49Pp6tLEJhTJDPF17qzM=; h=From:Date:To; b=C8ueIO6ruoA9NwS5dNi6HnDI4Wyyr3Ljsq/Zap5FHKuLU52yT3tMtE4rktJGExqlE yioaLcdqxKP/i4iZ/WoeW6WQoSCfUvkLexUtJsDMHltkLa6AA6oJ6UA0frwW/mYfYw 6v5AZvjMHfnHrHtD35pr0UwlFpb9XOy0TiGDghFY=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <20170321103039.GA35688@elstar.local>
Date: Tue, 21 Mar 2017 11:44:15 +0100
Cc: Robert Wilton <rwilton@cisco.com>, Mehmet Ersue <mersue@gmail.com>, Lou Berger <lberger@labn.net>, netmod@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5796C093-A399-4A91-BA64-37043242AB1A@nic.cz>
References: <15ad6df64e8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <000f01d29f21$8fe93c10$afbbb430$@gmail.com> <2748e6e6-5d16-05e9-0ce5-bc2b3a7e69cc@cisco.com> <C843261B-209D-4BEF-AD06-749F604C22D2@nic.cz> <562b9d03-dc1a-3741-8be7-c33afd7d74c4@cisco.com> <4D1DE368-9B3D-478B-BE06-C5ED9A88B8F8@nic.cz> <20170321080422.GB35044@elstar.local> <0298C599-E206-4777-A95C-5F58E0D519AA@nic.cz> <20170321094313.GA35449@elstar.local> <3B788B04-4728-45FC-86A7-33A9F4D5CF98@nic.cz> <20170321103039.GA35688@elstar.local>
To: Jürgen Schönwälder <j.schoenwaelder@jacobs-university.de>
X-Mailer: Apple Mail (2.3259)
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/EAzrTTNFgDB29YIt0DyJ7v3powE>
Subject: Re: [netmod] draft netmod charter update proposal
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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, 21 Mar 2017 10:44:19 -0000

> On 21 Mar 2017, at 11:30, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> 
> On Tue, Mar 21, 2017 at 10:59:11AM +0100, Ladislav Lhotka wrote:
>> 
>> If the "config" statement really carried some protocol-specific semantics that isn't meaningful for all potential uses of YANG, it would be better to remove it from core YANG and define it as an extension that would be mandatory for configuration protocols that need it.
>> 
> 
> YANG exists because we wanted to describe and manage configurations. And

... and operations and notifications where config true/false is already meaningless.

> some people still want to do this. I understand that you want to turn YANG
> into a general purpose data modeling language. But I am not sure this is

In reality, YANG has already been used as such quite a few times (not by me), mainly because it can define a schema of tree-like data in a representation-independent way, and there is no adequate substitute. Doing so in the current state of affairs means selectively ignoring some parts of RFC 7950, and creatively interpreting other parts. This is IMO not good.

Lada

> consensus. As of today, config true means what is defined in RFC 6020
> and RFC 7950.
> 
> /js
> 
> -- 
> Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67