1. Slide #1 Event Package for Device Information Mahfuzur Rahman (mahfuz@research.panasonic.com)mahfuz@research.panasonic.com Brijesh Kumar (kumarb@research.panasonic.com)kumarb@research.panasonic.com Bin Hu (bhu@motorola.com)bhu@motorola.com Ashir Ahmed (a.ahmed@ntt.com)a.ahmed@ntt.com

2. Slide #2 Draft Overview Event Package to retrieve device profile and status information Package name: device-info The Mime type in Accept header will differentiate between profile and status information Accept: application/device-profile+xml Accept: application/MyCamera+xml

3. Slide #3 Purpose Why we need this Device Monitoring Get Change in Operating Status

4. Slide #4 Device Profiles Device Profile only defines common format for core hardware related information which includes Mime type for status information Currently we do not define a common format for status information but it can be defined later This event package will use vendor specific Mime type for status information for different classes of devices. These Mime types will be registered with the IANA by the vendors

5. Slide #5 Core Profile Data Device Profile (only core information) Limited set of static attributes Device type Name Model URL Software Version Mime type format for status information Etc. Device Status Operating state Location Availability etc.

6. Slide #6 Feedback from Mailing List Cullen Jennings - made suggestions to include add an optional UUID to the profile add software version. To make the schema URL and name attributes of a schema object so that the device can lists multiple schema that it can support. Paul Kyzivat - suggested Device and AOR relationship clarification Add clarification to avoid ambiguity between device and service Also, additional clarification with regards to forking of Subscribe

7. Slide #7 Next Step Action!!!!! Accept as a Working Group Document