Presentation is loading. Please wait.

Presentation is loading. Please wait.

Consent Reqs and Framework draft-ietf-sipping-consent-reqs-00.txt draft-ietf-sipping-consent-framework-00.txt

Similar presentations


Presentation on theme: "Consent Reqs and Framework draft-ietf-sipping-consent-reqs-00.txt draft-ietf-sipping-consent-framework-00.txt"— Presentation transcript:

1 Consent Reqs and Framework draft-ietf-sipping-consent-reqs-00.txt draft-ietf-sipping-consent-framework-00.txt

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

5 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 | | | >| | | |(18) MESSAGE B | | | >| Example (2)

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

7 Authorizing Translations Beforehand example.com Registrar terminal12 terminal28 |(1) REGISTER | | | >| | |(2) 200 OK | | |< | | |(3) CONSENT | | >| | | |(4) CONSENT | |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)


Download ppt "Consent Reqs and Framework draft-ietf-sipping-consent-reqs-00.txt draft-ietf-sipping-consent-framework-00.txt"

Similar presentations


Ads by Google