Capability Exchange Requirements draftliorradextendtoendcaps00 txt Avi Lior Bridgewater

Capability Exchange Requirements draft-lior-radext-end-to-end-caps-00. txt Avi Lior, Bridgewater Systems Farid Adrangi, Intel Capability Exchange Requirements

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 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… 62 nd IETF

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. 62 nd IETF

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. 62 nd IETF

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 62 nd IETF

Granularity • Each capability can be viewed as having subcapabilities: – Prepaid capability • Volume, Duration etc, other prepaid feature – Location capability • Civil, geo, level of accuracy etc… 62 nd IETF

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. 62 nd IETF