[NNTP] LIST EXTENSIONS and an NNTPv2 capability

Ken Murchison ken at oceana.com
Mon Oct 18 15:26:06 PDT 2004


Charles Lindsey wrote:
> In <416FCD30.40906 at oceana.com> Ken Murchison <ken at oceana.com> writes:
> 
> 
>>Clive D.W. Feather wrote:
> 
> 
>>>>The proposed solution is this:  Specify in our base draft that any server
>>>>that fully complies with the new specification advertise the NNTPv2
>>>>capability as part of LIST EXTENSIONS.
>>>
>>>
>>>Right, stop here. I don't like this idea. It's a kludge, and an unstructured
>>>one at that.
> 
> 
>>I disagree that its a kludge, it simply states that the server is 
>>compliant with RFC 977bis.  Any server which does not advertise it, is 
>>at best compliant with RFC 977 and LIST EXTENSIONS may or may not be 
>>accurate (a.k.a. the currently deployed mess).  The beauty is in the 
>>simplicity.  As stated earlier, this approach has worked well for IMAP.
> 
> 
> FWIW, I am with Clive on this one.
> 
> Not that I would necessarily go with his full proposal (perhaps a cut down
> version). It might have been a good thing to consider earlier on, but not
> at this late stage.


Just out of curiosity, are you and Clive saying that a simple NNTPv2
capability does not solve the problem at hand, or that it doesn't take
things far enough?


-- 
Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--    http://www.oceana.com/~ken/ksm.pgp





More information about the ietf-nntp mailing list