Skip to main content

Diameter Routing Message Priority

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Steve Donovan
Last updated 2015-05-26
Replaced by draft-ietf-dime-drmp
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dime-drmp
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


When making routing and resource allocation decisions, Diameter nodes currently have no generic mechanism to determine the relative priority of Diameter messages. This document defines a mechanism to allow Diameter endpoints to indicate the relative priority of Diameter transactions. With this information Diameter nodes can factor that priority into routing, resource allocation and overload abatement decisions.


Steve Donovan

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