ObsoletedLegacy stream

RFC 1036: Standard for interchange of USENET messages

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5536, RFC 5537.

Current document in this lineage: RFC 5536Netnews Article Format; RFC 5537Netnews Architecture and Protocols

In plain English — editorial summary, not part of the RFC

This RFC defines the standard format for the interchange of network News messages among USENET hosts. It updates and replaces RFC-850, reflecting version B2.11 of the News program. This memo is distributed as an RFC to make this information easily accessible to the Internet community. It does not specify an Internet standard.

Document record

Document ID
RFC1036
Published
December 1987
Authors
M.R. Horton; R. Adams
Status
UNKNOWN
Stream
Legacy
Area
Pages
19
Also known as
Obsoletes:
RFC 850
Obsoleted by:
RFC 5536, RFC 5537

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 850 (1983)
  2. RFC 1036 (1987)
  3. RFC 1849 (2010)
  4. RFC 5536 (2009)
  5. RFC 5537 (2009)

Read the full history of Netnews Architecture and Protocols

Referenced by

2 later RFCs formally update or obsolete part of this document.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/1036-standard-for-interchange-of-usenet-messages