Diameter Applications Design Guidelines
draft-fajardo-dime-app-design-guide-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Victor Fajardo | ||
| Last updated | 2010-04-12 (Latest revision 2007-04-18) | ||
| Replaced by | draft-ietf-dime-app-design-guide | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-dime-app-design-guide | |
| 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
The Diameter Base protocol provides rules on how to extend Diameter and to create new Diameter applications. This is a companion document to clarify these rules. This document does not intended to add, remove or change these rules, rather it helps protocol designers to extend Diameter.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)