In your previous mail you wrote:

  You can see the results in
 http://search.ietf.org/internet-drafts/draft-ietf-ipv6-3gpp-recommend-00.txt.
   
=> the 3GPP/IPv6 DT seems to ignore this ID issue...

   The problem with IMEIs are that they are used in GSM, GPRS, and
  UMTS networks to screen stolen handsets. This makes additional
  requirements for privacy, and confidentiality of the IMEI value.
   
=> I agree, the only usage of IMEI is to optionally look up the EIR
for stolen terminals. I can't see any additional requirements for
privacy and confidentiality? Can you explain? Do you afraid someone
can declare his stolen phone has your phone IMEI (telcos are not
so stupid, they check or are sued to death :-)?
The only point is when you steal an handset you'd like to change the IMEI
(so the IMEI should not easy to change :-).

   I had phone once that for some reason had a different IMEI
  electronically than what was printed on the back of the phone. I am
  not sure if that was the mistake of the person putting the wrong label
  on the phone... (It was not from the manufacturer that I currently
  work for... ;)
   
=> we have already this kind of stories about Ethernet NICs...

   > Would an IMT2000 identifier be better adapted, since it has a wider
   > reach, more neutral.
   
   I am not sure what you are referring to. Something standardized in ITU?
   
=> I found a reference to a project to extend IMEIs to the whole IMT2000
but I am not an ITU expert (you should ask my co-author).

Regards

[EMAIL PROTECTED]

PS for Sun people: the MAC address is a part of the Serial Number of
a Sun box (at least for old Sparcs). Is this a privacy/confidentiality
issue?
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to