Browse Prior Art Database

Internet Protocol on Network System's HYPERchannel: Protocol specification (RFC1044)

IP.com Disclosure Number: IPCOM000001850D
Original Publication Date: 1988-Feb-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 33 page(s) / 94K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Hardwick: AUTHOR [+2]

Abstract

STATUS OF THIS MEMO

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 3% of the total text.

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

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 Addr...