RFC6929 - support for 4 octets vendorId?

Alan DeKok aland at deployingradius.com
Mon Dec 14 16:26:04 CET 2015


On Dec 14, 2015, at 4:03 AM, Vereecke, Katrien (Katrien) <katrien.vereecke at alcatel-lucent.com> wrote:
> RFC6929 states that it is recommended to support 4 octets for the vendorId field.
> 
> When I try to test this using  freeradius server , version V3.0.x I get the error :
> Errors reading dictionary: dict_init: /usr/local/share/freeradius/dictionary.alcatel.sr.ext[117]: dict_addvendor: Cannot handle vendor ID larger than 2^24
> Is it not supported yet in freeradius version V3.0.x?

  Arran's reply answers this directly.

  I'll add another note.  The highest IANA private enterprise number is currently 46935.  FreeRADIUS was assigned 11344 in 2000 or so.  So that's about 2000 numbers assigned per year.

  The PEC hasn't even broken 16 bits yet.  I think it will be a *long* time before we need 24 bits.

  Mandating 32 bits is useful for "future proofing" the specs.  But realistically, there is no need for it in my lifetime.

  Alan DeKok.




More information about the Freeradius-Users mailing list