Browse Prior Art Database

CRONUS Virtual Local Network (RFC0824)

IP.com Disclosure Number: IPCOM000003872D
Original Publication Date: 1982-Aug-25
Included in the Prior Art Database: 2000-Sep-13
Document File: 29 page(s) / 56K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W.I. MacGregor: AUTHOR [+2]

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

DOS-26 Rev A Virtual Local Network

RFC 824

THE CRONUS VIRTUAL LOCAL NETWORK

William I. MacGregor

Daniel C. Tappan

Bolt Beranek and Newman Inc.

25 August 1982

[The purpose of this note is to describe the CRONUS Virtual

Local Network, especially the addressing related features.

These features include a method for mapping between Internet

Addresses and Local Network addresses. This is a topic of

current concern in the ARPA Internet community. This note is

intended to stimulate discussion. This is not a specification

of an Internet Standard.]

1 Purpose and Scope

This note defines the Cronus (1) Virtual Local Network

(VLN), a facility which provides interhost message transport to

the Cronus Distributed Operating System. The VLN consists of a

'client interface specification' and an 'implementation'; the

client interface is expected to be available on every Cronus

host. Client processes can send and receive datagrams using

specific, broadcast, or multicast addressing as defined in the

interface specification.

_______________

(1) The Cronus Distributed Operating System is being designed by

Bolt Beranek and Newman Inc., as a component of the Distributed

Systems Technology Program sponsored by Rome Air Development

Center. This work is supported by the DOS Design/Implementation

contract, F30602-81-C-0132.

1

DOS-26 Rev A Virtual Local Network

RFC 824

From the viewpoint of other Cronus system software and

application programs, the VLN stands in place of a direct

interface to the physical local network (PLN). This additional

level of abstraction is defined to meet two major system

objectives:

* COMPATIBILITY. The VLN defines a communication facility

which is compatible with the Internet Protocol (IP)

developed by DARPA; by implication the VLN is compatible

with higher-level protocols such as the Transmission Control

Protocol (TCP) based on IP.

* SUBSTITUTABILITY. Cronus software built above the VLN is

dependent only upon the VLN interface and not its

implementation. It is possible to substitute one physical

local network for another in the VLN implementation,

provided that the VLN interface semantics are maintained.

(This note assumes the reader is familiar with the concepts

and terminology of the DARPA Internet Program; reference [6] is a

compilation of the important protocol specifications and other

documents. Documents in [6] of special significance here are [5]

and [4].)

The compatibility goal is motivated by fact...