RADIUS UDP transport mapping
draft-lior-radius-udp-transport-mapping-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Avi Lior | ||
| Last updated | 2003-10-16 | ||
| 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
The Remote Authentication Dial In User Service (RADIUS) Request For Comments (RFC) specify that RADIUS should use retransmit strategy to recover from the loss of packets but they do not provide any further guidance. This has resulted in implementations lacking support for congestion control. This Internet Draft discusses and recommends strategies for measuring, calculating and applying a retransmission timer for RADIUS.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)