Internet DRAFT - draft-avasarala-diameter-error-invalid-identity
draft-avasarala-diameter-error-invalid-identity
Diameter Maintenance and Extensions (DIME) Ranjit. Avasarala, Ed.
Internet-Draft Vamsidhar. Sivadi
Updates: 4006, 4740 (if approved) AT&T Services Inc
Intended status: Standards Track October 27, 2017
Expires: April 30, 2018
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
Avasarala & Sivadi Expires April 30, 2018 [Page 1]
Internet-Draft Diameter Invalid Mobile Identity October 2017
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
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
3.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 3
4. Instances of invalid IMEI . . . . . . . . . . . . . . . . . . 3
4.1. IMEI validation . . . . . . . . . . . . . . . . . . . . . 3
4.2. DIAMETER_INVALID_MOBILE_IDENTITY Error code . . . . . . . 3
4.3. Use of DIAMETER_INVALID_MOBILE_IDENTITY Error code . . . 4
5. Handling of DIAMETER_INVALID_MOBILE_IDENTITY error . . . . . 4
6. Examples of use of DIAMETER_INVALID_MOBILE_IDENTITY in
Diameter Responses . . . . . . . . . . . . . . . . . . . . . 4
6.1. Credit Control applications . . . . . . . . . . . . . . . 4
6.2. User Authorization applications . . . . . . . . . . . . . 4
7. Security Considerations . . . . . . . . . . . . . . . . . . . 5
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
10.1. Normative References . . . . . . . . . . . . . . . . . . 5
10.2. Informative References . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
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 [RFC2119].
Avasarala & Sivadi Expires April 30, 2018 [Page 2]
Internet-Draft Diameter Invalid Mobile Identity October 2017
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
Avasarala & Sivadi Expires April 30, 2018 [Page 3]
Internet-Draft Diameter Invalid Mobile Identity October 2017
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.
Avasarala & Sivadi Expires April 30, 2018 [Page 4]
Internet-Draft Diameter Invalid Mobile Identity October 2017
7. Security Considerations
None
8. Acknowledgements
9. IANA Considerations
This section registers a new Diameter protocol error code, 3011. The
required information for this registration, as specified in
[RFC6733], is:
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.
10. References
10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006,
DOI 10.17487/RFC4006, August 2005,
<https://www.rfc-editor.org/info/rfc4006>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012,
<https://www.rfc-editor.org/info/rfc6733>.
10.2. Informative References
[RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of
MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181,
September 2005, <https://www.rfc-editor.org/info/rfc4181>.
Avasarala & Sivadi Expires April 30, 2018 [Page 5]
Internet-Draft Diameter Invalid Mobile Identity October 2017
[RFC7254] Montemurro, M., Ed., Allen, A., McDonald, D., and P.
Gosden, "A Uniform Resource Name Namespace for the Global
System for Mobile Communications Association (GSMA) and
the International Mobile station Equipment Identity
(IMEI)", RFC 7254, DOI 10.17487/RFC7254, May 2014,
<https://www.rfc-editor.org/info/rfc7254>.
Authors' Addresses
Ranjit Avasarala (editor)
AT&T Services Inc
28W615 Ferry Rd
Warrenville, IL 60555
USA
Email: rkavasarala@att.com
Vamsidhar Sivadi
ATT Services Inc
28W615 Ferry Rd
Warrenville, IL 60555
USA
Email: vamsidhar.sivadi@att.com
Avasarala & Sivadi Expires April 30, 2018 [Page 6]
