IETF Logo Mail Archive

[ietf-822] Wherefore no HTAB in literal text strings in ABNF

Sean Leonard <dev+ietf@seantek.com> Mon, 15 August 2016 01:34 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CF7112D17E; Sun, 14 Aug 2016 18:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=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 4UdYSCR0eIMi; Sun, 14 Aug 2016 18:34:37 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E3B112D180; Sun, 14 Aug 2016 18:34:37 -0700 (PDT)
Received: from [192.168.123.110] (unknown [75.83.2.34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 18375509B5; Sun, 14 Aug 2016 21:34:35 -0400 (EDT)
From: Sean Leonard <dev+ietf@seantek.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CCAE9E2-DCE8-4AEC-9FDE-FA00A0C3727E@seantek.com>
Date: Sun, 14 Aug 2016 18:34:56 -0700
To: ABNF-Discuss <abnf-discuss@ietf.org>, ietf-822@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/KNaqZf8z9JsoAgxZ5kaGIOng1rU>
Subject: [ietf-822] Wherefore no HTAB in literal text strings in ABNF
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Aug 2016 01:34:39 -0000

Hello Knowledgeable ABNF Folks:

I have been working with RFC 5234 lately. What is the rationale (or what are the rationales) for including SP %d32 but excluding HTAB %d9 in char-val, aka the literal text string? I am sure that this decision was not an oversight.

It may be appreciated that the comment production is defined as WSP, which includes HTAB.

Regards,

Sean

v2.23.0 | Report a Bug | By Email