Re: ietf-nntp NNTP doubling of starting periods

Keith Moore <moore@cs.utk.edu> Thu, 14 November 1996 23:28 UTC

Received: from cnri by ietf.org id aa00996; 14 Nov 96 18:28 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa26678; 14 Nov 96 18:28 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.7.6/8.7.3) id RAA00275 for ietf-nntp-outgoing; Thu, 14 Nov 1996 17:23:36 -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 RAA00270 for <ietf-nntp@ACADEM2.ACADEM.COM>; Thu, 14 Nov 1996 17:23:34 -0600 (CST)
Received: from ig.cs.utk.edu ([128.169.94.149]) by academ.com (8.7.6/8.7.1) with ESMTP id RAA10371; Thu, 14 Nov 1996 17:23:31 -0600 (CST)
Received: from localhost by ig.cs.utk.edu with SMTP (cf v2.11c-UTK) id SAA18791; Thu, 14 Nov 1996 18:21:32 -0500 (EST)
Message-Id: <199611142321.SAA18791@ig.cs.utk.edu>
X-Mailer: exmh version 1.6.7 5/3/96
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Jean van Waterschoot <jvwater@mcs.net>
cc: Stan Barber <sob@academ.com>, ietf-nntp@academ.com, moore@cs.utk.edu
Subject: Re: ietf-nntp NNTP doubling of starting periods
In-reply-to: Your message of "Wed, 13 Nov 1996 01:37:31 CST." <199611130737.BAA05943@Kitten.mcs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 14 Nov 1996 18:21:32 -0500
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> RFC 977 specifies the following for lines that start with a period (.)
> > [...]
> Is this still in use? It seems unnecessary to distinguish lines that
> contain *only* a period (etx) from text lines that start with a period. Any
> parser should be able to recognize that <cr><lf>.<cr><lf> is the end of the
> data stream and treat lines that start with a period as normal text lines.
>
> I tried sending lines that started with 1-5 periods on a line through INN
> and it passed them unaltered as the second paragraph suggests it should.
> 
> If this is not used should it be phased out for the sake of
> transparency? 

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.

Keith