A No-Op Payload Format for RTP
draft-wing-avt-rtp-noop-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Flemming Andreasen | ||
| Last updated | 2005-05-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
This document defines an no-op payload format for the Real-time Transport Protocol (RTP), and a mechanism to request transmission of an early RTCP report. This can be used to verify RTP connectivity and to keep Network Address Translator (NAT) bindings and Firewall pinholes open.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)