1 / 8

Extended RADIUS Attributes

Extended RADIUS Attributes. Monday July 10, 2006 Barney Wolff IETF 66, Montreal, Canada. RADIUS Extended Attributes. draft-wolff-radext-ext-attribute-00.txt Needs updating, at least to add acknowledgement to Jari Arkko as the original proposer of this feature

baxter
Download Presentation

Extended RADIUS Attributes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Extended RADIUS Attributes Monday July 10, 2006 Barney Wolff IETF 66, Montreal, Canada

  2. RADIUS Extended Attributes • draft-wolff-radext-ext-attribute-00.txt • Needs updating, at least to add acknowledgement to Jari Arkko as the original proposer of this feature • Delete mention of RADIUS designer imagination • This is transfer syntax, must support desired power & flexibility available to definers of new RADIUS features

  3. Evaluation Criteria • Top priority • remove 255 limit on attribute type number • remove 253 limit on attribute value length • support rich set of standard attribute value types • support grouping • easy transition of attributes from VSA to standard

  4. Evaluation Criteria • Mid priority • ease of gatewaying  Diameter • support multi-level (nested) grouping • M-bit • build on / re-use existing work • Low priority • minimal attribute header size • elegance, alas

  5. How to evaluate the choices? • Should agree on criteria & priorities before evaluating formats! • Ideally, should have agreed on criteria & priorities before even thinking about formats, as too easy to warp to favor pet format, but too late now.

  6. Advantages of using Diameter attribute header format • Satisfies all top & mid priority criteria • All new RADIUS features need Diameter spec too; minimizes author work • Grouped sub-attributes are together in specified order, making validation & display straightforward • Definite - no need to spend time debating fine points of format

  7. Disadvantages of using Diameter attribute header format • Verbose, custom header could be somewhat smaller • Few would call it beautiful • NIH^H^H^HNot under sole control of RADEXT WG

  8. Feedback?

More Related