Subject: [Sipping] FW: I-D ACTION:draft-isomaki-sipping-file-transfer-00.txt

From: [email-masked]
Date: Wed, 26 Oct 2005 16:02:36 +0300

Hi,

There has been some interest in integrating "file transfer" as one of the services that can be used within the SIP communication framework, together with voice, video, IM, presence, conferencing and so on. There are also already many protocols and mechanisms for allowing this, including SIP content indirection, MSRP, HTTP, FTP and so on. However, "file transfer" covers multiple use cases (including 1-to-1 and multiparty situations), and it is not immediately clear which methods work in each of these cases. Also, always when there are multiple ways of doing the same thing, interoperability becomes a problem in practice.

I have written a draft which presents use cases and requirements for "file transfer" within the context of SIP based communication. The draft also very briefly discusses the potential options, such as MSRP and SIP content indirection.

At this point I would be interested in the following type of feedback:
- Do the use cases and the requirements make sense?
- Is there a need for any new standards track work to address any of the reqs, or would it be enough to document the use of existing protocols as BCP, Informational, etc.?
- What is the level of interest for this in general?

One reason why high level input on the interest would be useful is that OMA has requirements for this type of service. Typically OMA is willing to follow the IETF specs. In this case the question is whether IETF sees fit to do any more work in this area, or is it thought that the necessary mechanisms are already in place. 

Regards,
	Markus

> -----Original Message-----
> From: [email-masked]
> [mailto:[email-masked]]
> Sent: 20 October, 2005 22:50
> To: [email-masked]
> Subject: I-D ACTION:draft-isomaki-sipping-file-transfer-00.txt 
> 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> 
> 
> 	Title		: Requirements and Possible Mechanisms for File 
>                           Transfer Services Within the Context of SIP 
>                           Based Communication
> 	Author(s)	: M. Isomaki
> 	Filename	: draft-isomaki-sipping-file-transfer-00.txt
> 	Pages		: 11
> 	Date		: 2005-10-20
> 	
>    This document describes use cases and defines requirements for how
>    different types of file transfer services could be integrated into
>    the general Session Initiation Protocol (SIP) based communication
>    framework.  It also explores some of the possible solutions to meet
>    those requirements, either based on existing protocol mechanisms or
>    defining minor extensions to them.  The purpose of the 
> document is to
>    start the discussion on whether some new standardization work is
>    needed in this area.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-isomaki-sipping-file
-transfer-00.txt

To remove yourself from the I-D Announcement list, send a message to 
[email-masked] with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-isomaki-sipping-file-transfer-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[email-masked].
In the body type:
	"FILE /internet-drafts/draft-isomaki-sipping-file-transfer-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP