draft-ietf-dime-rfc4006bis-02.txt   draft-ietf-dime-rfc4006bis-03.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: September 10, 2017 Y. Lifshitz, Ed. Expires: November 11, 2017 Y. Lifshitz, Ed.
Sandvine Sandvine
March 9, 2017 May 10, 2017
Diameter Credit-Control Application Diameter Credit-Control Application
draft-ietf-dime-rfc4006bis-02 draft-ietf-dime-rfc4006bis-03
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 September 10, 2017. This Internet-Draft will expire on November 11, 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 80, line 37 skipping to change at page 80, line 37
The identifier is in international IMSI format, according to the The identifier is in international IMSI format, according to the
ITU-T E.212 numbering plan as defined in [E212] and [CE212]. ITU-T E.212 numbering plan as defined in [E212] and [CE212].
END_USER_SIP_URI 2 END_USER_SIP_URI 2
The identifier is in the form of a SIP URI, as defined in [RFC3261]. The identifier is in the form of a SIP URI, as defined in [RFC3261].
END_USER_NAI 3 END_USER_NAI 3
The identifier is in the form of a Network Access Identifier, as The identifier is in the form of a Network Access Identifier, as
defined in [RFC2486]. defined in [RFC7542].
END_USER_PRIVATE 4 END_USER_PRIVATE 4
The Identifier is a credit-control server private identifier. The Identifier is a credit-control server private identifier.
8.48. Subscription-Id-Data AVP 8.48. Subscription-Id-Data AVP
The Subscription-Id-Data AVP (AVP Code 444) is used to identify the The Subscription-Id-Data AVP (AVP Code 444) is used to identify the
end user and is of type UTF8String. The Subscription-Id-Type AVP end user and is of type UTF8String. The Subscription-Id-Type AVP
defines which type of identifier is used. defines which type of identifier is used.
skipping to change at page 84, line 37 skipping to change at page 84, line 37
8.61. Subscription-Id-SIP-URI AVP 8.61. Subscription-Id-SIP-URI AVP
The Subscription-Id-SIP-URI (AVP Code TBD10) is of type UTF8String. The Subscription-Id-SIP-URI (AVP Code TBD10) is of type UTF8String.
The Subscription-Id-SIP-URI AVP contains the identifier in the form The Subscription-Id-SIP-URI AVP contains the identifier in the form
of a SIP URI, as defined in [RFC3261]. of a SIP URI, as defined in [RFC3261].
8.62. Subscription-Id-NAI AVP 8.62. Subscription-Id-NAI AVP
The Subscription-Id-NAI (AVP Code TBD11) is of type UTF8String. The The Subscription-Id-NAI (AVP Code TBD11) is of type UTF8String. The
Subscription-Id-NAI AVP contains the identifier in the form of a Subscription-Id-NAI AVP contains the identifier in the form of a
Network Access Identifier, as defined in [RFC2486]. Network Access Identifier, as defined in [RFC7542].
8.63. Subscription-Id-Private AVP 8.63. Subscription-Id-Private AVP
The Subscription-Id-Private (AVP Code TBD12) is of type UTF8String. The Subscription-Id-Private (AVP Code TBD12) is of type UTF8String.
The Subscription-Id-Private AVP contains a credit-control server The Subscription-Id-Private AVP contains a credit-control server
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
skipping to change at page 99, line 42 skipping to change at page 99, line 42
[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>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 2434, IANA Considerations Section in RFCs", RFC 2434,
DOI 10.17487/RFC2434, October 1998, DOI 10.17487/RFC2434, October 1998,
<http://www.rfc-editor.org/info/rfc2434>. <http://www.rfc-editor.org/info/rfc2434>.
[RFC2486] Aboba, B. and M. Beadles, "The Network Access Identifier",
RFC 2486, DOI 10.17487/RFC2486, January 1999,
<http://www.rfc-editor.org/info/rfc2486>.
[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>. <http://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>. <http://www.rfc-editor.org/info/rfc3539>.
skipping to change at page 100, line 45 skipping to change at page 100, line 40
[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>. <http://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>. <http://www.rfc-editor.org/info/rfc7155>.
[RFC7542] DeKok, A., "The Network Access Identifier", RFC 7542,
DOI 10.17487/RFC7542, May 2015,
<http://www.rfc-editor.org/info/rfc7542>.
[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.
[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.
skipping to change at page 119, line 44 skipping to change at page 119, line 44
Control-Answer to the service element (17). Control-Answer to the service element (17).
Appendix C. Changes relative to RFC4006 Appendix C. Changes relative to RFC4006
The following changes were made relative to RFC4006: The following changes were made relative to RFC4006:
Update references to obsolete RFC 3588 to refer to RFC 6733. Update references to obsolete RFC 3588 to refer to RFC 6733.
Update references to obsolete RFC 4005 to refer to RFC 7155. Update references to obsolete RFC 4005 to refer to RFC 7155.
Update references to obsolete RFC 2486 to refer to RFC 7542.
Update references to current 3GPP documents. Update references to current 3GPP documents.
Update AVP per Errata ID 3329. Update AVP per Errata ID 3329.
Update reference to "IPsec or TLS" to be "TLS/TCP, DTLS/SCTP or Update reference to "IPsec or TLS" to be "TLS/TCP, DTLS/SCTP or
IPsec". IPsec".
Clarify Filter-Rule AVP in Restrict Access Action. Clarify Filter-Rule AVP in Restrict Access Action.
Remove Encr column from AVP flag rules. Remove Encr column from AVP flag rules.
 End of changes. 9 change blocks. 
10 lines changed or deleted 12 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/