Browse Prior Art Database

Standard for interchange of USENET messages (RFC1036)

IP.com Disclosure Number: IPCOM000001841D
Original Publication Date: 1987-Dec-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 25 page(s) / 43K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M.R. Horton: AUTHOR [+2]

Abstract

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.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group M. Horton

Request for Comments: 1036 AT&T Bell Laboratories

Obsoletes: RFC-850 R. Adams

Center for Seismic Studies

December 1987

Standard for Interchange of USENET Messages

STATUS OF THIS MEMO

This document defines the standard format for the interchange of

network News messages among USENET hosts. It updates and replaces

RFC-850, reflecting version B2.11 of the News program. This memo is

disributed as an RFC to make this information easily accessible to

the Internet community. It does not specify an Internet standard.

Distribution of this memo is unlimited.

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.

2. Message Format

The primary consideration in choosing a message format is that it

fit in with existing tools as well as possible. Existing tools

include implementations of both mail and news. (The notesfiles

system from the University of Illinois is considered a news

implementation.) A standard format for mail messages has existed

for many years on the Internet, and this format meets most of the

needs of USENET. Since the Internet format is extensible,

extensions to meet the additional needs of USENET are easily made

within the Internet standard. Therefore, the rule is adopted that

all USENET news messages must be formatted as valid Internet mail

messages, according to the Internet standard RFC-822. The USENET

News standard is more restrictive than the Internet standard,

placing additional requirements on each message and forbidding use

of certain Internet features. However, it should always be possible

to use a tool expecting an Internet message to process a news

message. In any situation where this standard conflicts with the

Internet standard, RFC-822 should be considered correct and this

standard in error.

Here is an example USENET message to illustrate the fields.

From: jerry@eagle.ATT.COM (Jerry Schwarz)

Path: cbosgd!mhuxj!mhuxt!eagle!jerry

Newsgroups: news.announce

Subject: Usenet Etiquette -- Please Read

Message-ID: <642@eagle.ATT.COM>

...