Received-SPF: pass (google.com: domain of abnf-discuss-bounces@ietf.org designates 4.31.198.44 as permitted sender) client-ip=4.31.198.44;
Message-ID: <53F299A9.1080209@alum.mit.edu>
Date: Mon, 18 Aug 2014 20:26:17 -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: Barry Leiba <barryleiba@computer.org>
References: <53E3B22E.5000708@alum.mit.edu>	<53EF8C18.3030004@alum.mit.edu>
 <CAC4RtVCii_j-54ixnuB6CqwQZSO_9rQstjqswDXsfuSy9ChDnA@mail.gmail.com>
In-Reply-To: <CAC4RtVCii_j-54ixnuB6CqwQZSO_9rQstjqswDXsfuSy9ChDnA@mail.gmail.com>
Content-Type: multipart/mixed; boundary="------------040208010707020306010106"
Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/Dli0qLULL5JBMwgrHqmPpvPG8Tc
Cc: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>
Subject: Re: [abnf-discuss] Case-sensitive string constants in ABNF
Precedence: list
Errors-To: abnf-discuss-bounces@ietf.org
Sender: "abnf-discuss" <abnf-discuss-bounces@ietf.org>

This is a multi-part message in MIME format.
--------------040208010707020306010106
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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
>


--------------040208010707020306010106
Content-Type: message/rfc822;
 name="Attached Message"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Attached Message"

X-Account-Key: account2
X-Mozilla-Keys: 
Return-Path: srs0=8h6e=5n=ietf.org=internet-drafts@alum.mit.edu
Received: from imta38.emeryville.ca.mail.comcast.net (LHLO
 imta38.emeryville.ca.mail.comcast.net) (76.96.30.98) by
 resmail-ch2-746v.sys.comcast.net with LMTP; Tue, 19 Aug 2014 00:13:59 +0000
 (UTC)
Received: from alum-mailsec-relay-3.mit.edu ([18.7.68.23])
	by imta38.emeryville.ca.mail.comcast.net with comcast
	id gQDy1o00V0W76AS0eQDyi3; Tue, 19 Aug 2014 00:13:59 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.1 cv=ENI/jTpC c=1 sm=1 tr=0
 a=PHWJ+KZMwVVO+RvU96ZAxQ==:117 a=14+JVjaIrF5vHQZXOdm4Ag==:17 a=C_IRinGWAAAA:8
 a=GGcpBh7Jt_oA:10 a=P6x1oVJDhoMA:10 a=gYzrTTrTaaQA:10 a=LSVET5z0puwA:10
 a=P8NLjCSqv-4A:10 a=wPDyFdB5xvgA:10 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10
 a=48vgC7mUAAAA:8 a=jGqiy6jZAAAA:8 a=UFUWElBiugZwCt4jZVoA:9 a=QEXdDO2ut3YA:10
Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15])
	by alum-mailsec-relay-3.mit.edu (8.14.7/8.12.8) with ESMTP id s7J0DlnJ016312
	for <pkyzivat@alum.mit.edu>; Mon, 18 Aug 2014 20:13:57 -0400
X-AuditID: 1207440f-f79156d000006a5c-a6-53f296c4a997
Authentication-Results: symauth.service.identifier
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44])
	(using TLS with cipher AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id B5.9F.27228.5C692F35; Mon, 18 Aug 2014 20:13:57 -0400 (EDT)
Received: from localhost (ietfa.amsl.com [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id A0A701A6F72
	for <pkyzivat@alum.mit.edu>; Mon, 18 Aug 2014 17:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.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 7sGXwhp56uzi for <pkyzivat@alum.mit.edu>;
	Mon, 18 Aug 2014 17:13:55 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 8C3D21A6FB1;
	Mon, 18 Aug 2014 17:13:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: Paul Kyzivat <pkyzivat@alum.mit.edu>,
        "Paul Kyzivat" <pkyzivat@alum.mit.edu>
Subject: New Version Notification for draft-kyzivat-case-sensitive-abnf-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p5
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140819001354.27833.41157.idtracker@ietfa.amsl.com>
Date: Mon, 18 Aug 2014 17:13:54 -0700
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrIKsWRWlGSWpSXmKPExsXCIn9MR/fotE/BBv/PKlms2HCA1YHR4+/7
	D0wBjFFcNimpOZllqUX6dglcGTOefmYteMdR8aT9BnMD4yO2LkZODgkBE4mrm7aD2YwCRhK7
	z71ihYiLSVy4tx4ozsUhJLCQSeLPt/2sEM4mRok7d06xQFRpSMxYeYERInGFUWJT126oqqmM
	Ei/Wf2MEqeIVEJQ4OfMJUAcHB7OApsT6XfogYWYBeYntb+cwg9hsAnISq19NAysXEQiS2D31
	ENhJwgJ+Evtm7GKGWCYi8e7qQyhbSmLLx8usEGfLSfw49pgJxBYQEJD4N+kCC8RaR4l381+B
	zWQRUJU48m8zywRGkVlILpqFcNEsJBctYGRexSiXmFOaq5ubmJlTnJqsW5ycmJeXWqRropeb
	WaKXmlK6iREY9kLsLvw7GLvWyxxiFOBgVOLhPfHxY7AQa2JZcWXuIUZJDiYlUd6lnZ+ChfiS
	8lMqMxKLM+KLSnNSiw8xSnAwK4nwtk4GyvGmJFZWpRblw6SkOViUxHnVl6j7CQmkJ5akZqem
	FqQWwWSZONgPMcpwcChJ8J6ZCtQtWJSanlqRlplTgqyGE0RwgazhAVrzDKSQt7ggMbc4Mx2i
	6BSjopQ4b/EUoIQASCKjNA9uACxVXWKUlRLmZWRgYBDiAboA6HFU+UeMghwv2YXYuJhS8wRU
	pFjy8vNSXzGKAwNCmLcHZCVPZl4J3MZXQMcwAR2zdfFHkGNKEhFSUg2MaSXG+u+mXd4SHci7
	uWFS1+FnQXNeND6/X6HcY8U3S5j1+ZJje9k8J735KS4YIftzV9zBc5GPX3Fu3Wn2r+HVZZuJ
	izgebAuP0O+989Fshcm3+6p7W3uWR3/sOdlTWjXzW++TavmGW+fa157dtV5+uR37M/aNOu4f
	3J/d+phYaBge93mv7/YpR5RYijMSDbWYi4oTAa+W5XBkAwAA


A new version of I-D, draft-kyzivat-case-sensitive-abnf-01.txt
has been successfully submitted by Paul Kyzivat and posted to the
IETF repository.

Name:		draft-kyzivat-case-sensitive-abnf
Revision:	01
Title:		Case-Sensitive String Support in ABNF
Document date:	2014-08-18
Group:		Individual Submission
Pages:		4
URL:            http://www.ietf.org/internet-drafts/draft-kyzivat-case-sensitive-abnf-01.txt
Status:         https://datatracker.ietf.org/doc/draft-kyzivat-case-sensitive-abnf/
Htmlized:       http://tools.ietf.org/html/draft-kyzivat-case-sensitive-abnf-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-kyzivat-case-sensitive-abnf-01

Abstract:
   This document extends the base definition of ABNF (Augmented Mackus-
   Naur Form) to include a way to specify ASCII string literals that are
   matched in a case-sensitive manner.

                                                                                  
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--------------040208010707020306010106
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--------------040208010707020306010106--