1 / 8

Gonzalo.Camarillo@ericsson

Consent Reqs and Framework draft-ietf-sipping-consent-reqs-00.txt draft-ietf-sipping-consent-framework-00.txt. Gonzalo.Camarillo@ericsson.com. Requirements. One addition requested:.

alina
Download Presentation

Gonzalo.Camarillo@ericsson

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Consent Reqs and Frameworkdraft-ietf-sipping-consent-reqs-00.txtdraft-ietf-sipping-consent-framework-00.txt Gonzalo.Camarillo@ericsson.com

  2. Requirements • One addition requested: When a relay sends a message to a user, it should be possible for the user to figure out which permissions server granted permission for that action and also any credentials that the user would need to revoke that permission.

  3. Framework: Two Operations • Authorize translations for incoming requests • E.g., a MESSAGE arrives to a proxy • Authorize translations beforehand • E.g., a UA registers (i.e., sets up a translation) and wants to set the permissions for this translation before receiving any request

  4. Example (1) A Relay + XCAP Server B |(1) MESSAGE list@relay | | |-------------------------->| | |(2) 470 Consent Needed | | |Call-Info: 123@relay; | | |purpose= wait-permission | | |xyz@relay | | |<--------------------------| | |(3) CONSENT xyz@relay | | |-------------------------->| | | |(4) CONSENT B | | |Permission-Requested: uri-req | |-------------------------->| | |(5) 202 Accepted | | |<--------------------------| |(6) 202 Accepted | | |<--------------------------| | |(7) SUBSCRIBE 123@relay | | |-------------------------->| | |(8) 200 OK | | |<--------------------------| | |(9) NOTIFY (no permission) | | |<--------------------------| | |(10) 200 OK | | |-------------------------->| |

  5. Example (2) A Relay + XCAP Server B | |(11) XCAP uri-req | | |Get Requested Permission | | |<--------------------------| | |(12) 200 OK | | |Permission Document | | |URI to Upload: uri-up | | |-------------------------->| | |(13) XCAP uri-up | | |Permission Document | | |<--------------------------| | |(14) 200 OK | | |-------------------------->| |(15) NOTIFY (permission) | | |<--------------------------| | |(16) 200 OK | | |-------------------------->| | |(17) MESSAGE list@relay | | |-------------------------->| | | |(18) MESSAGE B | | |-------------------------->|

  6. Open Issue • XCAP is used to upload permission document • Other options?

  7. Authorizing Translations Beforehand Joe@ example.com Registrar Joe@ terminal12 terminal28 |(1) REGISTER Joe.Smith@example.com | |To:Joe@terminal28.example.com | |-------------------------->| | |(2) 200 OK | | |<--------------------------| | |(3) CONSENT Joe.Smith@example.com | |-------------------------->| | | |(4) CONSENT Joe@terminal28.example.com | |Permission-Requested: uri-req | |-------------------------->| | |(5) 202 Accepted | | |<--------------------------|

  8. Open Issue • Option 1 • Using CONSENT as described in the previous flow • Option 2 • Flag in the REGISTER so that the registrar sends a CONSENT to the Contact being registered • I.e., we get rid of message (3) in the previous flow)

More Related