Subject: RE: draft-ietf-ip1394-dhcp-01.txt

From: "Henry, Mike" <[email-masked]>
Date: Thu, 8 Jul 1999 11:21:06 -0400 (EDT)

Kenji,

The UUID spec does not assume the device has an IEEE 802 address. It assumes
the UUID generator (the entity creating UUIDs for devices) uses an IEEE 802
address as a "spatially unique value". It is common for devices to be
assigned UUIDs based on the IEEE 802 address of the machine generating the
UUIDs. For example, in a manufacturing environment a single machine may
generate UUIDs for the devices being manufactured in much the same way that
serial numbers are created centrally and applied to each device.  The device
itself is not required to provide the seed (i.e. IEEE 802 address). This is
really not much different than the assumptions EUI-64 is built on.

 - Mike H.  7/6
----------------

> -----Original Message-----
> From: [email-masked] [mailto:[email-masked]]
> Sent: Wednesday, July 07, 1999 8:19 PM
> To: Multiple recipients of list
> Subject: Re: draft-ietf-ip1394-dhcp-01.txt 
> 
> 
> 
> >One MAY use a UUID Client ID for 1394 device.
> 
> This is true, but..
> http://www.opengroup.org/onlinepubs/9629399/apdxa.htm
> says,
> : This UUID specification assumes the availability of an IEEE 802
> : address. 
> 
> This will be a problem since TYPICAL IEEE1394 node does not have
> IEEE 802 address.
> 
> Kenji Fujisawa
>