"Remote Authentication Dial-In User Service (RADIUS) Authorization for Network Access Server (NAS) Management", David Nelson, Greg Weber, 10-Oct-08. ( bytes)

This document specifies Remote Authentication Dial-In User Service (RADIUS) attributes for authorizing management access to a Network Access Server (NAS). Both local and remote management are supported, with granular access rights and management privileges. Specific provisions are made for remote management via framed management protocols, and for management access over a secure transport protocol.

"RADIUS Design Guidelines", Greg Weber, Alan DeKok, Intellectual Property, 26-Aug-08. ( bytes)

This document provides guidelines for the design of attributes used by the Remote Authentication Dial In User Service (RADIUS) protocol. It is expected that these guidelines will prove useful to authors and reviewers of future RADIUS attribute specifications, both within the IETF as well as other Standards Development Organizations (SDOs).

"Extended Remote Authentication Dial In User Service (RADIUS) Attributes", Yong Li, Avi Lior, Glen Zorn, 7-Jul-08. ( bytes)

For the Remote Authentication Dial In User Service (RADIUS) protocol to continue to support new applications the RADIUS attribute type space must be extended beyond the current limit of 255 possible attribute types while maintaining backwards compatibility with the existing protocol. This document defines a mechanism to accomplish that task, along with standard methods to group together related attributes and to encode values that don't fit into 253 octets.

"Crypto-Agility Requirements for Remote Dial-In User Service (RADIUS)", David Nelson, 8-May-08. ( bytes)

This memo describes the requirements for a crypto-agility solution for Remote Authentication Dial-In User Service (RADIUS).

"TLS encryption for RADIUS over TCP (RadSec)", Stefan Winter, Mike McCauley, Stig Venaas, Klaas Wierenga, 22-Aug-08. ( bytes)

This document specifies security on the transport layer (TLS) for the RADIUS protocol [RFC2865] when transmitted over TCP [I-D.dekok-radext-tcp-transport]. This enables dynamic trust relationships between RADIUS servers.

"Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) Protocol", Alan DeKok, 25-Aug-08. ( bytes)

RFC 2865 defines a Status-Server code for use in RADIUS, but labels it as "Experimental" without further discussion. This document describes a practical use for the Status-Server packet code, which is to let clients query the status of a RADIUS server. These queries, and responses (if any) enable the client to make more informed decisions. The result is a more stable, and more robust RADIUS architecture.

Return to Internet-Draft directory.

Return to IETF home page.