IMHO, they _should_ be unique except for multicast addressing and uses
such as in HSRP/VRRP and such.   Network admins usually like to have
a firm grip concerning how traffic is routed.  They don't want traffic on
one segment/subnet getting routed to another.  IHMO, this is a vector
for viruses proliferation because the host vulnerable thinks that all
segments/subnets are the same.
I don't have the money to shell out for a copy of the IEEE 802.x standards, 
but I can quote some other folks on this:
RFC 826:
However, 48.bit Ethernet addresses are supposed to be unique and fixed for 
all time, so they shouldn't
change.
02.10Q: What is a MAC address?
A: It is  the unique hexadecimal serial number assigned to each Ether-
net  network device to identify it  on  the network.  With Ethernet
devices  (as  with  most other  network  types),  this  address  is
permanently set at  the time of manufacturer, though it can usually
be changed  through  software (though this is  generally a Very
Bad Thing to do).
02.11Q: Why must the MAC address to be unique?
A: Each card  has  a  unique MAC address,  so  that
it will be able to exclusively  grab  packets  off the wire
meant  for  it.   If  MAC addresses are not unique,  there is
no  way  to distinguish between two  stations.  Devices on the
network  watch  network traffic and look for their own MAC address
in each packet to determine whether they should decode  it or  not.
Special circumstances exist  for broadcasting to every device.
04.01Q: What is a "segment"?
A: A  piece of network wire bounded by bridges,  routers, repeaters or
terminators.
04.02Q: What is a "subnet"?
A: Another overloaded  term. It can  mean, depending on  the usage,  a
segment, a set of machines  grouped together by a specific protocol
feature  (note  that  these machines do not have to be on  the same
segment, but they could be) or a big  nylon  thing used  to capture
enemy subs.
-- timothy.covell@ashavan.org. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/