dime-1----Page:4
1 2 3 4
|
Design Considerations Common Tradeoffs Use of a single applications can lead to monolithic architectures Can be similar to a RADIUS model Complex management for distributed architectures Co-relation of application services, i.e. separation of authentication and authorization Increased traffic and implementation footprint Accounting support Base protocol accounting, split model ACR/ACA using app-id of the application, coupled model Generic extensions Common to any applications, i.e. redundancy, auditing, congestion control etc. Typically should not require a new application if: Peer-to-peer End-to-end but can be piggybacked to application traffic, i.e. Proxy-Info AVP Application Id used in base protocol session messages Application level messages RAR/RAA, STR/STA and ASR/ASA should use the application id of the application Server initiated request and Diameter user sessions |