IETF Logo Mail Archive

Re: [Dime] draft-avasarala-diameter-error-invalid-identity-00

Yuval Lifshitz <ylifshitz@sandvine.com> Tue, 31 October 2017 17:06 UTC

Return-Path: <ylifshitz@sandvine.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 D347B13F9D1 for <dime@ietfa.amsl.com>; Tue, 31 Oct 2017 10:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ys76Z0LSFLnb for <dime@ietfa.amsl.com>; Tue, 31 Oct 2017 10:06:45 -0700 (PDT)
Received: from mail1.sandvine.com (mail1.sandvine.com [64.7.137.165]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8B6513F9C6 for <dime@ietf.org>; Tue, 31 Oct 2017 10:06:38 -0700 (PDT)
Received: from WTL-EXCHP-1.sandvine.com ([fe80::ac6b:cc1e:f2ff:93aa]) by WTL-EXCHP-3.sandvine.com ([fe80::3c39:d305:d721:f00a%15]) with mapi id 14.03.0319.002; Tue, 31 Oct 2017 13:06:37 -0400
From: Yuval Lifshitz <ylifshitz@sandvine.com>
To: "AVASARALA, RANJIT KUMAR" <ra698k@att.com>, "dime@ietf.org" <dime@ietf.org>
CC: "ben@nostrum.com" <ben@nostrum.com>, Yuval Lifshitz <ylifshitz@sandvine.com>
Thread-Topic: draft-avasarala-diameter-error-invalid-identity-00
Thread-Index: AdNSZIrJm2O1lnw9Q5e+yrjpjtgOFgABIxwg
Date: Tue, 31 Oct 2017 17:06:36 +0000
Message-ID: <C43C255C7106314F8D13D03FA20CFE49ED56978C@wtl-exchp-1.sandvine.com>
References: <BD15502709C85D4DAA2DCBF30D38A3B7172894DC@MOSTLS1MSGUSRFG.ITServices.sbc.com>
In-Reply-To: <BD15502709C85D4DAA2DCBF30D38A3B7172894DC@MOSTLS1MSGUSRFG.ITServices.sbc.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.142.2]
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: multipart/alternative; boundary="_000_C43C255C7106314F8D13D03FA20CFE49ED56978Cwtlexchp1sandvi_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/VrFkwcTQkDYFdFJCLGMKL8kApr4>
Subject: Re: [Dime] draft-avasarala-diameter-error-invalid-identity-00
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.22
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, 31 Oct 2017 17:06:47 -0000

Dear Ranjit,
I think there are several issues with your proposal:

*         A standard diameter error already exists for the case described. It is DIAMETER_INVALID_AVP_VALUE (5004)

*         3xxx level error codes are meant for peer level (per hop) while the case you describe is session level (end 2 end)

*         User-Equipment-Info is an optional AVP (at least in RFC4006), and its payload is not necessarily IMEI or IMEISV. This mean that specification forcing the credit control server to validate it would contradict the existing specification

Best Regards,

Yuval

From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of AVASARALA, RANJIT KUMAR
Sent: Tuesday, October 31, 2017 6:32 PM
To: dime@ietf.org
Cc: ben@nostrum.com
Subject: [Dime] draft-avasarala-diameter-error-invalid-identity-00

Hello all

We published a new Internet draft addressing the issue of invalid IMEI in SIP / Diameter requests.

Here is the background

IMEI is used for uniquely identifying the mobile devices.  IMEI is present in SIP REGISTER request (Contact header) and Diameter CCR Request (user-Equipment-Info AVP).   It is always assumed that the IMEI value is correct and also the entities that receive IMEI usually do not validate the value.

This IMEI goes all the way till CCFs which use it as part of records generation that eventually lead to generation of CDRs.  So in scenarios where IMEI is correct, the records are considered good but if the IMEI is invalid or incorrect, then the records that are generated become "bad" and lead to inconsistency in billing.

So there is a need to reduce or prevent the generation of bad records and this can be done by validating the received IMEI and reporting invalid instances of IMEI.

So in order to report the cases of invalid iMEI, this draft proposes a new diameter protocol error code - DIAMETER_INVALID_MOBILE_IDENTITY

We request everyone to review the draft and comment.

The URL of the draft is - https://tools.ietf.org/html/draft-avasarala-diameter-error-invalid-identity-00.html

Regards
Ranjit

v2.39.1 | Report a Bug | By Email | System Status