1 / 7

Capability Exchange Requirements

This draft document outlines the capability exchange requirements between RADIUS servers and NAS devices to ensure correct operation. It covers the need for NAS devices to understand and implement prepaid attributes, the benefits of knowing supported RADIUS features, and the ability for NAS devices and servers to indicate their specific needs. The granularity of capabilities and the extensibility of the exchange process are also discussed.

kritchie
Download Presentation

Capability Exchange Requirements

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. Capability Exchange Requirements draft-lior-radext-end-to-end-caps-00.txt Avi Lior, Bridgewater Systems Farid Adrangi, Intel Capability Exchange Requirements

  2. Mandatory for Correct Operation • For certain services, the RADIUS server must know the capabilities that are supported by the NAS. Prepaid: when a prepaid user is connected to the network, access MUST only provided if the NAS can understand and implement the prepaid attributes – Otherwise, the NAS will ignore the attributes and the user will get free service. Allows us to prevent revenue leakage/fraud etc…

  3. Helps Efficiency • In certain situations it will be useful for the RADIUS server to know which RADIUS features are supported by a NAS. • What’s the point of sending a Disconnect Message or COA if the NAS does support 3576? • Knowing what is supported helps us be more efficient and also allows us to determine how certain services can be delivered.

  4. NAS Indicates Needs • In certain circumstances the NAS may need to indicate to the RADIUS server that it needs certain information. • NAS or Proxy may need Chargeable User Identity.

  5. Server Indicates Needs • In some cases, the server may need to indicate to the NAS that it needs some functionality. • NAS indicates support for Logoff message, the server can as the NAS to provide logoff messages. • NAS indicates that it can provide location information, the Server can then request the NAS deliver location information

  6. Granularity • Each capability can be viewed as having sub-capabilities: • Prepaid capability • Volume,Duration etc, other prepaid feature • Location capability • Civil, geo, level of accuracy etc…

  7. Summary and other items • Capability Exchange is end-to-end • Bi-directional • Fine grained • Needs to be extensible • Transported on a session-by-session • Express whether a feature is required or supported. • Allows us to have the concept of MANDATORY attributes.

More Related