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

1
SIP file directorydraft-garcia-sipping-file-shar
ing-framework-00.txtdraft-garcia-sipping-file-eve
nt-package-00.txtdraft-garcia-sipping-file-desc-p
idf-00.txt

• 69th IETF
• SIPPING WG
• July 2007
• Miguel Garcia ltmiguel.garcia_at_nsn.comgt
• Marcin Matuszewski ltmarcin.matuszewski_at_nokia.comgt

2
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

3
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
• 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)

4
File transfer push operation
INVITE sipbob_at_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
5
File transfer pull operation
INVITE sipbob_at_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
6
The file event package
PUBLISH Event file XML doc. including a
description of available files
SUBSCRIBE sipbob_at_example.com Event file
200 OK
200 OK
NOTIFY Event file XML doc. including XML file
description
PUBLISH Event file XML doc. including a
description of available files
200 OK
ESC
200 OK
Alice is aware of the list of available files at
Bobs mobile device and laptop
7
SIP file directory with presence
PUBLISH Event presence PIDF including a resource
description of available files
SUBSCRIBE sipbob_at_example.com Event presence
200 OK
200 OK
NOTIFY Event presence PIDF including a
description of available files
PUBLISH Event presence PIDF including a resource
description of available files
200 OK
ESC
200 OK
Alice is aware of the list of available files at
Bobs mobile device and laptop
8
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

9
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

10
file-metadata XML document

• lt?xml version"1.0" encoding"UTF-8"?gt
• ltfile-set xmlns"urnietfparamsxmlnsfile
  " version"123"gt
• ltfile id"id38sh12jd"gt
• ltidentity id"id9d8c9"gt
• ltmime-typegtimage/jpeglt/mime-typegt
• ltsizegt230432lt/sizegt
• ltsha1gt72245FE8653DDAF371362F86D4719
  13EE4A2CE2Elt/sha1gt
• ltidentitygt
• ltinstance id"idc989c00"gt
• ltnamegtcoolpic.jpglt/namegt
• ltdescriptiongtThis is my latest
  cool picture from my summer vacationlt/descriptiongt
  
• ltuser-gruugtsipmiguel.garcia_at_exampl
  e.comgrurnuuidf81d4fae-7dec-11d0-a765-00a0c91e
  6bf6lt/user-gruugt
• ltuser-aorgtsipmiguel.garcia_at_example
  .comlt/user-aorgt
• ltcreation-dategt2006-05-09T093047
  0300lt/creation-dategt
• ltmodification-dategt2006-05-09T1024
  340300lt/modification-dategt
• ltread-dategt2006-05-10T142432030
  0lt/read-dategt
• lticon-ptrgthttp//www.example.com/co
  olpic-icon.jpglt/icon-ptrgt
• ltkeywordsgt

11
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 wont work if file is
  edited
• Need a URN to describe files?
• Investigate the relation with the magnet URI

12
The big question

• The three drafts are in raw mode.
• Require quite some work
• Authors dont 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?