Support of fragmentation of RADIUS packets
draft-perez-radext-radius-fragmentation-06

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2014-01-02 (latest revision 2013-07-01)
Replaced by draft-ietf-radext-radius-fragmentation
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-radext-radius-fragmentation
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-perez-radext-radius-fragmentation-06.txt

Abstract

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.

Authors

Alejandro Perez-Mendez (alex@um.es)
Rafael Lopez (rafa@um.es)
Fernando Pereniguez-Garcia (pereniguez@um.es)
Gabriel Lopez-Millan (gabilm@um.es)
Diego Lopez (diego@tid.es)
Alan DeKok (aland@networkradius.com)

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