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 69 th IETF SIPPING WG July 2007 Miguel Garcia Marcin Matuszewski

History All decent communication suites provide some transfer of files between endpoints. We already have a file transfer mechanism with SIP draft-ietf-mmusic-file-transfer-mech-03.txt Unable to instantiate all use cases with a standard protocol Remote file directory Subscription to a picture collection available in a mobile phone Sharing a folder in commercial instant messaging systems

Documentation Three Internet-Drafts: Sharing Files 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 Files A Session Initiation Protocol (SIP) Event Package and Data Format for Describing Files Specifies a new file event package for describing files File Descriptions Extension to the Presence Information Data Format (PIDF) Extends PIDF by including the file data format Which are the evolution of the (today expired) previous 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 Main change: reduced scope to describe files only (previously: any resource)

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

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

The ‘file’ event package SUBSCRIBE Event: file 200 OK PUBLISH Event: file XML doc. including a description of available files 200 OK NOTIFY Event: file XML doc. including XML file description Alice is aware of the list of available files at Bob’s mobile device and laptop 200 OK PUBLISH Event: file XML doc. including a description of available files ESC

SIP file directory with presence SUBSCRIBE Event: presence 200 OK PUBLISH Event: presence PIDF including a resource description of available files 200 OK NOTIFY Event: presence PIDF including a description of available files 200 OK PUBLISH Event: presence PIDF including a resource description of available files ESC Alice is aware of the list of available files at Bob’s mobile device and laptop

Why SIP for file subscriptions? By using SIP, we have passed 95% of the pain: Authentication Authorization Rules Partial notification Diffs Filtering Integration with the communications suite and probably more Documented in a separate draft: draft-garcia-sipping-general-events-00.txt

file-metadata XML document A file XML document contains descriptions of one or more files Each file is modeled as an identity and one or more instances The identity describes the immutable properties of the file: MIME type Size Hash URN The instance describes metadata associated to the file and the endpoint that hosts the resource: URI Name Description Icon creation/modification/read date keywords file-metadata document File 1 Identity Instance 1 Instance 2 Instance n File 2 File n

file-metadata XML document image/jpeg FE8653DDAF371362F86D471913EE4A2CE2E coolpic.jpg This is my latest cool picture from my summer vacation 00a0c91e6bf T09:30:47+03: T10:24:34+03: T14:24:32+03:00 summer vacation

Other features (including missing ones) Subscription to selected files: Achieved by adding a filter (RFC 4661) to the SUBSCRIBE request Missing features: If owner edits the file, the file-metadata does not reflect correlation Should we investigate the subscription to a file? Indicating availability Changes of file, when it is edited Subscription with a filter won’t work if file is edited Need a URN to describe files? Investigate the relation with the ‘magnet’ URI

The big question The three drafts are in “raw” mode. Require quite some work Authors don’t want to use time inefficiently Is this work something that SIPPING should be working on? Are there interested folks who want to work on the topic?