ietf-nntp Why are RFCs hard formatted?
"J.B. Nicholson-Owens" <jbn@mystery-train.cu-online.com> Mon, 30 September 1996 18:59 UTC
Received: from cnri by ietf.org id aa18432; 30 Sep 96 14:59 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa06022;
30 Sep 96 14:59 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
NAA19476 for ietf-nntp-outgoing; Mon, 30 Sep 1996 13:57:10 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to
owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by
pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id NAA19472 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Mon, 30 Sep 1996 13:57:08 -0500
Received: from mystery-train.cu-online.com (mystery-train.cu-online.com
[205.198.248.104]) by academ.com (8.7.6/8.7.1) with SMTP id NAA14531 for
<ietf-nntp@academ.com>; Mon, 30 Sep 1996 13:57:04 -0500 (CDT)
Received: by mystery-train.cu-online.com (NX5.67d/NX3.0M)
id AA02031; Mon, 30 Sep 96 13:56:54 -0500
Date: Mon, 30 Sep 96 13:56:54 -0500
From: "J.B. Nicholson-Owens" <jbn@mystery-train.cu-online.com>
Message-Id: <9609301856.AA02031@mystery-train.cu-online.com>
To: ietf-nntp@academ.com
Subject: ietf-nntp Why are RFCs hard formatted?
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
Thanks for releasing the first draft of the NNTP spec. Out of curiosity, why are RFCs distributed with hard page formatting, even RFCs that don't have tables of contents or internal references to pages? Is there a place where unformatted RFCs can be downloaded?
- ietf-nntp Why are RFCs hard formatted? J.B. Nicholson-Owens
- Re: ietf-nntp Why are RFCs hard formatted? Stan Barber