Internet Protocol on Network System's HYPERchannel: Protocol Specification
RFC 1044
Document | Type |
RFC - Internet Standard
(February 1988; No errata)
Updated by RFC 5494
Also known as STD 45
|
|
---|---|---|---|
Authors | |||
Last updated | 2013-03-02 | ||
Stream | Legacy | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | Legacy state | (None) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | RFC 1044 (Internet Standard) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group K. Hardwick Request for Comments: 1044 NSC J. Lekashman NASA-Ames GE February 1988 Internet Protocol on Network Systems HYPERchannel Protocol Specification STATUS OF THIS MEMO The intent of this document is to provide a complete discussion of the protocols and techniques used to embed DoD standard Internet Protocol datagrams (and its associated higher level protocols) on Network Systems Corporation's HYPERchannel [1] equipment. Distribution of this memo is unlimited. This document is intended for network planners and implementors who are already familiar with the TCP/IP protocol suite and the techniques used to carry TCP/IP traffic on common networks such as the DDN or Ethernet. No great familiarity with NSC products is assumed; an appendix is devoted to a review of NSC technologies and protocols. At the time of this first RFC edition, the contents of this document has already been reviewed by about a dozen vendors and users active in the use of TCP/IP on HYPERchannel media. Comments and suggestions are still welcome (and implementable,) however. Any comments or questions on this specification may be directed to: Ken Hardwick Director, Software Technology Network Systems Corporation MS029 7600 Boone Avenue North Brooklyn Park, MN 55428 Phone: (612) 424-1607 John Lekashman Nasa Ames Research Center. NAS/GE MS 258-6 Moffett Field, CA, 94035 lekash@orville.nas.nasa.gov Phone: (415) 694-4359 Hardwick & Lekashman [Page 1] RFC 1044 IP on Network Systems HYPERchannel February 1988 TABLE OF CONTENTS Status of this memo . . . . . . . . . . . . . . . . . . . . . . 1 Goals of this document . . . . . . . . . . . . . . . . . . . . 3 Basic HYPERchannel network messages . . . . . . . . . . . . . . 4 Basic (16-bit address) Message Proper header . . . . . . . . . 5 TO addresses and open driver architecture . . . . . . . . . . 7 Extended (32-bit address) Message Proper header . . . . . . . . 8 Address Recognition and message forwarding . . . . . . . . . . 10 32-bit message fields . . . . . . . . . . . . . . . . . . . . 12 Broadcasting . . . . . . . . . . . . . . . . . . . . . . . . . 14 PROTOCOL SPECIFICATION . . . . . . . . . . . . . . . . . . . . 17 Basic (16-bit) Message Encapsulation . . . . . . . . . . . . 18 Compatibility with existing implementations . . . . . . . . . . 21 Extended (32-bit) Message Encapsulation . . . . . . . . . . . 24 Address Resolution Protocol . . . . . . . . . . . . . . . . . 27 Maximum Transmission Unit . . . . . . . . . . . . . . . . . . . 31 ADDRESS RESOLUTION . . . . . . . . . . . . . . . . . . . . . . 32 Local Address Resolution . . . . . . . . . . . . . . . . . . . 33 Configuration file format . . . . . . . . . . . . . . . . . . 34 ARP servers . . . . . . . . . . . . . . . . . . . . . . . . . 35 Broadcast ARP . . . . . . . . . . . . . . . . . . . . . . . . 36 Appendix A. NSC Product Architecture and Addressing . . . . . . . . . . . . 38 Appendix B. Network Systems HYPERchannel protocols . . . . . . . . . . . . 42 Hardwick & Lekashman [Page 2] RFC 1044 IP on Network Systems HYPERchannel February 1988 GOALS OF THIS DOCUMENT In this document, there are four major technical objectives: 1. To bless a "de facto" standard for IP on HYPERchannel that has been implemented by Tektronix, Cray, NASA Ames, and others. We are attempting to resolve some interoperability problems with this standard so as to minimize the changes to existing IP on HYPERchannel software. If any ambiguities remain in the de facto standard, we wish to assist in their resolution. 2. To address larger networks, NSC's newer network products are moving to a 32-bit address from the current 16-bit TO address. This document would introduce the addressing extension to the user community and specify how IP datagrams would work in the new addressing mode. 3. To define an Address Resolution Protocol for HYPERchannel and other NSC products. It is probably well known that current NSC products do not support the broadcast modes that make ARP particularly useful. However, many have expressed interest in "ARP servers" at a known network address. These servers could fade away as NSC products with broadcast capability come intoShow full document text