X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Delivered-To: barryleiba.mailing.lists@gmail.com
Received: by 10.58.181.71 with SMTP id du7csp43614vec;
        Wed, 6 Aug 2014 11:36:22 -0700 (PDT)
X-Received: by 10.66.163.164 with SMTP id yj4mr12758052pab.91.1407350182126;
        Wed, 06 Aug 2014 11:36:22 -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 x7si752664pdp.333.2014.08.06.11.36.21
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 06 Aug 2014 11:36:22 -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 1B0221ABC75;
	Wed,  6 Aug 2014 11:36:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1407350181; bh=5Wmz95akDwImubdmSnrD9gpVQTMp1+tSuMvkvurLya8=;
	h=MIME-version:Message-id:Date:From:In-reply-to:References:To:Cc:
	 Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:
	 List-Subscribe:Content-Transfer-Encoding:Content-Type:Sender;
	b=rxeyC6FE1F1tNI4NWEYjwscZsggGr5zswlGrcDgYMteM+zUmtGWdzGmYG91Am+TBj
	 TCEa/VmKAtiDMSB5RTpWIf4xYpHVeSgZ7qR0PVLxsK5VF79Kt7tiWYy+kpnh13z7MJ
	 5TPDixGZfnKgNEVpWGyeEW+lWg2y68m4kKIR13Lk=
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 5E5771ABB33
 for <abnf-discuss@ietfa.amsl.com>; Wed,  6 Aug 2014 11:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level: 
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001,
 SPF_PASS=-0.001] autolearn=ham
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 dn4INUdPftaO for <abnf-discuss@ietfa.amsl.com>;
 Wed,  6 Aug 2014 11:36:17 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17])
 by ietfa.amsl.com (Postfix) with ESMTP id C2B3C1ABC75
 for <abnf-discuss@ietf.org>; Wed,  6 Aug 2014 11:36:15 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com
 (PMDF V6.1-1 #35243) id <01PB24L87BW0000F8W@mauve.mrochek.com> for
 abnf-discuss@ietf.org; Wed, 6 Aug 2014 11:31:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve;
 t=1407349883; bh=JAS1sxP9AsDb+fnHbjgvjkigDDekBd3wswAwqtI0HUQ=;
 h=Cc:Date:From:Subject:In-reply-to:References:To;
 b=XFl97wwr9dzKtreMV+3V61WahFUcHkK9ji+owFMkWRtl48mBW7sF93SXtD5vs2QP2
 4WHPBKX84ox+AIwaFj+IneoxJSo90I1G+1crofYZEwBZsvwycWDd++xzMbNGDHrX+I
 JiTLydMfv61SnEJuo7Ret1L2+sQxDQzgWq36YjZw=
MIME-version: 1.0
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01PB1WDAOHGG0000SM@mauve.mrochek.com>; Wed,
 06 Aug 2014 11:31:10 -0700 (PDT)
Message-id: <01PB24L5SC060000SM@mauve.mrochek.com>
Date: Wed, 06 Aug 2014 11:29:44 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Wed, 06 Aug 2014 13:09:40 -0400"
 <53E26154.8020308@alum.mit.edu>
References: <53E26154.8020308@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/4u-cUW7_Rl3FHgjglF5phNQvlQo
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>

> Has there ever been consideration of supporting case-sensitive string
> constants in ABNF?

> While the case-insensitive ones are more often than not what is needed,
> some protocol designs have places where case-sensitivity is desired. It
> is possible to accomplish this now, using numeric byte values. But it is
> hard, both to read and to write.

Agreed.

> I see no *technical* problem with supporting both kinds. The only
> questions are:
> - Is it a good idea to support both? (Or is *not* supporting them
>    intentional, to discourage case-sensitive syntaxes?)

> - What syntax to use in ABNF to denote the two types, while remaining
>    backward compatible.

> Regarding the syntax, a straightforward approach would be to define
> case-sensitive strings using a new delimiter. Single quote is a likely
> candidate since it is currently unused.

It's the obvious thing, but I worry it will be confusing.

> Another possibility for syntax would be to allow an optional prefix on
> char-val. For example: %S"abc", %I"abc".

I like the idea of using prefixes. I don't especially care about the syntax.

				Ned

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