Jonathan Rosenberg dynamicsoft

Slides:



Advertisements
Similar presentations
Internet Peer-to-Peer Application Infrastructure Darren New Invisible Worlds, Inc.
Advertisements

SIP, Presence and Instant Messaging
An Application Component Architecture for SIP Jonathan Rosenberg Chief Scientist.
SIP and Instant Messaging. SIP Summit SIP and Instant Messaging What Does Presence Have to Do With SIP? How to Deliver.
Fall IM 2000 Introduction to SIP Jonathan Rosenberg Chief Scientist.
SIMPLE Open Issues Jonathan Rosenberg dynamicsoft IETF 52.
IM May 24, 2000 Introduction to SIP Jonathan Rosenberg Chief Scientist.
VON Europe /19/00 SIP and the Future of VON Protocols SIP and the Future of VON Protocols: Presence and IM Jonathan Rosenberg.
Fall VoN 2000 SIP for IP Communications Jonathan Rosenberg Chief Scientist.
XCAP Tutorial Jonathan Rosenberg.
Notification Explosion Calendaring –You have a new meeting request –Your meeting begins in 15 minutes SIP –Hello HTTP/WebDAV –A resource you want to edit.
Yunling Wang VoIP Security COMS 4995 Nov 24, 2008 XCAP The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
TCP/IP Protocol Suite 1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter 22 World Wide Web and HTTP.
XML Configuration Access Protocol (XCAP) Jonathan Rosenberg dynamicsoft.
The Future of SIP and Presence Jonathan Rosenberg Chief Scientist.
XCON architecture and protocol musings Henning Schulzrinne Columbia University.
1 The World Wide Web. 2  Web Fundamentals  Pages are defined by the Hypertext Markup Language (HTML) and contain text, graphics, audio, video and software.
JavaScript, Fourth Edition
WebDAV Issues Munich IETF August 11, Property URL encoding At present, spec. allows encoding of the name of a property so it can be appended to.
Abierman-nanog-30may03 1 XML Router Configs BOF Operator Involvement Andy Bierman
Chapter 8 Cookies And Security JavaScript, Third Edition.
1 CS 502: Computing Methods for Digital Libraries Lecture 19 Interoperability Z39.50.
I2RS draft-rfernando-yang-mods.txt I2RS Yang Extensions draft-rfernando-yang-data-mods R.Fernando, P.Chinnakannan, M.Madhayyan, A.Clemm.
Data Manipulation Jonathan Rosenberg dynamicsoft.
1 Web Services Web and Database Management System.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter Five Managing Addresses.
XCAP Jonathan Rosenberg dynamicsoft. Changes in Main Spec Removed POST usage Clarified the meaning of PUT for inserts vs. modifies Added AUID grammar.
SIMPLE Drafts Jonathan Rosenberg dynamicsoft. Presence List Changes Terminology change Presence List Information Data Format –Provides version, full/partial.
XCAP Jonathan Rosenberg dynamicsoft. Agenda XCAP Main spec changes XCAP Main spec open issues XCAP Package changes XCAP Package Open Issues Authorization.
SIP PUBLISH draft-ietf-simple-publish-01 Aki Niemi
Improving SLP Efficiency and Extendability by Using Global Attributes and Preference Filters Weibin Zhao Henning Schulzrinne
REST By: Vishwanath Vineet.
Topics Ahead …. What would the WG produce? Charter description of what we do Things we don’t do.
SIP PUBLISH Method Jonathan Rosenberg dynamicsoft.
SIP file directory draft-garcia-sipping-file-sharing-framework-00.txt draft-garcia-sipping-file-event-package-00.txt draft-garcia-sipping-file-desc-pidf-00.txt.
1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential XCAP Usage for Publishing Presence Information draft-isomaki-simple-xcap-publish-usage-00.
Partial Notifications IETF 56 SIMPLE WG draft-lonnfors-simple-presinfo-deliv-reqs-00 draft-lonnfors-simple-partial-notify-00 Mikko Lönnfors
Directory Services CS5493/7493. Directory Services Directory services represent a technological breakthrough by integrating into a single management tool:
DICOMwebTM 2015 Conference & Hands-on Workshop University of Pennsylvania, Philadelphia, PA September 10-11, 2015 DICOMweb Workflow API (UPS-RS) Jonathan.
Application Configuration Access Protocol Praveen S Thangavelu Nov Advisor: Dr Chung-E-Wang Department of Computer Science, CSUS.
Name of Presentation Red Hat Presenter RED HAT Developer conference Brno 2009 Mobicents/JBCP Pavel Slegr.
Company LOGO OMA Presence SIMPLE. What is OMA? The Open Mobile Alliance (OMA) is a standards body which develops open standards for the mobile phone industry.
XCAP. XML Configuration Access Protocol - an application layer protocol that allows a client to read, write, and modify application configuration data.
Architecture Review 10/11/2004
Session-Independent Policies draft-ietf-sipping-session-indep-policy-02 Volker Hilt Jonathan Rosenberg Gonzalo.
MQTT-255 Support alternate authenticaion mechanisms
MPEG-4 Binary Information for Scenes (BIFS)
XCON WG IETF-64 Meeting XCON Framework Overview & Issues
Using E-Business Suite Attachments
WEB SERVICES From Chapter 19 of Distributed Systems Concepts and Design,4th Edition, By G. Coulouris, J. Dollimore and T. Kindberg Published by Addison.
REST- Representational State Transfer Enn Õunapuu
SIP Configuration Issues: IETF 57, SIPPING
Topics Ahead …. What would the WG produce?
draft-lemonade-imap-submit-01.txt “Forward without Download”
Markus Isomäki Eva Leppänen
draft-ietf-simple-message-session-09
Middleware independent Information Service
Requirements and Implementation Options for the Multiple Line Appearance Feature using the Session Initiation Protocol (SIP) draft-johnston-bliss-mla-req-00.
draft-ietf-geopriv-lbyr-requirements-02 status update
IS333D: MULTI-TIER APPLICATION DEVELOPMENT
CE Operating Systems Lecture 21
Model-View-Controller Patterns and Frameworks
$, $$, $$$ API testing Edition
Architecture Competency Group
Jonathan Rosenberg dynamicsoft
SIP Session Policies Volker Hilt
WebDAV Design Overview
WEB SERVICES From Chapter 19, Distributed Systems
A RELOAD Usage for Distributed Conference Control (DisCo) – Update
Presentation transcript:

