Debian Codegraph @

rfc2067.html

raw
1 <pre>Network Working Group J. Renwick
2 Request for Comments: 2067 NetStar, Inc.
3 Category: Standards Track January 1997
4 Obsoletes: <a href="./rfc1374">1374</a>
5
6
7 <span class="h1">IP over HIPPI</span>
8
9 Status of This Memo
10
11 This document specifies an Internet standards track protocol for the
12 Internet community, and requests discussion and suggestions for
13 improvements. Please refer to the current edition of the "Internet
14 Official Protocol Standards" (STD 1) for the standardization state
15 and status of this protocol. Distribution of this memo is unlimited.
16
17 Abstract
18
19 ANSI Standard X3.218-1993 (HIPPI-LE[3]) defines the encapsulation of
20 IEEE 802.2 LLC PDUs and, by implication, IP on HIPPI. ANSI X3.222-
21 1993 (HIPPI-SC[4]) describes the operation of HIPPI physical
22 switches. The ANSI committee responsible for these standards chose
23 to leave HIPPI networking issues largely outside the scope of their
24 standards; this document describes the use of HIPPI switches as IP
25 local area networks.
26
27 This memo is a revision of <a href="./rfc1374">RFC 1374</a>, "IP and ARP on HIPPI", and is
28 intended to replace it in the Standards Track. <a href="./rfc1374">RFC 1374</a> has been a
29 Proposed Standard since November, 1992, with at least 10
30 implementations of IP encapsulation and HIPPI switch discipline. No
31 major changes to it are required. However, the ARP part of <a href="./rfc1374">RFC 1374</a>
32 has not had sufficient implementation experience to be advanced to
33 Draft Standard. The present document contains all of <a href="./rfc1374">RFC 1374</a> except
34 for the description ARP, which has been moved into a separate
35 document.
36
37 TABLE OF CONTENTS
38
39 <a href="#section-1">1</a> Introduction............................................. <a href="#page-2">2</a>
40 <a href="#section-2">2</a> Scope.................................................... <a href="#page-3">3</a>
41 <a href="#section-2.1">2.1</a> Changes from <a href="./rfc1374">RFC 1374</a>.............................. <a href="#page-3">3</a>
42 <a href="#section-2.2">2.2</a> Terminology........................................ <a href="#page-4">4</a>
43 <a href="#section-3">3</a> Definitions.............................................. <a href="#page-4">4</a>
44 <a href="#section-4">4</a> Equipment................................................ <a href="#page-5">5</a>
45 <a href="#section-5">5</a> Protocol ................................................ <a href="#page-7">7</a>
46 <a href="#section-5.1">5.1</a> Packet Format...................................... <a href="#page-7">7</a>
47 <a href="#section-5.2">5.2</a> 48 bit Universal LAN MAC addresses................. <a href="#page-11">11</a>
48 <a href="#section-5.3">5.3</a> I-Field Format..................................... <a href="#page-12">12</a>
49
50
51
52 <span class="grey">Renwick Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
55
56
57 <a href="#section-5.4">5.4</a> Rules For Connections.............................. <a href="#page-13">13</a>
58 <a href="#section-5.5">5.5</a> MTU................................................ <a href="#page-15">15</a>
59 <a href="#section-6">6</a> Camp-on ................................................. <a href="#page-16">16</a>
60 <a href="#section-7">7</a> Path MTU Discovery....................................... <a href="#page-17">17</a>
61 <a href="#section-8">8</a> Channel Data Rate Discovery.............................. <a href="#page-17">17</a>
62 <a href="#section-9">9</a> Performance.............................................. <a href="#page-18">18</a>
63 <a href="#section-10">10</a> Sharing the Switch....................................... <a href="#page-20">20</a>
64 <a href="#section-11">11</a> References............................................... <a href="#page-21">21</a>
65 <a href="#section-12">12</a> Security Considerations.................................. <a href="#page-21">21</a>
66 <a href="#section-13">13</a> Author's Address......................................... <a href="#page-21">21</a>
67 <a href="#section-14">14</a> <a href="#appendix-A">Appendix A</a> -- HIPPI Basics............................... <a href="#page-22">22</a>
68 <a href="#section-15">15</a> <a href="#appendix-B">Appendix B</a> -- How to Build a Practical HIPPI LAN......... <a href="#page-27">27</a>
69
70 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a> Introduction</span>
71
72 The ANSI High-Performance Parallel Interface (HIPPI) is a simplex
73 data channel. Configured in pairs, HIPPI can send and receive data
74 simultaneously at nearly 800 megabits per second. (HIPPI has an
75 equally applicable 1600 megabit/second option.) Between 1987 and
76 1991, the ANSI X3T9.3 HIPPI working group drafted four documents that
77 bear on the use of HIPPI as a network interface. They cover the
78 physical and electrical specification (HIPPI-PH [<a href="#ref-1" title="High-Performance Parallel Interface - Mechanical">1</a>]), the framing of
79 a stream of bytes (HIPPI-FP [<a href="#ref-2">2</a>]), encapsulation of IEEE 802.2 LLC
80 (HIPPI-LE [<a href="#ref-3">3</a>]), and the behavior of a standard physical layer switch
81 (HIPPI-SC [<a href="#ref-4">4</a>]). HIPPI-LE also implies the encapsulation of Internet
82 Protocol[5]. The reader should be familiar with the ANSI HIPPI
83 documents, copies of which are archived at the site "ftp.network.com"
84 in the directory "hippi", and may be obtained via anonymous FTP.
85
86 HIPPI switches can be used to connect a variety of computers and
87 peripheral equipment for many purposes, but the working group stopped
88 short of describing their use as Local Area Networks. This memo
89 takes up where the working group left off, using the guiding
90 principle that except for length and hardware header, Internet
91 datagrams sent on HIPPI should be identical to the same datagrams
92 sent on a conventional network, and that any datagram sent on a
93 conventional 802 network[6] should be valid on HIPPI.
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Renwick Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
111
112
113 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a> Scope</span>
114
115 This memo describes the HIPPI interface between a host and a
116 crosspoint switch that complies with the HIPPI-SC draft standard.
117 Issues that have no impact on host implementations are outside the
118 scope of this memo. Host implementations that comply with this memo
119 are believed to be interoperable on a network composed of a single
120 HIPPI-SC switch. They are also interoperable on a simple point-to-
121 point, two-way HIPPI connection with no switch between them. They
122 may be interoperable on more complex networks as well, depending on
123 the internals of the switches and how they are interconnected;
124 however, these details are implementation dependent and outside the
125 scope of this memo.
126
127 Within the scope of this memo are:
128
129 1. Packet format and header contents, including HIPPI-FP, HIPPI-
130 LE, IEEE 802.2 LLC[7] and SNAP.
131
132 2. I-Field contents
133
134 3. Rules for the use of connections.
135
136 Outside of the scope are
137
138 1. Address Resolution (ARP)
139
140 2. Network configuration and management
141
142 3. Host internal optimizations
143
144 4. The interface between a host and an outboard protocol
145 processor.
146
147 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Changes from <a href="./rfc1374">RFC 1374</a></span>
148
149 <a href="./rfc1374">RFC 1374</a> described the use of ARP on HIPPI, but because of
150 insufficient implementation experience, the description of ARP has
151 been separated from IP encapsulation and moved to an Informational
152 memo. It may be returned to the standards track in the future if
153 interest and implementations warrant it.
154
155
156
157
158
159
160
161
162
163
164 <span class="grey">Renwick Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
167
168
169 <a href="./rfc1374">RFC 1374</a>'s specification of IP over HIPPI has been changed in this
170 document. Certain packet format options, permitted in <a href="./rfc1374">RFC 1374</a>, are
171 no longer allowed:
172
173 1. Optional short burst first;
174
175 2. D1 fill bytes;
176
177 3. Nonzero D2 offset.
178
179 That is, the header format is no longer variable and is required to
180 be that which is recommended by <a href="./rfc1374">RFC 1374</a>.
181
182 With these changes, it is possible to send packets which conform to
183 the ANSI standards but not to this memo. Because there are no <a href="./rfc1374">RFC</a>
184 <a href="./rfc1374">1374</a> implementations in use that used these options, we believe that
185 all existing <a href="./rfc1374">RFC 1374</a> implementations are compliant with the
186 requirements of this memo, and there should be no interoperability
187 problems associated with these changes.
188
189 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Terminology</span>
190
191 In this document the use of the word SHALL in capital letters
192 indicates mandatory points of compliance.
193
194 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a> Definitions</span>
195
196 Conventional
197
198 Used with respect to networks, this refers to Ethernet, FDDI and
199 802 LAN types, as distinct from HIPPI-SC LANs.
200
201 Destination
202
203 The HIPPI implementation that receives data from a HIPPI Source.
204
205 Node
206
207 An entity consisting of one HIPPI Source/Destination pair that is
208 connected by parallel or serial HIPPI to a HIPPI-SC switch and
209 that transmits and receives IP datagrams. A node may be an
210 Internet host, bridge, router or gateway. This memo uses the term
211 node in place of the usual "host" to indicate that a host might be
212 connected to the HIPPI LAN not directly, but through an external
213 adaptor that does some of the protocol processing for the host.
214
215
216
217
218
219
220 <span class="grey">Renwick Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
223
224
225 Serial HIPPI
226
227 An implementation of HIPPI in serial fashion on coaxial cable or
228 optical fiber, informally standardized by implementor's agreement
229 in the Spring of 1991.
230
231 Switch Address
232
233 A value used as the address of a node on a HIPPI-SC network. It
234 is transmitted in the I-field. HIPPI-SC switches may map Switch
235 Addresses to physical port numbers.
236
237 Source
238
239 The HIPPI implementation that generates data to send to a HIPPI
240 Destination.
241
242 Universal LAN Address (ULA)
243
244 A 48 bit globally unique address, administered by the IEEE,
245 assigned to each node on an Ethernet, FDDI, 802 network or HIPPI-
246 SC LAN.
247
248 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a> Equipment</span>
249
250 A HIPPI network can be composed of nodes with HIPPI interfaces, HIPPI
251 cables or serial links, HIPPI-SC switches, gateways to other
252 networks.
253
254 Each HIPPI interconnection between a node and a switch SHALL consist
255 of a pair of HIPPI links, one in each direction.
256
257 If a link between a node and the switch is capable of the 1600
258 Megabit/second data rate option (i.e. Cable B installed for 64 bit
259 wide operation) in either direction, the node's HIPPI-PH
260 implementation SHALL also be capable of 32 bit operation (Cable B
261 data suppressed) and SHALL be able to select or deselect the 1600Mb/s
262 data rate option at the establishment of each new connection.
263
264
265
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Renwick Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
279
280
281 The following figure shows a sample HIPPI switch configuration.
282
283 +-----+
284 | H 4 |
285 | +--+--+
286 | +----+ +----+ +----+ |
287 | | H1 | | H2 | | H3 | +-++
288 | +--+ +-++-+ +-++-+ +-++-+ |PP|
289 +---+H5| || || || ++++
290 | +--+ || || || ||
291 | +---++--------++--------++------++----+
292 | | |
293 | +----+ | HIPPI-SC |
294 +---+ G1 +--------+ |
295 | | +--------+ Switch |
296 | +----+ | |
297 | +---++--------++--------++------++----+
298 | +--+ || || || ||
299 +---+H6| || ++++
300 | +--+ +-++-+ |PP|
301 | | | +-++
302 | | G2 | |
303 | | | +--+--+
304 | +--+-+ | H 7 |
305 | | +-----+
306 |
307 -----+------------+-------+-----------+-------------+------
308 | | | |
309 | | | |
310 +--+--+ +--+--+ +--+--+ +--+--+
311 | H 8 | | H 9 | | H10 | | H11 |
312 +-----+ +-----+ +-----+ +-----+
313
314 Legend: ---+---+---+-- = 802 network, Ethernet or FDDI
315 || = Paired HIPPI link
316 H = Host computer
317 PP = Outboard Protocol Processor
318 G = Gateway
319
320 A possible HIPPI configuration
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Renwick Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
335
336
337 A single HIPPI-SC switch has a "non-blocking" characteristic, which
338 means there is always a path available from any Source to any
339 Destination. If the network consists of more than one switch, the
340 path from a Source to a Destination may include a HIPPI link between
341 switches. If this link is used by more than one Source/Destination
342 pair, a "blocking" network is created: one Source may be blocked from
343 access to a Destination because another Source is using the link it
344 shares. Strategies for establishing connections may be more
345 complicated on blocking networks than on non-blocking ones.
346
347 This memo does not take blocking issues into account, assuming that
348 the HIPPI LAN consists of one HIPPI-SC switch or, if the network is
349 more complex than that, it presents no additional problems that a
350 node must be aware of.
351
352 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a> Protocol</span>
353
354 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Packet Format</span>
355
356 The HIPPI packet format for Internet datagrams SHALL conform to the
357 HIPPI-FP and HIPPI-LE draft standards, with further restrictions as
358 imposed by this memo. Because this memo is more restrictive than the
359 ANSI standards, it is possible to send encapsulated IP datagrams that
360 conform to the ANSI standards, but are illegal according to this
361 memo. Destinations may either accept or ignore such datagrams.
362
363 To summarize the additional restrictions on ANSI standards found
364 here:
365
366 Any short burst must be the last burst of the packet.
367 Leading short bursts are not permitted.
368
369 Nonzero values for the HIPPI-FP D2_Offset field are not
370 permitted.
371
372 The D1_AreaSize SHALL be 3 (64-bit words). No D1 Fill is
373 permitted.
374
375 Note: Although this document is for IP over HIPPI, the encapsulation
376 described below accommodates ARP as well.
377
378 The HIPPI-FP D1_Area SHALL contain the HIPPI-LE header. The HIPPI-FP
379 D2_Area, when present, SHALL contain one IEEE 802.2 Type 1 LLC
380 Unnumbered Information (UI) PDU. Support of IEEE 802.2 XID, TEST and
381 Type 2 PDUs is not required on HIPPI, and Destinations that receive
382 these PDUs may either ignore them or respond correctly according to
383 IEEE 802.2 requirements.
384
385
386
387
388 <span class="grey">Renwick Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
391
392
393 The length of a HIPPI packet, including trailing fill, SHALL be a
394 multiple of eight bytes as required by HIPPI-LE.
395
396 +----------+-----------+---------------------+----------- ------+
397 | | | | 0 - 7 |
398 | HIPPI-FP | HIPPI-LE | IEEE 802.2 LLC/SNAP | IP . . . bytes |
399 |(8 bytes) |(24 bytes) | (8 bytes) | fill |
400 +----------+-----------+---------------------+----------- ------+
401
402 HIPPI Packet Structure
403
404 ULP-id (8 bits) SHALL contain 4.
405
406 D1_Data_Set_Present (1 bit) SHALL be set.
407
408 Start_D2_on_Burst_Boundary (1 bit) SHALL be zero.
409
410 Reserved (11 bits) SHALL contain zero.
411
412 D1_Area_Size (8 bits) SHALL be sent as 3.
413
414 D2_Offset (3 bits) SHALL be zero.
415
416 D2_Size (32 bits) Shall contain the number of bytes in the
417 IEEE 802.2 LLC Type 1 PDU, or zero if no PDU is present. It
418 SHALL NOT exceed 65,288. This value includes the IEEE 802.2
419 LLC/SNAP header and the IP datagram. It does not include
420 trailing fill bytes. (See "MTU", below.)
421
422 HIPPI-LE Header
423
424 FC (3 bits) SHALL contain zero unless otherwise defined by local
425 administration.
426
427 Double_Wide (1 bit) SHALL contain one if the Destination associated
428 with the sending Source supports 64 bit HIPPI operation. Otherwise
429 it SHALL contain zero.
430
431 Message_Type (4 bits) contains a code identifying the type of HIPPI-
432 LE PDU. Defined values are:
433
434 0 Data PDU
435 1 Address Resolution Request PDU (AR_Request)
436 2 Address Resolution Response PDU (AR_Response)
437 3 Self Address Resolution Request PDU (AR_S_Request)
438 4 Self Address Resolution Response PDU (AR_S_Response)
439
440
441
442
443
444 <span class="grey">Renwick Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
447
448
449 Destination_Switch_Address is a 24-bit field containing the
450 Switch Address of the Destination if known, otherwise zero.
451 If the address comprises less than 24 bits, it SHALL be right
452 justified (occupying the least significant bits) in the
453 field.
454
455 Destination_Address_Type (4 bits) and Source_Address_Type (4
456 bits) contain codes identifying the type of addresses in the
457 Destination_Switch_Address and Source_Switch_Address fields
458 respectively. Defined values (binary) are:
459
460 0 Unspecified
461 1 HIPPI-SC Source Route (24 bits)
462 2 HIPPI-SC Address (12 bits)
463
464 Source_Switch_Address is a 24-bit field containing the Switch
465 Address of the Source. If the address comprises less than 24
466 bits, it SHALL be right justified (occupying the least
467 significant bits) in the field.
468
469 Reserved (16 bits) SHALL contain zero.
470
471 Destination_IEEE_Address (48 bits) SHALL contain the 48 bit
472 Universal LAN MAC Address of the Destination if known,
473 otherwise zero.
474
475 LE_Locally_Administered (16 bits) SHALL contain zero UNLESS
476 otherwise defined by local administration.
477
478 Source_IEEE_Address (48 bits) SHALL contain the 48 bit
479 Universal LAN MAC Address of the Source if known, otherwise
480 zero.
481
482 IEEE 802.2 LLC
483
484 The IEEE 802.2 LLC Header SHALL begin in the first byte of the
485 HIPPI-FP D2_Area.
486
487 SSAP (8 bits) SHALL contain 170 ('AA'h).
488
489 DSAP (8 bits) SHALL contain 170 ('AA'h).
490
491 CTL (8 bits) SHALL contain 3 (Unnumbered Information).
492
493 SNAP
494
495 Organization Code (24 bits) SHALL be zero.
496
497
498
499
500 <span class="grey">Renwick Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
503
504
505 EtherType (16 bits) SHALL be set as defined in Assigned Numbers [<a href="#ref-8" title="&quot;Assigned Numbers&quot;">8</a>]:
506 IP = 2048 ('0800'h), ARP = 2054 ('0806'h), RARP = 32,821 ('8035'h).
507
508 31 28 23 21 15 10 7 2 0
509 +-----+---------+-+-+-----------+---------+-----+---------+-----+
510 0 | 04 |1|0| Reserved | 03 | 0 |
511 +---------------+-+-+---------------------+---------------+-----+
512 1 | (n+8) |
513 +-----+-+-------+-----------------------------------------------+
514 2 |[LA] |W|M_Type | Destination_Switch_Address |
515 +-----+-+-------+-----------------------------------------------+
516 3 | D_A_T | S_A_T | Source_Switch_Address |
517 +-------+-------+---------------+-------------------------------+
518 4 | Reserved | [Destination_IEEE_Address] |
519 +-------------------------------+ |
520 5 | |
521 +-------------------------------+-------------------------------+
522 6 | [LA] | [Source_IEEE_Address] |
523 +-------------------------------+ |
524 7 | |
525 +---------------+---------------+---------------+---------------+
526 8 | AA | AA | 03 | 00 |
527 +---------------+---------------+---------------+---------------+
528 9 | 00 | 00 | [EtherType] |
529 +---------------+---------------+---------------+---------------+
530 10 |Message byte 0 |Message byte 1 |Message byte 2 | . . . |
531 +---------------+---------------+---------------+--- |
532 | . . .
533 |
534 | -------+---------------+---------------+---------------+
535 | . . . | byte (n-2) | byte (n-1) | FILL |
536 +---------------+---------------+---------------+---------------+
537 N-1| FILL | FILL | FILL | FILL |
538 +---------------+---------------+---------------+---------------+
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556 <span class="grey">Renwick Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
559
560
561 HIPPI Packet Format
562
563 Words 0-1: HIPPI-FP Header
564 Words 2-7: D1 Area (HIPPI-LE Header)
565 Words 8-9: D2 Area (IEEE 802.2 LLC/SNAP)
566 Words 10-(N-1): D2 Area (IP message)
567 (n) is the number of bytes in the IP message.
568 [LA] fields are zero unless used otherwise locally.
569 Abbreviations: "W" = Double_Wide field;
570 "M_Type" = Message_Type field;
571 "D_A_T" = Destination_Address_Type;
572 "S_A_T" = Source_Address_Type;
573 [FILL] bytes complete the HIPPI packet to an even
574 number of 32 bit words. The number of fill bytes
575 is not counted in the data length.
576
577 IEEE 802.2 Data
578
579 The IEEE 802.2 Data SHALL begin in the byte following the EtherType
580 field. Fill bytes SHALL be used following the Data as necessary to
581 make the number of bytes in the packet a multiple of 8. In
582 accordance with HIPPI-FP, the amount of this fill is not included in
583 the D2_Size value in the HIPPI- FP Header.
584
585 The order of the bytes in the data stream is from higher numbered to
586 lower numbered data signal (left to right) within the HIPPI word, as
587 specified in HIPPI-FP Clause 7, "Word and byte formats." With the
588 1600 megabit/second data rate option (64 bit) bits 32 through 63 are
589 on Cable B, so that the four bytes on Cable B come logically before
590 those on Cable A. Within each byte, the most significant bit is the
591 highest numbered signal.
592
593 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> 48 bit Universal LAN MAC Addresses</span>
594
595 IEEE Standard 802.1A specifies the Universal LAN MAC Address. The
596 globally unique part of the 48 bit space is administered by the IEEE.
597 Each node on a HIPPI-SC LAN should be assigned a ULA. Multiple ULAs
598 may be used if a node contains more than one IEEE 802.2 LLC protocol
599 entity.
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Renwick Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
615
616
617 The format of the address within its 48 bit HIPPI-LE fields follows
618 IEEE 802.1A canonical bit order and HIPPI-FP bit and byte order:
619
620 31 23 15 7 0
621 +-------------------------------+---------------+---------------+
622 | (not used for ULA) |ULA byte 0 |L|G| ULA byte 1 |
623 +---------------+---------------+---------------+---------------+
624 | ULA byte 2 | ULA byte 3 | ULA byte 4 | ULA byte 5 |
625 +---------------+---------------+---------------+---------------+
626
627 Universal LAN MAC Address Format
628
629 L (U/L bit) = 1 for Locally administered addresses, 0 for
630 Universal.
631 G (I/G bit) = 1 for Group addresses, 0 for Individual.
632
633 The use of ULAs is optional, but encouraged. Although ULAs are not
634 used by HIPPI-SC switches, they may be helpful for HIPPI Switch
635 Address resolution, and for distinguishing between multiple logical
636 entities that may exist within one node. They may also be used by
637 gateway devices that replace HIPPI hardware headers with the MAC
638 headers of other LANs. Carrying the ULAs in the HIPPI header may
639 simplify these devices, and it may also help if HIPPI is used as an
640 interface to some future HIPPI based LAN that uses ULAs for
641 addressing.
642
643 <span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a> I-Field format</span>
644
645 fi The I-field bits, as defined in HIPPI-SC, SHALL be set as follows:
646
647 Locally Administered (bit 31) SHALL be zero.
648
649 Reserved (bits 30, 29) should be zero. Destinations SHALL
650 accept any value for these bits.
651
652 Double wide (bit 28) SHALL be set when Source Cable B is
653 connected and the Source wants a 64 bit connection. It SHALL
654 be zero otherwise.
655
656 Direction (bit 27) should be sent as zero, however
657 Destinations SHALL accept either zero or one and interpret
658 the Routing Control field accordingly, per HIPPI-SC.
659
660 Path Selection (bits 26, 25) SHALL be 00, 01, or 11 (binary)
661 at the Source's option. 00 (source route mode) indicates
662 that the I-field bits 23-00 contain a 24 bit source route; 01
663 or 11 (logical address mode) indicate that bits 23-00 contain
664 12 bit Source and Destination Addresses. The value 11 is
665
666
667
668 <span class="grey">Renwick Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
671
672
673 meaningful when more than one route exists from a Source to a
674 Destination; it allows the switch to choose the route. Use
675 of 01 forces the switch always to use the same route for the
676 same Source/Destination pair.
677
678 Camp-on (bit 24) may be 1 or 0; however, a Source SHALL NOT
679 make consecutive requests without Camp-on to the same
680 Destination while the requests are being rejected. The
681 purpose of this restriction is to prevent a node from
682 circumventing the fair share arbitration mechanism of the
683 switch by repeating requests at a very high rate.
684
685 If logical address mode is used:
686
687 Source Address (bits 23-12) is not used.
688
689 Destination Address (bits 11-0) SHALL contain the Switch
690 Address of the Destination.
691
692 If source route mode is used:
693
694 Routing control (bits 23-00) SHALL contain the route to
695 the Destination.
696
697 <span class="h3"><a class="selflink" id="section-5.4" href="#section-5.4">5.4</a> Rules For Connections</span>
698
699 The following rules for connection management by Source and
700 Destination are intended to insure frequent, fair share access to
701 Destinations for which multiple Sources are contending. If possible,
702 nodes should transfer data at full HIPPI speeds and hold connections
703 no longer than necessary.
704
705 A source may hold a connection for as long as it takes to send 68
706 HIPPI bursts at what ever speed the two connected nodes can achieve
707 together. The number of packets sent in one connection is not
708 limited, except that the number of bursts over all the packets should
709 not exceed 68. This is not a recommendation to send as many packets
710 as possible per connection; one packet per connection is acceptable.
711 The purpose of this limit is to give each Source an fair share of a
712 common Destination's bandwidth. Without a limit, if there is a
713 Destination that is constantly in demand by multiple Sources, the
714 Source that sends the most data per connection wins the greatest
715 share of bandwidth.
716
717 The limit of 68 bursts is not absolute. An implementation may check
718 the burst count after transmission of a packet and end the connection
719 if it is greater than or equal to some threshold. If this is done,
720 the threshold should be less than 68 depending on the typical packet
721
722
723
724 <span class="grey">Renwick Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
727
728
729 size, to ensure that the 68 burst limit is not normally exceeded.
730 For instance, a Source sending 64K packets would send two per
731 connection (130 bursts) if it checked for 68 at the end of each
732 packet. In this situation the Source is required to check for a
733 value small enough that it will not send a second packet in the same
734 connection.
735
736 Destinations SHALL accept all packets that arrive during a
737 connection, and may discard those that exceed its buffering capacity.
738 A Destination SHALL NOT abort a connection (deassert CONNECT) simply
739 because too many bursts were received; however a Destination may
740 abort a connection whose duration has exceeded a time period of the
741 Destination's choosing, as long as the Source is allowed ample time
742 to transmit its quota of bursts.
743
744 The rules admonish the node to do certain things as fast as it can,
745 however there is no absolute measure of compliance. Nodes that
746 cannot transfer data at full HIPPI speeds can still interoperate but
747 the faster the implementation, the better the performance of the
748 network will be.
749
750 Assuming that bursts flow at the maximum rate, the most important
751 factor in network throughput is the connection switching time,
752 measured from the deassertion of REQUEST by the Source at the end of
753 one connection to its first assertion of BURST after the
754 establishment of the new connection.
755
756 Implementations should keep this time as short as possible. For a
757 guideline, assuming parallel HIPPI and a single HIPPI-SC switch, ten
758 microseconds permits nearly full HIPPI throughput with full-sized
759 packets, and at 60 microseconds the available throughput is reduced
760 by about 10%. (See "Performance", below.)
761
762 All HIPPI electrical signaling SHALL comply with HIPPI-PH. In every
763 case, the following rules go beyond what HIPPI-PH requires.
764
765 Rules for the Source
766
767 1. Do not assert REQUEST until a packet is ready to send.
768
769 2. Transmit bursts as quickly as READYs permit. Except for
770 the required HIPPI Source Wait states, there should be no
771 delay in the assertion of BURST whenever the Source's READY
772 counter is nonzero.
773
774 3. Make a best effort to ensure that connection durations do
775 not exceed 68 bursts.
776
777
778
779
780 <span class="grey">Renwick Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
783
784
785 4. Deassert REQUEST immediately when no packet is available
786 for immediate transmission or the last packet of the
787 connection has been sent.
788
789 Rules for the Destination
790
791 1. Reject all connections if unable to receive packets.
792 This frees the requesting Source to connect to other
793 Destinations with a minimum of delay. Inability to receive
794 packets is not a transient condition, but is the state of the
795 Destination when its network interface is not initialized.
796
797 2. A HIPPI node should be prepared to efficiently accept
798 connections and process incoming data packets. While this
799 may be best achieved by not asserting connect unless 68
800 bursts worth of buffers is available, it may be possible to
801 meet this requirement with fewer buffers. This may be due to
802 a priori agreement between nodes on packet sizes, the speed
803 of the interface to move buffers, or other implementation
804 dependent considerations.
805
806 3. Accept a connection immediately when buffers are
807 available. The Destination should never delay the acceptance
808 of a connection unnecessarily.
809
810 4. Once initialized, a Destination may reject connection
811 requests only for one of the following reasons:
812
813 1. The I-field was received with incorrect parity.
814
815 2. The I-field contents are invalid, e.g. the "W" bit set when the
816 Destination does not support the 1600 megabit data rate option,
817 the "Locally Administered" bit is set, the Source is not
818 permitted to send to this Destination, etc.
819
820 Transient conditions within the Destination, such as temporary
821 buffer shortages, must never cause rejected connections.
822
823 5. Ignore aborted connection sequences. Sources may time
824 out and abandon attempts to connect; therefore aborted
825 connection sequences are normal events.
826
827 <span class="h3"><a class="selflink" id="section-5.5" href="#section-5.5">5.5</a> MTU</span>
828
829 Maximum Transmission Unit (MTU) is defined as the length of the IP
830 packet, including IP header, but not including any overhead below IP.
831 Conventional LANs have MTU sizes determined by physical layer
832 specification. MTUs may be required simply because the chosen medium
833
834
835
836 <span class="grey">Renwick Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
839
840
841 won't work with larger packets, or they may serve to limit the amount
842 of time a node must wait for an opportunity to send a packet.
843
844 HIPPI has no inherent limit on packet size. The HIPPI-FP header
845 contains a 32 bit D2_Size field that, while it may limit packets to
846 about 4 gigabytes, imposes no practical limit for networking
847 purposes. Even so, a HIPPI-SC switch used as a LAN needs an MTU so
848 that Destination buffer sizes can be determined.
849
850 The MTU for HIPPI-SC LANs is 65280 bytes.
851
852 This value was selected because it allows the IP packet to fit in one
853 64K byte buffer with up to 256 bytes of overhead. The overhead is 40
854 bytes at the present time; there are 216 bytes of room for expansion.
855
856 HIPPI-FP Header 8 bytes
857 HIPPI-LE Header 24 bytes
858 IEEE 802.2 LLC/SNAP Headers 8 bytes
859 Maximum IP packet size (MTU) 65280 bytes
860 ------------
861 Total 65320 bytes (64K - 216)
862
863 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a> Camp-on</span>
864
865 When several Sources contend for a single Destination, the Camp-on
866 feature allows the HIPPI-SC switch to arbitrate and ensure that all
867 Sources have fair access. (HIPPI-SC does not specify the method of
868 arbitration.) Without Camp-on, the contending Sources would simply
869 have to retry the connection repeatedly until it was accepted, and
870 the fastest Source would usually win. To guarantee fair share
871 arbitration, Sources are prohibited from making repeated requests to
872 the same Destination without Camp-on in such a way as to defeat the
873 arbitration.
874
875 There is another important reason to use Camp-on: when a connection
876 without Camp-on is rejected, the Source cannot determine whether the
877 rejection came from the requested Destination or from the switch.
878 The Source also cannot tell the reason for the rejection, which could
879 be either that the Destination was off line or not cabled, or the I-
880 field was erroneous or had incorrect parity. Sources should not
881 treat a rejection of a request without Camp-on as an error. Camp-on
882 prevents rejection due to the temporary busy case; with one
883 exception, rejection of a Camp-on request indicates an error
884 condition, and an error event can be recorded. The exception occurs
885 when a 64 bit connection is attempted to a Destination that does not
886 have Cable B connected, resulting in a reject. This case is covered
887 in "Channel Data Rate Discovery", below.
888
889
890
891
892 <span class="grey">Renwick Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
895
896
897 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a> Path MTU Discovery</span>
898
899 <a href="./rfc1191">RFC 1191</a> [<a href="#ref-9" title="&quot;Path MTU discovery&quot;">9</a>] describes the method of determining MTU restrictions on
900 an arbitrary network path between two hosts. HIPPI nodes may use
901 this method without modification to discover restrictions on paths
902 between HIPPI-SC LANs and other networks. Gateways between HIPPI-SC
903 LANs and other types of networks should implement <a href="./rfc1191">RFC 1191</a>.
904
905 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a> Channel Data Rate Discovery</span>
906
907 HIPPI exists in two data rate options (800 megabit/second and 1600
908 megabit/second). The higher data rate is achieved by making the
909 HIPPI 64 bits parallel instead of 32, using an extra cable containing
910 32 additional data bits and four parity bits. HIPPI-SC switches can
911 be designed to attach to both. Source and Destination HIPPI
912 implementations can be designed to operate at either rate, selectable
913 at the time a connection is established. The "W" bit (bit 28) of the
914 I-field controls the width of the connection through the switch.
915 Sources with both cables A and B attached to the switch may set the
916 "W" bit to request a 1600 megabit/second connection. If the
917 requested destination also has both cables attached, the switch can
918 connect Source to Destination on both cables. If the requested
919 Destination has only Cable A, the switch rejects the request.
920 Sixty-four bit Sources can connect to 32 bit Destinations by
921 requesting with the "W" bit clear and not using Cable B. Sixty-four
922 bit Destinations must examine the "W" bit in the received I-field and
923 use or ignore Cable B accordingly. Note that both INTERCONNECT
924 signals stay active while a 64 bit HIPPI is used in 32 bit mode.
925
926 The following table summarizes the possible combinations, the
927 switch's action for each, and the width of the resulting connection.
928
929 Destination
930 +-------------------+-------------------+
931 | 32 | 64 |
932 +----+-----+-------------------+-------------------+
933 | | W=0 | Accept 32 | Accept 32 |
934 | 32 +-----+-------------------+-------------------+
935 | | W=1 | N/A | N/A |
936 Source +----+-----+-------------------+-------------------+
937 | | W=0 | Accept 32 | Accept 32 |
938 | 64 +-----+-------------------+-------------------+
939 | | W=1 | Reject | Accept 64 |
940 +----+-----+-------------------+-------------------+
941
942
943
944
945
946
947
948 <span class="grey">Renwick Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
951
952
953 HIPPI Connection Combinations
954
955 If the path between a 64 bit Source and a 64 bit Destination includes
956 more than one switch, and the route between switches uses a link that
957 is only 32 bits wide, the switch rejects 64 bit connection requests
958 as if the Destination did not have 64 bit capability.
959
960 In a mixed LAN of 32 bit and 64 bit HIPPIs, a 64 bit Source needs to
961 know the data rates available at each Destination and on the path to
962 it. This can be known a priori by manual configuration, or it can be
963 discovered dynamically. The only reliable method of discovery is
964 simply to attempt a 64 bit connection with Camp-on. As long as 64
965 bit connections succeed, the Source knows the Destination and path
966 are double width. If a 64 bit connection is rejected, the Source
967 tries to connect for 32 bits. If the 32 bit connection succeeds, the
968 Source assumes that the Destination or path is not capable of double
969 width operation, and uses only 32 bit requests after that. If the 32
970 bit request is rejected, the Source assumes that the Destination or
971 path is down and makes no determination of its capability.
972
973 The Double_Wide bit in the HIPPI-LE header, if nonzero, gives the
974 node that receives it a hint that the 64 bit connection attempt may
975 be worthwhile when sending on the return path.
976
977 Note that Camp-on must be used at least in the 64 bit attempt,
978 because it removes some ambiguity from the meaning of rejects. If
979 the request is made with the "W" bit and no Camp-on, a reject could
980 mean either that the Destination has no Cable B or that it is simply
981 busy, and no conclusion can be drawn as to its status for 64 bit
982 connections.
983
984 <span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a> Performance</span>
985
986 The HIPPI connection rules are designed to permit best utilization of
987 the available HIPPI throughput under the constraint that each
988 Destination must be made available frequently to receive packets from
989 different Sources. This discipline asks both Sources and
990 Destinations to minimize connection setup overhead to deliver high
991 performance. Low connection setup times are easily achieved by
992 hardware implementations, but overhead may be too high if software is
993 required to execute between the initial request of a connection and
994 the beginning of data transfer. Hardware implementations in which
995 connection setup and data transfer proceed from a single software
996 action are very desirable.
997
998 HIPPI connections are controlled by HIPPI Sources; a Destination,
999 being unable to initiate a disconnect without the possibility of data
1000 loss, is a slave to the Source once it has accepted a connection.
1001
1002
1003
1004 <span class="grey">Renwick Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1007
1008
1009 Optimizations of connection strategy are therefore the province of
1010 the HIPPI Source, and several optimizations are permitted.
1011
1012 If the rate of available message traffic is less than the available
1013 HIPPI throughput and Destinations are seldom busy when a connection
1014 is requested, connection optimizations do not pay off and the
1015 simplest strategy of waiting indefinitely for each connection to be
1016 made and sending messages strictly in the order queued cannot be
1017 improved upon. However if some nodes are slow, or network
1018 applications can send or receive messages at a higher aggregate rate
1019 than the available HIPPI bandwidth, Sources may frequently encounter
1020 a busy Destination. In these cases, certain host output queuing
1021 strategies may enhance channel utilization. Sources may maintain
1022 separate output queues for different HIPPI Destinations, and abandon
1023 one Destination in favor of another if a connection attempt without
1024 Camp-on is rejected or a connection request with Camp-on is not
1025 accepted within a predetermined interval. Such a strategy results in
1026 aborted connection sequences (defined in HIPPI-PH: REQUEST is
1027 deasserted before any data is sent). Destinations must treat these
1028 as normal events, perhaps counting them but otherwise ignoring them.
1029
1030 Two components of connection setup time are out of the control of
1031 both Source and Destination. One is the time required for the switch
1032 to connect Source to Destination, currently less than four
1033 microseconds in the largest commercially available (32 port) switch.
1034 The second component is the round trip propagation time of the
1035 REQUEST and CONNECT signals, negligible on a standard 25 meter copper
1036 HIPPI cable, but contributing a total of about 10 microseconds per
1037 kilometer on fiber optic links. HIPPI-SC LANs spanning more than a
1038 few kilometers will have reduced throughput. Limited span networks
1039 with buffered gateways or bridges between them may perform better
1040 than long serial HIPPI links.
1041
1042 A Source is required to drop its connection after the transmission of
1043 68 HIPPI bursts. This number was chosen to allow the transmission of
1044 one maximum sized packet or a reasonable number of smaller sized
1045 packets. The following table lists some possibilities, with
1046 calculated maximum burst and throughput rates in millions (10**6) of
1047 bytes per second:
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Renwick Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1063
1064
1065 Maximum HIPPI Throughput Rates
1066
1067 Number Number Hold Burst ------Max throughput MB/sec-------
1068 User of of Time Rate Connection Setup Overhead (usec)
1069 Data Packets Bursts (usec) MB/sec 10 30 60 90 120 150
1070 ---- ------- ------ ------ ------ ---- ---- ---- ---- ---- ----
1071 63K 1 64 654 98.7 97.2 94.4 90.4 86.8 83.4 80.3
1072 32K 2 66 665 98.6 97.1 94.3 90.4 86.8 83.5 80.4
1073 16K 4 68 667 98.3 96.8 94.1 90.2 86.6 83.3 80.2
1074 8K 7 63 587 97.8 96.1 93.0 88.7 84.8 81.2 77.8
1075 4K 13 65 551 96.7 95.0 91.7 87.2 83.1 79.4 76.0
1076 2K 22 66 476 94.6 92.7 89.0 84.0 79.6 75.6 72.0
1077 1K 34 68 384 90.8 88.5 84.2 78.5 73.5 75.8 65.3
1078
1079 These calculations are based 259 40 ns clock periods to transmit a
1080 full burst and 23 clock periods for a short burst. (HIPPI-PH
1081 specifies three clock periods of overhead per burst.) A packet of "n"
1082 kilobytes of user data consists of "n" full bursts and one short
1083 burst equal in length to the number of bytes in the HIPPI, LLC, IP
1084 and TCP headers. "Hold Time" is the minimum connection duration
1085 needed to send the packets. "Burst Rate" is the effective transfer
1086 rate for the duration of the connection, not counting connection
1087 switching time. Throughput rates are in megabytes/second, accounting
1088 for connection switching times of 10, 30, 60, 90, 120 and 150
1089 microseconds. These calculations ignore any limit on the rate at
1090 which a Source or Destination can process small packets; such limits
1091 may further reduce the available throughput if small packets are
1092 used.
1093
1094 <span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a> Sharing the Switch</span>
1095
1096 Network interconnection is only one potential application of HIPPI
1097 and HIPPI-SC switches. While network applications need very frequent
1098 transient connections, other applications may favor longer term or
1099 even permanent connections between Source and Destination. Since the
1100 switch can serve each Source or Destination with hardware paths
1101 totally separate from every other, it is quite feasible to use the
1102 same switch to support LAN interconnects and computer/peripheral
1103 applications simultaneously.
1104
1105 Switch sharing is no problem when unlike applications do not share a
1106 HIPPI cable on any path. However if a host must use a single input
1107 or output cable for network as well as other kinds of traffic, or if
1108 a link between switches must be shared, care must be taken to ensure
1109 that all applications are compatible with the connection discipline
1110 described in this memo. Applications that hold connections too long
1111 on links shared with network traffic may cause loss of network
1112 packets or serious degradation of network service.
1113
1114
1115
1116 <span class="grey">Renwick Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a> References</span>
1122
1123 [<a id="ref-1">1</a>] ANSI X3.183-1991, High-Performance Parallel Interface -
1124 Mechanical, Electrical and Signalling Protocol Specification
1125 (HIPPI-PH).
1126
1127 [<a id="ref-2">2</a>] ANSI X3.210-1992, High-Performance Parallel Interface - Framing
1128 Protocol (HIPPI-FP).
1129
1130 [<a id="ref-3">3</a>] ANSI X3.218-1993, High-Performance Parallel Interface -
1131 Encapsulation of IEEE 802.2 (IEEE Std 802.2) Logical Link
1132 Control Protocol Data Units (802.2 Link Encapsulation) (HIPPI-
1133 LE).
1134
1135 [<a id="ref-4">4</a>] ANSI X3.222-1993, High-Performance Parallel Interface - Physical
1136 Switch Control (HIPPI-SC).
1137
1138 [<a id="ref-5">5</a>] Postel, J., "Internet Protocol", STD 5, <a href="./rfc791">RFC 791</a>, USC/Information
1139 Sciences Institute, September 1981.
1140
1141 [<a id="ref-6">6</a>] IEEE, "IEEE Standards for Local Area Networks: Logical Link
1142 Control", IEEE, New York, New York, 1985.
1143
1144 [<a id="ref-7">7</a>] IEEE, "IEEE Standards for Local Area Networks: Logical Link
1145 Control", IEEE, New York, New York, 1985.
1146
1147 [<a id="ref-8">8</a>] Reynolds, J.K., and Postel, J., "Assigned Numbers", STD 2, <a href="./rfc1340">RFC</a>
1148 <a href="./rfc1340">1340</a>, USC/Information Sciences Institute, July 1992.
1149
1150 [<a id="ref-9">9</a>] Mogul, J.C., and Deering, S.E., "Path MTU discovery", <a href="./rfc1191">RFC 1191</a>,
1151 Stanford University, November, 1990.
1152
1153 <span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a> Security Considerations</span>
1154
1155 Security issues are not discussed in this memo.
1156
1157 <span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a> Author's Address</span>
1158
1159 John K. Renwick
1160 NetStar, Inc.
1161 10250 Valley View Road
1162 Minneapolis, MN USA 55344
1163
1164 Phone: (612) 996-6847
1165 EMail: [email protected]
1166
1167 Mailing List: [email protected]
1168
1169
1170
1171
1172 <span class="grey">Renwick Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1175
1176
1177 <span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a> <a href="#appendix-A">Appendix A</a> -- HIPPI Basics</span>
1178
1179 This section is included as an aid to readers who are not completely
1180 familiar with the HIPPI standards.
1181
1182 HIPPI-PH describes a parallel copper data channel between a Source
1183 and a Destination. HIPPI transmits data in one direction only, so
1184 that two sets are required for bidirectional flow. The following
1185 figure shows a simple point-to-point link between two computer
1186 systems:
1187
1188 +----------+ +----------+
1189 | | | |
1190 | +--------+ +--------+ |
1191 | | HIPPI | Cable | HIPPI | |
1192 | | +---------------------&gt;| | |
1193 | | Source | | Dest. | |
1194 | System +--------+ +--------+ System |
1195 | X +--------+ +--------+ Y |
1196 | | HIPPI | Cable | HIPPI | |
1197 | | |&lt;---------------------+ | |
1198 | | Dest. | | Source | |
1199 | +--------+ +--------+ |
1200 | | | |
1201 +----------+ +----------+
1202
1203 A Simple HIPPI Duplex Link
1204
1205 Parallel copper cables may be up to 25 meters in length.
1206
1207 In this document, all HIPPI connections are assumed to be paired
1208 HIPPI channels.
1209
1210 HIPPI-PH has a single optional feature: it can use a single cable in
1211 each direction for a 32 bit parallel channel with a maximum data rate
1212 of 800 megabit/second, or two cables for 64 bits and 1600
1213 megabit/second. Cable A carries bits 0-31 and is used in both modes;
1214 Cable B carries bits 32-63 and is use only with the 1600
1215 megabit/second data rate option.
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Renwick Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1231
1232
1233 HIPPI Signal Hierarchy
1234
1235 HIPPI has the following hardware signals:
1236
1237 Source to Destination
1238
1239 INTERCONNECT A
1240 INTERCONNECT B (64 bit only)
1241 CLOCK (25 MHz)
1242 REQUEST
1243 PACKET
1244 BURST
1245 DATA (32 or 64 signals)
1246 PARITY (4 or 8 signals)
1247
1248 Destination to Source
1249
1250 INTERCONNECT A
1251 INTERCONNECT B (64 bit only)
1252 CONNECT
1253 READY
1254
1255 The INTERCONNECT lines carry DC voltages that indicate that the cable
1256 is connected and that the remote interface has power. INTERCONNECT
1257 is not used for signaling.
1258
1259 The CLOCK signal is a continuous 25 MHz (40 ns period) square wave.
1260 All Source-to-Destination signals are synchronized to the clock.
1261
1262 The REQUEST and CONNECT lines are used to establish logical
1263 connections. A connection is always initiated by a Source as it
1264 asserts REQUEST. At the same time it puts 32 bits of data on DATA
1265 lines 0-31, called the I-field. The Destination samples the DATA
1266 lines and can complete a connection by asserting CONNECT. Packets
1267 can be transmitted only while both REQUEST and CONNECT are asserted.
1268
1269 A Destination can also reject a connection by asserting CONNECT for
1270 only a short interval between 4 and 16 HIPPI clock periods (160-640
1271 nanoseconds). The Source knows a connection has been accepted when
1272 CONNECT is asserted for more than 16 clocks or it receives a READY
1273 pulse.
1274
1275 Either Source or Destination can terminate a connection by
1276 deasserting REQUEST or CONNECT, respectively. Normally connections
1277 are terminated by the Source after its last Packet has been sent. A
1278 Destination cannot terminate a connection without potential loss of
1279 data.
1280
1281
1282
1283
1284 <span class="grey">Renwick Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1287
1288
1289 +------+-------------------------+------+
1290 | Idle | Connected | Idle | . . .
1291 +------+-------------------------+------+
1292 / \
1293 / \
1294 / \
1295 / \
1296 / \
1297 +-------+ +-------+ +-------+ +-------+
1298 |I-field| |Packet | |Packet | |Packet |
1299 +-------+ +-------+ +-------+ +-------+
1300 / \
1301 / \
1302 / \
1303 / \
1304 / \
1305 / \
1306 / \
1307 +-----+ +-----+ +-----+
1308 |Burst| |Burst|...|Burst|
1309 +-----+ +-----+ +-----+
1310
1311 HIPPI Logical Framing Hierarchy
1312
1313 The Source asserts PACKET for the duration of a Packet transmission,
1314 deasserting it to indicate the end of a Packet. A sequence of Bursts
1315 comprise a Packet. To send a burst, a Source asserts the BURST
1316 signal for 256 clock periods, during which it places 256 words of
1317 data on the DATA lines. The first or last Burst of a Packet may be
1318 less than 256 clock periods, allowing the transmission of any
1319 integral number of 32 or 64 bit words in a Packet.
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Renwick Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1343
1344
1345 The READY signal is a pulse four or more clock periods long. Each
1346 pulse signals the Source that the Destination can receive one Burst.
1347 The Destination need not wait for a burst before sending another
1348 READY if it has burst buffers available; up to 63 unanswered READYs
1349 may be sent, allowing HIPPI to operate at full speed over distances
1350 of many kilometers. If a Source must wait for flow control, it
1351 inserts idle periods between Bursts.
1352
1353 +------------------------------------------------+
1354 REQUEST---+ +----
1355 +--------------------------------------------+
1356 CONNECT---------+ +--
1357 +---------------------------------------+
1358 PACKET-------------+ +----
1359
1360 +-+ +-+ +-+ +-+ +-+ +-+ +-+ +-+
1361 READY------------+ +---+ +---+ +---+ +---+ +---+ +---+ +---+ +--
1362
1363 +-------+ +-------+ +-------+ +-----+
1364 BURST--------------+ +-+ +-+ +-+ +--------
1365
1366 DATA------I-field----DATA------DATA------DATA-----DATA----------
1367
1368 HIPPI Signal Timing Diagram
1369
1370 Serial HIPPI
1371
1372 There is no ANSI standard for HIPPI other than the parallel copper
1373 cable version. However an implementors' agreement exists, specifying
1374 a serial protocol to extend HIPPI signals on optical fiber or coaxial
1375 copper cable. Serial links may be used interchangeably with parallel
1376 links to overcome HIPPI distance limitations; they are transparent to
1377 the Source and Destination, except for the possibility of longer
1378 propagation delays.
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Renwick Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1399
1400
1401 I-Field and Switch Control
1402
1403 The REQUEST, CONNECT and I-field features of HIPPI-PH were designed
1404 for the control of switches as described in HIPPI-SC. A switch is a
1405 hub with a number of input and output HIPPI ports. HIPPI Sources are
1406 cabled to switch input ports, and switch output ports are cabled to
1407 HIPPI Destinations. When a HIPPI Source requests a connection, the
1408 switch interprets the I-field to select an output port and
1409 electrically connects the HIPPI Source to the HIPPI Destination on
1410 that port. Once connected, the switch does not interact with the
1411 HIPPIs in any way until REQUEST or CONNECT is deasserted, at which
1412 time it breaks the physical connection and deasserts its output
1413 signals to both sides. Some existing switch implementations can
1414 switch connections in less than one microsecond. There is the
1415 potential for as many simultaneous connections, each transferring
1416 data at HIPPI speeds, as there are input or output ports on the
1417 switch. A switch offers much greater total throughput capacity than
1418 broadcast or ring media.
1419
1420 31 28 26 23 11 0
1421 +-+---+-+-+---+-+-----------------------+-----------------------+
1422 |L| |W|D|PS |C| Source Address | Destination Address |
1423 +-+---+-+-+---+-+-----------------------+-----------------------+
1424
1425 HIPPI-SC I-field Format (Logical Address Mode)
1426
1427 L = Locally defined (1 =&gt; entire I-field is locally defined)
1428 W = Width (1 =&gt; 64 bit connection)
1429 D = Direction (1 =&gt; swap Source and Destination Address)
1430 PS = Path Selection (01 =&gt; Logical Address Mode)
1431 C = Camp-on (1 =&gt; wait until Destination is free)
1432
1433 HIPPI-SC defines I-field formats for two different addressing modes.
1434 The first, called Source Routing, encodes a string of port numbers in
1435 the lower 24 bits. This string specifies a route over a number of
1436 switches. A Destination's address may differ from one Source to
1437 another if multiple switches are used.
1438
1439 The second format, called Logical Address Mode, defines two 12 bit
1440 fields, Source Address and Destination Address. A Destination's 12
1441 bit Switch Address is the same for all Sources. Switches commonly
1442 have address lookup tables to map 12 bit logical addresses to
1443 physical ports. This mode is used for networking.
1444
1445
1446
1447
1448
1449
1450
1451
1452 <span class="grey">Renwick Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1455
1456
1457 Control fields in the I-field are:
1458
1459 L The "Locally Defined" bit, when set, indicates that the I-field
1460 is not in the standard format. The meaning of bits 30-0 are
1461 locally defined.
1462
1463 W The Width bit, when set, requests a 64 bit connection through
1464 the switch. It is meaningless if Cable B is not installed at
1465 the Source. If W is set and either the Source or the requested
1466 Destination has no Cable B to the switch, the switch rejects
1467 the connection. Otherwise the switch connects both Cable A and
1468 Cable B if W is set, or Cable A only if W is clear. This
1469 feature is useful if both Source and Destination
1470 implementations can selectively disable or enable Cable B on
1471 each new connection.
1472
1473 D The Direction bit, when set, reverses the sense of the Source
1474 Address and Destination Address fields. In other words, D=1
1475 means that the Source Address is in bits 0-11 and the
1476 Destination Address is in bits 12-23. This bit was defined to
1477 give devices a simple way to route return messages. It is not
1478 useful for LAN operations.
1479
1480 PS The Path Selection field determines whether the I-field
1481 contains Source Route or Address information, and in Logical
1482 Address mode, whether the switch may select from multiple
1483 possible routes to the destination. The value "01" selects
1484 Logical Address mode and fixed routes.
1485
1486 C The Camp-on bit requests the switch not to reject the
1487 connection if the selected Destination is busy (connected to
1488 another Source) but wait and make the connection when the
1489 Destination is free.
1490
1491 <span class="h2"><a class="selflink" id="section-15" href="#section-15">15</a> <a href="#appendix-B">Appendix B</a> -- How to Build a Practical HIPPI LAN</span>
1492
1493 "IP on HIPPI" describes the network host's view of a HIPPI local area
1494 network without providing much information on the architecture of the
1495 network itself. Here we describe a network constructed from
1496 available HIPPI components, having the following characteristics:
1497
1498 1. A tree structure with a central HIPPI-SC compliant hub and
1499 optional satellite switches
1500
1501 2. Each satellite is connected to the hub by just one bidirectional
1502 HIPPI link.
1503
1504
1505
1506
1507
1508 <span class="grey">Renwick Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1511
1512
1513 3. Serial HIPPI or transparent fiber optic HIPPI extender devices
1514 may be used in any link.
1515
1516 4. Some satellites may be a particular switch product which is not
1517 HIPPI-SC compliant.
1518
1519 5. Host systems are attached either directly to the hub or to
1520 satellites, by single bidirectional links in which both HIPPI cables
1521 go to the same numbered switch port.
1522
1523 Switch Address Management
1524
1525 Switch addresses use a flat address space. The 12-bit address is
1526 subdivided into 6 bits of switch number and 6 bits of port number.
1527
1528 11 5 0
1529 +-----------------------+-----------------------+
1530 | Switch Number | Port Number |
1531 +-----------------------+-----------------------+
1532
1533 Logical Address Construction
1534
1535 Switches may be numbered arbitrarily. A given host's address
1536 consists of the number of the switch it is directly attached to and
1537 the physical port number on that switch to which its input channel is
1538 attached.
1539
1540 In the singly-connected tree structure, there is exactly one path
1541 between any pair of hosts. Since each satellite must be connected
1542 directly to the hub, the maximum length of this path is three hops,
1543 and the minimum length is one. Each HIPPI-SC compliant switch is
1544 programmed to map each of the host switch addresses to the
1545 appropriate output port: either the port to which the host is
1546 directly attached or a port that is linked to another switch in the
1547 path to it.
1548
1549 Special Treatment of Nonstandard Switches
1550
1551 There is one commercially available switch that was designed
1552 before the drafting of HIPPI-SC and is not fully compliant. It is
1553 in common use, so it is worth making some special provisions to
1554 allow its use in a HIPPI LAN. This switch supports only the
1555 Source Route mode of addressing with a four bit right shift that
1556 can be disabled by a hardware switch on each input port.
1557 Addresses cannot be mapped. The switch does not support the "W",
1558 "D", or "PS" fields of the I-field; it ignores their contents.
1559 Use of this switch as a satellite will require a slight deviation
1560 from normal I-field usage by the hosts that are directly attached
1561
1562
1563
1564 <span class="grey">Renwick Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1567
1568
1569 to it. Hosts attached to standard switches are not affected.
1570
1571 For a destination connected to a non compliant satellite, the
1572 satellite uses only the least significant four bits of the I-field
1573 as the address. Since the address contains the destination's
1574 physical port number in the least significant bits, its port will
1575 be selected. Nonstandard switches should be set to disable I-
1576 field shifting at the input from the hub, so that the destination
1577 host will see its correct switch address in the I-field when
1578 performing self-address discovery. I-field shifting must be
1579 enabled on the satellite for each input port to which a host is
1580 attached.
1581
1582 Hosts attached to nonstandard satellites must deviate from the
1583 normal I-field usage when connecting to hosts on another switch.
1584 It is suggested that all host implementations have this capability
1585 as long as the nonstandard switches remain in use. The host must
1586 know, by some manual configuration method, that it is connected to
1587 a nonstandard switch, and it must have its "link port" number;
1588 that is, the number of the port on the satellite that is connected
1589 to the hub.
1590
1591 The normal I-field format for a 32-bit connection, per the
1592 document, is this:
1593
1594 31 26 23 11 0
1595 +---------+---+-+-----------------------+-----------------------+
1596 |0 0 0 0 0|x 1|C| Unused | Destination Address |
1597 +---------+---+-+-----------------------+-----------------------+
1598
1599 The special I-field format is:
1600
1601 31 26 24 15 4 3 0
1602 +---------+---+-+---------------+-----------------------+-------+
1603 |0 0 0 0 0|x 1|C| Unused | Destination Address | Link |
1604 +---------+---+-+---------------+-----------------------+-------+
1605
1606 This I-field is altered by shifting the lower 24 bits left by four
1607 and adding the link port number. Camp-on is optional, and the PS
1608 field is set to 01 or 11 (the host's option) as if the switch
1609 supported logical address mode. All other I-field bits are set to
1610 zero. When the host requests a connection with this I-field, the
1611 switch selects a connection through the link port to the hub, and
1612 shifts the lower 24 bits of the I-field right by four bits. The link
1613 port number is discarded and the I-field passed through to the hub is
1614 a proper HIPPI-SC I-field selecting logical address mode.
1615
1616
1617
1618
1619
1620 <span class="grey">Renwick Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc2067">RFC 2067</a> IP over HIPPI January 1997</span>
1623
1624
1625 A host on a nonstandard satellite may use the special I-field format
1626 for all connection requests. If connecting to another host on the
1627 same satellite, this will cause the connection to take an
1628 unnecessarily long path through the hub and back. If an optimization
1629 is desired, the host can be given additional information to allow it
1630 to use the standard I-field format when connecting to another host on
1631 the same switch. This information could consist of a list of the
1632 other hosts on the same switch, or the details of address formation,
1633 along with the switch number of the local satellite, which would
1634 allow the host to analyze the switch address to determine whether or
1635 not the destination is on the local switch. This optimization is
1636 fairly complicated and may not always be worthwhile.
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676 Renwick Standards Track [Page 30]
1677 </pre>