[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: Error-Cause Attribute in Disconnect-ACK?
Issue: Error-Cause Attribute in Disconnect-ACK?
Submitter name: Bernard Aboba
Submitter email address: aboba@internaut.com
Date first submitted: May 22, 2007
Reference:
Document: RFC3576bis-05
Comment type: Technical
Priority: S
Section: 3.4
Rationale/Explanation of issue:
In the process of editing the attribute table to address Issue 226, I noticed an oddity.
RFC 3576 Section 3.1 states the following:
It is possible that the NAS cannot honor Disconnect-Request or
CoA-Request messages for some reason. The Error-Cause Attribute
provides more detail on the cause of the problem. It MAY be
included within Disconnect-ACK, Disconnect-NAK and CoA-NAK
messages.
Why would an Error-Cause Attribute be included in a Disconnect-ACK? It is not allowed in a CoA-ACK, for example.
--
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/>