X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: barryleiba.mailing.lists@gmail.com Received: by 10.58.181.71 with SMTP id du7csp45365vec; Wed, 6 Aug 2014 12:04:49 -0700 (PDT) X-Received: by 10.70.133.33 with SMTP id oz1mr13078369pdb.72.1407351888844; Wed, 06 Aug 2014 12:04:48 -0700 (PDT) Return-Path: Received: from mail.ietf.org (mail.ietf.org. [2001:1900:3001:11::2c]) by mx.google.com with ESMTPS id df8si784940pdb.197.2014.08.06.12.04.47 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Aug 2014 12:04:47 -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 DDABA1B27D2; Wed, 6 Aug 2014 12:04:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1407351886; bh=OlZ+R9tQJNfltepj+u6vC1oyQ7j90Inw+VeIKra8vAw=; 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=AijgpK2sFbI0aa4IAL2QoINZvY3h95q1ak8P3Vb+H53pPI52FCJM13Pwd9XPJ08c8 vk8mkqO012/dCUERjQb8K6Xmu+hPVteBKhcBfwlNQzqcSrxOpZlMEhZNjGkUWXfOcd cN22W1F0GsUlGNMFG0aZJKiBphGj831vzuIJLMkI= 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 8E1491ACD01 for ; Wed, 6 Aug 2014 12:04:45 -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 M8gSq06cPFMg for ; Wed, 6 Aug 2014 12:04:44 -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 5A8AE1B27A6 for ; Wed, 6 Aug 2014 12:04:44 -0700 (PDT) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta05.westchester.pa.mail.comcast.net with comcast id bS6t1o00217dt5G55X4joG; Wed, 06 Aug 2014 19:04:43 +0000 Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta13.westchester.pa.mail.comcast.net with comcast id bX4j1o00d3ZTu2S3ZX4jDG; Wed, 06 Aug 2014 19:04:43 +0000 Message-ID: <53E27C4B.3050003@alum.mit.edu> Date: Wed, 06 Aug 2014 15:04:43 -0400 From: Paul Kyzivat 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: Dave Crocker , "abnf-discuss@ietf.org" References: <53E26154.8020308@alum.mit.edu> <53E26391.6060208@gmail.com> In-Reply-To: <53E26391.6060208@gmail.com> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1407351883; bh=UdOWBbFEkOBO2rgUKpjCUm0EbTi6FlwYcA2GONMyf8s=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=lsiDN+xBDRsDs3QDRy2SLOXp98ZnC23XSQ7o4e2piezKns4khpcr3mb66db9xRX4+ A/IQIeWw6R5A652C5JKuNwuR1OnRaQqCWlM8j6QoNfWD+HEKW7meowa8z1+vB4O1F9 3SpMk8fLPALy7UsIP+Zk0eNAdhGFPXOTtEzlBHmfwHjCAlPXx5VEn9x2hNW35kHAwU f7Q+fMJ9B6ay/tUpekd+H+W/WfopdERsM0hRV7ko9DKWf4xy77Y0x+U14/sQ4PAzjG RIwK/YHdjq8kKGsB90OibHaaPMsKtN3eSX5gGAW56HHp6LN2LCkcCjYW3N3u9z2H6u vQOEeQclohrLA== Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/BwKp2XJk010BHywrGpZc-1u1ibA 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: abnf-discuss-bounces@ietf.org Sender: "abnf-discuss" On 8/6/14 1:19 PM, Dave Crocker wrote: > On 8/6/2014 10:09 AM, Paul Kyzivat wrote: >> >> 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?) > > > As I recall, it's come up more than once. > > The issue seems to be that there has not been enough community pressure > to warrant embedding the construct into the core specification. > > Personally, I think it would be a nice example of a useful "extension" > that might warrant some sort of IANA registry, so that there is an > established library of ABNF rulesets. If you want to go that way, then ISTM there is the need for some sort of extension framework for ABNF. There would be need for a way for a particular grammar to declare what extension(s) it depends upon. It also could lead to fragmentation, where not all tools support the same extensions. > All this presumes continued broad use of ABNF, rather than any of the > newer and presumably spiffier specification conventions... Maybe its just my age, but for me it remains the go-to tool for modest grammars. It is very approachable - most people that have reason to understand a formal syntax can pick up ABNF quickly. (The quoted strings are the thing that seem most confusing.) Thanks, Paul _______________________________________________ abnf-discuss mailing list abnf-discuss@ietf.org https://www.ietf.org/mailman/listinfo/abnf-discuss