Re: ietf-nntp Initial draft FINALLY available
Stan Barber <sob@academ.com> Wed, 02 October 1996 14:50 UTC
Received: from cnri by ietf.org id aa06460; 2 Oct 96 10:50 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa11165;
2 Oct 96 10:50 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
JAA24176 for ietf-nntp-outgoing; Wed, 2 Oct 1996 09:47:34 -0500
X-Authentication-Warning: pheasant.ACADEM.COM: majordom set sender to
owner-ietf-nntp using -f
Received: from academ.com (sob@ACADEM.COM [198.137.249.2]) by
pheasant.ACADEM.COM (8.7.5/8.7.3) with ESMTP id JAA24172 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 09:47:32 -0500
Received: (from sob@localhost) by academ.com (8.7.6/8.7.1) id JAA23968;
Wed, 2 Oct 1996 09:47:30 -0500 (CDT)
Message-Id: <199610021447.JAA23968@academ.com>
From: Stan Barber <sob@academ.com>
Date: Wed, 2 Oct 1996 09:47:30 CDT
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Brian Kantor <brian@nothing.ucsd.edu>, ietf-nntp@academ.com
Subject: Re: ietf-nntp Initial draft FINALLY available
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
Brian, please be more specific in what you think is common practice that should be documented in the document that is not. Otherwise, I don't know exactly what you are referring to and can't try to fix it. Additionally, I intend that the NNTP extensions draft move forward to informational sometime soon (as an independent activity). Perhaps that will address whatever problem you are writing about. Please comment further. -- Stan | Academ Consulting Services |internet: sob@academ.com Olan | For more info on academ, see this |uucp: {mcsun|amdahl}!academ!sob Barber | URL- http://www.academ.com/academ |Opinions expressed are only mine.
- ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available Chris Caputo
- Re: ietf-nntp Initial draft FINALLY available James Fidell
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Ramanan
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Rich Salz
- Re: ietf-nntp Initial draft FINALLY available Nat Ballou
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Thomas 'Mike' Michlmayr
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available Bob Sloane
- Re: ietf-nntp Initial draft FINALLY available Stan Barber
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Brian Kantor
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available USENET news manager
- Re: ietf-nntp Initial draft FINALLY available Evan Champion
- Re: ietf-nntp Initial draft FINALLY available chris (c.) lewis
- Re: ietf-nntp Initial draft FINALLY available William H. Magill
- Re: ietf-nntp Initial draft FINALLY available Ben Polk
- ietf-nntp XHDR versus XPAT USENET news manager