[Dime] RFC 8506 on Diameter Credit-Control Application
rfc-editor@rfc-editor.org Fri, 01 March 2019 16:54 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91FCE130E9B; Fri, 1 Mar 2019 08:54:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpaBw_69EXIr; Fri, 1 Mar 2019 08:54:00 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01620130E90; Fri, 1 Mar 2019 08:53:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 88794B80A4E; Fri, 1 Mar 2019 08:53:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dime@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190301165338.88794B80A4E@rfc-editor.org>
Date: Fri, 01 Mar 2019 08:53:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dime/AcqRFVwBCjU5HO4cS7tWanbYsq4>
Subject: [Dime] RFC 8506 on Diameter Credit-Control Application
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dime/>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2019 16:54:03 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8506
Title: Diameter Credit-Control Application
Author: L. Bertz, Ed.,
D. Dolson, Ed.,
Y. Lifshitz, Ed.
Status: Standards Track
Stream: IETF
Date: March 2019
Mailbox: lyleb551144@gmail.com,
ddolson@acm.org,
yuvalif@yahoo.com
Pages: 130
Characters: 338474
Obsoletes: RFC 4006
I-D Tag: draft-ietf-dime-rfc4006bis-12.txt
URL: https://www.rfc-editor.org/info/rfc8506
DOI: 10.17487/RFC8506
This document specifies a Diameter application that can be used to
implement real-time credit-control for a variety of end-user services
such as network access, Session Initiation Protocol (SIP) services,
messaging services, and download services. The Diameter Credit-
Control application as defined in this document obsoletes RFC 4006,
and it must be supported by all new Diameter Credit-Control
application implementations.
This document is a product of the Diameter Maintenance and Extensions Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC