draft-ietf-dime-rfc4006bis-03.txt   draft-ietf-dime-rfc4006bis-04.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: November 11, 2017 Y. Lifshitz, Ed. Expires: June 4, 2018 Y. Lifshitz, Ed.
Sandvine Sandvine
May 10, 2017 December 1, 2017
Diameter Credit-Control Application Diameter Credit-Control Application
draft-ietf-dime-rfc4006bis-03 draft-ietf-dime-rfc4006bis-04
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
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 http://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 November 11, 2017. This Internet-Draft will expire on June 4, 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
(http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this 10, 2008. The person(s) controlling the copyright in some of this
skipping to change at page 5, line 16 skipping to change at page 5, line 16
12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 95 12.14. Redirect-Address-Type AVP . . . . . . . . . . . . . . . 95
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 . . . . . . . . . . . . . . . . . . . . . . . . . 98
15.1. Normative References . . . . . . . . . . . . . . . . . . 98 15.1. Normative References . . . . . . . . . . . . . . . . . . 98
15.2. Informative References . . . . . . . . . . . . . . . . . 101 15.2. Informative References . . . . . . . . . . . . . . . . . 100
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 101 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 101
Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 101 Appendix B. Credit-Control Sequences . . . . . . . . . . . . . . 101
B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 101 B.1. Flow I . . . . . . . . . . . . . . . . . . . . . . . . . 101
B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 104 B.2. Flow II . . . . . . . . . . . . . . . . . . . . . . . . . 104
B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 106 B.3. Flow III . . . . . . . . . . . . . . . . . . . . . . . . 106
B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 106 B.4. Flow IV . . . . . . . . . . . . . . . . . . . . . . . . . 106
B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 108 B.5. Flow V . . . . . . . . . . . . . . . . . . . . . . . . . 108
B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 109 B.6. Flow VI . . . . . . . . . . . . . . . . . . . . . . . . . 109
B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 110 B.7. Flow VII . . . . . . . . . . . . . . . . . . . . . . . . 110
B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 112 B.8. Flow VIII . . . . . . . . . . . . . . . . . . . . . . . . 112
skipping to change at page 6, line 28 skipping to change at page 6, line 28
To fulfill these requirements, it is necessary to facilitate credit- To fulfill these requirements, it is necessary to facilitate credit-
control communication between the network element providing the control communication between the network element providing the
service (e.g., Network Access Server, SIP Proxy, and Application service (e.g., Network Access Server, SIP Proxy, and Application
Server) and a credit-control server. Server) and a credit-control server.
The scope of this specification is the credit authorization. Service The scope of this specification is the credit authorization. Service
specific authorization and authentication is out of the scope. specific authorization and authentication is out of the scope.
1.1. Requirements Language 1.1. Requirements Language
In this document, the key words "MAY", "MUST", "MUST NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"OPTIONAL", "RECOMMENDED", "SHOULD", and "SHOULD NOT", are to be "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
1.2. Terminology 1.2. Terminology
AAA Authentication, Authorization, and Accounting AAA Authentication, Authorization, and Accounting
AA answer AA answer generically refers to a service specific AA answer AA answer generically refers to a service specific
authorization and authentication answer. AA answer commands are authorization and authentication answer. AA answer commands are
defined in service specific authorization applications, e.g., defined in service specific authorization applications, e.g.,
[RFC7155] and [RFC4004]. [RFC7155] and [RFC4004].
skipping to change at page 64, line 35 skipping to change at page 64, line 35
subscription, this value indicates that the credit-control server subscription, this value indicates that the credit-control server
MUST be contacted to perform the first interrogation. The value of MUST be contacted to perform the first interrogation. The value of
the Credit-Control AVP MUST always be set to 0 in an AA request sent the Credit-Control AVP MUST always be set to 0 in an AA request sent
to perform the first interrogation and to initiate a new credit- to perform the first interrogation and to initiate a new credit-
control session. control session.
RE_AUTHORIZATION 1 RE_AUTHORIZATION 1
This value indicates to the Diameter AAA server that a credit-control This value indicates to the Diameter AAA server that a credit-control
session is ongoing for the subscriber and that the credit-control session is ongoing for the subscriber and that the credit-control
server MUST not be contacted. The Credit-Control AVP set to the server MUST NOT be contacted. The Credit-Control AVP set to the
value of 1 is to be used only when the first interrogation has been value of 1 is to be used only when the first interrogation has been
successfully performed and the credit-control session is ongoing successfully performed and the credit-control session is ongoing
(i.e., re-authorization triggered by Authorization-Lifetime). This (i.e., re-authorization triggered by Authorization-Lifetime). This
value MUST NOT be used in an AA request sent to perform the first value MUST NOT be used in an AA request sent to perform the first
interrogation. interrogation.
8.14. Credit-Control-Failure-Handling AVP 8.14. Credit-Control-Failure-Handling AVP
The Credit-Control-Failure-Handling AVP (AVP Code 427) is of type The Credit-Control-Failure-Handling AVP (AVP Code 427) is of type
Enumerated. The credit-control client uses information in this AVP Enumerated. The credit-control client uses information in this AVP
skipping to change at page 76, line 27 skipping to change at page 76, line 27
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 MUST conform to the text representation of [RFC4291]. The address MUST conform to the text representation of
the address 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 [RFC3986].
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].
8.39. Redirect-Server-Address AVP 8.39. Redirect-Server-Address AVP
The Redirect-Server-Address AVP (AVP Code 435) is of type UTF8String The Redirect-Server-Address AVP (AVP Code 435) is of type UTF8String
and defines the address of the redirect server (e.g., HTTP redirect and defines the address of the redirect server (e.g., HTTP redirect
skipping to change at page 85, line 37 skipping to change at page 85, line 37
When encoded as an IPv6 address in 16 bytes, the IPv4-mapped IPv6 When encoded as an IPv6 address in 16 bytes, the IPv4-mapped IPv6
format [RFC4291] MAY be used to indicate an IPv4 address. format [RFC4291] MAY be used to indicate an IPv4 address.
8.66. Redirect-Address-URL AVP 8.66. Redirect-Address-URL AVP
The Redirect-Address-URL AVP (AVP Code TBD15) 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. The address type is in the form of Uniform Resource Locator, cost. The address type is in the form of Uniform Resource Locator,
as defined in [RFC1738]. as defined in [RFC3986].
8.67. Redirect-Address-SIP-URI AVP 8.67. Redirect-Address-SIP-URI AVP
The Redirect-Address-SIP-URI AVP (AVP Code TBD16) 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. 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.68. QoS-Final-Unit-Indication AVP 8.68. QoS-Final-Unit-Indication AVP
skipping to change at page 88, line 45 skipping to change at page 88, line 45
an AVP value that is not recognized or supported in the rating. The an AVP value that is not recognized or supported in the rating. The
Failed-AVP AVP MUST be included and contain a copy of the entire Failed-AVP AVP MUST be included and contain a copy of the entire
AVP(s) that could not be processed successfully or an example of the AVP(s) that could not be processed successfully or an example of the
missing AVP complete with the Vendor-Id if applicable. The value missing AVP complete with the Vendor-Id if applicable. The value
field of the missing AVP should be of correct minimum length and field of the missing AVP should be of correct minimum length and
contain zeros. contain zeros.
10. AVP Occurrence Table 10. AVP Occurrence Table
The following table presents the AVPs defined in this document and The following table presents the AVPs defined in this document and
specifies in which Diameter messages they MAY or MAY NOT be present. specifies in which Diameter messages they MAY or MUST NOT be present.
Note that AVPs that can only be present within a Grouped AVP are not Note that AVPs that can only be present within a Grouped AVP are not
represented in this table. represented in this table.
The table uses the following symbols: The table uses the following symbols:
0 The AVP MUST NOT be present in the message. 0 The AVP MUST NOT be present in the message.
0+ Zero or more instances of the AVP MAY be present in the 0+ Zero or more instances of the AVP MAY be present in the
message. message.
0-1 Zero or one instance of the AVP MAY be present in the 0-1 Zero or one instance of the AVP MAY be present in the
message. It is considered an error if there is more message. It is considered an error if there is more
skipping to change at page 94, line 34 skipping to change at page 94, line 34
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. available for assignment by a Designated Expert [RFC5226].
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 [RFC2434]. available for assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. available for assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 [RFC2434]. assignment by a Designated Expert [RFC5226].
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 99, line 26 skipping to change at page 99, line 26
[EUI64] IEEE, ""Guidelines for 64-bit Global Identifier (EUI-64) [EUI64] IEEE, ""Guidelines for 64-bit Global Identifier (EUI-64)
Registration Authority"", March 1997, Registration Authority"", March 1997,
<http://standards.ieee.org/regauth/oui/tutorials/ <http://standards.ieee.org/regauth/oui/tutorials/
EUI64.html >. EUI64.html >.
[ISO4217] "Codes for the representation of currencies and funds, [ISO4217] "Codes for the representation of currencies and funds,
International Standard ISO 4217", 2001. International Standard ISO 4217", 2001.
[RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791,
DOI 10.17487/RFC0791, September 1981, DOI 10.17487/RFC0791, September 1981,
<http://www.rfc-editor.org/info/rfc791>. <https://www.rfc-editor.org/info/rfc791>.
[RFC1738] Berners-Lee, T., Masinter, L., and M. McCahill, "Uniform
Resource Locators (URL)", RFC 1738, DOI 10.17487/RFC1738,
December 1994, <http://www.rfc-editor.org/info/rfc1738>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 2434,
DOI 10.17487/RFC2434, October 1998,
<http://www.rfc-editor.org/info/rfc2434>.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
DOI 10.17487/RFC3261, June 2002, DOI 10.17487/RFC3261, June 2002,
<http://www.rfc-editor.org/info/rfc3261>. <https://www.rfc-editor.org/info/rfc3261>.
[RFC3539] Aboba, B. and J. Wood, "Authentication, Authorization and [RFC3539] Aboba, B. and J. Wood, "Authentication, Authorization and
Accounting (AAA) Transport Profile", RFC 3539, Accounting (AAA) Transport Profile", RFC 3539,
DOI 10.17487/RFC3539, June 2003, DOI 10.17487/RFC3539, June 2003,
<http://www.rfc-editor.org/info/rfc3539>. <https://www.rfc-editor.org/info/rfc3539>.
[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
"IEEE 802.1X Remote Authentication Dial In User Service Resource Identifier (URI): Generic Syntax", STD 66,
(RADIUS) Usage Guidelines", RFC 3580, RFC 3986, DOI 10.17487/RFC3986, January 2005,
DOI 10.17487/RFC3580, September 2003, <https://www.rfc-editor.org/info/rfc3986>.
<http://www.rfc-editor.org/info/rfc3580>.
[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,
<http://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, <http://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,
<http://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,
<http://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,
<http://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,
<http://www.rfc-editor.org/info/rfc7155>. <https://www.rfc-editor.org/info/rfc7155>.
[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,
<http://www.rfc-editor.org/info/rfc7542>. <https://www.rfc-editor.org/info/rfc7542>.
[TGPPCHARG]
3rd Generation Partnership Project, "Technical
Specification Group Services and System Aspects, Service
aspects; Charging and Billing, (release 13), 3GPP TS
22.115 v. 13.3.0", 2016-03.
[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 [DIAMEAP] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", Work in Authentication Protocol (EAP) Application", Work in
Progress. 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,
<http://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,
"IEEE 802.1X Remote Authentication Dial In User Service
(RADIUS) Usage Guidelines", RFC 3580,
DOI 10.17487/RFC3580, September 2003,
<https://www.rfc-editor.org/info/rfc3580>.
[RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G. [RFC3725] Rosenberg, J., Peterson, J., Schulzrinne, H., and G.
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,
<http://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,
<http://www.rfc-editor.org/info/rfc4004>. <https://www.rfc-editor.org/info/rfc4004>.
[TGPPCHARG]
3rd Generation Partnership Project, "Technical
Specification Group Services and System Aspects, Service
aspects; Charging and Billing, (release 13), 3GPP TS
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.
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
 End of changes. 41 change blocks. 
62 lines changed or deleted 63 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/