xref: /freebsd/share/man/man5/protocols.5 (revision 22cf89c938886d14f5796fc49f9f020c23ea8eaf)
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.\"     @(#)protocols.5	8.1 (Berkeley) 6/5/93
29.\"
30.Dd December 7, 2020
31.Dt PROTOCOLS 5
32.Os
33.Sh NAME
34.Nm protocols
35.Nd protocol name data base
36.Sh DESCRIPTION
37The
38.Nm
39file contains information regarding the assigned protocol numbers
40used by IPv4 and IPv6 to identify the next level protocol.
41For each protocol a single line should be present
42with the following information:
43.Bd -unfilled -offset indent
44official protocol name
45protocol number
46aliases
47.Ed
48.Pp
49Items are separated by any number of blanks and/or
50tab characters.
51A ``#'' indicates the beginning of
52a comment; characters up to the end of the line are
53not interpreted by routines which search the file.
54.Pp
55Protocol names may contain any printable
56character other than a field delimiter, newline,
57or comment character.
58.Sh FILES
59.Bl -tag -width /etc/protocols -compact
60.It Pa /etc/protocols
61The
62.Nm
63file resides in
64.Pa /etc .
65.El
66.Sh SEE ALSO
67.Xr getprotoent 3
68.Rs
69.%R RFC 2780
70.%D March 2000
71.%T "IANA Allocation Guidelines For Values In the \
72Internet Protocol and Related Headers"
73.Re
74.Rs
75.%R RFC 5237
76.%D February 2008
77.%T "IANA Allocation Guidelines for the Protocol Field"
78.Re
79.Sh HISTORY
80The
81.Nm
82file format appeared in
83.Bx 4.2 ,
84describing the "known protocols used in the DARPA Internet".
85.Sh BUGS
86A name server should be used instead of a static file.
87