Notifying RTSP Clients and Proxy Servers About Streams: The RTSP "REGISTER" Command
draft-finlayson-rtsp-register-command-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dr. Ross Finlayson | ||
| Last updated | 2015-04-21 (Latest revision 2014-10-18) | ||
| 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
We define a new RTSP command - named "REGISTER" - that allows a server (or a third party) to notify a RTSP client or a RTSP proxy server about a RTSP stream (given by a "rtsp://" URL). This also provides a mechanism whereby a client (or proxy server) on the public Internet can access a RTSP server that is behind a firewall or NAT.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)