[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: backwards compatible introduction of NEW attribute such as CUI

To: "Nelson, David" <dnelson@enterasys.com>
Subject: RE: backwards compatible introduction of NEW attribute such as CUI
From: Bernard Aboba <aboba@internaut.com>
Date: Wed, 15 Dec 2004 18:29:12 -0800 (PST)
Cc: radiusext@ops.ietf.org
In-reply-to: <2A5E4540D4D5934D9A1E7E0B0FDB2D69E1900A@MAANDMBX2.ets.enterasys.com>
References: <2A5E4540D4D5934D9A1E7E0B0FDB2D69E1900A@MAANDMBX2.ets.enterasys.com>

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

References:
- RE: backwards compatible introduction of NEW attribute such as CUI
  - From: "Nelson, David" <dnelson@enterasys.com>

Prev by Date: RE: CUI - issues addressed in version 3
Next by Date: RE: CUI - issues addressed in version 3
Previous by thread: RE: backwards compatible introduction of NEW attribute such as CUI
Next by thread: RE: backwards compatible introduction of NEW attribute such as CUI
Index(es):
- Date
- Thread