X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Delivered-To: barryleiba.mailing.lists@gmail.com
Received: by 10.58.181.71 with SMTP id du7csp60647vec;
        Thu, 7 Aug 2014 17:32:52 -0700 (PDT)
X-Received: by 10.66.232.166 with SMTP id tp6mr20559951pac.127.1407457971983;
        Thu, 07 Aug 2014 17:32:51 -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 al7si4679684pbd.120.2014.08.07.17.32.51
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 07 Aug 2014 17:32:51 -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 A07211A0AF5;
	Thu,  7 Aug 2014 17:32:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1407457970; bh=XyB5/8oUqcKkiniVnAlgYNttSLLFxgBJSxGRH3yPMjY=;
	h=From:To:Date:Message-ID:References:In-Reply-To:Content-ID:
	 MIME-Version:Cc:Subject:List-Id:List-Unsubscribe:List-Archive:
	 List-Post:List-Help:List-Subscribe:Content-Type:
	 Content-Transfer-Encoding:Sender;
	b=jj0AKtaxCBoQaKybC9nRBdnuHGPXI0x0WOr2ekzPk7cIIZavag7sDq7ikMSfKkpKs
	 AdBEdW8Wo1AgMv2gpPQLVy1BHccnUG/0IRJQrZ8DCU2CsueF2DF43Ap7JZr0J/6THd
	 hJmwNhDSbC3I0uAg9AwWSN/ZmUdAcFaBnyzuxYTY=
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 820481A0330
 for <abnf-discuss@ietfa.amsl.com>; Thu,  7 Aug 2014 17:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001,
 SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 U_PgmyYhGnp1 for <abnf-discuss@ietfa.amsl.com>;
 Thu,  7 Aug 2014 17:32:46 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80])
 (using TLSv1 with cipher RC4-SHA (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 6A5101A0AF5
 for <abnf-discuss@ietf.org>; Thu,  7 Aug 2014 17:32:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
 d=cisco.com; i=@cisco.com; l=5400; q=dns/txt; s=iport;
 t=1407457966; x=1408667566;
 h=from:to:cc:subject:date:message-id:references:
 in-reply-to:content-id:content-transfer-encoding: mime-version;
 bh=VUeO+AZud+upyxLoV0kfhIadaC0+DMVjCvWVM+9h98M=;
 b=VtxlBX9+aHMMXzkyYDOVKpDApU8luE4kEwiDErV45uPrXq30SqsFipqu
 hDYkpo1AAdsdegxLf4ONTZ01PAmZ0Z5eu1QlOY+G0XUnYUCWwk2rfT+KW
 ClSnb0wTDC+DR1Nf348oYL0eW2GnE+vqPuRCosKRgCZdSo8y6jeyEGwaX A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjYFANkZ5FOtJA2D/2dsb2JhbABagw1SVwSCc8lVCodIARl7FneEBAEBBAEBASAROgsQAgEIGAICJgICAiULFRACBA4FiEINrWyWFhMEgSyNbTMHgnk2gRwFnBuLfIh0g1dsgUY
X-IronPort-AV: E=Sophos;i="5.01,821,1400025600"; d="scan'208";a="342842968"
Received: from alln-core-1.cisco.com ([173.36.13.131])
 by rcdn-iport-9.cisco.com with ESMTP; 08 Aug 2014 00:32:45 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81])
 by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s780Wj7D018065
 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
 Fri, 8 Aug 2014 00:32:45 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by
 xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Thu, 7
 Aug 2014 19:32:45 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Ned Freed <ned.freed@mrochek.com>
Thread-Topic: [abnf-discuss] Case-sensitive string constants in ABNF
Thread-Index: AQHPsmIBLMGVLQ8xdkK4m5QIH+a1a5vF1c+j///yfoCAABKlKf//8BAA
Date: Fri, 8 Aug 2014 00:32:45 +0000
Message-ID: <94814907-393C-41CB-8702-417CE06E3267@cisco.com>
References: <53E3B22E.5000708@alum.mit.edu>
 <01PB3UKRBQA80000SM@mauve.mrochek.com>
 <EC991A58-9852-4467-AC89-102E72CFDFEE@cisco.com>
 <01PB3V7RZSXK0000SM@mauve.mrochek.com>
In-Reply-To: <01PB3V7RZSXK0000SM@mauve.mrochek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/15.3.0.140730
x-originating-ip: [10.21.103.202]
Content-ID: <F25C492297B44943974493D7EFC3D6C9@emea.cisco.com>
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/f_xLx-65o-B_1csKjAcT-LPjGf4
Cc: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>,
 Paul Kyzivat <pkyzivat@alum.mit.edu>
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: abnf-discuss-bounces@ietf.org
Sender: "abnf-discuss" <abnf-discuss-bounces@ietf.org>

Slight rephrase.  What would you think about an update to 5234 that did 
nothing but add a syntax extension capability?

On 8/8/14, 12:23 AM, "Ned Freed" <ned.freed@mrochek.com> wrote:

>No formal way that I know of. So publishing a document that makes the 
>changes
>either as an addendum or replacement seems like the only way.
>
>				Ned
>
>> (timidly entering back into the conversation, hopefully following what's
>> *actually* being talked about this time)
>
>> Is there a generic way to do syntax extensions in ABNF?  For example, if
>> we defined that %<foo> was a syntax extension in the core spec, we could
>> tell folks to ignore extensions they don't understand, and throw them 
>>all
>> in a registry.
>
>> On 8/8/14, 12:05 AM, "Ned Freed" <ned.freed@mrochek.com> wrote:
>
>> >I would suggest writing this as an extension, not a revision.
>> >
>> >				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
>> >
>
>
>> --
>> Joe Hildebrand
>
>
>
>


-- 
Joe Hildebrand



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