RE: RFC3576bis and Session State

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

Avi Lior writes...

> I don't think therefore that 3576 should prohibit any of the above.
> It really is up to deployments to determine how these are used.

Freedom to innovate and differentiate your product is a wonderful thing, but
so is multi-vendor interoperability based on the formal specification alone.
I understand that you may wish to have a rich vocabulary to specify the
"filter" on which sessions to affect, but it also seems to me that writing
down the rules for everyone to see and implement is required.




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