Diameter Quality of Service Application

Document Type Replaced Internet-Draft (individual)
Author Frank Alfano 
Last updated 2008-04-16 (latest revision 2006-10-20)
Replaced by RFC 5866
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dime-diameter-qos
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document describes a Diameter application that performs Authentication, Authorization, and Accounting for Quality of Service (QoS) reservations. This protocol is used by elements along the path of a given application flow to authenticate a reservation request, ensure that the reservation is authorized, and to account for resources consumed during the lifetime of the application flow. Clients that implement the Diameter QoS application contact an authorizing entity/application server that is located somewhere in the network, allowing for a wide variety of flexible deployment models.


Frank Alfano (falfano@lucent.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)