API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Preference is stored in this browser only.

IETF RFC 5537
[ACTIVE]

Netnews Architecture and Protocols

Metadata

Publisher
IETF
Doc Type
Standard
Pages
48
Abstract
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]
Publication Date
2009-11-01
Status Note
Proposed Standard
DOI
10.17487/RFC5537
Link
https://doi.org/10.17487/RFC5537
Author(s)
Russ Allbery
Charles Lindsey
Keyword(s)
USEFOR, Usenet, Netnews
Latest version of IETF RFC 5537

Document Versions — IETF RFC 5537

  • ▶ IETF RFC 5537 (2009-11-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Amended by:

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5537.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5537, Netnews Architecture and Protocols. Available at https://doi.org/10.17487/RFC5537
Snippet:
IETF RFC 5537, Netnews Architecture and Protocols. Available at https://doi.org/10.17487/RFC5537

HTML (ISO 690 compliant)

Preview:
IETF RFC 5537, Netnews Architecture and Protocols. Available at https://doi.org/10.17487/RFC5537
Snippet:
<span class="citation"><cite>IETF RFC 5537</cite>, Netnews Architecture and Protocols. Available at <a href="https://doi.org/10.17487/RFC5537" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5537</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5537, Netnews Architecture and Protocols
doi: 10.17487/RFC5537
url: https://doi.org/10.17487/RFC5537
Snippet:
<li>
<cite id="bib-rfc5537">IETF RFC 5537</cite>, Netnews Architecture and Protocols
<span class="doi">10.17487/RFC5537</span>
</li>

Referenced By