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

Re: subtypes




My two cents (again :-) )about possible attribute format to carry subattributes.
When I say "subattribute" I speak about service or application specific
attributes which must be sended to specific hardware or software.



Type -- Attribute type. may be 226 for example


SoA ID -- Service or Application ID.  We can assign standard numbers to
services (SIP, WiFi, LAN etc) and applications (Prepaid etc). So all
vendors can use it in their products.

SoA Type -- Service or Application Type. This is SoA attribute type.

Tag -- tag to allow attribute assemble/disassemle (like EAP)


+---------------------------------------------------------------+ |0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1| +---------------+---------------+-------------------------------+ | Type (226) | Length | SoA ID | +---------------+---------------+-------------------------------+ | SoA Type | Tag | SoA length | +---------------+---------------+---------------+---------------+ | Value... +---------------+---


I hope it maybe really help to solve our "subtype problem".



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