RFC1036

Release Notes: In keeping with the RKT design guidelines, RFC1036 has been split up into over 30 separate files. (The complete RFC1036 is available at: http://www.cis.ohio-state.edu/htbin/rfc/rfc1036.html)

Related entry points into the Usenet RKT for Developers:


Network Working Group

Request for Comments: 1036

Obsoletes:

RFC-850

M. Horton, AT&T Bell Laboratories

R. Adams, Center for Seismic Studies

December 1987

Standard for Interchange of USENET Messages

1. Introduction

This document defines the standard format for the interchange of network News messages among USENET hosts. It describes the format for messages themselves and gives partial standards for transmission of news. The news transmission is not entirely in order to give a good deal of flexibility to the hosts to choose transmission hardware and software, to batch news, and so on.

There are five sections to this document. Section two defines the format. Section three defines the valid control messages. Section four specifies some valid transmission methods. Section five describes the overall news propagation algorithm.

RFC1036 STATUS OF THIS MEMO
RFC1036 2. Message Format
RFC1036 2.1. Required Header lines


RFC1036 2.2. Optional Headers

RFC1036 3. Control Messages

RFC1036 4. Transmission Methods

RFC1036 5. The News Propagation Algorithm

-B-r-o-a-d-e-n- your knowledge


Up to NNTP Protocol

RKT Rapid-Links:[Search] [RKT Tips] Path:For Developers / NNTProtocol / RFC1036