Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!rutgers!ucla-cs!zen!ucbvax!TOPAZ.RUTGERS.EDU!hedrick
From: hedrick@TOPAZ.RUTGERS.EDU (Charles Hedrick)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: IBM TCP.
Message-ID: <8708060434.AA15065@topaz.rutgers.edu>
Date: Thu, 6-Aug-87 00:34:59 EDT
Article-I.D.: topaz.8708060434.AA15065
Posted: Thu Aug  6 00:34:59 1987
Date-Received: Sat, 8-Aug-87 07:37:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 21

As far as I know, in phase V the DECnet address will consist of two
bytes of subnet and then the Ethernet address.  Once phase IV
compatibility is not needed (typically this would be at the next
phase), one could presumably stop using the special Ethernet address
forced on you by the phase IV DECnet design, and use the preassigned
Ethernet address.  So at that point, machines using DECnet would have
unique addresses.  

I think this discussion has diverged from its intent.  I was simply
trying to explain what was meant when someone said that machines
running DECnet did not have globally unique Ethernet addresses.  Your
comments about how DECnet addresses are assigned on your campus show
that there can't be any conflict in DECnet addresses at your
installation.  However the fact remains that your hosts no longer have
globally unique Ethernet addresses.  There are almost certainly at
least two hosts on the DEC corporate network with the same address
(since they have several DECnet networks each of which have very full
address space), and presumably some on other large corporate networks
as well.  This is not a criticism: obviously your machine will not
become confused with those other machines.  It is simply an
explanation of a statement in a previous posting.