UpdatedPROPOSED STANDARDIETF stream

RFC 5537: Netnews Architecture and Protocols

Still current, but amended. Parts of this document are changed or extended by RFC 8315. Read both.

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

This document defines the architecture of Netnews systems and specifies the correct manipulation and interpretation of Netnews articles by software that originates, distributes, stores, and displays them. It also specifies the requirements that must be met by any protocol used to transport and serve Netnews articles. [STANDARDS-TRACK]

Document record

Document ID
RFC5537
Published
November 2009
Authors
R. Allbery; C. Lindsey
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
48
Also known as
Obsoletes:
RFC 1036, RFC 1849
Updated by:
RFC 8315

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

One later RFC formally updates or obsoletes 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/5537-netnews-architecture-and-protocols