RE: Proposed Resolution to Issue 178: Allowing Hints in Request Messages

["Sanchez, Mauricio" <mauricio.sanchez@hp.com>]

Glenn questioned.. 

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Glen Zorn (gwz)
> Sent: Thursday, March 16, 2006 12:16 PM
> To: Bernard Aboba
> Cc: radiusext@ops.ietf.org
> Subject: RE: Proposed Resolution to Issue 178: Allowing Hints 
> in Request Messages
> 
> Bernard Aboba <> supposedly scribbled:
> 
> I'm fine with the hint thing, but I wonder why you would need 
> to send, e.g., multiple Egress-VLANID or User-Priority-Table 
> attributes as hints.  Would not one of each suffice?

Only zero or one user-priority-table attribute is allowed.  You must be
thinking about Egress-VLAN-Name attribute.  

The NAS may have the capability to allow a user session to be associated
with multiple VLANs.  By sending multiple vlan attributes up to the
server (i.e. the "hints"), the server finds out what is a possible set
of VLANs the session may be assigned.  

MS

--
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/>