From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Fri Jul 19 2002 - 13:30:52 CDT
In <GyzqEL.87y@clw.cs.man.ac.uk> "Charles Lindsey" <chl@clw.cs.man.ac.uk> writes:
>Well nobody has commented upon my text so far, so it is time to move on to
>the consequentials.
>First, the easy bit in 8.8.1. I had already posted changes there necessary
>for our new treatment of RFC 2047, UTF-8 and "non-UTF-8", so it is just
>necessary to fix the paragraph concerning the Newsgroups-header during
>gatewaying.
And then
>The next bit, in the Duties of an Injecting Agent are possibly more
>contentious. Here are the old text, followed by what I now propose:
And nobody commented on that except Clive, who had a small niggle, to
which I responded (and I await his response, if any, to that).
>[There are further consequential changes in the Duties of moderators and
>in the usage of application/news-transmission, but I think we need to
>establish (or not) the policy implied by my wording above before
>proceeding further.]
So time to proceed again:
In duties of Injecting Agents:
4. It MUST reject any article that does not have the correct
mandatory headers for a proto-article (5 and 8.2.1) present, or
which contains any header that does not have legal contents, and
it SHOULD reject any article which contains any header
deprecated for Netnews (4.2.1).
which becomes:
4. It MUST reject any article that does not have the correct
mandatory headers for a proto-article (5 and 8.2.1) present, or
which contains any header that does not have legal contents, and
it SHOULD reject any article which contains any header
deprecated for Netnews (4.2.1). In particular, it MUST reject
any article whose Newsgroups-header or Followup-To-header
contains an encoded newsgroup-name (5.5.2) although it MAY
instead decode those newsgroup-names and continue (this being a
useful service for moderators using that injecting agent, see
8.7).
Does anyone want to upgrade that MAY to a SHOULD?
In Duties of a Moderator:
5. Otherwise, he causes the article to be injected, having first
observed all the duties of a posting agent (8.5).
which becomes:
5. Otherwise, he causes the article to be injected, having first
decoded any encoded newgroup-name (5.5.2), unless his injecting
offers that service (8.2.2), and having observed all the duties
of a posting agent (8.5).
and also:
It should be the case that articles will be received by the moderator
encapsulated as an object of Content-Type application/news-
transmission (8.2.2), or possibly encapsulated but without an
explicit Content-Type-header. In such a case, the complete article is
immediately available for processing by the moderator.
However, prior to the introduction of this standard, it was more
common for injecting agents to transform proto-articles into email
messages, mixing the Netnews headers with the Email headers.
Moderators SHOULD therefore be prepared to accept submission in this
format, although they need then to be aware of the Duties of an
Incoming Gateway (8.8.2) (and, in particular, they SHOULD adopt the
Message-ID- and Date-headers of the email message, though they SHOULD
NOT add any Sender-header).
which becomes:
Articles will be received by the moderator either encapsulated as an
object of Content-Type application/news-transmission (8.2.2) (or
possibly encapsulated but without an explicit Content-Type-header),
or else directly as an email already containing all the headers
appropriate for a Netnews article (see 8.2.2) in which case he
needs to be aware of the Duties of an Incoming Gateway (8.8.2) (and,
in particular, he SHOULD adopt the Message-ID- and Date-headers of
the email message, though he SHOULD NOT add any Sender-header).
Moderators SHOULD be prepared to accept articles in either format.
And finally, in the description of Application/news-transmission:
The Content-Type "application/news-transmission" is intended for the
encapsulation of complete news articles where the intention is that
the recipient should then inject them into Netnews. This Application
type SHOULD be used when mailing articles to moderators and to
email-to-news gateways (see 8.2.2).
which becomes:
The Content-Type "application/news-transmission" is intended for the
encapsulation of complete news articles where the intention is that
the recipient should then inject them into Netnews. This Application
type provides one of the methods for mailing articles to moderators
(see 8.2.2) and it is also the preferred method when sending to an
email-to-news gateway (see 8.8.1).
I think that now completes all the changes arising from our recent
discussions on moderation and charsets in headers. If people are happy
with these wordings, then I think we are due for another complete draft,
and I would also summarize what we have done on the moderators' list.
-- Charles H. Lindsey ---------At Home, doing my own thing------------------------ Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl Email: chl@clw.cs.man.ac.uk Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K. PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5