ietf-nntp "Common NNTP Extensions" document updated
Tom Hughes
tom at compton.demon.co.uk
Mon Dec 1 09:32:36 PST 1997
In message <199712011648.LAA26314 at mail.cis.ohio-state.edu>
Dave Barr <barr at cis.ohio-state.edu> wrote:
> In message <19971201162803.00397 at oaktree.co.uk>, Jon Ribbens writes:
>
> > I really can't see how anyone can seriously propose that parts of such
> > a protocol can be removed with no warning. How on earth are people
> > supposed to write RFC-compliant software if tomorrow someone might
> > suddenly change the RFC so that their software is no longer compliant?
>
> That's how standards work.
No it isn't. It's normal to deprecate something for at least one
revision of the standard before you actually remove it.
Tom
--
Tom Hughes (tom at compton.demon.co.uk)
http://www.compton.demon.co.uk/
...There are two ways to write error-free programs. Only the third one works.
More information about the ietf-nntp
mailing list