Re: ietf-nntp Initial draft FINALLY available
Stan Barber <sob@academ.com> Wed, 02 October 1996 05:34 UTC
Received: from cnri by ietf.org id aa19334; 2 Oct 96 1:34 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa02349;
2 Oct 96 1:34 EDT
Received: (from majordom@localhost) by pheasant.ACADEM.COM (8.7.5/8.7.3) id
AAA22999 for ietf-nntp-outgoing; Wed, 2 Oct 1996 00:28:32 -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 AAA22995 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Wed, 2 Oct 1996 00:28:30 -0500
Received: (from sob@localhost) by academ.com (8.7.6/8.7.1) id AAA16702;
Wed, 2 Oct 1996 00:28:27 -0500 (CDT)
Message-Id: <199610020528.AAA16702@academ.com>
From: Stan Barber <sob@academ.com>
Date: Wed, 2 Oct 1996 00:28:27 CDT
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
To: Ben Polk <bpolk@netscape.com>, ietf-nntp@academ.com
Subject: Re: ietf-nntp Initial draft FINALLY available
Sender: owner-ietf-nntp@academ.com
Precedence: bulk
> At 11:37 PM 10/1/96 CDT, Stan Barber wrote: > > >> >9.1 AUTHINFO > >> > >> The AUTHINFO SIMPLE and AUTHINFO GENERIC commands are listed, but not the > >> plain (and widely used) AUTHINFO USER|PASS command. Is this intentional? > > > > > >Yes. > > Why? Isn't this what most software is using today? There is no need for both AUTHINFO (original) and AUTHINFO SIMPLE since they are so similar. We don't need both, so I chose one. If folks think that it should be the other one, I don't have a problem with that. > > >> Hmmmm. A couple of questions. First, why is this command renamed from > >> XOVER? > >X commands are not part of the spec. > > Can we consider explicitly supporting some subset of the X commands > in the spec? Is the problem with including them in this spec and > prohibiting their use as local extensions an aesthetic one, or is > there some more concrete reason to require everyone to make this > change? We should not spec an X command in this specification. Everyone can implement the X commands they like in implementation, but to include them in the spec is not consistent with the purpose of having X commands. X commands exist so that implementations can have non-standard extensions. Putting them in the spec makes them part of the standard. My intent with the name change was to initialize the extensions table with some extensions to prime the extensions mechanism. That is why I changed the names, but implementors can choose to implement XPAT, XOVER and so on if they want. Under those names, they are, by definition, NOT standard extensions. > > >XHDR is just a subset of XPAT. There is no need for both. > > Ok. > > >I was thinking that BATCH could be another reference added after the spec > >using the new extension mechanism. > > Sounds fine. > -- 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