[Dime] RFC 4006 bis - IMEI

"Gardella, Maryse (Nokia - FR)" <maryse.gardella@nokia.com> Thu, 30 June 2016 17:00 UTC

Return-Path: <maryse.gardella@nokia.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 742ED12DAC7 for <dime@ietfa.amsl.com>; Thu, 30 Jun 2016 10:00:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id urBwI8CeI0nT for <dime@ietfa.amsl.com>; Thu, 30 Jun 2016 10:00:08 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E85B012D885 for <dime@ietf.org>; Thu, 30 Jun 2016 10:00:07 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id D54422390D827 for <dime@ietf.org>; Thu, 30 Jun 2016 17:00:02 +0000 (GMT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (fr712usmtp2.zeu.alcatel-lucent.com [135.239.2.42]) by fr712umx4.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u5UH05pp018836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <dime@ietf.org>; Thu, 30 Jun 2016 17:00:06 GMT
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u5UGwppg011973 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dime@ietf.org>; Thu, 30 Jun 2016 19:00:04 +0200
Received: from FR712WXCHMBA09.zeu.alcatel-lucent.com ([169.254.5.62]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.03.0195.001; Thu, 30 Jun 2016 18:58:37 +0200
From: "Gardella, Maryse (Nokia - FR)" <maryse.gardella@nokia.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] RFC 4006 bis - IMEI
Thread-Index: AdHS8KRXUuwo33kKTp24S5zATa6Cnw==
Date: Thu, 30 Jun 2016 16:58:36 +0000
Message-ID: <F77ED24D51A356439EE433AD28B990DFC50E75CA@FR712WXCHMBA09.zeu.alcatel-lucent.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/JohNFEASwktNe2Bdr4L4pi744A8>
Subject: [Dime] RFC 4006 bis - IMEI
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2016 17:00:15 -0000

All,

As part of the updates to RFC 4006 I propose to consider the IMEI also when refering to IMEISV, otherwise it is not clear if User-Equipment-Info-Type value O can be used for IMEI. 


In section 8.50. User-Equipment-Info-Type AVP in RFC4006,the following is specified: 
  
 IMEISV                          0
      The identifier contains the International Mobile Equipment
      Identifier and Software Version in the international IMEISV format
      according to 3GPP TS 23.003 [3GPPIMEI].

Which I propose to be updated as follows:  

IMEI(SV)                          0
      The identifier contains the International Mobile Equipment
      Identifier and Software Version in the international IMEISV format, 
	or the International Mobile Equipment Identifier in the international IMEI format 
      according to 3GPP TS 23.003 [3GPPIMEI]. 


Differentiation between IMEI (15 digits) and IMEISV (16 digits) is based on AVP length, would this work?

BR
Maryse