PROTOCOLS(4) — Series 300 and 800 Only

NAME

protocols − protocol name data base

DESCRIPTION

This file associates protocol numbers with official protocol names and aliases. This allows the user to refer to a protocol by a symbolic name instead of a number. For each protocol a single line should be present with the following information:

<official protocol name> <official protocol number>

These mappings are defined by RFC 923 Assigned Numbers.

Aliases are other names under which the protocol is also known. For example:

tcp 6 TCP

In this example, the library call getprotobyname can be invoked as:

p = getprotobyname("TCP");

instead of

p = getprotobyname("tcp");

Both produce the same results.

A line cannot start with a space. Items are separated by any number of blanks and/or tab characters. A ‘#’ indicates the beginning of a comment. Characters from the ‘#’ to the end of the line are not interpreted by routines which search the file.

Protocol names can contain any printable character other than a white space, newline, or comment character. Trailing blanks or tabs are allowed at the end of a line.

EXAMPLES

tcp 6 TCP # transmission control protocol
udp 17 UDP # user datagram protocol

DEPENDENCIES

Implemented on the Series 300 and 800 only.

AUTHOR

UCB (University of California at Berkeley)

Museum