sipping-2----Page:6
1 2 3 4 5 6
|
Session-Dependent Policies (2) Open issues (cont.) Two party consent vs. one party consent. The current requirements are based on a two party consent model: Both UAs need to know all policies (REQ-CON-1 and REQ-CON-2) Proxies need to know the accepted policies (REQ-CON-5 and REQ-CON-6). Two party consent requires a three pass policy exchange. But: the third pass does not exist in “empty” INVITE and UPDATE flows. Approach 1: Two party consent Send policy information in a separate message (SUBSCRIBE/NOTIFY, INFO,...). Approach 2: One party consent (as discussed for OPES in RFC3238) Only one UA needs to know about and agree to a policies. Since each UA can set up a session policy locally, one party consent does not change the current model. Works with the two-way offer answer model. How to proceed? |