RE: Proposal: Capabilities Attribute

[Avi Lior <avi@bridgewatersystems.com>]

Oh I forgot to mention. We started this work already in draft and we are
going to move this to a stand alone draft for the next meeting.

Will post soon.

Thanx Avi and Farid

> -----Original Message-----
> From: Bernard Aboba [mailto:aboba@internaut.com] 
> Sent: Monday, January 17, 2005 1:23 AM
> To: Glen Zorn (gwz)
> Cc: radiusext@ops.ietf.org
> Subject: RE: Proposal: Capabilities Attribute
> 
> 
> > >       This Attribute includes a list of attribute types supported
> > >       by the client.  One or more Capabilities attributes 
> MAY be sent
> > >       within an Access-Request packet.
> >
> > Why only client & request?
> 
> The usage scenario I had in mind was a NAS announcing to a 
> server that it supported various attributes.  This could be 
> useful, for debugging purposes (oops, I forgot to upgrade 
> that NAS!), or backward compatibility (server won't send a 
> new attribute to a NAS that doesn't support it).
> 
> Can you describe how a server could use a Capabilities attribute?
> 
> --
> 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/>
> 

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