RE: [Technical Errata Reported] RFC5176 (2012)

["Dave Nelson" <d.b.nelson@comcast.net>]

> As you say, most of the existing uses of Error-Cause are for
> protocol error of some kind, so in looking at the IEEE 802.1X-REV 
> authorization scenarios, the preliminary thinking was to use some
> other attribute to communicate the content that might end up in
> EAPOL-Announcements that provide the client with an indication
> of the access status.

Haven't we already clarified, in RFC 5080 Section 2.6, that with the use of
an Access-Reject message "no means no" and that Access-Reject cannot be used
to provision restricted or alternate forms of service or access?



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