ietf-nntp Why not the Streaming Extensions in the Draft?

Jonathan Grobe <grobe@worf.netins.net> Fri, 05 September 1997 17:48 UTC

Received: from cnri by ietf.org id aa16382; 5 Sep 97 13:48 EDT
Received: from announcer.academ.com (majordomo@ANNOUNCER.ACADEM.COM [198.137.249.60]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid NAA06684 for <ietf-archive@cnri.reston.va.us>; Fri, 5 Sep 1997 13:51:39 -0400 (EDT)
Received: (from majordomo@localhost) by announcer.academ.com (8.8.5/8.8.5) id MAA08437; Fri, 5 Sep 1997 12:46:45 -0500 (CDT)
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by announcer.academ.com (8.8.5/8.8.5) with ESMTP id MAA08431 for <ietf-nntp@ANNOUNCER.ACADEM.COM>; Fri, 5 Sep 1997 12:46:43 -0500 (CDT)
Received: from ins6.netins.net (ins6.netins.net [167.142.225.6]) by academ.com (8.8.5/8.8.5) with ESMTP id MAA13158 for <ietf-nntp@academ.com>; Fri, 5 Sep 1997 12:46:41 -0500 (CDT)
Received: from worf.netins.net (grobe@worf.netins.net [167.142.225.4]) by ins6.netins.net (8.8.7/8.8.7) with SMTP id MAA26651 for <ietf-nntp@academ.com>; Fri, 5 Sep 1997 12:46:35 -0500 (CDT)
Date: Fri, 05 Sep 1997 12:46:35 -0500
From: Jonathan Grobe <grobe@worf.netins.net>
To: ietf-nntp@academ.com
Subject: ietf-nntp Why not the Streaming Extensions in the Draft?
Message-ID: <Pine.OSF.3.96.970905124031.24076A-100000@worf.netins.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

What was the rationale for not including the streaming extensions
in the new draft?

Jonathan Grobe.