Volker Hilt volkerh@bell-labs Gonzalo Camarillo Gonzalo.Camarillo@ericsson

1. Session-Independent Policiesdraft-ietf-sipping-session-indep-policy-03 Volker Hilt volkerh@bell-labs.com Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com Jonathan Rosenberg jdrosen@cisco.com

2. Status & Changes • Minor editorial changes. • Policy format is aligned with profile datasets framework. • Policy format defines a data set for media policies. • General concepts are discussed in profile datasets framework. • Changes to draft structure. • General attributes imported from profile datasets framework: • policy/excluded-policy, direction, q, visibility • Media-specific attributes: • stream-label, media-type • Common merging rules are discussed in datasets framework. • Use of merging rules and attributes is defined individually for each element.

3. Policy Format • Elements • <media-types> / <media-type> • Policy for the use of media types. • <codecs> / <codec> • Policy for the use of codecs. • <media-intermediary> • Insert an intermediary into media stream. • Intermediary types: IP-in-IP, IP-loose, TURN, media-specific, none. • <max-bandwidth> • Defines maximum bandwidth available to a UA. • <qos-dscp> • DSCP value to be used on streams.

4. Open Issues / Next Steps • Comments on the policy format needed. • How does a UA indicate support for the policy format? • Change the way drafts are split. • Session policy format draft • Session policy delivery mechanism draft

5. Session-Specific Policy Use Casesdraft-hilt-sipping-policy-usecases-00 Volker Hilt volkerh@bell-labs.com Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com

6. General Usage Pattern • UA provides session information to policy server. • UA describes the aspects of the session it wants to set up. • IP addresses, ports, codecs, media types, bandwidth estimate,… • “Ask if described session is permitted.” • Policy server responds with a policy. • The types of policy responses are possible: • Allow the session as it was proposed. • Allow the session if the supplied policies are applied. • Reject the session. • Policies may be updated during a session. • “Return acceptance decision possibly requiring changes to the session.”

7. Session-Specific Policiesdraft-hilt-sipping-session-spec-policy-03 Volker Hilt volkerh@bell-labs.com Gonzalo Camarillo Gonzalo.Camarillo@ericsson.com Jonathan Rosenberg jdrosen@cisco.com

8. Open Issues UA A Proxy A UA B • Design of the policy channel between UA and policy server. • Submit session information to policy server. • Retrieve session policies from policy server. Policy Server A

9. Retrieve Session Policies (1) • Subscription-based mechanism. • UA subscribes to policies on the policy server. • Policy server URI received during INVITE transaction. • Subscription covers the policies the policy server has composed for the UA. • One subscription per session or • Long-running subscription covering all active sessions. • Policies and policy changes are conveyed via notifications.

10. Retrieve Session Policies (2) • Current mechanism is based on the configuration framework. • Introduces new profile type ‘policy’. • Decouples subscriptions to session-specific policies from other sources of profile information. • Same mechanism as for session-independent policies. • Adds another source of policy information the UA needs to consider for its sessions. • Alternative: define a new policy event package.

11. Submit Session Information • Proposal: PUBLISH-based mechanism • UA uses PUBLISH to convey information about current session to the policy server. • Policy server composes policies for the UA and makes them available through a subscription. • UA can set up subscription and publish session information at the same time. • Third parties may also publish information that is relevant to session policies.