ietf-nntp "Common NNTP Extensions" document updated

[Stan Barber]

> Stan Barber wrote:
> > The new draft is at this URL:
> >         ftp://ftp.academ.com/pub/nntp/ietf/nntp-common-practices.txt
> 
> Comments since I won't be at the meeting:
> 
> Under the 'implementation issues' section, you should definitely add a
> section describing the disabling of the NEWNEWS command on many of the
> current news systems.  On most systems, the NEWNEWS command imposes
> serious performance penalties, and running just a few NEWNEWS commands
> can easily bring a carefully-tuned system to its knees.
> 
> NEWNEWS is disabled by default in INN 1.5.1 and later, and perhaps
> earlier versions as well.  It may be disabled in INN 1.4, but I couldn't
> find it on FTP sites to verify my guess.  :)  Since NEWNEWS is disabled
> on many of the Internet's client reader systems, the RFC should mention
> that this command cannot be counted on to be present.
> 
> I'm not sure if HighWind's Typhoon supports NEWNEWS or not.
> 
> Can NEWNEWS be considered deprecated?  There are far better ways of
> determining the availability of new news within the current RFC 977
> protocol, not to mention the command NNTP extensions XHDR (to retrieve
> just the msg ids) or XOVER.

Let's see what others think about this? I will add it to the issues list.

> 
> 
> Regarding the nntp reference implementation:
> 
> Can you package it such that the tarball is extracted into its own
> "nntp.1.5.12.2" directory.  Doing so will make it more admin-friendly.

Issues about the reference implementation package should be sent to the
nntp at academ.com, ietf-nntp at academ.com.


-- 
Stan   | Academ Consulting Services        |internet: sob at 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.