[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Issue: Diameter-RADIUS gateway behavior not completely specified



Barney Wolff <mailto:barney@databus.com> scribbled on Saturday, August
26, 2006 4:00 PM:

> On Sat, Aug 26, 2006 at 01:45:00PM -0700, Glen Zorn (gwz) wrote:
>> Barney Wolff <mailto:barney@databus.com> scribbled on Saturday,
>> August 26, 2006 12:34 PM: 
>> 
>>> I agree that the behavior should be specified.  It would seem that
>>> this is an opportunity to take advantage of Diameter's M-bit in
>>> governing the gateway's behavior.
>> 
>> Not sure how the M-bit helps.  Can you elaborate?
> 
> Sorry, I thought it was obvious:  An attribute lacking the M-bit may
> legitimately be ignored, so may be eliminated in translation.  Not so
> if the M-bit is set. 

Right, but RFC 4005 says that the M-bit MUST be set on the
NAS-Filter-Rule AVP...

Hope this helps,

~gwz

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