I have mixed feelings. On the one hand, there is precedent for glomming all instances of an attribute together, for EAP. On the other, EAP is different in that the RADIUS code does not parse the result. What will happen with the next attribute, where a byte value of 0x00 may be valid?
This approach works for this particular attribute because the IPFilter syntax only permits ASCII characters. It's not a general solution, as you point out. That wider problem may be part of the extended attribute discussion. Since NAS-Filter-Rule isn't an extended attribute I think that discussion is somewhat orthogonal.
-- 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/>