X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Delivered-To: barryleiba.mailing.lists@gmail.com
Received: by 10.107.163.148 with SMTP id m142csp690948ioe;
        Tue, 2 Sep 2014 06:58:08 -0700 (PDT)
X-Received: by 10.70.62.65 with SMTP id w1mr47508268pdr.21.1409666287691;
        Tue, 02 Sep 2014 06:58:07 -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 w15si6362718pde.10.2014.09.02.06.58.07
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 02 Sep 2014 06:58:07 -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 982EB1A8750;
	Tue,  2 Sep 2014 06:58:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1409666286; bh=heJG4hNXC/OGz0agdbebfVa1jv8Kb4oggbQ+Md48UoQ=;
	h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To:
	 Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:
	 List-Subscribe:Content-Transfer-Encoding:Content-Type:Sender;
	b=Lt9P7KgBKcrvceenS49tTSQOIQtJt8J5MK4U4xsWc3Zxg7OHq1GbPp/KwXF7C+rqW
	 J8Hnx/oatc3naeytwUGuJOec8mmryjtJ9yaSn4IF8X0eCH1fGSYYwbzI2QPEUCmWf3
	 cokc2VCyTYPhDEw972sL3MT/0ddY0Sej0HQ/mMeU=
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 C391F1A872A
 for <abnf-discuss@ietfa.amsl.com>; Tue,  2 Sep 2014 06:58:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.165
X-Spam-Level: 
X-Spam-Status: No, score=0.165 tagged_above=-999 required=5
 tests=[BAYES_05=-0.5, 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 wXvAt5PGhKjd for <abnf-discuss@ietfa.amsl.com>;
 Tue,  2 Sep 2014 06:58:03 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net
 (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48])
 by ietfa.amsl.com (Postfix) with ESMTP id 6A71E1A0B81
 for <abnf-discuss@ietf.org>; Tue,  2 Sep 2014 06:58:02 -0700 (PDT)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19])
 by qmta05.westchester.pa.mail.comcast.net with comcast
 id mD7L1o0040QuhwU55Dy1aJ; Tue, 02 Sep 2014 13:58:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151])
 by omta02.westchester.pa.mail.comcast.net with comcast
 id mDy11o00A3Ge9ey3NDy1EL; Tue, 02 Sep 2014 13:58:01 +0000
Message-ID: <5405CCE9.3040308@alum.mit.edu>
Date: Tue, 02 Sep 2014 09:58:01 -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: abnf-discuss@ietf.org
References: <53E3B22E.5000708@alum.mit.edu>	<53EF8C18.3030004@alum.mit.edu>
 <CAC4RtVCii_j-54ixnuB6CqwQZSO_9rQstjqswDXsfuSy9ChDnA@mail.gmail.com>
 <53F299A9.1080209@alum.mit.edu>
In-Reply-To: <53F299A9.1080209@alum.mit.edu>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
 s=q20140121; t=1409666281;
 bh=Pkti6udLiMax/gkaKaMol1pKUYW9VQHfnJaaMXPmpmk=;
 h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject:
 Content-Type;
 b=RY2ZLDtUOl+k5aTvqgfc8J/Bo9rFDGqVaPaYnm7eoFuHzhYd8yBSpzkTh7ekT/sDa
 9JRYEe/N3bTHGNUQHKzGPU+wTiM0pydgSt92xSKEFT7L++7CKC8SQwchXs+9tJV5Lx
 7FPbeACC11AWVj5y8ak6FLBAUaf9a7RwijhOeLVAb7HQ8i5XjvU71xQ/CRi/iKcbMB
 yREi5LJaEd/H0cLC9tCxhv2fXJ+9nBDgYDyXfZwfvIMAE19swxPXy7s8bXa10kTxG+
 4bdYyZtgUMUvVtD8YAdQ4XK1ueMR05kOUMg460+uHLEB/Ryek1Z77eF3heBn+pCG5v
 LtdxPN83YKkpw==
Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/VS8Ygv7Pk9kjPaiC7-raIbBxC6c
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>

I want to reiterate one point I made earlier:

> There may be one thing to be slightly concerned about: ABNF validators.
> Without updating them validation of ABNF that uses this will fail.

In particular, BAP.
Does Bill Fenner still maintain that?

	Thanks,
	Paul

On 8/18/14 8:26 PM, Paul Kyzivat wrote:
> Attached is the notification for a new version containing Barry's
> suggestion.
>
>      Thanks,
>      Paul
>
>
> On 8/18/14 7:31 PM, Barry Leiba wrote:
>>> http://datatracker.ietf.org/doc/draft-kyzivat-case-sensitive-abnf/
>>>
>>> I'm not quite sure what to do with it after this. But I guess we
>>> could start
>>> with comments here.
>>
>> Thanks, Paul.  The only comment I have is that I would make one thing
>> more explicit:
>>
>> OLD
>>     Another way to define a rule that is case sensitive is to specify the
>>     individual characters numerically.
>>
>>     For example:
>>
>>           rulename    =  %d97 %d98 %d99
>>
>>     or
>>
>>           rulename    =  %x61.62.63
>>
>>     will match only the string that comprises only the lowercase
>>     characters, abc.
>>
>> NEW
>>     The way that has been used in the past to define a rule that
>>     is case sensitive is to specify the individual characters
>>     numerically.
>>
>>     For example:
>>
>>           rulename    =  %d97 %d98 %d99
>>
>>     or
>>
>>           rulename    =  %x61.62.63
>>
>>     will match only the string that comprises only the lowercase
>>     characters, abc.  This mechanism has a clear readability
>>     disadvantage, with respect to using a literal text string with
>>     a prefix, and new the prefix mechanism is preferred.
>>
>> END
>>
>> I will be happy to AD-sponsor this any time you're ready for it to go.
>>
>> Barry
>>
>
>
>
>
> _______________________________________________
> abnf-discuss mailing list
> abnf-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/abnf-discuss
>

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