From: Kent Landfield (kent@landfield.com)
Date: Fri Jun 01 2001 - 16:58:46 CDT
Yes... English is my first language. I corrected a couple typos below.
# 6.12. Archive
#
# This optional header allows the poster to provide instructions regarding
# the preservation of the article in long-term publicly accessible archives.
#
# Archive-content = [CFWS] ("no" | "yes") [CFWS]
# Archive-filename-parameter
# = Filename-token "=" value
# ; for USENET-header-parameters see 4.1
# Archive-date-parameter
# = Date-token "=" date-time-value
# ; for USENET-header-parameters see 4.1
# Date-token = [CFWS] "date" [CFWS]
# Filename-token = [CFWS] "filename" [CFWS]
# date-time-value = date-time
#
# The presence of an "Archive: no" header in an article indicates the
# poster does not want long-term or permanent copies kept in publicly
# accessible archives. "Archive: yes" indicates the poster's desire
# for archives to store the article and make it publicly accessible.
# The lack of an Archive header indicates the poster has not specified
a preference either way. In that case, archiving of the article
# can occur.
#
# The optional Filename parameter MAY be used to suggest a filename
# under which the article may be stored.
#
# [Mention dangers of filename in the Security section.]
#
# The optional Date parameter allows a poster to specify a date after
# which the article should no longer be available from public archives.
This may not be the same as the date after which it is no longer
# available from the normal news spool, if any, which is controlled by
# site policy and the advisory "Expires" header.
#
# NOTE: There is no way per this standard to ensure articles posted
# to USENET are either archived or not archived. It is unwise for
# posters to assume that including an "Archive: no" in an article
# will reliably prevent it from being made available in a long-lived
# public form; indicating your wishes does not guarantee they will
# be respected. Moreover, even if this header prevents the poster's
# article from being archived publicly, it does nothing to prevent
# the archiving of a followup in which the poster's words are quoted.
#
# NOTE: This standard does not attempt to define the length of
# "long-term", since it is dependent on many factors, including
# the retention policies of individual sites, and the customs or
# policies established for particular newsgroup or hierarchies.
#
# --------------
#
Can we live with "try 42", take two ?
-- Kent Landfield Phone: 1-817-545-2502 Email: kent@landfield.com http://www.landfield.com/ Search the Usenet FAQ Archive at http://www.faqs.org/faqs/ Search the RFC/FYI/STD/BCP Archive at http://www.faqs.org/rfcs/