RE: Comments on draft-ietf-radext-filter-05

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

> -----Original Message-----
> From: Bernard Aboba [mailto:bernard_aboba@hotmail.com] 
> Sent: Friday, December 01, 2006 12:12 AM
> To: Romascanu, Dan (Dan) ; radiusext@ops.ietf.org
> Subject: RE: Comments on draft-ietf-radext-filter-05
> 
> Here is a rewritten Abstract:
> 
> "While RFC 2865 defines the Filter-Id attribute, this 
> requires that the Network Access Server (NAS) be 
> pre-populated with the desired filters.
> However, in situations where the server operator does not 
> know which filters have been pre-populated, it useful to 
> specify filter rules explicitly.
> This document defines the NAS-Filter-Rule attribute within 
> the Remote Authentication Dial In User Service (RADIUS).  
> This attribute is based on the Diameter NAS-Filter-Rule 
> Attribute Value Pair (AVP) described in RFC 4005, and the 
> IPFilterRule syntax defined in RFC 3588."

Thanks, looks good. 

> 
> Indicating that the Length value is >3 is a way of sayin that 
> a data field of zero length (e.g. Length =2) is not 
> acceptable for the NAS-Filter-Rule attribute.

I know, but this is cryptic for somebody who is not that familiar with
the stile of other RADIUS documents. 

Dan


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