Re: [netmod] regular expression flavours (again)

"Rob Wilton (rwilton)" <rwilton@cisco.com> Fri, 14 June 2019 10:08 UTC

Return-Path: <rwilton@cisco.com>
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 C3DF6120180 for <netmod@ietfa.amsl.com>; Fri, 14 Jun 2019 03:08:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=aijqntKT; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=tPN64ZRz
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 u_tXrYuLTJuP for <netmod@ietfa.amsl.com>; Fri, 14 Jun 2019 03:08:40 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B42F3120143 for <netmod@ietf.org>; Fri, 14 Jun 2019 03:08:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2698; q=dns/txt; s=iport; t=1560506920; x=1561716520; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hOtpR0GOAoityVQoFoHHpTZ5XKmUaQo2kGZL9KFNO9s=; b=aijqntKTECs+qF+GDJNUwaNaeLRs8mtdRaPnVR1ULsAWUR8JWdXs0VxD LWAghyHTW5uhCbmyQEJ5xcS52FN3ySlsUmx0Q8fwdmOTUfXbVhA7mXeEI 079s50Ho8eor48JpjcmmVsw7KCmSHj/U6SxAnskqkQ3804UJikFKs/Ajj Q=;
IronPort-PHdr: =?us-ascii?q?9a23=3Ae9zaHxPd2IU26S7W/BIl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEu60/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBjhM//ucys8NM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A3AADVcQNd/5pdJa1mGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBVAIBAQEBCwGBPVADgT8gBAsoCoQMg0cDjmKCV5c1glIDVAk?= =?us-ascii?q?BAQEMAQEtAgEBgUuCdQIXgjQjNwYOAQMBAQQBAQIBBG0cDIVKAQEBAQIBEhE?= =?us-ascii?q?RDAEBNwELBAIBBgIOAgEEAQEBAgImAgICMBUICAIEDgUIGoRrAw4PAQKOAJB?= =?us-ascii?q?gAoE4iF9xgTGCeQEBBYR/GIIPCYEMKAGLXBeBQD+BEUaCTD6ERoMIMoImjje?= =?us-ascii?q?bHgkCghCTa4InhwKOB6N2AgQCBAUCDgEBBYFlIoFYcBWDJ4IPDBeDTYpTcoE?= =?us-ascii?q?pjjMBgSABAQ?=
X-IronPort-AV: E=Sophos;i="5.63,373,1557187200"; d="scan'208";a="287181273"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 14 Jun 2019 10:08:39 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x5EA8dV0016594 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 14 Jun 2019 10:08:39 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 14 Jun 2019 05:08:38 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 14 Jun 2019 05:08:37 -0500
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 14 Jun 2019 06:08:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hOtpR0GOAoityVQoFoHHpTZ5XKmUaQo2kGZL9KFNO9s=; b=tPN64ZRzgaLlm7+I2dR16Boqd+6NE0sl/Ma7hq2uYh8v+iNboFt2VtRRXTkb59yBGImOLRY1LeusNQ9pZUABOKdS1V7uVHjx/2M1/T7htk0XWSIDtWhFnnsF4e7F+bT8reXl0ycUfProaZb32cXFJLRpTHuxGlUdHLTGbsSR01g=
Received: from BYAPR11MB2631.namprd11.prod.outlook.com (52.135.227.28) by BYAPR11MB2806.namprd11.prod.outlook.com (52.135.228.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1987.13; Fri, 14 Jun 2019 10:08:36 +0000
Received: from BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::ed99:b6a8:d6fb:5045]) by BYAPR11MB2631.namprd11.prod.outlook.com ([fe80::ed99:b6a8:d6fb:5045%4]) with mapi id 15.20.1987.013; Fri, 14 Jun 2019 10:08:36 +0000
From: "Rob Wilton (rwilton)" <rwilton@cisco.com>
To: Carsten Bormann <cabo@tzi.org>
CC: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Robert Varga <nite@hq.sk>, NETMOD WG <netmod@ietf.org>
Thread-Topic: [netmod] regular expression flavours (again)
Thread-Index: AQHVIPUyXZrpgNnnhkC8kWX+UPfSraaXv8IAgAHXCICAAAnOgIABOjTQgAASMICAAABbcA==
Date: Fri, 14 Jun 2019 10:08:36 +0000
Message-ID: <BYAPR11MB26314900335A447BF2AD8F81B5EE0@BYAPR11MB2631.namprd11.prod.outlook.com>
References: <291106e34498ebd68f26bf9ff9b679dd5bd8f0cd.camel@nic.cz> <20190612092555.xotrr4moh36xv4kl@anna.jacobs.jacobs-university.de> <4611382f-be58-a20f-1712-e5fb3e4ef3ec@hq.sk> <20190613140655.jyq3iltl2v22ekmb@anna.jacobs.jacobs-university.de> <BYAPR11MB26311142F2841456A42623CDB5EE0@BYAPR11MB2631.namprd11.prod.outlook.com> <815A80B5-A05F-4867-BFF4-7C08081F433A@tzi.org>
In-Reply-To: <815A80B5-A05F-4867-BFF4-7C08081F433A@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rwilton@cisco.com;
x-originating-ip: [173.38.220.62]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 34756965-b914-457b-84af-08d6f0b0443b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB2806;
x-ms-traffictypediagnostic: BYAPR11MB2806:
x-microsoft-antispam-prvs: <BYAPR11MB28068038A12616542A5A7577B5EE0@BYAPR11MB2806.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0068C7E410
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(39860400002)(376002)(136003)(366004)(396003)(189003)(199004)(13464003)(4326008)(7736002)(305945005)(14454004)(8936002)(11346002)(71200400001)(71190400001)(486006)(476003)(99286004)(52536014)(25786009)(446003)(5660300002)(53936002)(66066001)(55016002)(9686003)(6436002)(86362001)(81166006)(81156014)(8676002)(6916009)(256004)(229853002)(66446008)(6246003)(3846002)(26005)(54906003)(53546011)(316002)(74316002)(33656002)(6506007)(76176011)(6116002)(102836004)(66946007)(68736007)(186003)(73956011)(64756008)(7696005)(66556008)(66476007)(76116006)(2906002)(478600001); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2806; H:BYAPR11MB2631.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: px18KwlMj/FNCwvNpJXpqD1ff+p8nqDH2IvPce6EqhWe4dXOy8XS/R3XyQrtN0GDsxjRao9AL9wuJczQRj19dtdxHxghc9UO0TNPKuIyG76vW49CzbaTt0xw8k92XgZhsEN9LXHNX/yPDNIoWTUV/Qkh0fNJieYBVTMTsm1kbh5OvSsK0MJs6Jhh6ptMam7vZr3dvxxxqspdCH71BDu1x9alXCRUTuky6vSqstYbL8JA/3RC4FXZgaEskCwSpawPI+66fknvs63sWyMCEiJgPyYHHA/wsW2zHNCZmNldmXCHPxfwjrJb4rrleHnluMFxMpNNtpPCZCtiBIapVM/KgGbizr/iyKVGOpHB8gk0Cn56DTQCuPSPdDadIeAP83YNAuI/HyvSOcOiAd0enSXrc1F6nd/Xd86uRHOPLZkVSxE=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 34756965-b914-457b-84af-08d6f0b0443b
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jun 2019 10:08:36.7256 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rwilton@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2806
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/5P7bScNWMwUPEXz4zNlDwbZsT4s>
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 10:08:43 -0000


