Re: [netmod] regular expression flavours (again)

Ladislav Lhotka <lhotka@nic.cz> Fri, 14 June 2019 07:58 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 5288A12018C for <netmod@ietfa.amsl.com>; Fri, 14 Jun 2019 00:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.998
X-Spam-Level:
X-Spam-Status: No, score=-6.998 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, SPF_HELO_NONE=0.001, SPF_NONE=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 BumW7mCunIrP for <netmod@ietfa.amsl.com>; Fri, 14 Jun 2019 00:58:32 -0700 (PDT)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (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 409A912004A for <netmod@ietf.org>; Fri, 14 Jun 2019 00:58:32 -0700 (PDT)
Received: from birdie (unknown [IPv6:2001:718:1a02:1::380]) by mail.nic.cz (Postfix) with ESMTPSA id 49060140C97; Fri, 14 Jun 2019 09:58:30 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1560499110; bh=UbLYlEC5Suq8mBT460xazGyfn1xOs0CAIx4Q35skJ3k=; h=From:To:Date; b=xQ+W69r2hXlklHq9wLns4pv2S0c4okxzdkiLxOnwscTuMNusOTvfBpz1Wf9420Io7 Uq/Y8hqjauPZmp5jbqF1tetgeELa/npIe2xLGwLIwt8Or/Kw+Xc+1RnUtQkxkWkRiJ BvGi5w3RBaO9GnsycsIhMPHwudEPxR2rXNiCmkVg=
Message-ID: <ff9a92fb3e5ae65d0466cc81cb5ce42ce5549ce9.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Cc: NETMOD WG <netmod@ietf.org>
Date: Fri, 14 Jun 2019 09:58:30 +0200
In-Reply-To: <20190612092555.xotrr4moh36xv4kl@anna.jacobs.jacobs-university.de>
References: <291106e34498ebd68f26bf9ff9b679dd5bd8f0cd.camel@nic.cz> <20190612092555.xotrr4moh36xv4kl@anna.jacobs.jacobs-university.de>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.2
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.100.3 at mail.nic.cz
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/mrYOCXHDasaEaBsrY-b3g77HZsY>
Subject: Re: [netmod] regular expression flavours (again)
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, 14 Jun 2019 07:58:35 -0000

On Wed, 2019-06-12 at 11:25 +0200, Juergen Schoenwaelder wrote:
> On Wed, Jun 12, 2019 at 10:01:30AM +0200, Ladislav Lhotka wrote:
> 
> > I think it is very unfortunate that OpenConfig folks use POSIX regular
> > expressions instead of XSD. This of course causes confusion, see e.g. this
> > PR:
> > 
> > https://github.com/CZ-NIC/yangson/pull/22
> > 
> > Given the popularity of OpenConfig models, it seems to me that it would be
> > better if YANG somehow accomodates such (largely cosmetic) differences.
> 
> The differences are not cosmetic. See previous discussions on this topic.

What I meant is that such differences are still relatively easy to handle,
unlike e.g. the schema structure that is incompatible with the current
conventions and NMDA.

> 
> > One option would be that each YANG module declares the regex flavour used in
> > its
> > patterns. Yes, it is a complication, but having separate forks of YANG is
> > much
> > worse.
> 
> It is sad that OpenConfig does not follow the standard. If OpenConfig
> can't live without POSIX regular expressions, then OpenConfig should
> have used proper extension statements instead of simply changing the
> semantics of the YANG pattern statement to measn something
> different. That said, they do seem to declare something like
> oc-ext:regexp-posix; but it would have been much smarter to use for
> example oc-posix:regex instead of changing the semantics of the
> pattern statement.
> 
> I would rather see OpenConfig adopting the standard or fixing their
> POSIX regular expression solution so that it avoids changing the
> semantics of YANG statements. Having statements mean different things
> depending on some context is pretty bad design.

I agree with all this but, apparently, OpenConfig people don't care too much.
And since they are much more agile than the IETF, our views may soon become
irrelevant.

Lada

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