ietf
[Top] [All Lists]

Re: Last call: draft-montemurro-gsma-imei-urn-16.txt

2013-07-19 10:59:06
On Fri, Jul 19, 2013 at 8:38 AM, Andrew Allen 
<aallen(_at_)blackberry(_dot_)com> wrote:

 I suggest you also read

http://datatracker.ietf.org/doc/draft-allen-dispatch-imei-urn-as-instanceid/


Quoting from that document: “If a URN scheme other than UUID is used, the
UA MUST only use URNs for which an RFC (from the IETF stream) defines how
the specific URN needs to be constructed...”

Now, I’m not an expert in the 3GPP world; but the suggestion in that
extract that UUIDs are a better choice than a (shaky, unreliable,
privacy-problematic) device identifier certainly rings true for those of us
who think at the apps level.  -T




That will explain the primary application of this URN which is intended
for use in the 3GPP cellular standards.

Andrew

 *From*: Tim Bray [mailto:tbray(_at_)textuality(_dot_)com]
*Sent*: Friday, July 19, 2013 10:02 AM Central Standard Time
*To*: IETF-Discussion Discussion <ietf(_at_)ietf(_dot_)org>
*Subject*: Last call: draft-montemurro-gsma-imei-urn-16.txt

  Just wanted to point out that both Apple (for iOS) and Google (for
Android) have strongly discouraged the use of IMEI to identify devices for
the purposes of application software.  There are privacy, quality, and
availability issues with their use.  Apple has removed the ability of
developers to work with the (often IMEI-derived) “Universal Device ID” (see
http://blogs.avg.com/mobile-2/apple-ios-7-puts-unique-device-ids/) and
Google has officially deprecated their use:
http://android-developers.blogspot.ca/2011/03/identifying-app-installations.html

 I’m not sure from reading the draft what the goal of having this URN
namespace is, but if it involves encouraging its use by application
developers, I’m pretty sure it’s a bad idea.

  -Tim
 ---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other applicable privileges), or constitute non-public
information. Any use of this information by anyone other than the intended
recipient is prohibited. If you have received this transmission in error,
please immediately reply to the sender and delete this information from
your system. Use, dissemination, distribution, or reproduction of this
transmission by unintended recipients is not authorized and may be
unlawful.