RFC 2834 (rfc2834) - Page 2 of 34


ARP and IP Broadcast over HIPPI-800



Alternative Format: Original Text Document



RFC 2834          ARP and IP Broadcast over HIPPI-800           May 2000


       5.5 HARP and Permanent ARP Table Entries  . . . . . . . .  14
       5.6 HARP Table Aging  . . . . . . . . . . . . . . . . . .  14
   6.  HARP Message Encoding . . . . . . . . . . . . . . . . . .  15
       6.1 HIPPI-LE Header of HARP Messages  . . . . . . . . . .  15
           6.1.1 IEEE 802.2 LLC  . . . . . . . . . . . . . . . .  16
           6.1.2 SNAP  . . . . . . . . . . . . . . . . . . . . .  16
           6.1.3 Diagram . . . . . . . . . . . . . . . . . . . .  17
       6.2 HIPPI Hardware Address Formats and Requirements . . .  18
           6.2.1 48-bit Universal LAN MAC Addresses  . . . . . .  18
       6.3 HARP and InHARP Message Formats . . . . . . . . . . .  19
           6.3.1 Example Message encodings . . . . . . . . . . .  22
           6.3.2 HARP_NAK message format . . . . . . . . . . . .  22
           6.3.3 Combined HIPPI-LE and HARP message addresses  .  22
   7.  Broadcast and Multicast . . . . . . . . . . . . . . . . .  23
       7.1 Protocol for an IP Broadcast Emulation Server - PIBES  23
       7.2 IP Broadcast Address  . . . . . . . . . . . . . . . .  24
       7.3 IP Multicast Address  . . . . . . . . . . . . . . . .  24
       7.4 A Note on Broadcast Emulation Performance . . . . . .  24
   8.  HARP for Scheduled Transfer Protocol  . . . . . . . . . .  25
   9.  Discovery of One's Own Switch Address . . . . . . . . . .  25
   10. Security Considerations . . . . . . . . . . . . . . . . .  26
   11. Open Issues . . . . . . . . . . . . . . . . . . . . . . .  26
   12. HARP Examples . . . . . . . . . . . . . . . . . . . . . .  26
       12.1 Registration Phase of Client Y on Non-broadcast HW .  27
       12.2 Registration Phase of Client Y on Broadcast Hardware  28
       12.3 Operational Phase (phase II) . . . . . . . . . . . .  28
            12.3.1 Standard successful HARP_Resolve example  . .  29
            12.3.2 Standard non-successful HARP_Resolve example   30
   13. References  . . . . . . . . . . . . . . . . . . . . . . .  31
   14. Acknowledgments . . . . . . . . . . . . . . . . . . . . .  32
   15. Changes from RFC-1374 . . . . . . . . . . . . . . . . . .  32
   16. Author's Address  . . . . . . . . . . . . . . . . . . . .  33
   17. Full Copyright Statement  . . . . . . . . . . . . . . . .  34

1. Introduction

   The ANSI High-Performance Parallel Interface (HIPPI) is a dual
   simplex data channel.   HIPPI can send and receive data
   simultaneously at 800 or 1600 megabits per second. Between 1987 and
   1997, the ANSI X3T11.1 HIPPI working group (now known as NCITS T11.1)
   Standardized five documents that bear on the use of HIPPI as a
   network interface.  They cover the physical and electrical
   specification (HIPPI-PH [1]), the framing of a stream of bytes
   (HIPPI-FP [2]), encapsulation of IEEE 802.2 LLC (HIPPI-LE [3]), the
   behavior of a physical layer switch (HIPPI-SC [4]) and the physical-
   level and optical specification (HIPPI-Serial [5]).  HIPPI-LE also
   implies the encapsulation of Internet Protocol[5].  The reader should
   be familiar with the ANSI HIPPI documents. Approved ANSI NCITS



Pittet                      Standards Track