Re: [Dime] RFC 4006 bis - IMEI

"Gardella, Maryse (Nokia - FR)" <maryse.gardella@nokia.com> Tue, 05 July 2016 13:16 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 630DF12D556 for <dime@ietfa.amsl.com>; Tue, 5 Jul 2016 06:16:26 -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 Se7XsnDg5o7i for <dime@ietfa.amsl.com>; Tue, 5 Jul 2016 06:16:23 -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 7A07612D0E9 for <dime@ietf.org>; Tue, 5 Jul 2016 06:16:22 -0700 (PDT)
Received: from fr712umx4.dmz.alcatel-lucent.com (unknown [135.245.210.45]) by Websense Email Security Gateway with ESMTPS id A1BD4818BD0A8; Tue, 5 Jul 2016 13:16:17 +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 u65DGKfq003970 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 5 Jul 2016 13:16:20 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id u65DGKLr010888 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Jul 2016 15:16:20 +0200
Received: from FR712WXCHMBA09.zeu.alcatel-lucent.com ([169.254.5.62]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Tue, 5 Jul 2016 15:16:20 +0200
From: "Gardella, Maryse (Nokia - FR)" <maryse.gardella@nokia.com>
To: Dave Dolson <ddolson@sandvine.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] RFC 4006 bis - IMEI
Thread-Index: AdHS8KRXUuwo33kKTp24S5zATa6CnwABTOGwAB1boCAAD99PgADEmrXQ
Date: Tue, 5 Jul 2016 13:16:19 +0000
Message-ID: <F77ED24D51A356439EE433AD28B990DFC50E9969@FR712WXCHMBA09.zeu.alcatel-lucent.com>
References: <F77ED24D51A356439EE433AD28B990DFC50E75CA@FR712WXCHMBA09.zeu.alcatel-lucent.com> <E8355113905631478EFF04F5AA706E9830FDB614@wtl-exchp-2.sandvine.com> <F77ED24D51A356439EE433AD28B990DFC50E7E36@FR712WXCHMBA09.zeu.alcatel-lucent.com> <E8355113905631478EFF04F5AA706E9830FDCF7C@wtl-exchp-2.sandvine.com>
In-Reply-To: <E8355113905631478EFF04F5AA706E9830FDCF7C@wtl-exchp-2.sandvine.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.41]
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/BS9hzRVOdymOGYxJ5wnHcsMhWV0>
Subject: Re: [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: Tue, 05 Jul 2016 13:16:26 -0000

Hi Dave, 

Do you mean, in case this new value would be needed, it is possible to handle this via IANA allocation w/o impacting existing RFC 4006? Could you clarify this for me?

Thanks
Maryse 

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Dave Dolson
Sent: vendredi 1 juillet 2016 19:11
To: Gardella, Maryse (Nokia - FR); dime@ietf.org
Subject: Re: [Dime] RFC 4006 bis - IMEI

Maryse,
OK, I understand your question.

Reading 3GPP 23.003, IMEI and IMEISV are clearly defined as different things in sections 6.2.1 and 6.2.2.
And RFC4006 specifically says IMEISV. 

So I would say RFC4006 is not ambiguous. 

Also, the most recent 3GPP 32.299 indicates "The used value is 0 for the international mobile equipment identifier and software version according to 3GPP TS 23.003."

It seems reasonable to extend to a Type 4 for IMEI, but there does not seem to have been a need, or there would have been an IANA allocation (which does not require RFC revision).

Perhaps you could explain the need to the group?

-Dave


-----Original Message-----
From: Gardella, Maryse (Nokia - FR) [mailto:maryse.gardella@nokia.com] 
Sent: Friday, July 01, 2016 9:02 AM
To: Dave Dolson; dime@ietf.org
Subject: RE: [Dime] RFC 4006 bis - IMEI

Hi Dave,

Indeed it was not clear to me whether the current definition explicitly excluded the IMEI or not.
I was wondering about the behavior of the client in case the Software Version Number (SVN) is not available. 

Otherwise if a new value is needed for this distinction, I would propose the User-Equipment-Info-Type AVP to be extended with IMEI value 


BR
Maryse

-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Dave Dolson
Sent: jeudi 30 juin 2016 19:39
To: Gardella, Maryse (Nokia - FR); dime@ietf.org
Subject: Re: [Dime] RFC 4006 bis - IMEI

Maryse,

If I understand correctly, you are proposing overloading a type, distinguishing the types only by length.

Is there precedent for the overloading you propose, such as a 3GPP standard or de facto standard usage that you can cite?

Otherwise, IANA may assign new values for new types, and we aren't short on space:
http://www.iana.org/assignments/aaa-parameters/aaa-parameters.xhtml#aaa-parameters-41


-Dave



-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Gardella, Maryse (Nokia - FR)
Sent: Thursday, June 30, 2016 12:59 PM
To: dime@ietf.org
Subject: [Dime] RFC 4006 bis - IMEI

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

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime