Xref: utzoo comp.os.vms:9263 comp.sys.dec:815
Path: utzoo!attcan!uunet!seismo!esosun!ucsdhub!jack!crash!jeh
From: jeh@crash.cts.com (Jamie Hanrahan)
Newsgroups: comp.os.vms,comp.sys.dec
Subject: Re: Information Needed on DECNet
Summary: Phase IV doc nums, plus info on Ethernet driver
Keywords: Ethernet DNA
Message-ID: <3508@crash.cts.com>
Date: 7 Oct 88 19:09:00 GMT
References: <312@cocktrice.uucp>
Reply-To: jeh@crash.CTS.COM (Jamie Hanrahan)
Organization: CMKRNL Press, San Diego, CA
Lines: 32

(The author of the referenced article wants to get a piece of equipment
with an Ethernet port talking to VMS, either through DECnet or more directly.)

I would favor the "more direct" approach.  You certainly can issue $QIOs to
VMS's Ethernet driver.  u!The program that does this, and your other equipment,
must agree on an Ethernet "protocol type" parameter to distinguish your
packets from DECnet, LAT, and all the other Ethernet packets also destined
from your machine.  

As you guessed, your other alternative is essentially to implement DNA
layers 3 through 7 in your other machine.  This would be a large job; I
don't recommend trying this at home. :-)  However, if you want to see what
would be involved, order the following:

Phase IV General Description AA-N149A-TC
4.0 DDCMP AA-D588A-TC
4.1 DDCMP AA-K176A-TK
1.0 Ethernet DL Func Spec AA-Y298A-TK
1.0 Ethernet Product Arch Spec AA-X440A-TK
2.0 Routing Layer Func Spec AA-X435A-TK
3.2 NSP Func Spec AA-K176A-TK
4.0 NSP Func Spec AA-X439A-TK
1.0 Session Control Func Spec AA-K182A-TK
5.6 DAP Func Spec AA-K177A-TK
2.0 NVT Foundation Services AA-DY89A-TK
2.0 NVT CTERM AA-DY88A-TK
4.0 Net Mgmt Func Spec AA-X437A-TK
3.0 MOP Func Spec AA-X436A-TK
2.0 Ethernet (the blue book) AA-K759B-TK

(The above list courtesy of a previous message in this newsgroup, sent
by Joel M. Snyder, jms@mis.arizona.edu .)