Subject: [Dime] [Fwd: REVISED ANNOUNCEMENT Protocol Action: 'RADIUS Filter Rule Attribute' to Proposed Standard]

From: Hannes Tschofenig <[email-masked]>
Date: Tue, 30 Jan 2007 12:28:58 -0500

FYI

-------- Original Message --------
Subject: 	REVISED ANNOUNCEMENT Protocol Action: 'RADIUS Filter Rule 
Attribute' to Proposed Standard
Date: 	Tue, 30 Jan 2007 12:07:16 -0500
From: 	The IESG <[email-masked]>
To: 	IETF-Announce <[email-masked]>
CC: 	Internet Architecture Board <[email-masked]>, RFC Editor 
<[email-masked]>, radext mailing list 
<[email-masked]>, radext chair <[email-masked]>

The IESG has approved the following document:

- 'RADIUS Filter Rule Attribute '
   <draft-ietf-radext-filter-08.txt> as a Proposed Standard

This document is the product of the RADIUS EXTensions Working Group. 

The IESG contact persons are David Kessens and Dan Romascanu.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-radext-filter-08.txt

Technical Summary
 
 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.    
 
Working Group Summary
 
 This document is a product of the radext working group.
 
Protocol Quality
 
 David Kessens has reviewed this document for the IESG.

Note to RFC Editor
 
 In '1.  Introduction':

 OLD:

  However, in situations where the server
  operator does not know which filters have been pre-populated, it
  useful to specify filter rules explicitly.
  
 NEW:

  However, in situations where the server
  operator does not know which filters have been pre-populated, it
  is useful to specify filter rules explicitly.

--
to unsubscribe send a message to [email-masked] with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

_______________________________________________
DiME mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/dime