RFC 5537: Netnews Architecture and Protocols
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
- —
- 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.
- RFC 850 (1983)
- RFC 1036 (1987)
- RFC 1849 (2010)
- RFC 5536 (2009)
- 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.
- RFC 5536Netnews Article FormatCurrent
November 2009
- RFC 3977Network News Transfer Protocol (NNTP)Updated
October 2006
- RFC 6048Network News Transfer Protocol (NNTP) Additions to LIST CommandCurrent
November 2010
- RFC 8054Network News Transfer Protocol (NNTP) Extension for CompressionCurrent
January 2017
- RFC 8143Using Transport Layer Security (TLS) with Network News Transfer Protocol (NNTP)Current
April 2017
- RFC 3864Registration Procedures for Message Header FieldsUpdated
September 2004
- RFC 5545Internet Calendaring and Scheduling Core Object Specification (iCalendar)Updated
September 2009
- RFC 5546iCalendar Transport-Independent Interoperability Protocol (iTIP)Updated
December 2009
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?