Requirements and Possible Mechanisms for File Transfer Services Within the Context of SIP Based Communication
draft-isomaki-sipping-file-transfer-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Markus Isomaki | ||
| Last updated | 2006-03-08 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)