Correlating requests and replies in the Remote Authentication Dial In User Service (RADIUS) Protocol via the Request Authenticator.
draft-dekok-radext-request-authenticator-03

Document Type Expired Internet-Draft (individual)
Last updated 2018-06-07 (latest revision 2017-12-04)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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
https://www.ietf.org/archive/id/draft-dekok-radext-request-authenticator-03.txt

Abstract

RADIUS uses a one-octet Identifier field to correlate requests and responses, which limits clients to 256 "in flight" packets per connection. This document removes that limitation by allowing Request Authenticator to be used as an additional field for identifying packets. The capability is negotiated on a per- connection basis, and requires no changes to the RADIUS packet format, attribute encoding, or data types.

Authors

Alan DeKok (aland@freeradius.org)

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