Consentbased Communications in SIP RFC 4453 draftietfsippingconsentframework05'txt draftcamarillosip

1
Consent-based Communications in SIPRFC
4453draft-ietf-sipping-consent-framework-05.txt
draft-camarillo-sipping-consent-format-01.txt
draft-camarillo-sipping-pending-additions-00.txt

• Gonzalo.Camarillo_at_ericsson.com

2
Architecture
PermissionRequest
Permission Server
Client
Relay
Translation Logic
Permissions
Permission Request
Manipulation
Permission Grant
Recipient
3
(No Transcript)
4
Open Issue

• How to obtain the URI to subscribe to the
  pending additions event package?
• Proposal follow the model used in conferencing
• The URI of the URI-list service is used to
  subscribe to this event package

5
Addition

• When a request-contained URI-list contains one
  URI for which there are no permission, the relay
  can request permissions for it directly

6
Change

• When a client attempts to add more than one URI
  at a time using XCAP, the relay could return a
  408 instead of a 403 (Forbidden) response

7
Terminology

• Should we still define a logical element called
  Permission Server or shall we simply call it a
  store-and-forward server?