Re: ietf-nntp Issues with new draft
Stan Barber <sob@academ.com> Thu, 04 September 1997 15:29 UTC
Received: from cnri by ietf.org id aa10434; 4 Sep 97 11:29 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 LAA02451 for <ietf-archive@cnri.reston.va.us>; Thu, 4 Sep 1997 11:32:32 -0400 (EDT)
Received: (from majordomo@localhost) by announcer.academ.com (8.8.5/8.8.5) id KAA02602; Thu, 4 Sep 1997 10:28:40 -0500 (CDT)
Received: from academ.com (sob@ACADEM.COM [198.137.249.2]) by announcer.academ.com (8.8.5/8.8.5) with ESMTP id KAA02597 for <ietf-nntp@ANNOUNCER.ACADEM.COM>; Thu, 4 Sep 1997 10:28:38 -0500 (CDT)
Received: (from sob@localhost) by academ.com (8.8.5/8.8.5) id KAA01260; Thu, 4 Sep 1997 10:28:31 -0500 (CDT)
Message-Id: <199709041528.KAA01260@academ.com>
From: Stan Barber <sob@academ.com>
Date: Thu, 04 Sep 1997 10:28:30 -0500
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Nat Ballou <NatBa@ims.microsoft.com>, NNTP Working Group <ietf-nntp@academ.com>
Subject: Re: ietf-nntp Issues with new draft
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
Nat, The x8x response codes were always intended to be used by non-standard extensions. It makes no sense to continue to use them for something that will now be a standard extension. If we are going to use the x8x for authentication and identification, we can't use them for non-standard extensions. -- 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 Issues with new draft Nat Ballou
- Re: ietf-nntp Issues with new draft Stan Barber
- Re: ietf-nntp Issues with new draft Nat Ballou