RE: : ISSUE: SIP application policy considered unmanageable

Miguel Garcia writes... 

> My criticism was towards adding this mode of operation to the Diameter
> draft (not to the RADIUS), imported from the RADIUS draft, where it is
> hard to manage (and as I indicated, I don't have a good solution to
make
> it better for the time being).

I understand.

The issue, of course, is whether the IETF wishes to standardize new
attributes (features) in RADIUS that do not have a counterpart in
Diameter.  The traditional wisdom has been that we do not.  I suppose if
it could be documented that a particular RADIUS feature will *only* be
used in legacy deployments that will *never* have to interoperate with
Diameter (via dual-mode servers or via gateways), then we might choose
to relax that constraint.  However, I have learned to "never say
never"... :-)