Currently a combination of this and RFC 1036 are regarded as the de-facto standard. At the present time an urgent need has been identified to formalize and document many of the current and proposed extensions to the Usenet Article format. Many extensions are only vaguely documented and have competing and overlapping alternatives. Currently a combination of this and RFC 1036 are regarded as the de-facto standard. At the present time an urgent need has been identified to formalize and document many of the current and proposed extensions to the Usenet Article format.
Many extensions are only vaguely documented and have competing and overlapping alternatives.
The Goal of this working group is to publish a standards-track successor to RFC 1036 that with particular attention to backward compatibility, formalizes best current practice and best proposed practice. Publish a standards-track successor to RFC 1036 that formalizes best current practice and best proposed practice. Publish any other extensions to the Usenet Article Standard that warrant being formal extensions but are outside the scope of the main standard. To header is not present. Apparently, there is ambiguity in how this has been handled.