Re: Early comments for merged document RFC 977 plus extensions draft
USENET news manager <newsmaster@ucs.cam.ac.uk> Sun, 07 July 1996 15:11 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa08225;
7 Jul 96 11:11 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa08221;
7 Jul 96 11:11 EDT
Received: from PHEASANT.ACADEM.COM by CNRI.Reston.VA.US id aa08278;
7 Jul 96 11:11 EDT
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by
pheasant.academ.com (8.7.5/8.6.9) with ESMTP id KAA31788 for
<ietf-nntp@PHEASANT.ACADEM.COM>; Sun, 7 Jul 1996 10:11:05 -0500
Received: from lyra.csx.cam.ac.uk (news@lyra.csx.cam.ac.uk [131.111.8.36]) by
academ.com (8.7.5/8.7.1) with SMTP id KAA02980 for <ietf-nntp@academ.com>;
Sun, 7 Jul 1996 10:09:34 -0500 (CDT)
Received: by lyra.csx.cam.ac.uk (SMI-8.6/MDTG-V1.1.6@lyra.csx.cam.ac.uk)
id QAA22592; Sun, 7 Jul 1996 16:09:31 +0100
Message-Id: <199607071509.QAA22592@lyra.csx.cam.ac.uk>
Subject: Re: Early comments for merged document RFC 977 plus extensions draft
To: ietf-nntp@academ.com
Date: Sun, 7 Jul 1996 16:09:29 +0100 (BST)
In-Reply-To: <199606282107.RAA14500@alcor.concordia.ca> from "Anne Bennett" at
Jun 28, 96 05:07:47 pm
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: USENET news manager <newsmaster@ucs.cam.ac.uk>
X-Mailer: ELM [version 2.4 PL22]
Content-Type: text
Anne Bennett wrote:
>Comments on RFC 977:
>...
>| 3.7.1. NEWGROUPS
>|
>| NEWGROUPS date time [GMT] [<distributions>]
>[...]
>| The optional parameter "distributions" is a list of distribution
>| groups, enclosed in angle brackets. If specified, the distribution
>| portion of a new newsgroup (e.g, 'net' in 'net.wombat') will be
>| examined for a match with the distribution categories listed, and
>| only those new newsgroups which match will be listed. If more than
>| one distribution group is to be listed, they must be separated by
>| commas within the angle brackets.
>
>This use of the word "distributions", where really "hierarchy" is
>meant, has led to many misunderstandings and flame wars later. Or
>perhaps it would be more fair to say that subsequent changes in usage
>were at fault -- I wasn't around NNTP ten years ago, so I should not
>venture an opinion as to the origin of the problem.
>
>However, the fact remains that "distributions" now refers to the
>content of the "Distributions:" field -- and indeed you use it that
>way in your draft, as I recall -- so I think it would be wise to use
>another word in the text above.
>
>The same can be said under the description of NEWNEWS.
The comment about NEWNEWS left me puzzled, since it contradicted my
recollection of what NEWNEWS actually does in INN.
Further investigation confirmed that both INN 1.4 and NNTP 1.5.11t5 treat
the "distributions" field of NEWNEWS as items to match against Distribution:
header values, *not* as hierarchy names (whereas for NEWGROUPS they are
indeed treated as hierarchy names). The handling of NEWNEWS distributions in
INN appears to have been broken (i.e. wouldn't work properly, though it was
trying to match Distribution:) prior to INN 1.4unoff3, though.
It appears, then, that the predominant news transports disagree with RFC 977!
Incidentally, the draft mentions both Distribution: and Distributions: as
article headers.
John Line
--
Cambridge University Computing Service - USENET news manager. Usually John Line
newsmaster@ucs.cam.ac.uk (alias {newsmaster,news,usenet}@news.cam.ac.uk)
- Early comments for merged document RFC 977 plus e… Anne Bennett
- Re: Early comments for merged document RFC 977 pl… USENET news manager
- Re: Early comments for merged document RFC 977 pl… Stan Barber