RTC Provisioning Requirements draft-houri-speermint-rtc-provisioning-reqs-00 Avshalom Houri – IBM Edwin Aoki – AOL LLC Tim Rang - Microsoft
Motivation • RTC – Real Time Communication communities need a way to connect between them in easy and secure manner • Current experience is a cumbersome, manual and error prone negotiation • Provisioning is needed also in “open” environments: – Enable communities of users to share and obtain "profile" data for destinations they connect to, e. g. parameters, security certificates, etc. – Provide an entry point for other provisioning tasks, such as establishing permissions, policies, etc.
Definitions • Single Community – A server or set of servers that provide service to a community of users • Provisioning – The act of providing attributes between the communities. The attributes will provide easier and more secure connectivity between the communities
Core Requirements • Enable secure pushing and pulling provisioning data between the communities • Provision: – Security e. g. certificate data – Connectivity data – NAT/FW data – Encryption data – Allowed number of connections
Other Requirements • Services Data – List of services (N-way chat, file transfer) – Characteristics of each service – Policy for each service, E. g. • Subscribe refreshes • Error codes • Expected high limit usage profile • Immediate updates on changes to provisioning data
Clearing House • A service that facilitates interconnection between multiple communities • Can serve specific segment of industry or organizations: Financial, Scientific communities etc. • Clearing house provisioned data – List of enabled communities – Weather to be listed in communities list – White/black lists
Next? • Comments? • How to proceed with the draft?
Thanks!
Скачать презентацию RTC Provisioning Requirements draft-houri-speermint-rtc-provisioning-reqs-00 Avshalom Houri IBM
44d3958c27e3ec96d06323340d95433f.ppt