1 .\" $NetBSD: 2.t,v 1.3 2003/02/05 00:02:28 perry Exp $
3 .\" Copyright (c) 1983, 1986, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" @(#)2.t 8.1 (Berkeley) 6/8/93
40 the International Standards Organization's (ISO)
41 Open System Interconnection (OSI) model of
42 network communication [ISO81] [Zimmermann80],
43 the networking facilities
44 described here correspond to a portion of the
45 session layer (layer 3) and all of the transport and
46 network layers (layers 2 and 1, respectively).
48 The network layer provides possibly imperfect
49 data transport services with minimal addressing
51 Addressing at this level is normally host to host,
52 with implicit or explicit routing optionally supported
53 by the communicating agents.
56 layer the notions of reliable transfer, data sequencing,
57 flow control, and service addressing are normally
58 included. Reliability is usually managed by
59 explicit acknowledgement of data delivered. Failure
60 to acknowledge a transfer results in retransmission of
61 the data. Sequencing may be handled by tagging
62 each message handed to the network layer by a
63 \fIsequence number\fP and maintaining
64 state at the endpoints of communication to use
65 received sequence numbers in reordering data which
68 The session layer facilities may provide forms of
69 addressing which are mapped into formats required
70 by the transport layer, service authentication
71 and client authentication, etc. Various systems
72 also provide services such as data encryption and
73 address and protocol translation.
75 The following sections begin by describing some of the common
76 data structures and utility routines, then examine
77 the internal layering. The contents of each layer
78 and its interface are considered. Certain of the
79 interfaces are protocol implementation specific. For
80 these cases examples have been drawn from the Internet [Cerf78]
81 protocol family. Later sections cover routing issues,
82 the design of the raw socket interface and other