xref: /freebsd/share/man/man5/protocols.5 (revision e0c4386e7e71d93b0edc0c8fa156263fc4a8b0b6)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.Dd December 7, 2020
29.Dt PROTOCOLS 5
30.Os
31.Sh NAME
32.Nm protocols
33.Nd protocol name data base
34.Sh DESCRIPTION
35The
36.Nm
37file contains information regarding the assigned protocol numbers
38used by IPv4 and IPv6 to identify the next level protocol.
39For each protocol a single line should be present
40with the following information:
41.Bd -unfilled -offset indent
42official protocol name
43protocol number
44aliases
45.Ed
46.Pp
47Items are separated by any number of blanks and/or
48tab characters.
49A ``#'' indicates the beginning of
50a comment; characters up to the end of the line are
51not interpreted by routines which search the file.
52.Pp
53Protocol names may contain any printable
54character other than a field delimiter, newline,
55or comment character.
56.Sh FILES
57.Bl -tag -width /etc/protocols -compact
58.It Pa /etc/protocols
59The
60.Nm
61file resides in
62.Pa /etc .
63.El
64.Sh SEE ALSO
65.Xr getprotoent 3
66.Rs
67.%R RFC 2780
68.%D March 2000
69.%T "IANA Allocation Guidelines For Values In the \
70Internet Protocol and Related Headers"
71.Re
72.Rs
73.%R RFC 5237
74.%D February 2008
75.%T "IANA Allocation Guidelines for the Protocol Field"
76.Re
77.Sh HISTORY
78The
79.Nm
80file format appeared in
81.Bx 4.2 ,
82describing the "known protocols used in the DARPA Internet".
83.Sh BUGS
84A name server should be used instead of a static file.
85