[rfc-i] tabs [was: sourcecode indentation]

cabo at tzi.org (Carsten Bormann) Tue, 16 February 2016 07:08 UTC

From: cabo at tzi.org (Carsten Bormann)
Date: Tue, 16 Feb 2016 08:08:06 +0100
Subject: [rfc-i] tabs [was: sourcecode indentation]
In-Reply-To: <F5B55E50-D7AA-427A-932C-37D4872F9BD4@cisco.com>
References: <B7E2CCFD-F56B-4749-B8D2-C3F4CFF3EF5F@cisco.com> <56C2B0E8.7070900@it.aoyama.ac.jp> <F5B55E50-D7AA-427A-932C-37D4872F9BD4@cisco.com>
Message-ID: <56C2CAD6.7060500@tzi.org>

The last RFC I can find that contains HT characters is RFC 2329 (this
one is interesting in that has been aggressively tabbified, to the point
of replacing single spaces in the text by tabs whenever they occur
before a multiple-of-8 column).

Since that practice stopped in 1998, Makefiles couldn't be printed
literally in RFCs.
Why would we want to, anyway?  We don't include other binary files
literally, either, and don't use other perfectly fine ASCII characters
such as BS or RS.  (HT is actually worse because there is an illusion
that it might work.  In some cases.)

Gr??e, Carsten


Joe Hildebrand (jhildebr) wrote:
> Alternately, we could just say that tab-encrusted Makefile's aren't supported in an RFC,