RE: Comments on the draft-ietf-radext-filter-04 or.. -05

["Bernard Aboba" <bernard_aboba@hotmail.com>]

Your comment about combinations of 
NAS-Filter-Rule/NAS-Traffic-Rule/Filter-Id brought some other thoughts to 
mind:

a. What if an operator doesn't know whether a given NAS supports 
NAS-Filter-Rule or NAS-Traffic-Rule?  Can it send *both* attributes, knowing 
that a NAS supporting NAS-Traffic-Rule will automatically ignore 
NAS-Filter-Rule?

b. What if an operator has a large set of constant filter rules, but needs 
to tag a different rule onto the end of the rule set, which depends on the 
user?  Could they send a Filter-Id attribute as well as a NAS-Filter-Rule or 
NAS-Traffic-Rule attribute?

c. In what circumstances will we be likely to see Filter-Id and 
NAS-Filter-Rule in the same Diameter message?



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