Index Journeys
RFC 429 UNKNOWN TESTING · NETWORK SERVICES · DATA

Chargen: Character Generator Process

A proposed process that sends characters for network testing

On rfc-editor.org ↗
PUBLISHED
December 1972
AUTHORS
J. Postel
STREAM
Legacy
DOI
10.17487/RFC0429

RFC text

Original text · RFC Editor View on rfc-editor.org ↗ 
ARPA Network Information Center
Stanford Research Institute
Menlo Park, California  94025

NWG/RFC #429                                 Jonathan B. Postel (UCLA-NMC)
NIC #13281                                   12-DEC-72



                      Character Generator Process



I hereby propose that there be a standard process implemented on
whatever hosts desire which generates character data with out any
regard to input. In some sense the process is the converse of the
discard process [RFC 348]. Many hosts have an existing terminal
testing program [e.g. TTYTST] which would suit this function
adequately.

This Character Generator process would listen for a request for
connection and execute the Initial Connection Protocol (ICP) as
specified in NIC 7104 the "Current Network Protocols" notebook.  Upon
completion of the ICP the Character Generator process would begin to
send characters into the network as buffer space is made available .
The Character Generator process is terminated by closing the
connections.








       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by BBN Corp. under the   ]
       [ direction of Alex McKenzie.                      1/97 ]

ISO Plain Language

On this page
PROBLEMHosts could benefit from a common process that supplies character data for testing, rather than relying on separate local programs.
MECHANISMA host would accept a connection, complete the Initial Connection Protocol and send characters as buffer space became available.
PROPOSED SERVICEThe proposal defines a simple service that continues until the connection is closed.

§1A Standard Character Generator

Jonathan Postel proposes a process that generates character data without regard to input. Hosts could choose whether to implement it. The RFC notes that existing terminal-testing programs on many hosts could serve this purpose.

The proposal describes the process as the converse of the Discard process.

A host could offer a process that sends characters without using the data it receives. The RFC presents this as a proposed standard service.

§2Establishing and Closing a Connection

The Character Generator would listen for a connection request and perform the Initial Connection Protocol described in the Current Network Protocols notebook. After that protocol completed, it would send characters as buffer space became available. Closing the connections would terminate the process.

The service first follows the network's connection procedure. It then sends characters when space is available and stops when the connections close.

§3Host Implementation

The RFC proposes that hosts implement the process if they choose to provide it. It does not specify a socket number, character sequence, data rate or required deployment.

Each host could decide whether to run the proposed service. The RFC leaves its exact socket number and character sequence unspecified.