App-DocKnot
view release on metacpan or search on metacpan
t/data/spin/output/usefor/index.html view on Meta::CPAN
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>The Usenet Article Format and Protocols</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="stylesheet" href="/~eagle/styles/indent.css" type="text/css" />
<link rel="previous" href="../photos/" title="Photos" />
<link rel="next" href="../nntp/" title="NNTP" />
<link rel="up" href="../" title="Russ Allbery" />
<link rel="top" href="../" />
</head>
<!-- Spun from index.th by DocKnot %VERSION% on %DATE% -->
<body>
<table class="navbar"><tr>
<td class="navleft">< <a href="../photos/">Photos</a></td>
<td>
<a href="../">Russ Allbery</a>
</td>
<td class="navright"><a href="../nntp/">NNTP</a> ></td>
</tr></table>
<h1>The Usenet Article Format and Protocols</h1>
<blockquote class="quote"><p class="short">
Usenet interprets management as damage and routes around it.
</p><p class="attribution">
Peter da Silva
</p></blockquote>
<h2>Standards</h2>
<p>
The current standard for the format of Usenet (Netnews) articles is
<a href="rfcs/rfc5536.txt">RFC 5536</a>, published in November of 2009. The
standard for the architecture and protocols of Netnews, including how
articles are modified and checked when traveling from system to system, is
<a href="rfcs/rfc5537.txt">RFC 5537</a>, published at the same time. I was the
document editor for RFC 5537. Both of these documents are built on
<a href="rfcs/rfc5322.txt">RFC 5322</a>, the current standard for mail messages.
Netnews articles are compliant mail messages with some additional fields
and a few additional restrictions.
</p>
<p>
These RFCs obsolete the previous standard for the format of Usenet
articles, <a href="rfcs/rfc1036.txt">RFC 1036</a>, and the draft document known
as "Son-of-1036" which was published as <a href="rfcs/rfc1849.txt">RFC 1849</a>.
All software should now follow the newer standards, but RFC 1036 and RFC
1849 may be of interest in understanding the behavior of older standards.
</p>
<p>
There is one additional Netnews-specific RFC: <a href="rfcs/rfc8315.txt">RFC
8315</a>, which standardizes Cancel-Locks for Netnews articles.
</p>
<p>
( run in 0.452 second using v1.01-cache-2.11-cpan-39bf76dae61 )