rfc6929 radius ext - nested tlv format question

[Vereecke, Katrien (Katrien)]

Hello,

I have a question regarding the nesting of radius attributes according to rfc6929.

I am using the freeradius-server  version V3.0.x and I defined as test the following in my dictionary :
ATTRIBUTE  Test-Attr-50     241.50  tlv
ATTRIBUTE  Test-Attr-50_1   241.50.1 octets
ATTRIBUTE  Test-Attr-50_1_2 241.50.1.2 string

And in the users file :
Test-Attr-50_1 = 0x112233,
Test-Attr-50_1_2 = "testString50",

These attributes are sent in the access-accept:
(156) Sent Access-Accept Id 247 from 138.203.10.191:1812 to 138.203.10.123:64395 length 0
(156)   Test-Attr-50_1 = 0x112233
(156)   Test-Attr-50_1_2 = "testString50"

I expected that this would give problems because the attribute 241.50.1 is not defined as tlv in the dictionary, but the wireshark shows that the attribute includes both the octets for Test-Attr-50_1 and the nested attribute Test-Attr-50_1_2 .
Is the above a valid configuration? When decoding this attribute, how can one distinguish whether 241.50.1 contains real data or again a nested attribute 241.50.1.2?

f1 18 32 01 05 11 22 33 01 10 02 0e 74 65 73 74 53 74 72 69 6e 67 35 30

Thanks,
Kind regards,
Katrien.