IETF Logo Mail Archive

Re: ietf-nntp Thoughts on renaming X commands

Stan Barber <sob@academ.com> Wed, 16 October 1996 06:02 UTC

Received: from cnri by ietf.org id aa06495; 16 Oct 96 2:02 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa03330; 16 Oct 96 2:02 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id BAA18453 for ietf-nntp-outgoing; Wed, 16 Oct 1996 01:00:10 -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 BAA18449 for <ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 16 Oct 1996 01:00:08 -0500
Received: (from sob@localhost) by academ.com (8.7.6/8.7.1) id BAA04700; Wed, 16 Oct 1996 01:00:06 -0500 (CDT)
Message-Id: <199610160600.BAA04700@academ.com>
From: Stan Barber <sob@academ.com>
Date: Wed, 16 Oct 1996 01:00:06 CDT
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Keith Moore <moore@cs.utk.edu>, NetWin Support <netwin@world.std.com>
Subject: Re: ietf-nntp Thoughts on renaming X commands
Cc: ietf-nntp@academ.com
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

> > >the purpose of the doing this work in the first place.
> > 
> > To document existing practice and define a mechanism for future work?
> 
> Yes, this is what we discussed at the Montreal BOF:
> 
> 1. Document existing practice

RFC 977 + draft-barber-nntp-imp-05.txt mostly cover this. 

> 2. Define an extension negotiation mechanism

First cut of this is draft-barber-nntp-news-00.txt

> 3. After (and only after) the above two are done, the group can 
>    review suggested extensions that people want to submit.

First one of these is  draft-hernacki-nntpsrch-00.txt.
-- 
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.

v2.8.7 | Report a Bug | By Email