From: Charles Lindsey (chl@clerew.man.ac.uk)
Date: Sat Jun 07 2003 - 16:26:46 CDT
This turned out to be rather simple.
See http://www.landfield.com/usefor/drafts/useage_8.-1.00
http://www.landfield.com/usefor/drafts/section_8.10.01
As before, the diffs for USEFOR follow, and the full USEAGE text is
attached (not that there is much of it - note that there were no changes
at all in the gatewaying section).
I have looked through section 9 (Security issues etc), and I find nothing
that needs splitting. So this completes the first pass of the split.
Hopefully, we can now agree the few outstanding issues re the splitting,
and then we can publish a full USEFOR draft and move on to the next
stage.
Here are the diffs:
*** /tmp/dtiaiJr Sat Jun 7 22:01:19 2003
--- landfield/drafts/section_8.10.01 Sat Jun 7 22:00:27 2003
***************
*** 47,64 ****
into the relaying system for access by readers.
As such, an injecting agent is considered responsible for ensuring
! that any article it injects conforms with the rules of this standard
! and the policies of any newsgroups or hierarchies that the article is
! posted to. It is also expected to bear some responsibility towards
! the rest of the network for the behaviour of its posters (and
! provision is therefore made for it to be easily contactable by
! email).
- To this end injecting agents MAY cancel articles which they have
- previously injected (see 7.3).
8.2.1. Proto-articles
A proto-article is one that has been created by a posting agent and
--- 47,61 ----
into the relaying system for access by readers.
As such, an injecting agent is considered responsible for ensuring
! that any article it injects conforms with the rules of this standard.
! It is also expected to bear some responsibility towards the rest of
! the network for the behaviour of its posters (and provision is
! therefore made for it to be easily contactable by email).
8.2.1. Proto-articles
A proto-article is one that has been created by a posting agent and
***************
*** 142,155 ****
the specific exception of "tracing" headers such as Injector-Info
and Complaints-To, which are to be removed as already mentioned.
- NOTE: The addition of non-mandatory headers by the injecting
- agent may alter the posting agent's preferred presentation of
- information. In particular, adding a Sender-header that exposes
- a sender's mailbox has privacy implications; where the main or
- only purpose for doing so is as tracing information, it is
- preferable to use instead one of the options provided for the
- Injector-Info header (6.19.1).
-
11.If the Newsgroups-header contains no moderated groups, or if it
contains an Approved-header, the injecting agent forwards the
article to one or more relaying or serving agents.
--- 137,142 ----
***************
*** 294,300 ****
6. It MUST reject any article without an Approved-header posted to
any moderated newsgroup which it is configured to receive, and it
! MAY reject such articles for any newsgroup it knows be moderated.
7. It MUST remove any Xref-header (6.16) from each article. It then
MAY (and usually will) generate a fresh Xref-header.
--- 277,284 ----
6. It MUST reject any article without an Approved-header posted to
any moderated newsgroup which it is configured to receive, and it
! MAY reject such articles for any newsgroup it knows to be
! moderated.
7. It MUST remove any Xref-header (6.16) from each article. It then
MAY (and usually will) generate a fresh Xref-header.
***************
*** 321,328 ****
Followup agents MUST create valid followups, in particular by
providing correctly adjusted forms of those headers described as
inheritable (4.2.5.2), notably the Newsgroups-header (5.5), the
! Subject-header (5.4) and the References-header (6.10), and they Ought
! to observe appropriate quoting conventions in the body (see 4.3.2).
Followup agents SHOULD initialize the Newsgroups-header from the
precursor's Followup-To-header, if present, when preparing a
--- 308,314 ----
Followup agents MUST create valid followups, in particular by
providing correctly adjusted forms of those headers described as
inheritable (4.2.5.2), notably the Newsgroups-header (5.5), the
! Subject-header (5.4) and the References-header (6.10).
Followup agents SHOULD initialize the Newsgroups-header from the
precursor's Followup-To-header, if present, when preparing a
***************
*** 335,340 ****
--- 321,329 ----
explicitly requested by means of a Mail-Copies-To-header (6.8), but
they SHOULD include a Posted-And-Mailed-header (6.9) whenever a copy
is so emailed.
+ [It will probably be better to move the rules regarding "Re: " from the
+ Subject header, and the detailed actions to be taken for a Mail-Copies-
+ To-header to here in a future draft.]
8.7. Duties of a Moderator
***************
*** 357,375 ****
manually, or else partially or wholly with the aid of appropriate
software for whose operation he is then responsible. If the
article is a cancel nessage (7.3) issued by the poster of an
! earlier article, then he Ought to cancel it (in which case there
! is no more to be done). He MAY modify the article if that is in
! accordance with the applicable moderation policy (and in
! particular he MAY remove redundant headers and add Comments and
! other informational headers). He also needs to be aware if any
! change he makes to the article will invalidate some authentication
! check provided by the poster or by an earlier moderator.
! He MAY inform the poster if the article is accepted, and he Ought
! to inform the poster if it is rejected. If it is rejected, then
! it normally fails for all the newsgroups for which it was
! intended. If it is accepted, the moderator proceeds with the
! following steps.
2. If the Newsgroups-header contains further moderated newsgroups for
which approval has not already been given, he adds an indication
--- 346,363 ----
manually, or else partially or wholly with the aid of appropriate
software for whose operation he is then responsible. If the
article is a cancel nessage (7.3) issued by the poster of an
! earlier article, then he is expected to cancel that earlier
! article (in which case there is no more to be done). He MAY
! modify the article if that is in accordance with the applicable
! moderation policy (and in particular he MAY remove redundant
! headers and add Comments and other informational headers). He
! also needs to be aware if any change he makes to the article will
! invalidate some authentication check provided by the poster or by
! an earlier moderator.
! If the article is rejected, then it normally fails for all the
! newsgroups for which it was intended. If it is accepted, the
! moderator proceeds with the following steps.
2. If the Newsgroups-header contains further moderated newsgroups for
which approval has not already been given, he adds an indication
***************
*** 405,418 ****
that the article was acceptable to the moderators of all the
moderated groups involved.
! 4. A moderator Ought Not (absent any established and widely
! promulgated policy to the contrary) to remove any newsgroup-name
! from the Newsgroups-header, nor split an article into two versions
! with disjoint Newsgroups-headers. These are matters more usually
! within the prerogative of the poster; moreover splitting can lead
! to fragmentation of threads.
!
! 5. The Date-header SHOULD be retained, except that if it is stale
(5.1) for reasons understood by the moderator (e.g. delays in the
moderation process) he MAY substitute the current date (but must
then take responsibility for any loops that ensue). The Message-
--- 393,399 ----
that the article was acceptable to the moderators of all the
moderated groups involved.
! 4. The Date-header SHOULD be retained, except that if it is stale
(5.1) for reasons understood by the moderator (e.g. delays in the
moderation process) he MAY substitute the current date (but must
then take responsibility for any loops that ensue). The Message-
***************
*** 424,435 ****
2822], may reasonably be supposed to be conformant (and will, in
any case, be caught by the injecting agent if it is not).
! 6. Any variant headers (4.2.5.3) MUST be removed, except that a
Path-header MAY be truncated to only its pre-injection region
(5.6.3). Any Injector-Info-header (6.19) or Complaints-To-header
(6.20) MUST be removed.
! 7. He then causes the article to be injected, having first observed
all the duties of a posting agent.
NOTE: This standard does not prescribe how the moderator or
--- 405,416 ----
2822], may reasonably be supposed to be conformant (and will, in
any case, be caught by the injecting agent if it is not).
! 5. Any variant headers (4.2.5.3) MUST be removed, except that a
Path-header MAY be truncated to only its pre-injection region
(5.6.3). Any Injector-Info-header (6.19) or Complaints-To-header
(6.20) MUST be removed.
! 6. He then causes the article to be injected, having first observed
all the duties of a posting agent.
NOTE: This standard does not prescribe how the moderator or
***************
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@clerew.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
8. Duties of Various Agents
8.1. General principles to be followed
8.2. Duties of an Injecting Agent
An injecting agent MAY take account of the policies of any newsgroups
or hierarchies that the article is posted to.
As part of their responsibility for the actions of their posters,
injecting agents MAY cancel articles which they have previously
injected (see 7.3).
[That paragraph will move back to USEFOR if the rules governing who may
issue cancels are moved back.]
8.2.1. Proto-articles
8.2.2. Procedure to be followed by Injecting Agents
An injecting agent MAY add other headers not already provided by the
poster, but SHOULD NOT alter, delete, or reorder any existing header.
However, the addition of non-mandatory headers by the injecting agent
may alter the posting agent's preferred presentation of information.
In particular, adding a Sender-header that exposes a sender's mailbox
has privacy implications; where the main or only purpose for doing so
is as tracing information, it is preferable to use instead one of the
options provided for the Injector-Info header.
8.3. Duties of a Relaying Agent
8.4. Duties of a Serving Agent
8.5. Duties of a Posting Agent
8.6. Duties of a Followup Agent
Followup agents Ought to observe appropriate quoting conventions in
the body (see 4.3.2).
8.7. Duties of a Moderator
A moderator MAY inform the poster if the article is accepted, and he
Ought to inform the poster if it is rejected.
A moderator Ought Not (absent any established and widely promulgated
policy to the contrary) to remove any newsgroup-name from the
Newsgroups-header, nor split an article into two versions with
disjoint Newsgroups-headers. These are matters more usually within
the prerogative of the poster; moreover splitting can lead to
fragmentation of threads.
8.8. Duties of a Gateway
8.8.1. Duties of an Outgoing Gateway
8.8.2. Duties of an Incoming Gateway
8.8.3. Example