[NNTP] [2505] CAPABILITIES indication of features not currently available

Ken Murchison ken at oceana.com
Fri Dec 3 08:44:33 PST 2004


Russ Allbery wrote:

> Clive D W Feather <clive at demon.net> writes:
> 
>>Russ Allbery said:
> 
> 
>>>It's not implementation complexity that I'm worrying about so much as
>>>complexity of the standard itself.  It's not that the software has to
>>>understand all of that; it's that an implementor has to read it all and
>>>understand it and figure out when to use it and how to use it properly.
> 
> 
>>That is something I can cure by writing it better. Let me have another go
>>and see what you think then.
> 
> 
> I'll certainly take a look, but really, I don't think it's a matter of
> wording; regardless of how it's worded, it adds syntactic complexity to
> the CAPABILITIES command.  Not a lot, admittedly, but I'm also not seeing
> a lot of benefit for the way that I expect most clients to work.

I propose that we put this issue to rest for the current document.  We 
have bigger fish to fry.  The WG can revisit it down the road if deemed 
necessary.

Can we can an official ruling from the chair?  ;)

-- 
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