request for radius dictionary EVS entry examples

[Alan DeKok]

On Feb 20, 2020, at 10:16 AM, <robert.stannard at bt.com> <robert.stannard at bt.com> wrote:
> Thank you for the example in your email below. I've copied the example here,
> 
> 
> BEGIN-VENDOR BT format=Extended-Vendor-Specific-1
> ATTRIBUTE BT-Foo-Bar 1 integer
> ATTRIBUTE BT-Bar-Baz 2 integer
> ...
> END-VENDOR BT

Yes.

> Could I ask a couple of follow-up questions then please. Following your example then would,
> 
>> ATTRIBUTE BT-Foo-Bar 1 integer
> 
> 
> translate to a dictionary reference-id of,

 RFC 6929 calls this an "OID".

> 
>> 241.26.594.1

Yes.

> where,
> 
> 241.26 = Extended-Vendor-Specific-1 (evs data-type)
> 
> 594 = BT

Yes.

> 1 = BT-Foo-Bar

Yes.  :)

> and similarly for,
> 
>> ATTRIBUTE BT-Bar-Baz 2 integer
> 
> 
> this becomes,
> 
>> 241.26.594.2

Exactly.

> so when we read the dictionary file and find
> 
> format=Extended-Vendor-Specific-1
> 
> we need to "look-up"
> 
>> Extended-Vendor-Specific-1 from our dictionaries to retrieve the 241.26 id - so this means that the definitions for evs need to have been loaded first before we can reference them as in the example you have shown?

Yes.  The "Extended-Vendor-Specific-1" attribute MUST be loaded before the vendor dictionaries which use it.

Alan DeKok.