Re: [netmod] [Editorial Errata Reported] RFC7950 (5642)

Ladislav Lhotka <lhotka@nic.cz> Fri, 22 February 2019 14:33 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 CC17412941A for <netmod@ietfa.amsl.com>; Fri, 22 Feb 2019 06:33:50 -0800 (PST)
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] 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 X_OR5QcpPGgG for <netmod@ietfa.amsl.com>; Fri, 22 Feb 2019 06:33:48 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F65A1200D7 for <netmod@ietf.org>; Fri, 22 Feb 2019 06:33:48 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id 05ABD6295B; Fri, 22 Feb 2019 15:33:46 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1550846026; bh=YW0sT5qi9MFdRp11X1WPaveDbsGDN7heWKP5aoJ58zE=; h=From:To:Date; b=lSwC8H8gDBlFV0az9oAw17RQQ6IY2nK0hdKMPbjyILD5PGlsJ8DvixOKtQhYDqQDb RjWYoDc1vQGTaUSj9tbpYdMm4J3OpcqCU1k2MVnmhACenjF9YOuJEBtbgKOO5qdAO+ S/Elu2oMecGw8X55qQ1isiwCuyDf1dRI0bn9zgIM=
Message-ID: <3ddcd6b5917b6c93078fcc02ecabd5ec475a25e9.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Balázs Lengyel <balazs.lengyel@ericsson.com>
Cc: Ignas Bagdonas <ibagdona@gmail.com>, NetMod WG <netmod@ietf.org>, Peter Loborg <peter.loborg@ericsson.com>, Warren Kumari <warren@kumari.net>, RFC Editor <rfc-editor@rfc-editor.org>
Date: Fri, 22 Feb 2019 15:33:44 +0100
In-Reply-To: <20190222131549.4jetuckdsectna5h@anna.jacobs.jacobs-university.de>
References: <20190221163919.5196EB81AF4@rfc-editor.org> <20190221.175336.1995849216024607593.mbj@tail-f.com> <CABCOCHQMAq-vzANerP3ehY1y9fiiQZKY_S4dEh0qfhO=7bS8hA@mail.gmail.com> <eaa99bfa-16ca-8164-0fdf-7a873ef26ee0@ericsson.com> <20190222110756.bsggrzyxjtft7heg@anna.jacobs.jacobs-university.de> <af04bd6a-9177-f9cf-9b6a-5779ecacf743@ericsson.com> <20190222131549.4jetuckdsectna5h@anna.jacobs.jacobs-university.de>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/4Z_N6Y1P4cN0yOop1rsFfe6WciI>
Subject: Re: [netmod] [Editorial Errata Reported] RFC7950 (5642)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 22 Feb 2019 14:33:51 -0000

On Fri, 2019-02-22 at 14:15 +0100, Juergen Schoenwaelder wrote:
> On Fri, Feb 22, 2019 at 12:45:16PM +0000, Balázs Lengyel wrote:
> >    I am not asking for a change, but ...
> > 
> >    IMHO it would be better if YANG would not allow whitespace in enum names.
> >    It is a rarely needed freedom that degrades usability and can lead to
> >    mistakes
> >    and higher tool development costs. So it is bad for both people and
> > tools.
> > 
> >      * It is misleading, as a human user can mistakenly think that "this is
> >        legal" is actually 3 separate values
> >      * Some tools tend to consider spaces as separators
> >      * When creating code from YANG this needs special handling
> > 
> 
> Banning white space may make you feel better but it does not really
> solve the problem for tool makers. There are many more restrictions
> and going for the most restricted minimum gets us back to really
> limiting results.

I agree. It is not terribly difficult to support enum names containing spaces in
any programming language.

Lada 

> 
> /js
> 
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67