IETF Logo Mail Archive

Re: [netmod] Potential additions to rfc6087bis: RegEx guidelines

"Acee Lindem (acee)" <acee@cisco.com> Sat, 02 September 2017 10:40 UTC

Return-Path: <acee@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 2F819132335 for <netmod@ietfa.amsl.com>; Sat, 2 Sep 2017 03:40:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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
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 IlWalb_myOEb for <netmod@ietfa.amsl.com>; Sat, 2 Sep 2017 03:39:59 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 672841329C0 for <netmod@ietf.org>; Sat, 2 Sep 2017 03:39:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2374; q=dns/txt; s=iport; t=1504348799; x=1505558399; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Fs1olKM714J2KlK11ZJ+asEAXGOL6lpg8kRAvnz+RUk=; b=QVU47M03YTGZGpHBZyUb2Tc6xoHJ/c8tDQ+ZtFiw4xH9X0zeepAExj0/ 4B+PAatOUbMJQUjpT5M0R3Q7MiCCDcJTvPMfl3x8pAQNyoTidejiOgKz5 wWHmBtblECKS1X9JLtSA/g4sYOCajQTyW7Swlzr2Ci01oNM2na6/P1n/k g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D+AAC+iapZ/5JdJa1aAxkBAQEBAQEBAQEBAQcBAQEBAYNaZIEVB4NwiiCQIIFxliiCEiELhExPAhqDez8YAQIBAQEBAQEBayiFGQEBAQMBASEROgsOAgIBCA4CCAICJgICAhkMCxUQAgQOBYoxELF8gieLWgEBAQEBAQEBAQEBAQEBAQEBAQEBAR0FgQiCHYIChlmEdRcKJoJMgmEFoHQClE+ScZZKAR84gQ13FUmHG3aJcoEPAQEB
X-IronPort-AV: E=Sophos;i="5.41,463,1498521600"; d="scan'208";a="479796315"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Sep 2017 10:39:58 +0000
Received: from XCH-RTP-009.cisco.com (xch-rtp-009.cisco.com [64.101.220.149]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v82Advaj010930 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 2 Sep 2017 10:39:58 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-009.cisco.com (64.101.220.149) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Sat, 2 Sep 2017 06:39:57 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1263.000; Sat, 2 Sep 2017 06:39:57 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "Robert Wilton -X (rwilton - ENSOFT LIMITED at Cisco)" <rwilton@cisco.com>
CC: "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] Potential additions to rfc6087bis: RegEx guidelines
Thread-Index: AQHTHPE2wiW48ODwX0muaRIIfazDyAAhqHwAAAKnWIAAEce1gAAC0wGAACizCwAAAHCnAACXFjOAAAXbNQAAL4LGgAADyxwAACOm9gAAAoh/AAACxNqAAAGF9gAABORxgAAD6VyAADKKfzyik1ZcgIABbWkA///w5oA=
Date: Sat, 02 Sep 2017 10:39:57 +0000
Message-ID: <D5D00209.C5C67%acee@cisco.com>
References: <c8de6140-af50-0a4b-a479-b011a8dfbbe7@cisco.com> <CABCOCHRNt3Tkxy8Ffz3JGgPe-rQYwZ3MTLmD43OQi4P6tZQJmg@mail.gmail.com> <f7151a6b-9deb-52ad-62a9-78b29a552540@cisco.com> <20170830102902.2n5q6rgq2x2dxfq2@elstar.local> <e8482a9c-cba3-28e2-9ffa-ec5eb5c1c0a4@cisco.com> <20170830123156.cssrg5kklpo67fie@elstar.local> <CABCOCHTtN611FO2ov2kTLtZx-Q3=tzgH7Xk9uGvFUD1WuyMZyw@mail.gmail.com> <b13c5e9a-e9f9-96e9-8823-0402fb74af09@cisco.com> <1504223854014.55228@Aviatnet.com> <847e5bf9-7b3d-9ff8-9954-970f32a2094c@cisco.com> <20170902073342.xoziwor4tdr5bipw@elstar.local>
In-Reply-To: <20170902073342.xoziwor4tdr5bipw@elstar.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F05F7B21BF653E4E9C4BFA7B9192B1E7@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/3A38sqC96vfWT8J1k1HLDd3FTn4>
Subject: Re: [netmod] Potential additions to rfc6087bis: RegEx guidelines
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: Sat, 02 Sep 2017 10:40:01 -0000

Juergen, 

On 9/2/17, 3:33 AM, "netmod on behalf of Juergen Schoenwaelder"
<netmod-bounces@ietf.org on behalf of
j.schoenwaelder@jacobs-university.de> wrote:

>On Fri, Sep 01, 2017 at 10:45:51AM +0100, Robert Wilton wrote:
>> Hi Alex,
>> 
>> 
>> On 01/09/2017 00:57, Alex Campbell wrote:
>> > 
>> > Hi,
>> > 
>> > 
>> > I'd be very wary of adding guidelines that restrict the regex syntax.
>> > 
>> > 
>> > A tool that supports YANG must implement the full regex language
>>anyway
>> > (or ignore regexes altogether if they are not relevant to the tool's
>> > function).
>> > 
>> This is true if the tool is designed to work with any arbitrary YANG
>> module.  But if a tool only needs to work with a subset of YANG modules
>> (e.g. perhaps just IETF, OpenConfig, and Vendor models) then they only
>>need
>> to support the subset of the XML RE language that is used by the YANG
>> modules that they load.
>>
>
>Rob,
>
>you are on the path to create multiple flavours of YANG, an IETF
>flavour, an OC flavour, a Vendor XYZ flavour - in my view this can't
>be the goal of a standard.

This is not an effort to change or bifurcate the YANG 1.1. It is simply to
RECOMMEND a proper subset of XSD pattern that is more portable.

Thanks,
Acee


>
>A compliant implementation of YANG 1.0 and YANG 1.1 must handle XSD
>pattern.
>
>/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/>
>
>_______________________________________________
>netmod mailing list
>netmod@ietf.org
>https://www.ietf.org/mailman/listinfo/netmod

v2.23.0 | Report a Bug | By Email