draft-ietf-dime-rfc4006bis-07.txt   draft-ietf-dime-rfc4006bis-08.txt 
Network Working Group L. Bertz, Ed. Network Working Group L. Bertz, Ed.
Internet-Draft Sprint Internet-Draft Sprint
Obsoletes: 4006 (if approved) D. Dolson, Ed. Obsoletes: 4006 (if approved) D. Dolson, Ed.
Intended status: Standards Track Y. Lifshitz, Ed. Intended status: Standards Track Y. Lifshitz, Ed.
Expires: September 21, 2018 Sandvine Expires: November 19, 2018 Sandvine
March 20, 2018 May 18, 2018
Diameter Credit-Control Application Diameter Credit-Control Application
draft-ietf-dime-rfc4006bis-07 draft-ietf-dime-rfc4006bis-08
Abstract Abstract
This document specifies a Diameter application that can be used to This document specifies a Diameter application that can be used to
implement real-time credit-control for a variety of end user services implement real-time credit-control for a variety of end user services
such as network access, Session Initiation Protocol (SIP) services, such as network access, Session Initiation Protocol (SIP) services,
messaging services, and download services. The Diameter Credit- messaging services, and download services. The Diameter Credit-
Control application as defined in this document obsoletes RFC4006, Control application as defined in this document obsoletes RFC4006,
and it must be supported by all new Diameter Credit-Control and it must be supported by all new Diameter Credit-Control
Application implementations. Application implementations.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 21, 2018. This Internet-Draft will expire on November 19, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 46 skipping to change at page 4, line 46
9.1. Transient Failures . . . . . . . . . . . . . . . . . . . 87 9.1. Transient Failures . . . . . . . . . . . . . . . . . . . 87
9.2. Permanent Failures . . . . . . . . . . . . . . . . . . . 88 9.2. Permanent Failures . . . . . . . . . . . . . . . . . . . 88
10. AVP Occurrence Table . . . . . . . . . . . . . . . . . . . . 88 10. AVP Occurrence Table . . . . . . . . . . . . . . . . . . . . 88
10.1. Credit-Control AVP Table . . . . . . . . . . . . . . . . 89 10.1. Credit-Control AVP Table . . . . . . . . . . . . . . . . 89
10.2. Re-Auth-Request/Answer AVP Table . . . . . . . . . . . . 90 10.2. Re-Auth-Request/Answer AVP Table . . . . . . . . . . . . 90
11. RADIUS/Diameter Credit-Control Interworking Model . . . . . . 90 11. RADIUS/Diameter Credit-Control Interworking Model . . . . . . 90
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 93 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 93
12.1. Application Identifier . . . . . . . . . . . . . . . . . 94 12.1. Application Identifier . . . . . . . . . . . . . . . . . 94
12.2. Command Codes . . . . . . . . . . . . . . . . . . . . . 94 12.2. Command Codes . . . . . . . . . . . . . . . . . . . . . 94
12.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 94 12.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 94
12.4. Result-Code AVP Values . . . . . . . . . . . . . . . . . 94 12.4. Result-Code AVP Values . . . . . . . . . . . . . . . . . 95
12.5. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . 94 12.5. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . 95
12.6. CC-Session-Failover AVP . . . . . . . . . . . . . . . . 94 12.6. CC-Session-Failover AVP . . . . . . . . . . . . . . . . 95
12.7. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 94 12.7. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 95
12.8. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 95 12.8. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 95
12.9. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 95 12.9. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 95
12.10. Credit-Control-Failure-Handling AVP . . . . . . . . . . 95 12.10. Credit-Control-Failure-Handling AVP . . . . . . . . . . 96
12.11. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 95 12.11. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 96
12.12. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . 95 12.12. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . 96
12.13. Multiple-Services-Indicator AVP . . . . . . . . . . . . 95 12.13. Multiple-Services-Indicator AVP . . . . . . . . . . . . 96
12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 96 12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 96
12.15. Requested-Action AVP . . . . . . . . . . . . . . . . . . 96 12.15. Requested-Action AVP . . . . . . . . . . . . . . . . . . 96
12.16. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 96 12.16. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 97
12.17. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . 96 12.17. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . 97
12.18. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 96 12.18. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 97
13. Credit-Control Application Related Parameters . . . . . . . . 96 13. Credit-Control Application Related Parameters . . . . . . . . 97
14. Security Considerations . . . . . . . . . . . . . . . . . . . 97 14. Security Considerations . . . . . . . . . . . . . . . . . . . 98
14.1. Direct Connection with Redirects . . . . . . . . . . . . 98 14.1. Direct Connection with Redirects . . . . . . . . . . . . 99
15. Privacy Considerations . . . . . . . . . . . . . . . . . . . 99 15. Privacy Considerations . . . . . . . . . . . . . . . . . . . 99
15.1. Privacy Sensitive AVPs . . . . . . . . . . . . . . . . . 99 15.1. Privacy Sensitive AVPs . . . . . . . . . . . . . . . . . 100
15.2. Data Minimization . . . . . . . . . . . . . . . . . . . 100 15.2. Data Minimization . . . . . . . . . . . . . . . . . . . 101
15.3. Diameter Agents . . . . . . . . . . . . . . . . . . . . 101 15.3. Diameter Agents . . . . . . . . . . . . . . . . . . . . 102
16. References . . . . . . . . . . . . . . . . . . . . . . . . . 102 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 102
16.1. Normative References . . . . . . . . . . . . . . . . . . 102 16.1. Normative References . . . . . . . . . . . . . . . . . . 102
16.2. Informative References . . . . . . . . . . . . . . . . . 104 16.2. Informative References . . . . . . . . . . . . . . . . . 104
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 105 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 105
Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 105 Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 106
B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 105 B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 106
B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 108 B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 108
B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 110 B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 110
B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 110 B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 111
B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 112 B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 112
B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 113 B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 113
B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 114 B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 114
B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 116 B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 116
B.9. Flow IX . . . . . . . . . . . . . . . . . . . . . . . . . 118 B.9. Flow IX . . . . . . . . . . . . . . . . . . . . . . . . . 118
Appendix C. Changes relative to RFC4006 . . . . . . . . . . . . 123 Appendix C. Changes relative to RFC4006 . . . . . . . . . . . . 123
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 124 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 124
1. Introduction 1. Introduction
skipping to change at page 94, line 22 skipping to change at page 94, line 22
This specification uses the value 272 from the Command code namespace This specification uses the value 272 from the Command code namespace
defined in [RFC6733] for the Credit-Control-Request (CCR) and Credit- defined in [RFC6733] for the Credit-Control-Request (CCR) and Credit-
Control-Answer (CCA) commands. Control-Answer (CCA) commands.
12.3. AVP Codes 12.3. AVP Codes
See Section 8 for the assignment of the namespace in this See Section 8 for the assignment of the namespace in this
specification. specification.
This document describes new AVP codes beyond those described in
RFC4006. IANA is requested to allocated codes for the AVPs defined
in the following Table 7.
+-----------------------------------+-------+--------------------+
| Attribute Name | Code | Defined in section |
+-----------------------------------+-------+--------------------+
| User-Equipment-Info-Extension | TBD1 | 8.52 |
| User-Equipment-Info-IMEISV | TBD2 | 8.53 |
| User-Equipment-Info-MAC | TBD3 | 8.54 |
| User-Equipment-Info-EUI64 | TBD4 | 8.55 |
| User-Equipment-Info-ModifiedEUI64 | TBD5 | 8.56 |
| User-Equipment-Info-IMEI | TBD6 | 8.57 |
| Subscription-Id-Extension | TBD7 | 8.58 |
| Subscription-Id-E164 | TBD8 | 8.59 |
| Subscription-Id-IMSI | TBD9 | 8.60 |
| Subscription-Id-SIP-URI | TBD10 | 8.61 |
| Subscription-Id-NAI | TBD11 | 8.62 |
| Subscription-Id-Private | TBD12 | 8.63 |
| Redirect-Server-Extension | TBD13 | 8.64 |
| Redirect-Address-IPAddress | TBD14 | 8.65 |
| Redirect-Address-URL | TBD15 | 8.66 |
| Redirect-Address-SIP-URI | TBD16 | 8.67 |
| QoS-Final-Unit-Indication | TBD17 | 8.68 |
+-----------------------------------+-------+--------------------+
Table 7: Requested AVP Assignments
12.4. Result-Code AVP Values 12.4. Result-Code AVP Values
This specification assigns the values 4010, 4011, 4012, 5030, 5031 This specification assigns the values 4010, 4011, 4012, 5030, 5031
from the Result-Code AVP value namespace defined in [RFC6733]. See from the Result-Code AVP value namespace defined in [RFC6733]. See
Section 9 for the assignment of the namespace in this specification. Section 9 for the assignment of the namespace in this specification.
12.5. CC-Request-Type AVP 12.5. CC-Request-Type AVP
As defined in Section 8.3, the CC-Request-Type AVP includes As defined in Section 8.3, the CC-Request-Type AVP includes
Enumerated type values 1 - 4. IANA has created and is maintaining a Enumerated type values 1 - 4. IANA has created and is maintaining a
 End of changes. 10 change blocks. 
24 lines changed or deleted 52 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/