draft-ietf-dime-rfc4006bis-04.txt   draft-ietf-dime-rfc4006bis-05.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. Obsoletes: 4006 (if approved) D. Dolson, Ed.
Expires: June 4, 2018 Y. Lifshitz, Ed. Intended status: Standards Track Y. Lifshitz, Ed.
Sandvine Expires: June 23, 2018 Sandvine
December 1, 2017 December 20, 2017
Diameter Credit-Control Application Diameter Credit-Control Application
draft-ietf-dime-rfc4006bis-04 draft-ietf-dime-rfc4006bis-05
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. The Diameter Credit-
Control application as defined in this document obsoletes [RFC4006],
and it must be supported by all new Diameter Credit-Control
Application implementations.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 June 4, 2018. This Internet-Draft will expire on June 23, 2018.
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
(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 5, line 6 skipping to change at page 5, line 8
12.4. Result-Code AVP Values . . . . . . . . . . . . . . . . . 94 12.4. Result-Code AVP Values . . . . . . . . . . . . . . . . . 94
12.5. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . 94 12.5. CC-Request-Type AVP . . . . . . . . . . . . . . . . . . 94
12.6. CC-Session-Failover AVP . . . . . . . . . . . . . . . . 94 12.6. CC-Session-Failover AVP . . . . . . . . . . . . . . . . 94
12.7. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 94 12.7. CC-Unit-Type AVP . . . . . . . . . . . . . . . . . . . . 94
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 . . . . . . . . . . 95
12.11. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 95 12.11. Direct-Debiting-Failure-Handling AVP . . . . . . . . . . 95
12.12. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . 95 12.12. Final-Unit-Action AVP . . . . . . . . . . . . . . . . . 95
12.13. Multiple-Services-Indicator AVP . . . . . . . . . . . . 95 12.13. Multiple-Services-Indicator AVP . . . . . . . . . . . . 95
12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 95 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 . . . . . . . . . . . . . . . . 96
12.17. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . 96 12.17. Tariff-Change-Usage AVP . . . . . . . . . . . . . . . . 96
12.18. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 96 12.18. User-Equipment-Info-Type AVP . . . . . . . . . . . . . . 96
13. Credit-Control Application Related Parameters . . . . . . . . 96 13. Credit-Control Application Related Parameters . . . . . . . . 96
14. Security Considerations . . . . . . . . . . . . . . . . . . . 97 14. Security Considerations . . . . . . . . . . . . . . . . . . . 97
14.1. Direct Connection with Redirects . . . . . . . . . . . . 98 14.1. Direct Connection with Redirects . . . . . . . . . . . . 98
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 98 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 99
15.1. Normative References . . . . . . . . . . . . . . . . . . 98 15.1. Normative References . . . . . . . . . . . . . . . . . . 99
15.2. Informative References . . . . . . . . . . . . . . . . . 100 15.2. Informative References . . . . . . . . . . . . . . . . . 101
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 65, line 38 skipping to change at page 65, line 38
control messages can't be delivered. control messages can't be delivered.
RETRY_AND_TERMINATE 2 RETRY_AND_TERMINATE 2
When the Credit-Control-Failure-Handling AVP is set to When the Credit-Control-Failure-Handling AVP is set to
RETRY_AND_TERMINATE, the credit-control client SHOULD re-send the RETRY_AND_TERMINATE, the credit-control client SHOULD re-send the
request to an alternative server in the case of transport or request to an alternative server in the case of transport or
temporary failures, provided that a failover procedure is supported temporary failures, provided that a failover procedure is supported
in the credit-control server and the credit-control client, and that in the credit-control server and the credit-control client, and that
an alternative server is available. Otherwise, the service SHOULD an alternative server is available. Otherwise, the service SHOULD
not be granted when the credit-control messages can't be delivered. NOT be granted when the credit-control messages can't be delivered.
8.15. Direct-Debiting-Failure-Handling AVP 8.15. Direct-Debiting-Failure-Handling AVP
The Direct-Debiting-Failure-Handling AVP (AVP Code 428) is of type The Direct-Debiting-Failure-Handling AVP (AVP Code 428) is of type
Enumerated. The credit-control client uses information in this AVP Enumerated. The credit-control client uses information in this AVP
to decide what to do if sending credit-control messages (Requested- to decide what to do if sending credit-control messages (Requested-
Action AVP set to DIRECT_DEBITING) to the credit-control server has Action AVP set to DIRECT_DEBITING) to the credit-control server has
been, for instance, temporarily prevented due to a network problem. been, for instance, temporarily prevented due to a network problem.
TERMINATE_OR_BUFFER 0 TERMINATE_OR_BUFFER 0
skipping to change at page 82, line 21 skipping to change at page 82, line 21
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
enumerated types of 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 ]
skipping to change at page 94, line 19 skipping to change at page 94, line 19
Section 1.3 for more information. Section 1.3 for more information.
12.2. Command Codes 12.2. Command Codes
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
This specification assigns the values 411 - 461 from the AVP code See Section 8 for the assignment of the namespace in this
namespace defined in [RFC6733]. See Section 8 for the assignment of specification.
the namespace in this specification.
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
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.6. CC-Session-Failover AVP 12.6. CC-Session-Failover AVP
As defined in Section 8.4, the CC-Failover-Supported AVP includes As defined in Section 8.4, the CC-Failover-Supported AVP includes
Enumerated type values 0 - 1. IANA has created and is maintaining a Enumerated type values 0 - 1. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.7. CC-Unit-Type AVP 12.7. CC-Unit-Type AVP
As defined in Section 8.32, the CC-Unit-Type AVP includes Enumerated As defined in Section 8.32, the CC-Unit-Type AVP includes Enumerated
type values 0 - 5. IANA has created and is maintaining a namespace type values 0 - 5. IANA has created and is maintaining a namespace
for this AVP. All remaining values are available for assignment by a for this AVP. All remaining values are available for assignment by a
Designated Expert [RFC5226]. Designated Expert [RFC8126], under the conditions for enumerated
values described in [RFC7423] Section 5.6.
12.8. Check-Balance-Result AVP 12.8. Check-Balance-Result AVP
As defined in Section 8.6, the Check-Balance-Result AVP includes As defined in Section 8.6, the Check-Balance-Result AVP includes
Enumerated type values 0 - 1. IANA has created and is maintaining a Enumerated type values 0 - 1. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.9. Credit-Control AVP 12.9. Credit-Control AVP
As defined in Section 8.13, the Credit-Control AVP includes As defined in Section 8.13, the Credit-Control AVP includes
Enumerated type values 0 - 1. IANA has created and is maintaining a Enumerated type values 0 - 1. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.10. Credit-Control-Failure-Handling AVP 12.10. Credit-Control-Failure-Handling AVP
As defined in Section 8.14, the Credit-Control-Failure-Handling AVP As defined in Section 8.14, the Credit-Control-Failure-Handling AVP
includes Enumerated type values 0 - 2. IANA has created and is includes Enumerated type values 0 - 2. IANA has created and is
maintaining a namespace for this AVP. All remaining values are maintaining a namespace for this AVP. All remaining values are
available for assignment by a Designated Expert [RFC5226]. available for assignment by a Designated Expert [RFC8126], under the
conditions for enumerated values described in [RFC7423] Section 5.6.
12.11. Direct-Debiting-Failure-Handling AVP 12.11. Direct-Debiting-Failure-Handling AVP
As defined in Section 8.15, the Direct-Debiting-Failure-Handling AVP As defined in Section 8.15, the Direct-Debiting-Failure-Handling AVP
includes Enumerated type values 0 - 1. IANA has created and is includes Enumerated type values 0 - 1. IANA has created and is
maintaining a namespace for this AVP. All remaining values are maintaining a namespace for this AVP. All remaining values are
available for assignment by a Designated Expert [RFC5226]. available for assignment by a Designated Expert [RFC8126], under the
conditions for enumerated values described in [RFC7423] Section 5.6.
12.12. Final-Unit-Action AVP 12.12. Final-Unit-Action AVP
As defined in Section 8.35, the Final-Unit-Action AVP includes As defined in Section 8.35, the Final-Unit-Action AVP includes
Enumerated type values 0 - 2. IANA has created and is maintaining a Enumerated type values 0 - 2. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.13. Multiple-Services-Indicator AVP 12.13. Multiple-Services-Indicator AVP
As defined in Section 8.40, the Multiple-Services-Indicator AVP As defined in Section 8.40, the Multiple-Services-Indicator AVP
includes Enumerated type values 0 - 1. IANA has created and is includes Enumerated type values 0 - 1. IANA has created and is
maintaining a namespace for this AVP. All remaining values are maintaining a namespace for this AVP. All remaining values are
available for assignment by a Designated Expert [RFC5226]. available for assignment by a Designated Expert [RFC8126], under the
conditions for enumerated values described in [RFC7423] Section 5.6.
12.14. Redirect-Address-Type AVP 12.14. Redirect-Address-Type AVP
As defined in Section 8.38, the Redirect-Address-Type AVP includes As defined in Section 8.38, the Redirect-Address-Type AVP includes
Enumerated type values 0 - 3. IANA has created and is maintaining a Enumerated type values 0 - 3. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.15. Requested-Action AVP 12.15. Requested-Action AVP
As defined in Section 8.41, the Requested-Action AVP includes As defined in Section 8.41, the Requested-Action AVP includes
Enumerated type values 0 - 3. IANA has created and is maintaining a Enumerated type values 0 - 3. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.16. Subscription-Id-Type AVP 12.16. Subscription-Id-Type AVP
As defined in Section 8.47, the Subscription-Id-Type AVP includes As defined in Section 8.47, the Subscription-Id-Type AVP includes
Enumerated type values 0 - 4. IANA has created and is maintaining a Enumerated type values 0 - 4. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.17. Tariff-Change-Usage AVP 12.17. Tariff-Change-Usage AVP
As defined in Section 8.27, the Tariff-Change-Usage AVP includes As defined in Section 8.27, the Tariff-Change-Usage AVP includes
Enumerated type values 0 - 2. IANA has created and is maintaining a Enumerated type values 0 - 2. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
12.18. User-Equipment-Info-Type AVP 12.18. User-Equipment-Info-Type AVP
As defined in Section 8.50, the User-Equipment-Info-Type AVP includes As defined in Section 8.50, the User-Equipment-Info-Type AVP includes
Enumerated type values 0 - 3. IANA has created and is maintaining a Enumerated type values 0 - 3. IANA has created and is maintaining a
namespace for this AVP. All remaining values are available for namespace for this AVP. All remaining values are available for
assignment by a Designated Expert [RFC5226]. assignment by a Designated Expert [RFC8126], under the conditions for
enumerated values described in [RFC7423] Section 5.6.
13. Credit-Control Application Related Parameters 13. Credit-Control Application Related Parameters
Tx timer Tx timer
When real-time credit-control is required, the credit-control client When real-time credit-control is required, the credit-control client
contacts the credit-control server before and while the service is contacts the credit-control server before and while the service is
provided to an end user. Due to the real-time nature of the provided to an end user. Due to the real-time nature of the
application, the communication delays SHOULD be minimized; e.g., to application, the communication delays SHOULD be minimized; e.g., to
avoid an overly long service setup time experienced by the end user. avoid an overly long service setup time experienced by the end user.
skipping to change at page 98, line 44 skipping to change at page 99, line 8
control agent then forwards the CCR message directly to one of the control agent then forwards the CCR message directly to one of the
hosts identified by the CCA message from the redirect agent. If the hosts identified by the CCA message from the redirect agent. If the
value of the Redirect-Host-Usage AVP is unequal to zero, all value of the Redirect-Host-Usage AVP is unequal to zero, all
following messages are sent to the host specified in the Redirect- following messages are sent to the host specified in the Redirect-
Host AVP until the time specified by the Redirect-Max-Cache-Time AVP Host AVP until the time specified by the Redirect-Max-Cache-Time AVP
is expired. is expired.
There are some authorization issues even with redirects. There may There are some authorization issues even with redirects. There may
be attacks toward nodes that have been properly authorized, but that be attacks toward nodes that have been properly authorized, but that
abuse their authorization or have been compromised. These issues are abuse their authorization or have been compromised. These issues are
discussed more widely in [DIAMEAP], Section 8. discussed more widely in [RFC4072], Section 8.
15. References 15. References
15.1. Normative References 15.1. Normative References
[CE164] "Complement to ITU-T Recommendation E.164 (05/1997):"List [CE164] "Complement to ITU-T Recommendation E.164 (05/1997):"List
of ITU-T Recommendation E.164 assigned country codes"", of ITU-T Recommendation E.164 assigned country codes"",
June 2000. June 2000.
[CE212] "Complement to ITU-T Recommendation E.212 (11/1997):" List [CE212] "Complement to ITU-T Recommendation E.212 (11/1997):" List
skipping to change at page 100, line 9 skipping to change at page 100, line 24
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J. [RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006, Loughney, "Diameter Credit-Control Application", RFC 4006,
DOI 10.17487/RFC4006, August 2005, DOI 10.17487/RFC4006, August 2005,
<https://www.rfc-editor.org/info/rfc4006>. <https://www.rfc-editor.org/info/rfc4006>.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, DOI 10.17487/RFC4291, February Architecture", RFC 4291, DOI 10.17487/RFC4291, February
2006, <https://www.rfc-editor.org/info/rfc4291>. 2006, <https://www.rfc-editor.org/info/rfc4291>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<https://www.rfc-editor.org/info/rfc5226>.
[RFC5777] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M., [RFC5777] Korhonen, J., Tschofenig, H., Arumaithurai, M., Jones, M.,
Ed., and A. Lior, "Traffic Classification and Quality of Ed., and A. Lior, "Traffic Classification and Quality of
Service (QoS) Attributes for Diameter", RFC 5777, Service (QoS) Attributes for Diameter", RFC 5777,
DOI 10.17487/RFC5777, February 2010, DOI 10.17487/RFC5777, February 2010,
<https://www.rfc-editor.org/info/rfc5777>. <https://www.rfc-editor.org/info/rfc5777>.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952, Address Text Representation", RFC 5952,
DOI 10.17487/RFC5952, August 2010, DOI 10.17487/RFC5952, August 2010,
<https://www.rfc-editor.org/info/rfc5952>. <https://www.rfc-editor.org/info/rfc5952>.
[RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn, [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
Ed., "Diameter Base Protocol", RFC 6733, Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012, DOI 10.17487/RFC6733, October 2012,
<https://www.rfc-editor.org/info/rfc6733>. <https://www.rfc-editor.org/info/rfc6733>.
[RFC7155] Zorn, G., Ed., "Diameter Network Access Server [RFC7155] Zorn, G., Ed., "Diameter Network Access Server
Application", RFC 7155, DOI 10.17487/RFC7155, April 2014, Application", RFC 7155, DOI 10.17487/RFC7155, April 2014,
<https://www.rfc-editor.org/info/rfc7155>. <https://www.rfc-editor.org/info/rfc7155>.
[RFC7423] Morand, L., Ed., Fajardo, V., and H. Tschofenig, "Diameter
Applications Design Guidelines", BCP 193, RFC 7423,
DOI 10.17487/RFC7423, November 2014,
<https://www.rfc-editor.org/info/rfc7423>.
[RFC7542] DeKok, A., "The Network Access Identifier", RFC 7542, [RFC7542] DeKok, A., "The Network Access Identifier", RFC 7542,
DOI 10.17487/RFC7542, May 2015, DOI 10.17487/RFC7542, May 2015,
<https://www.rfc-editor.org/info/rfc7542>. <https://www.rfc-editor.org/info/rfc7542>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017,
<https://www.rfc-editor.org/info/rfc8126>.
[TGPPIMEI] [TGPPIMEI]
3rd Generation Partnership Project, "Technical 3rd Generation Partnership Project, "Technical
Specification Group Core Network, Numbering, addressing Specification Group Core Network, Numbering, addressing
and identification, (release 13), 3GPP TS 23.003 v. and identification, (release 13), 3GPP TS 23.003 v.
13.5.0", 2016-04. 13.5.0", 2016-04.
15.2. Informative References 15.2. Informative References
[DIAMEAP] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", Work in
Progress.
[RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866, [RFC2866] Rigney, C., "RADIUS Accounting", RFC 2866,
DOI 10.17487/RFC2866, June 2000, DOI 10.17487/RFC2866, June 2000,
<https://www.rfc-editor.org/info/rfc2866>. <https://www.rfc-editor.org/info/rfc2866>.
[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese,
"IEEE 802.1X Remote Authentication Dial In User Service "IEEE 802.1X Remote Authentication Dial In User Service
(RADIUS) Usage Guidelines", RFC 3580, (RADIUS) Usage Guidelines", RFC 3580,
DOI 10.17487/RFC3580, September 2003, DOI 10.17487/RFC3580, September 2003,
<https://www.rfc-editor.org/info/rfc3580>. <https://www.rfc-editor.org/info/rfc3580>.
skipping to change at page 101, line 22 skipping to change at page 101, line 39
Camarillo, "Best Current Practices for Third Party Call Camarillo, "Best Current Practices for Third Party Call
Control (3pcc) in the Session Initiation Protocol (SIP)", Control (3pcc) in the Session Initiation Protocol (SIP)",
BCP 85, RFC 3725, DOI 10.17487/RFC3725, April 2004, BCP 85, RFC 3725, DOI 10.17487/RFC3725, April 2004,
<https://www.rfc-editor.org/info/rfc3725>. <https://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,
<https://www.rfc-editor.org/info/rfc4004>. <https://www.rfc-editor.org/info/rfc4004>.
[RFC4072] Eronen, P., Ed., Hiller, T., and G. Zorn, "Diameter
Extensible Authentication Protocol (EAP) Application",
RFC 4072, DOI 10.17487/RFC4072, August 2005,
<https://www.rfc-editor.org/info/rfc4072>.
[TGPPCHARG] [TGPPCHARG]
3rd Generation Partnership Project, "Technical 3rd Generation Partnership Project, "Technical
Specification Group Services and System Aspects, Service Specification Group Services and System Aspects, Service
aspects; Charging and Billing, (release 13), 3GPP TS aspects; Charging and Billing, (release 13), 3GPP TS
22.115 v. 13.3.0", 2016-03. 22.115 v. 13.3.0", 2016-03.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The original authors of RFC4006 are: Harri Hakala, Leena Mattila, The original authors of RFC4006 are: Harri Hakala, Leena Mattila,
Juha-Pekka Koskinen, Marco Stura, and John Loughney. Juha-Pekka Koskinen, Marco Stura, and John Loughney.
skipping to change at page 120, line 35 skipping to change at page 121, line 35
(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.67). (from Section 8.64 to Section 8.67).
Add extensible QoS-Final-Unit-Indication AVP (in Section 8.68). 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.
Update references to obsolete RFC 5226 to refer to RFC 8126, and
resulting updateds to Section 12.
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
United States United States
Email: lyleb551144@gmail.com Email: lyleb551144@gmail.com
David Dolson (editor) David Dolson (editor)
 End of changes. 30 change blocks. 
53 lines changed or deleted 78 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/