X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
Delivered-To: barryleiba.mailing.lists@gmail.com
Received: by 10.107.163.148 with SMTP id m142csp7165ioe;
        Thu, 7 Aug 2014 19:36:39 -0700 (PDT)
X-Received: by 10.70.88.105 with SMTP id bf9mr21620658pdb.54.1407465398889;
        Thu, 07 Aug 2014 19:36:38 -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 gr3si4863944pbb.210.2014.08.07.19.36.38
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 07 Aug 2014 19:36:38 -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 CE0431A0538;
	Thu,  7 Aug 2014 19:36:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1407465397; bh=4Pm62lfNg7pP54tNa/BAWpQTu/+aPK8AC1xDAEiOYoI=;
	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-Type:Content-Transfer-Encoding:Sender;
	b=vCJFwmqzEtEeyltJvAEUUxHdnu6cL90H/9gc4sXdErQy9MDY8t6VmTPmu7DxKLrWU
	 gtp2N7XmQS+osqQohMd41TxTnUC+cjFcjFls9Pith5NdXdVLfj1ZNUt1o1crKubVmi
	 D7E4d3KU7jZ4U6PSBt5CdcyDF3vzerTpagHrtlaQ=
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 C307D1A043D
 for <abnf-discuss@ietfa.amsl.com>; Thu,  7 Aug 2014 19:36:36 -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 HtTRa2aGB7B0 for <abnf-discuss@ietfa.amsl.com>;
 Thu,  7 Aug 2014 19:36:34 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17])
 by ietfa.amsl.com (Postfix) with ESMTP id C41A11A0424
 for <abnf-discuss@ietf.org>; Thu,  7 Aug 2014 19:36:34 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com
 (PMDF V6.1-1 #35243) id <01PB3ZN3AQ8W000KCK@mauve.mrochek.com> for
 abnf-discuss@ietf.org; Thu, 7 Aug 2014 19:31:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve;
 t=1407465103; bh=HHOVdLZBihZnqmDlOMLbj5nqilIZ8tiGBRtmg2EOtDc=;
 h=Cc:Date:From:Subject:In-reply-to:References:To;
 b=UxZqqt1TfvAXI70l6L92YVBFtKKOzsOkCIkwAPHPu3KKXzgVnG6UpXiK0OM6TeaZK
 2+en7gvG5vADtHxq1J0HUkJAKZvYsFoqrkcOVwps+jn9ZbNjMaW7n2yixegdvXpgp0
 gPLndYN9QmGHFiIHBiWBRMQEoYfNGY0WMWvvZ9Cg=
MIME-version: 1.0
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243)
 id <01PB2RFWCBO00000SM@mauve.mrochek.com>; Thu,
 07 Aug 2014 19:31:29 -0700 (PDT)
Message-id: <01PB3ZN11FOS0000SM@mauve.mrochek.com>
Date: Thu, 07 Aug 2014 19:30:15 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 08 Aug 2014 00:32:45 +0000"
 <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>
 <94814907-393C-41CB-8702-417CE06E3267@cisco.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/7TaITQtkNgXYLiOep-Q7rTzqi5Y
Cc: Ned Freed <ned.freed@mrochek.com>,
 "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?

I'd have to see it to say. Given this is the first extension I've seen ~6
years I think has made some sense, I don't see a pressing need for such a
mechanism. But I'm not opposed to one either.

				Ned

> 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

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