RE: backwards compatible introduction of NEW attribute such as CUI

["Adrangi, Farid" <farid.adrangi@intel.com>]

That's right.  I will add a line for Error-Cause attribue in the
attribute table in CUI draft -- as David proposed.

> -----Original Message-----
> From: owner-radiusext@ops.ietf.org 
> [mailto:owner-radiusext@ops.ietf.org] On Behalf Of Bernard Aboba
> Sent: Wednesday, December 15, 2004 6:29 PM
> To: Nelson, David
> Cc: radiusext@ops.ietf.org
> Subject: RE: backwards compatible introduction of NEW 
> attribute such as CUI
> 
> 
> > RFC3576 does not indicate that the Error-Cause attribute 
> may be used in
> > any commands other than CoA-Request, CoA-ACK and CoA-NAK.
> 
> True, but RFC 3579 does allow the Error-Cause attribute in 
> Access-Reject
> and Access-Challenge messages.  See Section 3.3.
> 
> 
> --
> 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/>