Controlling FLUTE sessions with Real-Time Streaming Protocol (RTSP)
draft-lohmar-mmusic-rtsp-flute-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Thorsten Lohmar | ||
| Last updated | 2006-12-19 | ||
| 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
File Delivery over Unidirectional Transport (FLUTE) is defined in RFC 3926 and provide an extensible framework for delivering any type of files over UDP. FLUTE is mostly intended for IP multicast communication, but the use with IP unicast is not excluded. Real- time Streaming Protocol (RTSP) allow the play-out of media packets to multicast and unicast sessions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)