[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [dhcwg] Re: DUID for mobile phones



 In your previous mail you wrote:

   It was very much the intention when writing the DUID description that  
   things like IMEIs and MEIDs should be usable as DUIDs.   I would  
   suggest using the DUID-EN format, and assigning an enterprise number  
   for each discrete type of mobile phone identifier, since each of  
   these has to be standardized and there are therefore a limited number  
   of them.

=> ETSI, 3GPP, 3GPP2, ..., are standardization bodies, not enterprises.
Even when ETSI has an enterprise number and could provide a spec about
using IMEIs in DUIDs, the issue is 3GPP/ETSI did a too good job
and now 3GPP2 ids, MEIDs, have a format compatible with EMEIs,
so IMHO the next solution is better.

   It would also be reasonable to just define new DUID  
   types.   This should be documented in a new standards-track document;  
   I would suggest that if you know of more than one id space, you  

=> IEEE EUI-64s are another example of IDs attached to harware which
become common (one per IEEE 1394 device for instance).

   document all the ones you know about in a single draft, and that  
   other participants in the WG who know of id spaces that you don't  
   know of participate in writing this draft.   I don't know anything  
   about mobile phone id spaces, so if I'm making this sound more  
   complicated than it needs to be, that's why.
   
=> I forgot to cite my I-D about IMEIs/MEIDs for IPv6 IIDs
(draft-dupont-ipv6-imei-08.txt), we can find all details and
references about them in it. To summary any 3G device has a built-in ID
in its hardware, the original purpose of this ID was to track stolen phones.

   It's my understanding that for phones that don't have a built-in  
   identifier,

=> you are wrong, the IMEI/MEID is attached to the phone itself.

   the identifier is on a little sim card that can be  
   swapped from phone to phone.

=> this is the IMSI and is per subscription. For obvious privacy concern,
it should not be published without caution. IMHO for a per subscriber ID
the phone number itself is better.

Regards

Francis.Dupont at enst-bretagne.fr

_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg