Browse Prior Art Database

Diameter Routing Message Priority (RFC7944)

IP.com Disclosure Number: IPCOM000247105D
Original Publication Date: 2016-Aug-01
Included in the Prior Art Database: 2016-Aug-05
Document File: 36 page(s) / 41K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

S. Donovan: AUTHOR

Abstract

The Diameter Overload Indication Conveyance (DOIC) solution [RFC7683] for Diameter overload control introduces scenarios where Diameter routing decisions made by Diameter nodes can be influenced by the overload state of other Diameter nodes. This includes the scenarios where Diameter endpoints and Diameter Agents can throttle requests as a result of the target for the request being overloaded.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 7% of the total text.

Internet Engineering Task Force (IETF)                        S. Donovan Request for Comments: 7944                                        Oracle Category: Standards Track                                    August 2016 ISSN: 2070-1721

                    Diameter Routing Message Priority

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 addresses this by    defining 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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7944.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Donovan                      Standards Track                    [Page 1]
 RFC 7944                          DOIC                       August 2016

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

     1.1.  Applicability . . . . . . . . . . . . . . . . . . . . . .   3

   2.  Terminology and Abbreviations . . . . . . . . . . . . . . . .   4

   3.  Conventions Used in This Document . . . . . . . . . . . . . .   4

   4.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   5

   5.  Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . .   6

     5.1.  First-Responder-Related Sig...