Commit | Line | Data |
---|---|---|
15637ed4 RG |
1 | .\" Copyright (c) 1990, 1991 The Regents of the University of California. |
2 | .\" 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. All advertising materials mentioning features or use of this software | |
13 | .\" must display the following acknowledgement: | |
14 | .\" This product includes software developed by the University of | |
15 | .\" California, Berkeley and its contributors. | |
16 | .\" 4. Neither the name of the University nor the names of its contributors | |
17 | .\" may be used to endorse or promote products derived from this software | |
18 | .\" without specific prior written permission. | |
19 | .\" | |
20 | .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND | |
21 | .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE | |
22 | .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE | |
23 | .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE | |
24 | .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL | |
25 | .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS | |
26 | .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | |
27 | .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | |
28 | .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | |
29 | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | |
30 | .\" SUCH DAMAGE. | |
31 | .\" | |
32 | .\" @(#)cltp.4 6.2 (Berkeley) 3/28/91 | |
33 | .\" | |
34 | .Dd March 28, 1991 | |
35 | .Dt CLTP 4 | |
36 | .Os | |
37 | .Sh NAME | |
38 | .Nm cltp | |
39 | .Nd | |
40 | .Tn ISO | |
41 | Connectionless Transport Protocol | |
42 | .Sh SYNOPSIS | |
43 | .Fd #include <sys/socket.h> | |
44 | .Fd #include <netiso/iso.h> | |
45 | .Ft int | |
46 | .Fn socket AF_ISO SOCK_DGRAM 0 | |
47 | .Sh DESCRIPTION | |
48 | .Tn CLTP | |
49 | is a simple, unreliable datagram protocol which is accessed | |
50 | via the | |
51 | .Dv SOCK_DGRAM | |
52 | abstraction for the | |
53 | .Tn ISO | |
54 | protocol family. | |
55 | .Tn CLTP | |
56 | sockets are connectionless, and are | |
57 | normally used with the | |
58 | .Xr sendto | |
59 | and | |
60 | .Xr recvfrom | |
61 | calls, though the | |
62 | .Xr connect 2 | |
63 | call may also be used to fix the destination for future | |
64 | packets (in which case the | |
65 | .Xr recv 2 | |
66 | or | |
67 | .Xr read 2 | |
68 | and | |
69 | .Xr send 2 | |
70 | or | |
71 | .Xr write 2 | |
72 | system calls may be used). | |
73 | .Pp | |
74 | .Tn CLTP | |
75 | address formats are identical to those used by TP. | |
76 | In particular | |
77 | .Tn CLTP | |
78 | provides a service selector in addition | |
79 | to the normal | |
80 | .Tn ISO NSAP . | |
81 | Note that the | |
82 | .Tn CLTP | |
83 | selector | |
84 | space is separate from the TP selector space (i.e. a | |
85 | .Tn CLTP | |
86 | selector | |
87 | may not be | |
88 | .Dq connected | |
89 | to a TP selector). | |
90 | .Pp | |
91 | Options at the | |
92 | .Tn CLNP | |
93 | network level may be used with | |
94 | .Tn CLTP ; | |
95 | see | |
96 | .Xr clnp 4 . | |
97 | .Sh DIAGNOSTICS | |
98 | A socket operation may fail with one of the following errors returned: | |
99 | .Bl -tag -width [EADDRNOTAVAIL] | |
100 | .It Bq Er EISCONN | |
101 | when trying to establish a connection on a socket which | |
102 | already has one, or when trying to send a datagram with the destination | |
103 | address specified and the socket is already connected; | |
104 | .It Bq Er ENOTCONN | |
105 | when trying to send a datagram, but | |
106 | no destination address is specified, and the socket hasn't been | |
107 | connected; | |
108 | .It Bq Er ENOBUFS | |
109 | when the system runs out of memory for | |
110 | an internal data structure; | |
111 | .It Bq Er EADDRINUSE | |
112 | when an attempt | |
113 | is made to create a socket with a selector which has already been | |
114 | allocated; | |
115 | .It Bq Er EADDRNOTAVAIL | |
116 | when an attempt is made to create a | |
117 | socket with a network address for which no network interface | |
118 | exists. | |
119 | .El | |
120 | .Sh SEE ALSO | |
121 | .Xr getsockopt 2 , | |
122 | .Xr recv 2 , | |
123 | .Xr send 2 , | |
124 | .Xr socket 2 , | |
125 | .Xr intro 4 , | |
126 | .Xr iso 4 , | |
127 | .Xr clnp 4 | |
128 | .Sh HISTORY | |
129 | The | |
130 | .Nm | |
131 | protocol implementation | |
132 | .Ud |