1 / 4

Event Package for User Profiles draft-ietf-sipping-config-framework-01.txt

Event Package for User Profiles draft-ietf-sipping-config-framework-01.txt. Dan Petrie dpetrie@pingtel.com Pingtel Corp. Differences from simple xcap package. Token represents the profile type (as opposed to URI)

lamar-tate
Télécharger la présentation

Event Package for User Profiles draft-ietf-sipping-config-framework-01.txt

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. Event Package for User Profilesdraft-ietf-sipping-config-framework-01.txt Dan Petrie dpetrie@pingtel.com Pingtel Corp.

  2. Differences from simple xcap package • Token represents the profile type (as opposed to URI) • Multiple profiles may be associated with the token e.g. device may imply device profile and default user profile • Profile and deltas provided via content indirection (as opposed to deltas in body)

  3. Data Delivery Security • AES to encrypt profile on server, decrypt on UA MUST? • MAY use basic/digest authentication over HTTPS • MAY use client certificate to authenticate

  4. Other issues from the list • Need clarification of discovery process • Need clarification of the user vs. device profile semantics and rational • Missing IANA Considerations • Event header parameter names • Profile type tokens

More Related