X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Delivered-To: barryleiba.mailing.lists@gmail.com
Received: by 10.107.163.148 with SMTP id m142csp5658ioe;
        Thu, 7 Aug 2014 19:17:19 -0700 (PDT)
X-Received: by 10.68.197.65 with SMTP id is1mr21180970pbc.125.1407464239317;
        Thu, 07 Aug 2014 19:17:19 -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 k10si1280173pdr.197.2014.08.07.19.17.18
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 07 Aug 2014 19:17:19 -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 4CA291B27C9;
	Thu,  7 Aug 2014 19:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1407464238; bh=vtfhHKkVX+m+Kj5X3CLV+LpC6xpjoKsMc8rC9z1i3FY=;
	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=HMHEgLWCkl+azyMSc51BPNVvXvxSz/jjWH6FVyg2UPWrAQuUW5mzOhZJDyyCQd5Xq
	 Q4T00tZe6uToZ/euy2ewTIZVMmohyiDi8Oc448JkOd7KoN/tk+Xku5w12oIbg0spMt
	 vuPqojNxfRwvX01QvaBF89u2SbWOGx+EWG0Wh/GA=
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 C93A41A0502
 for <abnf-discuss@ietfa.amsl.com>; Thu,  7 Aug 2014 19:17:14 -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 ZIRzAlEKedjN for <abnf-discuss@ietfa.amsl.com>;
 Thu,  7 Aug 2014 19:17:13 -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 261611A01F6
 for <abnf-discuss@ietf.org>; Thu,  7 Aug 2014 19:17:13 -0700 (PDT)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19])
 by qmta05.westchester.pa.mail.comcast.net with comcast
 id c1NY1o00B0QuhwU552HCDz; Fri, 08 Aug 2014 02:17:12 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164])
 by omta02.westchester.pa.mail.comcast.net with comcast
 id c2HC1o00J3ZTu2S3N2HCaS; Fri, 08 Aug 2014 02:17:12 +0000
Message-ID: <53E43328.7040503@alum.mit.edu>
Date: Thu, 07 Aug 2014 22:17:12 -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: Ned Freed <ned.freed@mrochek.com>
References: <53E3B22E.5000708@alum.mit.edu>
 <01PB3UKRBQA80000SM@mauve.mrochek.com>
In-Reply-To: <01PB3UKRBQA80000SM@mauve.mrochek.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net;
 s=q20140121; t=1407464232;
 bh=MLSaFcr9ol8w3wehOjSNVgK79BXf/c7y7C+6UU2ln/Q=;
 h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject:
 Content-Type;
 b=XPdlTfsQaVRMXGbLVdMrQg17THUrH68y5Mlk/sVjExMRJvMnqVDzjB4vqboP+odZh
 pzDBytbjzivGcNg5OL+QsJfLPMDSf6nRsd5jFbMKt9dKg4yK0Ew6aC7itZWQrNN7m3
 e8wUmqNNkeO+sDk1Raeq0e8j3ai2BkWaNWTd2Tp9yQj3GSnmZoCaKRMNTbtPkPGbZb
 z2M7V/ToJhrLQON9PUOnZmHyp4pLL6bjn8hAO3kz5rdPYH6ztSLkw9B61TC/JuITyc
 M+B1Rwz2WESH7tVLchcNRwdmuv8MPQ972e2oHCAu/WcOFkMr3smL5YL1HKdPOhkpBP
 a4MWBVpaeTwag==
Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/Zo93rssfAnb3hopJ9bqnVUxAjVg
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 8:05 PM, Ned Freed wrote:
> I would suggest writing this as an extension, not a revision.

I'm not opposed to that, in principle. But I am not sure what that would 
look like.

Certainly the syntax changes can be done incrementally using /=.
The result would be functionally the same, but wouldn't be as readable.

I don't know how I would write the descriptive part as an extension 
document.

 From a practical perspective, why would an extension be better? Would 
it be any easier to put the extension doc through the process to an RFC? 
Why?

After the fact it would certainly be easier for somebody to consult a 
revised document than to consult both the base document and an extension.

	Thanks,
	Paul

>                  Ned
>
>> Here is a concrete proposal for changes to RFC5234 that would add in
>> case-sensitive strings using a prefix:
>
>> 1) Revise the last half of section 2.3 (beginning with "ABNF permits the
>> specification of literal text strings ") as follows:
>
>>     ABNF permits the specification of literal text strings directly,
>>     enclosed in quotation marks.  Hence:
>
>>           command     =  "command string"
>
>>     Literal text strings are interpreted as a concatenated set of
>>     printable characters. The character set for these strings is
>>     US-ASCII.
>
>>     Literal text strings in ABNF may be either case sensitive or case
>>     insensitive. The form of matching used with a literal text string is
>>     denoted by a prefix to the quoted string. The following prefixes are
>>     allowed:
>
>>          %s          =  case-sensitive
>>          %i          =  case-insensitive
>
>>     If no prefix is present then the string is case-insensitive.
>
>>     Hence:
>
>>           rulename = %i"abc"
>
>>     and:
>
>>           rulename = "aBc"
>
>>     will both match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC", and
>>     "ABC".
>
>>     In contrast:
>
>>           rulename = %s"aBc"
>
>>     will match only "aBc", and will not match "abc", "Abc", "abC",
>>     "ABc", "aBC", "AbC", or "ABC".
>> .
>>     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.
>
>> 2) Replace the char-val rule in section 4 with the following:
>
>>           char-val       =  case-insensitive-string /
>>                             case-sensitive-string
>
>>           case-insensitive-string =
>>                             [ "%i" ] quoted-string
>
>>           case-sensitive-string =
>>                             "%s" quoted-string
>
>>           quoted-string  =  DQUOTE *(%x20-21 / %x23-7E) DQUOTE
>>                                  ; quoted string of SP and VCHAR
>>                                  ;  without DQUOTE
>
>
>> Is there an xml2rfc version of RFC5234?
>
>>     Thanks,
>>     Paul
>
>> _______________________________________________
>> 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