Diameter Routing Message Priority
draft-donovan-dime-drmp-01

Document Type Replaced Internet-Draft (individual)
Last updated 2015-05-26
Replaced by draft-ietf-dime-drmp
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dime-drmp
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
https://www.ietf.org/archive/id/draft-donovan-dime-drmp-01.txt

Abstract

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.

Authors

Steve Donovan (srdonovan@usdonovans.com)

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