Debian Codegraph @

rfc2143.html

raw
1 <pre>Network Working Group B. Elliston
2 Request for Comments: 2143 Compucat Research
3 Category: Experimental May 1997
4
5
6 <span class="h1">Encapsulating IP with the Small Computer System Interface</span>
7
8 Status of this Memo
9
10 This memo defines an Experimental Protocol for the Internet
11 community. This memo does not specify an Internet standard of any
12 kind. Discussion and suggestions for improvement are requested.
13 Distribution of this memo is unlimited.
14
15 Table of Contents
16
17 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-1">1</a>
18 2. Brief background to the Small Computer System Interface . 2
19 <a href="#section-3">3</a>. Link Encapsulation . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
20 <a href="#section-4">4</a>. An Address Resolution Protocol . . . . . . . . . . . . . . <a href="#page-4">4</a>
21 <a href="#section-5">5</a>. Scalability . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
22 <a href="#section-6">6</a>. Possible applications . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
23 <a href="#section-7">7</a>. Security considerations . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
24 <a href="#section-8">8</a>. References . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
25 <a href="#section-9">9</a>. Author's Address . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
26
27 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
28
29 As the capacity of local area networks increases to meet the demands
30 of high volume application data, there is a class of network
31 intensive problems which may be applied to small clusters of
32 workstations with high bandwidth interconnection.
33
34 A general observation of networks is that the bit rate of the data
35 path typically decreases as the distance between hosts increases. It
36 is common to see regional networks connected at a rate of 64Kbps and
37 office networks connected at 100Mbps, but the inverse is far less
38 common.
39
40 The same is true of peripheral and memory interconnection. Memory
41 close to a CPU's core may run at speeds equivalent to a gigabit
42 network. More importantly, devices such as disks may connect a
43 number of metres away from its host at speeds well in excess of
44 current local area network capacity.
45
46
47
48
49
50
51
52 <span class="grey">Elliston Experimental [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2143">RFC 2143</a> Encapsulating IP with the SCSI May 1997</span>
55
56
57 This document outlines a protocol for connecting hosts running the
58 TCP/IP protocol suite over a Small Computer System Interface (SCSI)
59 bus. Despite the limitation in the furthest distance between hosts,
60 SCSI permits close clusters of workstations to communicate between
61 each other at speeds approaching 360 megabits per second.
62
63 The proposed introduction of newer SCSI implementations such as
64 serial SCSI will bring much faster communication at greater
65 distances.
66
67 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Background to the Small Computer System Interface (SCSI)</span>
68
69 SCSI defines a physical and data link protocol for connecting
70 peripherals to hosts. Devices connect autonomously to a bus and send
71 synchronous or asynchronous messages to other devices.
72
73 Devices are identified by a numeric identifier (ID). For the
74 original SCSI protocol, devices are given a user-selectable SCSI ID
75 between 0 and 7. Wide SCSI specifies a range of SCSI IDs between 0
76 and 15. The most typical SCSI configuration comprises of a host
77 adapter and one or more SCSI- capable peripherals responding to
78 asynchronous messages from the host adapter.
79
80 The most critical aspect of the protocol with respect to its use as a
81 data link for the Internet protocols is that a SCSI device must act
82 as an "initiator" (generator of SCSI commands/requests) or a "target"
83 (a device which responds to SCSI commands from the initiator). This
84 model is correct for a master/slave relationship between host adapter
85 and devices. The only time an initiator receives a message addressed
86 to it is in response to a command issued by it in the past and a
87 target device always generates a response to every command it
88 receives.
89
90 Clearly this is unsuitable for the peer-to-peer model required for
91 multiple host adapters to asynchronously send SCSI commands to one
92 another without surplus bus traffic. Furthermore, some host adapters
93 may refuse to accept a message from another adapter as it expects to
94 only initiate SCSI commands. This restriction to the protocol
95 requires that SCSI adapters used for IP encapsulation support what is
96 known as "target mode", with software device driver support to pass
97 these messages up to higher layer modules for processing.
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Elliston Experimental [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2143">RFC 2143</a> Encapsulating IP with the SCSI May 1997</span>
111
112
113 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Link Encapsulation</span>
114
115 The ANSI SCSI standard defines classes of peripherals which may be
116 interconnected with the SCSI protocol. One of these is the class of
117 "communication devices" [<a href="#ref-1" title="&quot;Small Computer System Interface - 2&quot;">1</a>].
118
119 The standard defines three message types capable of carrying a
120 general-purpose payload across communication devices. Each of these
121 are known as the "SEND MESSAGE" message type, but the size and and
122 structure of the message header differs amongst them. The three
123 forms of message header are six (6), ten (10) and twelve (12) bytes
124 long.
125
126 It was decided that the ten byte header offers the greatest
127 flexibility for encapsulating version 4 IP datagrams for the
128 following reasons:
129
130 a. The transfer length field is 16 bits in size which is perfectly
131 matched to the datagram length field in IP version 4.
132 Implementations of IP will run efficiently as datagrams will
133 never be fragmented over SCSI networks.
134
135 b. The SCSI "stream select" field, which was designed to permit
136 a device to specify the stream of data to which a block
137 belongs, may be used to encode the payload type (in a similar
138 manner to the Ethernet frame type field). For consistency, the
139 lowest four bits of the "stream select" field should match the
140 set of values assigned by the IEEE for Ethernet protocol types.
141
142 Encapsulating an IP datagram within a SCSI message is
143 straightforward:
144
145 +------------------+-----------------------------------+
146 | SCSI header | IP datagram |
147 +------------------+-----------------------------------+
148
149 The fields of the SCSI header should be completed as follows:
150
151 Byte 0: 0x2A (SEND_MESSAGE(10) opcode)
152 Byte 1: Logical unit number encoded into top 3 bits | 0x00
153 Byte 2: 0x00
154 Byte 3: 0x00
155 Byte 4: 0x00
156 Byte 5: Protocol type encoded into lowest 4 bits | 0x00
157 Byte 6: 0x00
158 Bytes 7/8: IP datagram length, big endian representation
159 Byte 9: 0x00
160
161
162
163
164 <span class="grey">Elliston Experimental [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2143">RFC 2143</a> Encapsulating IP with the SCSI May 1997</span>
167
168
169 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. An Address Resolution Protocol</span>
170
171 When IP decides that the next hop for a datagram will be onto a SCSI
172 network supported by a SCSI IP network interface implementation, it
173 is necessary to acquire a data link address to deliver the datagram.
174
175 Network interfaces such as Ethernet have well-known methods for
176 acquiring the media address for an Internet protocol address, the
177 most common being the Address Resolution Protocol (ARP). In existing
178 implementations, the forwarding host "yells" using a broadcast media
179 address and expects the named host to respond.
180
181 The SCSI protocol does not provide a broadcast data link address. An
182 acceptable solution to the address resolution problem for a SCSI
183 network is to simulate a broadcast by performing a series of round-
184 robin transmissions to each target. Depending on the SCSI protocol
185 being used, this would require upward of seven independent bus
186 accesses. This is not grossly inefficient, however, if combined with
187 an effective ARP caching policy. A further possible optimisation is
188 negative ARP caching, whereby incomplete ARP bindings are not queried
189 for some period in the future.
190
191 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Scalability</span>
192
193 While the utility of a network architecture based around a bus
194 network which can span less than ten metres and support only eight
195 hosts may be questionable, the flexibility of IP and in particular,
196 IP routing, improves the scalability of this architecture.
197
198 Consider a network of eight hosts connected to a SCSI bus in which
199 each host acts as a multi-homed host with a second host adapter
200 connecting another seven hosts to it. When configured with IP packet
201 routing capability, each of the 64 total hosts may communicate with
202 one another at high speed in a packet switched manner.
203
204 Depending on the I/O bus capabilities of certain workstations, it may
205 also be possible to configure a multi-homed host with a greater
206 number of SCSI host adapters, permitting centralised star
207 configurations to be constructed.
208
209 It should be apparent that for little expense, massively parallel
210 virtual machines can be built based upon the IP protocol running over
211 the high-bandwidth SCSI protocol.
212
213
214
215
216
217
218
219
220 <span class="grey">Elliston Experimental [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2143">RFC 2143</a> Encapsulating IP with the SCSI May 1997</span>
223
224
225 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Possible Applications</span>
226
227 Research has been made into the capability of "networks of
228 workstations", and their performance compared to supercomputers. An
229 observation that has been made thus far is that bottlenecks exist in
230 the channels by which executable code is transported between hosts
231 for execution. A very high-speed network architecture based around
232 the Internet protocol would permit a seamless transition of existing
233 application software to a high-bandwidth environment.
234
235 Other applications that have been considered are server clusters for
236 fault-tolerant NFS, World-Wide Web and database services.
237
238 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
239
240 Transmitting IP datagrams across a SCSI bus raises similar security
241 issues to other local area networking architectures. The scale of
242 security problems relating to protocols above the data link layer
243 should be obvious to a reader current in Internet security.
244
245 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. References</span>
246
247 [<a id="ref-1">1</a>] ANSI X3T9 Technical Committee, "Small Computer System
248 Interface - 2", X3T9.2, Project 375D, Revision 10L, September
249 1993.
250
251 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Author's Address</span>
252
253 Ben Elliston
254 Compucat Research Pty Limited
255 Box 7305 Canberra Mail Centre
256 Canberra ACT 2610
257 Australia
258
259 Phone: +61 6 295 1331
260 Fax: +61 6 295 1855
261 Email: [email protected]
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276 Elliston Experimental [Page 5]
277 </pre>