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

Mary Barnes <mary.h.barnes@gmail.com> Tue, 27 August 2013 14:28 UTC

Return-Path: <mary.h.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31CD311E8354 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 07:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level:
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JFymKcAD3OU3 for <ietf@ietfa.amsl.com>; Tue, 27 Aug 2013 07:28:18 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5D02E11E81A8 for <ietf@ietf.org>; Tue, 27 Aug 2013 07:28:18 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id ij15so3012617vcb.2 for <ietf@ietf.org>; Tue, 27 Aug 2013 07:28:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XswmZSseMMb/HJMmsv6946/JYfZKh9zua7ssvJB7xEw=; b=sDy06ME13XTR3Nzwa+PeIGA1cynr9oyHwYZcNeqJMvFj01kD3CBz85+/WfWD1jiLwK /Gze41ayBvt0UJxhNePa0BKNo3iAztwuarNwMQiGVbTvEaKXLuvrDobXAfX7H8S4fTzL dw4UpRfXSu/zL6jcLlv7MTGmMbaFk2XxpXaIWyPixWrhQLfjZSkxHcjzg3QJ3v5aQsSu +7P2ZsL+k9fU6U0CyHmoKcyMTXp0nVSvlHJnSfdh/guW/L7d/DZFFkLriL0ftGahkgn/ vi2rB+T+KZ4wCGon8rTzWUM6hdDO15VpcBesgyoQU3E47LjbkNYGPAdcc/+zQWOisWyR QZ0w==
MIME-Version: 1.0
X-Received: by 10.220.164.202 with SMTP id f10mr1758500vcy.25.1377613696779; Tue, 27 Aug 2013 07:28:16 -0700 (PDT)
Received: by 10.58.74.97 with HTTP; Tue, 27 Aug 2013 07:28:16 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130721070808.0c808140@elandnews.com>
References: <6.2.5.6.2.20130720193906.06cdd008@resistor.net> <BBF5DDFE515C3946BC18D733B20DAD2338DD2606@XMB104ADS.rim.net> <6.2.5.6.2.20130721070808.0c808140@elandnews.com>
Date: Tue, 27 Aug 2013 09:28:16 -0500
Message-ID: <CABmDk8nmQLY1mBbpECjo7KLULXyEvXYNgDiOVjuH6mgy-sDL9w@mail.gmail.com>
Subject: Re: Last call: draft-montemurro-gsma-imei-urn-16.txt
From: Mary Barnes <mary.h.barnes@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary="001a11c1e98008c97b04e4eeaffc"
Cc: John C Klensin <john@jck.com>, Mary Barnes <mary.ietf.barnes@gmail.com>, tbray@textuality.com, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Aug 2013 14:28:19 -0000

SM,

As far as the IPR, as the shepherd and DISPATCH WG co-chair, I posted a
note to the DISPATCH WG mailing list before progressing this document to
see if anyone had any concerns about the IPR disclosures, which had been
discussed in the past and were updated when I asked the authors the
requisite questions about IPR while doing the PROTO write-up.  No concerns
were raised with regards to the updated IPR disclosures (i.e., no one
responded to that email).     And, you can google  "draft montemurro ietf
ipr archives" to find past discussions such as this one:  draft montemurro
ietf ipr archives

Regards,
Mary.


On Sun, Jul 21, 2013 at 11:38 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> At 00:03 21-07-2013, Andrew Allen wrote:
>
>> The reason why the IMEI namespace is being registered as a GSMA namespace
>> and not as part of the 3GPP namespace is that the GSMA has the
>> responsibility for IMEI assignment and hence in maintaining uniqueness of
>> the namespace. It has nothing to do with IPR which was extensively
>> discussed on the dispatch list.
>>
>
> I read the dispatch mailing list.  I did not see the extensive discussion.
>  I saw the following comment "Surely that is just trying to turn the IETF
> into the policeman".
>
>
>  The primary purpose of the IMEI is for preventing use of stolen mobile
>> phones and enabling emergency calls to be made from mobiles that don't have
>> a valid subscription.
>>
>
> From what I read the main purpose of the IMEI is to be able to take
> measures against stolen phones and against equipment which the use cannot
> be accepted for technical or safety reasons.  The secondary purpose is the
> tracing of malicious calls.
>
> There is an apps which sends the IMEI in a cryptographically-protected
> form over the network.  For what it is worth, it's MD5.
>
> There has been some work in the IETF on emergency calls (see service URN).
>
>
> At 00:12 21-07-2013, Andrew Allen wrote:
>
>> As John pointed out having the sub namespace reviewed by IETF provides
>> the opportunity to add text to address privacy concerns with any
>> inappropriate usage.
>>
>
> I don't think that it is the role of the IETF to determine whether the
> usage of a sub-namespace is appropriate or not as it can cause namespace
> management issues.
>
> I tried the explain the subtlety between privacy concerns and privacy
> considerations.  The IMEI can also be used as a customer identifier.
>
> Regards,
> S. Moonesamy
>