usefor-usefor-01 September 2004
[< Prev]
[TOC] [ Next >]
3.2.5 Supersedes
The Supersedes header contains a message identifier specifying an
article to be superseded upon the arrival of this one. The specified
article MUST be treated as though a "cancel" [USEPRO] control message
had arrived for the article (but observe that a site MAY choose not
to honor a "cancel" message, especially if its authenticity is in
doubt).
supersedes = "Supersedes:" SP [CFWS] msg-id-core [CFWS] CRLF
NOTE: There is no "c" in Supersedes.
[< Prev]
[TOC] [ Next >]
#Diff to first older
--- ../usefor-article-13/Supersedes.out May 2004
+++ ../usefor-usefor-01/Supersedes.out September 2004
@@ -1,34 +1,13 @@
-6.15. Supersedes
+3.2.5 Supersedes
- The Supersedes-header contains a message identifier specifying an
+ The Supersedes header contains a message identifier specifying an
article to be superseded upon the arrival of this one. The specified
- article MUST be treated as though a "cancel" control message had
- arrived for the article (but observe that a site MAY choose not to
- honour a "cancel" message, especially if its authenticity is in
- doubt). The content syntax makes use of syntax defined in [RFC 2822]
- (but see the revised definition of msg-id in section 2.4.3).
+ article MUST be treated as though a "cancel" [USEPRO] control message
+ had arrived for the article (but observe that a site MAY choose not
+ to honor a "cancel" message, especially if its authenticity is in
+ doubt).
- header =/ Supersedes-header
- Supersedes-header = "Supersedes" ":" SP Supersedes-content
- Supersedes-content = [CFWS] msg-id [CFWS]
+ supersedes = "Supersedes:" SP [CFWS] msg-id-core [CFWS] CRLF
- NOTE: There is no "c" in "Supersedes".
-
- NOTE: The Supersedes-header defined here has no connection with
- the Supersedes-header that sometimes appears in Email messages
- converted from X.400 according to [RFC 2156]; in particular, the
- syntax here permits only one msg-id in contrast to the multiple
- msg-ids in that Email version.
-
- Thus when an article contains a Supersedes-header, the old article
- mentioned SHOULD be withdrawn from circulation or access, as in a
- cancel message (7.3), and the new article inserted into the system as
- any other new article would have been.
-
- Whatever security or authentication checks are normally applied to a
- Control cancel message (or may be prescribed for such messages by
- some extension to this standard - see the remarks in 7.1 and 7.3)
- MUST also be applied to an article with a Supersedes-header. In the
- event of the failure of such checks, the article SHOULD be discarded,
- or at most stored as an ordinary article.
+ NOTE: There is no "c" in Supersedes.