draft-aboba-radius-rfc2869bis-21 (fwd)

[Bernard Aboba <aboba@internaut.com>]

> Why isn't this document on the Standards Track?

Here's the answer as I understand it.

RFC 2869bis updates RFC 2869, which was Informational.  My understanding
is that a Standards Track document can't update an Informational document.

Why was RFC 2869 Informational?

It included accounting attributes, and RFC 2866 (RADIUS Accounting) was
Informational.

Why was RFC 2866 Informational?

RFC 2866 was Informational because of deficiencies in its design.  These
included undefined retransmission behavior and failover support as well as
lack of replay protection (e.g. no liveness in the exchanges).