draft-ietf-dime-rfc4006bis-11.txt   draft-ietf-dime-rfc4006bis-12.txt 
Network Working Group L. Bertz, Ed. Network Working Group L. Bertz, Ed.
Internet-Draft Sprint Internet-Draft Sprint
Obsoletes: 4006 (if approved) D. Dolson, Ed. Obsoletes: 4006 (if approved) D. Dolson, Ed.
Intended status: Standards Track Y. Lifshitz, Ed. Intended status: Standards Track Y. Lifshitz, Ed.
Expires: February 27, 2019 Sandvine Expires: March 17, 2019 Sandvine
August 26, 2018 September 13, 2018
Diameter Credit-Control Application Diameter Credit-Control Application
draft-ietf-dime-rfc4006bis-11 draft-ietf-dime-rfc4006bis-12
Abstract Abstract
This document specifies a Diameter application that can be used to This document specifies a Diameter application that can be used to
implement real-time credit-control for a variety of end user services implement real-time credit-control for a variety of end user services
such as network access, Session Initiation Protocol (SIP) services, such as network access, Session Initiation Protocol (SIP) services,
messaging services, and download services. The Diameter Credit- messaging services, and download services. The Diameter Credit-
Control application as defined in this document obsoletes RFC4006, Control application as defined in this document obsoletes RFC4006,
and it must be supported by all new Diameter Credit-Control and it must be supported by all new Diameter Credit-Control
Application implementations. Application implementations.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 27, 2019. This Internet-Draft will expire on March 17, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 61, line 14 skipping to change at page 61, line 14
numbers is to set the value to 0 for a credit-control request of type numbers is to set the value to 0 for a credit-control request of type
INITIAL_REQUEST and EVENT_REQUEST and to set the value to 1 for the INITIAL_REQUEST and EVENT_REQUEST and to set the value to 1 for the
first UPDATE_REQUEST, to 2 for the second, and so on until the value first UPDATE_REQUEST, to 2 for the second, and so on until the value
for TERMINATION_REQUEST is one more than for the last UPDATE_REQUEST. for TERMINATION_REQUEST is one more than for the last UPDATE_REQUEST.
8.3. CC-Request-Type AVP 8.3. CC-Request-Type AVP
The CC-Request-Type AVP (AVP Code 416) is of type Enumerated and The CC-Request-Type AVP (AVP Code 416) is of type Enumerated and
contains the reason for sending the credit-control request message. contains the reason for sending the credit-control request message.
It MUST be present in all Credit-Control-Request messages. The It MUST be present in all Credit-Control-Request messages. The
following values are defined for the CC-Request-Type AVP: following values are defined for the CC-Request-Type AVP (The value
of zero is reserved):
INITIAL_REQUEST 1 INITIAL_REQUEST 1
An Initial request is used to initiate a credit-control session, and An Initial request is used to initiate a credit-control session, and
contains credit-control information that is relevant to the contains credit-control information that is relevant to the
initiation. initiation.
UPDATE_REQUEST 2 UPDATE_REQUEST 2
An Update request contains credit-control information for an existing An Update request contains credit-control information for an existing
 End of changes. 4 change blocks. 
5 lines changed or deleted 6 lines changed or added

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