INN commit: trunk (5 files)

Sat May 16 12:27:52 UTC 2009

Date: Saturday, May 16, 2009 @ 05:27:51
  Author: iulius
Revision: 8467

Update references of RFC 977 and RFC 1036 to new RFC 3977,
4642, 4643, 4644, 5536 and 5537 when it applies.

Modified:
  trunk/TODO
  trunk/doc/FAQ
  trunk/doc/pod/readme.pod
  trunk/include/inn/nntp.h
  trunk/include/nntp.h

--------------------+
 TODO               |    4 ++--
 doc/FAQ            |   10 ++++++----
 doc/pod/readme.pod |    8 +++++---
 include/inn/nntp.h |   42 ++++++++++++++++++++++--------------------
 include/nntp.h     |   19 +------------------
 5 files changed, 36 insertions(+), 47 deletions(-)

Modified: TODO
===================================================================

--- TODO	2009-05-16 12:19:06 UTC (rev 8466)
+++ TODO	2009-05-16 12:27:51 UTC (rev 8467)
@@ -206,8 +206,8 @@
 * Add documentation for slave servers.  [Russ has articles from
   inn-workers that can be used as a beginning.]
 
-* Write complete documentation for all of our extensions to RFC 977 or RFC
-  1036, preferrably in a format that could be suitable for future
+* Write complete documentation for all of our extensions to RFC 3977 or RFC
+  5536 and 5537, preferrably in a format that could be suitable for future
   inclusion into new revisions of the RFCs.
 
 * Audit readers.conf.5 against perm.c for missing options ("include" at

Modified: doc/FAQ
===================================================================
--- doc/FAQ	2009-05-16 12:19:06 UTC (rev 8466)
+++ doc/FAQ	2009-05-16 12:27:51 UTC (rev 8467)
@@ -109,9 +109,11 @@
 The README that comes with INN has this to say (in part):
 
     INN (InterNetNews), originally written by Rich Salz, is an extremely
-    flexible and configurable Usenet / netnews news server.  For a
-    complete description of the protocols behind Usenet and netnews, see
-    RFC 1036 and RFC 977 (or their replacements).  In brief, netnews is a
+    flexible and configurable Usenet / Netnews news server.  For a
+    complete description of the protocols behind Usenet and Netnews, see
+    RFC 3977 (NNTP), RFC 4642 (TLS/NNTP), RFC 4643 (NNTP authentication),
+    RFC 4644 (streaming NNTP feeds), RFC 5536 (USEFOR) and RFC 5537
+    (USEPRO) or their replacements.  In brief, Netnews is a
     set of protocols for exchanging messages between a decentralized
     network of news servers.  News articles are organized into newsgroups,
     which are themselves organized into hierarchies.  Each individual news
@@ -126,7 +128,7 @@
     volunteers around the world.
 
 For a more complete answer, see that file.  A full description of what
-Usenet and netnews are is beyond the scope of this document; for a
+Usenet and Netnews are is beyond the scope of this document; for a
 beginner's introduction, see the news.newusers.questions home page at
 <http://www.anta.net/misc/nnq/>.
 

Modified: doc/pod/readme.pod
===================================================================
--- doc/pod/readme.pod	2009-05-16 12:19:06 UTC (rev 8466)
+++ doc/pod/readme.pod	2009-05-16 12:27:51 UTC (rev 8467)
@@ -13,9 +13,11 @@
 =head1 What is INN?
 
 INN (InterNetNews), originally written by Rich Salz, is an extremely
-flexible and configurable Usenet / netnews news server.  For a complete
-description of the protocols behind Usenet and netnews, see S<RFC 1036> and
-S<RFC 977> (or their replacements).  In brief, netnews is a set of protocols
+flexible and configurable Usenet / Netnews news server.  For a complete
+description of the protocols behind Usenet and Netnews, see S<RFC 3977>
+(NNTP), S<RFC 4642> (TLS/NNTP), S<RFC 4643> (NNTP authentication),
+S<RFC 4644> (streaming NNTP feeds), S<RFC 5536> (USEFOR) and S<RFC 5537>
+(USEPRO) or their replacements.  In brief, Netnews is a set of protocols
 for exchanging messages between a decentralized network of news servers.
 News articles are organized into newsgroups, which are themselves
 organized into hierarchies.  Each individual news server stores locally

Modified: include/inn/nntp.h
===================================================================
--- include/inn/nntp.h	2009-05-16 12:19:06 UTC (rev 8466)
+++ include/inn/nntp.h	2009-05-16 12:27:51 UTC (rev 8467)
@@ -131,31 +131,33 @@
 };
 
 
