X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Delivered-To: barryleiba.mailing.lists@gmail.com Received: by 10.58.181.71 with SMTP id du7csp60281vec; Thu, 7 Aug 2014 17:23:16 -0700 (PDT) X-Received: by 10.70.14.227 with SMTP id s3mr20757352pdc.88.1407457396319; Thu, 07 Aug 2014 17:23:16 -0700 (PDT) Return-Path: Received: from mail.ietf.org (mail.ietf.org. [2001:1900:3001:11::2c]) by mx.google.com with ESMTPS id hb1si4685789pbd.26.2014.08.07.17.23.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Aug 2014 17:23:16 -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 60B751A0400; Thu, 7 Aug 2014 17:23:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1407457395; bh=7j3y8ZpUXkN3aaVS8DISj5oJ3XFs86Ovn/Amqvc3K6I=; 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=jRd8+YTw+xWIbE7+av1DriayFJMkpHDmMBxJg3uZDxM/QJmnvWY6LX9EXJgrjgCMs lYNnGMwP6SUEsV69jGC+/WMdvC1nWkdG7L9hIjez9AjSIlA2iRbhydpWPU1yN6Xv3N boRVq6I/MbIv17OBJY0BNFWw06cciB8ph1apa6Qk= 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 1587C1A03CA for ; Thu, 7 Aug 2014 17:23:09 -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 NQXqoUu8yuVH for ; Thu, 7 Aug 2014 17:23:06 -0700 (PDT) Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FC151A0309 for ; Thu, 7 Aug 2014 17:23:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4422; q=dns/txt; s=iport; t=1407457386; x=1408666986; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=FIvySsYxiknnoYnivtI+rdMUotsv1Sz7LTRVgDDsv4s=; b=itd/smFqg6x1nhY9yUAzZWBBs7zSSarAAjfYMhIAiUkI9/OuKqLklCab WG7HS+rjmY5DCLyajA8qnevTtC6YV/gZUPujBVYp7YWRgrQA1+xSUrp7L v+LRi44Y7I54DK5OOY4q3i4lCNGBa2CyOYOzmzcVAsovXtPTTci2XJDMX I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjYFAEQX5FOtJV2S/2dsb2JhbABaDoJ/UlcEgnPJVQqHSAEZexZ3hAQBAQQBAQEgEToLEAIBCBoCJgICAiULFRACBAENBYhCDa1xlhcTBIEsjW0zB4J5NoEcBZwbi3yIdIMVQmyBRg X-IronPort-AV: E=Sophos;i="5.01,821,1400025600"; d="scan'208";a="345957408" Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-3.cisco.com with ESMTP; 08 Aug 2014 00:23:05 +0000 Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s780N5uN008154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Aug 2014 00:23:05 GMT Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Thu, 7 Aug 2014 19:23:05 -0500 From: "Joe Hildebrand (jhildebr)" To: Ned Freed , Paul Kyzivat Thread-Topic: [abnf-discuss] Case-sensitive string constants in ABNF Thread-Index: AQHPsmIBLMGVLQ8xdkK4m5QIH+a1a5vF1c+j///yfoA= Date: Fri, 8 Aug 2014 00:23:04 +0000 Message-ID: References: <53E3B22E.5000708@alum.mit.edu> <01PB3UKRBQA80000SM@mauve.mrochek.com> In-Reply-To: <01PB3UKRBQA80000SM@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: <987863CF1C19364094493C33C5D1730A@emea.cisco.com> MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/abnf-discuss/rwo176nOLpCz9jj0OZ4n0BqejwU Cc: "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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: abnf-discuss-bounces@ietf.org Sender: "abnf-discuss" (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 % 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" 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 _______________________________________________ abnf-discuss mailing list abnf-discuss@ietf.org https://www.ietf.org/mailman/listinfo/abnf-discuss