[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue: Attribute concatenation/splitting
Submitter name: Pasi Eronen
Submitter email address: firstname.lastname@example.org
Date first submitted: June 30, 2006
Comment type: 'T'echnical
Priority: 'S' Must fix
Section: 2 and 4
Rationale/Explanation of issue:
Section 2 currently says that "Where more than one NAS-Filter-Rule
attribute is included in a RADIUS packet, the attributes MUST be
consecutive and it is assumed that the attributes are to be
concatenated to form a single filter list."
I guess this means that a single long rule can be split into multiple
NAS-Filter-Rule attributes? And a single NAS-Filter-Rule attribute
could contain pieces of multiple rules? If so, I'd recommend
separating the individual rules somehow. In the current version of
NAS-Traffic-Rule each individual rule ends with LF, making it easy to
determine where one rule ends and another one begins. I'd suggest
adopting this same convention for RADIUS NAS-Filter-Rule.
This concatenation/splitting has also implications for Diameter
translation (Section 4): AVPs coming from Diameter side may have to be
split to several RADIUS attributes (and rule delimiters added), and
attributes coming from RADIUS side have to be concatenated/split to
Diameter AVPs (and rule delimiter removed).
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.