From: Charles Lindsey (chl@clw.cs.man.ac.uk)
Date: Wed Apr 03 2002 - 08:43:54 CST
<http://www.landfield.com/usefor/drafts/section_7.06.02>
Principal changes:
You can't have "(Moderated)" in a newsgroups line except at the end to
indicate a moderated group.
I have removed the multipart/alternative from the newgroup example (it
might have been justified in that case, but generally we are supposed to
be discouraging it).
Msg-ids in the header of an Ihave-message are now SHOULD NOT generate,
MAY accept.
Point for discussion regarding the Cancel-message:
Currently it says
NOTE: The former requirement [RFC 1036] that the From and/or
Sender-headers of the cancel message should match those of the
original article has been removed from this standard, since it
only encouraged cancel issuers to conceal their true identity,
and it was not usually checked or enforced by canceling
software. Therefore, both the From and/or Sender-headers and
any Approved-header should now relate to the entity responsible
for issuing the cancel message.
Does anyone want to change that situation in view of anything we might
want to say in the proposed Security extension?
Here are the full diffs:
*** /tmp/dCxaW5D Wed Apr 3 15:20:26 2002
--- landfield/drafts/section_7.06.02 Wed Apr 3 15:19:31 2002
***************
*** 9,11 ****
created, modified or removed, or containing articles to be canceled).
! This is to ensure that the message progagates to all sites which
receive (or would receive) that group(s). It MAY include other
--- 9,11 ----
created, modified or removed, or containing articles to be canceled).
! This is to ensure that the message propagates to all sites which
receive (or would receive) that group(s). It MAY include other
***************
*** 13,15 ****
cause the control message to propagate also to places where it is
! unwanted, or even cause it not to progatate where it should, so it
should not be used without good reason).
--- 13,15 ----
cause the control message to propagate also to places where it is
! unwanted, or even cause it not to propagate where it should, so it
should not be used without good reason).
***************
*** 28,30 ****
Relaying Agents MUST propagate even control messages that they do not
! recognise.
--- 28,30 ----
Relaying Agents MUST propagate even control messages that they do not
! recognize.
***************
*** 67,69 ****
! Newgroup-verb = "newgroup"
Newgroup-arguments = CFWS newsgroup-name [ CFWS newgroup-flag ]
--- 67,70 ----
! control-message =/ Newgroup-message
! Newgroup-message = "newgroup" Newgroup-arguments
Newgroup-arguments = CFWS newsgroup-name [ CFWS newgroup-flag ]
***************
*** 81,83 ****
NOTE: Specifically, some alternative flags such as "y" and "m",
! which are sent and recognised by some current software, are NOT
part of this standard. Moreover, some existing implementations
--- 82,84 ----
NOTE: Specifically, some alternative flags such as "y" and "m",
! which are sent and recognized by some current software, are NOT
part of this standard. Moreover, some existing implementations
***************
*** 85,87 ****
unmoderated newsgroup. Both of these usages are contrary to this
! standard.
--- 86,89 ----
unmoderated newsgroup. Both of these usages are contrary to this
! standard and control messages with such non-standard flags
! should be ignored.
***************
*** 113,114 ****
--- 115,117 ----
+
1. An "application/news-groupinfo" part (7.2.1.2) containing the name
***************
*** 166,168 ****
newsgroup-description
! = 1*( [WSP] utext)
moderation-flag = %x28.4D.6F.64.65.72.61.74.65.64.29
--- 169,171 ----
newsgroup-description
! = utext *( *WSP utext )
moderation-flag = %x28.4D.6F.64.65.72.61.74.65.64.29
***************
*** 169,172 ****
; case sensitive "(Moderated)"
- The whole groupinfo-body is intended to be interpreted as a text
- written in the UTF-8 character set.
--- 172,173 ----
***************
*** 173,174 ****
--- 174,178 ----
+ The newsgroup-description MUST NOT contain any occurrence of the
+ string "(Moderated)" within it. The whole groupinfo-body is intended
+ to be interpreted as a text written in the UTF-8 character set.
***************
*** 176,184 ****
"newgroup" (7.2.1) and "mvgroup" (7.2.3) control messages. The
! newsgroup-name(s) in the newsgroups-line MUST agree with the
! newsgroup-name(s) in the "newgroup" or "mvgroup" control message.
! The Content-Type "application/news-groupinfo" MUST NOT be used except
! as a part of such control messages. Although optional, the
! newsgroups-tag SHOULD be included until such time as this standard
! has been widely adopted, to ensure compatibility with present
! practice.
--- 180,187 ----
"newgroup" (7.2.1) and "mvgroup" (7.2.3) control messages. The
! newsgroup-name in the newsgroups-line MUST agree with the newsgroup-
! name in the "newgroup" or "mvgroup" control message. The Content-
! Type "application/news-groupinfo" MUST NOT be used except as a part
! of such control messages. Although optional, the newsgroups-tag
! SHOULD be included until such time as this standard has been widely
! adopted, to ensure compatibility with present practice.
***************
*** 208,209 ****
--- 211,215 ----
avoid unnecessary conversions.
+ [If, at the time of publication of this standard, [NNTP] is still [RFC
+ 977], that NOTE will need to be changed to indicate that "it is expected
+ that a future extension of [RFC 977] will require ...".]
***************
*** 230,232 ****
The proto-article SHOULD be injected at the serving agent that
! processes the control message AFTER the newsgroup(s) in question has
been created or modified. It MUST NOT be injected if the newsgroup is
--- 236,238 ----
The proto-article SHOULD be injected at the serving agent that
! processes the control message AFTER the newsgroup in question has
been created or modified. It MUST NOT be injected if the newsgroup is
***************
*** 238,244 ****
- NOTE: The "$p=<n>" convention, if applied uniformly, should
- ensure that initial articles relayed beyond the local server in
- contravention of the above prohibition will not propagate in
- competition with similar copies injected at other local servers.
-
NOTE: It is not precluded that the proto-article is itself a
--- 244,245 ----
***************
*** 252,262 ****
! A "newgroup" with bilingual charter and policy information:
! From: "example.all Administrator" <admin@example.invalid>
! Newsgroups: example.admin.groups,example.admin.announce
! Date: 27 Feb 1997 12:50:22 +0200
Subject: cmsg newgroup example.admin.info moderated
! Approved: admin@example.invalid
Control: newgroup example.admin.info moderated
! Message-ID: <ng-example.admin.info-19970227@example.invalid>
Content-Type: multipart/mixed; boundary="nxtprt"
--- 253,264 ----
! A "newgroup" with its charter:
! From: "example.all Administrator" <admin@noc.example>
! Newsgroups: example.admin.info,example.admin.announce
! Date: 27 Feb 2002 12:50:22 +0200
Subject: cmsg newgroup example.admin.info moderated
! Approved: admin@noc.example
Control: newgroup example.admin.info moderated
! Message-ID: <ng-example.admin.info-20020227@noc.example>
! MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="nxtprt"
***************
*** 275,285 ****
Newsgroups: example.admin.info
! From: "example.all Administrator" <admin@example.invalid>
Subject: Charter for example.admin.info
! Message-ID: <ng-example.admin.info-19970227$p=1@example.invalid>
Distribution: local
- Content-Type: multipart/alternative ;
- differences = content-language ;
- boundary = nxtlang
-
- --nxtlang
Content-Type: text/plain; charset=us-ascii
--- 277,282 ----
Newsgroups: example.admin.info
! From: "example.all Administrator" <admin@noc.example>
Subject: Charter for example.admin.info
! Message-ID: <charter-example.admin.info-20020227@noc.example>
Distribution: local
Content-Type: text/plain; charset=us-ascii
***************
*** 286,288 ****
Content-Transfer-Encoding: 7bit
- Content-Language: en
--- 283,284 ----
***************
*** 289,291 ****
The group example.admin.info contains regularly posted
-
information on the example.* hierarchy.
--- 285,286 ----
***************
*** 292,301 ****
- --nxtlang
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- Content-Language: de
-
- Die Gruppe example.admin.info enthaelt regelmaessig versandte
- Informationen ueber die example.*-Hierarchie.
- --nxtlang--
--nxtprt--
--- 287,288 ----
***************
*** 302,303 ****
--- 289,291 ----
+
7.2.2. The 'rmgroup' Control Message
***************
*** 304,306 ****
! Rmgroup-verb = "rmgroup"
Rmgroup-arguments = CFWS newsgroup-name
--- 292,295 ----
! control-message =/ Rmgroup-message
! Rmgroup-message = "rmgroup" Rmgroup-arguments
Rmgroup-arguments = CFWS newsgroup-name
***************
*** 319,326 ****
! From: "example.all Administrator" <admin@example.invalid>
! Newsgroups: example.admin.groups, example.admin.announce
! Date: 4 Jul 1997 22:04 -0900 (PST)
Subject: cmsg rmgroup example.admin.obsolete
! Message-ID: <rm-example.admin.obsolete-19970730@example.invalid>
! Approved: admin@example.invalid
Control: rmgroup example.admin.obsolete
--- 308,315 ----
! From: "example.all Administrator" <admin@noc.example>
! Newsgroups: example.admin.obsolete, example.admin.announce
! Date: 4 Apr 2002 22:04 -0900 (PST)
Subject: cmsg rmgroup example.admin.obsolete
! Message-ID: <rm-example.admin.obsolete-20020404@noc.example>
! Approved: admin@noc.example
Control: rmgroup example.admin.obsolete
***************
*** 332,334 ****
! Mvgroup-verb = "mvgroup"
Mvgroup-arguments = CFWS newsgroup-name CFWS newsgroup-name
--- 321,324 ----
! control-message =/ Mvgroup-message
! Mvgroup-message = "mvgroup" Mvgroup-arguments
Mvgroup-arguments = CFWS newsgroup-name CFWS newsgroup-name
***************
*** 354,359 ****
not exist already) as for a "newgroup" control message, and MUST in
! any case be made moderated if a newgroup-flag "moderated" is present.
! At the same time, arrangements SHOULD be made to remove the old group
! (as with a "rmgroup" control message), but only after a suitable
! overlap period to allow the network to adjust to the new arrangement.
--- 344,350 ----
not exist already) as for a "newgroup" control message, and MUST in
! any case be made moderated if a newgroup-flag "moderated" is present,
! and vice versa. At the same time, arrangements SHOULD be made to
! remove the old group (as with a "rmgroup" control message), but only
! after a suitable overlap period to allow the network to adjust to the
! new arrangement.
***************
*** 378,382 ****
changeover from dragging on indefinitely.
- [We could easily provide an extra parameter for the issuer of the
- mvgroup message to suggest how many days the overlap should be. Does
- anybody want to pursue that possibility?]
--- 369,370 ----
***************
*** 409,411 ****
! On the other hand, it is recognised that this feature would
likely not be implementable if the new group was already in
--- 397,399 ----
! On the other hand, it is recognized that this feature would
likely not be implementable if the new group was already in
***************
*** 417,418 ****
--- 405,407 ----
+
7.2.3.1. Example
***************
*** 419,427 ****
! From: "example.all Administrator" <admin@example.invalid>
! Newsgroups: example.admin.groups, example.admin.announce
! Date: 30 Jul 1997 22:04 -0500 (EST)
Subject: cmsg mvgroup example.oldgroup example.newgroup moderated
! Message-ID: <mvgroup-example.oldgroup-19970730@example.invalid>
! Approved: admin@example.invalid
Control: mvgroup example.oldgroup example.newgroup moderated
Content-Type: multipart/mixed; boundary=nxt
--- 408,417 ----
! From: "example.all Administrator" <admin@noc.example>
! Newsgroups: example.oldgroup,example.newgroup,example.admin.announce
! Date: 30 Apr 2002 22:04 -0500 (EST)
Subject: cmsg mvgroup example.oldgroup example.newgroup moderated
! Message-ID: <mvgroup-example.oldgroup-20020430@noc.example>
! Approved: admin@noc.example
Control: mvgroup example.oldgroup example.newgroup moderated
+ MIME-Version: 1.0
Content-Type: multipart/mixed; boundary=nxt
***************
*** 437,441 ****
The moderated group example.oldgroup is replaced by
! example.newgroup. Please update your configuration, and please
! arrange to file articles arriving for example.oldgroup as if
! they were in example.newgroup.
--nxt--
--- 427,432 ----
The moderated group example.oldgroup is replaced by
! example.newgroup. Please update your configuration, and please,
! if possible, arrange to file articles arriving for
! example.oldgroup as if they were in example.newgroup.
!
--nxt--
***************
*** 447,449 ****
! Checkgroup-verb = "checkgroups"
Checkgroup-arguments= [ chkscope ] [ chksernr ]
--- 438,441 ----
! control-message =/ Checkgroup-message
! Checkgroup-message = "checkgroups" Checkgroup-arguments
Checkgroup-arguments= [ chkscope ] [ chksernr ]
***************
*** 483,485 ****
! NOTE: The checkgroups nessage is intended to synchronize the
list of newsgroups stored by a serving agent, and their
--- 475,477 ----
! NOTE: The checkgroups message is intended to synchronize the
list of newsgroups stored by a serving agent, and their
***************
*** 520,523 ****
-
-
NOTE: The possibility of removing a complete hierarchy by means
--- 512,513 ----
***************
*** 530,531 ****
--- 520,523 ----
+
+
7.3. Cancel
***************
*** 545,547 ****
specifically, the entity identified by the path-identity in front
! of the leftmost '%' delimeter in the Path-header (5.6) or in the
Injector-Info-header (6.19) and, where appropriate, the moderator
--- 537,539 ----
specifically, the entity identified by the path-identity in front
! of the leftmost '%' delimiter in the Path-header (5.6) or in the
Injector-Info-header (6.19) and, where appropriate, the moderator
***************
*** 561,563 ****
! Cancel-verb = "cancel"
Cancel-arguments = CFWS msg-id
--- 553,556 ----
! control-message =/ Cancel-message
! Cancel-message = "cancel" Cancel-arguments
Cancel-arguments = CFWS msg-id
***************
*** 591,594 ****
for issuing the cancel message.
- [Do we want to review that now in the light of what the Security
- Extension may contain?]
--- 584,585 ----
***************
*** 598,600 ****
predecessor of the NNTP [NNTP] protocol. They are largely obsolete on
! the Internet, but still see use in conjunction with some transort
protocols such as UUCP, especially for backup feeds that normally are
--- 589,591 ----
predecessor of the NNTP [NNTP] protocol. They are largely obsolete on
! the Internet, but still see use in conjunction with some transport
protocols such as UUCP, especially for backup feeds that normally are
***************
*** 609,613 ****
! Ihave-verb = "ihave"
! Ihave-arguments = *( msg-id SP ) relayer-name
! Sendme-verb = "sendme"
Sendme-arguments = Ihave-arguments
--- 600,606 ----
! control-message =/ Ihave-message
! Ihave-message = "ihave" Ihave-arguments
! Ihave-arguments = relayer-name
! control-message =/ Sendme-message
! Sendme-message = "sendme" Sendme-arguments
Sendme-arguments = Ihave-arguments
***************
*** 617,621 ****
! Msg-ids MUST appear in either the arguments or the body, but NOT
! both. Relayers SHOULD generate the form putting msg-ids in the body,
! but the other form MUST be supported for backward compatibility.
--- 610,617 ----
! The body of the message consists of a list of msg-ids, one per line.
! [RFC 1036] also permitted the list of msg-ids to appear in the Ihave-
! or Sendme-arguments with the syntax
! Ihave-arguments = *( msg-id FWS ) [relayer-name]
! but this form SHOULD NOT now be used, though relaying agents MAY
! recognize and process it for backward compatibility.
***************
*** 629,642 ****
point messages, by using newsgroup-names in the Newsgroups-header of
! the form "to." followed by one of more components in the form of a
! relayer-name (see section 5.5.1 which forbids "to" as the first
! component of a newsgroup-name). The control message SHOULD then be
! delivered ONLY to the relaying agent(s) identitifed by that relayer-
! name, and any relaying agent receiving such a message which includes
! its own relayer-name MUST NOT propagate it further. Each pair of
! relaying agent(s) sending and receiving these messages MUST be
! immediate neighbors, exchanging news directly with each other. Each
! relaying agent advertises its new arrivals to the other using ihave
! messages, and each uses sendme messages to request the articles it
! lacks.
To reduce overhead, ihave and sendme messages SHOULD be sent
--- 625,639 ----
point messages, by using newsgroup-names in the Newsgroups-header of
! the form "to." followed by one (or possibly more) components in the
! form of a relayer-name (see section 5.5.1 which forbids "to" as the
! first component of a newsgroup-name). The control message SHOULD then
! be delivered ONLY to the relaying agent(s) identified by that
! relayer-name, and any relaying agent receiving such a message which
! includes its own relayer-name MUST NOT propagate it further. Each
! pair of relaying agent(s) sending and receiving these messages MUST
! be immediate neighbors, exchanging news directly with each other.
! Each relaying agent advertises its new arrivals to the other using
! ihave messages, and each uses sendme messages to request the articles
! it lacks.
+
To reduce overhead, ihave and sendme messages SHOULD be sent
***************
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