X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Delivered-To: barryleiba.mailing.lists@gmail.com
Received: by 10.107.163.148 with SMTP id m142csp92303ioe;
        Fri, 8 Aug 2014 08:29:29 -0700 (PDT)
X-Received: by 10.66.243.6 with SMTP id wu6mr1650472pac.157.1407511769314;
        Fri, 08 Aug 2014 08:29:29 -0700 (PDT)
Return-Path: <abnf-discuss-bounces@ietf.org>
Received: from mail.ietf.org (mail.ietf.org. [2001:1900:3001:11::2c])
        by mx.google.com with ESMTPS id zo5si4466879pac.90.2014.08.08.08.29.28
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Fri, 08 Aug 2014 08:29:29 -0700 (PDT)
Received-SPF: pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) client-ip=2001:1900:3001:11::2c;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 2001:1900:3001:11::2c as permitted sender) smtp.mail=abnf-discuss-bounces@ietf.org;
       dkim=pass header.i=@ietf.org
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 3947F1B2B5C;
	Fri,  8 Aug 2014 08:29:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1407511768; bh=4QGafDOC8lvX0WDj9SD9xWygMtKusH1Z/QOXyYW9CeM=;
	h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:Cc:
	 Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:
	 List-Subscribe:Content-Transfer-Encoding:Content-Type:Sender;
	b=yqiR6rRA36evuSyLeKdTlvADVzTtGz5+qItlqMNBvuYn+iY3KOVXsGAHeMz1Awl01
	 V98nkPoDwQ4kYdmKtYSV235xqk8JgrPq5MQehafQmDs9O9vDYj0dd8E1P3h55N6ECb
	 DehFRU+aIbQ+iYc5FN4jpppGBoxM/kXzK72PHnKM=
X-Original-To: abnf-discuss@ietfa.amsl.com
Delivered-To: abnf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id EB1311B2B49
 for <abnf-discuss@ietfa.amsl.com>; Fri,  8 Aug 2014 08:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 SPF_SOFTFAIL=0.665] autolearn=no
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 TseOOVjEmcMv for <abnf-discuss@ietfa.amsl.com>;
 Fri,  8 Aug 2014 08:29:25 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net
 (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212])
 by ietfa.amsl.com (Postfix) with ESMTP id AF9C11B2AEE
 for <abnf-discuss@ietf.org>; Fri,  8 Aug 2014 08:29:24 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89])
 by qmta14.westchester.pa.mail.comcast.net with comcast
 id cEX01o0071vXlb85EFVQAs; Fri, 08 Aug 2014 15:29:24 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164])
 by omta17.westchester.pa.mail.comcast.net with comcast
 id cFVP1o00M3ZTu2S3dFVPC9; Fri, 08 Aug 2014 15:29:24 +0000
Message-ID: <53E4ECD3.4000802@alum.mit.edu>
Date: Fri, 08 Aug 2014 11:29:23 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, 
 Ned Freed <ned.freed@mrochek.com>
References: <53E3B22E.5000708@alum.mit.edu>
 <01PB3UKRBQA80000SM@mauve.mrochek.com>
 <EC991A58-9852-4467-AC89-102E72CFDFEE@cisco.com>
 <01PB3V7RZSXK0000SM@mauve.mrochek.com>
 <94814907-393C-41CB-8702-417CE06E3267@cisco.com>
 <01PB3ZN11FOS0000SM@mauve.mrochek.com>
 <9ADBC170-284D-44FA-99E3-C871F53505C5@cisco.com>
In-Reply-To: <9ADBC170-284D-44FA-99E3-C871F53505C5@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
 s=q20140121; t=1407511764;
 bh=Xsyz8qfQZ4XP7dGuO8bWQ5HNS2y7ttOYEOpTR/uqixk=;
 h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject:
 Content-Type;
 b=MnQODmcCdED1ly2RgN42EcsGRvd9+NZkKPUzSvmuc/OGP7hAM9M5oo/oISp+0vAFv
 fOZLRlXLewH8eX8a7ENULqbr3LzGkSdjK1rV8/wSeOccQCJK1QLb3VamWvSVG8AcIO
 Hza8O8ZTqd2vCp8qpX3W4EoU+VjaCZ4ePBTJi+gSgYVDL8N2hyZcIBFN3yvEqLDGCF
 d2WEqZabozkRE94dgwoiS8AZRd5/f7moVPnfmqR3K8STgFF1gM7wnPubPTdiL9fNut
 GtNH7Kt3mRtsnOegRyM9fmFPdQoAzmHL6JNcZOp47V03xescDi/Dy4NUAsg1Luu7VV
 TRQZWSwbcIgbQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/Iw6ayM-Hh65ZwDldSXsfidTSYvk
Cc: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>
Subject: Re: [abnf-discuss] Case-sensitive string constants in ABNF
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "General discussion about tools,
 activities and capabilities involving the ABNF meta-language"
 <abnf-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abnf-discuss>,
 <mailto:abnf-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/abnf-discuss/>
List-Post: <mailto:abnf-discuss@ietf.org>
List-Help: <mailto:abnf-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abnf-discuss>,
 <mailto:abnf-discuss-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: abnf-discuss-bounces@ietf.org
Sender: "abnf-discuss" <abnf-discuss-bounces@ietf.org>

On 8/7/14 11:00 PM, Joe Hildebrand (jhildebr) wrote:
> On 8/8/14, 2:30 AM, "Ned Freed" <ned.freed@mrochek.com> wrote:
>
>>> Slight rephrase.  What would you think about an update to 5234 that did
>>> nothing but add a syntax extension capability?
>>
>> I'd have to see it to say. Given this is the first extension I've seen ~6
>> years I think has made some sense, I don't see a pressing need for such a
>> mechanism. But I'm not opposed to one either.
>
> Here are a couple of other features I've wanted:

Here comes the slippery slope - there may be a lot of latent desire for 
a variety of ABNF extensions. It *might* be a good idea to gather those 
and then winnow them down to practical ones.

> - match any character except for these specified ones

I've wanted something similar to that, but more generalized:

match anything that matches rule1 but not rule2. E.g., anything that 
matches VCHAR but not COLON. Mostly I've wanted it for single byte 
matching, but it seems meaningful more generally.

> - match any character from a given Unicode category
> - match a grapheme cluster
> - explicitly operate on codepoints rather than octets

Moving into unicode would probably be a good thing, since it is now so 
widely used. But it probably introduces a lot of new complexity. If it 
can be done in a way that hides much of that complexity then it may be a 
good thing.

	Thanks,
	Paul

> I don't know if extensions would be good for any of these, and there may
> be ways of doing them that I don't know about yet.
>

_______________________________________________
abnf-discuss mailing list
abnf-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/abnf-discuss