1 / 12

68 th IETF Prague, Check Republic SIPPING WG 23-March-2007

A mechanism for file directory with SIP draft-garcia-sipping-resource-sharing-framework-01.txt draft-garcia-sipping-resource-event-package-01.txt draft-garcia-sipping-resource-desc-pidf-00.txt. 68 th IETF Prague, Check Republic SIPPING WG 23-March-2007

hestia
Download Presentation

68 th IETF Prague, Check Republic SIPPING WG 23-March-2007

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. A mechanism for file directory with SIPdraft-garcia-sipping-resource-sharing-framework-01.txtdraft-garcia-sipping-resource-event-package-01.txtdraft-garcia-sipping-resource-desc-pidf-00.txt 68th IETF Prague, Check Republic SIPPING WG 23-March-2007 Miguel Garcia <miguel.an.garcia@nokia.com> Marcin Matuszewski <marcin.matuszewski@nokia.com> 1

  2. History • All decent communication suites allow transfer of files between endpoints • Requirements for file transfer already documented • draft-isomaki-sipping-file-transfer-00.txt • File transfer mechanism draft in progress • draft-ietf-mmusic-file-transfer-mech-00.txt • This discussion is about these three resource sharing drafts: • draft-garcia-sipping-resource-sharing-framework-01.txt • draft-garcia-sipping-resource-event-package-01.txt • draft-garcia-sipping-resource-desc-pidf-00.txt 2

  3. File transfer: push operation INVITE sip:bob@example.com SDP describes the file to be sent 200 OK SDP describes the file to be received ACK MSRP SEND Including a file User is presented with the offer. He can accept of reject the file transfer MSRP 200 OK 3

  4. File transfer: pull operation How can Alice know the description of a file stored a Bob’s device? INVITE sip:bob@example.com SDP describes the file to be received 200 OK SDP describes the file to be sent ACK MSRP SEND Including a file User is presented with the offer. He can accept of reject the file transfer MSRP 200 OK 4

  5. SIP file directory: The ‘resource’ event package PUBLISH Event: resource XML doc. including a resource description of available resources: files, printers, etc. SUBSCRIBE sip:bob@example.com Event: resource 200 OK 200 OK NOTIFY Event: resource XML doc. including a resource description of available resources: files, printers, etc. PUBLISH Event: resource XML doc. including a resource description of available resources: files, printers, etc. 200 OK ESC 200 OK Now Alice is aware of the list of available files at Bob’s mobile device and laptop 5

  6. ‘resource’ event package end-to-end SUBSCRIBE sip:bob@example.com Event: resource 200 OK NOTIFY Event: resource XML doc. including a resource description of available resources: files, printers, etc. 200 OK 6

  7. SIP file directory with presence PUBLISH Event: presence PIDF including a resource description of available files SUBSCRIBE sip:bob@example.com Event: presence 200 OK 200 OK NOTIFY Event: presence PIDF including a resource description of available resources: files, printers, etc. PUBLISH Event: presence PIDF including a resource description of available resources: files, printers, etc. 200 OK Now Alice is aware of the list of available files at Bob’s mobile device and laptop 200 OK 7

  8. Why SIP? • By using SIP, we have passed 95% of the pain: • Authentication • Authorization • Rules • Partial notification • Diffs • Filtering • and probably more 8

  9. A resource XML document contains descriptions of one or more resources A resource may be a file, a printer, a chat room hosted in an endpoint, etc. Each resource is modeled as an identity and one or more instances The identity describes the resource: MIME type Size Hash URN The instance describes metadata associated to the resource and the endpoint that hosts the resource: URI Name Description Icon creation/modification/read date keywords Resource XML document Resource XML Document Resource 1 Identity Instance 1 Instance 2 Instance n Resource 2 Resource n 9

  10. Resource XML document <?xml version="1.0" encoding="UTF-8"?> <resource-setxmlns="urn:ietf:params:xml:ns:resource"version="123"> <resourceid="id38sh12jd"> <identityid="id9d8c9"isfile="true"> <mime-type>image/jpeg</mime-type> <size>230432</size> <sha1>72245FE8653DDAF371362F86D471913EE4A2CE2E</sha1> </identity> <instanceid="idc989c00"> <name>coolpic.jpg</name> <description>This is my latest cool picture from my summer vacation</description> <user-gruu>sip:miguel.an.garcia@example.com;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6</user-gruu> <user-aor>sip:miguel.an.garcia@example.com</user-aor> <creation-date>2006-05-09T09:30:47+03:00</creation-date> <modification-date>2006-05-09T10:24:34+03:00</modification-date> <read-date>2006-05-10T14:24:32+03:00</read-date> <icon-ptr>http://www.example.com/coolpic-icon.jpg</icon-ptr> <keywords> <keyword>summer</keyword> <keyword>vacation</keyword> </keywords> </instance> </resource> </resource-set> 10

  11. Documentation • Three Internet-Drafts submitted: • A Framework for Sharing Resources with the Session Initiation Protocol (SIP) • Untidy collection of use cases, ideas, and solutions • Should be really a generic framework describing what and how to do it • A Session Initiation Protocol (SIP) Event Package and Data Format for Describing Generic Resources • New resource event package for describing files • Nokia has an IPR declaration • Resource Descriptions Extension to the Presence Information Data Format (PIDF) • Extending PIDF by including the resource data format 11

  12. The big question Is there enough interest to pursue some of the ideas and enabling the use cases and other similar to those described in the framework document? 12

More Related