Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Support of Fragmentation of RADIUS Packets (RFC7499)

IP.com Disclosure Number: IPCOM000241223D
Original Publication Date: 2015-Apr-01
Included in the Prior Art Database: 2015-Apr-07
Document File: 76 page(s) / 84K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Perez-Mendez: AUTHOR [+7]

Abstract

The RADIUS [RFC2865] protocol carries authentication, authorization, and accounting information between a RADIUS Client and a RADIUS Server. Information is exchanged between them through RADIUS packets. Each RADIUS packet is composed of a header, and zero or more attributes, up to a maximum packet size of 4096 bytes. The protocol is a request/response protocol, as described in the operational model ([RFC6158], Section 3.1).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)              A. Perez-Mendez, Ed. Request for Comments: 7499                                R. Marin-Lopez Category: Experimental                              F. Pereniguez-Garcia ISSN: 2070-1721                                          G. Lopez-Millan                                                     University of Murcia                                                                 D. Lopez                                                           Telefonica I+D                                                                 A. DeKok                                                           Network RADIUS                                                               April 2015

                Support of Fragmentation of RADIUS Packets

Abstract

   The Remote Authentication Dial-In User Service (RADIUS) protocol is    limited to a total packet size of 4096 bytes.  Provisions exist for    fragmenting large amounts of authentication data across multiple    packets, via Access-Challenge packets.  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 they are designed to be invisible to    proxies and "fail-safe" to legacy RADIUS Clients and Servers.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for examination, experimental implementation, and    evaluation.

   This document defines an Experimental Protocol for the Internet    community.  This document is a product of the Internet Engineering    Task Force (IETF).  It represents the consensus of the IETF    community.  It has received public review and has been approved for    publication by the Internet Engineering Steering Group (IESG).  Not    all documents approved by the IESG are a candidate for any level of    Internet Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7499.

 Perez-Mendez, et al.          Experimental                      [Page 1]
 RFC 7499             Fragmentation of RADIUS Packets          April 2015

 Copyrigh...