> -----Original Message-----
> From: Carsten Bormann <cabo@tzi.org>
> Sent: 14 June 2019 10:57
> To: Rob Wilton (rwilton) <rwilton@cisco.com>
> Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>de>; Robert
> Varga <nite@hq.sk>sk>; NETMOD WG <netmod@ietf.org>
> Subject: Re: [netmod] regular expression flavours (again)
> 
> On Jun 14, 2019, at 11:29, Rob Wilton (rwilton) <rwilton@cisco.com> wrote:
> >
> > I'm sure that someone can post an XKCD of why this is a bad idea 😉
> 
> Yeah, going ahead and standardizing another regex dialect that is subtly
> incompatible with everything else is exactly what we need.

This is not what I am suggesting.

We don't need a standard regex dialect that is subtly incompatible with all the normal regex implementations because that is exactly what W3C produced.

What I am suggesting is standardizing a regex dialect that is well defined and widely compatible with normal regex engines.  I.e. a standardized subset of PCRE.

> 
> We could even make sure that dialect is actually useful in a pattern
> statement (e.g., by making it self-anchoring).

I don't think that adding/removing the anchor characters is really the issue, since they are trivial to add/remove as required.


> 
> But wait, somebody has already done that work for us!
> 
> W3C did, when they designed their XSD-types… So we are done already!

I disagree, please see above.


> 
> Now the main deployability problem with W3C XSD regexes is that they added
> some functionality that is sorely missing in other dialects, such as
> character class subtraction, so it is more than an hour of work to write a
> converter from XSD regexes to you favorite flavor.  Maybe we should
> encourage some open source software in this space…

Or perhaps we could define a regex language that worked with normal implementations without requiring any conversion.

Thanks,
Rob


> 
> Grüße, Carsten
> 
>