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