📄 2.t
字号:
.\" Copyright (c) 1983, 1986, 1993.\" The Regents of the University of California. All rights reserved..\".\" Redistribution and use in source and binary forms, with or without.\" modification, are permitted provided that the following conditions.\" are met:.\" 1. Redistributions of source code must retain the above copyright.\" notice, this list of conditions and the following disclaimer..\" 2. Redistributions in binary form must reproduce the above copyright.\" notice, this list of conditions and the following disclaimer in the.\" documentation and/or other materials provided with the distribution..\" 3. All advertising materials mentioning features or use of this software.\" must display the following acknowledgement:.\" This product includes software developed by the University of.\" California, Berkeley and its contributors..\" 4. Neither the name of the University nor the names of its contributors.\" may be used to endorse or promote products derived from this software.\" without specific prior written permission..\".\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION).\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF.\" SUCH DAMAGE..\".\" @(#)2.t 8.1 (Berkeley) 6/8/93.\".nr H2 1.\".ds RH Overview.br.ne 2i.NH\s+2Overview\s0.PPIf we considerthe International Standards Organization's (ISO)Open System Interconnection (OSI) model ofnetwork communication [ISO81] [Zimmermann80],the networking facilitiesdescribed here correspond to a portion of thesession layer (layer 3) and all of the transport andnetwork layers (layers 2 and 1, respectively)..PPThe network layer provides possibly imperfectdata transport services with minimal addressingstructure.Addressing at this level is normally host to host,with implicit or explicit routing optionally supportedby the communicating agents. .PPAt the transportlayer the notions of reliable transfer, data sequencing,flow control, and service addressing are normallyincluded. Reliability is usually managed by explicit acknowledgement of data delivered. Failureto acknowledge a transfer results in retransmission ofthe data. Sequencing may be handled by taggingeach message handed to the network layer by a\fIsequence number\fP and maintainingstate at the endpoints of communication to utilizereceived sequence numbers in reordering data whicharrives out of order..PPThe session layer facilities may provide forms ofaddressing which are mapped into formats requiredby the transport layer, service authenticationand client authentication, etc. Various systemsalso provide services such as data encryption andaddress and protocol translation..PPThe following sections begin by describing some of the commondata structures and utility routines, then examinethe internal layering. The contents of each layerand its interface are considered. Certain of theinterfaces are protocol implementation specific. Forthese cases examples have been drawn from the Internet [Cerf78]protocol family. Later sections cover routing issues,the design of the raw socket interface and othermiscellaneous topics.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -