RADIUS Filter Rule Attribute
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Internet Architecture Board <email@example.com>, RFC Editor <firstname.lastname@example.org>, radext mailing list <email@example.com>, radext chair <firstname.lastname@example.org> Subject: Protocol Action: 'RADIUS Filter Rule Attribute' to Proposed Standard The IESG has approved the following document: - 'RADIUS Filter Rule Attribute ' <draft-ietf-radext-filter-09.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-09.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.