|
> Note that the Vendor type field in the recommended VSA format is only > a single octet, like the RADIUS type field. While this limitation > results in an efficient encoding, there are situations in which a > vendor or SDO will eventually wish to define more than 255 > attributes. Also, an SDO can be comprised of multiple subgroups, > each of whom can desire autonomy over the definition of attributes > within their group. > > These desires have led vendors to define the following non-standard > VSA formats: How about this? "Note that the Vendor type field in the recommended VSA format is only a single octet, like the RADIUS type field. While this limitation results in an efficient encoding, there are situations in which a vendor or SDO will eventually wish to define more than 255 attributes. Also, an SDO can be comprised of multiple subgroups, each of whom can desire autonomy over the definition of attributes within their group. The most interoperable way to address these issues is for the vendor or SDO to request allocation of multiple Vendor identifiers. However, instead of doing this, vendors have defined the following non-standard VSA formats:" |