your new text proposal looks much better.
You need to modify Section 3 as well:
"
Access- Access- Access- Access- CoA-
Request Accept Reject Challenge Req # Attribute
0 0-1 0 0 0-1 TBD User-Priority-Table
"
Got it. BTW, do you think that *any* of the attributes are appropriate for inclusion in an Accounting-Request?
BTW, I just thought of another issue. If not careful, it is quite possible for the administrator to cause considerable chaos with these attributes. For example, it would be possible to configure multiple untagged Egress-VLANIDs or Egress-VLAN-Name attributes, effectively connecting multiple broadcast domains together.
I am thinking that it should only be possible to send at most a single Untagged Egress-VLANID, or Egress-VLAN-Name attribute in an Access-Accept, which makes me wonder whether there shouldn't be two separate attributes for Tagged-Egress-VLANID/Name (0+) and Untagged-Egress-VLANID/Name (0-1).
-- 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/>