RE: Issue 130: Diameter Compatibility

[<john.loughney@nokia.com>]

I agree, Bernard's proposal seems reasonable.

John 

>-----Original Message-----
>From: owner-radiusext@ops.ietf.org 
>[mailto:owner-radiusext@ops.ietf.org] On Behalf Of ext Jari Arkko
>Sent: 08 September, 2005 11:04
>To: Bernard Aboba
>Cc: radiusext@ops.ietf.org
>Subject: Re: Issue 130: Diameter Compatibility
>
>Bernard Aboba wrote:
>
>>The NAS-Filter-Rule attribute defined in the document is not 
>compatible 
>>with the NAS-Filter-Rule attribute defined in RFC 4005, which 
>is based 
>>on the IPFilterRule type defined in RFC 3588.
>>This incompatibility will break RADIUS/Diameter gateways. 
>>  
>>
>This is a problem.
>
>>My suggestion is to define the restrict the NAS-Filter-Rule attribute 
>>to the RFC 3588 syntax, and define additional attributes for other 
>>purposes, such as Layer 2 filtering and HTTP redirect. It is 
>ok if the 
>>same general syntax is used for these other filters, but they need to 
>>be defined as separate attributes to enable translation of 
>>NAS-Filter-Rule AVP from RADIUS to Diameter and back.
>>  
>>
>Sounds like a good suggestion to me.
>
>--Jari
>
>
>--
>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/>
>

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