"Son of 1036": News Article Format and Transmission
Metadata
- Publisher
- IETF
- Doc Type
- Specification
- Pages
- 106
- Abstract
- 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.
- Publication Date
- 2010-03-01
- Status Note
- Historic
- DOI
10.17487/RFC1849- Link
- https://doi.org/10.17487/RFC1849
- Author(s)
- Henry Spencer
- Keyword(s)
- Netnews, Usenet, USEFOR
Latest version of IETF RFC 1849
Document Versions — IETF RFC 1849
-
▶ IETF RFC 1849 (2010-03-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- ANSI/INCITS X3.4 [Active]
- ISO 9899 [Active]
- Borenstein, N., < http://ftp.funet.fi/pub/unix/mail/metamail/ANNOUNCE >, February 1994. EXTERNAL
- Tim O'Reilly and Grace Todino, Managing UUCP and Usenet, O'Reilly & Associates Ltd., January 1992. EXTERNAL
- David Sanderson, Smileys, O'Reilly & Associates Ltd., 1993. EXTERNAL
- IETF RFC 821 [Superseded*]
- IETF RFC 822 [Superseded*]
- IETF RFC 850 [Superseded*]
- IETF RFC 977 [Superseded*]
- IETF RFC 1036 [Superseded*]
- IETF RFC 1123 [Active*]
- IETF RFC 1341 [Superseded*]
- IETF RFC 1342 [Superseded*]
- IETF RFC 1345 [Active*]
- IETF RFC 1413 [Active*]
- IETF RFC 1456 [Active*]
- IETF RFC 1544 [Superseded*]
- IETF RFC 1896 [Active*]
- IETF RFC 2045 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2047 [Active*]
- IETF RFC 2049 [Active*]
- IETF RFC 2822 [Superseded*]
- IETF RFC 3977 [Active*]
- IETF RFC 5322 [Active, Amended*]
- IETF RFC 5536 [Active*]
- IETF RFC 5537 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1849.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1849, "Son of 1036": News Article Format and Transmission. Available at https://doi.org/10.17487/RFC1849
Snippet:
IETF RFC 1849, "Son of 1036": News Article Format and Transmission. Available at https://doi.org/10.17487/RFC1849
HTML (ISO 690 compliant)
Preview:
IETF RFC 1849, "Son of 1036": News Article Format and Transmission. Available at https://doi.org/10.17487/RFC1849
Snippet:
<span class="citation"><cite>IETF RFC 1849</cite>, "Son of 1036": News Article Format and Transmission. Available at <a href="https://doi.org/10.17487/RFC1849" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1849</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1849, "Son of 1036": News Article Format and Transmission
doi: 10.17487/RFC1849
url: https://doi.org/10.17487/RFC1849
doi: 10.17487/RFC1849
url: https://doi.org/10.17487/RFC1849
Snippet:
<li> <cite id="bib-rfc1849">IETF RFC 1849</cite>, "Son of 1036": News Article Format and Transmission <span class="doi">10.17487/RFC1849</span> </li>