RFC 348 UNKNOWN ARPANET · TESTING

Discard Process

A voluntary Discard process for network debugging and measurement.

RFC EDITOR

Postel, J., "Discard Process", RFC 348, DOI 10.17487/RFC0348, May 1972, <https://www.rfc-editor.org/info/rfc348>.

BIBTEX

@misc{rfc348,
  series = {Request for Comments},
  number = 348,
  howpublished = {RFC 348},
  publisher = {RFC Editor},
  doi = {10.17487/RFC0348},
  url = {https://www.rfc-editor.org/info/rfc348},
  author = {J. Postel},
  title = {{Discard Process}},
  pagetotal = 1,
  year = 1972,
  month = may,
}

PUBLISHED: May 1972
AUTHORS: J. Postel
STREAM: Legacy
DOI: 10.17487/RFC0348

RFC text

Original text · RFC Editor View on rfc-editor.org ↗

Network Working Group                           Jon Postel
Request for Comments : 348                      Computer Science
                                                UCLA-NMC
NIC : 10427                                     30 May 72

Categories : Standard Processes



                            Discard Process



I suggest that for debugging and measurement purposes those hosts which
are willing implement a "Discard" process.

This discard 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 discard process would wait for data from the network.  When data is
received from the network it is discarded at once, (and the buffer space
is re-allocated).  The discard process is terminated by closing the
network 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.                   12/96   ]

ISO Plain Language

On this page

PROBLEMThe author proposes a simple service that could help with network debugging and measurement.

MECHANISMA willing host listens for a connection, performs the Initial Connection Protocol, and immediately discards data it receives until the connection closes.

HOW IT WORKSThe proposal is voluntary and applies only to hosts that choose to implement the Discard process.

§1The Discard Proposal

Jon Postel suggests that hosts willing to do so implement a Discard process for debugging and measurement. The RFC does not require every host to provide it.

The author proposes an optional service for network tests. A host can choose whether to run it.

§2Accepting and Discarding Data

The process listens for a connection request and performs the Initial Connection Protocol described in the Current Network Protocols notebook. After the ICP finishes, it waits for data from the Network.

Whenever data arrives, the process discards it at once and reallocates the buffer space. The process ends when the network connections are closed.

The service establishes a connection in the usual way, then throws away incoming data. It stays active until the connection closes.

§3Scope of the Suggestion

The RFC gives a short description of the process and its intended uses. It does not specify a return message or another service beyond receiving and discarding data.

The process has one job: accept data and discard it. The RFC does not define extra behavior.