Diameter Group Signaling
draft-ietf-dime-group-signaling-06
| Document | Type | Expired Internet-Draft (dime WG) | |
|---|---|---|---|
| Last updated | 2016-09-22 (latest revision 2016-03-21) | ||
| Replaces | draft-jones-diameter-group-signaling | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | Jouni Korhonen | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dime-group-signaling-06.txt
Abstract
In large network deployments, a single Diameter node can support over a million concurrent Diameter sessions. Recent use cases have revealed the need for Diameter nodes to apply the same operation to a large group of Diameter sessions concurrently. The Diameter base protocol commands operate on a single session so these use cases could result in many thousands of command exchanges to enforce the same operation on each session in the group. In order to reduce signaling, it would be desirable to enable bulk operations on all (or part of) the sessions managed by a Diameter node using a single or a few command exchanges. This document specifies the Diameter protocol extensions to achieve this signaling optimization.
Authors
Mark Jones
(mark@azu.ca)
Marco Liebsch
(marco.liebsch@neclab.eu)
Lionel Morand
(lionel.morand@orange.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)