![]() In this article, we’ll look at two main approaches to QoS: IntServ and DiffServ, their strengths and limitations, and when to use which one. But what about other parts of the network like the pre-existing routers, switches and firewall? All it takes is one missing link for the whole system to be compromised. Yes, the IP PBX and the IP endpoints will already be configured for QoS. Without configuring their data network for quality of service (QoS), they will experience a severe deterioration in voice quality and may regret making the decision to switch. They install an IP PBX and buy some IP phones. More precise definitions (i.e.Your customer using a legacy phone system decides to switch to voice over internet protocol (VoIP).Do we need to encode session hierarchy in the session id?.How does this work with the different authorization models (RFC2904).The End San Diego IETF, December 2000: AAAARCH Meeting - Session ID Number of open issues San Diego IETF, December 2000: AAAARCH Meeting - Session ID.audit_server user: audit info X, Y, Z, V, W San Diego IETF, December 2000: AAAARCH Meeting - Session ID audit request) user audit_server: query X audit_server CP: X. auditing information is transferred to trusted server during session lifetime.Session ID: Unique ID in the scope of the service San Diego IETF, December 2000: AAAARCH Meeting - Session IDĮxample: VoD over Diffserv 1 ID: X ID: X Y User CP X (Content) X Y (Diffserv Access) Y TP 2 TP 1 Z (Diffserv) Z ID: Y ID: Z Z CP: Content Provider TP: Transport Provider San Diego IETF, December 2000: AAAARCH Meeting - Session IDĮxample: VoD over Diffserv 2 ID: Y ID: Y Z User CP Y (Content) Z (Diffserv Access) X Y Z TP 2 TP 1 X (Diffserv) ID: X ID: X Z CP: Content Provider TP: Transport Provider San Diego IETF, December 2000: AAAARCH Meeting - Session IDĮxample: VoD over Diffserv 3 ID: X ID: X Y, Z User CP X (Content) Y (Diffserv Access) Z V X W Z Y ID: V V (Diffserv) TP 2 TP 1 ID: V W Y W (Diffserv) ID: W Z TP 3 CP: Content Provider TP: Transport Provider San Diego IETF, December 2000: AAAARCH Meeting - Session ID.Service ID: Identify a service at a AAA server.AAA ID: Global unique ID of the AAA server.Simple scheme to create global unique ID: AAA ID + Service ID + Session ID.user and/or server specific information.Server generates ID during initial message exchange (e.g.Security is important San Diego IETF, December 2000: AAAARCH Meeting - Session ID. ![]() ![]() SDP/SAP San Diego IETF, December 2000: AAAARCH Meeting - Session ID.IP address, start time) San Diego IETF, December 2000: AAAARCH Meeting - Session ID Late Binding: Binding is not done during session lifetime but is created later if needed based on attributes (e.g.Peer-to-peer Binding: Two “equal” sessions without specifying hierarchy.Hierarchical Binding: Subsession IDs are derived from supersession (e.g.Different service sessions that logically belong together Binding needed for Auditing and Accounting San Diego IETF, December 2000: AAAARCH Meeting - Session IDīinding Objectives Session Auth Authoriz Service Usage Accounting Subsession 1 Subsession 2 Time San Diego IETF, December 2000: AAAARCH Meeting - Session ID.Accounting records (maybe generated by different hosts) which provide the accounting data for the services a user has used.Authentication, Authorization and Accounting with the Service provisioning process (Service Session).Summary San Diego IETF, December 2000: AAAARCH Meeting - Session ID.Session ID Georg Carle, John Vollbrecht, Sebastian Zander, Tanja Zseby San Diego, December 2000
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |