Diameter/RADIUS Vendor Specific AVP Translation
draft-mitton-diameter-radius-vsas-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | David Mitton | ||
| Last updated | 2006-02-13 | ||
| 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 document describes how a Diameter protocol application would interact with a RADIUS protocol application with respect to translation of Vendor Specific Attributes and AVPs in both networks. This interactions between Diameter applications and RADIUS specified in this document are in addition to that specified in the Diameter Base, the Diameter NAS Application and RADIUS. In this sense, this document extends the Base Diameter protocol and requests an addition to the RADIUS attribute space.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)