60 likes | 211 Views
-additional-data. Brian Rosen Hannes Tschofenig. Fundamental Idea. Devices and services providers have data useful to PSAPs Examples of data include identification & contact data of SP, subscriber data, “class of service” provided by SP to subscriber
E N D
-additional-data Brian Rosen HannesTschofenig
Fundamental Idea • Devices and services providers have data useful to PSAPs • Examples of data include identification & contact data of SP, subscriber data, “class of service” provided by SP to subscriber • Draft seeks to standardize the form of this data, and how it’s transported
Transport • HTTPS Get of an XML structure defined by this document • URI to the XML carried in a SIP Call-Info header • Device or any/all SPs in the path could add such a header • As far as we know, this is non controversial
Data itself • Service Provider ID & contact data • Subscriber ID & contact data • “Class of Service” provided by SP • Device specific info • Includes hooks for things like telematics and sensor data
Discussion from prior meeting • Switch to XML representation of vcard • No need for 3rd party insertion OBO end user • Device can provide data • SP can provide any data it has • Can be more than one SP in path, each one can insert data • But none of that is OBO user • Identity of inserter will be in the data • No real issue with deletion of data. Not something we want to have, but no need for mechanisms to know it happened
Actions • Authors will update with XML vcard stuff + mime type containers • NEED MORE REVIEW • Need any more suggestions for content