News Article Format
draft-ietf-usefor-article-02
USEFOR Working Group
6. Optional Headers
[Previous Up to Table of Contents Next ]
6. Optional Headers
The headers appearing in this section have established
meanings. They MUST be interpreted according to the
definitions made in this document. None of them are required to
appear in every article. All of the headers appearing in this
document MUST NOT appear more than once in an article. Headers
not appearing in this document (i.e. X-headers, headers defined
by cooperating subnets) are exempt from this requirement. See
"Responsibilities of Agents" for a clear picture.
6.1 Followup-To
6.2 Sender
6.3 Expires
6.3. Reply-To
6.3.1 Examples:
6.4. References
6.4.1 Examples:
6.5. Control
6.6. Control Messages
6.6.1 The "newgroup" Control Message
6.6.1.1 multipart/news-groupinfo
6.6.1.2 application/news-groupinfo
6.6.1.3 Initial Named Articles
6.6.2 The "rmgroup" Control Message
6.6.3 The "mvgroup" Control Message
6.6.3.1 Single group
6.6.3.2 Multiple Groups
6.6.4 The "checkgroups" Control Message
6.6.4.1 Example:
6.6.5 application/news-checkgroups
6.6.5.1 Examples
6.6.6 Cancel
6.6.7 ihave, sendme
6.6.8 Obsolete control messages.
6.7. Distribution
6.7.1 Historical Note
6.7.1.1 New Semantics
6.7.1.2 Planned Uses
6.7.2 Definition
6.8. Keywords
6.9. Summary
6.10. Approved
6.11 Lines
6.12 Xref
6.13 Organization
6.14 User-Agent
6.14.1 Examples:
6.15 MIME headers
6.15.1 Syntax
6.15.2 Content-Transfer-Encoding
6.15.3 Content-Type
6.15.4 Character Sets
6.15.5 Definition of some new Content-Types
6.15.5.1 Application/news-transmission
6.15.5.2 Application/news-message
6.15.5.3 Message/news obsoleted
6.15.6 MIME within headers
6.16 Supersedes / Replaces
6.16.1 Message-ID version numbers chain procedure.
6.16.2 Implementation and Use Note
6.16.3 Transition
6.16.4 Replaced-by
6.16.5.1 Examples
6.16.5.2 Example
6.16.7 Issues
6.17 Archive
6.18. Obsolete Headers
[Previous Up to Table of Contents Next ]