[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
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."
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.
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <radiusext@ops.ietf.org>
Subject: Comments on draft-ietf-radext-filter-05 Date: Thu, 30 Nov 2006
23:37:40 +0200
A couple of editorial comments:
1. Acronyms in the Abstract section should be expanded. In this document
NAS and AVP are present in the Abstract section and not expanded (but
RADIUS is!)
2. In the format description there is no explanation about the Length
field other than saying '>=3'. While this may be normal in a document
where Length is explained some other part, or may be easy to understand
for people familiar with the other RADIUS documents, it is cryptic for
the reader of this document alone. It would be useful to provide at
least a reference for a definition of the Length of a attribute in
another document.
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/>
--
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/>