RFC 1223 (rfc1223) - Page 2 of 12
OSI CLNS and LLC1 protocols on Network Systems HYPERchannel
Alternative Format: Original Text Document
RFC 1223 OSI and LLC1 on HYPERchannel May 1991
2. To describe how multicast protocols such as ES-IS and IS-IS shall
operate over HYPERchannel. As a medium, HYPERchannel does not
support either broadcast or multicast. Therefore, special
techniques are needed to handle these protocols. Note that these
techniques do not allow general multicast, although any specific
problem may be solved by a generalization of these methods.
3. To make use of a standardized "message type" field in bytes
8 and 9 of the HYPERchannel network message. To permit better
interoperability, NSC maintains a "network protocol registry"
where any interested party may obtain a unique value in byte 8
(or bytes 8 and 9) for their own public, private, commercial or
proprietary protocol. Lists of assigned protocol type numbers
and their "owners" would be periodically published by NSC and
are available to interested parties.
HYPERchannel Network Messages
Unlike most datagram delivery systems, the HYPERchannel network
message consists of two parts:
Message Proper
+--------------------+
| |
| |
| |
| 16-64 bytes |
| |
| |
| |
+--------------------+
Associated Data
+----------------------------------------------------+
| |
| |
| |
| |
| |
| |
| Unlimited length |
| |
| |
| |
| |
| |
| |
+----------------------------------------------------+
Halpern