A No-Op Payload Format for RTP
draft-ietf-avt-rtp-no-op-04
| Document | Type |
Expired Internet-Draft
(avt WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Flemming Andreasen | ||
| Last updated | 2007-05-22 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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). This packet is not played out by receivers. It can be useful as a way to keep Network Address Translator (NAT) bindings and Firewall pinholes open. Other uses are discussed in the document.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)