Subject: Re: (radius) Class.

From: Barney Wolff <[email-masked]>
Date: Wed, 20 Jan 1999 15:58 EST

In theory, this ought to work.  I wonder how many NAS impelmentations
support returning multiple Class attributes safely in the acct request.
The implication for NAS memory is fairly profound, as all the Classes
have to be kept around until the end of the session.  Trivial for a
new hardware design, of course, but not necessarily for updated software
on old hardware.

Barney

> Date: Wed, 20 Jan 1999 13:32:33 +0200 (MET-DST)
> From: MARC DE VRIES WE41/KT <[email-masked]>
> 
> I have seen multiple Class attributes in Access-Accept, all of which returned
> in Accounting-Request (tested with only one NAS type). 
> 
> You can have the two Class implementations (session-id and group) using two
> distict attribute instances or a single one.
> 
> Access-Accept:
>   Class = "realm:faraway.com;auth-session-id:123456"
> 
> or
> 
> Access-Accept:
>   Class = "realm:faraway.com",
>   Class = "auth-session-id:123456"
> 
> For roaming, using multiple class attributes may be better than class-in-class
> encapsulation because of the attribute length limit.
-
To unsubscribe, email [email-masked]' with
'unsubscribe ietf-radius' in the body of the message.