We want to be able to name AAA attributes. The reason is that we want GSS applications to be able to request these attributes from the gss library so they can get authorization information returned from the AAA server.
That's relatively easy for standardized attributes. What do we do about vendor specific attributes (VSAs)? At the Moonshot meeting last September, people were assuming that VSAs were uniform in format. That's not true. There is a suggested format in the RADIUS spec (I have not looked at Diameter). However it's not used by everything. So, how do we want to name these attributes? I guess one option is to define attribute names for the recommended VSA format and later if there are VSA formats that are used in abfab, we can describe how they are handled. One robustness concern is this means that a GSS implementation needs to parse each VSA and be robust even if it is mall-formed under the standard format. Another implication is that an attribute may end up generating incorrect names because it happens to parse under the recommended format even when that is not the actual format. _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
