metasystema.org
ObsoletedHISTORICINDEPENDENT stream

RFC 1849: "Son of 1036": News Article Format and Transmission

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 5536 — Netnews Article Format; RFC 5537 — Netnews Architecture and Protocols

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

By the early 1990s, it had become clear that RFC 1036, then the specification for the Interchange of USENET Messages, was badly in need of repair. This "Internet-Draft-to-be", though never formally published at that time, was widely circulated and became the de facto standard for implementors of News Servers and User Agents, rapidly acquiring the nickname "Son of 1036". Indeed, under that name, it could fairly be described as the best-known Internet Draft (n)ever published, and it formed the starting point for the recently adopted Proposed Standards for Netnews. It is being published now in order to provide the historical background out of which those standards have grown. Present-day implementors should be aware that it is NOT NOW APPROPRIATE for use in current implementations. This document defines a Historic Document for the Internet community.

Document record

Document ID
RFC1849
Published
March 2010
Authors
H. Spencer
Status
HISTORIC
Stream
INDEPENDENT
Area
—
Pages
106
Also known as
—
Obsoleted by:
RFC 5536, RFC 5537

Topics

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.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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/1849-son-of-1036-news-article-format-and-transmission