Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!SUN.COM!melohn
From: melohn@SUN.COM (Bill Melohn)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: TCP/IP and DECnet
Message-ID: <8709290741.AA02129@sluggo.sun.com>
Date: Tue, 29-Sep-87 03:41:04 EDT
Article-I.D.: sluggo.8709290741.AA02129
Posted: Tue Sep 29 03:41:04 1987
Date-Received: Wed, 30-Sep-87 06:38:09 EDT
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14

Not true. Downline loading, upline dumping, and the remote console
utility are handled by MOP, the Maintenance Operations Protocol, yet
another Digital propriatary protocol that is NOT included under the
publically available DECnet suite. True, to provide a mapping between
LAT server names and their ethernet addresses they use the DECnet node
database, but this is purely an implementation convienence (since
their is no DNA equivalant of ARP).

The point I was making is that DECnet is a publically specified
interface for talking to DEC machines; however it does NOT include
terminal servers, VAX clusters, and many other protocols which Digital
considers propritary. I'm tired of explaining to customers why we
can't support DEC terminal servers, "since they run DECnet" (which we
can and do support under SunOS).