Re: [Dime] RFC 4006 bis - IMEI

<lionel.morand@orange.com> Tue, 05 July 2016 17:09 UTC

Return-Path: <lionel.morand@orange.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 DA2CD12D662 for <dime@ietfa.amsl.com>; Tue, 5 Jul 2016 10:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 uG_jAVj0J5iM for <dime@ietfa.amsl.com>; Tue, 5 Jul 2016 10:09:33 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E7E312D128 for <dime@ietf.org>; Tue, 5 Jul 2016 10:09:32 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 958F332481E; Tue, 5 Jul 2016 19:09:30 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [10.114.31.27]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 6D39D238075; Tue, 5 Jul 2016 19:09:30 +0200 (CEST)
Received: from OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c]) by OPEXCLILM7C.corporate.adroot.infra.ftgroup ([fe80::8007:17b:c3b4:d68b%19]) with mapi id 14.03.0294.000; Tue, 5 Jul 2016 19:09:30 +0200
From: <lionel.morand@orange.com>
To: "jouni.nospam@gmail.com" <jouni.nospam@gmail.com>, Dave Dolson <ddolson@sandvine.com>, "Gardella, Maryse (Nokia - FR)" <maryse.gardella@nokia.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] RFC 4006 bis - IMEI
Thread-Index: AdHS8KRXUuwo33kKTp24S5zATa6CnwABTOGwAB1boCAAD99PgADEmrXQAAEW2gAAAh02AAAFULFQ
Date: Tue, 5 Jul 2016 17:09:29 +0000
Message-ID: <21004_1467738570_577BE9CA_21004_4347_1_6B7134B31289DC4FAF731D844122B36E01EE3EDA@OPEXCLILM43.corporate.adroot.infra.ftgroup>
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> <F77ED24D51A356439EE433AD28B990DFC50E9969@FR712WXCHMBA09.zeu.alcatel-lucent.com> <E8355113905631478EFF04F5AA706E9830FE4A5B@wtl-exchp-2.sandvine.com> <e9b91f39-ad3f-4224-0e5e-ff1b8048e23d@gmail.com>
In-Reply-To: <e9b91f39-ad3f-4224-0e5e-ff1b8048e23d@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.2.1.2478543, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.7.5.154216
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/3svwyetLa0oKeXNTSbuI4altdf0>
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 17:09:36 -0000

For clarification, for Diameter related IANA allocation requests, it is under the responsibility of CT4 secretary.

Now, as said by Dave and Jouni, we should clarify the requirement for an IMEI specific value whereas only the IMEISV is actually used.

Regards,

Lionel

> -----Message d'origine-----
> De : DiME [mailto:dime-bounces@ietf.org] De la part de Jouni Korhonen
> Envoyé : mardi 5 juillet 2016 18:32
> À : Dave Dolson; Gardella, Maryse (Nokia - FR); dime@ietf.org
> Objet : Re: [Dime] RFC 4006 bis - IMEI
> 
> Designated experts would most likely be either Lionel or me. Basically the
> procedure goes like: there's a public spec (no need to be in IETF) or at least
> technical discussion (preferably in IETF) of the allocation need of the new code
> point, and once that is "done" someone does a request to IANA. Then IANA will
> contact the "expert", who evaluates the allocation requests and either grants or
> denies it. The more information there is available for the allocation requests the
> more comfortble the expert is backing up the request towards IANA.
> 
> For example various 3GPP CT group secretaries have done allocation requests to
> IANA during years.
> 
> Regarding the User-Equipment-Info-Type AVP doing the new allocation doing it
> in RFC4006bis would be "easy".. assuming we finish this discussion into an
> agreement for a need.
> 
> - Jouni
> 
> 7/5/2016, 8:31 AM, Dave Dolson kirjoitti:
> > Maryse,
> > Referring to BCP26,  https://tools.ietf.org/html/bcp26,
> > You can read about "Assignment by Designated Expert" in section 3
> > https://tools.ietf.org/html/bcp26#section-3
> >
> > I don't know who the designated expert would be, but I think the first step
> would be to begin a thread on the dime mailing list to request the new
> allocation, justifying why it is needed.
> >
> > Hopefully the dime chairs can provide more insight on the process.
> >
> > -Dave
> >
> >
> > -----Original Message-----
> > From: Gardella, Maryse (Nokia - FR) [mailto:maryse.gardella@nokia.com]
> > Sent: Tuesday, July 05, 2016 9:16 AM
> > To: Dave Dolson; dime@ietf.org
> > Subject: RE: [Dime] RFC 4006 bis - IMEI
> >
> > 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#aa
> > a-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
> >
> > _______________________________________________
> > 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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.