[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Capabilities (was Re: AW: Review of draft-ietf-geopriv-radius-lo-04.txt )
Hi,
On Fri, Sep 09, 2005 at 05:24:32PM -0400, Avi Lior wrote:
> > > And by the way, RADIUS does keep transactional state.
> >
> > The RADIUS protocol was designed so that RADIUS servers could
> > be stateless. This is achieved by passing the state "cookie"
> > back to the RADIUS clients in the form of the State and Class
> > attributes.
>
> Exactly. State is how RADIUS can keep transactional state.
For complete clarity: indeed, state per transaction.
No state per NAS, per client, or per user.
Of course policies may any keep per-NAS, per-client or per-user
statistics they want, and even use such per-NAS, per-client or per-user
information in subsequent authentications, but there's nothing in the
protocol that specifically caters for or requires state for anything
other than individual transactions.
Cheers,
Emile.
--
E-Advies - Emile van Bergen emile@e-advies.nl
tel. +31 (0)78 6136282 http://www.e-advies.nl
--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>