[Ietf-message-headers] Re: Jabber-ID header field

Frank Ellermann <nobody@xyzzy.claranet.de> Thu, 14 September 2006 17:20 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GNutN-0007UL-Qg; Thu, 14 Sep 2006 13:20:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GNutM-0007UF-2I for ietf-message-headers@lists.ietf.org; Thu, 14 Sep 2006 13:20:48 -0400
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GNutJ-0003BQ-Oa for ietf-message-headers@lists.ietf.org; Thu, 14 Sep 2006 13:20:48 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GNut9-0007mH-FB for ietf-message-headers@lists.ietf.org; Thu, 14 Sep 2006 19:20:35 +0200
Received: from du-001-021.access.de.clara.net ([212.82.227.21]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Thu, 14 Sep 2006 19:20:35 +0200
Received: from nobody by du-001-021.access.de.clara.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf-message-headers@lists.ietf.org>; Thu, 14 Sep 2006 19:20:35 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: ietf-message-headers@lists.ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Thu, 14 Sep 2006 19:19:40 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 28
Message-ID: <45098F2C.21F8@xyzzy.claranet.de>
References: <45071704.6020400@jabber.org> <45091155.6000507@ninebynine.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: du-001-021.access.de.clara.net
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc:
Subject: [Ietf-message-headers] Re: Jabber-ID header field
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
Errors-To: ietf-message-headers-bounces@ietf.org

Graham Klyne wrote:
 
> why allow the obsolete folding-whitespace (obs-FWS)?

It's more like "inherited" than "allow", it's what you
get if you remove the "F" from ... [FWS] CRLF

Clearly nobody should fold trailing white-space before
the CRLF, that's a MUST NOT in 2822.  The FWS-syntax is:

| FWS =  ([*WSP CRLF] 1*WSP) /   ; Folding white space
|        obs-FWS

With that you inherit obs-FWS (MUST NOT generate etc.)
as soon as you say FWS.  If you then remove the bogus 
folding from ... [FWS] CRLF the rest is the same as
... [ 1*WSP / obs-FWS ] CRLF   

Where "obs" stands for MUST accept + MUST NOT generate.

Getting rid of it would work best in a future 2822bis,
until then obsolete gateways could try strange foldings.

For another attempt to nail this oddity see
<http://permalink.gmane.org/gmane.ietf.rfc.interest/110>
 
Frank



_______________________________________________
Ietf-message-headers mailing list
Ietf-message-headers@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-message-headers