draft-ietf-dime-rfc4006bis-01.txt   draft-ietf-dime-rfc4006bis-02.txt 
Network Working Group L. Bertz, Ed. Network Working Group L. Bertz, Ed.
Internet-Draft Sprint Internet-Draft Sprint
Intended status: Standards Track D. Dolson, Ed. Intended status: Standards Track D. Dolson, Ed.
Expires: August 27, 2017 Y. Lifshitz, Ed. Expires: September 10, 2017 Y. Lifshitz, Ed.
Sandvine Sandvine
February 23, 2017 March 9, 2017
Diameter Credit-Control Application Diameter Credit-Control Application
draft-ietf-dime-rfc4006bis-01 draft-ietf-dime-rfc4006bis-02
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. messaging services, and download services.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 August 27, 2017. This Internet-Draft will expire on September 10, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 3, line 16 skipping to change at page 3, line 16
6. One Time Event . . . . . . . . . . . . . . . . . . . . . . . 43 6. One Time Event . . . . . . . . . . . . . . . . . . . . . . . 43
6.1. Service Price Enquiry . . . . . . . . . . . . . . . . . . 44 6.1. Service Price Enquiry . . . . . . . . . . . . . . . . . . 44
6.2. Balance Check . . . . . . . . . . . . . . . . . . . . . . 45 6.2. Balance Check . . . . . . . . . . . . . . . . . . . . . . 45
6.3. Direct Debiting . . . . . . . . . . . . . . . . . . . . . 45 6.3. Direct Debiting . . . . . . . . . . . . . . . . . . . . . 45
6.4. Refund . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.4. Refund . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.5. Failure Procedure . . . . . . . . . . . . . . . . . . . . 47 6.5. Failure Procedure . . . . . . . . . . . . . . . . . . . . 47
7. Credit-Control Application State Machine . . . . . . . . . . 49 7. Credit-Control Application State Machine . . . . . . . . . . 49
8. Credit-Control AVPs . . . . . . . . . . . . . . . . . . . . . 57 8. Credit-Control AVPs . . . . . . . . . . . . . . . . . . . . . 57
8.1. CC-Correlation-Id AVP . . . . . . . . . . . . . . . . . . 60 8.1. CC-Correlation-Id AVP . . . . . . . . . . . . . . . . . . 60
8.2. CC-Request-Number AVP . . . . . . . . . . . . . . . . . . 60 8.2. CC-Request-Number AVP . . . . . . . . . . . . . . . . . . 60
8.3. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . . 61 8.3. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . . 60
8.4. CC-Session-Failover AVP . . . . . . . . . . . . . . . . . 62 8.4. CC-Session-Failover AVP . . . . . . . . . . . . . . . . . 61
8.5. CC-Sub-Session-Id AVP . . . . . . . . . . . . . . . . . . 62 8.5. CC-Sub-Session-Id AVP . . . . . . . . . . . . . . . . . . 61
8.6. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 62 8.6. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 62
8.7. Cost-Information AVP . . . . . . . . . . . . . . . . . . 63 8.7. Cost-Information AVP . . . . . . . . . . . . . . . . . . 62
8.8. Unit-Value AVP . . . . . . . . . . . . . . . . . . . . . 64 8.8. Unit-Value AVP . . . . . . . . . . . . . . . . . . . . . 63
8.9. Exponent AVP . . . . . . . . . . . . . . . . . . . . . . 64 8.9. Exponent AVP . . . . . . . . . . . . . . . . . . . . . . 63
8.10. Value-Digits AVP . . . . . . . . . . . . . . . . . . . . 64 8.10. Value-Digits AVP . . . . . . . . . . . . . . . . . . . . 63
8.11. Currency-Code AVP . . . . . . . . . . . . . . . . . . . . 64 8.11. Currency-Code AVP . . . . . . . . . . . . . . . . . . . . 63
8.12. Cost-Unit AVP . . . . . . . . . . . . . . . . . . . . . . 64 8.12. Cost-Unit AVP . . . . . . . . . . . . . . . . . . . . . . 64
8.13. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 65 8.13. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 64
8.14. Credit-Control-Failure-Handling AVP . . . . . . . . . . . 65 8.14. Credit-Control-Failure-Handling AVP . . . . . . . . . . . 64
8.15. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 66 8.15. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 65
8.16. Multiple-Services-Credit-Control AVP . . . . . . . . . . 67 8.16. Multiple-Services-Credit-Control AVP . . . . . . . . . . 66
8.17. Granted-Service-Unit AVP . . . . . . . . . . . . . . . . 68 8.17. Granted-Service-Unit AVP . . . . . . . . . . . . . . . . 67
8.18. Requested-Service-Unit AVP . . . . . . . . . . . . . . . 69 8.18. Requested-Service-Unit AVP . . . . . . . . . . . . . . . 68
8.19. Used-Service-Unit AVP . . . . . . . . . . . . . . . . . . 69 8.19. Used-Service-Unit AVP . . . . . . . . . . . . . . . . . . 68
8.20. Tariff-Time-Change AVP . . . . . . . . . . . . . . . . . 70 8.20. Tariff-Time-Change AVP . . . . . . . . . . . . . . . . . 69
8.21. CC-Time AVP . . . . . . . . . . . . . . . . . . . . . . . 70 8.21. CC-Time AVP . . . . . . . . . . . . . . . . . . . . . . . 69
8.22. CC-Money AVP . . . . . . . . . . . . . . . . . . . . . . 70 8.22. CC-Money AVP . . . . . . . . . . . . . . . . . . . . . . 69
8.23. CC-Total-Octets AVP . . . . . . . . . . . . . . . . . . . 71 8.23. CC-Total-Octets AVP . . . . . . . . . . . . . . . . . . . 70
8.24. CC-Input-Octets AVP . . . . . . . . . . . . . . . . . . . 71 8.24. CC-Input-Octets AVP . . . . . . . . . . . . . . . . . . . 70
8.25. CC-Output-Octets AVP . . . . . . . . . . . . . . . . . . 71 8.25. CC-Output-Octets AVP . . . . . . . . . . . . . . . . . . 70
8.26. CC-Service-Specific-Units AVP . . . . . . . . . . . . . . 71 8.26. CC-Service-Specific-Units AVP . . . . . . . . . . . . . . 70
8.27. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . . 71 8.27. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . . 70
8.28. Service-Identifier AVP . . . . . . . . . . . . . . . . . 72 8.28. Service-Identifier AVP . . . . . . . . . . . . . . . . . 71
8.29. Rating-Group AVP . . . . . . . . . . . . . . . . . . . . 72 8.29. Rating-Group AVP . . . . . . . . . . . . . . . . . . . . 71
8.30. G-S-U-Pool-Reference AVP . . . . . . . . . . . . . . . . 72 8.30. G-S-U-Pool-Reference AVP . . . . . . . . . . . . . . . . 71
8.31. G-S-U-Pool-Identifier AVP . . . . . . . . . . . . . . . . 73 8.31. G-S-U-Pool-Identifier AVP . . . . . . . . . . . . . . . . 72
8.32. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 73 8.32. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 72
8.33. Validity-Time AVP . . . . . . . . . . . . . . . . . . . . 73 8.33. Validity-Time AVP . . . . . . . . . . . . . . . . . . . . 72
8.34. Final-Unit-Indication AVP . . . . . . . . . . . . . . . . 74 8.34. Final-Unit-Indication AVP . . . . . . . . . . . . . . . . 73
8.35. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . . 75 8.35. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . . 74
8.36. Restriction-Filter-Rule AVP . . . . . . . . . . . . . . . 76 8.36. Restriction-Filter-Rule AVP . . . . . . . . . . . . . . . 75
8.37. Redirect-Server AVP . . . . . . . . . . . . . . . . . . . 76 8.37. Redirect-Server AVP . . . . . . . . . . . . . . . . . . . 75
8.38. Redirect-Address-Type AVP . . . . . . . . . . . . . . . . 77 8.38. Redirect-Address-Type AVP . . . . . . . . . . . . . . . . 76
8.39. Redirect-Server-Address AVP . . . . . . . . . . . . . . . 77 8.39. Redirect-Server-Address AVP . . . . . . . . . . . . . . . 76
8.40. Multiple-Services-Indicator AVP . . . . . . . . . . . . . 77 8.40. Multiple-Services-Indicator AVP . . . . . . . . . . . . . 76
8.41. Requested-Action AVP . . . . . . . . . . . . . . . . . . 78 8.41. Requested-Action AVP . . . . . . . . . . . . . . . . . . 77
8.42. Service-Context-Id AVP . . . . . . . . . . . . . . . . . 79 8.42. Service-Context-Id AVP . . . . . . . . . . . . . . . . . 78
8.43. Service-Parameter-Info AVP . . . . . . . . . . . . . . . 79 8.43. Service-Parameter-Info AVP . . . . . . . . . . . . . . . 78
8.44. Service-Parameter-Type AVP . . . . . . . . . . . . . . . 80 8.44. Service-Parameter-Type AVP . . . . . . . . . . . . . . . 79
8.45. Service-Parameter-Value AVP . . . . . . . . . . . . . . . 80 8.45. Service-Parameter-Value AVP . . . . . . . . . . . . . . . 79
8.46. Subscription-Id AVP . . . . . . . . . . . . . . . . . . . 80 8.46. Subscription-Id AVP . . . . . . . . . . . . . . . . . . . 79
8.47. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 81 8.47. Subscription-Id-Type AVP . . . . . . . . . . . . . . . . 80
8.48. Subscription-Id-Data AVP . . . . . . . . . . . . . . . . 81 8.48. Subscription-Id-Data AVP . . . . . . . . . . . . . . . . 80
8.49. User-Equipment-Info AVP . . . . . . . . . . . . . . . . . 82 8.49. User-Equipment-Info AVP . . . . . . . . . . . . . . . . . 81
8.50. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 82 8.50. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 81
8.51. User-Equipment-Info-Value AVP . . . . . . . . . . . . . . 83 8.51. User-Equipment-Info-Value AVP . . . . . . . . . . . . . . 82
8.52. User-Equipment-Info-Extension AVP . . . . . . . . . . . . 83 8.52. User-Equipment-Info-Extension AVP . . . . . . . . . . . . 82
8.53. User-Equipment-Info-IMEISV AVP . . . . . . . . . . . . . 83 8.53. User-Equipment-Info-IMEISV AVP . . . . . . . . . . . . . 82
8.54. User-Equipment-Info-MAC AVP . . . . . . . . . . . . . . . 83 8.54. User-Equipment-Info-MAC AVP . . . . . . . . . . . . . . . 82
8.55. User-Equipment-Info-EUI64 AVP . . . . . . . . . . . . . . 83 8.55. User-Equipment-Info-EUI64 AVP . . . . . . . . . . . . . . 82
8.56. User-Equipment-Info-ModifiedEUI64 AVP . . . . . . . . . . 84 8.56. User-Equipment-Info-ModifiedEUI64 AVP . . . . . . . . . . 83
8.57. User-Equipment-Info-IMEI AVP . . . . . . . . . . . . . . 84 8.57. User-Equipment-Info-IMEI AVP . . . . . . . . . . . . . . 83
8.58. Subscription-Id-Extension AVP . . . . . . . . . . . . . . 84 8.58. Subscription-Id-Extension AVP . . . . . . . . . . . . . . 83
8.59. Subscription-Id-E164 AVP . . . . . . . . . . . . . . . . 85 8.59. Subscription-Id-E164 AVP . . . . . . . . . . . . . . . . 84
8.60. Subscription-Id-IMSI AVP . . . . . . . . . . . . . . . . 85 8.60. Subscription-Id-IMSI AVP . . . . . . . . . . . . . . . . 84
8.61. Subscription-Id-SIP-URI AVP . . . . . . . . . . . . . . . 85 8.61. Subscription-Id-SIP-URI AVP . . . . . . . . . . . . . . . 84
8.62. Subscription-Id-NAI AVP . . . . . . . . . . . . . . . . . 85 8.62. Subscription-Id-NAI AVP . . . . . . . . . . . . . . . . . 84
8.63. Subscription-Id-Private AVP . . . . . . . . . . . . . . . 85 8.63. Subscription-Id-Private AVP . . . . . . . . . . . . . . . 84
8.64. Redirect-Server-Extension AVP . . . . . . . . . . . . . . 85 8.64. Redirect-Server-Extension AVP . . . . . . . . . . . . . . 84
8.65. Redirect-Address-IPv4Address AVP . . . . . . . . . . . . 86 8.65. Redirect-Address-IPAddress AVP . . . . . . . . . . . . . 85
8.66. Redirect-Address-IPv6Address AVP . . . . . . . . . . . . 86 8.66. Redirect-Address-URL AVP . . . . . . . . . . . . . . . . 85
8.67. Redirect-Address-URL AVP . . . . . . . . . . . . . . . . 86 8.67. Redirect-Address-SIP-URI AVP . . . . . . . . . . . . . . 85
8.68. Redirect-Address-SIP-URI AVP . . . . . . . . . . . . . . 87 8.68. QoS-Final-Unit-Indication AVP . . . . . . . . . . . . . . 86
8.69. QoS-Final-Unit-Indication AVP . . . . . . . . . . . . . . 87 9. Result Code AVP Values . . . . . . . . . . . . . . . . . . . 87
9. Result Code AVP Values . . . . . . . . . . . . . . . . . . . 88 9.1. Transient Failures . . . . . . . . . . . . . . . . . . . 87
9.1. Transient Failures . . . . . . . . . . . . . . . . . . . 89 9.2. Permanent Failures . . . . . . . . . . . . . . . . . . . 88
9.2. Permanent Failures . . . . . . . . . . . . . . . . . . . 89 10. AVP Occurrence Table . . . . . . . . . . . . . . . . . . . . 88
10. AVP Occurrence Table . . . . . . . . . . . . . . . . . . . . 90 10.1. Credit-Control AVP Table . . . . . . . . . . . . . . . . 89
10.1. Credit-Control AVP Table . . . . . . . . . . . . . . . . 90 10.2. Re-Auth-Request/Answer AVP Table . . . . . . . . . . . . 90
10.2. Re-Auth-Request/Answer AVP Table . . . . . . . . . . . . 91 11. RADIUS/Diameter Credit-Control Interworking Model . . . . . . 90
11. RADIUS/Diameter Credit-Control Interworking Model . . . . . . 92 12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 93
12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 95 12.1. Application Identifier . . . . . . . . . . . . . . . . . 94
12.1. Application Identifier . . . . . . . . . . . . . . . . . 95 12.2. Command Codes . . . . . . . . . . . . . . . . . . . . . 94
12.2. Command Codes . . . . . . . . . . . . . . . . . . . . . 95 12.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 94
12.3. AVP Codes . . . . . . . . . . . . . . . . . . . . . . . 95 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 . . . . . . . . . . . . . . . . . . . . 96 12.8. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 95
12.8. Check-Balance-Result AVP . . . . . . . . . . . . . . . . 96 12.9. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 95
12.9. Credit-Control AVP . . . . . . . . . . . . . . . . . . . 96 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 . . . . . . . . . . . . . . . 95
12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 97 12.15. Requested-Action AVP . . . . . . . . . . . . . . . . . . 96
12.15. Requested-Action AVP . . . . . . . . . . . . . . . . . . 97 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 98
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 100 15.1. Normative References . . . . . . . . . . . . . . . . . . 98
15.1. Normative References . . . . . . . . . . . . . . . . . . 100 15.2. Informative References . . . . . . . . . . . . . . . . . 101
15.2. Informative References . . . . . . . . . . . . . . . . . 102 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 101
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 102 Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 101
Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 102 B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 101
B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 102 B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 104
B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 105 B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 106
B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 107 B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 106
B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 107 B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 108
B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 109 B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 109
B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 110 B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 110
B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 111 B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 112
B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 113 B.9. Flow IX . . . . . . . . . . . . . . . . . . . . . . . . . 114
B.9. Flow IX . . . . . . . . . . . . . . . . . . . . . . . . . 115 Appendix C. Changes relative to RFC4006 . . . . . . . . . . . . 119
Appendix C. Changes relative to RFC4006 . . . . . . . . . . . . 120 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 120
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 121
1. Introduction 1. Introduction
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. It provides a general messaging services, and download services. It provides a general
solution to real-time cost and credit-control. solution to real-time cost and credit-control.
The prepaid model has been shown to be very successful, for instance, The prepaid model has been shown to be very successful, for instance,
skipping to change at page 10, line 17 skipping to change at page 10, line 15
If Diameter credit-control proxies exist between the credit-control If Diameter credit-control proxies exist between the credit-control
client and the credit-control server, they MUST advertise the client and the credit-control server, they MUST advertise the
Diameter credit-control application support. Diameter credit-control application support.
3. Credit-Control Messages 3. Credit-Control Messages
This section defines new Diameter message Command-Code values that This section defines new Diameter message Command-Code values that
MUST be supported by all Diameter implementations that conform to MUST be supported by all Diameter implementations that conform to
this specification. The Command Codes are as follows: this specification. The Command Codes are as follows:
+------------------------+--------+------+-----------+ +------------------------+---------+------+-----------+
| Command-Name | Abrev. | Code | Reference | | Command-Name | Abbrev. | Code | Reference |
+------------------------+--------+------+-----------+ +------------------------+---------+------+-----------+
| Credit-Control-Request | CCR | 272 | 3.1 | | Credit-Control-Request | CCR | 272 | 3.1 |
| Credit-Control-Answer | CCA | 272 | 3.2 | | Credit-Control-Answer | CCA | 272 | 3.2 |
+------------------------+--------+------+-----------+ +------------------------+---------+------+-----------+
Table 1: Credit-Control Commands Table 1: Credit-Control Commands
Diameter Base [RFC6733] defines in the section 3.2 the Command Code Diameter Base [RFC6733] defines in the section 3.2 the Command Code
format specification. These formats are observed in Credit-Control format specification. These formats are observed in Credit-Control
messages. messages.
3.1. Credit-Control-Request (CCR) Command 3.1. Credit-Control-Request (CCR) Command
The Credit-Control-Request message (CCR) is indicated by the command- The Credit-Control-Request message (CCR) is indicated by the command-
skipping to change at page 39, line 14 skipping to change at page 39, line 14
5.6.3. Restrict Access Action 5.6.3. Restrict Access Action
A Final-Unit-Indication AVP with the Final-Unit-Action A Final-Unit-Indication AVP with the Final-Unit-Action
RESTRICT_ACCESS indicates to the device supporting this action that, RESTRICT_ACCESS indicates to the device supporting this action that,
upon consumption of the final granted units, the user's access MUST upon consumption of the final granted units, the user's access MUST
be restricted according to the IP packet filters given in the be restricted according to the IP packet filters given in the
Restriction-Filter-Rule AVP(s) or according to the IP packet filters Restriction-Filter-Rule AVP(s) or according to the IP packet filters
identified by the Filter-Id AVP(s). The credit-control server SHOULD identified by the Filter-Id AVP(s). The credit-control server SHOULD
include either the Restriction-Filter-Rule AVP or the Filter-Id AVP include either the Restriction-Filter-Rule AVP or the Filter-Id AVP
in the Credit-Control-Answer message. in the Final-Unit-Indication group AVP of the Credit-Control-Answer
message.
A QoS-Final-Unit-Indication AVP with the Final-Unit-Action A QoS-Final-Unit-Indication AVP with the Final-Unit-Action
RESTRICT_ACCESS indicates to the device supporting this action that, RESTRICT_ACCESS indicates to the device supporting this action that,
upon consumption of the final granted units, the actions specified in upon consumption of the final granted units, the actions specified in
Filter-Rule AVP(s) MUST restrict the traffic according to the Filter-Rule AVP(s) MUST restrict the traffic according to the
classifiers in the Filter-Rule AVP(s). If Filter-Id AVP(s) are classifiers in the Filter-Rule AVP(s). If Filter-Id AVP(s) are
provided in the Credit-Control-Answer message, the credit control provided in the Credit-Control-Answer message, the credit control
client MUST restrict the traffic according to the IP packet filters client MUST restrict the traffic according to the IP packet filters
identified by the Filter-Id AVP(s). The credit-control server SHOULD identified by the Filter-Id AVP(s). The credit-control server SHOULD
include either the Filter-Rule AVP or the Filter-Id AVP in the include either the Filter-Rule AVP or the Filter-Id AVP in the QoS-
Credit-Control-Answer message. Final-Unit-Indication group AVP of the Credit-Control-Answer message.
If both Final-Unit-Indication AVP and QoS-Final-Unit-Indication AVP If both Final-Unit-Indication AVP and QoS-Final-Unit-Indication AVP
exist in the Credit-Control-Answer message, a credit control client exist in the Credit-Control-Answer message, a credit control client
which supports the QoS-Final-Unit-Indication AVP SHOULD follow the which supports the QoS-Final-Unit-Indication AVP SHOULD follow the
directives included in it. directives included in the QoS-Final-Unit-Indication AVP and SHOULD
ignore the Final-Unit-Indication AVP.
An entity other than the credit-control server may provision the An entity other than the credit-control server may provision the
access device with appropriate IP packet filters to be used in access device with appropriate IP packet filters to be used in
conjunction with the Diameter credit-control application. Such an conjunction with the Diameter credit-control application. Such an
entity may, for instance, configure the access device with IP flows entity may, for instance, configure the access device with IP flows
to be passed when the Diameter credit-control application indicates to be passed when the Diameter credit-control application indicates
RESTRICT_ACCESS or REDIRECT. The access device passes IP packets RESTRICT_ACCESS or REDIRECT. The access device passes IP packets
according to the filter rules that may have been received in the according to the filter rules that may have been received in the
Credit-Control-Answer message in addition to those that may have been Credit-Control-Answer message in addition to those that may have been
configured by the other entity. However, when the user's account configured by the other entity. However, when the user's account
skipping to change at page 52, line 25 skipping to change at page 52, line 25
| PendingI | Failure to send, or temporary | Grant | Idle | | PendingI | Failure to send, or temporary | Grant | Idle |
| | error and CCFH equal to | service to | | | | error and CCFH equal to | service to | |
| | CONTINUE | end user | | | | CONTINUE | end user | |
| PendingI | Failure to send, or temporary | Terminate | Idle | | PendingI | Failure to send, or temporary | Terminate | Idle |
| | error and CCFH equal to | end user's | | | | error and CCFH equal to | end user's | |
| | TERMINATE or to | service | | | | TERMINATE or to | service | |
| | RETRY_AND_TERMINATE | | | | | RETRY_AND_TERMINATE | | |
| PendingI | Tx expired and CCFH equal to | Terminate | Idle | | PendingI | Tx expired and CCFH equal to | Terminate | Idle |
| | TERMINATE | end user's | | | | TERMINATE | end user's | |
| | | service | | | | | service | |
| PendingI | Tx expired and CCFH equal to | Grant | Idle | | PendingI | Tx expired and CCFH equal to | Grant | PendingI |
| | CONTINUE or to | service to | | | | CONTINUE or to | service to | |
| | RETRY_AND_TERMINATE | end user | | | | RETRY_AND_TERMINATE | end user | |
| PendingI | CC initial answer received | Terminate | Idle | | PendingI | CC initial answer received | Terminate | Idle |
| | with result code | end user's | | | | with result code | end user's | |
| | END_USER_SERVICE_DENIED or | service | | | | END_USER_SERVICE_DENIED or | service | |
| | USER_UNKNOWN | | | | | USER_UNKNOWN | | |
| PendingI | CC initial answer received | Grant | Idle | | PendingI | CC initial answer received | Grant | Idle |
| | with result code equal to | service to | | | | with result code equal to | service to | |
| | CREDIT_CONTROL_NOT_APPLICABLE | end user | | | | CREDIT_CONTROL_NOT_APPLICABLE | end user | |
| PendingI | Failed CC initial answer | Grant | Idle | | PendingI | Failed CC initial answer | Grant | Idle |
skipping to change at page 53, line 10 skipping to change at page 53, line 10
| | | event | | | | | event | |
+----------+-------------------------------+-------------+----------+ +----------+-------------------------------+-------------+----------+
Table 3: CLIENT, SESSION BASED for the first interrogation with CCR Table 3: CLIENT, SESSION BASED for the first interrogation with CCR
+----------+-------------------------------+-------------+----------+ +----------+-------------------------------+-------------+----------+
| State | Event | Action | New | | State | Event | Action | New |
| | | | State | | | | | State |
+----------+-------------------------------+-------------+----------+ +----------+-------------------------------+-------------+----------+
| Open | Granted unit elapses and no | Send CC | PendingU | | Open | Granted unit elapses and no | Send CC | PendingU |
| | final unit indication | update req. | | | | final unit indication | update | |
| | received | | | | | received | req., start | |
| | | Tx | |
| Open | Granted unit elapses and | Terminate | PendingT | | Open | Granted unit elapses and | Terminate | PendingT |
| | final unit action equal to | end user's | | | | final unit action equal to | end user's | |
| | TERMINATE received | service, | | | | TERMINATE received | service, | |
| | | send CC | | | | | send CC | |
| | | termination | | | | | termination | |
| | | req. | | | | | req. | |
| Open | Change in rating condition in | Send CC | PendingU | | Open | Change in rating condition in | Send CC | PendingU |
| | queue | update | | | | queue | update | |
| | | req., Start | | | | | req., Start | |
| | | Tx | | | | | Tx | |
skipping to change at page 54, line 6 skipping to change at page 54, line 7
| | RETRY_AND_TERMINATE | | | | | RETRY_AND_TERMINATE | | |
| PendingU | Tx expired and CCFH equal to | Terminate | Idle | | PendingU | Tx expired and CCFH equal to | Terminate | Idle |
| | TERMINATE | end user's | | | | TERMINATE | end user's | |
| | | service | | | | | service | |
| PendingU | Tx expired and CCFH equal to | Grant | PendingU | | PendingU | Tx expired and CCFH equal to | Grant | PendingU |
| | CONTINUE or to | service to | | | | CONTINUE or to | service to | |
| | RETRY_AND_TERMINATE | end user | | | | RETRY_AND_TERMINATE | end user | |
| PendingU | CC update answer received | Terminate | Idle | | PendingU | CC update answer received | Terminate | Idle |
| | with result code | end user's | | | | with result code | end user's | |
| | END_USER_SERVICE_DENIED | service | | | | END_USER_SERVICE_DENIED | service | |
| PendingU | CC update answer received | Terminate | Idle | | PendingU | CC update answer received | Grant | Idle |
| | with result code equal to | end user's | | | | with result code equal to | service to | |
| | CREDIT_CONTROL_NOT_APPLICABLE | service | | | | CREDIT_CONTROL_NOT_APPLICABLE | end user | |
| PendingU | Failed CC update answer | Grant | Idle | | PendingU | Failed CC update answer | Grant | Idle |
| | received and CCFH equal to | service to | | | | received and CCFH equal to | service to | |
| | CONTINUE | end user | | | | CONTINUE | end user | |
| PendingU | Failed CC update answer | Terminate | Idle | | PendingU | Failed CC update answer | Terminate | Idle |
| | received and CCFH equal to | end user's | | | | received and CCFH equal to | end user's | |
| | TERMINATE or to | service | | | | TERMINATE or to | service | |
| | RETRY_AND_TERMINATE | | | | | RETRY_AND_TERMINATE | | |
| PendingU | User service terminated | Queue | PendingU | | PendingU | User service terminated | Queue | PendingU |
| | | termination | | | | | termination | |
| | | event | | | | | event | |
skipping to change at page 54, line 46 skipping to change at page 54, line 47
| State | Event | Action | New | | State | Event | Action | New |
| | | | State | | | | | State |
+----------+--------------------------------+------------+----------+ +----------+--------------------------------+------------+----------+
| Idle | Client or device requests a | Send CC | PendingE | | Idle | Client or device requests a | Send CC | PendingE |
| | one-time service | event | | | | one-time service | event | |
| | | req., | | | | | req., | |
| | | Start Tx | | | | | Start Tx | |
| Idle | Request in storage | Send | PendingB | | Idle | Request in storage | Send | PendingB |
| | | stored | | | | | stored | |
| | | request | | | | | request | |
| PendingE | Grant service to end user | Send | Idle | | PendingE | Successful CC event answer | Grant | Idle |
| | | stored | | | | received | service to | |
| | | request | | | | | end user | |
| PendingE | Failure to send, temporary | Indicate | Idle | | PendingE | Failure to send, temporary | Indicate | Idle |
| | error, failed CC event answer | service | | | | error, failed CC event answer | service | |
| | received, or Tx expired; | error | | | | received, or Tx expired; | error | |
| | requested action CHECK_BALANCE | | | | | requested action CHECK_BALANCE | | |
| | or PRICE_ENQUIRY | | | | | or PRICE_ENQUIRY | | |
| PendingE | CC event answer received with | Terminate | Idle | | PendingE | CC event answer received with | Terminate | Idle |
| | result code | end user's | | | | result code | end user's | |
| | END_USER_SERVICE_DENIED or | service | | | | END_USER_SERVICE_DENIED or | service | |
| | USER_UNKNOWN and Tx running | | | | | USER_UNKNOWN and Tx running | | |
| PendingE | CC event answer received with | Grant | Idle | | PendingE | CC event answer received with | Grant | Idle |
skipping to change at page 55, line 33 skipping to change at page 55, line 34
| | DIRECT_DEBITING; DDFH equal to | | | | | DIRECT_DEBITING; DDFH equal to | | |
| | TERMINATE_OR_BUFFER and Tx | | | | | TERMINATE_OR_BUFFER and Tx | | |
| | running | | | | | running | | |
| PendingE | Tx expired; requested action | Grant | PendingE | | PendingE | Tx expired; requested action | Grant | PendingE |
| | DIRECT_DEBITING | service to | | | | DIRECT_DEBITING | service to | |
| | | end user | | | | | end user | |
| PendingE | Failure to send; requested | Store | Idle | | PendingE | Failure to send; requested | Store | Idle |
| | action DIRECT_DEBITING; DDFH | request | | | | action DIRECT_DEBITING; DDFH | request | |
| | equal to TERMINATE_OR_BUFFER | with | | | | equal to TERMINATE_OR_BUFFER | with | |
| | | T-flag | | | | | T-flag | |
| PendingE | Failure to send; requested | Store | Idle |
| | action DIRECT_DEBITING; DDFH | request | |
| | equal to TERMINATE_OR_BUFFER | with | |
| | | T-flag | |
| PendingE | Temporary error; requested | Store | Idle | | PendingE | Temporary error; requested | Store | Idle |
| | action DIRECT_DEBITING; DDFH | request | | | | action DIRECT_DEBITING; DDFH | request | |
| | equal to TERMINATE_OR_BUFFER; | | | | | equal to TERMINATE_OR_BUFFER; | | |
| | Tx expired | | | | | Tx expired | | |
| PendingE | Failed answer or answer | | Idle | | PendingE | Failed answer or answer | | Idle |
| | received with result code | | | | | received with result code | | |
| | END_USER_SERVICE DENIED or | | | | | END_USER_SERVICE DENIED or | | |
| | USER_UNKNOWN; requested action | | | | | USER_UNKNOWN; requested action | | |
| | DIRECT_DEBITING; Tx expired | | | | | DIRECT_DEBITING; Tx expired | | |
| PendingE | Failed CC event answer | Indicate | Idle | | PendingE | Failed CC event answer | Indicate | Idle |
| | received; requested action | service | | | | received; requested action | service | |
| | REFUND_ACCOUNT | error and | | | | REFUND_ACCOUNT | error and | |
| | | delete | | | | | delete | |
| | | request | | | | | request | |
| PendingE | Failure to send or Tx expired; | Store | Idle | | PendingE | Failure to send or Tx expired; | Store | Idle |
| | requested action | request | | | | requested action | request | |
| | REFUND_ACCOUNT | with | | | | REFUND_ACCOUNT | with | |
| | | T-flag | | | | | T-flag | |
| PendingE | Temporary error, and requested | Store | Idle | | PendingE | Temporary error, and requested | Store | Idle |
| | action REFUND_ACCOUNT | request | | | | action REFUND_ACCOUNT | request | |
| PendingE | Successful CC answer received | Delete | Idle | | PendingB | Successful CC answer received | Delete | Idle |
| | | request | | | | | request | |
| PendingE | Failed CC answer received | Delete | Idle | | PendingB | Failed CC answer received | Delete | Idle |
| | | request | | | | | request | |
| PendingE | Failure to send or temporary | | Idle | | PendingB | Failure to send or temporary | | Idle |
| | error | | | | | error | | |
+----------+--------------------------------+------------+----------+ +----------+--------------------------------+------------+----------+
CLIENT, EVENT BASED Table 5: CLIENT, EVENT BASED
+-------+------------------------+--------------------------+-------+ +-------+------------------------+--------------------------+-------+
| State | Event | Action | New | | State | Event | Action | New |
| | | | State | | | | | State |
+-------+------------------------+--------------------------+-------+ +-------+------------------------+--------------------------+-------+
| Idle | CC initial request | Send CC initial answer, | Open | | Idle | CC initial request | Send CC initial answer, | Open |
| | received and | reserve units, start Tcc | | | | received and | reserve units, start Tcc | |
| | successfully processed | | | | | successfully processed | | |
| Idle | CC initial request | Send CC initial answer | Idle | | Idle | CC initial request | Send CC initial answer | Idle |
| | received but not | with Result-Code != | | | | received but not | with Result-Code != | |
skipping to change at page 57, line 40 skipping to change at page 56, line 51
| | received and | Stop Tcc, debit used | | | | received and | Stop Tcc, debit used | |
| | successfully processed | units | | | | successfully processed | units | |
| Open | CC termination request | Send CC termin. answer | Idle | | Open | CC termination request | Send CC termin. answer | Idle |
| | received but not | with Result-Code != | | | | received but not | with Result-Code != | |
| | successfully processed | SUCCESS, debit used | | | | successfully processed | SUCCESS, debit used | |
| | | units | | | | | units | |
| Open | Session supervision | Release reserved units | Idle | | Open | Session supervision | Release reserved units | Idle |
| | timer Tcc expired | | | | | timer Tcc expired | | |
+-------+------------------------+--------------------------+-------+ +-------+------------------------+--------------------------+-------+
SERVER, SESSION AND EVENT BASED Table 6: SERVER, SESSION AND EVENT BASED
8. Credit-Control AVPs 8. Credit-Control AVPs
This section defines the credit-control AVPs that are specific to This section defines the credit-control AVPs that are specific to
Diameter credit-control application and that MAY be included in the Diameter credit-control application and that MAY be included in the
Diameter credit-control messages. Diameter credit-control messages.
The AVPs defined in this section MAY also be included in The AVPs defined in this section MAY also be included in
authorization commands defined in authorization-specific authorization commands defined in authorization-specific
applications, such as [RFC7155] and [RFC4004], if the first applications, such as [RFC7155] and [RFC4004], if the first
skipping to change at page 58, line 41 skipping to change at page 58, line 4
CC-Time 420 8.21 Unsigned32 | M | | V | CC-Time 420 8.21 Unsigned32 | M | | V |
CC-Total-Octets 421 8.23 Unsigned64 | M | | V | CC-Total-Octets 421 8.23 Unsigned64 | M | | V |
CC-Unit-Type 454 8.32 Enumerated | M | | V | CC-Unit-Type 454 8.32 Enumerated | M | | V |
Check-Balance- 422 8.6 Enumerated | M | | V | Check-Balance- 422 8.6 Enumerated | M | | V |
Result | | | | Result | | | |
Cost-Information 423 8.7 Grouped | M | | V | Cost-Information 423 8.7 Grouped | M | | V |
Cost-Unit 424 8.12 UTF8String | M | | V | Cost-Unit 424 8.12 UTF8String | M | | V |
Credit-Control 426 8.13 Enumerated | M | | V | Credit-Control 426 8.13 Enumerated | M | | V |
Credit-Control- 427 8.14 Enumerated | M | | V | Credit-Control- 427 8.14 Enumerated | M | | V |
Failure-Handling | | | | Failure-Handling | | | |
Currency-Code 425 8.11 Unsigned32 | M | | V | Currency-Code 425 8.11 Unsigned32 | M | | V |
Direct-Debiting- 428 8.15 Enumerated | M | | V | Direct-Debiting- 428 8.15 Enumerated | M | | V |
Failure-Handling | | | | Failure-Handling | | | |
Exponent 429 8.9 Integer32 | M | | V | Exponent 429 8.9 Integer32 | M | | V |
Final-Unit-Action 449 8.35 Enumerated | M | | V | Final-Unit-Action 449 8.35 Enumerated | M | | V |
Final-Unit- 430 8.34 Grouped | M | | V | Final-Unit- 430 8.34 Grouped | M | | V |
Indication | | | | Indication | | | |
QoS-Final-Unit- TBD18 8.69 Grouped | | M | V | QoS-Final-Unit- TBD17 8.68 Grouped | | M | V |
Indication | | | | Indication | | | |
Granted-Service- 431 8.17 Grouped | M | | V | Granted-Service- 431 8.17 Grouped | M | | V |
Unit | | | | Unit | | | |
G-S-U-Pool- 453 8.31 Unsigned32 | M | | V | G-S-U-Pool- 453 8.31 Unsigned32 | M | | V |
Identifier | | | | Identifier | | | |
G-S-U-Pool- 457 8.30 Grouped | M | | V | G-S-U-Pool- 457 8.30 Grouped | M | | V |
Reference | | | | Reference | | | |
Multiple-Services 456 8.16 Grouped | M | | V | Multiple-Services 456 8.16 Grouped | M | | V |
-Credit-Control | | | | -Credit-Control | | | |
Multiple-Services 455 8.40 Enumerated | M | | V | Multiple-Services 455 8.40 Enumerated | M | | V |
-Indicator | | | | -Indicator | | | |
Rating-Group 432 8.29 Unsigned32 | M | | V | Rating-Group 432 8.29 Unsigned32 | M | | V |
Redirect-Address 433 8.38 Enumerated | M | | V | Redirect-Address 433 8.38 Enumerated | M | | V |
-Type | | | | -Type | | | |
Redirect-Server 434 8.37 Grouped | M | | V | Redirect-Server 434 8.37 Grouped | M | | V |
Redirect-Server 435 8.39 UTF8String | M | | V | Redirect-Server 435 8.39 UTF8String | M | | V |
-Address | | | | -Address | | | |
Redirect-Server TBD13 8.64 Grouped | | M | V | Redirect-Server TBD13 8.64 Grouped | | M | V |
-Extension | | | | -Extension | | | |
Redirect-Address TBD14 8.65 UTF8String | | M | V | Redirect-Address TBD14 8.65 Address | | M | V |
-IPv4Address | | | | -IPAddress | | | |
Redirect-Address TBD15 8.66 UTF8String | | M | V | Redirect-Address TBD15 8.66 UTF8String | | M | V |
-IPv6Address | | | |
Redirect-Address TBD16 8.67 UTF8String | | M | V |
-URL | | | | -URL | | | |
Redirect-Address TBD17 8.68 UTF8String | | M | V | Redirect-Address TBD16 8.67 UTF8String | | M | V |
-SIP-URI | | | | -SIP-URI | | | |
Requested-Action 436 8.41 Enumerated | M | | V | Requested-Action 436 8.41 Enumerated | M | | V |
Requested-Service 437 8.18 Grouped | M | | V | Requested-Service 437 8.18 Grouped | M | | V |
-Unit | | | | -Unit | | | |
Restriction 438 8.36 IPFiltrRule| M | | V | Restriction 438 8.36 IPFiltrRule| M | | V |
-Filter-Rule | | | | -Filter-Rule | | | |
Service-Context 461 8.42 UTF8String | M | | V | Service-Context 461 8.42 UTF8String | M | | V |
-Id | | | | -Id | | | |
Service- 439 8.28 Unsigned32 | M | | V | Service- 439 8.28 Unsigned32 | M | | V |
Identifier | | | | Identifier | | | |
skipping to change at page 74, line 43 skipping to change at page 73, line 43
execute the specified action immediately. If the home service execute the specified action immediately. If the home service
provider policy is to terminate the service, naturally, the server provider policy is to terminate the service, naturally, the server
SHOULD return the appropriate transient failure (see Section 9.1) in SHOULD return the appropriate transient failure (see Section 9.1) in
order to implement the policy-defined action. order to implement the policy-defined action.
The Final-Unit-Action AVP defines the behavior of the service element The Final-Unit-Action AVP defines the behavior of the service element
when the user's account cannot cover the cost of the service and MUST when the user's account cannot cover the cost of the service and MUST
always be present if the Final-Unit-Indication AVP is included in a always be present if the Final-Unit-Indication AVP is included in a
command. command.
If the Final-Unit-Action AVP is set to TERMINATE, no other AVPs MUST If the Final-Unit-Action AVP is set to TERMINATE, the Final-Unit-
be present. Indication group MUST NOT contain any other AVPs.
If the Final-Unit-Action AVP is set to REDIRECT at least the If the Final-Unit-Action AVP is set to REDIRECT at least the
Redirect-Server AVP MUST be present. The Restriction-Filter-Rule AVP Redirect-Server AVP MUST be present. The Restriction-Filter-Rule AVP
or the Filter-Id AVP MAY be present in the Credit-Control-Answer or the Filter-Id AVP MAY be present in the Credit-Control-Answer
message if the user is also allowed to access other services that are message if the user is also allowed to access other services that are
not accessible through the address given in the Redirect-Server AVP. not accessible through the address given in the Redirect-Server AVP.
If the Final-Unit-Action AVP is set to RESTRICT_ACCESS, either the If the Final-Unit-Action AVP is set to RESTRICT_ACCESS, either the
Restriction-Filter-Rule AVP or the Filter-Id AVP SHOULD be present. Restriction-Filter-Rule AVP or the Filter-Id AVP SHOULD be present.
The Filter-Id AVP is defined in [RFC7155]. The Filter-Id AVP can be The Filter-Id AVP is defined in [RFC7155]. The Filter-Id AVP can be
used to reference an IP filter list installed in the access device by used to reference an IP filter list installed in the access device by
means other than the Diameter credit-control application, e.g., means other than the Diameter credit-control application, e.g.,
locally configured or configured by another entity. locally configured or configured by another entity.
If the type of Final-Unit-Action AVP is set to REDIRECT and the type If the Final-Unit-Action AVP is set to REDIRECT and the type of
of server is not one of the types in the Redirect-Server-Type AVP, server is not one of the enumerations in the Redirect-Address-Type
then the QoS-Final-Unit-Indication AVP SHOULD be used together with AVP, then the QoS-Final-Unit-Indication AVP SHOULD be used together
the Redirect-Server-Extension AVP instead of the Final-Unit- with the Redirect-Server-Extension AVP instead of the Final-Unit-
Indication AVP. Indication AVP.
If the type of Final-Unit-Action AVP is set to RESTRICT_ACCESS or If the Final-Unit-Action AVP is set to RESTRICT_ACCESS or REDIRECT
REDIRECT and the classification of the restricted traffic cannot be and the classification of the restricted traffic cannot be expressed
expressed using IPFilterRule, or different actions (e.g., QoS) than using IPFilterRule, or different actions (e.g., QoS) than just
just allowing QoS needs to be enforced traffic, then the QoS-Final- allowing QoS needs to be enforced traffic, then the QoS-Final-Unit-
Unit-Indication AVP SHOULD be used instead of the Final-Unit- Indication AVP SHOULD be used instead of the Final-Unit-Indication
Indication AVP. However, if the credit control server wants to AVP. However, if the credit control server wants to preserve
preserve backward compatibility with credit-control clients that backward compatibility with credit-control clients that support only
support only [RFC4006], the Final-Unit-Indication AVP SHOULD be used [RFC4006], the Final-Unit-Indication AVP SHOULD be used together with
together with the Filter-Id AVP. the Filter-Id AVP.
The Final-Unit-Indication AVP is defined as follows (per the grouped- The Final-Unit-Indication AVP is defined as follows (per the grouped-
avp-def of [RFC6733]): avp-def of [RFC6733]):
Final-Unit-Indication ::= < AVP Header: 430 > Final-Unit-Indication ::= < AVP Header: 430 >
{ Final-Unit-Action } { Final-Unit-Action }
*[ Restriction-Filter-Rule ] *[ Restriction-Filter-Rule ]
*[ Filter-Id ] *[ Filter-Id ]
[ Redirect-Server ] [ Redirect-Server ]
skipping to change at page 76, line 16 skipping to change at page 75, line 16
REDIRECT 1 REDIRECT 1
The service element MUST redirect the user to the address specified The service element MUST redirect the user to the address specified
in the Redirect-Server-Address AVP or one of the AVPs included in the in the Redirect-Server-Address AVP or one of the AVPs included in the
Redirect-Server-Extension AVP. The redirect action is defined in Redirect-Server-Extension AVP. The redirect action is defined in
Section 5.6.2. Section 5.6.2.
RESTRICT_ACCESS 2 RESTRICT_ACCESS 2
The access device MUST restrict the user access according to the IP The access device MUST restrict the user access according to the
packet filters defined in the Restriction-Filter-Rule AVP, the filter AVPs contained in the applied grouped AVP: according to IP
Filter-Rule AVP or according to the IP packet filters identified by packet filters defined in the Restriction-Filter-Rule AVP, according
the Filter-Id AVP. All the packets not matching the filters MUST be to the packet classifier filters defined in Filter-Rule AVP, or
dropped (see Section 5.6.3). In the case that Restriction-Filter- according to the packet filters identified by the Filter-Id AVP. All
Rule AVP is used, all the packets matching the filters MUST be the packets not matching any filters MUST be dropped (see
allowed. In the case that Filter-Rule AVP or Filter-Id AVP are used, Section 5.6.3).
other actions (e.g., QoS) may be deployed on the packets matching the
filters.
8.36. Restriction-Filter-Rule AVP 8.36. Restriction-Filter-Rule AVP
The Restriction-Filter-Rule AVP (AVP Code 438) is of type The Restriction-Filter-Rule AVP (AVP Code 438) is of type
IPFilterRule and provides filter rules corresponding to services that IPFilterRule and provides filter rules corresponding to services that
are to remain accessible even if there are no more service units are to remain accessible even if there are no more service units
granted. The access device has to configure the specified filter granted. The access device has to configure the specified filter
rules for the subscriber and MUST drop all the packets not matching rules for the subscriber and MUST drop all the packets not matching
these filters. Zero, one, or more such AVPs MAY be present in a these filters. Zero, one, or more such AVPs MAY be present in a
Credit-Control-Answer message or in an AA answer message. Credit-Control-Answer message or in an AA answer message.
skipping to change at page 77, line 21 skipping to change at page 76, line 21
The address type can be one of the following: The address type can be one of the following:
IPv4 Address 0 IPv4 Address 0
The address type is in the form of "dotted-decimal" IPv4 address, as The address type is in the form of "dotted-decimal" IPv4 address, as
defined in [RFC0791]. defined in [RFC0791].
IPv6 Address 1 IPv6 Address 1
The address type is in the form of IPv6 address, as defined in The address type is in the form of IPv6 address, as defined in
[RFC4291]. The address is a text representation of the address [RFC4291]. The address MUST conform to the text representation of
according to [RFC5952]. the address according to [RFC5952].
URL 2 URL 2
The address type is in the form of Uniform Resource Locator, as The address type is in the form of Uniform Resource Locator, as
defined in [RFC1738]. defined in [RFC1738].
SIP URI 3 SIP URI 3
The address type is in the form of SIP Uniform Resource Identifier, The address type is in the form of SIP Uniform Resource Identifier,
as defined in [RFC3261]. as defined in [RFC3261].
skipping to change at page 83, line 17 skipping to change at page 82, line 17
The User-Equipment-Info-Value AVP (AVP Code 460) is of type The User-Equipment-Info-Value AVP (AVP Code 460) is of type
OctetString. The User-Equipment-Info-Type AVP defines which type of OctetString. The User-Equipment-Info-Type AVP defines which type of
identifier is used. identifier is used.
8.52. User-Equipment-Info-Extension AVP 8.52. User-Equipment-Info-Extension AVP
The User-Equipment-Info-Extension AVP (AVP Code TBD1) is of type The User-Equipment-Info-Extension AVP (AVP Code TBD1) is of type
Grouped and allows the credit-control client to indicate the identity Grouped and allows the credit-control client to indicate the identity
and capability of the terminal the subscriber is using for the and capability of the terminal the subscriber is using for the
connection to network. If the type of the equipment is one of the connection to network. If the type of the equipment is one of the
types listed in the User-Equipment-Info-Type AVP, then the credit- enumerated types of User-Equipment-Info-Type AVP, then the credit-
control client SHOULD send the information in the User-Equipment-Info control client SHOULD send the information in the User-Equipment-Info
AVP, in addition to or instead of the User-Equipment-Info-Extension AVP, in addition to or instead of the User-Equipment-Info-Extension
AVP. This is in order to preserve backward compatibility with AVP. This is in order to preserve backward compatibility with
credit-control servers that support only RFC4006. Exactly one AVP credit-control servers that support only RFC4006. Exactly one AVP
MUST be included inside the User-Equipment-Info-Extension AVP. MUST be included inside the User-Equipment-Info-Extension AVP.
It is defined as follows (per the grouped-avp-def of [RFC6733]): It is defined as follows (per the grouped-avp-def of [RFC6733]):
User-Equipment-Info-Extension ::= < AVP Header: TBD1 > User-Equipment-Info-Extension ::= < AVP Header: TBD1 >
[ User-Equipment-Info-IMEISV ] [ User-Equipment-Info-IMEISV ]
[ User-Equipment-Info-MAC ] [ User-Equipment-Info-MAC ]
[ User-Equipment-Info-EUI64 ] [ User-Equipment-Info-EUI64 ]
[ User-Equipment-Info-ModifiedEUI64 ] [ User-Equipment-Info-ModifiedEUI64 ]
[ User-Equipment-Info-IMEI ] [ User-Equipment-Info-IMEI ]
*[ AVP ] [ AVP ]
8.53. User-Equipment-Info-IMEISV AVP 8.53. User-Equipment-Info-IMEISV AVP
The User-Equipment-Info-IMEISV (AVP Code TBD2) is of type The User-Equipment-Info-IMEISV (AVP Code TBD2) is of type
OctetString. The User-Equipment-Info-IMEISV AVP contains the OctetString. The User-Equipment-Info-IMEISV AVP contains the
International Mobile Equipment Identifier and Software Version in the International Mobile Equipment Identifier and Software Version in the
international IMEISV format according to 3GPP TS 23.003 [TGPPIMEI]. international IMEISV format according to 3GPP TS 23.003 [TGPPIMEI].
8.54. User-Equipment-Info-MAC AVP 8.54. User-Equipment-Info-MAC AVP
skipping to change at page 84, line 28 skipping to change at page 83, line 28
The User-Equipment-Info-IMEI (AVP Code TBD6) is of type OctetString. The User-Equipment-Info-IMEI (AVP Code TBD6) is of type OctetString.
The User-Equipment-Info-IMEI AVP contains the International Mobile The User-Equipment-Info-IMEI AVP contains the International Mobile
Equipment Identifier in the international IMEI format according to Equipment Identifier in the international IMEI format according to
3GPP TS 23.003 [TGPPIMEI]. 3GPP TS 23.003 [TGPPIMEI].
8.58. Subscription-Id-Extension AVP 8.58. Subscription-Id-Extension AVP
The Subscription-Id-Extension AVP (AVP Code TBD7) is used to identify The Subscription-Id-Extension AVP (AVP Code TBD7) is used to identify
the end user's subscription and is of type Grouped. The the end user's subscription and is of type Grouped. The
Subscription-Id-Extension AVP contains an included AVP holding the Subscription-Id-Extension group AVP MUST include an AVP holding the
subscription identifier itself. The type of this included AVP subscription identifier. The type of this included AVP indicates the
indicates the type of the subscription identifier. The existing type of the subscription identifier. For each of the enumerated
identifier types are listed in the Subscription-Id-Type AVP. For values of the Subscription-Id-Type AVP, there is a corresponding sub-
each existing identifier type there is a separate sub-AVP AVP for use within the Subscription-Id-Extension group AVP. If a new
corresponding to it. If a new identifier type is required a identifier type is required a corresponding new sub-AVP SHOULD be
corresponding new sub-AVP SHOULD be defined. defined for use within the Subscription-Id-Extension group AVP.
If full backward compatibility with [RFC4006] is required, then the If full backward compatibility with [RFC4006] is required, then the
Subscription-Id AVP MUST be used to carry out identifier types listed Subscription-Id AVP MUST be used to indicate identifier types
in the Subscription-Id-Type AVP. While Subscription-Id-Extension AVP enumerated in the Subscription-Id-Type AVP, whereas the Subscription-
MUST be used only for newly defined identifier types. If full Id-Extension AVP MUST be used only for newly defined identifier
backward compatibility with [RFC4006] is not required, then the types. If full backward compatibility with [RFC4006] is not
Subscription-Id-Extension AVP MAY be used to carry out the existing required, then the Subscription-Id-Extension AVP MAY be used to carry
identifier types. In this case, Subscription-Id-Extension AVP MAY be out the existing identifier types. In this case, Subscription-Id-
sent together with Subscription-Id AVP. Extension AVP MAY be sent together with Subscription-Id AVP.
Exactly one sub-AVP MUST be included inside the Subscription-Id- Exactly one sub-AVP MUST be included inside the Subscription-Id-
Extension AVP. Extension AVP.
It is defined as follows (per the grouped-avp-def of [RFC6733]): It is defined as follows (per the grouped-avp-def of [RFC6733]):
Subscription-Id-Extension ::= < AVP Header: TBD7 > Subscription-Id-Extension ::= < AVP Header: TBD7 >
[ Subscription-Id-E164 ] [ Subscription-Id-E164 ]
[ Subscription-Id-IMSI ] [ Subscription-Id-IMSI ]
[ Subscription-Id-SIP-URI ] [ Subscription-Id-SIP-URI ]
[ Subscription-Id-NAI ] [ Subscription-Id-NAI ]
[ Subscription-Id-Private ] [ Subscription-Id-Private ]
*[ AVP ] [ AVP ]
8.59. Subscription-Id-E164 AVP 8.59. Subscription-Id-E164 AVP
The Subscription-Id-E164 (AVP Code TBD8) is of type UTF8String. The The Subscription-Id-E164 (AVP Code TBD8) is of type UTF8String. The
Subscription-Id-E164 AVP contains the international E.164 format Subscription-Id-E164 AVP contains the international E.164 format
(e.g., MSISDN), according to the ITU-T E.164 numbering plan defined (e.g., MSISDN), according to the ITU-T E.164 numbering plan defined
in [E164] and [CE164]. in [E164] and [CE164].
8.60. Subscription-Id-IMSI AVP 8.60. Subscription-Id-IMSI AVP
skipping to change at page 86, line 5 skipping to change at page 85, line 5
private identifier. private identifier.
8.64. Redirect-Server-Extension AVP 8.64. Redirect-Server-Extension AVP
The Redirect-Server-Extension AVP (AVP Code TBD13) is of type Grouped The Redirect-Server-Extension AVP (AVP Code TBD13) is of type Grouped
and contains the address information of the redirect server (e.g., and contains the address information of the redirect server (e.g.,
HTTP redirect server, SIP Server) with which the end user is to be HTTP redirect server, SIP Server) with which the end user is to be
connected when the account cannot cover the service cost. It MUST be connected when the account cannot cover the service cost. It MUST be
present inside the QoS-Final-Unit-Indication AVP when the Final-Unit- present inside the QoS-Final-Unit-Indication AVP when the Final-Unit-
Action AVP is set to REDIRECT. If the type of the redirect server is Action AVP is set to REDIRECT. If the type of the redirect server is
one of the types listed in the Redirect-Address-Type AVP, then the one of the enumerated values of the Redirect-Address-Type AVP, then
credit-control server SHOULD send the information in the Redirect- the credit-control server SHOULD send the information in the
Server AVP, in addition to or instead of the Redirect-Server- Redirect-Server AVP, in addition to or instead of the Redirect-
Extension AVP. This is in order to preserve backward compatibility Server-Extension AVP. This is in order to preserve backward
with credit-control clients that support only [RFC4006]. Exactly compatibility with credit-control clients that support only
only one AVP MUST be included inside the Redirect-Server-Extension [RFC4006]. Exactly one AVP MUST be included inside the Redirect-
AVP. Server-Extension AVP.
It is defined as follows (per the grouped-avp-def of [RFC6733]): It is defined as follows (per the grouped-avp-def of [RFC6733]):
Redirect-Server-Extension ::= < AVP Header: TBD13 > Redirect-Server-Extension ::= < AVP Header: TBD13 >
[ Redirect-Address-IPv4Address ] [ Redirect-Address-IPAddress ]
[ Redirect-Address-IPv6Address ]
[ Redirect-Address-URL ] [ Redirect-Address-URL ]
[ Redirect-Address-SIP-URI ] [ Redirect-Address-SIP-URI ]
*[ AVP ] [ AVP ]
8.65. Redirect-Address-IPv4Address AVP
The Redirect-Address-IPv4Address AVP (AVP Code TBD14) is of type 8.65. Redirect-Address-IPAddress AVP
UTF8String and defines the address of the redirect server with which
the end user is to be connected when the account cannot cover the
service cost. When the address type of the redirect server is in the
form of "dotted-decimal" IPv4 address, as defined in [RFC0791].
8.66. Redirect-Address-IPv6Address AVP The Redirect-Address-IPAddress AVP (AVP Code TBD14) is of type
Address and defines the IPv4 or IPv6 address of the redirect server
with which the end user is to be connected when the account cannot
cover the service cost.
The Redirect-Address-IPv6Address AVP (AVP Code TBD15) is of type When encoded as an IPv6 address in 16 bytes, the IPv4-mapped IPv6
UTF8String and defines the address of the redirect server with which format [RFC4291] MAY be used to indicate an IPv4 address.
the end user is to be connected when the account cannot cover the
service cost. When the address type is in the form of IPv6 address,
as defined in [RFC4291]. The address is a text representation of the
address according to [RFC5952].
8.67. Redirect-Address-URL AVP 8.66. Redirect-Address-URL AVP
The Redirect-Address-URL AVP (AVP Code TBD16) is of type UTF8String The Redirect-Address-URL AVP (AVP Code TBD15) is of type UTF8String
and defines the address of the redirect server with which the end and defines the address of the redirect server with which the end
user is to be connected when the account cannot cover the service user is to be connected when the account cannot cover the service
cost. When the address type is in the form of Uniform Resource cost. The address type is in the form of Uniform Resource Locator,
Locator, as defined in [RFC1738]. as defined in [RFC1738].
8.68. Redirect-Address-SIP-URI AVP 8.67. Redirect-Address-SIP-URI AVP
The Redirect-Address-SIP-URI AVP (AVP Code TBD17) is of type The Redirect-Address-SIP-URI AVP (AVP Code TBD16) is of type
UTF8String and defines the address of the redirect server with which UTF8String and defines the address of the redirect server with which
the end user is to be connected when the account cannot cover the the end user is to be connected when the account cannot cover the
service cost. When the address type is in the form of SIP Uniform service cost. The address type is in the form of SIP Uniform
Resource Identifier, as defined in [RFC3261]. Resource Identifier, as defined in [RFC3261].
8.69. QoS-Final-Unit-Indication AVP 8.68. QoS-Final-Unit-Indication AVP
The QoS-Final-Unit-Indication AVP (AVP Code TBD18) is of type Grouped The QoS-Final-Unit-Indication AVP (AVP Code TBD17) is of type Grouped
and indicates that the Granted-Service-Unit AVP in the Credit- and indicates that the Granted-Service-Unit AVP in the Credit-
Control-Answer, or in the AA answer, contains the final units for the Control-Answer, or in the AA answer, contains the final units for the
service. After these units have expired, the Diameter credit-control service. After these units have expired, the Diameter credit-control
client is responsible for executing the action indicated in the client is responsible for executing the action indicated in the
Final-Unit-Action AVP (see Section 5.6). Final-Unit-Action AVP (see Section 5.6).
If more than one unit type is received in the Credit-Control-Answer, If more than one unit type is received in the Credit-Control-Answer,
the unit type that first expired SHOULD cause the credit-control the unit type that first expired SHOULD cause the credit-control
client to execute the specified action. client to execute the specified action.
skipping to change at page 87, line 40 skipping to change at page 86, line 32
to execute the specified action immediately. If the home service to execute the specified action immediately. If the home service
provider policy is to terminate the service, naturally, the server provider policy is to terminate the service, naturally, the server
SHOULD return the appropriate transient failure (see Section 9.1) in SHOULD return the appropriate transient failure (see Section 9.1) in
order to implement the policy-defined action. order to implement the policy-defined action.
The Final-Unit-Action AVP defines the behavior of the service element The Final-Unit-Action AVP defines the behavior of the service element
when the user's account cannot cover the cost of the service and MUST when the user's account cannot cover the cost of the service and MUST
always be present if the QoS-Final-Unit-Indication AVP is included in always be present if the QoS-Final-Unit-Indication AVP is included in
a command. a command.
If the Final-Unit-Action AVP is set to TERMINATE, no other AVPs MUST If the Final-Unit-Action AVP is set to TERMINATE, the QoS-Final-Unit-
be present. Indication group MUST NOT contain any other AVPs.
If the Final-Unit-Action AVP is set to REDIRECT at least the If the Final-Unit-Action AVP is set to REDIRECT at least the
Redirect-Server-Extension AVP MUST be present. The Filter-Rule AVP Redirect-Server-Extension AVP MUST be present. The Filter-Rule AVP
or the Filter-Id AVP MAY be present in the Credit-Control-Answer or the Filter-Id AVP MAY be present in the Credit-Control-Answer
message if the user is also allowed to access other services that are message if the user is also allowed to access other services that are
not accessible through the address given in the Redirect-Server- not accessible through the address given in the Redirect-Server-
Extension AVP or if the access to these services needs to be limited Extension AVP or if the access to these services needs to be limited
in some way (e.g., QoS). in some way (e.g., QoS).
If the QoS-Final-Unit-Action AVP is set to RESTRICT_ACCESS, either If the Final-Unit-Action AVP is set to RESTRICT_ACCESS, either the
the Filter-Rule AVP or the Filter-Id AVP SHOULD be present. Filter-Rule AVP or the Filter-Id AVP SHOULD be present.
The Filter-Rule AVP is defined in [RFC5777]. The Filter-Rule AVP can The Filter-Rule AVP is defined in [RFC5777]. The Filter-Rule AVP can
be used to define a specific condition and action combination. If be used to define a specific condition and action combination. If
used only with traffic conditions, it should define which traffic used only with traffic conditions, it should define which traffic
should allowed when no more service units are granted. However, if should allowed when no more service units are granted. However, if
QoS or treatment information exists in the AVP, these actions should QoS or treatment information exists in the AVP, these actions should
be executed, e.g., limiting the allowed traffic with certain QoS. be executed, e.g., limiting the allowed traffic with certain QoS.
When multiple Filter-Rule AVPs exist, precedence should be determined When multiple Filter-Rule AVPs exist, precedence should be determined
as defined in [RFC5777]. as defined in [RFC5777].
The Filter-Id AVP is defined in [RFC7155]. The Filter-Id AVP can be The Filter-Id AVP is defined in [RFC7155]. The Filter-Id AVP can be
used to reference an IP filter list installed in the access device by used to reference an IP filter list installed in the access device by
means other than the Diameter credit-control application, e.g., means other than the Diameter credit-control application, e.g.,
locally configured or configured by another entity. locally configured or configured by another entity.
If the type of Final-Unit-Action AVP is set TERMINATE, or set to If the Final-Unit-Action AVP is set to TERMINATE, or set to
RESTRICT_ACCESS and the action required is allow only traffic that RESTRICT_ACCESS and the action required is allow only traffic that
could be classified using an IPFilterRule, or set to REDIRECT of a could be classified using an IPFilterRule, or set to REDIRECT of a
type which is one of the types in the Redirect-Address-Type AVP, then type which is one of the types in the Redirect-Address-Type AVP, then
the credit-control server SHOULD send the information in the Final- the credit-control server SHOULD send the information in the Final-
Unit-Indication AVP, in addition to or instead of the QoS-Final-Unit- Unit-Indication AVP, in addition to or instead of the QoS-Final-Unit-
Indication AVP. This is in order to preserve backward compatibility Indication AVP. This is in order to preserve backward compatibility
with credit-control clients that support only [RFC4006]. with credit-control clients that support only [RFC4006].
The QoS-Final-Unit-Indication AVP is defined as follows (per the The QoS-Final-Unit-Indication AVP is defined as follows (per the
grouped-avp-def of [RFC6733]): grouped-avp-def of [RFC6733]):
QoS-Final-Unit-Indication ::= < AVP Header: TBD18 > QoS-Final-Unit-Indication ::= < AVP Header: TBD17 >
{ Final-Unit-Action } { Final-Unit-Action }
*[ Filter-Rule ] *[ Filter-Rule ]
*[ Filter-Id ] *[ Filter-Id ]
[ Redirect-Server-Extension ] [ Redirect-Server-Extension ]
*[ AVP ] *[ AVP ]
9. Result Code AVP Values 9. Result Code AVP Values
This section defines new Result-Code AVP [RFC6733] values that must This section defines new Result-Code AVP [RFC6733] values that must
be supported by all Diameter implementations that conform to this be supported by all Diameter implementations that conform to this
skipping to change at page 102, line 40 skipping to change at page 101, line 34
BCP 85, RFC 3725, DOI 10.17487/RFC3725, April 2004, BCP 85, RFC 3725, DOI 10.17487/RFC3725, April 2004,
<http://www.rfc-editor.org/info/rfc3725>. <http://www.rfc-editor.org/info/rfc3725>.
[RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., Ed., [RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., Ed.,
and P. McCann, "Diameter Mobile IPv4 Application", and P. McCann, "Diameter Mobile IPv4 Application",
RFC 4004, DOI 10.17487/RFC4004, August 2005, RFC 4004, DOI 10.17487/RFC4004, August 2005,
<http://www.rfc-editor.org/info/rfc4004>. <http://www.rfc-editor.org/info/rfc4004>.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The original authors of RFC4006 are: Harri Hakala, Leena Mattila,
Juha-Pekka Koskinen, Marco Stura, and John Loughney.
The authors would like to thank Bernard Aboba, Jari Arkko, Robert The authors would like to thank Bernard Aboba, Jari Arkko, Robert
Ekblad, Pasi Eronen, Benny Gustafsson, Robert Karlsson, Avi Lior, Ekblad, Pasi Eronen, Benny Gustafsson, Robert Karlsson, Avi Lior,
Paco Marin, Jussi Maki, Jeff Meyer, Anne Narhi, John Prudhoe, Paco Marin, Jussi Maki, Jeff Meyer, Anne Narhi, John Prudhoe,
Christopher Richards, Juha Vallinen, and Mark Watson for their Christopher Richards, Juha Vallinen, and Mark Watson for their
comments and suggestions. comments and suggestions.
Appendix B. Credit-Control Sequences Appendix B. Credit-Control Sequences
B.1. Flow I B.1. Flow I
NAS NAS
skipping to change at page 121, line 26 skipping to change at page 120, line 26
Describe immediate graceful service termination procedure (in Describe immediate graceful service termination procedure (in
Section 5.6). Section 5.6).
Add extensible User-Equipment-Info-Extension AVP and included Add extensible User-Equipment-Info-Extension AVP and included
types (from Section 8.52 to Section 8.57). types (from Section 8.52 to Section 8.57).
Add extensible Subscription-Id-Extension AVP and included types Add extensible Subscription-Id-Extension AVP and included types
(from Section 8.58 to Section 8.63). (from Section 8.58 to Section 8.63).
Add extensible Redirect-Server-Extension AVP and included types Add extensible Redirect-Server-Extension AVP and included types
(from Section 8.64 to Section 8.68). (from Section 8.64 to Section 8.67).
Add extensible QoS-Final-Unit-Indication AVP (in Section 8.69). Add extensible QoS-Final-Unit-Indication AVP (in Section 8.68).
Updated Security Section to include language consistent with Updated Security Section to include language consistent with
structures of latest base protocol specification. structures of latest base protocol specification.
Authors' Addresses Authors' Addresses
Lyle Bertz (editor) Lyle Bertz (editor)
Sprint Sprint
6220 Sprint Parkway 6220 Sprint Parkway
Overland Park, KS 66251 Overland Park, KS 66251
 End of changes. 58 change blocks. 
232 lines changed or deleted 223 lines changed or added

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