80 likes | 100 Views
Session-Independent Policies draft-hilt-sipping-session-indep-policy-01. Volker Hilt volkerh@bell-labs.com Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com Jonathan Rosenberg jdrosen@dynamicsoft.com. Session-Independent Policies. XML-schema for session policy documents.
E N D
Session-Independent Policiesdraft-hilt-sipping-session-indep-policy-01 Volker Hilt volkerh@bell-labs.com Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com Jonathan Rosenberg jdrosen@dynamicsoft.com
Session-Independent Policies • XML-schema for session policy documents. • User Agent Profile Delivery Framework to deliver policies to UA. • Other transport mechanisms are possible. • Change Log • Removed framework definition. • Removed event package definition. • Added use of User Agent Profile Delivery Framework. • Number of fixes.
Considerations for Session-Specific Policiesdraft-hilt-sipping-consider-policy-00 Volker Hilt volkerh@bell-labs.com Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com
Session-Specific Policies • Pervious draft proposed to piggyback policy operations onto INVITE – OK – ACK cycle. • But this proved to have two major problems: • Requires that both UAs support policies. • Does not support “asynchronous” policies. • This makes the piggyback approach unsuitable as a general purpose model!
Separation of Tasks • Session-specific policies involve two tasks: • UA needs to disclose information about the current session to a proxy. • Proxy needs to send policy instructions to the UA. • Policies may require the first or both tasks. • Policies can apply to the • offer and / or • answer. • A mechanisms must support both tasks on both directions of the offer/answer exchange.
Sending Policy Instructions A P B Policies INV (offer) • Use a separate channel from proxy to UA. • UA uses subscription to policies. • Receives NOTIFYs on new and updated policies. • How is the URI for policy subscriptions provided to UA? • Proxy provides URI in a header / 4xx response body or • URI is provided through configuration. • Same mechanism as session-independent policies. INV (offer) Policies 200 (answer) 200 (answer) ACK ACK Fig. 1: Offer in INVITE request A P B INV INV Policies 200 (offer) 200 (offer) Policies ACK (answer) ACK (answer) Fig. 2: Offer in INVITE response
Disclosing Session Information A P B A P B INV (offer) INV (offer) INV (offer) INV (offer) 200 (answer) 200 (answer) 200 (answer) 200 (answer) • Two alternatives to disclose session information: • Piggyback model (along with the offer/answer). • Use a separate channel. ACK ACK ACK ACK Fig. 1: P provides policies for A / Offer in INVITE request Fig. 2: P provides policies for B / Offer in INVITE request A P B A P B INV INV INV INV 200 (offer) 200 (offer) 200 (offer) 200 (offer) ACK (answer) ACK (answer) ACK (answer) ACK (answer) Fig. 3: P provides policies for A / Offer in INVITE response Fig. 4: P provides policies for B / Offer in INVITE response
Open Issues • Which model fits best? • Separate Channel for sending policy instructions / Piggyback for session information disclosure. • Separate Channel for both. • How can a separate channel be realized? • Protocol other than SIP. • Disclose session information through other protocol / send policy instructions using SUBSCRIBE/NOTIFY. • SUBSCRIBE/NOTIFY for information disclosure (SUBSCRIBE) and policy instructions (NOTIFY). • Comments/Opinions/Feedback?