As per Relevance of the word february, we have this rfc below:
Network Working Group D.L.
Request for Comments: 996 University of
February 1987
Statistics
STATUS OF THIS
This RFC specifies a standard for the ARPA Internet community.
and gateways on the DARPA Internet that choose to implement a
statistics monitoring facility may use this protocol to
statistics data upon request to a monitoring center or
host. Distribution of this memo is unlimited
Many host and gateway implementations include a facility
records traffic statistics, such as packet counters, error
and significant event counters for debugging and
evluation. Simple data-access and formatting programs can be used
display these statistics along with the status of connections, etc
Several operating systems, including the various Unix systems
Fuzzball systems, already provide extensive facilities to capture
display these data for local users and/or operators
In many instances it is highly useful to observe statistics data
remote hosts and gateways from a monitoring center or debugging host
Indeed, several protocols have been implemented and used
for this purpose [1-6]. In many cases the data can be retrieved
conventional services such as remote login or even file transfer
However, use of these heavyweight mechanisms is awkward and
if conducted on a regular, frequent basis and may involve
intrusion in the operating system if retrofitted to existing systems
The Statistics Server (STATSRV) protocol is intended as a
mechanism similar in spirit to NETSTAT [7] and complementary to it
STATSRV is designed to capture statistics data with minimal
on existing systems or networks. It is intended for use with
hosts and gateways primarily for casual monitoring and
purposes. It is not intended as a full-function monitoring
[1,5,6] providing detailed, standardized reports suitable for
analysis, for example, but could be useful in exploratory
leading to enduring systems of this type
The STATSRV model is based on the native host command language
for statistics monitoring and display. The client sends a null
terminated ASCII command to the server, which then responds with
null-terminated ASCII response suitable for a printer or CRT display
Although in principle STATSRV could be used over TCP, it is
intrusive and more efficient to use it over UDP. In the case of UDP
D. L. Mills [Page 1]
RFC 996 February 1987
commands and responses must fit into a single 576-octet IP datagram
In both UDP and TCP the assigned port number is 133 (decimal).
As is conventional in other lightweight services of this
(NETSTAT, FINGER, etc.), there is no provision for access control
authentication in STATSRV. If necessary, each command could include
password or other mechanism to discourage casual abuse
The Fuzzball system includes many local commands to display
data structures, including one that produces the following
for each network device, in this case "dm0" on host "udel2.udel.edu":
Process type: 000027 options: 040000
Subnet: DMV status: 376 hello: 15 timeout: 2000
Foreign address: [192.5.39.87] max size: 576
Input packets 3645 Output packets 3690
bad format 0 ICMP msgs 0
bad checksum 0 Input errors 0
returned 0 Output errors 0
dropped 2 No buffer 0
HELLO msgs 2286 Preempted 0
The same billboard is returned as a null-terminated ASCII string in
UDP datagram by sending the null-terminated ASCII command "dm0" in
UDP datagram to the host. Similar billboards can be produced for
processes in the system. Unix programs and shell scripts have
built which send commands like these to selected hosts on a
basis in order to construct a simple, ad-hoc monitoring facility
[1] Flood Page, D.,"Gateway Monitoring Protocol", DARPA
Working Group Report IEN-131, Bolt Beranek and Newman,
1980.
[2] Flood Page, D., "The CMCC Terminal Process", DARPA
Working Group Report IEN-132, Bolt Beranek and Newman,
1980.
[3] Flood Page, D., "CMCC Performance Measurement Message Formats",
DARPA Network Working Group Report IEN-157, Bolt Beranek
Newman, September 1980.
[4] Jones, R.G., " A Proposal for Simple Measurement Support
Users", DARPA Network Working Group Report IEN-161,
College London, November 1980.
D. L. Mills [Page 2]
RFC 996 February 1987
[5] Littauer, B.M., A.J. Huang and R.M. Hinden," A Host
Protocol", DARPA Network Working Group Report IEN-197,
Beranek and Newman, September 1981.
[6] Hinden, R.M.," A Host Monitoring Protocol", DARPA
Working Group Report RFC-869, BBN Communications Corporation
December 1983.
[7] Reynolds, J.K., and J. Postel, "Assigned Numbers", DARPA
Working Group Report RFC-990, USC Information
Institute, November 1986.
D. L. Mills [Page 3]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
