RE: ietf-nntp NNTP doubling of starting periods

Michael Nerone <mnerone@fibrcom.com> Fri, 15 November 1996 18:55 UTC

Received: from cnri by ietf.org id aa02693; 15 Nov 96 13:55 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa17142; 15 Nov 96 13:55 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.7.6/8.7.3) id MAA03030 for ietf-nntp-outgoing; Fri, 15 Nov 1996 12:09:04 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.7.6/8.7.3) with ESMTP id MAA03025 for <ietf-nntp@ACADEM2.ACADEM.COM>; Fri, 15 Nov 1996 12:09:02 -0600 (CST)
Received: from midway.fibr.net (midway.fibr.net [204.57.66.2]) by academ.com (8.7.6/8.7.1) with ESMTP id MAA21482 for <ietf-nntp@academ.com>; Fri, 15 Nov 1996 12:08:59 -0600 (CST)
Received: from stark.fibrcom.com (stark.fibrcom.com [204.17.217.38]) by midway.fibr.net (8.7.5/8.7.3) with SMTP id MAA27735 for <ietf-nntp@academ.com>; Fri, 15 Nov 1996 12:08:57 -0600 (CST)
Received: by stark.fibrcom.com with Microsoft Mail id <01BBD2ED.D81ECD40@stark.fibrcom.com>; Fri, 15 Nov 1996 12:09:25 -0600
Message-ID: <01BBD2ED.D81ECD40@stark.fibrcom.com>
From: Michael Nerone <mnerone@fibrcom.com>
To: 'IETF NNTP Mailing List' <ietf-nntp@academ.com>
Subject: RE: ietf-nntp NNTP doubling of starting periods
Date: Fri, 15 Nov 1996 12:09:22 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Aww...but that might save us 1 byte out of every few hundred articles!!! That's worth breaking a few thousand servers, isn't it?!? <g>

----------
From: 	dread@texas.net[SMTP:dread@texas.net]
Sent: 	Friday, 15 November, 1996 03:34
To: 	ietf-nntp@academ.com
Subject: 	Re: ietf-nntp NNTP doubling of starting periods 

 ----------
>From: Mailer-Daemon
>To: Don Read
>Subject: Re: ietf-nntp NNTP doubling of starting periods
>Date: Friday, November 15, 1996 12:49AM
>
>
>> RFC 977 specifies the following for lines that start with a period (.)
>> > [...]
>> Is this still in use? It seems unnecessary to distinguish lines that

<snip>

>
>The current scheme provides transparency.  Senders add a dot to every
>line that begins with a dot.  Receivers remove the initial dot from
>any line that begins with a dot.  It's simple, it works, and anyone
>can understand how to do it right.
>
>Changing the spec can only lead to confusion and breakage.
>It's not broken, so don't fix it.
>

I agree !!!!