100 likes | 219 Views
Diameter General Purpose Session draft-liebsch-dime-diameter-gps-01.txt. M. Liebsch, G. Punz IETF79, Beijing Diameter Extensions (DIME) WG 11 th November 2010. Outline. Idea behind this minor extension Again: Use cases Stepwise Realization Coding options for bulk signaling Next .
E N D
Diameter General Purpose Sessiondraft-liebsch-dime-diameter-gps-01.txt M. Liebsch, G. Punz IETF79, BeijingDiameter Extensions (DIME) WG 11th November 2010
Outline • Idea behind this minor extension • Again: Use cases • Stepwise Realization • Coding options for bulk signaling • Next
History • Initial version presented at IETF78 in Maastricht • Many comments received • First revision addresses comments and adds more details as well as clarifications
Idea behind the GP Session (1/2) • Eshablish a dedicated session (and Session-ID) to signal multi-user context (bulk signaling) GP Session • Clarification: GP Session-ID does not identify a group of users! • GP Session-ID.. • .. allows the re-use of available commands (e.g. STR), which mandate a single Session-ID AVP, to signal attribues/values applying to multiple users • RFC3588: Single Session-ID AVP at fixed location (after Diameter header) identifies the user where subsequent attribute/values apply to • .. indicates that attributes/values apply to a group of users or all users! • .. avoids specification of new command codes and formats for bulk signaling
Idea behind the GP Session (2/2) AVPs apply to single user Single-user context(RFC3588) Diameter Hdr Session-ID AVPs Maintain standard format,but adopt new interpretation AVPs apply to group of users Multi-user context/ Bulk signaling Diameter Hdr GP Session-ID Users AVPs - Group-ID - List of individual Session-IDs - Grouped AVP
Again: Use cases • Bulk signaling, e.g. • Bulk Session Termination using STR • Bulk policy enforcement • Recovery from total/partial Diameter node failure Server states restoration Group policy enforcement server server Req(multiple users [failed_server_id]) Req(multiple users, context1, context2, ...contextN) Resp (multiple users,context1, context2,... contextN) client client PCEF data traffic Policy Enforcement
Stepwise realization of the extended session concept Deployment-specificguidelines forbulk signaling Specify GP Sessionextension Bulk-signaling operation andextensions specified in Applications Deployment by usingRFC4006+ and RFC4005+ Deployment-specific guidelines and specification (e.g. By 3GPP) NASREQRFC4005 BulkExt. BulkExt. NASREQRFC4005+ Credit ControlRFC4006 Credit ControlRFC4006+ GPS GPS Diameter Base RFC3588 Diameter Base RFC3588
Coding options for bulk signaling(in the order of efficiency) • Group-ID identifies multiple users, list of attributes/values applies to all users of the group • List of Session-IDs identifies a group of users, list of attributes/values applies to all users of the group • List of Session-IDs identifies multiple users, each Session-ID has an individual list of AVPs associated Diameter Hdr GP Session-ID AVP 1 AVP 2 AVP N Group-ID Diameter Hdr GP Session-ID AVP 1 AVP 2 AVP N Session-ID 1 Session-ID K Diameter Hdr GP Session-ID Session-ID 1 AVP 1.1 AVP 1.2 AVP 1.N Session-ID K AVP K.1 AVP K.2 AVP K.N
Next • More details to be elaborated and specified • Concept of interest to the DIME WG?