Re: bad rfc text

William Allen Simpson <wsimpson@greendragon.com> Sun, 12 September 1999 18:30 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id OAA01652 for ietf-outbound.10@ietf.org; Sun, 12 Sep 1999 14:30:02 -0400 (EDT)
Received: from runningman.rs.itd.umich.edu (runningman.rs.itd.umich.edu [141.211.144.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01610 for <ietf@ietf.org>; Sun, 12 Sep 1999 14:22:17 -0400 (EDT)
Received: from greendragon.com (pm457-17.dialip.mich.net [198.110.21.123]) by runningman.rs.itd.umich.edu (8.8.5/2.3) with ESMTP id OAA12805 for <ietf@ietf.org>; Sun, 12 Sep 1999 14:22:17 -0400 (EDT)
Message-ID: <37DBEEB9.56E8B6B9@greendragon.com>
Date: Sun, 12 Sep 1999 14:19:37 -0400
From: William Allen Simpson <wsimpson@greendragon.com>
X-Mailer: Mozilla 4.6 (Macintosh; U; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: bad rfc text
References: <37DBD7C6.D0ED485B@greendragon.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hmmm, on inspection, there are a lot of early RFCs from ISI that are not on
ietf.org.  But there are at least 2 at ietf.org that are not at ISI (rfc17
and 189).

WSimpson@UMich.edu
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32