Diameter Invalid Mobile Identity
draft-avasarala-diameter-error-invalid-identity-00.txt

Abstract

This specification documents an extension to the Diameter Base Protocol RFC6733. This extension adds a new Diameter Protocol Error code to the Result-Code AVP to the Diameter responses for indicating error in the mobile identity in the Diameter requests.

This extension is mainly applicable to the credit control applications defined in RFC4006 and user authorization procedures defined in RFC4740.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on April 30, 2018.

Copyright Notice

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.

Table of Contents

• 1. Conventions used in this document
• 2. Introduction
• 3. Terminology and Abbreviations
• 3.1. Terminology
• 3.2. Abbreviations
• 4. Instances of invalid IMEI
• 4.1. IMEI validation
• 4.2. DIAMETER_INVALID_MOBILE_IDENTITY Error code
• 4.3. Use of DIAMETER_INVALID_MOBILE_IDENTITY Error code
• 5. Handling of DIAMETER_INVALID_MOBILE_IDENTITY error
• 6. Examples of use of DIAMETER_INVALID_MOBILE_IDENTITY in Diameter Responses
• 6.1. Credit Control applications
• 6.2. User Authorization applications
• 7. Security Considerations
• 8. Acknowledgements
• 9. IANA Considerations
• 10. References
• 10.1. Normative References
• 10.2. Informative References
• Authors' Addresses

1. Conventions used in this document

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

2. Introduction

This document defines a new Diameter error code for indicating error in mobile identity e.g. IMEI.

The Diameter base protocol defined in [RFC6733] defines the various Diameter protocol errors that can occur in Diameter requests. This document extends it to add the new Diameter error code to report invalid IMEI value.

3. Terminology and Abbreviations

3.1. Terminology

Diameter Node

A RFC6733 Diameter Client, RFC6733 Diameter Server, or RFC6733 Diameter Agent.

Diameter Endpoint

An RFC6733 Diameter Client or RFC6733 Diameter Server.

3.2. Abbreviations

              
 IMEI    : International Mobile Equipment Identifier
 IMESISV : International Mobile Equipment Identifier Software Version
              
	    

4. Instances of invalid IMEI

4.1. IMEI validation

The Diameter entities that receive IMEI value as part of Diameter AVPs like User-Equipment-Info-Value as defined in Section 8.50 of [RFC4006] should validate the IMEI value as per the validation rules described in sections 4.2 for IMEI and Section 4.3 of [RFC7254] for IMEISV respectively.

4.2. DIAMETER_INVALID_MOBILE_IDENTITY Error code

A new Diameter Protocol Error - DIAMETER_INVALID_MOBILE_IDENTITY with code 301x is defined for entities to use to report the cases of invalid IMEI in Diameter AVPs

4.3. Use of DIAMETER_INVALID_MOBILE_IDENTITY Error code

When the Diameter endpoints determine that the IMEI value is invalid as per the procedure defined in Section 4 they should populate the Diameter Result-Code AVP with the DIAMETER_INVALID_MOBILE_IDENTITY Error code and insert the Result-Code AVP into the Diameter response.

5. Handling of DIAMETER_INVALID_MOBILE_IDENTITY error

Diameter nodes receiving a Diameter response with Result-Code AVP set to DIAMETER_INVALID_MOBILE_IDENTITY SHOULD attempt to re-send the Diameter Request with a valid IMEI value User-Equipment-Info AVP. If they cannot do this, then they need to generate appropriate response to the previous node and abort the transaction.

6. Examples of use of DIAMETER_INVALID_MOBILE_IDENTITY in Diameter Responses

The IMEI value is received in the User-Equipment-info AVP defined in Section 8.50 of [RFC4006]

6.1. Credit Control applications

The Credit control applications can receive IMEI value as part of Diameter CCR message as defined in Section 8.50 of [RFC4006].

When the server that receives the Diameter CCR message determines that the IMEI value obtained is invalid, SHOULD use the Result-Code 301x (defined in this document) along with the DIAMETER_INVALID_MOBILE_IDENTITY error to indicate invalid IMEI value in the Diameter CCA response.

The Credit-control client receiving this error SHOULD attempt to re-send the CCR message with a valid IMEI in User-Equipment-Info AVP, else the request should be aborted.

6.2. User Authorization applications

The user authorization applications that determine the IMEI value to be invalid as part of user authorization procedure SHOULD use the Result-Code 301x (defined in this document) along with the DIAMETER_INVALID_MOBILE_IDENTITY error to indicate invalid IMEI value.

7. Security Considerations

None

8. Acknowledgements

9. IANA Considerations

               
      Name:  DIAMETER_INVALID_MOBILE_IDENTITY
   
      Description:  This protocol error code is for indicating that the 
                    IMEI value obtained in the Diameter request is 
                    determined to be invalid.
                
           

This section registers a new Diameter protocol error code, 3011. The required information for this registration, as specified in [RFC6733], is:

10. References

10.1. Normative References

10.2. Informative References

Authors' Addresses