Remote Authentication Dial-In User Service (RADIUS) Reliable Transport
draft-lior-radius-reliable-accounting-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Avi Lior | ||
| Last updated | 2003-06-20 | ||
| 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
Remote Authentication Dial-In User Service (RADIUS) Request For Comments (RFCs) do not address RADIUS reliability with respect to transport of RADIUS messages. This Informational Internet Draft describes procedures for Retransmission, Failover and Failback.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)