Jonathan Rosenberg dynamicsoft Data Manipulation Jonathan Rosenberg dynamicsoft

Where are we Problem Statement Big idea: Use a generic mechanism Manipulate buddy lists (create, list, add, delete) Manipulate authorization policy (black/white lists, per-attribute permissions, etc.) Captured in draft-ietf-simple-data-req Big idea: These are just examples of application data manipulation Use a generic mechanism ACAP is close

What is ACAP? Application Configuration Access Protocol, RFC2244 (Issued November 1997) Target application: Server-based storage and client access to web browser address books and bookmarks Goal: Generic mechanisms for application-independent access to per-user application configuration data from multiple clients

ACAP Quick Summary Protocol operates much like IMAP in its syntax and message flow Client/Server Text-based SASL for security Based on the ACAP Data Model Hierarchical tree of name/value pairs Server doesn’t care about the meanings of the names or values Each usage defines a convention – ACAP Dataset Class – on what the names and values mean Only the clients care about this (usually)

ACAP Key Concepts Access Controls are Built In Inheritance Each attribute has an acl which defines what users can do with it Inheritance One part of the tree can inherit from another But can make local modifications that are not reflected in the parent Usage: department wide buddy lists ACAP URL: points to a tree locally or on another server Synchronization Multiple clients can access the data Versioning for collision detection, notifications to indicate if it changes under you

ACAP Primitives Rights Management Quotas Searching Boolean expressions on attributes Can limit number of responses, response pagination, sorting of response, list specific attributes to return STORE command Create, modify, delete entries Can be conditioned on a version number Can set multiple attributes at once Rights Management Can set and delete ACLS Can query for permissions visible to themselves Quotas Maximum amount of data per user

The Presence List Each entry in the tree is either another list or a presentity A presentity has attributes for The URI to subscribe to A display name An ACAP URL for an address book entry A list has attributes for A display name A URI to use to subscribe to it Inheritance is possible Department or company wide lists

Authorization Policy Each entry in the tree is a watcher or a list of watchers Each attribute specifies a permission Can they subscribe What attributes will they see “Inversion” of a black/white list Requires a well specified set of processing logic as part of dataset class Benefits of this model Allows for inheritance to work Avoids the needs for scripts (described previously in requirements document) Enables capabilities discovery Allows for operator defined permissions and user defined permissions I.e., “friend”

Permissions Notification Attributes Status attributes Presence-auth-list.onEvent.any .ontransition: from state to a state Etc. Content Attributes Presence-auth-list.content.tuples: list of tuples that can be seen Presence-auth-list.content.status-type: status types that can be seen Transformational Attributes “lying” Status attributes presence-auth-list.Accept.Any – anyone can subscribe presence-auth-list.accept.TOD – value is an iCal object for tod subscriptions Presence-auth-list.Accept.ReqTuples – authorize requested tuples Etc.

Permission Groups User defined sets of permissions For example, “friend” Accept any subscription Let them see non-work phone and IM Each group is defined by a set of primitive permissions

Capabilities List of permissions supported by the provider Both primitive and vendor-defined Includes textual description of the permission Allows to “Grey Out” UI components not available for this provider

Open Issues ACAP Dataset Model works well for us, but ACAP itself has some problems Based on a long-lived persistent TCP connection Doesn’t work well with intermittent connectivity SASL security not a good match for the rest of SIP No support for intermediaries Syntax not consistent with SIP

Proposal Specify SEACAP – SOAP Encoded ACAP Encompasses the query/response aspects of ACAP, omits the notifications Specify a SIP event package for data changes Receive a NOTIFY when a dataset has changed Benefits Makes use of protocols that are already on devices Works better for wireless – no longer a requirement for persistent TCP Can use any SIP/HTTP authentication mechanism Rfc822 and XML syntaxes Drawbacks May be less compact that ACAP