[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Issue 37: Merging of Filter Attributes

To: "Nelson, David" <dnelson@enterasys.com>
Subject: RE: Issue 37: Merging of Filter Attributes
From: Bernard Aboba <aboba@internaut.com>
Date: Tue, 25 Jan 2005 14:19:10 -0800 (PST)
Cc: radiusext@ops.ietf.org
In-reply-to: <2A5E4540D4D5934D9A1E7E0B0FDB2D69E190C0@MAANDMBX2.ets.enterasys.com>
References: <2A5E4540D4D5934D9A1E7E0B0FDB2D69E190C0@MAANDMBX2.ets.enterasys.com>

> Does this issue exist in "merging" two or more instances of Filter-ID?

RFC 2865 doesn't have much to say on this subject, other than that zero
or more instances of Filter-Id can be included in an Access-Accept.  In
my experience, implementations merge the filters in the order they are
specified.  But perhaps there are implementations that do not do this?


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

References:
- RE: Issue 37: Merging of Filter Attributes
  - From: "Nelson, David" <dnelson@enterasys.com>

Prev by Date: RE: Issue 37: Merging of Filter Attributes
Next by Date: RE: Issue 37: Merging of Filter Attributes
Previous by thread: RE: Issue 37: Merging of Filter Attributes
Next by thread: RE: Issue 37: Merging of Filter Attributes
Index(es):
- Date
- Thread