Support of fragmentation of RADIUS packets

Document Type Replaced Internet-Draft (individual)
Authors Alejandro Pérez-Méndez  , Rafael Marin-Lopez  , Fernando Pereniguez-Garcia  , Gabriel Lopez-Millan  , Diego Lopez  , Alan DeKok 
Last updated 2014-01-02 (latest revision 2013-07-01)
Replaced by RFC 7499
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-radext-radius-fragmentation
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The Remote Authentication Dial-In User Service (RADIUS) protocol is limited to a total packet size of 4096 octets. Provisions exist for fragmenting large amounts of authentication data across multiple packets, via Access-Challenge. No similar provisions exist for fragmenting large amounts of authorization data. This document specifies how existing RADIUS mechanisms can be leveraged to provide that functionality. These mechanisms are largely compatible with existing implementations, and are designed to be invisible to proxies, and "fail-safe" to legacy clients and servers.


Alejandro Pérez-Méndez (
Rafael Marin-Lopez (
Fernando Pereniguez-Garcia (
Gabriel Lopez-Millan (
Diego Lopez (
Alan DeKok (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)