Capabilities Update Problem Statement
draft-tsou-dime-capabilities-update-statement-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tina Tsou (Ting ZOU) | ||
| Last updated | 2008-07-28 | ||
| 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
This specification clarifies "Capabilities Update" in OPEN state defined in RFC 3588bis. Capabilities update in OPEN state can reuse commands CER/CEA commands for re-negotiation between Diameter peers when one of them changes its capabilities.It is a very important function in Diameter. However, RFC 3588 has defined a mechanism of containing capabilities list both in CER and CEA commands and the peer should update its local database whenever it receives CER/CEA. This makes the process complex and redundant when they are used in OPEN state. So this draft proposes a simpler solution based on CER/CEA commands to deal with this problem.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)