-/*     Command lines MUST NOT exceed 512 octets, which includes the
-       terminating  CRLF pair.  The arguments MUST NOT exceed 497
-       octets.  A server MAY relax these limits for commands defined
-       in an extension.
+/*
+**  Command lines MUST NOT exceed 512 octets, which includes the
+**  terminating  CRLF pair.  The arguments MUST NOT exceed 497
+**  octets.  A server MAY relax these limits for commands defined
+**  in an extension.
+**
+**  Also see below for an additional restriction on message-IDs.
+*/
 
-   Also see below for an additional restriction on message IDs. */
-
 #define NNTP_MAXLEN_COMMAND     512
 #define NNTP_MAXLEN_ARG         497
 
-/* Consensus on the USEFOR mailing list in June of 2000 indicates that the
-   next revision of the Usenet article standard will limit the length of the
-   message ID to 250 characters.  This is also the limit recommended by
-   son-of-1036.
+/*
+**  The length of a message-ID is limited to 250 characters by RFC 3977
+**  and RFC 5536 (USEFOR).
+**
+**  You can increase this limit if you want, but don't increase it above 497.
+**  RFC 3977 limits each line of the NNTP protocol to 512 octets, including
+**  the terminating CRLF.  For a message-ID to be passed using the TAKETHIS
+**  command, it can therefore be a maximum of 501 octets but 497 is the
+**  maximum length of an argument.
+**
+**  Both Cyclone and DNews are known to reject message-IDs longer than 500
+**  octets as of June of 2000.  DNews has been reported to have problems with
+**  message-IDs of 494 octets.
+*/
 
-   You can increase this limit if you want, but don't increase it above 497.
-   RFC 977 limits each line of the NNTP protocol to 512 octets, including
-   the terminating CRLF.  For a message ID to be passed using the TAKETHIS
-   command, it can therefore be a maximum of 501 octets.  The November 1999
-   draft of the replacement RFC limits it to 497 octets.
-
-   Both Cyclone and DNews are known to reject message IDs longer than 500
-   octets as of June of 2000.  DNews has been reported to have problems with
-   message IDs of 494 octets. */
-
 #define NNTP_MAXLEN_MSGID       250
 
 /* Forward declaration. */

Modified: include/nntp.h
===================================================================
--- include/nntp.h	2009-05-16 12:19:06 UTC (rev 8466)
+++ include/nntp.h	2009-05-16 12:27:51 UTC (rev 8467)
@@ -1,6 +1,6 @@
 /*  $Id$
 **
-**  Here be a set of NNTP response codes as defined in RFC977 and elsewhere.
+**  Here be a set of NNTP response codes as defined in RFC3977 and elsewhere.
 **  The reponse codes are three digits, RFI, defined like this:
 **	R, Response:
 **		1xx	Informative message
@@ -93,20 +93,3 @@
 #define NNTP_XBATCH_BADSIZE	"501 Invalid or missing size for xbatch"
 
 #define NNTP_STRLEN			512
-
-/* Consensus on the USEFOR mailing list in June of 2000 indicates that the
-   next revision of the Usenet article standard will limit the length of the
-   message ID to 250 characters.  This is also the limit recommended by
-   son-of-1036.
-
-   You can increase this limit if you want, but don't increase it above 497.
-   RFC 977 limits each line of the NNTP protocol to 512 octets, including
-   the terminating CRLF.  For a message ID to be passed using the TAKETHIS
-   command, it can therefore be a maximum of 501 octets.  The November 1999
-   draft of the replacement RFC limits it to 497 octets.
-
-   Both Cyclone and DNews are known to reject message IDs longer than 500
-   octets as of June of 2000.  DNews has been reported to have problems with
-   message IDs of 494 octets. */
-
-#define NNTP_MSGID_MAXLEN       250


