Can we setup a vsa allocation tied to an iana registry? Skickat från min iPad
18 okt 2011 kl. 09:42 skrev Sam Hartman <[email protected]>: > > > Hi. > > We need a couple of RADIUS attributes. Realistically I don't think we > can get our attributes from the standard IETF namespace: it's basically > running out of attributes. There's work in radext > (draft-ietf-radext-radius-extensions) to extend the namespace. > > we could create a normative dependency on that work. I have two > concerns: > > 1) It's moving kind of slowly. > > 2) It requires significant changes to client and server RADIUS > libraries. For example the libraries I'm familiar with identify > attributes either by a 32-bit identifier (16 bits of vendor and 16-bits > of attribute) or as a vendor plus an attribute. It's not entirely > obvious what interface changes will need to be made to support these new > attributes, but it's quite clear something is required and it's not done > yet. > > For those of us implementing today it's be really convenient to use > RADIUS attributes from a VSA space. Personally I don't see the problem > with this so long as the organization in question is willing to give up > change control of at least those attributes to the IETF. It's possible > we could get push back from the IESG. > > I'd like to ask the WG though about whether we are willing to try and > use VSA space in a standard assuming we can get change control of the > attributes in question. I think it will significantly help our > time-to-market and will not have any cost other than cleanliness of > standard. > _______________________________________________ > abfab mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/abfab _______________________________________________ abfab mailing list [email protected] https://www.ietf.org/mailman/listinfo/abfab
