Auditing Functionality in Diameter
draft-bodin-dime-auditing-reqs-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ulf Bodin | ||
| Last updated | 2007-09-10 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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:
Abstract
Diameter is being increasingly included in the work of other standards organizations and has become a key protocol in many architectures. O maintaining hard-state and soft-state during failover and in the event of delayed refresh messages respectively. Often there is a need to query for information on active sessions for backup or synchronization purposes. ne of the uses of Diameter includes setting and
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)